The board definition boards/seeed-xiao-s3.json sets -DARDUINO_USB_MODE=0 while also declaring use_1200bps_touch: true. With mode 0 the 1200-baud touch is an application-level TinyUSB feature that dies with the app, so it can never fire. Was mode 0 chosen deliberately for this board, and if so, what depends on it? Building with ARDUINO_USB_MODE=1 fixes unreliable CLI config writes and button-free download-mode entry in my testing, but I don't want to propose that if it breaks something I can't see.
The board definition boards/seeed-xiao-s3.json sets -DARDUINO_USB_MODE=0 while also declaring use_1200bps_touch: true. With mode 0 the 1200-baud touch is an application-level TinyUSB feature that dies with the app, so it can never fire. Was mode 0 chosen deliberately for this board, and if so, what depends on it? Building with ARDUINO_USB_MODE=1 fixes unreliable CLI config writes and button-free download-mode entry in my testing, but I don't want to propose that if it breaks something I can't see.