cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Visitor
Visitor
983 Views
Registered: ‎09-10-2019

programming flash failes

When I tring to programing flash via vivado it failes, so Im tring to ust program_flash application
and it said that he can varify it.
when i turn off and on the power i see that the now program didn't flashed to the device.
what am i doing wrong?

 

home@home-ThinkPad-E590:/opt/Xilinx/SDK/2017.4/bin$ sudo ./program_flash -f /home/Xilinx/proj/images/BOOT.bin -flash_type qspi_single -verify -fsbl /home/Xilinx/proj/images/fsbl_golden.elf
[sudo] password for home:

****** Xilinx Program Flash
****** Program Flash v2017.4 (64-bit)
**** SW Build 2086221 on Fri Dec 15 20:54:30 MST 2017
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

Connecting to hw_server @ TCP:localhost:3121

Connected to hw_server @ TCP:localhost:3121
Available targets and devices:
Target 0 : jsn-DLC10-0000196a638b01
Device 0: jsn-DLC10-0000196a638b01-4ba00477-0

Retrieving Flash info...

Initialization done, programming the memory
BOOT_MODE REG = 0x00000001
WARNING: [Xicom 50-100] The current boot mode is QSPI.
If flash programming fails, configure device for JTAG boot mode and try again.
f probe 0 0 0
Performing Erase Operation...
Erase Operation successful.
INFO: [Xicom 50-44] Elapsed time = 0 sec.
Performing Program Operation...
0%...30%...60%...90%...100%
Program Operation successful.
INFO: [Xicom 50-44] Elapsed time = 78 sec.
Performing Verify Operation...
0%...INFO: [Xicom 50-44] Elapsed time = 1 sec.
Verify Operation unsuccessful.

ERROR: Flash Operation Failed

0 Kudos
Reply
11 Replies
Teacher
Teacher
972 Views
Registered: ‎07-09-2009

why do yo say vivado fails

whats the vivado messages

<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos
Reply
Visitor
Visitor
962 Views
Registered: ‎09-10-2019

start_gui
open_project /home/Xilinx/Vivado/project_1/project_1.xpr
open_project /home/Xilinx/Vivado/project_1/project_1.xpr
Scanning sources...
Finished scanning sources
INFO: [IP_Flow 19-234] Refreshing IP repositories
INFO: [IP_Flow 19-1704] No user IP repositories specified
INFO: [IP_Flow 19-2313] Loaded Vivado IP repository '/opt/Xilinx/Vivado/2017.4/data/ip'.
open_project: Time (s): cpu = 00:00:18 ; elapsed = 00:00:20 . Memory (MB): peak = 6369.758 ; gain = 341.262 ; free physical = 2504 ; free virtual = 11341
open_hw
update_compile_order -fileset sources_1
connect_hw_server
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
INFO: [Labtools 27-2222] Launching hw_server...
INFO: [Labtools 27-2221] Launch Output:

****** Xilinx hw_server v2017.4
**** Build date : Dec 15 2017-21:02:11
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.


