If you cannot do a complete reboot and remove the OS and GPIO isetup, can you return the unit to the place you bought it from, and let them figure it out.
On Thu, Jan 25, 2018 at 11:37 AM, <cnctechr...@gmail.com> wrote: > Could it be the on board battery is retaining the GPio confirguration from > your ROS setup? > > On Thursday, January 4, 2018 at 8:51:56 AM UTC-5, George Terzakis wrote: >> >> Hello everyone, >> >> I have been using the Beaglebone Blue for over 3 months now without any >> problems until now. The board typically boots off the SD card, primarily >> because I needed the extra space for a ROS installation. I originallyt used >> the latest Debian Jessie image for a couple of months and then created a >> new SD card (early December 2017) with the new Debian stretch image and >> then setup ROS (from source). >> >> EMMC does not boot anymore >> -------------------------------------------- >> I recently noticed that when the SD card is removed, the board will not >> boot from the EMMC for some reason. This was clearly not the case about a >> month ago when I moved on to stretch, so whatever caused this must have >> happened recently. I typically power the board from the USB and >> occasionally from an external 12V DC source. In terms of devices, I am >> using the IMU and the UART to talk to a motor controller (Roboteq in >> particular), but during the last month the controller was not connected, so >> the board was practically running with no external devices connected to it. >> I once or twice briefly used different SD cards on it. >> >> Other (potentially) Related Issues >> -------------------------------------- >> In addition to not booting from the EMMC, I noticed occasional hangs >> during updates and/or prolonged downloads. In some cases, the crashed >> download/update process can be interrupted by Ctrl-C and in others not. >> Regardless, the Beaglebone does not work properly, as many subsequent >> commands (for instance, "ps") will crash and the only way to recover is by >> hard reset. However, in many occasions after the reset, the root file >> system is corrupted and we have to repair it using fsck. >> >> Consistency >> ------------------ >> I originally believed that the stretch installation was the source of the >> crash problem (did not think it was related to the EMMC not booting up), so >> I re-installed Debian Jessie and stretch multiple times to realize that the >> crashing-during-updates problem was consistently re-appearing regardless of >> Debian version at various stages. Thus, I was led to believe that this a >> board issue rather than something that has to do with the Debian and most >> probably, not being able to boot from the EMMC is a symptom of the same >> problem. In my last attempt, I burned the stretch image into the SD card >> and the Debian could not update right off the bat (it gave a root file >> system error : >> >> E: List directory /var/lib/apt/lists/partial is missing. - Acquire (30: >> Read-only file system) >> >> Note that the Beaglebone Blue board appears to be in working order >> otherwise (i.e., wireless appears to work, cloud page, etc.). >> >> I would very much appreciate your help in troubleshooting this problem >> and most importantly, finding out its cause. >> >> Regards >> >> >> George >> >> >> >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/beagleboard/oC-XSkl9lBc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beagleboard/45378119-7180-4407-83c6-a05befb50be7%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/45378119-7180-4407-83c6-a05befb50be7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAEPro0e6WHv%2B4WNWKkn-yTJCDsEityU0arNS-xGSHZC54bkwzQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
