UART-Rx-Tx (Serial and Serial0) and Native USB (HWCDC and USBCDC) monitor capture

[sivar2311]

@t_magdahl

If I attempt to upload under this condittion I get an error (I will copy two sequential upload attempts one with upload_port = COM34 in the INI file [obviously fails because it does not exists] and the next one with upload_port = COM36, that does exist)

@t_magdahl

Second UPLOAD attempt on COM36 (TinyUSB). Seems to me that TinyUSB is not good for UPLOAD.

True, as I wrote above!

The TinyUSB interface cannot be used for uploading (and debugging to answer your next question beforehand).

@t_magdahl

If I reset the Kit with its two buttons COM36 (TinyUSB) mutates to COM34 (JTAG Interface 0). Under these condittions UPLOAD works fine.

True again, as I wrote above.
The ESP32 is now in upload mode and awaiting new firmware to be uploaded.

@t_magdahl

Now from one of your previous posts I understant I might need to reset the Kit after UPLOAD finishes?,

True, otherwise the ESP will stay in upload mode.

@t_magdahl

But in my case after an upload success and manual reset my COM34 stays as COM34 which seems to be odd.

That’s strange! A single press to RESET should result in a reset of your ESP32 !?
Don’t hold the BOOT Button pressed! Otherwise the ESP32 will again enter upload mode.

@t_magdahl

Instead of manual resetting after upload I will do the reset by unplugging the USB cable which will make it change from COM34 (your COM12) to COM36 (your COM13).

In result this is a RESET of the ESP32.

@t_magdahl

I do have output now, but missed a lot of the first prints due to the USB cable disconnect and because the still open Serial Monitor will not reconnect and I have to kill it and launch it again.

Great! The Serial Monitor (VS Code Extension) offers automatic reconnection:

This will minimize your loss of the first lines.

For some (unknown) reason, my COM13 (TinyUSB) is not shown correctly. It is statet as "USB JTAG/serial debung unit. While running ZADIG this is shown correctly:

@t_magdahl

I am not 100% sure but this cable disconnect might generate a big mess when trying to debug?

As written above, TinyUSB cannot be used for debugging. This is only available via HWUSB (ARDUINO_USB_MODE=1) which will result in a single COM (COM 12 in my case) and shown correctly in Zadig as follow:

@t_magdahl

So it seems it will be impossible to inspect the Serial CDC output while debugging under these terms?

Yes, as written above, TinyUSB cannot be used for debugging.