I used Quartus Lite 19.1
I used @thaler’s u-boot repo
I checked out branch socfpga_v2019.04
I used the exact script from post 9 that @thaler posted with the changes in u-boot that I made explicitly in post 7. I compiled the script not as the name he compiled it to (which was boot.img) and made changes to the file names in the script to match my files, and named my compiled script u-boot.scr to match the changes I made in the u-boot environment variables.
- the compiled device tree (in my case socfpga_cyclone5_socdk.dtb)
- the kernel boot image (zImage)
- the rbf (in my case I called it hps_only.rbf)
in the rootfs in the /boot/ directory as thalers script would suggest.
I used the make_image.py script documented in https://rocketboards.org/foswiki/Documentation/BuildingBootloader
and ran it with this command
sudo ./make_sdimage.py -f \
-P u-boot-with-spl.sfp,num=3,format=raw,size=10M,type=A2 \
-P sdfs/*,num=1,format=vfat,size=100M \
-P rootfs/*,num=2,format=ext3,size=300M \
-s 512M \
Where the ./sdfs had the compiled u-boot.scr
and ./rootfs had the root file system with the extra files added in the /boot directory as described above.
Copied the sdcard_cv.img onto the sdcard using Balena Etcher
If you can get into Linux, I would suggest you play with the fpga manger. I was able to read the status and state files for fpga0. The state was “powered off”. That alerted me that there was something wrong at the board level. That’s when I rechecked the electrical connections and reviewed the DIP switch settings. If your fpga is powered off, but you are sure your DIP switches and other circuit settings are right, maybe your board has an electrical problem.
Hope this helps.