**** BEGIN LOGGING AT Tue Aug 23 02:59:58 2016
Aug 23 04:34:14 <pabs3> http://www.zdnet.com/article/apple-samsung-capture-all-of-industrys-smartphone-profits/
Aug 23 05:37:25 <stdint> the original hardware is that
Aug 23 05:38:09 <stdint> DP+ DP- connected. USB_DRVBUS connect USB_VBUS at usb port plug
Aug 23 05:38:16 <stdint> DP+ DP- connected. USB_DRVBUS connect to USB_VBUS at usb port plug
Aug 23 05:39:34 <stdint> but in peripheral mode, DP+ DP- should connect to USB port plugin, USB_VBUS(the other pin in am3358, not the USB_DRVBUS) should connect to port
Aug 23 05:40:05 <stdint> which is left connected before while USB_DRVBUS should connected to nothing
Aug 23 05:40:29 <stdint> once I make the hardware connection correct, it could work at hi-speed mode
Aug 23 16:49:33 <DocScrutinizer05> err
Aug 23 16:53:00 <DocScrutinizer05> never heard of any "mux" or switching needed in VBUS. You typically got a logical pin for the HNP etc related to USB data at large, and then VBUS also (often) connects to a combined step-down converter/chargepump for charging battery (in device mode) or providing 100mA (or more) to VBUS in host mode
Aug 23 16:53:52 <DocScrutinizer05> or (like in e.g. GTA02) those two functions are implemented with separate dedicated chips, in which case you should make sure they are mutually exlusive
Aug 23 16:54:48 <DocScrutinizer05> TWL5030 has a chargepump implemented, but alsi iirc has a logical signal to control an external chargepump
Aug 23 16:54:58 <DocScrutinizer05> or booster
Aug 24 01:00:17 <stdint> DocScrutinizer05, I don't why VBUS would effect the speed either, but I just write to mail list and got such reply
Aug 24 01:00:28 <stdint> after following that, it works
Aug 24 01:38:10 <DocScrutinizer05> can't comment without knowing the circuit
Aug 24 01:40:20 <DocScrutinizer05> I also can't decode your description above >>in peripheral mode, DP+ DP- should connect to USB port plugin, USB_VBUS(the other pin in am3358, not the USB_DRVBUS) should connect to port<<
Aug 24 01:43:51 <DocScrutinizer05> http://processors.wiki.ti.com/index.php/AM335x_Schematic_Checklist#USB
Aug 24 01:49:32 <DocScrutinizer05> so basically what I said above: USB_VBUS is an imput pin and should always be connected to USB jack. USB_DRVVBUS is an output that enables the power supply for VBUS. USB_CE is to enable charging in peripheral mode. USB_DRVVBUS and USB_CE are mutually exclusive, since you never want to charge the device from a voltage on VBUS that is provided by the device itself
Aug 24 01:51:02 <DocScrutinizer05> you can't connect USB_DRVVBUS directly to VBUS, it's just a logic signal to enable the VBUS power supply
Aug 24 01:51:32 <DocScrutinizer05> >>USB_DRVBUS connect to USB_VBUS<< doesn't work
**** ENDING LOGGING AT Wed Aug 24 02:59:58 2016