Programming QSPI Without SD card

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)?

0 bhfletcher over 12 years ago

When you say JTAG, are you OK using iMPACT?
Bryan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 12 years ago

I'm not sure what iMPACT is off hand. I'm just looking for an option to program the flash without using SD at all. *If there is one
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bhfletcher over 12 years ago

iMPACT is Xilinx' JTAG configuration tool which traditionally was used to configure FPGAs but has now also been adapted to programming Flash attached to Xilinx devices. You get it with an ISE tool install, or you can install the Lab Tools version. Go to this URL and browse down the page for the Lab Tools.
http://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/design-tools.html

SDK can also program the Flash, and this is probably the easiest way to do things in development. You mention in your original post that you don't want to use SDK. Is that right?

Bryan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 12 years ago

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 zedhed over 12 years ago

Hi pkaye,

I just wanted to clear something up that is not clear from the thread here. Are you running Linux on your ZedBoard? If so, you can FTP the desired QSPI components to the Root File System and then write those files to the MTD partitions with the flashcp command. We are doing this today for MicroZed and there is a reference design tutorial posted that covers the MTD write process.

If you are not running Linux, do you have access to Ethernet? If so, you can TFTP files into memory first and then "sf write" like you are used to.

Take a look at this Wiki page to see how this is done on other Zynq target boards for PL reconfig.

http://www.wiki.xilinx.com/Zynq+AP+SoC+-+Programmable+Logic+Configuration+via+Ethernet

Regards,

-Kevin
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel