you can also enjoy that deep search yourself , it is the basic sample from here

https://github.com/sqfmi/Watchy/tree/master/examples/WatchFaces/7_SEG

hours and hours of deep, deep , DEEP search

output from Arduino IDE

deep search started

actually my code was based on the same sample and it compiles

Simon@Visual Micro wrote on Feb 18^th, 2025 at 8:47am:


no, my code compiles, sample - not

but my code is based on that sample

Quote:

That should not be an issue, my example is also a copy which has been placed in the Documents\Arduino\My Examples folder.

I'll update as soon as I understand the differences causing the example not to compile.

So I added the sources manually 

Project compiles

In serial debug mode it writes the messages but the connection disappears within about 3 seconds so it even does not write all the messages while continuing to execute code, like I hear the buzz but do not have the messages about it because connection already out.

So it sleeps, then on button press it activates the USB connection only for short time. If VS connects to it then it gets activation reason 0 and so decides to reset, draws the deal and during this process it writes some messages to serial.

Then I compiled in hardware debug mode. The compile output is attached. So no more messages to serial. Again it wakes up on button press and makes USB connection for short time.

If I press "Attach to process" then I get the message box 

Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run. Try "help target".

also in output

=thread-group-added,id="i1"
Reading symbols from .elf...
+echo vMicro: Hardware Debugging
vMicro: Hardware Debugging+echo vMicro: debug.tool = esps3usb\n
vMicro: debug.tool = esps3usb
+set mi-async on
=cmd-param-changed,param="mi-async",value="on"
+set remotetimeout 5
=cmd-param-changed,param="remotetimeout",value="5"
+set logging file _DebugGDB.log
=cmd-param-changed,param="logging p32s3\\Debug/7_SEG.ino_DebugGDB.log"
+set logging overwrite on
=cmd-param-changed,param="logging overwrite",value="on"
+set logging off
+set logging on
+echo vMicro: Initializing remote target...\n
vMicro: Initializing remote target...
+echo Running Setup Actions\n
Running Setup Actions
+target extended-remote | " -d2 -c "gdb_port pipe; telnet_port disabled" -c "adapter_khz 5000" -l no_DebugOpenOCD.log}" -s ts/" -c "set ESP_FLASH_SIZE 0" -f ts/interface/../board/esp32s3-builtin.cfg" -c "set ESP32_RTOS none" -c "init; reset halt"
=cmd-param-changed,param="pagination",value="off"
The program '' has exited with code 42 (0x2a).

Simon@Visual Micro wrote on Feb 24^th, 2025 at 4:06pm:


deep search started 18:58   

uploaded 19:15 

I walk in the Watchy menu, during this time it is active and 
connected by USB, I press "Attach to process" and get 

Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.  Try "help target".

output

=thread-group-added,id="i1"
Reading symbols from .elf...
+echo vMicro: Hardware Debugging
vMicro: Hardware Debugging+echo vMicro: debug.tool = esps3usb\n
vMicro: debug.tool = esps3usb
+set mi-async on
=cmd-param-changed,param="mi-async",value="on"
+set remotetimeout 5
=cmd-param-changed,param="remotetimeout",value="5"
+set logging file _DebugGDB.log
=cmd-param-changed,param="logging p32s3\\Debug/7_SEG.ino_DebugGDB.log"
+set logging overwrite on
=cmd-param-changed,param="logging overwrite",value="on"
+set logging off
+set logging on
+echo vMicro: Initializing remote target...\n
vMicro: Initializing remote target...
+echo Running Setup Actions\n
Running Setup Actions
+target extended-remote | " -d2 -c "gdb_port pipe; telnet_port disabled" -c "adapter_khz 5000" -l no_DebugOpenOCD.log}" -s ts/" -c "set ESP_FLASH_SIZE 0" -f ts/interface/../board/esp32s3-builtin.cfg" -c "set ESP32_RTOS none" -c "init; reset halt"
=cmd-param-changed,param="pagination",value="off"
The program '' has exited with code 42 (0x2a).