From: Sascha Hauer <sha@pengutronix.de>
To: barebox+mailing@cookiesoft.de
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Heartbeat LED during init script
Date: Wed, 17 Feb 2021 13:35:17 +0100 [thread overview]
Message-ID: <20210217123517.GC19583@pengutronix.de> (raw)
In-Reply-To: <1474779923.1916.1613564552090@office.mailbox.org>
On Wed, Feb 17, 2021 at 01:22:32PM +0100, barebox+mailing@cookiesoft.de wrote:
> Hey everyone,
>
> we use the barebox bootloader in on of our products.
> Because of some norms we need to make a memtest of the RAM. To do that, we use the provided memtest tool.
> So one of our our scripts is `/env/init/10-memtest`, which has just `memtest -tc` in it.
>
>
> The other script is `/env/init/05-heartbeat` which contains
>
> #!/bin/sh
>
> led -b board-red 100 1000
>
> So, at first the 05 script is executed, afterwards the memtest script.
>
> The problem is, that during the memtest the led does not blink, but flashes red the whole time. After the memtest is done, the blinking is done perfectly fine, but not during the memtest.
>
> I create a small video to showcase this exact problem: https://imgur.com/a/9sxHTcm
>
> Can anybody tell me why the barebox isn't able to keep up with the blinking as well as how to mitigate that?
barebox doesn't support interrupts. LED blinking is done in pollers,
that are little function that run each time a timing related function is
called. What you can do is to add for example add a ctrlc() call to your
memtester code inside some loop. That will cause the poller to run.
Sascha
--
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-02-17 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 12:22 barebox+mailing
2021-02-17 12:35 ` Sascha Hauer [this message]
2021-02-17 12:44 ` barebox+mailing
2021-02-17 13:17 ` Sascha Hauer
2021-02-18 8:00 ` Marcel Hellwig
2021-02-18 8:34 ` Sascha Hauer
2021-02-18 9:01 ` Ahmad Fatoum
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=20210217123517.GC19583@pengutronix.de \
--to=sha@pengutronix.de \
--cc=barebox+mailing@cookiesoft.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