On Tue, Dec 03, 2024 at 09:28:39PM +0100, Ahmad Fatoum wrote:
> - Try it first on a correctly working system an see that you get a >
> at the usual place.
Working system and comparison of its registers of PMIC with broken one
tomorrow. If still required.
> - Try it on a broken system and see if you get a >
YES. I get this at the very first start with a '2' and console note
before 2 empty newlines and then
the "barebox 2024.10.0-00152-g53c99b9f550b-dirty #33 Tue Dec 3 22:01:26
CET 2024":
2>Switch to console [cs0]
barebox 2024.10.0[...]
> See the patch I just Cc'd you on.
Worked like a charm!
With vanilla code (one ">" in lowlevel.c) I get
the LL output, the warm reset behaviour (stuck at S1, watchdog, reset
cmd, linux reboot) is the same. As expected since its only debugging
dealt with here.
Being the playful idiot child I am I was so happy this now working I wanted to
see something more and added this in lowlevel.c:
@@ -135,6 +140,9 @@ static noinline int beaglebone_sram_init(void)
am33xx_enable_uart0_pin_mux();
omap_debug_ll_init();
putc_ll('>');
+ putc_ll('6');
+ putc_ll('6');
+ putc_ll('6');
Aka added three 6 to be put out, which they are!
The side effect of my additional 3 6 chars is:
reset cmd, S1, wd 3, mw 0x44e00f00 0x1 and linux reboot are working fine now!
Additional LL debug output is there, console notification message, >, my sixes,
and it comes reliably up!
Kind Regards
Konstantin
--
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
