Perhaps a work-around would be to provide a software possibility of freezing the unit after the kernel is down. Handy for someone who has a power-hungry cape requiring a power supply, no Ethernet and would like to safely replace the sd card. If it were possible to detect, that the unit is going to reboot anyway, the freeze could even be chosen automatically if a shutdown is requested.
On Thursday, April 27, 2017 at 6:41:17 PM UTC+2, William Hermans wrote: > > By the way those changes which I mentioned for the USB OTG port are made > through device tree configurations. I think in the main board file, but > that problem has been corrected so long ago, I do not remember exactly how. > > Here, we do not connect to our boards in this manner, ever.I have one > beaglebone black that I do power over that USB port here, but never with a > barrel jack, or through the P9 header at the same time. We have a few capes > we're working on, with different beaglebone greens. These are all powered > through the P9 header, but communication is made through ethernet on those > boards. Well actually, all the boards we have in our "lab" are connected > via ethernet for communications. > > On Thu, Apr 27, 2017 at 9:34 AM, William Hermans <[email protected] > <javascript:>> wrote: > >> >> >> On Thu, Apr 27, 2017 at 1:27 AM, ithinu <[email protected] <javascript:> >> > wrote: >> >>> > Short story, you're using a powered hub, and you need to keep that hub >>> from sending power back into the host. >>> >>> No, the hub is not powered. Also, as I said, the problem exists only >>> with the combination power supply/usb connection, which I rarely need. But >>> it still can be a problem of someone else. >>> >>> So, I would guess, it is more of checking the issue by the board >>> constructors before the next rev of BeagleBone. Especially that someone in >>> the other thread reports that the problem is spotty. With an oscilloscope, >>> power supplies of different power, capes or not, USB cables of different >>> length etc., until the cause is apparent. Or just don't care :) >>> >>> In any case, I can be of help, for example I can check if the problem >>> persists with the board connected directly to a PC. >>> >> >> The issue in the post you linked to has to be different. Unless you've >> gone and reconfigured the USB OTG port, though software, which is possible. >> So while the problem Harvey was talking about in that post *could* be >> corrected through hardware changes. Making those changes would be less than >> ideal. As it would reduce the flexibility of the USB mini connector. There >> are two or possibly three different modes the USB mini connector could be >> configured into through software. >> > > -- 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/9580793f-c85c-4827-a6c2-5e9ad9336893%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
