* Quick question?
@ 2020-09-24 21:36 jchludzinski
2020-09-24 21:39 ` jchludzinski
0 siblings, 1 reply; 6+ messages in thread
From: jchludzinski @ 2020-09-24 21:36 UTC (permalink / raw)
To: u-boot
I'm trying to bring up an RTOS (vxworks) using u-boot and have had some
"partial" success:
If I use the 2014 u-boot that comes with Quartus 18.1 (a tarball in the
download), vxworks successfully boots.
If I clone the github repo
(https://github.com/altera-opensource/u-boot-socfpga.git) and build
u-boot from that (2020), vxworks fails to boot. What appears to be
happening is an (fpga?) watchdog timer goes off and a HW reset is
called. Then of course, u-boot reboots.
Any thoughts? Why would this occur with the newer u-boot and not with
the older u-boot?
---John
^ permalink raw reply [flat|nested] 6+ messages in thread
* Quick question?
2020-09-24 21:36 Quick question? jchludzinski
@ 2020-09-24 21:39 ` jchludzinski
2020-09-25 11:13 ` Rayagonda Kokatanur
0 siblings, 1 reply; 6+ messages in thread
From: jchludzinski @ 2020-09-24 21:39 UTC (permalink / raw)
To: u-boot
On 2020-09-24 17:36, jchludzinski wrote:
> I'm trying to bring up an RTOS (vxworks) using u-boot and have had
> some "partial" success:
>
> If I use the 2014 u-boot that comes with Quartus 18.1 (a tarball in
> the download), vxworks successfully boots.
>
> If I clone the github repo
> (https://github.com/altera-opensource/u-boot-socfpga.git) and build
> u-boot from that (2020), vxworks fails to boot. What appears to be
> happening is an (fpga?) watchdog timer goes off and a HW reset is
> called. Then of course, u-boot reboots.
>
> Any thoughts? Why would this occur with the newer u-boot and not with
> the older u-boot?
>
> ---John
I don't see the "Watchdog enabled" message in the output from the older
u-boot.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Quick question?
2020-09-24 21:39 ` jchludzinski
@ 2020-09-25 11:13 ` Rayagonda Kokatanur
2020-09-25 15:59 ` jchludzinski
0 siblings, 1 reply; 6+ messages in thread
From: Rayagonda Kokatanur @ 2020-09-25 11:13 UTC (permalink / raw)
To: u-boot
On Fri, Sep 25, 2020, 4:32 PM jchludzinski <jchludzinski@vivaldi.net> wrote:
> On 2020-09-24 17:36, jchludzinski wrote:
> > I'm trying to bring up an RTOS (vxworks) using u-boot and have had
> > some "partial" success:
> >
> > If I use the 2014 u-boot that comes with Quartus 18.1 (a tarball in
> > the download), vxworks successfully boots.
> >
> > If I clone the github repo
> > (https://github.com/altera-opensource/u-boot-socfpga.git) and build
> > u-boot from that (2020), vxworks fails to boot. What appears to be
> > happening is an (fpga?) watchdog timer goes off and a HW reset is
> > called. Then of course, u-boot reboots.
> >
> > Any thoughts? Why would this occur with the newer u-boot and not with
> > the older u-boot?
> >
> > ---John
>
> I don't see the "Watchdog enabled" message in the output from the older
> u-boot.
>
watchdog service starts by default in latest uboot and it's set to 60s.
If you wait for more than 60s at uboot prompt or you os loading takes long
time then watchdog resets.
Define CONFIG_WATCHDOG , this will takes care of resting watchdog.
Thanks,
Rayagonda
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4187 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200925/6187d11c/attachment.bin>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Quick question?
2020-09-25 11:13 ` Rayagonda Kokatanur
@ 2020-09-25 15:59 ` jchludzinski
2020-09-25 16:17 ` Rayagonda Kokatanur
0 siblings, 1 reply; 6+ messages in thread
From: jchludzinski @ 2020-09-25 15:59 UTC (permalink / raw)
To: u-boot
On 2020-09-25 07:13, Rayagonda Kokatanur wrote:
> On Fri, Sep 25, 2020, 4:32 PM jchludzinski <jchludzinski@vivaldi.net>
> wrote:
>
>> On 2020-09-24 17:36, jchludzinski wrote:
>>> I'm trying to bring up an RTOS (vxworks) using u-boot and have had
>>> some "partial" success:
>>>
>>> If I use the 2014 u-boot that comes with Quartus 18.1 (a tarball
>> in
>>> the download), vxworks successfully boots.
>>>
>>> If I clone the github repo
>>> (https://github.com/altera-opensource/u-boot-socfpga.git) and
>> build
>>> u-boot from that (2020), vxworks fails to boot. What appears to be
>>> happening is an (fpga?) watchdog timer goes off and a HW reset is
>>> called. Then of course, u-boot reboots.
>>>
>>> Any thoughts? Why would this occur with the newer u-boot and not
>> with
>>> the older u-boot?
>>>
>>> ---John
>>
>> I don't see the "Watchdog enabled" message in the output from the
>> older
>> u-boot.
>
> watchdog service starts by default in latest uboot and it's set to
> 60s.
>
> If you wait for more than 60s at uboot prompt or you os loading takes
> long time then watchdog resets.
>
> Define CONFIG_WATCHDOG , this will takes care of resting watchdog.
>
> Thanks,
> Rayagonda
>
>>
Thanks for the suggestion but this reset occurs while vxworks is in the
process of booting up.
Could u-boot set a HW watchdog timer before handing control over to
vxworks and, while vxworks is booting, the timer goes off and calls
reset?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Quick question?
2020-09-25 15:59 ` jchludzinski
@ 2020-09-25 16:17 ` Rayagonda Kokatanur
2020-09-25 16:48 ` jchludzinski
0 siblings, 1 reply; 6+ messages in thread
From: Rayagonda Kokatanur @ 2020-09-25 16:17 UTC (permalink / raw)
To: u-boot
On Fri, Sep 25, 2020 at 9:29 PM jchludzinski <jchludzinski@vivaldi.net>
wrote:
> On 2020-09-25 07:13, Rayagonda Kokatanur wrote:
> > On Fri, Sep 25, 2020, 4:32 PM jchludzinski <jchludzinski@vivaldi.net>
> > wrote:
> >
> >> On 2020-09-24 17:36, jchludzinski wrote:
> >>> I'm trying to bring up an RTOS (vxworks) using u-boot and have had
> >>> some "partial" success:
> >>>
> >>> If I use the 2014 u-boot that comes with Quartus 18.1 (a tarball
> >> in
> >>> the download), vxworks successfully boots.
> >>>
> >>> If I clone the github repo
> >>> (https://github.com/altera-opensource/u-boot-socfpga.git) and
> >> build
> >>> u-boot from that (2020), vxworks fails to boot. What appears to be
> >>> happening is an (fpga?) watchdog timer goes off and a HW reset is
> >>> called. Then of course, u-boot reboots.
> >>>
> >>> Any thoughts? Why would this occur with the newer u-boot and not
> >> with
> >>> the older u-boot?
> >>>
> >>> ---John
> >>
> >> I don't see the "Watchdog enabled" message in the output from the
> >> older
> >> u-boot.
> >
> > watchdog service starts by default in latest uboot and it's set to
> > 60s.
> >
> > If you wait for more than 60s at uboot prompt or you os loading takes
> > long time then watchdog resets.
> >
> > Define CONFIG_WATCHDOG , this will takes care of resting watchdog.
> >
> > Thanks,
> > Rayagonda
> >
> >>
> Thanks for the suggestion but this reset occurs while vxworks is in the
> process of booting up.
>
> Could u-boot set a HW watchdog timer before handing control over to
> vxworks and, while vxworks is booting, the timer goes off and calls
> reset?
>
If wdt is not initialized by vxworks then I think uboot wdt will be running
and it will reset.
Did you try defining CONFIG_WATCHDOG in uboot ?
Best regards,
Rayagonda
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4187 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200925/2ab79835/attachment.bin>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Quick question?
2020-09-25 16:17 ` Rayagonda Kokatanur
@ 2020-09-25 16:48 ` jchludzinski
0 siblings, 0 replies; 6+ messages in thread
From: jchludzinski @ 2020-09-25 16:48 UTC (permalink / raw)
To: u-boot
On 2020-09-25 12:17, Rayagonda Kokatanur wrote:
> On Fri, Sep 25, 2020 at 9:29 PM jchludzinski
> <jchludzinski@vivaldi.net> wrote:
>
>> On 2020-09-25 07:13, Rayagonda Kokatanur wrote:
>>> On Fri, Sep 25, 2020, 4:32 PM jchludzinski
>> <jchludzinski@vivaldi.net>
>>> wrote:
>>>
>>>> On 2020-09-24 17:36, jchludzinski wrote:
>>>>> I'm trying to bring up an RTOS (vxworks) using u-boot and have
>> had
>>>>> some "partial" success:
>>>>>
>>>>> If I use the 2014 u-boot that comes with Quartus 18.1 (a tarball
>>>> in
>>>>> the download), vxworks successfully boots.
>>>>>
>>>>> If I clone the github repo
>>>>> (https://github.com/altera-opensource/u-boot-socfpga.git) and
>>>> build
>>>>> u-boot from that (2020), vxworks fails to boot. What appears to
>> be
>>>>> happening is an (fpga?) watchdog timer goes off and a HW reset
>> is
>>>>> called. Then of course, u-boot reboots.
>>>>>
>>>>> Any thoughts? Why would this occur with the newer u-boot and not
>>>> with
>>>>> the older u-boot?
>>>>>
>>>>> ---John
>>>>
>>>> I don't see the "Watchdog enabled" message in the output from the
>>>> older
>>>> u-boot.
>>>
>>> watchdog service starts by default in latest uboot and it's set to
>>> 60s.
>>>
>>> If you wait for more than 60s at uboot prompt or you os loading
>> takes
>>> long time then watchdog resets.
>>>
>>> Define CONFIG_WATCHDOG , this will takes care of resting watchdog.
>>>
>>> Thanks,
>>> Rayagonda
>>>
>>>>
>> Thanks for the suggestion but this reset occurs while vxworks is in
>> the
>> process of booting up.
>>
>> Could u-boot set a HW watchdog timer before handing control over to
>> vxworks and, while vxworks is booting, the timer goes off and calls
>> reset?
>
> If wdt is not initialized by vxworks then I think uboot wdt will be
> running and it will reset.
> Did you try defining CONFIG_WATCHDOG in uboot ?
>
> Best regards,
> Rayagonda
Yes I did. It continues to reset.
---John
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-09-25 16:48 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-09-24 21:36 Quick question? jchludzinski
2020-09-24 21:39 ` jchludzinski
2020-09-25 11:13 ` Rayagonda Kokatanur
2020-09-25 15:59 ` jchludzinski
2020-09-25 16:17 ` Rayagonda Kokatanur
2020-09-25 16:48 ` jchludzinski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox