On Thu, Nov 28, 2024 at 12:18:45PM +0100, Ahmad Fatoum wrote:
>
> Are you still building with the same toolchain?
Yes, I am always using a yocto kirkstone with its toolchain:
- git clone -b kirkstone git://git.yoctoproject.org/poky.git
- git -C poky checkout tags/yocto-4.0.13
and
- git clone -b kirkstone https://github.com/menschel-d/meta-barebox.git
- mv meta-barebox poky/meta-barebox
> So repeating these steps on some boards never shows any issues and on
> some others it always shows issues?
Yes
> So this happens even after a completely cold reset?
Yes: Power on, hit S1 or type reset in stopped barebox -> freeze
> I'd suggest you enable CONFIG_DEBUG_LL and look if you see at least a >
> character on the serial console output by the MLO.
>
> If you don't see it, try moving these lines:
>
> am33xx_uart_soft_reset((void *)AM33XX_UART0_BASE);
> am33xx_enable_uart0_pin_mux();
> omap_debug_ll_init();
> putc_ll('>');
>
> to the start of beaglebone_sram_init() and see if you get the > printed.
>
> The point is making sure that barebox itself starts up before seeing where
> it's getting stuck.
I will try that immediately.
I reproduced the same behaviour with a non resetting BBB device with
different software setup:
Checked out current barebox git: barebox 2024.10.0-00150-g7a3cb7e6fd63 #2 Thu Nov 28 12:37:15 CET 2024
Changed CONFIG_BAREBOX_MAX_IMAGE_SIZE from 0x1b400 to 0x2b400
Did am335x_mlo_defconfig and omap_defconfig and copied those images.
I used another crosscompiler toolchain for this: gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf
Same error behaviour: Power up -> S1 or "reset" produce freeze.
Will test CONFIG_DEBUG_LL and/or move those lines around.
Regards
Konsti
--
INSIDE M2M GmbH
Konstantin Kletschke
Berenbosteler Straße 76 B
30823 Garbsen
Telefon: +49 (0) 5137 90950136
Mobil: +49 (0) 151 15256238
Fax: +49 (0) 5137 9095010
konstantin.kletschke@xxxxxxxxxxxxx
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Derek Uhlig
HRB: 111204, AG Hannover
