And, for an RP2 in BOOTSEL mode, for me ...So it should be possible to put an RP2 into BOOTSEL mode, figure out what device it is, scan the '.uf2' to figure out what device or devices it will upload to, whether the device being uploaded to will accept it or just ignore it.
Which would have saved me over half an hour of trying to figure out why uploading a '.uf2' wasn't exhibiting the behaviour I expected it to.
That was resolved when the lightbulb came on and I finally twigged "it's as if the upload is being completely ignored".
It would have been resolved a whole lot sooner if 'picotool' had reported "that ain't going to work, sunshine".
Luckily I use an application which wraps 'picotool' to do my interactions with RP2 devices so I have been able to update that to do it myself.
Another option is to scan 'dmesg' to find the info for it having entered BOOTSEL mode, upload, see if it has changed USB state, disconnected itself. If not there's a good chance the upload has been ignored and that can be reported.
Code:
pi@Pi4B:~ $ picotool info -dDevice Information type: RP2040 flash size: 2048K flash id: 0xE6614104031D892FWhich would have saved me over half an hour of trying to figure out why uploading a '.uf2' wasn't exhibiting the behaviour I expected it to.
That was resolved when the lightbulb came on and I finally twigged "it's as if the upload is being completely ignored".
It would have been resolved a whole lot sooner if 'picotool' had reported "that ain't going to work, sunshine".
Luckily I use an application which wraps 'picotool' to do my interactions with RP2 devices so I have been able to update that to do it myself.
Another option is to scan 'dmesg' to find the info for it having entered BOOTSEL mode, upload, see if it has changed USB state, disconnected itself. If not there's a good chance the upload has been ignored and that can be reported.
Statistics: Posted by hippy — Tue Dec 31, 2024 7:12 pm