If OTG is unsupported, how should USB0_ID be connected? Can it be left floatinng (i.e. Is there an internal pullup)?
If you are using USB0 in BF70x as peripheral/device then USB0_ID pin should be left floating. There is a internal pull-up but and it is enabled only for short period during start up, but the final state of this pin is Tri-State.
Reviving this old question. In the current case, we are using a USB-C connector, so will be driving the ID pin low by an external GPIO when in host mode (no ID pin on USB-C connector). In other cases, I believe this pin needs to float up to VDD_USB.
1) What is Vih for the VDD_USB domain, USB_ID specifically, if it were to be actively driven high.
2) If not, does this pin need an external pull to VDD_USB if OTG is supported? You say the internal pull is "enabled only for short period during start up".
The programming reference says: "VBUS is always supplied by the A device on the bus. The USB controller determines whether it is the A device or the B device by sampling the USB_ID input from the PHY. This signal is pulled low when an A- type plug is sensed (signifying that the USB controller is the A device), but the input is taken high when a B-type plug is sensed (signifying that the USB controller is the B device)." These two statements seem to contradict eachother. Please confirm whether the BF reenables it's internal pullup, or if an external pull is required, or if active drive is allowed by a GPIO, what the Vih is.
Retrieving data ...