Troubleshooting Guide¶
If you’re experiencing problems with your CodeAIR, don’t panic! Following the steps below will resolve most common issues.
Reboot and Reload¶
If CodeAIR doesn’t seem to be responding to CodeSpace, try the following sequence:
Unplug the USB cable.
Click Chrome’s Reload button.
Plug the USB cable back in.
Test CodeAIR with a simple “known good” Python program - hopefully you’re back in business!
Reformat CodeAIR’s Filesystem¶
Your Python code is written to files on CodeAIR’s CircuitPython file-system.
It is possible to write code that disables the USB connection immediately at bootup, which makes it difficult to recover using CodeSpace!
If power is lost while writing to files they can become corrupted, so you need a way to wipe the slate clean…
To re-format the file system:
Press and hold button B1 and keep holding it down…
Briefly press the RST button.
Keep holding button B1, you will hear a short two-tone beep - KEEP HOLDING until you hear five quick beeps.
You may now release B1. Your CodeAIR should restart and be running the restored factory default code (blue LEDs cycling, waiting to pair).
Firmware Update¶
CodeAIR’s firmware is the Operating System code that includes the Python language, and all the low-level APIs you use to access the hardware. Doing a firmware update takes less than a minute, and it completely replaces the contents of the onboard FLASH memory with factory-fresh code.
Note: Under normal circumstances, CodeSpace will prompt you when there’s a newer version of firmware available for CodeAIR. Every time you connect it, CodeSpace confirms it’s running the latest version.