I'm having repeated issues programming some Trinket M0s with Arduino. In all cases the code compiles (with the output below) then seemingly uploads successfully.
Code: Select all
/Users/xxxx/Library/Arduino15/packages/adafruit/tools/arm-none-eabi-gcc/9-2019q4/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: warning: changing start of section .bss by 12 bytes
/Users/xxxx/Library/Arduino15/packages/adafruit/tools/arm-none-eabi-gcc/9-2019q4/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: warning: changing start of section .bss by 12 bytes
/Users/xxxx/Library/Arduino15/packages/adafruit/tools/arm-none-eabi-gcc/9-2019q4/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: warning: changing start of section .bss by 12 bytes
/Users/xxxx/Library/Arduino15/packages/adafruit/tools/arm-none-eabi-gcc/9-2019q4/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: warning: changing start of section .bss by 12 bytes
/Users/xxxx/Library/Arduino15/packages/adafruit/tools/arm-none-eabi-gcc/9-2019q4/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-noneSketch uses 42912 bytes (16%) of program storage space. Maximum is 262144 bytes.
-eabi/bin/ld: warning: changing start of section .bss by 12 bytes
Software/upload
I've tried both Arduino IDE v 2.0.1 and Arduino 1.8.19 on both a 2013 MacBook Pro and a 2021 MacBook Pro (both Monterey and Ventura OS). I've updated the UF2 to the latest for this board.
Hardware
To test that the board isn't 'bricked' I've uploaded CircuitPython and verified function. I've had slightly better success with uploading simpler Arduino code (successful compilation/upload/function) to the same boards. I've also tried uploading to a bare Trinket M0 with similar results (intermittent purple LED after reportedly successful upload).
I've attempted to monitor the Serial output to see if there's a place in the code that's causing the issue and it doesn't seem that it even gets to Serial initialization.
Is there anything I can do to investigate further to see what's happening on the hardware that's causing it to lock up? I'm happy to add the code that mostly seems to cause problems (although even simple example scripts seem to have issues as well).