BeagleBone Green Wireless - serial debug port hangs after sending u-boot-spl.bin (since v2021.01)

BeagleBone Green Wireless - serial debug port hangs after sending u-boot-spl.bin (since v2021.01)

[Darren Ng]

(Hello, from a U-Boot NOOB.)

Issue
-----
After sending u-boot-spl.bin with xmodem, the serial debug port seems to
hang.
Neither "...U-Boot SPL...\n...\nTrying to boot from UART..."
nor "CCC..." shows up in minicom.
Always 0% if I try sending u-boot.img with xmodem anyway.

Target Device
-------------
Seeed Studio BeagleBone? Green Wireless
https://seeeddoc.github.io/Beaglebone_green_wireless/
https://wiki.seeedstudio.com/BeagleBone_Green_Wireless/#hardware-overview
https://source.denx.de/u-boot/u-boot/-/commits/master/configs/am335x_boneblack_vboot_defconfig

Matrix
------
This issue applies to tags ever since v2021.01. In the following table:
(x) - This issue applies.
(O) - I can send both u-boot-spl.bin and u-boot.img
      then execute u-boot commands without trouble.
------
tag          result
------------ ------------------
v2021.07-rc1 (x) hangs
v2021.04     (x) hangs
v2021.01     (x) hangs
v2020.10     (O) success
v2020.07     (?) not tested yet
v2020.04     (?) not tested yet
v2020.01     (O) success


Toolchain
---------
"Official toolchain for Arch ARM builds via distcc on x86_64 volunteers"
https://aur.archlinux.org/packages/distccd-alarm-armv7h
https://archlinuxarm.org/wiki/Distcc_Cross-Compiling
---------
$ gcc --version
gcc (GCC) 10.2.0
Copyright...
---------
$ cd /opt/x-tools7h/arm-unknown-linux-gnueabihf/bin/
$ ./armv7l-unknown-linux-gnueabihf-gcc --version
armv7l-unknown-linux-gnueabihf-gcc (crosstool-NG 1.23.0.418-d590) 10.2.0
Copyright...


Build
-----
tar xf ...
cd u-boot-*/
export PATH="$PATH:/opt/x-tools7h/arm-unknown-linux-gnueabihf/bin/"
export CROSS_COMPILE="armv7l-unknown-linux-gnueabihf-"
export KBUILD_OUTPUT="O"
make -j4 am335x_boneblack_vboot_defconfig
make -j4 all


Regards,
Darren "Un1Gfn" Ng
Jumat, 7 Mei 2021 WITA(UTC+8)

BeagleBone Green Wireless - serial debug port hangs after sending u-boot-spl.bin (since v2021.01)

[Tom Rini]

On Sat, May 08, 2021 at 12:02:21AM +0800, Darren Ng wrote:

> (Hello, from a U-Boot NOOB.)
> 
> Issue
> -----
> After sending u-boot-spl.bin with xmodem, the serial debug port seems to
> hang.
> Neither "...U-Boot SPL...\n...\nTrying to boot from UART..."
> nor "CCC..." shows up in minicom.
> Always 0% if I try sending u-boot.img with xmodem anyway.
> 
> Target Device
> -------------
> Seeed Studio BeagleBone? Green Wireless
> https://seeeddoc.github.io/Beaglebone_green_wireless/
> https://wiki.seeedstudio.com/BeagleBone_Green_Wireless/#hardware-overview
> https://source.denx.de/u-boot/u-boot/-/commits/master/configs/am335x_boneblack_vboot_defconfig
> 
> Matrix
> ------
> This issue applies to tags ever since v2021.01. In the following table:
> (x) - This issue applies.
> (O) - I can send both u-boot-spl.bin and u-boot.img
>       then execute u-boot commands without trouble.
> ------
> tag          result
> ------------ ------------------
> v2021.07-rc1 (x) hangs
> v2021.04     (x) hangs
> v2021.01     (x) hangs
> v2020.10     (O) success

It looks like something broke between v2020.10 and v2021.01 then.  Since
you have a testcase, using "git bisect" should help figure out which
exact commit broke things.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210507/6ab1d386/attachment.sig>

BeagleBone Green Wireless - serial debug port hangs after sending u-boot-spl.bin (since v2021.01)

[Darren Ng]

On Sat, May 8, 2021 at 1:40 AM Tom Rini <trini@konsulko.com> wrote:

> On Sat, May 08, 2021 at 12:02:21AM +0800, Darren Ng wrote:
>
> > (Hello, from a U-Boot NOOB.)
> >
> > Issue
> > -----
> > After sending u-boot-spl.bin with xmodem, the serial debug port seems to
> > hang.
> > Neither "...U-Boot SPL...\n...\nTrying to boot from UART..."
> > nor "CCC..." shows up in minicom.
> > Always 0% if I try sending u-boot.img with xmodem anyway.
> >
> > Target Device
> > -------------
> > Seeed Studio BeagleBone? Green Wireless
> > https://seeeddoc.github.io/Beaglebone_green_wireless/
> >
> https://wiki.seeedstudio.com/BeagleBone_Green_Wireless/#hardware-overview
> >
> https://source.denx.de/u-boot/u-boot/-/commits/master/configs/am335x_boneblack_vboot_defconfig
> >
> > Matrix
> > ------
> > This issue applies to tags ever since v2021.01. In the following table:
> > (x) - This issue applies.
> > (O) - I can send both u-boot-spl.bin and u-boot.img
> >       then execute u-boot commands without trouble.
> > ------
> > tag          result
> > ------------ ------------------
> > v2021.07-rc1 (x) hangs
> > v2021.04     (x) hangs
> > v2021.01     (x) hangs
> > v2020.10     (O) success
>
> It looks like something broke between v2020.10 and v2021.01 then.  Since
> you have a testcase, using "git bisect" should help figure out which
> exact commit broke things.
>
> --
> Tom
>

