With two Genesys-ZU 3EG boards, one boots from QSPI the other fails in the FSBL

[John J]

I have two 3EG boards and a 5EV board.  They are both current revision boards and were bought in late 2021 and early 2023.

I am testing booting multi-core bare metal apps from QSPI on the 3EG boards.  The FSBL fails on just one of the 3EG boards.  It also boots on a 5EV board.  All boards function properly via JTAG boot.  The FSBL output of the 3EG boards is shown below.

This is failure output.  (The bare metal project uses all 6 cores.)

Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 30 2023  -  16:08:38
MultiBootOffset: 0x0
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
XFsbl_SpkVer: XFSBL_ERROR_INVALID_EFUSE_SELECT
Failure at boot header authentication
Boot Device Initialization failed 0x74
Fsbl Error Status: 0x0
Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 30 2023  -  16:08:38
MultiBootOffset: 0x400
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed 
Boot Device Initialization failed 0x19
Fsbl Error Status: 0x0
Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 30 2023  -  16:08:38
MultiBootOffset: 0x800
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed 
Boot Device Initialization failed 0x19
Fsbl Error Status: 0x0
Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 30 2023  -  16:08:38
MultiBootOffset: 0xC00
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed 
Boot Device Initialization failed 0x19
Fsbl Error Status: 0x0
Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 30 2023  -  16:08:38
MultiBootOffset: 0x1000
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed 
Boot Device Initialization failed 0x19
Fsbl Error Status: 0x0
Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 30 2023  -  16:08:38
MultiBootOffset: 0x1400
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed 
Boot Device Initialization failed 0x19
Fsbl Error Status: 0x0
Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 30 2023  -  16:08:38
MultiBootOffset: 0x1800
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed 
Boot Device Initialization failed 0x19
Fsbl Error Status: 0x0
Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 30 2023  -  16:08:38
MultiBootOffset: 0x1C00
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed 
Boot Device Initialization failed 0x19
Fsbl Error Status: 0x0

This is the working output:

Xilinx Zynq MP First Stage Boot Loader 
Release 2022.1   Oct 31 2023  -  13:29:16
MultiBootOffset: 0x0
Reset Mode      :       System Reset
Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU3EG
Digilent Genesys ZU board-specific init
QSPI 32 bit Boot Mode 
FlashID=0x9D 0x60 0x19
Non authenticated Bitstream download to start now
PL Configuration done successfully 
Initializing TCM ECC
Initializing TCM ECC
PMU-FW is not running, certain applications may not be supported.
Protection configuration applied
PL Configuration done successfully 
Exit from FSBL
...
[App output not shown]

What is going on with the failing board?

Edited October 31, 2023 by John J

[JColvin]

Hi @John J,

I've reached out to an engineer with a bit more insight into the Genesys ZU; however they are out of the office until sometime next week.

Thanks,
JColvin

[John J]

Thank you @JColvin.

[John J]

❓

[JColvin]

Hi @John J,

The engineer who most recently worked with the Genesys ZU QSPI flash (thinkthinkthink) is out of office for longer than I expected, though I was asked to clarify the following information:

Are the two Genesys ZU 3EG boards using the same file programmed into them, or are the running different projects.

You were already on this thread from before, https://forum.digilent.com/topic/26069-unable-to-flash-qspi-vivado-rev-20221-5ev-eval-board/, and the engineer I talked to hasn't observed teh XFSBL_ERROR_INVALID_EFUSE_SELECT on the Genesys 3EG, but did you happen to try the QSPI x2 workaround that got mentioned at the end of the thread?

If you encountered this error with the same file programmed into both boards QSPI flash memories and the x2 mode workaround is not working, some further investigation will be needed.

Let me know what you learn.

Thanks,
JColvin

 

[John J]

I have tried using the same compiled binary file with the two 3EG boards and the same Vivado+computer to program all three boards.  I have also tried a second computer, a different Vivado version and other HW/SW projects.  In all cases there is just one board that does not run the executables correctly, but passed the verification test.

The QSPI x2 mode using an appropriately modified hardware configuration for the "Init File" made no difference.

I'm programming with the method that my colleague found in that same post you just mentioned.  Without using that method, the flash won't even properly verify on any board.

I did not try the x2 mode with the Digilent FSBL, but so far all of my attempts point to an issue with one particular board.

We also have another 5EV at a different facility that my colleague was using to come up with the programming method listed in the other post, and it was working fine back then too.

Thank you for your response.

Edited November 9, 2023 by John J

[JColvin]

Hi @John J,

If the two boards are showing different behaviors with the same .bin and based on everything else you have tried, I am inclinded to think that there is some sort of hardware error on the board and that you should work on getting it replaced.

If you purchased the board directly from Digilent, please private message me the following information:

- Order Number
- Purchase date
- Serial number of the board (on the barcode sticker that starts with "D")
- Preferred email contact so that our Sales team can follow up with for any additional information that I don't have access to (such as confirmation of shipping address)

If you instead purchased the 3EG from a distributor (such as Mouser or RS Components), you will need to contact them for their own RMA process.

Let me know if you have any questions.

Thanks,
JColvin