Actions
Forum Thread Details
  • State Not Answered
  • Replies 11 replies
  • Subscribers 341 subscribers
  • Views 1053 views
  • Users 0 members are here
Related

Deadlock of Microzed

Former Member

Hello

I work with Vivado 2014.2 and the AES-Z7MB-7Z020-SOM-I-G.

Iu2019m new to the Zynq world and worked through the ZynqSW and ZynqHW tutorials for the Zedboard (we already had Zedboards) as well as the CTT tutorial. Then I wanted to adapt the CTT tutorial to my target hardware, the Microzed (version with a Z7020).

Since it is a lot of new stuff that is discussed, it happened that I corrupted my Microzed somehow. I managed to crash my serial console, the zynq just doesnu2019t send any message (Tx of Zynq is always 1V8) even though Iu2019m able to download some (default) helloworld projects or connect to the zynq via XMD console.
However, I was able to debug the helloworld.c file andu2026 see there. I have the same deadlock as described here:

https://lists.rtems.org/pipermail/users/2015-May/028793.html


My Debug Disassembly exctract is this:
ffffff2c:   dsb     sy
ffffff30:   wfe
ffffff34:   mvn     r0, #15
ffffff38:   ldr     lr, [r0]
ffffff3c:   cmn     lr, #212
ffffff40:   beq     -28     ; addr=0xffffff2c

This exact same disassembly extract appears with any code I try to debug on the microzed now.

Can you tell me if there is a way to overcome this deadlock? Is there a way to download an fsbl and bring the PS up and running again?

I would be very happy for an answer or even a way to reset my system again.

Parents
  • 0

    Hello Nicolas,

     

    Your results do not seem be consistent. It may be that you have a corrupt board definition file. I would suggest that you upgrade to a more recent version of the Xilinx tools, Vivado 2015.x, as the version you are using is a little dated, and download a fresh version of the current board definition files.

     

    You could also take a look at the MicroZed 7020 solutions for the Tutorials 01-04 for Vivado 2015.1 or 2015.2 available here:

    http://microzed.org/support/design/1519/10

     

    or try the pre-built platform in the PetaLinux BSP for 2015.2, or one of the earlier versions.

     

    And, just to make sure it is not the issue, be aware that the SiLabs USB-UART device on each MicroZed has a unique ID and will enumerate with a different Comm port for a given host PC. So the TeraTerm Comm port for your MicroZed 7010 will be different than the one for your MicroZed 7020 on the same host PC.

     

    -Gary

Reply
  • 0

    Hello Nicolas,

     

    Your results do not seem be consistent. It may be that you have a corrupt board definition file. I would suggest that you upgrade to a more recent version of the Xilinx tools, Vivado 2015.x, as the version you are using is a little dated, and download a fresh version of the current board definition files.

     

    You could also take a look at the MicroZed 7020 solutions for the Tutorials 01-04 for Vivado 2015.1 or 2015.2 available here:

    http://microzed.org/support/design/1519/10

     

    or try the pre-built platform in the PetaLinux BSP for 2015.2, or one of the earlier versions.

     

    And, just to make sure it is not the issue, be aware that the SiLabs USB-UART device on each MicroZed has a unique ID and will enumerate with a different Comm port for a given host PC. So the TeraTerm Comm port for your MicroZed 7010 will be different than the one for your MicroZed 7020 on the same host PC.

     

    -Gary

Children
No Data