Closed SolidStateLEDLighting closed 6 months ago
I just noticed some improvement by moving my USB input line away from "USB" over to the other USB input that is labeled "COM". This registered another serial port in my system -- and I moved my IDE to it.
The program behavior is pretty much normal now when I awake from light sleep.
So, evidently I have been getting my serial out through the USB previously (GPIO pins 19 and 20) and now I'm getting the I/O through the normal expected default Tx/Rx serial port which is buffered in the USB to UART bridge chip (CH343).
Any ideas on why the native USB port (GPIO pins 19 and 20) remain inoperative after light sleep? Is there a command that stimulates that port back into service?
It is confirmed now -- everything works exactly as expected on the real physical serial port UART0 (pins 36 and 37 for this S3).
Can anyone shed some light on why the USB output dies on light sleep? Is there any restore call that might bring that USB serial output back after sleep?
Got the same issue. This is solved by switching from the micro USB port "USB" to the other micro USB port labeled "UART"
Answers checklist.
IDF version.
5.2
Espressif SoC revision.
ESP32S3
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
DevKitC
Power Supply used.
USB
What is the expected behavior?
The process of going to light sleep and waking up again IS WORKING -- but it disables my serial port output in the IDE.
The example code doesn't indicate that the serial port would be disabled. And it doesn't indicate that I need to restart it.
I never start the seral port manually in my IDF builds. Can someone point me in a direction where I can get the commands to manually reset/restart the serial port?
What is the actual behavior?
When I have this issue, I can depress the reset button on the unit and then I see:
None (written in red) Waiting for the device to reconnect (written in yellow)