Unable to mount board when connected and in Bootloader mode

[sam-lev]

Hi All,

I was hoping to gain some clarity on how to find the connected drive for the Sensor Watch Pro once in bootloader mode. I am able to enter bootloader mode (pulsing red), and I have tried multiple micro usb micro B cables and four separate computers with four separate operating systems: one Mac running Monterey, another Mac running Sonoma, one System76 running Ubuntu, and a Raspberry Pi 5 using the stock OS, so Debian. In all cases, when the Sensor Watch is plugged in I am able to get the light on the board to pulse red after double clicking the reset button. Despite the board being in bootloader mode I am unable to find any connected drives on my machines. Do you have any idea why this might be or ideas on what I should do?

Thanks for any help or clarity you can offer!

Best,
Sam

[wryun]

I know you've tried four cables, but it's usually the micro-usb data lines not being connected. Have you used those cables for other purposes (e.g. connect an old phone and make sure it shows up)?

In Linux, you can check the kernel logs (i.e. journalctl or dmesg) to see if anything is showing up when you plug it in. In non-bootloader mode, it should show up as a serial device.

[xophos-commits]

I have a similar problem. The drive shows, but i can't access it.
dmesg says this: [ 1395.411897] usb 3-2: new full-speed USB device number 21 using xhci_hcd
[ 1395.570706] usb 3-2: New USB device found, idVendor=1209, idProduct=2150, bcdDevice=42.01
[ 1395.570721] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1395.570728] usb 3-2: Product: Sensor Watch Lite
[ 1395.570734] usb 3-2: Manufacturer: Oddly Specific Objects
[ 1395.570739] usb 3-2: SerialNumber: 33C141C25154524C37202020FF112D04
[ 1395.741073] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[ 1395.741652] usb-storage 3-2:1.2: USB Mass Storage device detected
[ 1395.742276] scsi host0: usb-storage 3-2:1.2
[ 1395.749859] hid-generic 0003:1209:2150.000E: hiddev97,hidraw4: USB HID v1.00 Device [Oddly Specific Objects Sensor Watch Lite] on usb-0000:04:00.4-2/input3
[ 1396.777515] scsi 0:0:0:0: Direct-Access Sensor W atch Lite 1.00 PQ: 0 ANSI: 2
[ 1396.778354] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1396.779475] sd 0:0:0:0: [sda] 16000 512-byte logical blocks: (8.19 MB/7.81 MiB)
[ 1396.779709] sd 0:0:0:0: [sda] Write Protect is off
[ 1396.779720] sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00
[ 1396.779905] sd 0:0:0:0: [sda] No Caching mode page found
[ 1396.779910] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 1396.813991] sda:
[ 1396.814055] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 1404.216808] usb 3-2: reset full-speed USB device number 21 using xhci_hcd
[ 1404.543774] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[ 1434.873349] usb 3-2: reset full-speed USB device number 21 using xhci_hcd
[ 1435.200376] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[ 1455.194923] usb 3-2: USB disconnect, device number 21
[ 1455.202526] sda: detected capacity change from 16000 to 0
[ 1455.506774] usb 3-2: new full-speed USB device number 22 using xhci_hcd
[ 1455.657161] usb 3-2: New USB device found, idVendor=1209, idProduct=2151, bcdDevice= 1.00
[ 1455.657175] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1455.657182] usb 3-2: Product: Sensor Watch
[ 1455.657187] usb 3-2: Manufacturer: Oddly Specific Objects
[ 1455.657193] usb 3-2: SerialNumber: 33C141C25154524C37202020FF112D0
[ 1455.696152] cdc_acm 3-2:1.0: ttyACM0: USB ACM device

[xophos-commits]

it seems to reset twice before the led stops to slow-blink again after a minute.

[xophos-commits]

I tried with different cables and different computers.

[wryun]

This is a different problem, as your device is being correctly detected by the OS but then disappears. This usually happens on Linux because you're running some daemon which tries to interact with the disk (and since it's a fake disk, any interaction can stop it). This is usually fwupd; try:

sudo systemctl stop fwupd

and see if that helps.