Sorry, you need to enable JavaScript to visit this website.

Error In 04_MiniZed_FSBL_Boot_2017.1_01?

Zedboard forums is currently read-only while it under goes maintenance.

2 posts / 0 new
Error In 04_MiniZed_FSBL_Boot_2017.1_01?

Granted I am using 2017.3, however, I still believe there is an error in MiniZed tutorial #4, "MiniZed: Boot from QSPI using FSBL". Specifically, in the section, "Experiment 3: Write and boot from QSPI", step 1, I  found that I had to set up the MiniZed for Flash mode, not Cascaded JTAG mode (SW1 to the F<BOOT position). Secondly, in "Figure 4 - Program the QSPI Flash Memory" the "Program" button will not enable until the FSBL file is inserted. I used:
My apologies, in advance, if this has already been addressed in the forms, or I am wrong, but I could not find a reference to this particular issue. I could be wrong, but can't believe I would have successfully completed the exercise using these changes if I am wrong.
Has anyone else had this issue?

Hello Dave,

Hello Dave,

The instructions given are correct. Adrressing your concerns

As far as using Vivado 2017.3 that is most likely OK, however I have not verified the lab flow myself.


1. "Experiment 3: Write and boot from QSPI", step 1 - it is best practices to have your device in JTAG boot mode while programing the QSPI over your JTAG connection. That is not to say if it was in QSPI boot mode when you programmed it would not work, programming the QSPI over JTAG while in QSPI is not the suggested tool flow while using the Program feature in SDK.


2. Secondly, in "Figure 4 - Program the QSPI Flash Memory" the "Program" button will not enable until the FSBL file is inserted

- I believe you are acutally refering to figure 12 correct? By saying you completed the lab successfully do you refer to the blue led enumerating when powering on? The end goal from lab 4 is to have you program the .mcs file you created in experiment 2 into your MiniZed and then run it over QSPI boot. Try programming in the file you created in lab 2 then enable a uart connection to verify the Peripheral test is working properly.