That is exactly what would happen if your UF2 are built for a Pico / RP2040 rather than a Pico 2 / RP235X.
What does 'picotool info -a *.uf2' show ?
Code:
lawrence@whitebox:~/pico/pico-examples/build/hello_world/usb$ cat /etc/debian_version 12.11lawrence@whitebox:~/pico/pico-examples/build/hello_world/usb$ picotool info -a *.uf2File hello_usb.uf2 family ID 'rp2350-arm-s':Program Information name: hello_usb features: USB stdin / stdout binary start: 0x10000000 binary end: 0x10005514 target chip: RP2350 image type: ARM SecureFixed Pin Information noneBuild Information sdk version: 2.2.0 pico_board: pico2_w boot2_name: boot2_w25q080 build date: Sep 6 2025 build attributes: ReleaseMetadata Block 1 address: 0x10000138 next block address: 0x10005500 block type: image def target chip: RP2350 image type: ARM SecureMetadata Block 2 address: 0x10005500 next block address: 0x10000138 block type: ignoredWhat PICO_BOARD are you specifying when building your UF2 ?
Code:
cmake -DPICO_BOARD=pico2_w ..So a summary:
Debian 11 + Pico W = ttyACM0 appears and works
Debian 11 + Pico2 W = ttyACM0 appears and works
Debian 12 + Pico W = ttyACM0 appears and works
Debian 12 + Pico2 W = No ttyACM0
Statistics: Posted by aslak3 — Sun Sep 07, 2025 8:27 am