Other Parts Discussed in Thread: LM94022
Device mode works great on EK launch pad with +VBUS/ID input signals. Disconnects windows device client after PWM0/ADC0 start to run full out with duty cycle updates and interrupts occurring.
Changing USB device host buffer 2048kb up to 32kb did not stop client disconnects but one time only. Note +VBUS/ID are being forced high via USB0 GPCS register. Note too there is no USB disconnect status returned when +VBUS/ID are being forced high by software. Lowering the USB0 INT priority has no effect either way to stop client disconnects that occur when PWM0 starts up. Re-establishing the USB device endpoint while PWM0/ADC0 are crunching only lasts a few cycles then disconnects the client.
Any thoughts what could be disconnecting the bulk device client in the above scenario? USB0 shell/shield are connected to PCB edge frame ground via 1Meg/3300pf in parallel. Frame ground is connected to electrical panel bonded ground, located 2' away from PCB and analog ground plane ties into frame ground via similar RC network. USB0 RX/TX differential pair are same length traces located within 1" to MCU inputs and connector has no ground plane foil as TM4C129x design guidelines suggest.