From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399
Date: Wed, 20 Jan 2021 16:08:33 -0800 [thread overview]
Message-ID: <87o8hj5eym.fsf@yucca> (raw)
It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb
is started. It hangs indefinitely at:
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
I have observed this also using 2020.10 on rockpro64-rk3399, though on
pinebook-pro-rk3399 usb does not work and so it basically avoids
triggering the issue.
Setting CONFIG_USE_PREBOOT=n in the config works around the problem,
though obviously by breaking usb keyboard support or booting from USB
devices.
Related bugs in Debian and manjaro:
https://bugs.debian.org/973323
https://bugs.debian.org/980434
https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-rockpro64/-/issues/4
Boot log:
U-Boot 2021.01+dfsg-1 (Jan 17 2021 - 03:50:13 +0000)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc at fe310000: 2, mmc at fe320000: 1, sdhci at fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 RockPro64 v2.1
Net: eth0: ethernet at fe300000
starting USB...
Bus usb at fe380000: USB EHCI 1.00
Bus usb at fe3a0000: USB OHCI 1.0
Bus usb at fe3c0000: USB EHCI 1.00
Bus usb at fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb at fe380000 for devices... 1 USB Device(s) found
scanning bus usb at fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb at fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb at fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
=> printenv preboot
preboot=usb start
=> usb reset
resetting USB...
Bus usb at fe380000: USB EHCI 1.00
Bus usb at fe3a0000: USB OHCI 1.0
Bus usb at fe3c0000: USB EHCI 1.00
Bus usb at fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb at fe380000 for devices... 1 USB Device(s) found
scanning bus usb at fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb at fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb at fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
=> boot
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
144 bytes read in 5 ms (27.3 KiB/s)
1: Debian-Installer
Retrieving file: /initrd.gz
28995285 bytes read in 1287 ms (21.5 MiB/s)
Retrieving file: /vmlinuz
26922864 bytes read in 1195 ms (21.5 MiB/s)
Retrieving file: /dtbs/rockchip/rk3399-rockpro64.dtb
56849 bytes read in 13 ms (4.2 MiB/s)
Moving Image from 0x2080000 to 0x2200000, end=3c50000
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210120/d5898991/attachment.sig>
next reply other threads:[~2021-01-21 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 0:08 Vagrant Cascadian [this message]
2021-01-21 3:37 ` Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399 Kever Yang
2021-01-21 9:12 ` Alper Nebi Yasak
2021-01-22 1:31 ` Jonathan Gray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8hj5eym.fsf@yucca \
--to=vagrant@debian.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.