Troubleshooting

Erase the Filesystem

If your board has a filesystem problem, you can clean things up by wiping the QSPI. Download the file linked here, then plug in your M4SK and double-click the reset button. You'll see a M4SKM4BOOT drive show up on your computer. Drag the M4SK_QSPI_Eraser.UF2 onto that drive. After a few moments, the board's drive will disconnect. Double-click reset to put the board back into bootloader mode.

You will now need to go back to this page and follow the instructions for prepping the board's filesystem by putting the CircuitPython .uf2 on it.

Diagnostics

Want to see some stats on your M4SK? Double-click the board's reset button to get to bootloader mode, then drag the M4SK_Diagnostics.UF2 onto the M4SKM4BOOT drive!

Technicolor Snow

If you see one or more of your texture maps show up as multicolored snow/noise, it may be an indication that you've run out of texture memory and will need to reduce the file size of some of your maps.

If the entire screen is snow, it usually means you’ve run out of RAM, and the most likely culprit there is the eyeRadius setting. Larger eyes require geometrically more RAM. Dial it back until everything fits.

Ol’ Blue Eyes

If the eyes used to work but after editing have reverted to flat-colored blue irises, that’s almost always a JSON syntax error…usually a missing or extra comma. The “Customization Basics” page has more tips for ensuring proper syntax.

Crossed Eyes

Occasionally the eyes might go crossed and stay that way. The software thinks the “nose booper” is being held and this is its attempt at being funny.

This false booping can happen when the battery is running low and its voltage starts to drop.

Occasionally though…it just gets a false reading, maybe due to gradual changes in temperature, humidity or other unknown factors. Tap the reset button (or toggle power off and on) and this should clear up…the booper calibrates it’s un-booped state on start-up.

This guide was first published on Aug 20, 2019. It was last updated on Aug 20, 2019. This page (Troubleshooting) was last updated on Mar 13, 2020.