First issue is that the Pico 2 LED is actually active-high, not active-low - although that just means your bootsel activity LED will be inverted
The main issue is that due to Errata E3 in the datasheet, the Arm USB Bootloader (which runs in Non-Secure mode) doesn't have the correct permissions to access the bootsel activity LED pads registers, so cannot configure it correctly. The activity LED will work when booted in Risc-V (eg `picotool reboot -u -c riscv`), but when booted in Arm it won't work.
The main issue is that due to Errata E3 in the datasheet, the Arm USB Bootloader (which runs in Non-Secure mode) doesn't have the correct permissions to access the bootsel activity LED pads registers, so cannot configure it correctly. The activity LED will work when booted in Risc-V (eg `picotool reboot -u -c riscv`), but when booted in Arm it won't work.
Picotool should automatically use ECC when you write an ECC row, so this shouldn't be an issue - I've just double checked, and the command used does correctly set the ECC bits for me (using picotool 2.1.0).Maybe you didn't use ECC, which is required.
Statistics: Posted by will-v-pi — Thu Dec 12, 2024 4:03 pm