From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Tom Rini <trini@konsulko.com>, Aleksei <alex3kov@zoho.com>
Cc: u-boot@lists.denx.de, Jagan Teki <jagan@amarulasolutions.com>,
Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [BUG] RockPro64 not booting since 3ae64582fb
Date: Sat, 13 Nov 2021 00:42:49 +0300 [thread overview]
Message-ID: <f1be2d58-e337-424b-d50e-ebb80077a64b@gmail.com> (raw)
In-Reply-To: <20211112163959.GZ24579@bill-the-cat>
On 12/11/2021 19:39, Tom Rini wrote:
> On Fri, Nov 12, 2021 at 11:35:15AM +0300, Aleksei wrote:
>
>> Hi U-boot developers,
>> I'm booting RockPro64 by writing compiled u-boot-rockchip.bin to SD card offset
>> 64 as described in doc/board/rockchip/rockchip.rst. There is a USB flash drive
>> plugged into USB2 port containing ext4 filesystem with extlinux/exlinux.conf
>> and a kernel+initrd images. This setup boots fine on 02ce99ec91 but not on the
>> next 3ae64582fb. It gets stuck on "Booting using the fdt blob at 0x1f000000".
>>
>> Let me know if I can help debug this. I have a "daily driver" RockPro64 v2.1,
>> can pull from git repos/branches or apply patches to source tree - whichever
>> you prefer.
>
> So the commit in question is enabling USB3.0 support on the board.
> Jagan, Kevar?
This is probably the same inno-usb2 hang [1] that happens on other
RK3399 boards.
[1]
https://patchwork.ozlabs.org/project/uboot/patch/20210406151059.1187379-1-icenowy@aosc.io/
next prev parent reply other threads:[~2021-11-12 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 8:35 [BUG] RockPro64 not booting since 3ae64582fb Aleksei
2021-11-12 16:39 ` Tom Rini
2021-11-12 21:42 ` Alper Nebi Yasak [this message]
2021-11-13 10:41 ` Peter Robinson
2021-11-13 15:09 ` Tom Rini
2022-06-05 9:14 ` Aleksei
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=f1be2d58-e337-424b-d50e-ebb80077a64b@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=alex3kov@zoho.com \
--cc=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=trini@konsulko.com \
--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.