Actions
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 328 subscribers
  • Views 153 views
  • Users 0 members are here
Related

Microzed: SW1 Glow RED when power ON fsbl data abort

Former Member

I have created fsbl, u-boot and tried below steps.

Power on the board with USB.

<<< Board SW1 Glow RED >>>
xsdb% connect
tcfchan#0
xsdb% targets
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsdb% targets 2
xsdb% dow /opt/fsbl.elf
xsdb% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0xffffff28 (Suspended)
xsdb% con
Info: ARM Cortex-A9 MPCore #0 (target 2) Running

Saw FSBL logs on console.

<<< this step SW1 turned off >>>

xsdb% stop
xsdb% dow u-boot.elf
xsdb% con

Console log says:
----------------
DATA_ABORT_HANDLER
FSBL_Status = 0xA304

This Boot Mode Doesn't Support Fallback
In FsblHookFallback function

Can anyone help, when I reboot the board it's again SW1 glow RED.

And QSPI, SD bootmodes are not working I can able to use JTAG bootmode.

Can anyone help,
Jagan.

  • 0

    Hello Jagan,

     

    It is difficult to tell exactly what is and is not working based on this post and your other similar post: http://zedboard.org/content/sw1-glow-red-when-i-connect-usb-cable

     

    I think it would be useful to step back and make sure your hardware, both MicroZed board and JTAG cable and connections, are working correctly first. You don't mention if your MicroZed is a 7010 or 7020 version so make sure you select the proper images.

     

    First, please download the solution image for Tutorials 01-04 that match your MicroZed board type: http://zedboard.org/support/design/1519/10

     

    Once you have unzipped the prebuilt project for your MicroZed from the archive please follow the steps in Tutorial 04, starting with Experiment 3, to verify that your hardware setup works with these pretested images for booting from both QSPI and microSD Card. Pay close attention to make sure the MicroZed jumpers are set correctly. If this works that indicates that there is some error in the images you have generated. This could be due to an error in following the tutorial or perhaps a corrupted Xilinx tool image. While it is rare we have seen strange issues that can be traced to a corrupted Vivado download. If you still have the image you downloaded from the Xilinx website it might be useful to check that the MD5 checksum matches the one posted for that image.

     

    Let us know your progress.

     

    -Gary