Unable to load on pico clones

[mafteialbert]

I have a marble pico , and as far as I can tell, this implementation of the RP2040 has something wrong with the way it reports the serial number(I get garbled data everytime I try to load a program). Thanks to that, the serial number filtering the picotool does during a load -f can't find the pico again, so I'm unable to use that method to load the file, even tho it reboots in bootsel mode.

picotool load pico_micro_ros_example.uf2 -F --vid 11914

��� for reboot
The device was asked to reboot into BOOTSEL mode so the command can be executed.
Waiting for device to reboot.........

Despite the reboot attempt, no accessible RP-series devices in BOOTSEL mode were found found with serial number �
���. It is possible the device is not responding, and will have to be manually entered into BOOTSEL mode.

[mafteialbert]

Fixed, turned out if the pico has an app flashed that disables usb, the serial number is garbled

[lurch]

I'll re-open this, as IMHO picotool ought to "detect" garbled serial numbers, and not echo them out to the user's terminal.

[mafteialbert]

Adding on this, this seems to happen when a fault occurs on the pico(I'm setting up to read some encoders and somewhere the pico is hanging)

[will-v-pi]

I'll re-open this, as IMHO picotool ought to "detect" garbled serial numbers, and not echo them out to the user's terminal.

Note that a serial number is permitted to be any ASCII string, and can be modified on RP2350 using white-labelling - so you could choose to use a garbled serial number for your RP2350, and it would be valid.

[lurch]

I'll re-open this, as IMHO picotool ought to "detect" garbled serial numbers, and not echo them out to the user's terminal.

Note that a serial number is permitted to be any ASCII string, and can be modified on RP2350 using white-labelling - so you could choose to use a garbled serial number for your RP2350, and it would be valid.

Fair enough. But any idea why the OP is getting a garbled serial number on RP2040? (I'd expect it to either get a normal serial-number, or no serial-number at all?) Please close this issue again @will-v-pi if I was mistaken, and there's not really anything that picotool can do here.

[will-v-pi]

My guess would be that the firmware is reporting the serial number differently than the bootrom does - for example treating it as raw hex numbers and writing that out (giving garbled characters), rather than converting it to a hex string