Actions
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 354 subscribers
  • Views 770 views
  • Users 0 members are here
Related

Programming QSPI Without SD card

Former Member

Hi,

I am trying to program the QSPI without using the SD card. I am aware that I can use JTAG and I want to; however, in the boot guide 14.1 doc, it states to still use the SD to load BOOT.BIN.

Programming the QSPI via SD is really simple (fatload then sf write) and all you need is BOOT.BIN, zImage, ramdisk.image.gz, and devicetree.dtb.

Can someone outline how to program the QSPI via JTAG or USB using the same programming approach as SD (not having to use the SDK)?

Parents
  • 0

    Basically, I read that to program the QSPI via JTAG you have to use the SDK and the SD card. You only need the SD card to load BOOT.BIN and then once up and running, you can push everything over with JTAG.

    For my situation, I can bring up the board with the SD card once, but then I have to disable the SD slot afterwards -- leaving no way to reprogram the flash. I really like how via the SD slot you can push over the BOOT.BIN, Kernel, FS, and devicetree separately and not have it combined it in a .mcs file because I am constantly changing my filesystem and updating the Zedboard is simple when the objects are separated liked this. I also had to change where the boot loader expects the files located in memory addresses because i had to make more room for my filesystem.

    So assuming I can stop the loader and access the zed-boot menu, I am looking for a way to fatload files into RAM and sf write them into QSPI. Is there a way to push these files individually or is the only option over JTAG by mcs format?

Reply
  • 0

    Basically, I read that to program the QSPI via JTAG you have to use the SDK and the SD card. You only need the SD card to load BOOT.BIN and then once up and running, you can push everything over with JTAG.

    For my situation, I can bring up the board with the SD card once, but then I have to disable the SD slot afterwards -- leaving no way to reprogram the flash. I really like how via the SD slot you can push over the BOOT.BIN, Kernel, FS, and devicetree separately and not have it combined it in a .mcs file because I am constantly changing my filesystem and updating the Zedboard is simple when the objects are separated liked this. I also had to change where the boot loader expects the files located in memory addresses because i had to make more room for my filesystem.

    So assuming I can stop the loader and access the zed-boot menu, I am looking for a way to fatload files into RAM and sf write them into QSPI. Is there a way to push these files individually or is the only option over JTAG by mcs format?

Children
No Data