Actions
Forum Thread Details
  • State Not Answered
  • Replies 11 replies
  • Subscribers 274 subscribers
  • Views 535 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 Gary

    I upgraded to Vivado2015.2 and followed the tutorial 01-02 of the MicroZed 7020 for Vivado 2015.1 or 2015.2.
    I can program the FPGA successfully but when I try to download the HelloZed project an error window appears with the message details:
    An internal error occurred during: "Launching HelloZed Debug".
    No Target with ID 64 in the System

    The two MicroZed have UART ID 13 and 14. Of course I can only choose the one that is pluged in on host PC when I configure my terminal.

    I also tried to boot from the pre-built platform on sd card with the files from "microzed_7010_7020_petalinux_SD_images" without success (means no serial output).

    Does this give a more consistant picture of the failure behaviour?
    All I can say is that I had no issue with the ZynqHW and ZynqSW tutorials as well as the CTT tutorial on Zedboard. Since I work with the MZ 7020 I wasn't able to set up an own hardware with a running helloworld program on it. In contrast I was able to set up an own hardware and run the helloworld successfully with the MZ 7010. This leads me to the assumption that my MZ 7020 is corrupt. Or do you disagree?

    If you agree please send me an RMA for my MZ 7020. The fault finding is quite cost intensive on our side.

    Kind regards
    Nicolas

Reply
  • 0

    Hello Gary

    I upgraded to Vivado2015.2 and followed the tutorial 01-02 of the MicroZed 7020 for Vivado 2015.1 or 2015.2.
    I can program the FPGA successfully but when I try to download the HelloZed project an error window appears with the message details:
    An internal error occurred during: "Launching HelloZed Debug".
    No Target with ID 64 in the System

    The two MicroZed have UART ID 13 and 14. Of course I can only choose the one that is pluged in on host PC when I configure my terminal.

    I also tried to boot from the pre-built platform on sd card with the files from "microzed_7010_7020_petalinux_SD_images" without success (means no serial output).

    Does this give a more consistant picture of the failure behaviour?
    All I can say is that I had no issue with the ZynqHW and ZynqSW tutorials as well as the CTT tutorial on Zedboard. Since I work with the MZ 7020 I wasn't able to set up an own hardware with a running helloworld program on it. In contrast I was able to set up an own hardware and run the helloworld successfully with the MZ 7010. This leads me to the assumption that my MZ 7020 is corrupt. Or do you disagree?

    If you agree please send me an RMA for my MZ 7020. The fault finding is quite cost intensive on our side.

    Kind regards
    Nicolas

Children