Skip to contentSkip to conversation

Quick question?

DISCUSSION jchludzinski 2 participants 6 messages Sep 24, 2020 – Sep 25, 2020

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 12 lines · jchludzinski

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.

Quoted 4 lines

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.

#2 lore raw
Quoted 13 lines · jchludzinski
Quoted 12 lines · jchludzinski

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.

Quoted 8 lines
Quoted 4 lines

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

Quoted 1 line

-------------- 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>

#3 lore raw
Quoted 31 lines · Rayagonda Kokatanur
Quoted 16 lines · jchludzinski
Quoted 4 lines · jchludzinski

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

Quoted 4 lines

the download), vxworks successfully boots.

If I clone the github repo
(https://github.com/altera-opensource/u-boot-socfpga.git) and

build

Quoted 5 lines

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

Quoted 8 lines

with

Quoted 3 lines

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.

Quoted 9 lines

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

Quoted 1 line

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?

#4 lore raw
Quoted 41 lines · jchludzinski
Quoted 31 lines · Rayagonda Kokatanur
Quoted 16 lines · jchludzinski
Quoted 4 lines · jchludzinski

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

Quoted 4 lines

the download), vxworks successfully boots.

If I clone the github repo
(https://github.com/altera-opensource/u-boot-socfpga.git) and

build

Quoted 5 lines

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

Quoted 8 lines

with

Quoted 3 lines

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.

Quoted 9 lines

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

Quoted 1 line
Quoted 7 lines

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>

#5 lore raw
Quoted 57 lines · Rayagonda Kokatanur
Quoted 46 lines · jchludzinski
Quoted 1 line · Rayagonda Kokatanur

On Fri, Sep 25, 2020, 4:32 PM jchludzinski

<[email protected]>

Quoted 4 lines
Quoted 2 lines · wrote:
Quoted 1 line · jchludzinski

I'm trying to bring up an RTOS (vxworks) using u-boot and have

had

Quoted 10 lines
Quoted 10 lines
Quoted 3 lines

some "partial" success:

If I use the 2014 u-boot that comes with Quartus 18.1 (a tarball

in

Quoted 4 lines

the download), vxworks successfully boots.

If I clone the github repo
(https://github.com/altera-opensource/u-boot-socfpga.git) and

build

Quoted 1 line

u-boot from that (2020), vxworks fails to boot. What appears to

be

Quoted 1 line
Quoted 1 line
Quoted 1 line

happening is an (fpga?) watchdog timer goes off and a HW reset

is

Quoted 8 lines
Quoted 8 lines
Quoted 3 lines

called. Then of course, u-boot reboots.

Any thoughts? Why would this occur with the newer u-boot and not

with

Quoted 3 lines

the older u-boot?

---John

Quoted 8 lines
Quoted 3 lines

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

Quoted 8 lines

long time then watchdog resets.

Define CONFIG_WATCHDOG , this will takes care of resting watchdog.

Thanks,
Rayagonda

Quoted 1 line
Quoted 7 lines

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?

Quoted 6 lines

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