Overo IronSTORM on Tobi boot restarts after 18-20sec

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Overo IronSTORM on Tobi boot restarts after 18-20sec

gab_ngek
This post has NOT been accepted by the mailing list yet.
I have a new Overo IronSTORM-y and new Tobi expansion board.  Everything worked fine for a couple months.  Now the system reboots after about 18 to 20 seconds into the boot process.  No error message, the system just restarts the boot process:
 ... normal boot start messages...
[   18.945007] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   18.971557] systemd[1]: PID file /run/ntpd.pid not readable (yet?) after start.
[  OK  ] Started Network Time Service.
         Starting WPA supplicant...
[  OK  ] Started WPA supplicant.
�tذb�$U
             @ @ @D��` @ @
U-Boot SPL 2015.07 (May 24 2017 - 02:46:49)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
... normal boot start messages...
[   19.191497] systemd[1]: PID file /run/ntpd.pid not readable (yet?) after start.
[  OK  ] Started Network Time Service.
         Starting WPA supplicant...
[  OK  ] Started WPA supplicant.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
�tذb�$U
             @ @ @D��` @ @
U-Boot SPL 2015.07 (May 24 2017 - 02:46:49)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
Same COM will boot just fine on a Arbor 70C expansion board.
Same behavior if I boot from internal memory or from the MMC.
A second IronSTORM-y COM I have will boot just fine.  
The boot parameters are identical on the two COMS.

Any hints as to why one of the COMs has suddenly started having trouble without any changes to the software?

Thanks,
george
Loading...