We are programming QSPI flash with a custom board which requires the Zynq UltraScale+ device to boot in JTAG mode from both XSDK and Vivado Hardware Manager.
QSPI programming on a ZCU102 board requires the Zynq UltraScale+ device to boot in JTAG mode from both XSDK and Vivado Hardware Manager.
Note: this Answer record applies to the 2017.2 release as well as earlier versions. Please see below for differences.
The programming flow in 2017.2 and earlier is to set the boot mode pins to JTAG and issue a PS_POR_B before programming the QSPI.
This tool limitation will be removed in 2017.3.
The programming flow also requires you to specify an FSBL that runs on A53 (an FSBL running on R5 will not work) to help the programmer to initialize the system.
If you are QSPI programming with SDK 2017.2 and earlier, the FSBL should be generated for an A53 processor only.
For the 2017.3 SDK and later versions, FSBL can run from either an A53 or R5 processor while QSPI indirect programming:
|Boards & Kits||