Somewhere in the documentation I took the literal text 'PICO' as the only valid board name in the list of available boards. 'PICO_R1_3.py' is a filename. Subtle difference, but I'm following the documentation verbatim. Just can't find that location on github right now, but will post when I stumble across it.
So, no this error doesn't explain what may be intuitive to you.
'Isn't arm-none-eabi-gcc: Command not found message in plain English?'
I guess it comes with experience:
'Experience is what you get when you dont get what you wanted!'
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Sat 2021.09.25 - 11:49am CST
Somewhere in the documentation I took the literal text 'PICO' as the only valid board name in the list of available boards. 'PICO_R1_3.py' is a filename. Subtle difference, but I'm following the documentation verbatim. Just can't find that location on github right now, but will post when I stumble across it.
So, no this error doesn't explain what may be intuitive to you.
I guess it comes with experience: