You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
blinky example's Makefile has the "make prog" target. This doesn't program the flash. When power is removed & reconnected, the bitstream that was flashed earlier gets loaded. This is confusing - for beginners at-least.
The openFPGALoader tool works with the EVN. Adding this as an optional flashing step in the makefile would help those starting off. e.g., the "flash" target would look like:
flash: ${PROJ}.bit
openFPGALoader -f $<
The text was updated successfully, but these errors were encountered:
Lattice Deployment tool can also generate an SVF file to do background programming per
Programming External SPI Flash through JTAG for ECP5/ECP5-5G Technical Note FPGA-TN-02050 https://latticesemi.com/view_document?document_id=52228
Many years ago I added PLD support to OpenOCD for programming & reconfiguring ECP3 without needing to generate SVF, maybe I should get the patch up to date and add a flashing mode https://github.com/shuckc/urjtag/pull/4/files . The benefit of doing this 'within' OpenOCD is you get support for all the flash models for free.
blinky example's Makefile has the "make prog" target. This doesn't program the flash. When power is removed & reconnected, the bitstream that was flashed earlier gets loaded. This is confusing - for beginners at-least.
The openFPGALoader tool works with the EVN. Adding this as an optional flashing step in the makefile would help those starting off. e.g., the "flash" target would look like:
The text was updated successfully, but these errors were encountered: