Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
uboot getting hang after "tftpb 0x80000 Image"
#1
Hello,

I am using Xen Zynq Distribution, following user Manual (Xilinx-XenZynq-DOC-0001 v0.7 July 1, 2016). I am seeing a random issue of uboot getting stuck. Previously I was running uboot script "xen" as specified in 4.2.1.6 as "run xen". Later i started running each command from the xen script on uboot console. I found that after image is loaded, the uboot console hangs.

Following are the logs. I am loading u-boot.elf from JTAG. Is there an issue/bug in u-boot.elf. Please advice.

Thanks,
Sunit

Xilinx Zynq MP First Stage Boot Loader

Release 2016.1   Jun 30 2016  -  11:23:07
Platform: Silicon, Board Configuration successful
Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor
Processor Initialization Done
================= In Stage 2 ============
In JTAG Boot Mode
================= In Stage 4 ============
Exit from FSBL
NOTICE:  ATF running on XCZU9EG/silicon v1/RTL5.1 at 0xfffe5000
NOTICE:  BL31: Secure code at 0xfffc0000
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v1.2(release):6397b33
NOTICE:  BL31: Built : 09:33:01, Jun 30 2016


U-Boot 2016.01 (Jun 30 2016 - 11:25:04 -0400) Xilinx ZynqMP ZCU102

I2C:   ready
DRAM:  4 GiB
Enabling Caches...
EL Level:       EL2
MMC:   sdhci@ff170000: 0
Using default environment

In:    serial@ff000000
Out:   serial@ff000000
Err:   serial@ff000000
Bootmode: JTAG_MODE
SCSI:  SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net:   ZYNQ GEM: ff0e0000, phyaddr 12, interface rgmii-id

Warning: ethernet@ff0e0000 (eth0) using random MAC address - f2:a4:42:46:d2:75
eth0: ethernet@ff0e0000
Hit any key to stop autoboot:  0
U-Boot-PetaLinux> setenv serverip 10.9.51.203
U-Boot-PetaLinux> setenv gatewayip 10.9.51.1
U-Boot-PetaLinux> setenv netmask 255.255.255.0
U-Boot-PetaLinux> setenv ipaddr 10.9.51.216
U-Boot-PetaLinux> ping 10.9.51.203
Using ethernet@ff0e0000 device
host 10.9.51.203 is alive
U-Boot-PetaLinux> tftpb $fdt_addr xen.dtb
Using ethernet@ff0e0000 device
TFTP from server 10.9.51.203; our IP address is 10.9.51.216
Filename 'xen.dtb'.
Load address: 0x4000000
Loading: ##
         12.7 MiB/s
done
Bytes transferred = 26662 (6826 hex)
U-Boot-PetaLinux> fdt addr $fdt_addr
U-Boot-PetaLinux> fdt resize
U-Boot-PetaLinux> tftpb 0x80000 Image
Using ethernet@ff0e0000 device
TFTP from server 10.9.51.203; our IP address is 10.9.51.216
Filename 'Image'.
Load address: 0x80000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################
         12.8 MiB/s
done
Bytes transferred = 11202912 (aaf160 hex)

--------UBOOT HANGS AFTER THIS------


Attached Files
.txt   jtag_boot.txt.txt (Size: 2.5 KB / Downloads: 1)
.txt   uboot_log.txt.txt (Size: 2.97 KB / Downloads: 1)
Reply
#2
Sunit,

Thank you for letting us know about this issue. I am assuming from your logs that you are running on development board, as opposed to QEMU. What kind of board are you running on?

Regards,
-Jarvis
Reply
#3
(09-07-2016, 05:07 PM)jarvis_roach Wrote: Sunit,

Thank you for letting us know about this issue. I am assuming from your logs that you are running on development board, as opposed to QEMU. What kind of board are you running on?

Regards,
-Jarvis

Hi Jarvis,

Thanks for quick response, I am using ZCU102 Ref board.

Sunit
Reply
#4
Sunit,

What rev ZCU board? Prior to releasing that version we tested extensively on rev C boards, and I just followed the procedure you indicated on a rev D board and was able to boot into Xen.


-Jarvis
Reply
#5
(09-07-2016, 05:24 PM)jarvis_roach Wrote: Sunit,

What rev ZCU board? Prior to releasing that version we tested extensively on rev C boards, and I just followed the procedure you indicated on a rev D board and was able to boot into Xen.


-Jarvis
Jarvis,

I have a Rev D1 board. It do sometimes boot into Xen, but is not consistent. One attempt out of few (10) results into a proper boot. Two options i have to debug further

a) I do have another D1 board, I can check to see if I can reproduce this issue on another board. May be a board specific issue.
b) JTAG attach to see where it is stuck, but for this option I may need some support either from you or Xilinx to understand what is happening. Is this a Xilinx released uboot or modified Dornerworks uboot?

On a), will get back by end of today.

Thanks,
Sunit
Reply
#6
Sunnit,

It worked the first time on my D1 board, but I'll try it a few more times tomorrow just in case I was lucky.

Our u-boot is mostly pulled from Xilinx's repo, but we have some confg environment differences to define and support that 'xen' command.

-J
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)