So now I'm in pitbull mode, but I wont be able to do any further research at this time.
https://www.kernel.org/doc/Documentation/devicetree/bindings/usb/am33xx-usb.txt . . . USB ~~~ - compatible: ti,musb-am33xx - reg: offset and length of "USB Controller Registers", and offset and length of "USB Core" register space. - reg-names: control for the ""USB Controller Registers" and "mc" for "USB Core" register space - interrupts: USB interrupt number - interrupt-names: mc - *dr_mode: Should be one of "host", "peripheral" or "otg".* - mentor,multipoint: Should be "1" indicating the musb controller supports multipoint. This is a MUSB configuration-specific setting. - mentor,num-eps: Specifies the number of endpoints. This is also a MUSB configuration-specific setting. Should be set to "16" - mentor,ram-bits: Specifies the ram address size. Should be set to "12" - mentor,power: Should be "500". This signifies the controller can supply up to 500mA when operating in host mode. - phys: reference to the USB phy - dmas: specifies the dma channels - dma-names: specifies the names of the channels. Use "rxN" for receive and "txN" for transmit endpoints. N specifies the endpoint number. The controller should have an "usb" alias numbered properly in the alias node. . . . You can try experimenting with the "mode" I've highlighted above. You'd have to modify this board file here: https://github.com/jadonk/cape-firmware/blob/master/arch/arm/boot/dts/am335x-bone-common.dtsi#L204 And recompile all of, or the single board file you use at boot time. Of course then you've have to move the old board file out of the way, and replace it with the one you built yourself. On Thu, Apr 27, 2017 at 1:59 PM, William Hermans <[email protected]> wrote: > It would not be part of "my" FAQ. I have no affiliation with > beagleboard.org, at all. I'm just some guy, who has had 4+ years hands on > experience with this specific platform, who also just so happens to get > paid by a third party who builds systems based on this platform as well. > But obviously I do not know everything. > > I actually want to fix the way this board powers down when a battery is > connected to the beaglebone, myself. Which means when I did into the guts > of everything that is involved I could probably look into this problem as > well.It's not something that is high priority in my life right now, but > *is* something that I've spent money out of my own pocket on having > hardware designed for. PCB's, and components, etc. Now, I just need the > time to develop the software, which may, or may not happen some time soon. > > > > -- 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/CALHSORpg3tJVpq%3DSR%2BO9-H2-4FgaRj3un38ZTj773_LaykUBBQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
