Comms error after flashing Seeds Studio XIAO ESP32-S3

[dakent22]

Help required installing nanoFramework on the Seeds Studio XIAO ESP32-S3.

The flashing process appears to run ok but when I restart the device there are serial comms errors as shown below. Interestingly the port number also changes from port 5 to 6. If I restart the device back to boot mode then the comms port changes back to 5 and i can flash the device again. I get the same result for firmware targets ESP32_S3, ESP32_S3_BLE and ESP32_S3_ALL. I have tried this from two computers and get the same result.

nanoff --target ESP32_S3 --update  --serialport COM5

.NET nanoFramework Firmware Flasher v2.5.126+716b21797a
Copyright (C) 2019 .NET Foundation and nanoFramework project contributors


Reading details from chip...OK

Connected to:
ESP32-S3 (ESP32-S3 (QFN56) (revision v0.2))
Features WiFi, BLE, Embedded PSRAM 8MB (AP_3v3)
Flash size 8MB GD25Q64 from GIGADEVICE (manufacturer 0x200 device 0x16407)
PSRAM: 8MB
Crystal 40MHz
MAC F0:9E:9E:3B:E0:7C

Extracting ESP32_S3-1.12.4.216.zip...OK

Updating to 1.12.4.216

Erasing flash...OK
Flashing firmware...
Flashing firmware...OK                                                                                                                                

nanoff --devicedetails --serialport COM6
.NET nanoFramework Firmware Flasher v2.5.126+716b21797a
Copyright (C) 2019 .NET Foundation and nanoFramework project contributors


Reading details from chip...Error E4000: Error executing esptool command. (esptool.py v4.8.1
Serial port COM6
Connecting......................................

A fatal error occurred: Failed to connect to Espressif device: Invalid head of packet (0x4E): Possible serial noise or corruption.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html

If I switch to the Arduino IDE, I get the following results in the Serial Monitor after reset. If I put into boot mode then I can successfully flash the Arduino Blink example to the device which runs as expected.

NFPKTV1��� 8   AssemblyRef    =        0 bytes (       0 elements)
NFPKTV1��� 8   TypeRef        =        0 bytes (       0 elements)
NFPKTV1��� 8   FieldRef       =        0 bytes (       0 elements)
NFPKTV1��� 8   MethodRef      =        0 bytes (       0 elements)
NFPKTV1��� 8   TypeDef        =        0 bytes (       0 elements)
NFPKTV1�	� 8   FieldDef       =        0 bytes (       0 elements)
NFPKTV1�
� 8   MethodDef      =        0 bytes (       0 elements)
NFPKTV1��� 8   StaticFields   =        0 bytes (       0 elements)
NFPKTV1�� �
NFPKTV1�
� $   DebuggingInfo  =        0 bytes
NFPKTV1��� �
NFPKTV1��� 9   Attributes      =        0 bytes (       0 elements)
NFPKTV1��