Twang: Well, that is what the "Auto-Ping" is all about.
If I don't get a ping from you in the last two minutes, then you get power-cycled/rebooted. There are IoT PICs that are ~$5 that can speak Ethernet and could be programmed to reset, or press the power button if 5V was present, and they had not heard from the BBB lately. More appropriate monitoring for a server, than watching some GPIO wiggle. --- Graham On Monday, May 16, 2016 at 8:08:01 PM UTC-5, Super Twang wrote: > > @Graham > Wow! I hadn’t yet thought of Ethernet as a point of failure. Apart from > the (“It doesn’t always soft-reset" issue — see outline I.B.1.b) I’d guess > you could solve this with the onboard watchdog timer. Run some kind of > daemon that periodically “Checks for good ethernet” (a bit vague, I know), > if found, it tickles the watchdog, if not, it provokes a reboot. But yes, > the problem remains that the reboot doesn’t always complete. > > Of course if your ethernet got fried, that’d turn into a reboot cycle > without some logic to notify you of the problem, and stop after a number of > cycles. > > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/20debbaf-a5a3-48e3-95a1-2984b714daf4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
