clifford changed the topic of #yosys to: Yosys Open SYnthesis Suite: http://www.clifford.at/yosys/ -- Channel Logs: https://irclog.whitequark.org/yosys
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
attie has joined #yosys
attie has quit [Ping timeout: 258 seconds]
Forty-Bot has quit [Ping timeout: 245 seconds]
PyroPeter has quit [Ping timeout: 246 seconds]
stzsch has joined #yosys
PyroPeter has joined #yosys
rohitksingh has quit [Ping timeout: 265 seconds]
_whitelogger has joined #yosys
Forty-Bot has joined #yosys
rohitksingh has joined #yosys
Jybz has joined #yosys
emeb has quit [Quit: Leaving.]
citypw has joined #yosys
Jybz has quit [Quit: Konversation terminated!]
forksand has quit [Ping timeout: 276 seconds]
forksand has joined #yosys
emeb_mac has quit [Ping timeout: 265 seconds]
awordnot has quit [Read error: Connection reset by peer]
awordnot has joined #yosys
phantomcircuit has quit [Ping timeout: 244 seconds]
phantomcircuit has joined #yosys
attie has joined #yosys
citypw has quit [Remote host closed the connection]
citypw has joined #yosys
rohitksingh has quit [Ping timeout: 245 seconds]
dys has joined #yosys
PyroPeter has quit [Ping timeout: 245 seconds]
PyroPeter has joined #yosys
_whitelogger has joined #yosys
PyroPeter has quit [Ping timeout: 245 seconds]
flaviusb has quit [Quit: Leaving.]
PyroPeter has joined #yosys
<janrinze> daveshah: Any chance we will see updated tools that properly write to the flash of ECP5 eval board?
PyroPeter has quit [Ping timeout: 276 seconds]
PyroPeter has joined #yosys
Thorn has quit [Ping timeout: 265 seconds]
Thorn has joined #yosys
voxadam has quit [Ping timeout: 246 seconds]
<ZipCPU> janrinze: What ECP5 eval board are you using?
dys has quit [Ping timeout: 276 seconds]
Thorn has quit [Ping timeout: 258 seconds]
Thorn has joined #yosys
<ZipCPU> I just ask because ... I've been writing to the external (QSPI) flash chips for some time on Xilinx/Intel/iCE40/ECP5 boards without too much hassle
Thorn has quit [Ping timeout: 264 seconds]
dys has joined #yosys
<janrinze> ZipCPU: the one from lattice. http://www.latticesemi.com/ecp5-evaluation
<tpb> Title: ECP5 Evaluation Board - Lattice Semiconductor (at www.latticesemi.com)
voxadam has joined #yosys
<ZipCPU> Bummer. I was hoping it would be the one I was working with: http://www.latticesemi.com/Products/DevelopmentBoardsAndKits/ECP5VersaDevelopmentKit.aspx
<tpb> Title: ECP5 Versa Development Kit - Lattice Semiconductor (at www.latticesemi.com)
<ZipCPU> The problem with a "generic" flash writer is that ... there are so many different incompatible flash devices out there
<ZipCPU> My own "generic" solution depends upon software to detect the flash, and then add in special commands for certain flash chips. It's by no means complete.
<tpb> Title: Building a universal QSPI flash controller (at zipcpu.com)
<ZipCPU> I also just updated the ECP5 demo: https://github.com/ZipCPU/zipversa/tree/dev
<tpb> Title: GitHub - ZipCPU/zipversa at dev (at github.com)
<janrinze> The versa board is nice. I prefer stand-alone boards myself.
<ZipCPU> I'm using it as a stand-alone ;)
<ZipCPU> I have yet to fire up either the SDRAM or the PCIe interface
<ZipCPU> That said, it's not the board that you have, so my work might (or might not) help you :/
citypw has quit [Ping timeout: 258 seconds]
<janrinze> does your build flash the design or just upload it to the ecp5?
<janrinze> I see in the .cfg that openocd will program the ecp5
forksand has quit [Ping timeout: 276 seconds]
<ZipCPU> The openOCD is used to load the design into the FPGA via JTAG. The zipload.cpp program (based upon flashdrvr.cpp) is used to actually write to the flash once the design is loaded.
<ZipCPU> You can find both zipload.cpp and flashdrvr.cpp in the sw/host directory, since they'll run from an external (PC) host
<janrinze> would this work over USB? the versa has PCI-bus, right?
<ZipCPU> I use it over a USB serial port, yes
<janrinze> Okay. interesting. I can try build it and see how that goes,
<ZipCPU> This particular design also has some amount of serial port compression going over the command channel
<janrinze> i remember that compression was particularly difficult with programming the ecp5
<ZipCPU> I didn't say that I was compressing the ECP5 image, just the serial port command channel
<janrinze> okay. Does the zipcpu write the flash?
<ZipCPU> No
<janrinze> ah. good.
<ZipCPU> The dev branch doesn't even have the ZipCPU enabled in it anymore--the customer wanted a picoRV
<ZipCPU> That said, the PicoRV isn't involved in writing the flash either.
<ZipCPU> You can see a picture of the serial port command channel processing in Fig 1 of this post: http://zipcpu.com/blog/2017/06/05/wb-bridge-overview.html
<tpb> Title: An Overview of a Wishbone-UART Bridge (at zipcpu.com)
forksand has joined #yosys
<janrinze> so it requires the wishbone-uart bridge.
<ZipCPU> You'd need something to communicate data from the PC/host to the FPGA
<janrinze> in order to make that work, first the design with a wishbone-uart bridge needs to be uploaded to the FPGA, correct?
<ZipCPU> Yes
<janrinze> okay, a two stage uploader would work, i guess.
<ZipCPU> I think that's the way most of the commercial loaders work
<janrinze> currently I use the python script that creates a script for openocd.
Thorn has joined #yosys
emeb has joined #yosys
Jybz has joined #yosys
rohitksingh has joined #yosys
rohitksingh has quit [Ping timeout: 252 seconds]
Jybz has quit [Quit: Konversation terminated!]
rohitksingh has joined #yosys
MrBismuth has quit [Read error: Connection reset by peer]
rohitksingh has quit [Ping timeout: 245 seconds]
MrBismuth has joined #yosys
rohitksingh has joined #yosys
emeb_mac has joined #yosys
rohitksingh has quit [Ping timeout: 245 seconds]
rohitksingh has joined #yosys
PyroPeter has quit [Ping timeout: 264 seconds]
gnufan_home has joined #yosys
PyroPeter has joined #yosys
rohitksingh has quit [Ping timeout: 246 seconds]