Thanks for the report.

Can you try disabling the Serial Debugger (set vMicro > Debugger > Debug: Off), or change to the Release Build Configuration, and Build and Upload again?

Quote:

Do you mean the COM Port will not connect, or that it no longer appears?

Also can you confirm if the source for this project is available online for us to test with on a non-Watchy device?

Thanks for the detail and logs.

One option which appears non-default is "USB CDC On Boot" Board Option to "Disabled", and build and upload the code again.

From the user guide it seems the board has to be manually put into bootloader mode using the buttons (to make the COM port appear), and then manually reset to run the firmware.

I was referring to their instructions, which from their GitHub may differ depending on the Hardware version of the product you have.

Quote:


If it doesn't show anything after this, there may be some output in the Serial Monitor if there is an exception in the code, which can be decoded by pressing the [!] button at the bottom.

For debugging further in this scenario the Hardware debugging would be needed, which requires the v3 Hardware.  The ESP32S3 can be debugged via the USB-JTAG Interface as shown below:
https://www.visualmicro.com/page/ESP32S3-USB-Debugging.aspx

Can you confirm if the problem present in the Arduino IDE when uploading the same code?

Quote:

Apologies, do you mean it all works as expected in Arduino IDE?

Quote:

Thanks, this looks different from the version 3 schematic listed in the official repository, and from your initial log you do have an ESP32-S3 chip.
https://watchy.sqfmi.com/docs/hardware

In this case you should not need to wire the USB interface manually, as the pins are already connected to the USB port available on the device.

If you install the Zadig tool and connect the watch to the PC via its usual USB Connection:
https://www.visualmicro.com/page/Zadig-Driver-Installation-Guide.aspx

Then after clicking Options > List All Devices, you can check the WinUSB Driver is installed for Interface2 of the chip as shown in the attached image.

Once that is correct you will be able to follow the rest of the ESP32S3 Page below to setup the Hardware Debugging:
https://www.visualmicro.com/page/ESP32S3-USB-Debugging.aspx

Also it may be worth downgrading the ESP32 Board package in use to 2.0.14 as it has issues with some libraries for Eink displays after this.

If I try to press Debug -> Attach to process

I get the message

Unable to start debugging. Launch options string provided by the project system is invalid. This string is null or empty.

What is it about:

This currenly requires a Local board.txt to function at its best

?

Where is that board.txt and whether I need to do anything with it ?

Tip: When you receive a stack trace error like the one posted, you can click the [!] button at the bottom of the Serial Monitor to decode the error and show the methods/files which led to it in the output window. Clicking these will take you to the relevant code.  This may be useful for when your board restarts, 

There are also reason codes within the output when the board resets which explain why it has done so:
e.g. rst:0xc (RTC_SW_CPU_RST),boot:0x2b (SPI_FAST_FLASH_BOOT)
Espressif Documentation: https://docs.espressif.com/projects/esptool/en/latest/esp32s3/advanced-topics/bo...
Quote:


This is related to the DTR/RTS signals which can be altered at the bottom of the Serial Monitor. If you disable DTR it should no longer reset the board when connecting the Serial Monitor (this setting is per-session, so needs to be unset again after reloading Visual Studio).

Quote:

The Local board.txt can be added to the project from vMicro > Add Code > Add Local Board.txt.  Then the entries specified on the page can be added in and saved.  They will take effect the next time the debugging session is started from Debug > Attach to Process (if the code has already been uploaded), or Debug > Start (this will build and upload the code and then attach the debugger).

Quote:

This has been the case in the past, however in this scenario with so many libraries involved it should work with just "Default Optimization".



The previous build log didn't include the Watchy library, which I expected to be included for this device.

So we can assist more easily can you ZIP your project (minus the .vs folder) and email it to us (info (at) visualmicro.com) with a link to this thread so we can review?

Also please include the latest buiid output, and any output shown in the Serial Monitor in full as text files?

now I just clicked "upload" again and it again started that idiotic deep search for libraries that is expected to last 15 minutes

Now you can check whether that deep search went right way