open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Xilinx/0000196a638b01
current_hw_device [get_hw_devices xc7z020_1]
refresh_hw_device -update_hw_probes false [lindex [get_hw_devices xc7z020_1] 0]
INFO: [Labtools 27-1434] Device xc7z020 (JTAG device index = 1) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device. To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
create_hw_cfgmem -hw_device [lindex [get_hw_devices] 1] -mem_dev [lindex [get_cfgmem_parts {s25fl256s-3.3v-qspi-x4-single}] 0]
set_property PROGRAM.ADDRESS_RANGE {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
set_property PROGRAM.FILES [list "/home/Xilinx/proj/images/BOOT.bin" ] [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
set_property PROGRAM.ZYNQ_FSBL {/home/Xilinx/proj/images/fsbl_golden.elf} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
set_property PROGRAM.BLANK_CHECK 0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
set_property PROGRAM.ERASE 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
set_property PROGRAM.CFG_PROGRAM 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
set_property PROGRAM.VERIFY 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
set_property PROGRAM.CHECKSUM 0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
startgroup
program_hw_cfgmem -hw_cfgmem [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
WARNING: [Xicom 50-100] The current boot mode is QSPI.
If flash programming fails, configure device for JTAG boot mode and try again.
f probe 0 0 0
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 = 77 sec.
Performing Verify Operation...
INFO: [Xicom 50-44] Elapsed time = 2 sec.
Verify Operation unsuccessful.
ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
program_hw_cfgmem: Time (s): cpu = 00:00:04 ; elapsed = 00:01:25 . Memory (MB): peak = 6667.121 ; gain = 0.000 ; free physical = 2757 ; free virtual = 11478
ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.

0 Kudos
Reply
Visitor
Visitor
960 Views
Registered: ‎09-10-2019

Vivado Commandsrefresh_hw_device -update_hw_probes false [lindex [get_hw_devices xc7z020_1] 0]
[Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device. To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
program_hw_cfgmem -hw_cfgmem [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices xc7z020_1] 0]]
[Xicom 50-100] The current boot mode is QSPI.
If flash programming fails, configure device for JTAG boot mode and try again.
[Labtools 27-3161] Flash Programming Unsuccessful

0 Kudos
Reply
Visitor
Visitor
889 Views
Registered: ‎09-10-2019

how can I fix this problem?

I can't flash after every reboot.

0 Kudos
Reply
Teacher
Teacher
875 Views
Registered: ‎07-09-2009

WARNING: [Xicom 50-100] The current boot mode is QSPI.
If flash programming fails, configure device for JTAG boot mode and try again.
<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos
Reply
Visitor
Visitor
819 Views
Registered: ‎09-10-2019

when I am tring to flash it from another computer (windows os) it succeed so it's not an hardware problem

0 Kudos
Reply
Teacher
Teacher
814 Views
Registered: ‎07-09-2009

So Im now confused, Are yo usaying you have one compiuter you cna program from

    another that you cant ?

 

 

<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos
Reply
Visitor
Visitor
810 Views
Registered: ‎09-10-2019

I have a laptop (linux os), while tring to flash it's failed on verifing step.

my partner has another pc (windows os).

the device can be flash from the windows pc.

when i am tring to do it (on the same hardware) it fails.

i also try to add the blank check step and it fails on this step:

WARNING: [Xicom 50-100] The current boot mode is QSPI.
If flash programming fails, configure device for JTAG boot mode and try again.
f probe 0 0 0
Performing Erase Operation...
Erase Operation successful.
INFO: [Xicom 50-44] Elapsed time = 0 sec.
Performing Blank Check Operation...
INFO: [Xicom 50-44] Elapsed time = 2 sec.
Blank Check Operation unsuccessful. The part is not blank.
ERROR: [Labtools 27-3161] Flash Programming Unsuccessful

0 Kudos
Reply
Teacher
Teacher
787 Views
Registered: ‎07-09-2009

Ok,

 

Assuming you have used the programer and cables on the tow machines, were down to it looking like the laptop ,

 

Have you programmed any other parts with thses cables/  programmer pod on the laptop ?

 

<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos
Reply
Visitor
Visitor
729 Views
Registered: ‎09-10-2019

yes,

The cables and programmer works on the 2'nd computer.

i didn't tried to program another part with my laptop.

i can debug the program via my laptop (without flashing)

0 Kudos
Reply
Xilinx Employee
Xilinx Employee
708 Views
Registered: ‎10-06-2016

Hi @almog123 ,

Taking into account your synthoms it seems to me that this issue might be driven by a race condition. As @drjohnsmith  mentioned earlier your log file states that you are programming the target in QSPI boot mode and this warning message has a good reason to be there. When a part is configured in any non JTAG boot mode, any power-up or system reset event will generate the BootROM code to run again, so the system gets to a race condition where the program_flash in the host machine is trying to execute code through JTAG while the device might be trying to boot the part. As any race condition, the synthoms might not be persisten or might vary from machine to machine, and the fact that you have two different host machines with different OS's might be a good indicator of that.

I guess that you probably have a fixed boot mode on your hardware but definitively I would suggest to a quick modification (just need to use a wire) to test in JTAG boot mode.

Regards


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