Crickit is Adafruit’s Creative Robotics & Interactive Construction Kit. It’s an add-on to popular Feather ecosystem boards that lets you #MakeRobotFriend using CircuitPython.
Plug in any Feather mainboard you want into the center, and you’re good to go! The Crickit is powered by seesaw, an I2C-to-whatever bridge firmware. So you only need to use two I2C data pins to control the huge number of inputs and outputs on the Crickit. All those timers, PWMs, sensors are offloaded to the co-processor.
The only thing that is not managed by seesaw is the audio output. Provided is a small jumper you can solder to connect the audio amplifier to the first analog pin. On Feather M0’s this is a true analog output (DAC) and you can play audio clips with CircuitPython. Other Feathers may not have a DAC! In that case, you can solder a wire to jumper the audio amp to a PWM pin.
You get to use all the non-I2C signal pins on your feather and get a boat-load of extra in/out pins, motor controllers, capacitive touch sensors, a NeoPixel driver and amplified speaker output. It complements & extends your Feather so you can still use all the goodies, including stacking FeatherWings on top. But now you have a robotics playground as well.
All are powered via 5V DC, so you can use any 5V-powered servos, DC motors, steppers, solenoids, relays etc. To keep things simple and safe, we don’t support mixing voltages, so only 5V, not for use with 9V or 12V robotic components.
Have some info to add for this board? Edit the source for this page here.
This is the latest stable release of CircuitPython that will work with the Feather M0 Express + Crickit.
Start here if you are new to CircuitPython.
This is the latest unstable release of CircuitPython that will work with the Feather M0 Express + Crickit.
Unstable builds have the latest features but are more likely to have critical bugs.
Every time we commit new code to CircuitPython we automatically build binaries for each board and language. The binaries are stored on Amazon S3, organized by board, and then by language. Try them if you want the absolute latest and are feeling daring or want to see if a problem has been fixed.
All previous releases are listed on GitHub, with release notes, and are available for download from Amazon S3. They are handy for testing, but otherwise we recommend using the latest stable release. Some older GitHub release pages include the same binaries for downloading. But we have discontinued including binaries as assets on newer release pages because of the large number of files for each release.