I have seen this strange behavior with my zedboard, when I connect usb as power cable SW1 glows RED and D5-R41 Blue. This behavior is irrespective of boot_mode jumper settings JP1-JP3, I'm unable to boot the board.
Can anyone help?
I have seen this strange behavior with my zedboard, when I connect usb as power cable SW1 glows RED and D5-R41 Blue. This behavior is irrespective of boot_mode jumper settings JP1-JP3, I'm unable to boot the board.
Can anyone help?
SW1 is a push-button, so it should not be glowing. If it is, you have a much more serious problem.
I suspect you meant D3 on MicroZed which is above SW1. This is an LED under user control. When in JTAG mode or if the board is unconfigured, it is expected that this LED will glow red.
D5 is a green LED that lights when power is good. It is expected that this should light under all normal conditions.
If you are having trouble configuring the board, try the following:
Bryan
Thanks Bryan.
Can you point the bitstream and MicroZed Reference Design page links, I have 7010 microzed board.
Jagan.
Hello Jagan,
Here is the link to the MicroZed Reference Design page: http://zedboard.org/support/design/1519/10
The 7010 versions are clearly marked.
-Gary
Thanks Gary for the info.
I have done the relevant steps and created bitstream.
Shall I use Xilinx Platform Cable USB II for microzed jtag? http://www.xilinx.com/products/boards-and-kits/hw-usb-ii-g.html
I couldn't see the status LED glow even after I install the cable drivers?
Installing cable drivers.
Script name = ./install_drivers
HostName = Jubuntu
Current working dir = /opt/install_drivers
Kernel version = 4.0.1-040001-generic.
Arch = x86_64.
Installer version = 2015
USB udev file exists and will not be updated.
--File /etc/udev/rules.d/52-xilinx-pcusb.rules exists.
--File /etc/udev/rules.d/52-xilinx-pcusb.rules version = 0002
--File 52-xilinx-pcusb.rules exists.
--File 52-xilinx-pcusb.rules version = 0002
--File 52-xilinx-pcusb.rules is already updated.
Digilent Return code = 0
Xilinx Return code = 0
Return code = 0
Driver installation successful.
Any help?
The Platform Cable USB from Xilinx is supported with MicroZed. Are you using a supported operating system? If you are having trouble with the Xilinx tools and cable, you should contact Xilinx support.
Bryan
Finally I was able connect platform cable.
I downloaded fsbl and u-boot but nothing comes up on uart can you see below setps.
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 4
xsdb% fpga -f /opt/sys.bit
100% 1MB 0.4MB/s 00:05
xsdb% targets
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4* xc7z010
xsdb% targets 2
xsdb% targets
1 APU
2* ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsdb% dow /opt/fsbl.elf
Downloading Program -- /opt/fsbl.elf
tsection, .text: 0x00000000 - 0x0000f76f
tsection, .handoff: 0x0000f770 - 0x0000f7bb
tsection, .init: 0x0000f7bc - 0x0000f7d3
tsection, .fini: 0x0000f7d4 - 0x0000f7eb
tsection, .rodata: 0x0000f7ec - 0x00010ae3
tsection, .data: 0x00010ae8 - 0x00013987
tsection, .eh_frame: 0x00013988 - 0x0001398b
tsection, .mmu_tbl: 0x00014000 - 0x00017fff
tsection, .init_array: 0x00018000 - 0x00018007
tsection, .fini_array: 0x00018008 - 0x0001800b
tsection, .rsa_ac: 0x0001800c - 0x0001903f
tsection, .bss: 0x00019040 - 0x0001ae4b
tsection, .heap: 0x0001ae4c - 0x0001ce4f
tsection, .stack: 0xffff0000 - 0xffffd3ff
100% 0MB 0.1MB/s 00:01
Setting PC to Program Start Address 0x00000000
Successfully downloaded /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
xsdb% stop
xsdb% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0xf790 (Suspended)
xsdb% dow /opt/u-boot
Downloading Program -- /opt/u-boot
tsection, .text: 0x04000000 - 0x0403b573
tsection, .rodata: 0x0403b574 - 0x040499d2
tsection, .hash: 0x040499d4 - 0x040499ff
tsection, .dtb.init.rodata: 0x04049a00 - 0x0404ba0f
tsection, .data: 0x0404ba10 - 0x0404de63
tsection, .got.plt: 0x0404de64 - 0x0404de6f
tsection, .u_boot_list: 0x0404de70 - 0x0404ea2b
tsection, .rel.dyn: 0x0404ea2c - 0x04056dab
tsection, .bss_start: 0x0404ea2c - 0x0404ea2b
tsection, .bss: 0x0404ea2c - 0x0408ead7
tsection, .bss_end: 0x0408ead8 - 0x0408ead7
100% 0MB 0.1MB/s 00:05
Setting PC to Program Start Address 0x04000000
Successfully downloaded /opt/u-boot
xsdb% con
Info: ARM Cortex-A9 MPCore #0 (target 2) Running
Was the steps executed fine? let me know if I missed anything?
Hi Bryan, finally I was able to connect the platform cable and still some issue like I'm unable to get the uart messages please see below steps and let me know if I missed anything.
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 4
xsdb% fpga -f /opt/sys.bit
100% 1MB 0.4MB/s 00:05
xsdb% targets
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4* xc7z010
xsdb% targets 2
xsdb% targets
1 APU
2* ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsdb% dow /opt/fsbl.elf
Downloading Program -- /opt/fsbl.elf
tsection, .text: 0x00000000 - 0x0000f76f
tsection, .handoff: 0x0000f770 - 0x0000f7bb
tsection, .init: 0x0000f7bc - 0x0000f7d3
tsection, .fini: 0x0000f7d4 - 0x0000f7eb
tsection, .rodata: 0x0000f7ec - 0x00010ae3
tsection, .data: 0x00010ae8 - 0x00013987
tsection, .eh_frame: 0x00013988 - 0x0001398b
tsection, .mmu_tbl: 0x00014000 - 0x00017fff
tsection, .init_array: 0x00018000 - 0x00018007
tsection, .fini_array: 0x00018008 - 0x0001800b
tsection, .rsa_ac: 0x0001800c - 0x0001903f
tsection, .bss: 0x00019040 - 0x0001ae4b
tsection, .heap: 0x0001ae4c - 0x0001ce4f
tsection, .stack: 0xffff0000 - 0xffffd3ff
100% 0MB 0.1MB/s 00:01
Setting PC to Program Start Address 0x00000000
Successfully downloaded /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
xsdb% stop
xsdb% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0xf790 (Suspended)
xsdb% dow /opt/u-boot
Downloading Program -- /opt/u-boot
tsection, .text: 0x04000000 - 0x0403b573
tsection, .rodata: 0x0403b574 - 0x040499d2
tsection, .hash: 0x040499d4 - 0x040499ff
tsection, .dtb.init.rodata: 0x04049a00 - 0x0404ba0f
tsection, .data: 0x0404ba10 - 0x0404de63
tsection, .got.plt: 0x0404de64 - 0x0404de6f
tsection, .u_boot_list: 0x0404de70 - 0x0404ea2b
tsection, .rel.dyn: 0x0404ea2c - 0x04056dab
tsection, .bss_start: 0x0404ea2c - 0x0404ea2b
tsection, .bss: 0x0404ea2c - 0x0408ead7
tsection, .bss_end: 0x0408ead8 - 0x0408ead7
100% 0MB 0.1MB/s 00:05
Setting PC to Program Start Address 0x04000000
Successfully downloaded /opt/u-boot
xsdb% con
Info: ARM Cortex-A9 MPCore #0 (target 2) Running
thanks.
Jagan.
Now the Xilinx Platform cables's working fine.
I have created fsbl, u-boot and tried below steps.
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
<<< this step SW1 turned off >>>
xsdb% stop
xsdb% dow u-boot.elf
xsdb% con
I saw log on console
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 still glow RED.
Have you tried following any of the tutorials rather than the low-level XMD commands?
Bryan
Fsbl I have created on the tutorial it self