Actions
Forum Thread Details
  • State Not Answered
  • Replies 8 replies
  • Subscribers 366 subscribers
  • Views 802 views
  • Users 0 members are here
Related

MicroZed Boot Problem

Former Member

Hello All,

I have been running my MicroZed (BD-Z7MB-7Z010-G REVF06) with a Breakout Carrier Card for several months now with no issues.  Recently, however, when I booted up in SD Card mode (as per usual, I have Ubuntu loaded on there) the board & card powered up but I was unable to connect to the serial port using my terminal program.  I then tried booting up in QSPI mode and JTAG mode (which seemed to work fine, although oddly the blue "ready" light was on immediately) but I was not able to connect to either the serial port or the JTAG cable.

To isolate the problem I separated the MicroZed from the Breakout Carrier Card, and tried booting it up as a standalone device.  The MicroZed would not boot up at all when powered only by the USB cable.  I tried switching USB cables and using different USB ports, but none of the LEDs would light up.

Any troubleshooting ideas out there?

Thanks.

Adam

Parents
  • 0

    Hello Adam,

     

    Sounds like there are a couple of things to address, so perhaps we can work on them one at a time. 

     

    It is very possible to create a Zynq design that will require more power than the typical USB port will provide. If you can try an actively powered USB hub, or some other USB port that you are sure will provide enough current. Otherwise you might try connecting the USB power supply from your Break Out Carrier Card directly to the MicroZed. While this will not provide the USB UART terminal it should provide enough current so that you can see if the MicroZed will boot. If the LEDs do light as expected this would indicate the 'standalone' booting issue might be power related.

     

    Next, you could try enabling the built in terminal in the SDK, using JTAG mode, to see if the board is otherwise operating correctly. The first exercises in the Avnet Zynq Software Speedway workshop labs detail how to enable the SDK terminal.

    http://zedboard.org/course/developing-zynq%C2%AE-7000-all-programmable-soc-software-vivado-20133-and-201441

     

    Let us know if you are able to make any progress and we can proceed from there.

     

    -Gary

  • 0 in reply to Former Member

    Gary,
    Thanks for your prompt and on-point suggestions.  Here are the results:
    With the standalone MicroZed plugged into the USB power supply from the Breakout Carrier Card there is still no visible boot activity, and no LEDs light up.
    With the MicroZed reconnected to the Breakout Carrier Card I ran through the workshop labs you suggested.  I booted up into JTAG mode (all jumpers towards the center of board) it powered up, immediately giving me both the green "Power Good" LED and the blue "DONE" LED.  Clicking Program FPGA produces the following error:

    Connection to Board Failed
    Unknown Error Occurred
    Cable is not powered-on

    I get the exact same error when I try to run the Hello_Zynq application with a JTAG UART STDIO Connection.  And just for giggles, I get the exact same error if I open a XMD console and try "connect arm hw".
    Any other suggestions?  I've got a sinking feeling about this issue...
    Thanks.
    Adam

Reply
  • 0 in reply to Former Member

    Gary,
    Thanks for your prompt and on-point suggestions.  Here are the results:
    With the standalone MicroZed plugged into the USB power supply from the Breakout Carrier Card there is still no visible boot activity, and no LEDs light up.
    With the MicroZed reconnected to the Breakout Carrier Card I ran through the workshop labs you suggested.  I booted up into JTAG mode (all jumpers towards the center of board) it powered up, immediately giving me both the green "Power Good" LED and the blue "DONE" LED.  Clicking Program FPGA produces the following error:

    Connection to Board Failed
    Unknown Error Occurred
    Cable is not powered-on

    I get the exact same error when I try to run the Hello_Zynq application with a JTAG UART STDIO Connection.  And just for giggles, I get the exact same error if I open a XMD console and try "connect arm hw".
    Any other suggestions?  I've got a sinking feeling about this issue...
    Thanks.
    Adam

Children
No Data