Author Topic: TE0808 SK_demo1 Boot Error  (Read 7595 times)

urock

  • Active Member
  • *
  • Posts: 4
TE0808 SK_demo1 Boot Error
« on: December 05, 2017, 11:15:20 AM »
Hello,
I have purchased
TE0808-04-09EG-1EB
TEBF0808-04

and I want to run TE0808 StarterKit Demo Design with Debian_8.4 64Bit Example.
https://shop.trenz-electronic.de/en/TE0808-04-09EG-1ED-UltraSOM-MPSoC-Modul-with-Zynq-UltraScale-XCZU9EG-1FFVC900E-4-GByte-DDR4-LP?path=Trenz_Electronic/TE0808/Reference_Design/2017.1/SK_Demo1

I am doing the following
1. Downloaded http://www.trenz-electronic.de/fileadmin/docs/Trenz_Electronic/TE0808/Reference_Design/2017.1/SK_Demo1/te0808-SK_demo1-vivado_2017.1-build_04_20170824174614.zip and took SK_demo1_prebuilt/prebuilt/os/debian/te0808-debian.img file (md5sum = 068d191dd2bb2506fbc61c1592510a21)
2. Burned mentioned file to micro SD card using Win32DiskImager (also tried dd linux command)
3. Took SK_demo1_prebuilt/prebuilt/os/petalinux/default/image.ub and SK_demo1_prebuilt/prebuilt/boot_images/te0808_eg_1eb_tebf0808/u-boot/BOOT.bin and copied them to SD card FAT partition
4. Inserted micro SD card in TEBF0808, power up, reset, saw output in serial console.
5. Boot process hangs on discovering usb devices (see attached error_log.txt of console output)

Code: [Select]
--------------------------------------------------------------------------------
[    6.643769] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    6.787980] usb 1-1: New USB device found, idVendor=04b4, idProduct=650a
[    6.794744] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    6.832560] hub 1-1:1.0: USB hub found
[    6.836349] hub 1-1:1.0: 4 ports detected
[    6.907793] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[    6.932016] usb 2-1: New USB device found, idVendor=04b4, idProduct=6508
[    6.938781] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    6.961844] hub 2-1:1.0: USB hub found
[    6.965638] hub 2-1:1.0: 4 ports detected
[    7.151769] usb 1-1.3: new low-speed USB device number 3 using xhci-hcd
[    7.260858] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c31c
[    7.267799] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    7.275176] usb 1-1.3: Product: USB Keyboard
[    7.279450] usb 1-1.3: Manufacturer: Logitech
[    7.322445] input: Logitech USB Keyboard as /devices/platform/amba/ff9d0000.usb0/fe200000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.3/1-1.3:1.0/0003:046D:C31C.0001/input/input0
[    7.400161] hid-generic 0003:046D:C31C.0001: input: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-xhci-hcd.0.auto-1.3/input0
[    7.424645] input: Logitech USB Keyboard as /devices/platform/amba/ff9d0000.usb0/fe200000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.3/1-1.3:1.1/0003:046D:C31C.0002/input/input1
[    7.503866] hid-generic 0003:046D:C31C.0002: input: USB HID v1.10 Device [Logitech USB Keyboard] on usb-xhci-hcd.0.auto-1.3/input1
[  122.577861] random: crng init done


I have tried two SD cards: SanDisk Exteme 32 GB and Sony 8 GB. I have tried to use both slots on TEBF0808 - J27 and J16.

Two questions:
1. What I am doing wrong? 
2. Why I see in console output 2 GB RAM instead of 4 GB? (error_log.txt line 18)

Code: [Select]
TE0808 Board Initialisation
Si534x Init Function
Si534x Init Complete
PCIe Reset Complete
NOTICE:  ATF running on XCZU9EG/silicon v4/RTL5.1 at 0xfffea000, with PMU firmware
NOTICE:  BL31: Secure code at 0x0
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v1.3(release):7d1a673
NOTICE:  BL31: Built : 14:37:19, Jul 25 2017
U-Boot 2017.01 (Jul 25 2017 - 16:38:40 +0200) Xilinx ZynqMP ZCU102 revB

I2C:   Error, wrong i2c adapter 0 max 0 possible
Error, wrong i2c adapter 0 max 0 possible
ready
DRAM:  2 GiB

Full console output
https://drive.google.com/file/d/1XgW96AcKgKTP_mTV2JtgGjw6PsjPTvOk/view?usp=sharing

