From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Reset on Beaglebone Black has become unreliable/broken
Date: Tue, 3 Dec 2024 22:45:54 +0100 [thread overview]
Message-ID: <Z098Eor4bedpsol9@hephaistos> (raw)
In-Reply-To: <49df1ec9-aca8-49b0-95fe-d577c5b615db@pengutronix.de>
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@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Derek Uhlig
HRB: 111204, AG Hannover
next prev parent reply other threads:[~2024-12-03 21:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 9:07 Konstantin Kletschke
2024-11-28 9:23 ` Ahmad Fatoum
2024-11-28 9:46 ` Konstantin Kletschke
2024-11-28 11:18 ` Ahmad Fatoum
2024-11-28 12:02 ` Konstantin Kletschke
2024-11-28 15:25 ` Konstantin Kletschke
2024-12-02 12:41 ` Ahmad Fatoum
2024-12-02 14:15 ` Konstantin Kletschke
2024-12-03 18:28 ` Ahmad Fatoum
2024-12-03 18:51 ` Konstantin Kletschke
2024-12-03 20:28 ` Ahmad Fatoum
2024-12-03 21:45 ` Konstantin Kletschke [this message]
2024-12-04 6:14 ` Ahmad Fatoum
2024-12-04 16:29 ` Konstantin Kletschke
2024-12-10 21:52 ` Ahmad Fatoum
2024-12-11 14:52 ` Konstantin Kletschke
2024-12-20 11:05 ` Konstantin Kletschke
2024-12-03 18:34 ` Konstantin Kletschke
2024-12-03 18:46 ` Ahmad Fatoum
2024-12-03 19:03 ` Konstantin Kletschke
2024-12-04 11:07 ` Konstantin Kletschke
2024-12-04 11:20 ` Konstantin Kletschke
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=Z098Eor4bedpsol9@hephaistos \
--to=konstantin.kletschke@inside-m2m.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox