cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
926 Views
Registered: ‎06-21-2017

Programming Flash Hangs

I am trying to program a boot flash for an Ultrascale Zynq using SDK and Vivado 2019.1.  Using SDK and verifying the programming, everything goes well until the very end.  What I think is the last block hangs on verification.

Capture.PNG

I have seen the verification complete successfully before.  Any thoughts?

0 Kudos
14 Replies
Highlighted
Xilinx Employee
Xilinx Employee
896 Views
Registered: ‎10-12-2018

Hi @bruce_karaffa ,

Can you please provide full log of flash programming?

To get more prints for debug purpose, please enable Debug Environmental Variable XIL_CSE_ZYNQ_DISPLAY_UBOOT_MESSAGES can be set to 1. Please check 5) point for more details in https://www.xilinx.com/support/answers/68656.html

 

Thanks & Regards
Anil B
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Highlighted
875 Views
Registered: ‎06-21-2017

What log is that?  The SDK log produced while I was programming shows no reference to the flash operation.  It is attached (with project names obfuscated).  If there is another log associated with flash programming, I can't find it.  The terminal shows this:

Xilinx Zynq MP First Stage Boot Loader
Release 2019.1 Jan 30 2020 - 14:34:16
PMU-FW is not running, certain applications may not be supported.

That's it.  I did change the environment variable and rebooted before trying.  I see no difference.

 

0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
836 Views
Registered: ‎10-12-2018

Hi @bruce_karaffa ,

The log which you can see in XSDK Console while flash programming as below screen shot for your reference. You have already provided in initial reply but expecting full log.

SDK_flash_log.PNG

 

Thanks & Regards
Anil B
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Highlighted
801 Views
Registered: ‎06-21-2017

@abommera Since this log doesn't seem to be saved anywhere, I had to run it again.  The log is attached.  It still hangs on the last verification.

0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
795 Views
Registered: ‎10-12-2018

Hi @bruce_karaffa ,

Thank you for sharing full log!! 

By looking into your log, you are using QSPI boot mode while flash programming but we recommend to use JTAG boot mode.

Can you please change to JTAG boot mode when you are programming flash and try?

Thanks & Regards
Anil B
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Highlighted
781 Views
Registered: ‎06-21-2017

Boot mode changed to JTAG.  Still hangs on last verify. 

0 Kudos
Highlighted
Explorer
Explorer
576 Views
Registered: ‎04-26-2017

Did you find the solution?

I am facing the same problem here... with the SDK 2019.1. The FPGA is a Zynq UltraScale+.

 

Screenshot from 2020-06-11 14-59-57.png

 

Thanks and best regards,

baldrism

 

0 Kudos
Highlighted
570 Views
Registered: ‎06-21-2017

If we found the solution, I don't remember it.  We have a FSBL in the flash now and use it to load the rest of the code and bit stream.  I don't have the board on my desk anymore, so I can't even try to check.

0 Kudos
Highlighted
Newbie
Newbie
399 Views
Registered: ‎10-30-2018

Did you end up finding a solution? I am also having the same problem.

0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
237 Views
Registered: ‎10-12-2018

Hi @bruce_karaffa ,

>> Seems, you are trying with .mcs file for flash programming.

>> Can you please try with .bin file rather than .mcs file and see if it works?

>> I have verified this in sdk 2019.1 and could not see any issue. Please see the attached log. 

 

Thanks & Regards
Anil B
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Highlighted
234 Views
Registered: ‎06-21-2017

@abommera As mentioned in a previous post, I no longer have the board on my desk.  We are loading using the FSBL now, not through JTAG, so I can't test with the bin file. 

0 Kudos
Highlighted
Newbie
Newbie
168 Views
Registered: ‎10-30-2018

Hi @abommera ,

 

I'm having the same problem Bruce is, and I still haven't been able to get it resolved. I am using Vivado Lab 2019.1, programming a Zynq Ultrascale, with the boot mode set to JTAG boot, and the verify operation occasionally hangs verifying the last block. I see this issue maybe about 50% of the time I program, the other half it works as expected. I have a log file attached, which is from running Vivado Lab from the command line with a .tcl script input, if it matters, but I do get the same error when using the Vivado UI. 

0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
149 Views
Registered: ‎10-12-2018

Hi @amcguan_vs ,

Since you are using Zynq UltraScale for QSPI flash programming, we do recommend to use XSDK for flash programming rather than the Vivado. You can use vivado for flash programming in case of non-zynq (non-SoC) devices.

Hence can you please try with XSDK for QSPI flash programming?

Please refer to ug1209(v2019.1), page no.79 for the boot sequence for QSPI boot mode.

https://www.xilinx.com/support/documentation/sw_manuals/xilinx2019_1/ug1209-embedded-design-tutorial.pdf

Thanks & Regards
Anil B
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Highlighted
Newbie
Newbie
112 Views
Registered: ‎10-30-2018

@abommera 

 

I have used the XSDK for programming, with no issues. I'm trying to keep the installation size to a minimum which is why I chose Vivado Lab for this purpose. Is this a known issue with Vivado?

0 Kudos