Hope to hear from you soon.
Thanks

Yury

urock

  • Active Member
  • *
  • Posts: 4
Re: TE0808 SK_demo1 Boot Error
« Reply #1 on: December 05, 2017, 11:45:01 AM »
Upd: I have also tried booting without any usb devices connected. Still hangs on the following:

Code: [Select]
[    6.875718] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[    6.899946] usb 2-1: New USB device found, idVendor=04b4, idProduct=6508
[    6.906709] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    6.922237] hub 2-1:1.0: USB hub found
[    6.926017] hub 2-1:1.0: 4 ports detected
[    7.019697] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    7.163894] usb 1-1: New USB device found, idVendor=04b4, idProduct=650a
[    7.170657] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    7.196971] hub 1-1:1.0: USB hub found
[    7.200766] hub 1-1:1.0: 4 ports detected

JH

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1988
Re: TE0808 SK_demo1 Boot Error
« Reply #2 on: December 05, 2017, 02:52:53 PM »
Hi,

do you have this problem only with this debian demo or also with other reference design?
Can you try this:
put only image.ub and Boot.bin to SD.

When did you buy the board?
Can you update CPLD Firmware, if you older Firmware:
USB should also work on older Firmware, but maybe try out this.

Do you run TEF0808+TE0808 standalone or on Starterkit enclosure? If alone, can you check your external 12V power supply. I there a current limit?

It's also possible that you have no problem with USB, this was only the last output on console. Maybe something else is crash in this time.

To your memory question: 2GB instead of 4GB, this was a bug from HDF update of the petalinux project on 2017.1. Petalinux did not change memmory size with 2017.1, normally he shoud read this from HDF. We recognized this later. We are currently updating our design to 17.2. We will fix this issue there.

br
John

urock

  • Active Member
  • *
  • Posts: 4
Re: TE0808 SK_demo1 Boot Error
« Reply #3 on: December 06, 2017, 10:42:25 AM »
Hi John,

1. I have tried Referense design Starterkit on my SanDisk microSD and it worked - I was able to boot into console

Code: [Select]
starting Busybox HTTP Daemon: httpd... done.
Starting syslogd/klogd: done
Starting tcf-agent: OK
INIT: Id "hvc0" respawning too fast: disabled for 5 minutes

PetaLinux 2017.1 plnx_aarch64 /dev/ttyPS0

plnx_aarch64 login:

2. I have placed the order on board on the 10th of October

3. I am using TEF0808+TE0808 standalone with Trenz approved 12V power supply (actually boght also from Trenz, PARTNUM = 25200)

Also I have tried yet another microSD card (from Samsung) on SK_Demo1 and it also worked! I was able to tog into console via UART, also tried ssh, keyboard and mouse also worked (I have started x server).

So on my side the problem was in microSD, but I want to notice that it was one from three cards that were bought recently. Also I have SanDisk card that works with your Starterkit design, but not with SK_Demo1. I think there might be a bug in your (or Xilinx) U-BOOT or kernel code that shows up on certain SD cards.

What cards do you use while testing? Do you still suggest me to update CPLD firmware?

JH

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1988
Re: TE0808 SK_demo1 Boot Error
« Reply #4 on: December 06, 2017, 11:04:17 AM »
Hi,

we detect problems with faster SDs and SDs which support SD3.0.
Add following to the device tree and try again:
Code: [Select]
&sdhci1 {   
no-1-8-v;
};

This should help. But normally Linux output is SD Error, so I hadn't considered it. We will add this entry to the newer reference designs.

Update is not necessary, but there are better features, like improved LED Status outputs and power management (this will be better for FMC usage), PJTAG on addition JTAG heater... see:

br
John

urock

  • Active Member
  • *
  • Posts: 4
Re: TE0808 SK_demo1 Boot Error
« Reply #5 on: December 06, 2017, 12:06:56 PM »
Ok, I'll try to modify device tree

For your reference attached are sd cards that did not work with current SK_Demo1 design.

Thanks

JH

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1988
Re: TE0808 SK_demo1 Boot Error
« Reply #6 on: December 06, 2017, 12:13:13 PM »
Hi,

yes HC I was one of the non working types without this device tree entry. I think this should work after device tree modification.
Some notes to the different types:
https://kb-de.sandisk.com/app/answers/detail/a_id/8317/~/sd%2Fsdhc%2Fsdxc-spezifikationen-und-kompatibilit%C3%A4ten

br
John