* [U-Boot] Kernel to U-boot messaging and vice versa.
@ 2015-03-17 15:28 Dev
2015-03-17 18:57 ` Hannes Petermaier
2015-03-17 19:15 ` Andy Pont
0 siblings, 2 replies; 6+ messages in thread
From: Dev @ 2015-03-17 15:28 UTC (permalink / raw)
To: u-boot
Hello,
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. We have a situation were our firmware keeps hanging due to some issues. 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.
I understand that once the Linux Kernel is booted, the bootloader is not there anymore. BUT, is there any way by modifying the Linux Kernel, we can achieve periodic U-boot to Kernel communication.
Thanks,
-Dev
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Kernel to U-boot messaging and vice versa.
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
1 sibling, 0 replies; 6+ messages in thread
From: Hannes Petermaier @ 2015-03-17 18:57 UTC (permalink / raw)
To: u-boot
Hi Dev,
for opinion, no way.
best regards,
Hannes
On 2015-03-17 16:28, Dev wrote:
> Hello,
> 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. We have a situation were our firmware keeps hanging due to some issues. 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.
>
> I understand that once the Linux Kernel is booted, the bootloader is not there anymore. BUT, is there any way by modifying the Linux Kernel, we can achieve periodic U-boot to Kernel communication.
>
> Thanks,
> -Dev
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Kernel to U-boot messaging and vice versa.
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
2015-03-17 20:53 ` Dev
1 sibling, 1 reply; 6+ messages in thread
From: Andy Pont @ 2015-03-17 19:15 UTC (permalink / raw)
To: u-boot
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Kernel to U-boot messaging and vice versa.
2015-03-17 19:15 ` Andy Pont
@ 2015-03-17 20:53 ` Dev
2015-03-17 21:39 ` Hannes Petermaier
0 siblings, 1 reply; 6+ messages in thread
From: Dev @ 2015-03-17 20:53 UTC (permalink / raw)
To: u-boot
Thank You Hannes and Andy for replying back.
I agree that the kernel and U-boot are very old. There are many units deployed out in the field which are running these versions. Hence, we are stuck on these old versions.
There are some kernel modules which are running above linux kernel. When we try to field upgrade these deployed units, due to external failures for example power surge, these kernel modules hang in a bad state, which causes the unit unusable. In those conditions we want the unit to go through reset sequence.
Regards,
-Dev
> From: andy.pont at sdcsystems.com
> To: dsupehia at hotmail.com
> CC: u-boot at lists.denx.de
> Subject: RE: [U-Boot] Kernel to U-boot messaging and vice versa.
> Date: Tue, 17 Mar 2015 19:15:24 +0000
>
> 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.
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Kernel to U-boot messaging and vice versa.
2015-03-17 20:53 ` Dev
@ 2015-03-17 21:39 ` Hannes Petermaier
2015-03-18 13:50 ` Dev
0 siblings, 1 reply; 6+ messages in thread
From: Hannes Petermaier @ 2015-03-17 21:39 UTC (permalink / raw)
To: u-boot
Hi Dev,
Altough your problem is off-topic from u-boot, we want to help you :-)
the only solution what i see, is some watchdog.
Maybe your CPU has such feature or your hardware around does offer some
watchdog.
best regards,
Hannes
On 2015-03-17 21:53, Dev wrote
> Thank You Hannes and Andy for replying back.
>
> I agree that the kernel and U-boot are very old. There are many units deployed out in the field which are running these versions. Hence, we are stuck on these old versions.
>
> There are some kernel modules which are running above linux kernel. When we try to field upgrade these deployed units, due to external failures for example power surge, these kernel modules hang in a bad state, which causes the unit unusable. In those conditions we want the unit to go through reset sequence.
>
> Regards,
> -Dev
>
>> From: andy.pont at sdcsystems.com
>> To: dsupehia at hotmail.com
>> CC: u-boot at lists.denx.de
>> Subject: RE: [U-Boot] Kernel to U-boot messaging and vice versa.
>> Date: Tue, 17 Mar 2015 19:15:24 +0000
>>
>> 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.
>>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Kernel to U-boot messaging and vice versa.
2015-03-17 21:39 ` Hannes Petermaier
@ 2015-03-18 13:50 ` Dev
0 siblings, 0 replies; 6+ messages in thread
From: Dev @ 2015-03-18 13:50 UTC (permalink / raw)
To: u-boot
Thanks Hannes, Let me look around for watchdog functionality.
Regards,
-Dev
> Date: Tue, 17 Mar 2015 22:39:41 +0100
> From: hannes at petermaier.org
> To: u-boot at lists.denx.de
> Subject: Re: [U-Boot] Kernel to U-boot messaging and vice versa.
>
> Hi Dev,
>
> Altough your problem is off-topic from u-boot, we want to help you :-)
>
> the only solution what i see, is some watchdog.
> Maybe your CPU has such feature or your hardware around does offer some
> watchdog.
>
> best regards,
> Hannes
>
> On 2015-03-17 21:53, Dev wrote
> > Thank You Hannes and Andy for replying back.
> >
> > I agree that the kernel and U-boot are very old. There are many units deployed out in the field which are running these versions. Hence, we are stuck on these old versions.
> >
> > There are some kernel modules which are running above linux kernel. When we try to field upgrade these deployed units, due to external failures for example power surge, these kernel modules hang in a bad state, which causes the unit unusable. In those conditions we want the unit to go through reset sequence.
> >
> > Regards,
> > -Dev
> >
> >> From: andy.pont at sdcsystems.com
> >> To: dsupehia at hotmail.com
> >> CC: u-boot at lists.denx.de
> >> Subject: RE: [U-Boot] Kernel to U-boot messaging and vice versa.
> >> Date: Tue, 17 Mar 2015 19:15:24 +0000
> >>
> >> 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.
> >>
> >
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
> >
> >
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-03-18 13:50 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2015-03-17 20:53 ` Dev
2015-03-17 21:39 ` Hannes Petermaier
2015-03-18 13:50 ` Dev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox