cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
1,370 Views
Registered: ‎09-30-2017

zcu102: restoring flash with SDK's GUI

Jump to solution

Hello,

 

I used the 'Program Flash Memory' window in order to restore the QSPI to it's original image.

The settings I used are:

Programming.PNG

The programming completed OK according to the following output:

cmd /C program_flash -f \
C:\Users\990598\Desktop\Zynq\rdf0383-zcu102-restoring-flash-c-2017-2\zcu102_restore_flash\blinkbist.MCS \
-offset 0 -flash_type qspi_dual_parallel -fsbl \
C:\Users\990598\Desktop\Zynq\rdf0383-zcu102-restoring-flash-c-2017-2\zcu102_restore_flash\zynq_mp_fsbl.elf \
-cable type xilinx_tcf url TCP:127.0.0.1:3121

****** Xilinx Program Flash
****** Program Flash v2017.2 (64-bit)
**** SW Build 1909853 on Thu Jun 15 18:39:09 MDT 2017
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

Connecting to hw_server @ TCP:127.0.0.1:3121

Connected to hw_server @ TCP:127.0.0.1:3121
Available targets and devices:
Target 0 : jsn-JTAG-SMT2NC-210308A3C27C
Device 0: jsn-JTAG-SMT2NC-210308A3C27C-24738093-0

Retrieving Flash info...

Initialization done, programming the memory
BOOT_MODE REG = 0x0000
f probe 0 0 0

Performing Erase Operation...
Erase Operation successful.
INFO: [Xicom 50-44] Elapsed time = 175 sec.
Performing Program Operation...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Program Operation successful.
INFO: [Xicom 50-44] Elapsed time = 736 sec.

Flash Operation Successful

 

But after power up, the original FSBL is not running. 

 

In the xsdb window I got:

143: couldn't open "C:/zcu102_ipi/zcu102_ipi.sdk/zynq_mp_fsbl/Debug/../src/xfsbl_exit.S": no such file or directory
xsdb% Info: Cortex-A53 #0 (target 9) Running
xsdb% Info: Cortex-A53 #0 (target 9) Stopped at 0xffff181c (External Debug Request)
Info: Cortex-A53 #0 (target 9) Running
xsdb% Info: Cortex-A53 #0 (target 9) Stopped at 0xffff181c (External Debug Request)
xsdb% Info: Cortex-A53 #0 (target 9) Running
xsdb% Info: Cortex-A53 #0 (target 9) Stopped at 0xffff181c (External Debug Request)
xsdb% Info: Cortex-A53 #0 (target 9) Running

....

Then I tried progrmming from the command window with:

program_flash -f blinkbist.mcs -offset 0 -flash_type qspi_dual_parallel -fsbl zynq_mp_fsbl.elf -blank_check -verify

 

This worked Ok.

Is there any difference between the GUI programming to the CMD one ?

 

Thank you,

Zvika 

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Xilinx Employee
Xilinx Employee
1,943 Views
Registered: ‎10-06-2016

Hi @zvivered

 

There should not be any difference between them, as at the end of the day the GUI will call to program_flash tool. Taking a look to the log there a few differences between two use cases:

 

cmd /C program_flash -f \
C:\Users\990598\Desktop\Zynq\rdf0383-zcu102-restoring-flash-c-2017-2\zcu102_restore_flash\blinkbist.MCS \
-offset 0 -flash_type qspi_dual_parallel -fsbl \
C:\Users\990598\Desktop\Zynq\rdf0383-zcu102-restoring-flash-c-2017-2\zcu102_restore_flash\zynq_mp_fsbl.elf \
-cable type xilinx_tcf url TCP:127.0.0.1:3121

 

program_flash -f blinkbist.mcs -offset 0 -flash_type qspi_dual_parallel -fsbl zynq_mp_fsbl.elf -blank_check -verify

 

Take a look to if the files you are using are the same ones, as in one of them you are using absolute paths and relatives in the other one ;)


Ibai
Don’t forget to reply, kudo, and accept as solution.

View solution in original post

0 Kudos
2 Replies
Highlighted
Xilinx Employee
Xilinx Employee
1,944 Views
Registered: ‎10-06-2016

Hi @zvivered

 

There should not be any difference between them, as at the end of the day the GUI will call to program_flash tool. Taking a look to the log there a few differences between two use cases:

 

cmd /C program_flash -f \
C:\Users\990598\Desktop\Zynq\rdf0383-zcu102-restoring-flash-c-2017-2\zcu102_restore_flash\blinkbist.MCS \
-offset 0 -flash_type qspi_dual_parallel -fsbl \
C:\Users\990598\Desktop\Zynq\rdf0383-zcu102-restoring-flash-c-2017-2\zcu102_restore_flash\zynq_mp_fsbl.elf \
-cable type xilinx_tcf url TCP:127.0.0.1:3121

 

program_flash -f blinkbist.mcs -offset 0 -flash_type qspi_dual_parallel -fsbl zynq_mp_fsbl.elf -blank_check -verify

 

Take a look to if the files you are using are the same ones, as in one of them you are using absolute paths and relatives in the other one ;)


Ibai
Don’t forget to reply, kudo, and accept as solution.

View solution in original post

0 Kudos
Highlighted
Adventurer
Adventurer
1,298 Views
Registered: ‎09-30-2017
Thank you very much !
0 Kudos