QSPI programming fails in Hardware Manager

[thngttr]

Hello, everyone.

We have designed custom xc7z010clg400 board with MT25QL01GBBB8E12 QSPI Flash memory chip, to which we were attempting to program a firmware (BOOT.bin: fsbl+bitstream).

1) We started with Vivado 2017.4, but got unsuccessful verification result when programming BOOT.bin/BOOT.msc from Hardware Manager, while the programming itself was reported as successful. After board reboot in QSPI mode, bitstream was not actually downloaded to FPGA (Done pin is low), but we are still able to successfully download bitstream via JTAG mode.

We have also tested small file (7KB) downloading using Hardware Manager, and verification was successful. But while reading Flash memory from application, data wasn't actually written at all.

Blank Check never returned success in any case attempted.

We also used SDK 2017.4 with same results.

2) After that we installed the latest version of Vivado - 2018.2.1.
Hardware manager results:
- very quick and reported successful operations: erase, blank check, program and verify.

Performing Erase Operation...
Erase Operation successful.
INFO: [Xicom 50-44] Elapsed time = 0 sec.
Performing Program Operation...
Program Operation successful.
INFO: [Xicom 50-44] Elapsed time = 0 sec.
Performing Verify Operation...
INFO: [Xicom 50-44] Elapsed time = 1 sec.
Verify Operation successful.
INFO: [Labtoolstcl 44-377] Flash programming completed successfully

- after rebooting in QSPI mode, bitsteam was never downloaded to FPGA.

- changing Address range from Configuration File to Entire Configuration File didn't change result, aside from programming time.

SDK 2018.2.1 results:
- successful programming. Successful verification. Successful boot in QSPI mode (Done pin is high).

Also maybe worth mentioning that FSBL file size is 341 KB, while TRM says the limit is 192 KB.

So the question is - what is the problem with hardware manager, while SDK is OK?

Thanks in advance for any help.

[gudishak]

@thngttr,

Can you enable debug logs as mentioned in below Answer Record to check what went wrong while programing form Vivado?

https://www.xilinx.com/support/answers/59272.html

Regards
Kranthi
--------------------------
Don't forget to reply, kudo, and accept as solution.

[gudishak]

Can you please update on this issue?

[thngttr]

@gudishak Oh, really sorry for the delay!
So, output in Hardware Manager 2018.2.1:

set_property PROGRAM.ADDRESS_RANGE  {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
set_property PROGRAM.FILES [list "F:/Projects/BigCNC/Xilinx/Linux_Test/BOOT.BIN" ] [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
set_property PROGRAM.BIN_OFFSET {0} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
set_property PROGRAM.ZYNQ_FSBL {F:/Projects/BigCNC/Xilinx/Linux_Test/fsbl.elf} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
set_property PROGRAM.CHECKSUM  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
startgroup 
program_hw_cfgmem -hw_cfgmem [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z010_1] 0]]
f probe 0 0 0
Performing Erase Operation...
Erase Operation successful.
INFO: [Xicom 50-44] Elapsed time = 3 sec.
Performing Program Operation...
Program Operation successful.
INFO: [Xicom 50-44] Elapsed time = 7 sec.
Performing Verify Operation...
INFO: [Xicom 50-44] Elapsed time = 8 sec.
Verify Operation successful.
INFO: [Labtoolstcl 44-377] Flash programming completed successfully
program_hw_cfgmem: Time (s): cpu = 00:00:01 ; elapsed = 00:00:21 . Memory (MB): peak = 1638.980 ; gain = 0.281
endgroup

With no actual success, as before. BOOT.bin (file we were programming)  is 1 357 KB in size.

[stephenm]

Can you enable the debug in the fsbl, and regenerate the boot.bin and try again. Here we will see what the fsbl is doing