From: Andy Pont <andy.pont@sdcsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Kernel to U-boot messaging and vice versa.
Date: Tue, 17 Mar 2015 19:15:24 -0000 [thread overview]
Message-ID: <010d01d060e6$bf55f310$3e01d930$@pont@sdcsystems.com> (raw)
In-Reply-To: <BLU171-W140221FBF71B22109A3126FD8030@phx.gbl>
Dev wrote...
> I am new to U-boot development. We are using U-Boot 1.1.4 on a MIPS
> 74Kc QCA 9557 processor, which is running Linux Kernel 2.6.32.27.
Is there a reason why you have to be running a kernel from 2010 and a
version of bootloader that is even older? It makes life much easier to
provide support if you can update to more recent versions and you never know
they may already have fixed your problems!
> We have a situation were our firmware keeps hanging due to some issues.
What is your "firmware" in this context? As you rightly said, once the
Linux kernel is running U-Boot is no more and if U-Boot is hanging then you
aren't going to get to the kernel anyway!
> We are looking into a solution where U-boot and Kernel keep communicating
> with each other every some minutes. If U-boot finds that there is no
> communication, it will reset the board.
This sounds like it is the territory of watchdog timers. I don't know that
CPU to know whether it has one built in though, nor if the kernel supports
it.
Andy.
next prev parent reply other threads:[~2015-03-17 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 15:28 [U-Boot] Kernel to U-boot messaging and vice versa Dev
2015-03-17 18:57 ` Hannes Petermaier
2015-03-17 19:15 ` Andy Pont [this message]
2015-03-17 20:53 ` Dev
2015-03-17 21:39 ` Hannes Petermaier
2015-03-18 13:50 ` Dev
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='010d01d060e6$bf55f310$3e01d930$@pont@sdcsystems.com' \
--to=andy.pont@sdcsystems.com \
--cc=u-boot@lists.denx.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