BlueSCSI v2 won't appear as USB device in linux.

[funniman-exe]

I'm trying to update the firmware of my BlueSCSI v2. According to the documentation, I am supposed to plug it into my computer with a Micro-USB cable, holding down the BOOTSEL button. The first two times I did this, linux would pretend the device didn't exist for about 45 seconds, before detecting it, then immediately stating it had been disconnected. Every subsequent attempt has resulted in linux not detecting the device at all. There are no logs in dmesg mentioning the device, nothing has been written to the sd card by the BlueSCSI, and picotool also fails to detect the device.

I have no clue what could be happening here, and it would be greatly appreciated if someone could help me.

[funniman-exe]

Update: I decided to put a hard drive image on the sd card, and boot my Mac SE with it connected. The Macintosh SE detects the hard drive image, and finally a log file is generated, but the BlueSCSI still doesn't update firmware off the SD card, and still doesn't show up in linux when in BOOTSEL mode.

[erichelgeson]

I'm using Linux as my primary device, no issues with it finding the uf2 bootloader provided by the Pico itself. SD Updates will depend on if you already had the firmware with the SD bootloader present. Please provide more details on what version you are coming from, what linux you're using, what lsusb says, any dmsg's, etc. Try a different cable, do not use a usb hub, try a different computer to rule it out.

[funniman-exe]

I am using Fedora Linux 44 (KDE Plasma Edition) with x86_64 architecture. I don't know the current firmware version of the BlueSCSI (I bought it through Tots Retro, pre-assembled). I've tried two different usb cables, both of which show the same behaviour: When holding down the BOOTSEL button, the activity light turns on solid and never turns off, otherwise it turns on for about half a second then the BlueSCSI boots normally (notably, it does not present the SD card as a usb mass storage device, but that could be because I'm not using a custom bluescsi.ini file). lsusb and dmsg don't see the device at all. I unfortunately don't have another computer on hand, and I am not using a usb hub. I suspect it may be the cables, since in my experience micro-usb cables for whatever reason are very finicky and unstable.