("reply all" instead of "reply")

v2021.04 running successfully with am335x_evm_defconfig(AED) now

> commit 8fa7f65dd02c176ee6021eaf40114560b8954ba2
> Author: Faiz Abbas <faiz_abbas@ti.com>
> Date:   Thu Jan 17 15:44:06 2019 +0530
>
>     configs: Remove am335x_boneblack_defconfig
>
>     The am335x_evm_defconfig supports all am335x_boneblack variants.
Remove
>     the redundant am335x_boneblack_defconfig.
>
>     Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
>     Reviewed-by: Tom Rini <trini@konsulko.com>
>
> D       configs/am335x_boneblack_defconfig

According to the commit log above, a previous
am335x_boneblack_defconfig(ABD)
is removed in favor of am335x_evm_defconfig(AED)

However there is a am335x_boneblack_vboot_defconfig(ABVD) in the tree,
which is what I have failed with.

What does am335x_boneblack_vboot_defconfig(ABVD) do?
What is the meaning of "_vboot_"?
Is that "Verified Boot" as of
<
https://source.denx.de/u-boot/u-boot/-/blob/master/test/py/tests/test_vboot.py
>?
If so, do I need it?

BeagleBone Green Wireless - serial debug port hangs after sending u-boot-spl.bin (since v2021.01)

[Tom Rini]

On Tue, May 11, 2021 at 04:04:34PM +0800, Darren Ng wrote:
> On Sat, May 8, 2021 at 1:40 AM Tom Rini <trini@konsulko.com> wrote:
> 
> > On Sat, May 08, 2021 at 12:02:21AM +0800, Darren Ng wrote:
> >
> > > (Hello, from a U-Boot NOOB.)
> > >
> > > Issue
> > > -----
> > > After sending u-boot-spl.bin with xmodem, the serial debug port seems to
> > > hang.
> > > Neither "...U-Boot SPL...\n...\nTrying to boot from UART..."
> > > nor "CCC..." shows up in minicom.
> > > Always 0% if I try sending u-boot.img with xmodem anyway.
> > >
> > > Target Device
> > > -------------
> > > Seeed Studio BeagleBone? Green Wireless
> > > https://seeeddoc.github.io/Beaglebone_green_wireless/
> > >
> > https://wiki.seeedstudio.com/BeagleBone_Green_Wireless/#hardware-overview
> > >
> > https://source.denx.de/u-boot/u-boot/-/commits/master/configs/am335x_boneblack_vboot_defconfig
> > >
> > > Matrix
> > > ------
> > > This issue applies to tags ever since v2021.01. In the following table:
> > > (x) - This issue applies.
> > > (O) - I can send both u-boot-spl.bin and u-boot.img
> > >       then execute u-boot commands without trouble.
> > > ------
> > > tag          result
> > > ------------ ------------------
> > > v2021.07-rc1 (x) hangs
> > > v2021.04     (x) hangs
> > > v2021.01     (x) hangs
> > > v2020.10     (O) success
> >
> > It looks like something broke between v2020.10 and v2021.01 then.  Since
> > you have a testcase, using "git bisect" should help figure out which
> > exact commit broke things.
> >
> > --
> > Tom
> >
> 
> ("reply all" instead of "reply")
> 
> v2021.04 running successfully with am335x_evm_defconfig(AED) now

OK, that's good.

> > commit 8fa7f65dd02c176ee6021eaf40114560b8954ba2
> > Author: Faiz Abbas <faiz_abbas@ti.com>
> > Date:   Thu Jan 17 15:44:06 2019 +0530
> >
> >     configs: Remove am335x_boneblack_defconfig
> >
> >     The am335x_evm_defconfig supports all am335x_boneblack variants.
> Remove
> >     the redundant am335x_boneblack_defconfig.
> >
> >     Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
> >     Reviewed-by: Tom Rini <trini@konsulko.com>
> >
> > D       configs/am335x_boneblack_defconfig
> 
> According to the commit log above, a previous
> am335x_boneblack_defconfig(ABD)
> is removed in favor of am335x_evm_defconfig(AED)

Yes, am335x_evm_defconfig supports a wide range of am335x-based
platforms, that have an i2c EEPROM on them to identify which board it is
at run-time.

> However there is a am335x_boneblack_vboot_defconfig(ABVD) in the tree,
> which is what I have failed with.
> 
> What does am335x_boneblack_vboot_defconfig(ABVD) do?
> What is the meaning of "_vboot_"?
> Is that "Verified Boot" as of
> <
> https://source.denx.de/u-boot/u-boot/-/blob/master/test/py/tests/test_vboot.py
> >?
> If so, do I need it?

Correct, it's an example of using that verified boot and you likely do
not need to use it.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210511/42972a74/attachment.sig>