Help Wanted : S3 on Windows 10 - device mgr always shows the S3 as 2 separate JTAG/serial debug units

[rpbgit]

no matter what button sequence try, the S3 always comes up in dev mgr as two "USB JTAG/serial debug unit" devices.

how do i get it to appear as COMn port ???

eventually, want to use one JTAG debug port for debugging/single stepping/breakpoints, and the other as download.

but at this point its rather useless to me. i have two S3's and they behave the same way.

how to correct/fix ?

[rpbgit]

dev environment is Microsoft Visual Code with Platform I/O

[lewisxhe]

Press and hold the BOOT button, do not release it, then press RST, release RST, and finally release BOOT

[rpbgit]

Hi Lewis,

Thanks for the reply...

Did this many times, no joy...

I finally used Zadig to force the USBSER.sys driver to be installed on the first JTAG port, now I have a COM port back.... but even though I see a pile of stuff coming over the serial port, it seems like its simply spinning in circles. And I cannot break out of it by any combination of button reset presses/sequences.

I have two objectives –

1. Get get back to being able to upload code to the S3. I was able to do this ONCE and now it seems like its bricked...
2. Get the jtag debugger working from platform i/o on the second port, which is supposed to work. My understanding is that the JTAG debugger must use libusb?

Maybe I installed the USBSER driver on the wrong port ?

When I connect a term emulator to the port it keeps spinning in this circle... like a WDT or something is expiring. When I hold the reset button, the COM port disappears as one would expect, release it ant it gets enumerated again.

-bob

From: Lewis He @.> Sent: Friday, April 21, 2023 11:37 AM To: Xinyuan-LilyGO/T-Display-S3 @.> Cc: rpbgit @.>; Author @.> Subject: Re: [Xinyuan-LilyGO/T-Display-S3] Help Wanted : S3 on Windows 10 - device mgr always shows the S3 as 2 separate JTAG/serial debug units (Issue #141)

Press and hold the BOOT button, do not release it, then press RST, release RST, and finally release BOOT

— Reply to this email directly, view it on GitHub https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/141#issuecomment-1518078743 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACE2IUQ3DCBNZEAY32UG2GDXCKZRNANCNFSM6AAAAAAXE4JARM . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ACE2IUSIEOBJE4ZMA3FZBHTXCKZRNA5CNFSM6AAAAAAXE4JAROWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS2PQFRO.gif Message ID: @. @.> >

[rpbgit]

this is the loop the S3 seems stuck in when connected to the COM port

[lewisxhe]

I have not used the jata function of esp32s3, please refer to the official guide for specific usage. https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/jtag-debugging/index.html It can be seen from the output log that the chip is abnormal. It may be that the program is abnormal and causes infinite restarts. You can flash the factory firmware to check whether the chip can work normally. https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/firmware

[369Martin369]

I encountered this problem once too....no problem. get your IDE settings right. Put the S3 into "waiting for download" position. And flash with correct IDE settings which will switch of USB behaviour.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.