From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
Cc: barebox@lists.infradead.org
Subject: Re: Reset on Beaglebone Black has become unreliable/broken
Date: Tue, 7 Jan 2025 15:35:04 +0100 [thread overview]
Message-ID: <9c8d6171-c228-4e4a-97da-f1ce93e14aed@pengutronix.de> (raw)
In-Reply-To: <Z30oWivcXTQmw9ZO@hephaistos>
Hello Konstantin,
On 07.01.25 14:12, Konstantin Kletschke wrote:
> On Tue, Jan 07, 2025 at 12:17:03PM +0100, Ahmad Fatoum wrote:
> Should add a delay of 1.8ms. Is this feasible?
Sounds ok to me. Please send a patch to that effect with an explanatory
comment, summarizing what hardware was observed to have what issues.
>> If it's indeed just a millisecond, I am in favor of adding this to
>> barebox upstream with a comment explaining what this fixes, even
>> if we don't fully understand it yet.
>
> Yes, I agree to the not fully yet understood part.
> What me holds back from lowering the speed is the following:
>
> I went into production with the final result part above and reflashe all
> our BBB devices which failed warm start without the additional delay and
> all passed 100% flawlessly after the modficication. So it is tested upon
> roughly 30 devices which failed before.
I am surprised you are still shipping new products with a Beaglebone Black,
but anyhow, we need to be pragmatic and a ~2ms delay, even if not completely
understood is an acceptable price to pay for barebox reliably starting up
on newly produced BBBs.
Cheers,
Ahmad
>
> Kind Regards
> Konstantin
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-01-07 14:36 UTC|newest]
Thread overview: 27+ 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
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
2025-01-07 11:17 ` Ahmad Fatoum
2025-01-07 13:12 ` Konstantin Kletschke
2025-01-07 14:29 ` Konstantin Kletschke
2025-01-07 14:35 ` Ahmad Fatoum [this message]
2025-01-07 15:03 ` 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=9c8d6171-c228-4e4a-97da-f1ce93e14aed@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=konstantin.kletschke@inside-m2m.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox