I can also probe the board with a logic analyzer, wait to the event to occur and figure where in the hardware it started. Just don't want to be doing something that have already been discarded.
Robert: could you please put us in the loop about your investigation so we can team efforts? Thanks, Nuno On Wednesday, July 29, 2015 at 4:42:20 PM UTC+1, Graham wrote: > > > Robert: > > I know you are not looking for a hardware modification as a solution, but > if hardware modifications would help diagnose and debug the problem, I have > the capability to do "blue wires" or change parts, for about anything other > than a BGA. > > The trick is to get the BBB to tell you what is triggering the reboot. > > The USB power feed does not do it, the +5 V barrel power input does. > > Kernel 3.xx does not do it, kernel 4.x.x does. > > I suspect some code changes from the USB main line code has changed the > way the power source/direction sniffing works. > For instance, the USB connectors on tablets, which is probably inside > kernel 4, can accept power for charging tablet batteries, or supply power > for running thumb-drives or other USB accessories. > How they do this would change code in this exact area. > > If the PMIC is allowed to autonomously make power source switch-overs, > without permission from the Sitara, and it is making bad decisions, as > others have suggested, then I am not sure how to approach it. > > --- Graham > > == > > > -- 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. For more options, visit https://groups.google.com/d/optout.
