Quick question?

jchludzinski jchludzinski at vivaldi.net
Fri Sep 25 17:59:35 CEST 2020


On 2020-09-25 07:13, Rayagonda Kokatanur wrote:
> On Fri, Sep 25, 2020, 4:32 PM jchludzinski <jchludzinski at 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?


More information about the U-Boot mailing list