From: jchludzinski <jchludzinski@vivaldi.net>
To: u-boot@lists.denx.de
Subject: Quick question?
Date: Fri, 25 Sep 2020 11:59:35 -0400 [thread overview]
Message-ID: <63b3f47ef8c46f07d56d33ee57c78347@vivaldi.net> (raw)
In-Reply-To: <CAHO=5PH5mh7YJiLeuSiBH6DcgjRWc=BsFtn1WZO5YXGmR33iEQ@mail.gmail.com>
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?
next prev parent reply other threads:[~2020-09-25 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2020-09-25 16:17 ` Rayagonda Kokatanur
2020-09-25 16:48 ` jchludzinski
-- strict thread matches above, loose matches on Subject: below --
2013-12-09 15:59 Stojsavljevic, Zoran
2013-12-09 16:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-09 16:10 ` Andrey Borzenkov
2013-12-10 12:40 ` Stojsavljevic, Zoran
2013-12-11 13:17 ` Colin Watson
2006-05-22 15:46 4 disks in raid 5: 33MB/s read performance? Dexter Filmore
2006-05-22 23:02 ` Neil Brown
2006-05-24 8:21 ` Max. md array size under 32-bit i368 Gordon Henderson
2006-06-06 9:36 ` Quick Question Gordon Henderson
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=63b3f47ef8c46f07d56d33ee57c78347@vivaldi.net \
--to=jchludzinski@vivaldi.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.