On Wed, Aug 12, 2015 at 6:35 PM, <[email protected]> wrote: > Jumping Rx to 3V3 pretty much solved the problem for me. > > Why only "pretty much"? Well - I actually installed my first project on a > customer site. This project consists of 12 boards communicating back to a > management system. Because of the issue with the eth0 occasionally not > reconnecting (e.g. after the switch is restarted) I added safety code that > restarts the board if there is no communication back to the management > system for 120s. > > The system has been running perfectly for 2 months - but last week the > customer accidentally switched the management system off (power button > pressed; I've since disabled that button). The problem was only detected > after 4 days - so all 12 boards kept restarting for 4 days. This resulted in > roughly 30,000 restarts. After the management system was finally switched > back on 2 boards did not establish communication. I had to go on site > (luckily it is in the same city) and found that the 2 boards did not start > up. So 2 failed restarts out of 30,000 - even with Rx connected straight to > 3V3. > > I have to admit that I now look into other options (other than the BBB) > because as much as I like it I cannot use a HW platform that a.) does not > start up 100.00% reliably (even after manual modifications that should not > be necessary in the 1st place) and that b.) that does not always connect > back to the switch. I am scratching my head a little bit why the BBB team > does not fix those issues as they are not exactly disputed. It is clear > enough that the BBB does have a serious reboot issue (as this thread > certainly proves). Even worse is the issue with eth0 not always > re-connecting if static IP configuration is used. Just in case somebody > wonders if I really implemented all fixes suggested in the various forums - > this is what I've done for all 12 boards for my 1st project: > > Soldered Rx to 3V3 (much improved the restart issue but still 2 out of > 30,000 restarts fail) > Installed latest Debian image > Updated Kernel to latest version > Removed apache service > Removed DHCP service > Removed wicd service > Disabled lightdm (my applications doesn't need it) > Disabled HDMI (my applications doesn't need it) > Adjusted /etc/interfaces (set static IP for eth0) > > Note that ifconfig shows the correct IP address when the issue with eth0 not > connecting happens. > > So yeah - the BBB seems to be a great board but unfortunately not reliable > enough for 24*7 unattended operation. And I really cannot spend more time on > trouble shooting - I have enough work at my hands with the actual > application so I need a platform that works out of the box.
Please confirm which kernel your running: uname -r There's a big thread on this list, where a bunch spend about 2 weeks bisecting the v4.1.x kernel to find the cause of the "random" reboot.. sudo apt-get update sudo apt-get install linux-image-4.1.4-ti-r9 sudo reboot Regards, -- Robert Nelson https://rcn-ee.com/ -- 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]. For more options, visit https://groups.google.com/d/optout.
