I think I’m going to have to confess myself defeated for the moment by badger and thonny. With badger2040 USB type C connected into my laptop (running Ubuntu 22.04.1) I get the Clock/Fonts/eBook screen. The LED is illuminated.
Holding down badger’s boot button and pressing its reset button attaches badger as a storage device RPI-RP2. I’ve downloaded the latest pimoroni-badger2040-v1.19.6-micropython.uf2 and I copy this across to the root of RPI-RP2 and hit the badger’s boot button. The RPI-RP2 drive disconnects (as expected) and I’m left with badger’s Clock/Fonts/eBook screen and the illuminated LED.
Expected behaviour: Badger’s a b and c buttons should take me into Clock, Fonts, eBook respectively. Actual behaviour: the buttons do nothing. Pressing the reset button switches off the LED but on release there’s no change of state. Power-cycling: same result.
Holding down the boot button and pressing the reset button puts the badger back into storage mode and RPI-RP2 reappears as a drive.
USING BADGER OS
You can navigate around the launcher using the up and down arrows, and select an example by pressing A, B, or C. To return to the launcher when you’re done with an example, press buttons A and C at the same time.
Hold BOOT whilst pressing up or down to adjust the font size, or hold BOOT whilst pressing A to toggle dark mode
None of this does anything. Badger’s buttons remain inert. I’ve tried
connecting with thonny but:
Unable to connect to /dev/ttyACM0: [Errno 13] could not open port /dev/ttyACM0: [Errno 13] Permission denied: '/dev/ttyACM0' Try adding yourself to the 'nfsnobody' group: > sudo usermod -a -G nfsnobody <username> (NB! You may need to reboot your system after this!) Backend terminated or disconnected. Use 'Stop/Restart' to restart.
I can’t make any sense of the nfsnobody instruction. Presumably it applies to badger’s operating system (the nfsnobody group is unknown by Ubuntu) but the thonny display area marked “shell” seems not to accept commands.
Helpful suggestions would be very welcome.