# Adafruit Fruit Jam
## Overview
We were catching up on a recent [Hackaday Hackchat with Eben Upton](https://hackaday.io/event/202122-raspberry-pi-hack-chat-with-eben-upton) and learned some fun facts, such as the DVI hack for the RP2040 was inspired by [a device called the IchigoJam](https://www.hackster.io/news/ichigojam-combines-strawberry-and-raspberry-to-deliver-a-raspberry-pi-pico-powered-educational-micro-66aa5d2f6eec). We remember reading about this back when it was an LPC1114. Now it uses an RP2040. Well, we're wrapping up the [Metro RP2350](https://www.adafruit.com/product/6003) and lately we've been joking around that with DVI output and USB Host support via bit-banged PIO, you could sorta build a little stand-alone computer.
Well, one pear-green-tea-fueled-afternoon later we tried our hand at designing a 'credit card sized' computer - that's 3.375" x 2.125", [about the same size as a business card](https://hackaday.com/2024/05/07/the-2024-business-card-challenge-starts-now/) and turns out there's even a standard named for it: [ISO/IEC 7810 ID-1](https://www.iso.org/standard/70483.html).
**With the extra pins of the QFN-80 RP2350B, we're able to jam a ridonkulous amount of hardware into this shape:**
- RP2350B dual 150MHz Cortex M33 microcontroller
- PicoProbe debug port
- 16 MB Flash + 8 MB PSRAM - the PSRAM will help when we want do do things like run emulations that we need to store in fast RAM access, and also let us use the main SRAM as the DVI video buffer.
- USB type C for bootloading/USB client
- Micro SD card with SPI or SDIO
- DVI output on the HSTX port
- I2S stereo headphone + mono speaker via the [TLV320DAC3100](https://www.digikey.com/en/products/detail/texas-instruments/tlv320dac3100irhbt/2353656)
- 2-port USB type A hub for both keyboard and mouse or game controllers
- ESP32-C6 for WiFi / Internet connectivity
- Chunky on-off switch
- Stemma QT I2C
- Stemma classic JST 3-pin
- 5x NeoPixels
- 3x tactile switches
- 2x16 pin socket header with 10 A/D GPIO + 5V/3V/GND power pins.
It's like a mini computer, reminiscent of retro computing of the 70's and 80's: plug in a monitor and keyboard + mouse to make toy programs and applications in CircuitPython, Arduino, or even Pico SDK!
**This mini-kit comes with:**
- Assembled and tested Fruit Jam PCB assembly
- Top plate to protect your board
- 3 x nylon screws to attach the top plate (we don't have a metal standoff next to the ESP32-C6 antenna)
- Mini speaker
- Bumper kit
# Adafruit Fruit Jam
## Pinout
Click diagram for larger resolution images. There is also a PrettyPins [PDF on GitHub](https://github.com/adafruit/Adafruit-Fruit-Jam-PCB/blob/main/Adafruit_Fruit_Jam_PrettyPins.pdf).
## Power Pins and Connections
- **USB C connector** - This is used for power and data. Connect to your computer via a USB C cable to update firmware and edit code.
- **ON LED** - To the right of the USB C connector is the power indicator LED, labeled **ON** on the board silk. When the Fruit Jam is powered, this LED will be lit.
- **GND** - This is the common ground for all power and logic.
- **3V** - These pins are the output from the 3.3V regulator, they can supply 500mA peak.
- **5V** - These pins are the output from the 5V regulator. It can supply up to around 500mA peak.
- **Power Switch** - At the bottom edge of the board is a sliding switch labeled **OFF ON**. This is the power switch for the board.
## Logic Pins
### UART, I2C, and SPI on RP2350
The RP2350 is capable of handling I2C, SPI, and UART on many pins. However, there are really only two peripherals each of I2C, SPI, and UART: I2C0 and I2C1, SPI0 and SPI1, and UART0 and UART1. So while many pins are capable of I2C, SPI, and UART, you can only do two at a time, and only on separate peripherals, 0 and 1. I2C, SPI and UART peripherals are included and numbered below.
### PWM on RP2350B
The RP2350B supports PWM on all pins. However, it is not capable of PWM on all pins at the same time. There are 12 PWM "slices", each with two outputs, A and B. Each pin on the Fruit Jam is assigned a PWM slice and output. For example, A0 is PWM8A, which means it is the first output of the eighth slice. You can have up to 24 PWM objects on this board. The important thing to know is that **you cannot use the same slice and output more than once at the same time**. The PWM slices and outputs are indicated below.
### Analog Pins
The Fruit Jam has six ADCs. These pins are the only pins capable of handling analog, and they can also do digital.
- **A0/GPIO40** - This pin is ADC0. It is also SPI1 MOSI, UART1 TX, I2C0 SDA and PWM8A. It is not broken out on the 2x16 header. It is only available on the JST-PH port, discussed later on this page.
- **A1/GPIO41** - This pin is ADC1. It is also SPI1 CSn, UART1 RX, I2C0 SCL and PWM8B.
- **A2/GPIO42** - This pin is ADC2. It is also SPI1 SCK, UART1 CTS, I2C1 SDA and PWM9A.
- **A3/GPIO43** - This pin is ADC3. It is also SPI1 MOSI, UART1 RTS, I2C1 SCL and PWM9B.
- **A4/GPIO44** - This pin is ADC4. It is also SPI1 MOSI, UART0 TX, I2C0 SDA and PWM10A.
- **A5/GPIO45** - This pin is ADC5. It is also SPI1 CSn, UART0 RX, I2C0 SCL and PWM10B.
### Digital Pins
These are the digital I/O pins. They all have multiple capabilities.
- **D6/GPIO6** - Digital I/O pin 6. It is also SPI0 SCK, UART1 CTS, I2C1 SDA, and PWM3A.
- **D7/GPIO7** - Digital I/O pin 7. It is also SPI0 MOSI, UART1 RTS, I2C1 SCL, and PWM3B.
- **D8/TX/GPIO8** - Digital I/O pin 8 and the main UART1 TX pin for the board. It is also SPI1 MOSI, UART1 TX, I2C0 SDA, and PWM4A. It is used as the TX pin for the ESP32-C6 AirLift.
- **D9/RX/GPIO9** - Digital I/O pin 9 and the main UART1 RX pin for the board. It is also SPI1 CSn, UART1 RX, I2C0 SCL, and PWM4B. It is used as the RX pin for the ESP32-C6 AirLift.
- **D10/GPIO10** - Digital I/O pin 10. It is also SPI1 SCK, UART1 CTS, I2C1 SDA, and PWM5A.
- **SCK/GPIO30** - The main SPI1 SCK. It is also UART0 CTS, I2C1 SDA, and PWM7A.
- **MISO/GPIO28** - The main SPI1 MISO. It is also UART0 RTS, I2C1 SCL, and PWM7B.
- **MOSI/GPIO31** - The main SPI1 MOSI. It is also UART0 TX, I2C0 SDA, and PWM6A.
- **SDA/GPIO20** - The main I2C0 data pin. It is also SPI0 MISO, UART1 TX and PWM2A.
- **SCL/GPIO21** - The main I2C0 clock pin. It is also SPI0 CSn, UART1 RX and PWM2B.
### CircuitPython I2C, SPI, and UART
Note that in CircuitPython, there is a board object each for STEMMA QT, I2C, SPI, and UART that use the connector and pins labeled on the Fruit Jam. You can use these objects to initialize these peripherals in your code.
- `board.STEMMA_I2C()` uses the STEMMA QT connector (in this case, SCL/SDA pins)
- `board.I2C()` uses SCL/SDA pins (GPIO21 and GPIO20)
- `board.SPI()` uses SCK/MO/MI pins (GPIO30, GPIO31 and GPIO28)
- `board.UART()` uses RX/TX pins (GPIO9 and GPIO8)
### Arduino I2C, SPI, and UART
I2C, SPI, and UART can be accessed with these objects in Arduino:
- `Wire` is used for the default I2C and STEMMA QT connector (GPIO21 and GPIO20).
- `SPI` is used for the default SPI pins (GPIO30, GPIO31 and GPIO28).
- `Serial1` is used for the default UART pins (GPIO9 and GPIO8).
The peripheral order is defined in the board support definition for Arduino. For example, you'll notice that even though the default SPI (GPIO30, GPIO31 and GPIO28) is located on SPI1, it is defined as `SPI` rather than `SPI1`.
### RP2350 A2 E9 Erratum
The Adafruit Fruit Jam comes with the A2 version of the RP2350B, [which is affected by the E9 erratum](https://datasheets.raspberrypi.com/rp2350/rp2350-datasheet.pdf#page=1358). This errata affects some uses of GPIO and PIO such as high-impedance inputs and the internal pulldowns. A pin can read as high even when driven or pulled low, if the input signal is high impedance or if an attached pull-down resistor is too weak (has too high a value). You may need to use 8.2K or smaller resistors if pull-downs are required.
## Microcontroller, Flash, and PSRAM
The large square towards the middle is the **RP2350 microcontroller** , the "brains" of this board. It has dual M33 cores with 150 MHz clock rate. It has 520KB of SRAM and 8KB OTP memory, which means that MicroPython and CircuitPython run great, and also IoT projects that need a lot of memory buffer space will run better.
Other features include 3 PIO blocks, a TrustZone secure boot, and a special High Speed Transmit (HSTX) peripheral that drives 4 lanes of differential data transmission such the DVI output onboard without needing to overclock or use PIO.
The square towards the top-middle is the **16 MB** **QSPI Flash**. It is connected to 6 pins that are not brought out on the GPIO pads. It is used for storing files and MicroPython/CircuitPython code storage.
The Fruit Jam comes with **8 MB of PSRAM**. This allows for more storage for things like graphics and audio. Make sure to put your memory hungry assets at the top of your code to have them go into PSRAM to maximize the storage capability on your board.
## ESP32-C6 Co-Processor
The WiFi capability uses an **Espressif ESP32-C6 Wi-Fi coprocessor,** aka the **AirLift,** with TLS/SSL support built-in. Communication is over SPI and it has CircuitPython library support ready to go for fast wireless integration with the following pins:
- **MOSI** pin (`board.MOSI`)
- **MISO** pin (`board.MISO`)
- **SCK** pin (`board.SCK`)
- **CS** pin (`board.ESP_CS`)
- **Interrupt** pin (`board.ESP_IRQ`)
- **Ready/Busy** pin (`board.ESP_BUSY`)
- **Reset** pin (`board.ESP_RESET`, also known as `board.PERIPH_RESET`). This reset pin is shared with the reset pin on the TLV320DAC3100 I2S DAC.
- ESP **RX** / **TX** pins (`board.RX` and `board.TX`) are shared with the RP2350 **RX** / **TX** pins.
- The ESP **ReSeT** pin (used in some serial contexts) is a shared peripheral reset pin on `board.PERIPH_RST` that is also used by the TLV320 I2S DAC.
- The ESP **GPIO9** pin for bootloader enable is connected to `board.BUTTON1`
Warning: Since the ESP32-C6 WiFi co-procesor and the TLV320DAC3100 I2S DAC share a reset pin, you must set up the C6 _first_, and _then_ set up the TLV320DAC3100. Calling `adafruit_esp32spi.ESP_SPIcontrol(...)` will toggle the reset pin and will clear any prior setup done to the TLV320DAC3100.
## DVI HSTX Output
The RP2350 has a new built-in peripheral called the High Speed Transmit (HSTX) peripheral. It can drive 4 lanes of differential data transmission without needing to overclock or use PIO. These pins are connected to the DVI Video port on the Fruit Jam:
- **CKN/GPIO12** - Digital I/O pin 12 and one of the 8 HSTX peripheral pins. It is also SPI1 MOSI, UART0 TX, I2C0 SDA and PWM6A.
- **CKP/GPIO13** - Digital I/O pin 13 and one of the 8 HSTX peripheral pins. It is also SPI1 CSn, UART0 RX, I2C0 SCL and PWM6B.
- **D0N/GPIO14** - Digital I/O pin 14 and one of the 8 HSTX peripheral pins. It is also SPI1 SCK, UART0 CTS, I2C1 SDA and PWM7A.
- **D0P/GPIO15** - Digital I/O pin 15 and one of the 8 HSTX peripheral pins. It is also SPI1 MISO, UART0 RTS, I2C1 SCL and PWM7B.
- **D1N/GPIO16** - Digital I/O pin 16 and one of the 8 HSTX peripheral pins. It is also SPI0 MISO, UART0 TX, I2C0 SDA and PWM0A.
- **D1P/GPIO17** - Digital I/O pin 17 and one of the 8 HSTX peripheral pins. It is also SPI0 CS, UART0 RX, I2C0 SCL and PWM0B.
- **D2N/GPIO18** - Digital I/O pin 18 and one of the 8 HSTX peripheral pins. It is also SPI0 SCK, UART0 CTS, I2C1 SDA, and PWM1A.
- **D2P/GPIO19** - Digital I/O pin 19 and one of the 8 HSTX peripheral pins. It is also SPI0 RTS, UART0 RTS, I2C1 SCL, and PWM1B.
## TLV320DAC3100 I2S DAC
On the front of the board, to the left of Button #3, is the TLV320DAC3100 I2S DAC. It is a stereo audio DAC that can drive a mono 4-8Ω speaker or up to 16Ω stereo headphones directly. It communicates with the RP2350 via these pins:
- **Data** - Located on **GPIO24**. It can be accessed via `board.I2S_DIN` in CircuitPython and `PIN_I2S_DATAOUT` in Arduino.
- **Main Clock** - Located on **GPIO25**. It can be accessed via `board.I2S_MCLK` in CircuitPython and `PIN_I2S_MCLK` in Arduino. This pin is **optional** because you can configure the I2C driver to use BCLK as the PLL input.
- **Bit Clock** - Located on **GPIO26**. It can be accessed via `board.I2S_BCLK` in CircuitPython and `PIN_I2S_BITCLK` in Arduino.
- **Word Select** - Located on **GPIO27**. It can be accessed via `board.I2S_WS` in CircuitPython and `PIN_I2S_WORDSEL` in Arduino.
- **Interrupt** - Located on **GPIO23**. It can be accessed via `board.I2S_IRQ` in CircuitPython and `PIN_I2S_IRQ` in Arduino.
- **Peripheral Reset** - Located on **GPIO22**. It can be accessed via `bobard.PERIPH_RESET` in CircuitPython and `PIN_PERIPHERAL_RESET` in Arduino. The DAC needs to be reset before use by toggling this pin from low to high. This pin is shared with the reset pin ESP32-C6 and is broken out on the 2x16 header.
- **3.5mm output jack** - Labeled **Stereo Headphone** on the board silk, this is the onboard headphone jack. It can provide stereo audio that can connect directly to your 16Ω headphones.
- **Speaker Output** - Labeled **4-8Ω Speaker** on the board silk, this is the onboard JST-SH speaker port. You'll want to disable speaker output when using the headphone output for the best possible sound quality. The class-D amplifier for the speaker can cause some noise on the headphone output.
There is a dedicated guide for the [TLV320DAC3100 I2S DAC](https://learn.adafruit.com/adafruit-tlv320dac3100-i2s-dac) with more information on its features.
Warning: Since the ESP32-C6 WiFi co-procesor and the TLV320DAC3100 I2S DAC share a reset pin, you must set up the C6 _first_, and _then_ set up the TLV320DAC3100. Calling `adafruit_esp32spi.ESP_SPIcontrol(...)` will toggle the reset pin and will clear any prior setup done to the TLV320DAC3100.
### Adafruit TLV320DAC3100 I2S DAC - Overview
[Adafruit TLV320DAC3100 I2S DAC](https://learn.adafruit.com/adafruit-tlv320dac3100-i2s-dac)
[Overview](https://learn.adafruit.com/adafruit-tlv320dac3100-i2s-dac/overview)
## JST-SH Speaker & Top Plate
A small JST-SH speaker can be semi-permanently connected by plugging in the JST-SH connector to the **Speaker Output** connector on the Fruit Jam, then using the self adhesive on the back of the mini speaker to attach it on the under side of the top plate. It is easiest to attach over in the center of the board where there are fewer components to interfere with placement.
After adhering the speaker to the top plate flip it over, and align it with the holes for mount screws, header pins, and buttons. Carefully screw in the M3 screws to the mounting holes. _ **Do not tighten the screw nearest to the speaker connector all the way.** _ There needs to enough of a gap to not pinch the wires coming from the JST-PH connector.
## Buttons and RST Pin
There are three buttons available on the right edge of the board:
- **Button #1** - Located on GPIO0. It is available at `board.BUTTON1` in CircuitPython. It is also the UF2 BOOT button and is broken out on the 2x16 header.
- **Button #2** - Located on GPIO4. It is available at `board.BUTTON2` in CircuitPython
- **Button #3** - Located on GPIO5. It is available at `board.BUTTON3` in CircuitPython
The **Boot button** is the button on the right, shared with Button #1. It is also broken out on the 2x16 header. It is used to enter the bootloader. To enter the bootloader, press and hold Button #1 and then power up the board (either by plugging it into USB or pressing Reset). The bootloader is used to install/update CircuitPython.
The **Reset button** is on the left of the board. It restarts the board and helps enter the bootloader. You can click it to reset the board without unplugging the USB cable.
The **Reset pin** can be used to reset the board and is broken out on the 2x16 header. Tie to ground manually to reset the board.
## NeoPixels and Red LED
On the left side of the board are five onboard status **NeoPixel** LEDs. They are connected to **GPIO32**. In CircuitPython, the NeoPixels are available at `board.NEOPIXEL` and the library for it is available in [the bundle](https://circuitpython.org/libraries). In Arduino, they are accessible at `PIN_NEOPIXEL`. The NeoPixel is powered by the 3.3V power supply but that hasn't shown to make a big difference in brightness or color. In CircuitPython, the LEDs are used to indicate the runtime status.
To the left of the USB C connector is the onboard **LED** , connected to **GPIO29**. This little red LED is controllable in CircuitPython code using `board.LED`, and in Arduino as `PIN_LED`. It shares a GPIO pin with the IR receiver.
Unusually, the built-in LED is wired with its **anode** connected to **3.3V** , and its **cathode** connected to **GPIO29**. That means that setting the pin to `LOW` results in the LED turning on, and setting the pin to `HIGH` results in the LED turning off.
Danger: The built-in LED lights up if you ground its pin (setting it to low). This is unusual and is the reverse from most other boards.
## IR Receiver
Warning: If you have a 1st batch Fruit Jam shipped before 8/10/2025 the IR receiver will not work without replacing the resistor near the IR in label on the silkscreen with one that is 150-1k ohm. See discussion [on this issue](https://github.com/adafruit/circuitpython/issues/10546) for more details. Any Fruit Jams shipped after 8/10/25 already have the corrected resistor value.
At the top of the board, between the USB C port and the DVI Video port, is the IR receiver. It is labeled **IR In** on the board silk. You can write code to use this receiver with an IR remote. It is connected to **GPIO29** , the same pin as the built-in LED, and is available as `board.IR` in CircuitPython.
## STEMMA QT
In the bottom right corner, below Button #1, is the **STEMMA QT connector**! This means you can connect up [all sorts of I2C sensors and breakouts](https://www.adafruit.com/?q=stemma+qt), no soldering required! This connector uses the SCL and SDA pins for I2C, which end up being the RP2350's I2C0 peripheral. In CircuitPython, you can initialize the STEMMA connector with `board.STEMMA_I2C()` (as well as with `board.SCL` `board.SDA`). In Arduino it is `Wire`.
### STEMMA QT / Qwiic JST SH 4-pin Cable - 100mm Long
[STEMMA QT / Qwiic JST SH 4-pin Cable - 100mm Long](https://www.adafruit.com/product/4210)
This 4-wire cable is a little over 100mm / 4" long and fitted with JST-SH female 4-pin connectors on both ends. Compared with the chunkier JST-PH these are 1mm pitch instead of 2mm, but still have a nice latching feel, while being easy to insert and remove.
Out of Stock
[Buy Now](https://www.adafruit.com/product/4210)
[Related Guides to the Product](https://learn.adafruit.com/products/4210/guides)
## JST-PH Connector
In the bottom left corner of the board is the JST-PH connector. You can plug in a JST-PH cable to access **VCC** (red wire), **GND** (black wire) and pin **A0** (white wire). Perfect for adding a potentiometer or extra component. **A0** is connected to GPIO40 and is ADC0. It is also SPI1 MOSI, UART1 TX, I2C0 SDA and PWM8A.
By default, **VCC** is connected to the 5V regulator. You can change VCC from 5V to 3.3V via the jumper on the back of the board labeled JST VCC. You can cut the 5V and center pad and then solder the center pad to the 3V pad.
### STEMMA JST PH 2mm 3-Pin to Male Header Cable - 200mm
[STEMMA JST PH 2mm 3-Pin to Male Header Cable - 200mm](https://www.adafruit.com/product/3893)
This cable will let you turn a JST PH 3-pin cable port into 3 individual wires with high-quality 0.1" male header plugs on the end. We're carrying these to match up with our Hallowing, for extending and connecting sensors or LEDs - and the wires are even color coded!
In Stock
[Buy Now](https://www.adafruit.com/product/3893)
[Related Guides to the Product](https://learn.adafruit.com/products/3893/guides)
## MicroSD Card Slot
The Fruit Jam comes with a microSD card slot. It is wired up for SPI interfacing.
It also has extra pins connected for advanced-user SDIO interfacing.
These are the pins for the MicroSD card slot.
- **SD\_SCK/GPIO34** - This is the main SPI0 SCK pin. It is also I2C1 SDA, and PWM9A.
- **SD\_MOSI/GPIO35** - This is the main SPI0 MOSI pin. It is also I2C1 SCL, and PWM9B.
- **SD\_MISO/GPIO36** - This is the main SPI0 MISO pin. It is also UART1 TX, I2C0 SDA, and PWM10A.
- **SD\_CS/GPIO39** - This is the chip select pin. It is also SPI0 MOSI, I2C1 SCL, and PWM11B.
- **SD\_CARD\_DETECT/GPIO34** - This is the card detect pin. It is also SPI0 CSn, UART0 RX, I2C0 SCL, and PWM8B
- **SDIO\_DATA1/GPIO37** - This is the SDIO data1 pin. It is also SPI0 CS, UART1 RX, I2C0 SCL, and PWM10B.
- **SDIO\_DATA2/GPIO38** - This is the SDIO data2 pin. It is also SPI0 SCK, I2C1 SDA, and PWM11A.
## USB Host
The Fruit Jam uses two pins for USB host, along with power and ground:
- **GND** - Common ground for power and logic.
- **USB\_HOST\_DATA\_PLUS/GPIO1** - The D+ pin for USB Host. It is also SPI0 CS, UART0 RS, I2C0 SCL and PWM0B.
- **USB\_HOST\_DATA\_MINUS/GPIO2** - The D- pin for USB Host. It is also SPI0 SCK, UART0 CTS, I2C1 SDA and PWM1A.
- **USB\_HOST\_5V\_POWER/GPIO11** - The 5V pin for USB Host. It is also SPI1 MOSI, UART1 RTS, I2C1 SCL and PWM5B.
The 'native' USB host pins are exposed as two solderable pins above the STEMMA QT connector. There is a **CH334F USB hub** to the left of the D+ and D- pins. The USB hub chip has 3 ports, two are on USB A connectors and a third port **D+** and **D-** pins are broken out in the 2x16 header. The two **USB A ports** are connected to the hub. Each port has an indicator LED on either side of the power switch.
## Debug Port
Below the SD card slot is the JST SH 3-pin **Debug** port for SWD debugging. This port matches the [Raspberry Pi 3-pin Debug Connector Specification](https://datasheets.raspberrypi.com/debug/debug-connector-specification.pdf) for use with the Debug Probe Kit. It breaks out the following serial debug pins:
- Pin 1: **SWCLK** (serial clock)
- Pin 2: **GND**
- Pin 3: **SWDIO** (bidirectional serial data)
### Raspberry Pi Debug Probe Kit for Pico and RP2040
[Raspberry Pi Debug Probe Kit for Pico and RP2040](https://www.adafruit.com/product/5699)
The Raspberry Pi Debug Probe is an all-in-one USB-to-debug kit that provides all the necessary hardware and cables for easy, solderless, plug-and-play debugging. For when "printf-style-debugging" just isn't enough, this kit which brings the power of gdb &...
In Stock
[Buy Now](https://www.adafruit.com/product/5699)
[Related Guides to the Product](https://learn.adafruit.com/products/5699/guides)
# Adafruit Fruit Jam
## Install CircuitPython
[CircuitPython](https://github.com/adafruit/circuitpython) is a derivative of [MicroPython](https://micropython.org) designed to simplify experimentation and education on low-cost microcontrollers. It makes it easier than ever to get prototyping by requiring no upfront desktop software downloads. Simply copy and edit files on the **CIRCUITPY** drive to iterate.
## CircuitPython Quickstart
Follow this step-by-step to quickly get CircuitPython running on your board.
Warning: Please use the latest release of 10.x or higher for the Fruit Jam. Also use the latest libraries for the best functionality.
[Download the latest version of CircuitPython for this board via circuitpython.org](https://circuitpython.org/board/adafruit_fruit_jam/)
**Click the link above to download the latest CircuitPython UF2 file.**
Save it wherever is convenient for you.
To enter the bootloader, hold down the **BOOT/**** BOOTSEL button**(highlighted in red above), and while continuing to hold it (don't let go!), press and release the**reset button**(highlighted in red or blue above). **Continue to hold the BOOT/BOOTSEL button until the RP2350 drive appears!**
If the drive does not appear, release all the buttons, and then repeat the process above.
You can also start with your board unplugged from USB, press and hold the BOOTSEL button (highlighted in red above), continue to hold it while plugging it into USB, and wait for the drive to appear before releasing the button.
A lot of people end up using charge-only USB cables and it is very frustrating! **Make sure you have a USB cable you know is good for data sync.**
You will see a new disk drive appear called **RP2350**.
Drag the **adafruit-circuitpython-_boardname_-_language_-_version_.uf2** file to **RP2350.**
The **RP2350** drive will disappear and a new disk drive called **CIRCUITPY** will appear.
That's it, you're done! :)
## Safe Mode
You want to edit your **code.py** or modify the files on your **CIRCUITPY** drive, but find that you can't. Perhaps your board has gotten into a state where **CIRCUITPY** is read-only. You may have turned off the **CIRCUITPY** drive altogether. Whatever the reason, safe mode can help.
Safe mode in CircuitPython does not run any user code on startup, and disables auto-reload. This means a few things. First, safe mode _bypasses any code in_ **boot.py** (where you can set **CIRCUITPY** read-only or turn it off completely). Second, _it does not run the code in_ **code.py**. And finally, _it does not automatically soft-reload when data is written to the_ **CIRCUITPY** _drive_.
Therefore, whatever you may have done to put your board in a non-interactive state, safe mode gives you the opportunity to correct it without losing all of the data on the **CIRCUITPY** drive.
### Entering Safe Mode
To enter safe mode when using CircuitPython, plug in your board or hit reset (highlighted in red above). Immediately after the board starts up or resets, it waits 1000ms. On some boards, the onboard status LED (highlighted in green above) will blink yellow during that time. If you press reset during that 1000ms, the board will start up in safe mode. It can be difficult to react to the yellow LED, so you may want to think of it simply as a slow double click of the reset button. (Remember, a fast double click of reset enters the bootloader.)
### In Safe Mode
If you successfully enter safe mode on CircuitPython, the LED will intermittently blink yellow three times.
If you connect to the serial console, you'll find the following message.
```terminal
Auto-reload is off.
Running in safe mode! Not running saved code.
CircuitPython is in safe mode because you pressed the reset button during boot. Press again to exit safe mode.
Press any key to enter the REPL. Use CTRL-D to reload.
```
You can now edit the contents of the **CIRCUITPY** drive. Remember, _your code will not run until you press the reset button, or unplug and plug in your board, to get out of safe mode._
## Flash Resetting UF2
If your board ever gets into a really _weird_ state and CIRCUITPY doesn't show up as a disk drive after installing CircuitPython, try loading this 'nuke' UF2 to RP2350. which will do a 'deep clean' on your Flash Memory. **You will lose all the files on the board** , but at least you'll be able to revive it! After loading this UF2, follow the steps above to re-install CircuitPython.
[Download flash erasing "nuke" UF2 for RP2350](https://cdn-learn.adafruit.com/assets/assets/000/132/526/original/rp2350_flash_nuke.uf2)
# Adafruit Fruit Jam
## Installing the Mu Editor
Mu is a simple code editor that works with the Adafruit CircuitPython boards. It's written in Python and works on Windows, MacOS, Linux and Raspberry Pi. The serial console is built right in so you get immediate feedback from your board's serial output!
Info: Mu is our recommended editor - please use it (unless you are an experienced coder with a favorite editor already!). While it has been announced end of life in 2026, it still works fine.
You are free to use whatever text editor you wish along with a terminal program to connect to the CircuitPython REPL. Thonny is one such editor.
## Download and Install Mu
Download Mu from [https://codewith.mu](https://codewith.mu/).
Click the **Download** link for downloads and installation instructions.
Click **Start Here ** to find a wealth of other information, including extensive tutorials and and how-to's.
Warning:
## Starting Up Mu
The first time you start Mu, you will be prompted to select your 'mode' - you can always change your mind later. For now please select **CircuitPython**!
The current mode is displayed in the lower right corner of the window, next to the "gear" icon. If the mode says "Microbit" or something else, click the **Mode** button in the upper left, and then choose "CircuitPython" in the dialog box that appears.
Mu attempts to auto-detect your board on startup, so if you do not have a CircuitPython board plugged in with a **CIRCUITPY** drive available, Mu will inform you where it will store any code you save until you plug in a board.
To avoid this warning, plug in a board and ensure that the **CIRCUITPY** drive is mounted before starting Mu.
## Using Mu
You can now explore Mu! The three main sections of the window are labeled below; the button bar, the text editor, and the serial console / REPL.
Now you're ready to code! Let's keep going...
# Adafruit Fruit Jam
## The CIRCUITPY Drive
When CircuitPython finishes installing, or you plug a CircuitPython board into your computer with CircuitPython already installed, the board shows up on your computer as a USB drive called **CIRCUITPY**.
The **CIRCUITPY** drive is where your code and the necessary libraries and files will live. You can edit your code directly on this drive and when you save, it will run automatically. When you create and edit code, you'll save your code in a **code.py** file located on the **CIRCUITPY** drive. If you're following along with a Learn guide, you can paste the contents of the tutorial example into **code.py** on the **CIRCUITPY** drive and save it to run the example.
With a fresh CircuitPython install, on your **CIRCUITPY** drive, you'll find a **code.py** file containing `print("Hello World!")` and an empty **lib** folder. If your **CIRCUITPY** drive does not contain a **code.py** file, you can easily create one and save it to the drive. CircuitPython looks for **code.py** and executes the code within the file automatically when the board starts up or resets. Following a change to the contents of **CIRCUITPY** , such as making a change to the **code.py** file, the board will reset, and the code will be run. You do not need to manually run the code. This is what makes it so easy to get started with your project and update your code!
Note that all changes to the contents of **CIRCUITPY** , such as saving a new file, renaming a current file, or deleting an existing file will trigger a reset of the board.
## Boards Without CIRCUITPY
CircuitPython is available for some microcontrollers that do not support native USB. Those boards cannot present a **CIRCUITPY** drive. This includes boards using ESP32 or ESP32-C3 microcontrollers.
On these boards, there are alternative ways to transfer and edit files. You can use the [Thonny editor](https://thonny.org), which uses hidden commands sent to the REPL to read and write files. Or you can use the CircuitPython web workflow, introduced in Circuitpython 8. The web workflow provides browser-based WiFi access to the CircuitPython filesystem. These guides will help you with the web workflow:
- [CircuitPython on ESP32 Quick Start](https://learn.adafruit.com/circuitpython-with-esp32-quick-start)
- [CircuitPython Web Workflow Code Editor Quick Start](https://learn.adafruit.com/getting-started-with-web-workflow-using-the-code-editor)
# Adafruit Fruit Jam
## Creating and Editing Code
One of the best things about CircuitPython is how simple it is to get code up and running. This section covers how to create and edit your first CircuitPython program.
To create and edit code, all you'll need is an editor. There are many options. **Adafruit strongly recommends using Mu! It's designed for CircuitPython, and it's really simple and easy to use, with a built in serial console!**
If you don't or can't use Mu, there are a number of other editors that work quite well. The [Recommended Editors page](https://learn.adafruit.com/welcome-to-circuitpython/recommended-editors) has more details. Otherwise, make sure you do "Eject" or "Safe Remove" on Windows or "sync" on Linux after writing a file if you aren't using Mu. (This was formerly not a problem on macOS, but see the warning below.)
Warning: macOS Sonoma 14.1 introduced a bug that delays writes to small drives such as CIRCUITPY drives. This caused errors when saving files to CIRCUITPY. There is a [workaround](https://learn.adafruit.com/welcome-to-circuitpython/troubleshooting#macos-sonoma-14-dot-x-disk-errors-writing-to-circuitpy-3160304). The bug was fixed in Sonoma 14.4, but at the cost of greatly slowed writes to drives 1GB or smaller.
## Creating Code
Installing CircuitPython generates a **code.py** file on your **CIRCUITPY** drive. To begin your own program, open your editor, and load the **code.py** file from the **CIRCUITPY** drive.
If you are using Mu, click the **Load** button in the button bar, navigate to the **CIRCUITPY** drive, and choose **code.py**.
Copy and paste the following code into your editor:
```python
import board
import digitalio
import time
led = digitalio.DigitalInOut(board.LED)
led.direction = digitalio.Direction.OUTPUT
while True:
led.value = True
time.sleep(0.5)
led.value = False
time.sleep(0.5)
```
Danger: The KB2040, QT Py , Qualia, and the Trinkeys do not have a built-in little red LED! There is an addressable RGB NeoPixel LED. The above example will NOT work on the KB2040, QT Py, Qualia, or the Trinkeys!
If you're using a KB2040, QT Py, Quaila, or a Trinkey, or any other board without a single-color LED that can blink, please download the [NeoPixel blink example](https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/master/Welcome_to_CircuitPython/code.py).
Info:
It will look like this. Note that under the `while True:` line, the next four lines begin with four spaces to indent them, and they're indented exactly the same amount. All the lines before that have no spaces before the text.
Save the **code.py** file on your **CIRCUITPY** drive.
The little LED should now be blinking. Once per half-second.
Congratulations, you've just run your first CircuitPython program!
Info: On most boards you'll find a tiny red LED. On the ItsyBitsy nRF52840, you'll find a tiny blue LED. On QT Py M0, QT Py RP2040, Qualia, and the Trinkey series, you will find only an RGB NeoPixel LED.
## Editing Code
To edit code, open the **code.py** file on your **CIRCUITPY** drive into your editor.
Make the desired changes to your code. Save the file. That's it!
### Your code changes are run as soon as the file is done saving.
There's one warning before you continue...
Danger:
The CircuitPython code on your board detects when the files are changed or written and will automatically re-start your code. This makes coding very fast because you save, and it re-runs. If you unplug or reset the board before your computer finishes writing the file to your board, you can corrupt the drive. If this happens, you may lose the code you've written, so it's important to backup your code to your computer regularly.
There are a couple of ways to avoid filesystem corruption.
### **1. Use an editor that writes out the file completely when you save it.**
Check out the [Recommended Editors page](https://learn.adafruit.com/welcome-to-circuitpython/recommended-editors) for details on different editing options.
Info:
### **2. Eject or Sync the Drive After Writing**
If you are using one of our not-recommended-editors, not all is lost! You can still make it work.
On Windows, you can Eject or Safe Remove the **CIRCUITPY** drive. It won't actually eject, but it will force the operating system to save your file to disk. On Linux, use the **sync** command in a terminal to force the write to disk.
You also need to do this if you use Windows Explorer or a Linux graphical file manager to drag a file onto **CIRCUITPY**.
###
Don't worry! Corrupting the drive isn't the end of the world (or your board!). If this happens, follow the steps found on the [Troubleshooting](https://learn.adafruit.com/welcome-to-circuitpython/troubleshooting) page of every board guide to get your board up and running again.
Info: If you are having trouble saving code on Windows 10, try including this code snippet at the top of code.py:
```python
import supervisor
supervisor.runtime.autoreload = False
```
## Back to Editing Code...
Now! Let's try editing the program you added to your board. Open your **code.py** file into your editor. You'll make a simple change. Change the first `0.5` to `0.1`. The code should look like this:
```python
import board
import digitalio
import time
led = digitalio.DigitalInOut(board.LED)
led.direction = digitalio.Direction.OUTPUT
while True:
led.value = True
time.sleep(0.1)
led.value = False
time.sleep(0.5)
```
Leave the rest of the code as-is. Save your file. See what happens to the LED on your board? Something changed! Do you know why?
You don't have to stop there! Let's keep going. Change the second `0.5` to `0.1` so it looks like this:
```
while True:
led.value = True
time.sleep(0.1)
led.value = False
time.sleep(0.1)
```
Now it blinks really fast! You decreased the both time that the code leaves the LED on and off!
Now try increasing both of the `0.1` to `1`. Your LED will blink much more slowly because you've increased the amount of time that the LED is turned on and off.
Well done! You're doing great! You're ready to start into new examples and edit them to see what happens! These were simple changes, but major changes are done using the same process. Make your desired change, save it, and get the results. That's really all there is to it!
# Naming Your Program File
CircuitPython looks for a code file on the board to run. There are four options: **code.txt** , **code.py** , **main.txt** and **main.py**. CircuitPython looks for those files, in that order, and then runs the first one it finds. While **code.py** is the recommended name for your code file, it is important to know that the other options exist. If your program doesn't seem to be updating as you work, make sure you haven't created another code file that's being read instead of the one you're working on.
# Adafruit Fruit Jam
## Exploring Your First CircuitPython Program
First, you'll take a look at the code you're editing.
Here is the original code again for the LED blink example (if your board doesn't have a single-color LED to blink, look instead at the NeoPixel blink example):
```python
import board
import digitalio
import time
led = digitalio.DigitalInOut(board.LED)
led.direction = digitalio.Direction.OUTPUT
while True:
led.value = True
time.sleep(0.5)
led.value = False
time.sleep(0.5)
```
## Imports & Libraries
Each CircuitPython program you run needs to have a lot of information to work. The reason CircuitPython is so simple to use is that most of that information is stored in other files and works in the background. The files built into CircuitPython are called **modules** , and the files you load separately are called **libraries**. Modules are built into CircuitPython. Libraries are stored on your **CIRCUITPY** drive in a folder called **lib**.
```python
import board
import digitalio
import time
```
The `import` statements tells the board that you're going to use a particular library or module in your code. In this example, you imported three modules: `board`, `digitalio`, and `time`. All three of these modules are built into CircuitPython, so no separate library files are needed. That's one of the things that makes this an excellent first example. You don't need anything extra to make it work!
These three modules each have a purpose. The first one,`board`, gives you access to the _hardware on your board_. The second, `digitalio`, lets you _access that hardware as inputs/outputs_._ _The third, `time`, let's you control the flow of your code in multiple ways, including passing time by 'sleeping'.
## Setting Up The LED
The next two lines setup the code to use the LED.
```auto
led = digitalio.DigitalInOut(board.LED)
led.direction = digitalio.Direction.OUTPUT
```
Your board knows the red LED as `LED`. So, you initialise that pin, and you set it to output. You set `led` to equal the rest of that information so you don't have to type it all out again later in our code.
## Loop-de-loops
The third section starts with a `while` statement. `while True:` essentially means, "forever do the following:". `while True:` creates a loop. Code will loop "while" the condition is "true" (vs. false), and as `True` is never False, the code will loop forever. All code that is indented under `while True:` is "inside" the loop.
Inside our loop, you have four items:
```python
while True:
led.value = True
time.sleep(0.5)
led.value = False
time.sleep(0.5)
```
First, you have `led.value = True`. This line tells the LED to turn on. On the next line, you have `time.sleep(0.5)`. This line is telling CircuitPython to pause running code for 0.5 seconds. Since this is between turning the led on and off, the led will be on for 0.5 seconds.
The next two lines are similar. `led.value = False` tells the LED to turn off, and `time.sleep(0.5)` tells CircuitPython to pause for another 0.5 seconds. This occurs between turning the led off and back on so the LED will be off for 0.5 seconds too.
Then the loop will begin again, and continue to do so as long as the code is running!
So, when you changed the first `0.5` to `0.1`, you decreased the amount of time that the code leaves the LED on. So it blinks on really quickly before turning off!
Great job! You've edited code in a CircuitPython program!
## What Happens When My Code Finishes Running?
When your code finishes running, CircuitPython resets your microcontroller board to prepare it for the next run of code. That means any set up you did earlier no longer applies, and the pin states are reset.
For example, try reducing the code snippet above by eliminating the loop entirely, and replacing it with `led.value = True`. The LED will flash almost too quickly to see, and turn off. This is because the code finishes running and resets the pin state, and the LED is no longer receiving a signal.
To that end, most CircuitPython programs involve some kind of loop, infinite or otherwise.
## What if I Don't Have the Loop?
If you don't have the loop, the code will run to the end and exit. This can lead to some unexpected behavior in simple programs like this since the "exit" also resets the state of the hardware. This is a different behavior than running commands via REPL. So if you are writing a simple program that doesn't seem to work, you may need to add a loop to the end so the program doesn't exit.
The simplest loop would be:
```python
while True:
pass
```
And remember - you can press CTRL+C to exit the loop.
See also the [Behavior section in the docs](https://circuitpython.readthedocs.io/en/latest/README.html#behavior).
# Adafruit Fruit Jam
## Connecting to the Serial Console
One of the staples of CircuitPython (and programming in general!) is something called a "print statement". This is a line you include in your code that causes your code to output text. A print statement in CircuitPython (and Python) looks like this:
`print("Hello, world!")`
This line in your code.py would result in:
`Hello, world!`
However, these print statements need somewhere to display. That's where the serial console comes in!
The serial console receives output from your CircuitPython board sent over USB and displays it so you can see it. This is necessary when you've included a print statement in your code and you'd like to see what you printed. It is also helpful for troubleshooting errors, because your board will send errors and the serial console will display those too.
The serial console requires an editor that has a built in terminal, or a separate terminal program. A terminal is a program that gives you a text-based interface to perform various tasks.
# Are you using Mu?
If so, good news! The serial console **is built into Mu** and will **autodetect your board** making using the serial console _really really easy_.
First, make sure your CircuitPython board is plugged in.
If you open Mu without a board plugged in, you may encounter the error seen here, letting you know no CircuitPython board was found and indicating where your code will be stored until you plug in a board.
[If you are using Windows 7, make sure you installed the drivers](https://learn.adafruit.com/welcome-to-circuitpython/windows-7-and-8-1-drivers).
Once you've opened Mu with your board plugged in, look for the **Serial** button in the button bar and click it.
The Mu window will split in two, horizontally, and display the serial console at the bottom.
Info:
## Serial Console Issues or Delays on Linux
If you're on Linux, and are seeing multi-second delays connecting to the serial console, or are seeing "AT" and other gibberish when you connect, then the `modemmanager` service might be interfering. Just remove it; it doesn't have much use unless you're still using dial-up modems.
To remove `modemmanager`, type the following command at a shell:
```terminal
sudo apt purge modemmanager
```
## Setting Permissions on Linux
On Linux, if you see an error box something like the one below when you press the **Serial** button, you need to add yourself to a user group to have permission to connect to the serial console.
On Ubuntu and Debian, add yourself to the **dialout** group by doing:
```terminal
sudo adduser $USER dialout
```
After running the command above, reboot your machine to gain access to the group. On other Linux distributions, the group you need may be different. See the [Advanced Serial Console on Linux](https://learn.adafruit.com/welcome-to-circuitpython/advanced-serial-console-on-linux) for details on how to add yourself to the right group.
# Using Something Else?
If you're not using Mu to edit, are using or if for some reason you are not a fan of its built in serial console, you can run the serial console from a separate program.
Windows requires you to download a terminal program. [Check out the Advanced Serial Console on Windows page for more details.](../../../../welcome-to-circuitpython/advanced-serial-console-on-windows)
MacOS has Terminal built in, though there are other options available for download. [Check the Advanced Serial Console on Mac page for more details.](../../../../welcome-to-circuitpython/advanced-serial-console-on-mac-and-linux)
Linux has a terminal program built in, though other options are available for download. [Check the Advanced Serial Console on Linux page for more details.](https://learn.adafruit.com/welcome-to-circuitpython/advanced-serial-console-on-linux)
Once connected, you'll see something like the following.
# Adafruit Fruit Jam
## Interacting with the Serial Console
Once you've successfully connected to the serial console, it's time to start using it.
The code you wrote earlier has no output to the serial console. So, you're going to edit it to create some output.
Open your code.py file into your editor, and include a `print` statement. You can print anything you like! Just include your phrase between the quotation marks inside the parentheses. For example:
```python
import board
import digitalio
import time
led = digitalio.DigitalInOut(board.LED)
led.direction = digitalio.Direction.OUTPUT
while True:
print("Hello, CircuitPython!")
led.value = True
time.sleep(1)
led.value = False
time.sleep(1)
```
Save your file.
Now, let's go take a look at the window with our connection to the serial console.
Excellent! Our print statement is showing up in our console! Try changing the printed text to something else.
```python
import board
import digitalio
import time
led = digitalio.DigitalInOut(board.LED)
led.direction = digitalio.Direction.OUTPUT
while True:
print("Hello back to you!")
led.value = True
time.sleep(1)
led.value = False
time.sleep(1)
```
Keep your serial console window where you can see it. Save your file. You'll see what the serial console displays when the board reboots. Then you'll see your new change!
The `Traceback (most recent call last):` is telling you the last thing your board was doing before you saved your file. This is normal behavior and will happen every time the board resets. This is really handy for troubleshooting. Let's introduce an error so you can see how it is used.
Delete the `e` at the end of `True` from the line `led.value = True` so that it says `led.value = Tru`
```python
import board
import digitalio
import time
led = digitalio.DigitalInOut(board.LED)
led.direction = digitalio.Direction.OUTPUT
while True:
print("Hello back to you!")
led.value = Tru
time.sleep(1)
led.value = False
time.sleep(1)
```
Save your file. You will notice that your red LED will stop blinking, and you may have a colored status LED blinking at you. This is because the code is no longer correct and can no longer run properly. You need to fix it!
Usually when you run into errors, it's not because you introduced them on purpose. You may have 200 lines of code, and have no idea where your error could be hiding. This is where the serial console can help. Let's take a look!
The `Traceback (most recent call last):` is telling you that the last thing it was able to run was `line 10` in your code. The next line is your error: `NameError: name 'Tru' is not defined`. This error might not mean a lot to you, but combined with knowing the issue is on line 10, it gives you a great place to start!
Go back to your code, and take a look at line 10. Obviously, you know what the problem is already. But if you didn't, you'd want to look at line 10 and see if you could figure it out. If you're still unsure, try googling the error to get some help. In this case, you know what to look for. You spelled True wrong. Fix the typo and save your file.
Nice job fixing the error! Your serial console is streaming and your red LED Is blinking again.
The serial console will display any output generated by your code. Some sensors, such as a humidity sensor or a thermistor, receive data and you can use print statements to display that information. You can also use print statements for troubleshooting, which is called "print debugging". Essentially, if your code isn't working, and you want to know where it's failing, you can put print statements in various places to see where it stops printing.
The serial console has many uses, and is an amazing tool overall for learning and programming!
# Adafruit Fruit Jam
## The REPL
The other feature of the serial connection is the **R** ead- **E** valuate **-**** P **rint-** L**oop, or REPL. The REPL allows you to enter individual lines of code and have them run immediately. It's really handy if you're running into trouble with a particular program and can't figure out why. It's interactive so it's great for testing new ideas.
## Entering the REPL
To use the REPL, you first need to be connected to the serial console. Once that connection has been established, you'll want to press **CTRL+C**.
If there is code running, in this case code measuring distance, it will stop and you'll see `Press any key to enter the REPL. Use CTRL-D to reload.` Follow those instructions, and press any key on your keyboard.
The `Traceback (most recent call last):` is telling you the last thing your board was doing before you pressed Ctrl + C and interrupted it. The `KeyboardInterrupt` is you pressing CTRL+C. This information can be handy when troubleshooting, but for now, don't worry about it. Just note that it is expected behavior.
If your **code.py** file is empty or does not contain a loop, it will show an empty output and `Code done running.`. There is no information about what your board was doing before you interrupted it because there is no code running.
If you have no **code.py** on your **CIRCUITPY** drive, you will enter the REPL immediately after pressing CTRL+C. Again, there is no information about what your board was doing before you interrupted it because there is no code running.
Regardless, once you press a key you'll see a `>>>` prompt welcoming you to the REPL!
If you have trouble getting to the `>>>` prompt, try pressing Ctrl + C a few more times.
The first thing you get from the REPL is information about your board.
This line tells you the version of CircuitPython you're using and when it was released. Next, it gives you the type of board you're using and the type of microcontroller the board uses. Each part of this may be different for your board depending on the versions you're working with.
This is followed by the CircuitPython prompt.
## Interacting with the REPL
From this prompt you can run all sorts of commands and code. The first thing you'll do is run `help()`. This will tell you where to start exploring the REPL. To run code in the REPL, type it in next to the REPL prompt.
Type `help()` next to the prompt in the REPL.
Then press enter. You should then see a message.
First part of the message is another reference to the version of CircuitPython you're using. Second, a URL for the CircuitPython related project guides. Then... wait. What's this? To list built-in modules type `help("modules").` Remember the modules you learned about while going through creating code? That's exactly what this is talking about! This is a perfect place to start. Let's take a look!
Type `help("modules")` into the REPL next to the prompt, and press enter.
This is a list of all the core modules built into CircuitPython, including `board`. Remember, `board` contains all of the pins on the board that you can use in your code. From the REPL, you are able to see that list!
Type `import board` into the REPL and press enter. It'll go to a new prompt. It might look like nothing happened, but that's not the case! If you recall, the `import` statement simply tells the code to expect to do something with that module. In this case, it's telling the REPL that you plan to do something with that module.
Next, type `dir(board)` into the REPL and press enter.
This is a list of all of the pins on your board that are available for you to use in your code. Each board's list will differ slightly depending on the number of pins available. Do you see `LED`? That's the pin you used to blink the red LED!
The REPL can also be used to run code. Be aware that **any code you enter into the REPL isn't saved** anywhere. If you're testing something new that you'd like to keep, make sure you have it saved somewhere on your computer as well!
Every programmer in every programming language starts with a piece of code that says, "Hello, World." You're going to say hello to something else. Type into the REPL:
`print("Hello, CircuitPython!")`
Then press enter.
That's all there is to running code in the REPL! Nice job!
You can write single lines of code that run stand-alone. You can also write entire programs into the REPL to test them. Remember that nothing typed into the REPL is saved.
There's a lot the REPL can do for you. It's great for testing new ideas if you want to see if a few new lines of code will work. It's fantastic for troubleshooting code by entering it one line at a time and finding out where it fails. It lets you see what modules are available and explore those modules.
Try typing more into the REPL to see what happens!
Warning:
# Returning to the Serial Console
When you're ready to leave the REPL and return to the serial console, simply press **CTRL+D**. This will reload your board and reenter the serial console. You will restart the program you had running before entering the REPL. In the console window, you'll see any output from the program you had running. And if your program was affecting anything visual on the board, you'll see that start up again as well.
You can return to the REPL at any time!
# Adafruit Fruit Jam
## CircuitPython Libraries
Danger:
Each CircuitPython program you run needs to have a lot of information to work. The reason CircuitPython is so simple to use is that most of that information is stored in other files and works in the background. These files are called _libraries_. Some of them are built into CircuitPython. Others are stored on your **CIRCUITPY** drive in a folder called **lib**. Part of what makes CircuitPython so great is its ability to store code separately from the firmware itself. Storing code separately from the firmware makes it easier to update both the code you write and the libraries you depend.
Your board may ship with a **lib** folder already, it's in the base directory of the drive. If not, simply create the folder yourself. When you first install CircuitPython, an empty **lib** directory will be created for you.
CircuitPython libraries work in the same way as regular Python modules so the [Python docs](https://docs.python.org/3/tutorial/modules.html) are an excellent reference for how it all should work. In Python terms, you can place our library files in the **lib** directory because it's part of the Python path by default.
One downside of this approach of separate libraries is that they are not built in. To use them, one needs to copy them to the **CIRCUITPY** drive before they can be used. Fortunately, there is a library bundle.
The bundle and the library releases on GitHub also feature optimized versions of the libraries with the **.mpy** file extension. These files take less space on the drive and have a smaller memory footprint as they are loaded.
Due to the regular updates and space constraints, Adafruit does not ship boards with the entire bundle. Therefore, you will need to load the libraries you need when you begin working with your board. You can find example code in the guides for your board that depends on external libraries.
Either way, as you start to explore CircuitPython, you'll want to know how to get libraries on board.
# The Adafruit Learn Guide Project Bundle
The quickest and easiest way to get going with a project from the Adafruit Learn System is by utilising the Project Bundle. Most guides now have a **Download Project Bundle** button available at the top of the full code example embed. This button downloads all the necessary files, including images, etc., to get the guide project up and running. Simply click, open the resulting zip, copy over the right files, and you're good to go!
The first step is to find the Download Project Bundle button in the guide you're working on.
Info:
Warning:
The Download Project Bundle button downloads a zip file. This zip contains a series of directories, nested within which is the **code.py** , any applicable assets like images or audio, and the **lib/** folder containing all the necessary libraries. The following zip was downloaded from the Piano in the Key of Lime guide.
Info:
When you open the zip, you'll find some nested directories. Navigate through them until you find what you need. You'll eventually find a directory for your CircuitPython version (in this case, 7.x). In the version directory, you'll find the file and directory you need: **code.py** and **lib/**. Once you find the content you need, you can copy it all over to your **CIRCUITPY** drive, replacing any files already on the drive with the files from the freshly downloaded zip.
Info:
Once you copy over all the relevant files, the project should begin running! If you find that the project is not running as expected, make sure you've copied ALL of the project files onto your microcontroller board.
That's all there is to using the Project Bundle!
# The Adafruit CircuitPython Library Bundle
Adafruit provides CircuitPython libraries for much of the hardware they provide, including sensors, breakouts and more. To eliminate the need for searching for each library individually, the libraries are available together in the Adafruit CircuitPython Library Bundle. The bundle contains all the files needed to use each library.
## Downloading the Adafruit CircuitPython Library Bundle
You can download the latest Adafruit CircuitPython Library Bundle release by clicking the button below. The libraries are being constantly updated and improved, so you'll always want to download the latest bundle.
**Match up the bundle version with the version of CircuitPython you are running.** For example, you would download the 6.x library bundle if you're running any version of CircuitPython 6, or the 7.x library bundle if you're running any version of CircuitPython 7, etc. If you mix libraries with major CircuitPython versions, you will get incompatible mpy errors due to changes in library interfaces possible during major version changes.
[Click to visit circuitpython.org for the latest Adafruit CircuitPython Library Bundle](https://circuitpython.org/libraries)
**Download the bundle version that matches your CircuitPython firmware version.** If you don't know the version, check the version info in **boot\_out.txt** file on the **CIRCUITPY** drive, or the initial prompt in the CircuitPython REPL. For example, if you're running v7.0.0, download the 7.x library bundle.
There's also a **py** bundle which contains the uncompressed python files, you probably _don't_ want that unless you are doing advanced work on libraries.
# The CircuitPython Community Library Bundle
The CircuitPython Community Library Bundle is made up of libraries written and provided by members of the CircuitPython community. These libraries are often written when community members encountered hardware not supported in the Adafruit Bundle, or to support a personal project. The authors all chose to submit these libraries to the Community Bundle make them available to the community.
**These libraries are maintained by their authors and are not supported by Adafruit.** As you would with any library, if you run into problems, feel free to file an issue on the GitHub repo for the library. Bear in mind, though, that most of these libraries are supported by a single person and you should be patient about receiving a response. Remember, these folks are not paid by Adafruit, and are volunteering their personal time when possible to provide support.
## Downloading the CircuitPython Community Library Bundle
You can download the latest CircuitPython Community Library Bundle release by clicking the button below. The libraries are being constantly updated and improved, so you'll always want to download the latest bundle.
[Click for the latest CircuitPython Community Library Bundle release](https://github.com/adafruit/CircuitPython_Community_Bundle/releases)
The link takes you to the latest release of the CircuitPython Community Library Bundle on GitHub. There are multiple versions of the bundle available. **Download the bundle version that matches your CircuitPython firmware version.** If you don't know the version, check the version info in **boot\_out.txt** file on the **CIRCUITPY** drive, or the initial prompt in the CircuitPython REPL. For example, if you're running v7.0.0, download the 7.x library bundle.
# Understanding the Bundle
After downloading the zip, extract its contents. This is usually done by double clicking on the zip. On Mac OSX, it places the file in the same directory as the zip.
Open the bundle folder. Inside you'll find two information files, and two folders. One folder is the lib bundle, and the other folder is the examples bundle.
Now open the lib folder. When you open the folder, you'll see a large number of **.**** mpy** files, and folders.
## Example Files
All example files from each library are now included in the bundles in an **examples** directory (as seen above), as well as an examples-only bundle. These are included for two main reasons:
- Allow for quick testing of devices.
- Provide an example base of code, that is easily built upon for individualized purposes.
## Copying Libraries to Your Board
First open the **lib** folder on your **CIRCUITPY** drive. Then, open the **lib** folder you extracted from the downloaded zip. Inside you'll find a number of folders and **.mpy** files. Find the library you'd like to use, and copy it to the **lib** folder on **CIRCUITPY**.
If the library is a directory with multiple **.mpy** files in it, be sure to **copy the entire folder to CIRCUITPY/lib**.
This also applies to example files. Open the **examples** folder you extracted from the downloaded zip, and copy the applicable file to your **CIRCUITPY** drive. Then, rename it to **code.py** to run it.
Info:
# Understanding Which Libraries to Install
You now know how to load libraries on to your CircuitPython-compatible microcontroller board. You may now be wondering, how do you know _which_ libraries you need to install? Unfortunately, it's not always straightforward. Fortunately, there is an obvious place to start, and a relatively simple way to figure out the rest. First up: the best place to start.
When you look at most CircuitPython examples, you'll see they begin with one or more `import` statements. These typically look like the following:
- `import library_or_module`
However, `import` statements can also sometimes look like the following:
- `from library_or_module import name`
- `from library_or_module.subpackage import name`
- `from library_or_module import name as local_name`
They can also have more complicated formats, such as including a `try` / `except` block, etc.
The important thing to know is that **an** `import` **statement will always include the name of the module or library that you're importing**.
Therefore, the best place to start is by reading through the `import` statements.
Here is an example import list for you to work with in this section. There is no setup or other code shown here, as the purpose of this section involves only the import list.
```python
import time
import board
import neopixel
import adafruit_lis3dh
import usb_hid
from adafruit_hid.consumer_control import ConsumerControl
from adafruit_hid.consumer_control_code import ConsumerControlCode
```
Keep in mind, not all imported items are libraries. Some of them are almost always built-in CircuitPython modules. How do you know the difference? Time to visit the REPL.
In the [Interacting with the REPL section](https://learn.adafruit.com/welcome-to-circuitpython/the-repl#interacting-with-the-repl-2977486-14) on [The REPL page](https://learn.adafruit.com/welcome-to-circuitpython/the-repl) in this guide, the `help("modules")` command is discussed. This command provides a list of all of the built-in modules available in CircuitPython for your board. So, if you connect to the serial console on your board, and enter the REPL, you can run `help("modules")` to see what modules are available for your board. Then, as you read through the `import` statements, you can, for the purposes of figuring out which libraries to load, ignore the statement that import modules.
The following is the list of modules built into CircuitPython for the Feather RP2040. Your list may look similar or be anything down to a significant subset of this list for smaller boards.
Now that you know what you're looking for, it's time to read through the import statements. The first two, `time` and `board`, are on the modules list above, so they're built-in.
The next one, `neopixel`, is not on the module list. That means it's your first library! So, you would head over to the bundle zip you downloaded, and search for **neopixel**. There is a **neopixel.mpy** file in the bundle zip. Copy it over to the **lib** folder on your **CIRCUITPY** drive. The following one, `adafruit_lis3dh`, is also not on the module list. Follow the same process for **adafruit\_lis3dh** , where you'll find **adafruit\_lis3dh.mpy** , and copy that over.
The fifth one is `usb_hid`, and it is in the modules list, so it is built in. Often all of the built-in modules come first in the import list, but sometimes they don't! Don't assume that everything after the first library is also a library, and verify each import with the modules list to be sure. Otherwise, you'll search the bundle and come up empty!
The final two imports are not as clear. Remember, when `import` statements are formatted like this, the first thing after the `from` is the library name. In this case, the library name is `adafruit_hid`. A search of the bundle will find an **adafruit\_hid _folder_**. When a library is a folder, you must copy the **entire folder and its contents _as it is in the bundle_** to the **lib** folder on your **CIRCUITPY** drive. In this case, you would copy the entire **adafruit\_hid** folder to your **CIRCUITPY/lib** folder.
Notice that there are _two_ imports that begin with `adafruit_hid`. Sometimes you will need to import more than one thing from the same library. Regardless of how many times you import the same library, you only need to load the library by copying over the **adafruit\_hid** folder _once_.
That is how you can use your example code to figure out what libraries to load on your CircuitPython-compatible board!
There are cases, however, where libraries require other libraries internally. The internally required library is called a _dependency_. In the event of library dependencies, the easiest way to figure out what other libraries are required is to connect to the serial console and follow along with the `ImportError` printed there. The following is a very simple example of an `ImportError`, but the concept is the same for any missing library.
# Example: `ImportError` Due to Missing Library
If you choose to load libraries as you need them, or you're starting fresh with an existing example, you may end up with code that tries to use a library you haven't yet loaded. This section will demonstrate what happens when you try to utilise a library that you don't have loaded on your board, and cover the steps required to resolve the issue.
This demonstration will only return an error if you do not have the required library loaded into the **lib** folder on your **CIRCUITPY** drive **.**
Let's use a modified version of the Blink example.
```auto
import board
import time
import simpleio
led = simpleio.DigitalOut(board.LED)
while True:
led.value = True
time.sleep(0.5)
led.value = False
time.sleep(0.5)
```
Save this file. Nothing happens to your board. Let's check the serial console to see what's going on.
You have an `ImportError`. It says there is `no module named 'simpleio'`. That's the one you just included in your code!
Click the link above to download the correct bundle. Extract the lib folder from the downloaded bundle file. Scroll down to find **simpleio.mpy**. This is the library file you're looking for! Follow the steps above to load an individual library file.
The LED starts blinking again! Let's check the serial console.
No errors! Excellent. You've successfully resolved an `ImportError`!
If you run into this error in the future, follow along with the steps above and choose the library that matches the one you're missing.
# Library Install on Non-Express Boards
If you have an M0 non-Express board such as Trinket M0, Gemma M0, QT Py M0, or one of the M0 Trinkeys, you'll want to follow the same steps in the example above to install libraries as you need them. Remember, you don't need to wait for an `ImportError` if you know what library you added to your code. Open the library bundle you downloaded, find the library you need, and drag it to the **lib** folder on your **CIRCUITPY** drive.
You can still end up running out of space on your M0 non-Express board even if you only load libraries as you need them. There are a number of steps you can use to try to resolve this issue. You'll find suggestions on the [Troubleshooting page](https://learn.adafruit.com/welcome-to-circuitpython/troubleshooting).
# Updating CircuitPython Libraries and Examples
Libraries and examples are updated from time to time, and it's important to update the files you have on your **CIRCUITPY** drive.
To update a single library or example, follow the same steps above. When you drag the library file to your lib folder, it will ask if you want to replace it. Say yes. That's it!
A new library bundle is released every time there's an update to a library. Updates include things like bug fixes and new features. It's important to check in every so often to see if the libraries you're using have been updated.
## CircUp CLI Tool
There is a command line interface (CLI) utility called [CircUp](https://learn.adafruit.com/keep-your-circuitpython-libraries-on-devices-up-to-date-with-circup) that can be used to easily install and update libraries on your device. Follow the directions on the [install page within the CircUp learn guide](https://learn.adafruit.com/keep-your-circuitpython-libraries-on-devices-up-to-date-with-circup/install-circup). Once you've got it installed you run the command `circup update` in a terminal to interactively update all libraries on the connected CircuitPython device. See the [usage page in the CircUp guide](https://learn.adafruit.com/keep-your-circuitpython-libraries-on-devices-up-to-date-with-circup/usage) for a full list of functionality
# Adafruit Fruit Jam
## CircuitPython Documentation
You've learned about the CircuitPython built-in modules and external libraries. You know that you can find the modules in CircuitPython, and the libraries in the Library Bundles. There are guides available that explain the basics of many of the modules and libraries. However, there's sometimes more capabilities than are necessarily showcased in the guides, and often more to learn about a module or library. So, where can you find more detailed information? That's when you want to look at the API documentation.
The entire CircuitPython project comes with extensive documentation available on Read the Docs. This includes both the [CircuitPython core](https://circuitpython.readthedocs.io/) and the [Adafruit CircuitPython libraries](https://circuitpython.readthedocs.io/projects/bundle/en/latest/).
## CircuitPython Core Documentation
The [CircuitPython core documentation](https://circuitpython.readthedocs.io/) covers many of the details you might want to know about the CircuitPython core and related topics. It includes API and usage info, a design guide and information about porting CircuitPython to new boards, MicroPython info with relation to CircuitPython, and general information about the project.
The main page covers the basics including where to **download CircuitPython** , how to **contribute** , **differences from MicroPython** , information about the **project structure** , and a **full table of contents** for the rest of the documentation.
The list along the left side leads to more information about specific topics.
The first section is **API and Usage**. This is where you can find information about how to use individual built-in **core modules** , such as `time` and `digitalio`, details about the **supported ports** , suggestions for **troubleshooting** , and basic info and links to the **library bundles**. The **Core Modules** section also includes the **Support Matrix** , which is a table of which core modules are available on which boards.
The second section is **Design and Porting** **Reference**. It includes a **design guide** , **architecture** information, details on **porting** , and **adding module support** to other ports.
The third section is **MicroPython Specific**. It includes information on **MicroPython and related libraries** , and a **glossary** of terms.
The fourth and final section is **About the Project**. It includes further information including details on **building, testing, and debugging CircuitPython** , along with various other useful links including the **Adafruit Community Code of Conduct**.
Whether you're a seasoned pro or new to electronics and programming, you'll find a wealth of information to help you along your CircuitPython journey in the documentation!
## CircuitPython Library Documentation
The Adafruit CircuitPython libraries are documented in a very similar fashion. Each library has its own page on Read the Docs. There is a comprehensive list available [here](https://circuitpython.readthedocs.io/projects/bundle/en/latest/). Otherwise, to view the documentation for a specific library, you can visit the GitHub repository for the library, and find the link in the README.
For the purposes of this page, the [LED Animation library](https://github.com/adafruit/Adafruit_CircuitPython_LED_Animation) documentation will be featured. There are two links to the documentation in each library GitHub repo. The first one is the **docs badge** near the top of the README.
The second place is the **Documentation section** of the README. Scroll down to find it, and click on Read the Docs to get to the documentation.
Now that you know how to find it, it's time to take a look at what to expect.
Info:
The **Introduction** page is generated from the README, so it includes all the same info, such as PyPI installation instructions, a quick demo, and some build details. It also includes a full table of contents for the rest of the documentation (which is not part of the GitHub README). The page should look something like the following.
The left side contains links to the rest of the documentation, divided into three separate sections: **Examples** , **API Reference** , and **Other Links**.
### Examples
The [Examples section](https://circuitpython.readthedocs.io/projects/led-animation/en/latest/examples.html) is a list of library examples. This list contains anywhere from a small selection to the full list of the examples available for the library.
This section will always contain at least one example - the **simple test** example.
The simple test example is usually a basic example designed to show your setup is working. It may require other libraries to run. Keep in mind, it's _simple_ - it won't showcase a comprehensive use of all the library features.
The LED Animation simple test demonstrates the Blink animation.
In some cases, you'll find a longer list, that may include examples that explore other features in the library. The LED Animation documentation includes a series of examples, all of which are available in the library. These examples include demonstrations of both basic and more complex features. Simply click on the example that interests you to view the associated code.
Info:
You can view the rest of the examples by clicking through the list or scrolling down the page. These examples are fully working code. Which is to say, while they may rely on other libraries as well as the library for which you are viewing the documentation, they should not require modification to otherwise work.
### API Reference
The [API Reference section](https://circuitpython.readthedocs.io/projects/led-animation/en/latest/api.html) includes a list of the library functions and classes. The API (Application Programming Interface) of a library is the set of functions and classes the library provides. Essentially, the API defines how your program interfaces with the functions and classes that you call in your code to use the library.
There is always at least one list item included. Libraries for which the code is included in a single Python ( **.py** ) file, will only have one item. Libraries for which the code is multiple Python files in a directory (called subpackages) will have multiple items in this list. The LED Animation library has a series of subpackages, and therefore, multiple items in this list.
Click on the first item in the list to begin viewing the API Reference section.
Info:
When you click on an item in the API Reference section, you'll find details about the classes and functions in the library. In the case of only one item in this section, all the available functionality of the library will be contained within that first and only subsection. However, in the case of a library that has subpackages, each item will contain the features of the particular subpackage indicated by the link. The documentation will cover _all_ of the available functions of the library, including more complex ones that may not interest you.
The first list item is the animation subpackage. If you scroll down, you'll begin to see the available features of animation. They are listed alphabetically. Each of these things can be called in your code. It includes the name and a description of the specific function you would call, and if any parameters are necessary, lists those with a description as well.
You can view the other subpackages by clicking the link on the left or scrolling down the page. You may be interested in something a little more practical. Here is an example. To use the LED Animation library Comet animation, you would run the following example.
https://github.com/adafruit/Adafruit_CircuitPython_LED_Animation/blob/main/examples/led_animation_comet.py
Note the line where you create the `comet` object. There are a number of items inside the parentheses. In this case, you're provided with a fully working example. But what if you want to change how the comet works? The code alone does not explain what the options mean.
So, in the API Reference documentation list, click the `adafruit_led_animation.animation.comet` link and scroll down a bit until you see the following.
Look familiar? It is! This is the documentation for setting up the comet object. It explains what each argument provided in the comet setup in the code meant, as well as the other available features. For example, the code includes `speed=0.02`. The documentation clarifies that this is the "Animation speed in seconds". The code doesn't include `ring`. The documentation indicates this is an available setting that enables "Ring mode".
This type of information is available for any function you would set up in your code. If you need clarification on something, wonder whether there's more options available, or are simply interested in the details involved in the code you're writing, check out the documentation for the CircuitPython libraries!
### Other Links
This section is the same for every library. It includes a list of links to external sites, which you can visit for more information about the CircuitPython Project and Adafruit.
That covers the CircuitPython library documentation! When you are ready to go beyond the basic library features covered in a guide, or you're interested in understanding those features better, the library documentation on Read the Docs has you covered!
# Adafruit Fruit Jam
## Recommended Editors
The CircuitPython code on your board detects when the files are changed or written and will automatically re-start your code. This makes coding very fast because you save, and it re-runs.
**However, you must** **wait until the file is done being saved before unplugging or resetting your board!** **On Windows using some editors this can sometimes take up to** **90 seconds, on Linux it can take 30 seconds** to complete because the text editor does not save the file completely. Mac OS does not seem to have this delay, which is nice!
This is really important to be aware of. If you unplug or reset the board before your computer finishes writing the file to your board, you can corrupt the drive. If this happens, you may lose the code you've written, so it's important to backup your code to your computer regularly.
To avoid the likelihood of filesystem corruption, use an editor that writes out the file completely when you save it. Check out the list of recommended editors below.
## Recommended editors
- [**mu**](https://learn.adafruit.com/welcome-to-circuitpython/installing-mu-editor) is an editor that safely writes all changes (it's also our recommended editor!)
- [**emacs**](https://www.gnu.org/software/emacs/) is also an editor that will [fulIy write files on save](https://www.gnu.org/software/emacs/manual/html_node/emacs/Customize-Save.html)
- **[Sublime Text](https://www.sublimetext.com/) **safely writes all changes
- **[Visual Studio Code](https://code.visualstudio.com/)** appears to safely write all changes
- **gedit** on Linux appears to safely write all changes
- [IDLE](https://docs.python.org/3/library/idle.html), in Python 3.8.1 or later, [was fixed](https://bugs.python.org/issue36807) to write all changes immediately
- [Thonny](https://thonny.org/) fully writes files on save
- [Notepad++](https://notepad-plus-plus.org/) flushes files after writes, as of several years ago. In addition, you can change the path used for "Enable session snapshot and periodic backup" to write somewhere else than the CIRCUITPY drive. This will save space on CIRCUITPY and reduce writes to the drive.
## Recommended _only_ with particular settings or add-ons
- [**vim**](http://www.vim.org/) / **vi** safely writes all changes. But set up **vim** to not write [swapfiles](https://vi.stackexchange.com/a/179) (.swp files: temporary records of your edits) to **CIRCUITPY**. Run vim with `vim -n`, set the `no swapfile` option, or set the `directory` option to write swapfiles elsewhere. Otherwise the swapfile writes trigger restarts of your program.
- The **[PyCharm IDE](https://www.jetbrains.com/pycharm/)** is safe if "Safe Write" is turned on in Settings-\>System Settings-\>Synchronization (true by default).
- If you are using [**Atom**](https://atom.io/), install the [fsync-on-save package](https://atom.io/packages/fsync-on-save) or the [language-circuitpython package](https://atom.io/packages/language-circuitpython) so that it will always write out all changes to files on **CIRCUITPY**.
- [**SlickEdit**](https://www.slickedit.com/) works only if you [add a macro to flush the disk](https://forums.adafruit.com/viewtopic.php?f=57&t=144412#p713290).
Danger:
## Editors that are NOT recommended
- **notepad** (the default Windows editor) can be slow to write, so the editors above are recommended! If you are using notepad, be sure to eject the drive.
- **IDLE** in Python 3.8.0 or earlier does not force out changes immediately. Later versions do force out changes.
- **nano** (on Linux) does not force out changes.
- **geany** (on Linux) does not force out changes.
- **Anything else** - Other editors have not been tested so please use a recommended one!
# Adafruit Fruit Jam
## Advanced Serial Console on Windows
# What's the COM?
First, you'll want to find out which serial port your board is using. When you plug your board in to USB on your computer, it connects to a serial port. The port is like a door through which your board can communicate with your computer using USB.
You'll use Windows Device Manager to determine which port the board is using. The easiest way to determine which port the board is using is to first check **without** the board plugged in. Open Device Manager. Click on Ports (COM & LPT). You should find something already in that list with (COM#) after it where # is a number.
Now plug in your board. The Device Manager list will refresh and a new item will appear under Ports (COM & LPT). You'll find a different (COM#) after this item in the list.
Sometimes the item will refer to the name of the board. Other times it may be called something like USB Serial Device, as seen in the image above. Either way, there is a new (COM#) following the name. This is the port your board is using.
## Windows Serial Port Terminal Programs
- Putty is a venerable serial port connection program. More details are below.
- [Tera Term](https://teratermproject.github.io/index-en.html) is a nice terminal program. It will reconnect automatically after disconnections
- VSCode has a number of serial port extensions, such as [Serial Monitor](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-serial-monitor).
- PyCharm has a [Serial Port Monitor](https://plugins.jetbrains.com/plugin/8031-serial-port-monitor) plugin.
## Install Putty
PuTTY is a well-known choice for connecting to serial ports on Windows.
The first thing to do is download the [latest version of PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html). You'll want to download the Windows installer file. It is most likely that you'll need the 64-bit version. Download the file and install the program on your machine. If you run into issues, you can try downloading the 32-bit version instead. However, the 64-bit version will work on most PCs.
Now you need to open PuTTY.
- Under **Connection type:** choose the button next to **Serial**.
- In the box under **Serial line** , enter the serial port you found that your board is using.
- In the box under **Speed** , enter 115200. This called the baud rate, which is the speed in bits per second that data is sent over the serial connection. For boards with built in USB it doesn't matter so much but for ESP8266 and other board with a separate chip, the speed required by the board is 115200 bits per second. So you might as well just use 115200!
If you want to save those settings for later, use the options under **Load, save or delete a stored session.** Enter a name in the box under **Saved Sessions** , and click the **Save** button on the right.
Once your settings are entered, you're ready to connect to the serial console. Click "Open" at the bottom of the window. A new window will open.
If no code is running, the window will either be blank or will look like the window above. Now you're ready to see the results of your code.
Great job! You've connected to the serial console!
# Windows 7 and 8.1
If you're using Windows 7 (or 8 or 8.1), you'll need to install drivers. See the [Windows 7 and 8.1 Drivers page](https://learn.adafruit.com/welcome-to-circuitpython/windows-7-and-8-1-drivers) for details. You will not need to install drivers on Mac, Linux or Windows 10 or 11.
# Adafruit Fruit Jam
## Advanced Serial Console on Mac
Connecting to the serial console on Mac does not require installing any drivers or extra software. You'll use a terminal program to find your board, and `screen` to connect to it. Terminal and `screen` both come installed by default.
## What's the Port?
First you'll want to find out which serial port your board is using. When you plug your board in to USB on your computer, it connects to a serial port. The port is like a door through which your board can communicate with your computer using USB.
The easiest way to determine which port the board is using is to first check **without** the board plugged in. Open Terminal and type the following:
`ls /dev/tty.*`
Each serial connection shows up in the `/dev/` directory. It has a name that starts with `tty.`. The command `ls` shows you a list of items in a directory. You can use `*` as a wildcard, to search for files that start with the same letters but end in something different. In this case, you're asking to see all of the listings in `/dev/` that start with `tty.` and end in anything. This will show us the current serial connections.
Now, plug your board. In Terminal, type:
`ls /dev/tty.*`
This will show you the current serial connections, which will now include your board.
A new listing has appeared called `/dev/tty.usbmodem141441`. The `tty.usbmodem141441` part of this listing is the name the example board is using. Yours will be called something similar.
Danger: Using the `screen` terminal program can cause your CircuitPython program to hang when trying to print, if you exit `screen` after you've used it to connect.
## macOS Serial Port Terminal Programs
- `screen` is included with macOS. However, it's problematic because when it starts up, it enables the using DTR/RTS flow control signals and does not turn that off when it quits. This causes CircuitPython to block sending output when `screen` has exited, which will cause your program to stall until it is reconnected. See [this issue](https://github.com/adafruit/circuitpython/issues/10814) for a discussion.
- `tio` is a nice terminal program that works properly. You can install it with [Homebrew](https://brew.sh/).
- VSCode has a number of serial port extensions, such as [Serial Monitor](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-serial-monitor).
- PyCharm has a [Serial Port Monitor](https://plugins.jetbrains.com/plugin/8031-serial-port-monitor) plugin.
## Connect with screen
Despite the caveats above, if you can't download a better terminal program, you can use `screen`. The `screen` command is included with MacOS. To connect to the serial console, use Terminal. Type the following command, replacing `board_name` with the name you found your board is using:
`screen /dev/tty.board_name 115200`
The first part of this establishes using the `screen` command. The second part tells screen the name of the board you're trying to use. The third part tells screen what baud rate to use for the serial connection. The baud rate is the speed in bits per second that data is sent over the serial connection. In this case, the speed required by the board is 115200 bits per second.
Press enter to run the command. It will open in the same window. If no code is running, the window will be blank. Otherwise, you'll see the output of your code.
Great job! You've connected to the serial console!
# Adafruit Fruit Jam
## Advanced Serial Console on Linux
Connecting to the serial console on Linux does not require installing any drivers, but you may need to install `screen` using your package manager. You'll use a terminal program to find your board, and `screen` to connect to it. There are a variety of terminal programs such as gnome-terminal (called Terminal) or Konsole on KDE.
The `tio` program works as well to connect to your board, and has the benefit of automatically reconnecting. You would need to install it using your package manager.
## What's the Port?
First you'll want to find out which serial port your board is using. When you plug your board in to USB on your computer, it connects to a serial port. The port is like a door through which your board can communicate with your computer using USB.
The easiest way to determine which port the board is using is to first check **without** the board plugged in. Open your terminal program and type the following:
`ls /dev/ttyACM*`
Each serial connection shows up in the **/dev/** directory. It has a name that starts with **ttyACM**. The command `ls` shows you a list of items in a directory. You can use `*` as a wildcard, to search for files that start with the same letters but end in something different. In this case, You're asking to see all of the listings in **/dev/** that start with **ttyACM** `` and end in anything. This will show us the current serial connections.
In the example below, the error is indicating that are no current serial connections starting with **ttyACM**.
Now plug in your board. In your terminal program, type:
`ls /dev/ttyACM*`
This will show you the current serial connections, which will now include your board.
A new listing has appeared called **/dev/ttyACM0**. The **ttyACM0** part of this listing is the name the example board is using. Yours will be called something similar.
## Linux Serial Port Terminal Programs
- `tio` is a nice terminal program that works properly. You can install it using your package manager.
- VSCode has a number of serial port extensions, such as [Serial Monitor](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-serial-monitor).
- PyCharm has a [Serial Port Monitor](https://plugins.jetbrains.com/plugin/8031-serial-port-monitor) plugin.
## Connect with `tio`
Now that you know the name your board is using, you're ready connect to the serial console. Install `tio` using your package manager..
ype the following command, replacing `ttyACMx` with the name you found your board is using:
`tio /dev/ttyACMx`
This will connect to the serial port and display a header like this:
```terminal
$ tio /dev/ttyACM0
[11:07:00.578] tio v2.7
[11:07:00.578] Press ctrl-t q to quit
```
## Permissions on Linux
If you try to run `tio` and it doesn't work, then you may be running into an issue with permissions. Your Linux distribution may not allow access to serial ports by defaut. You may see something like this; note the "permission denied".
```terminal
[11:13:42.754] tio v2.7
[11:13:42.754] Press ctrl-t q to quit
[11:13:42.754] Warning: Could not open tty device (Permission denied)
[11:13:42.754] Waiting for tty device..
```
then you may need to grant yourself access. There are generally two ways you can do this. The first is to just run `screen` using the `sudo` command, which temporarily gives you elevated privileges.
```terminal
$ sudo tio /dev/ttyACM0
[sudo] password for smith:
```
Once you enter your password, you should be in:
The second way is to add yourself to the user group associated with the hardware. To figure out what that group is, use the command `ls -l` as shown below. The group name is circled in red.
Then use the command `adduser` to add yourself to that group. You need elevated privileges to do this, so you'll need to use `sudo`. In the example below, the group is **adm** and the user is **ackbar**.
On Debian-based distributions, such as,Ubuntu the group will be **dialout** , not **adm**.
After you add yourself to the group, you'll need to logout and log back in, or in some cases, reboot your machine. After you log in again, verify that you have been added to the group using the command `groups`. If you are still not in the group, reboot and check again.
And now you should be able to run `screen` without using `sudo`.
And you're in:
# Adafruit Fruit Jam
## Troubleshooting
From time to time, you will run into issues when working with CircuitPython. Here are a few things you may encounter and how to resolve them.
Danger:
# Always Run the Latest Version of CircuitPython and Libraries
As CircuitPython development continues and there are new releases, Adafruit will stop supporting older releases. **You need to [update to the latest CircuitPython](https://circuitpython.org/downloads).**
You need to download the CircuitPython Library Bundle that matches your version of CircuitPython. **Please update CircuitPython and then [download the latest bundle](https://circuitpython.org/libraries)**.
As new versions of CircuitPython are released, Adafruit will stop providing the previous bundles as automatically created downloads on the Adafruit CircuitPython Library Bundle repo. If you must continue to use an earlier version, you can still download the appropriate version of `mpy-cross` from the particular release of CircuitPython on the CircuitPython repo and create your own compatible .mpy library files. **However, it is best to update to the latest for both CircuitPython and the library bundle.**
## I have to continue using CircuitPython 7.x or earlier. Where can I find compatible libraries?
**Adafruit is no longer building or supporting the CircuitPython 7.x or earlier library bundles. You are highly encourged to [update CircuitPython to the latest version](https://circuitpython.org/downloads) and use [the current version of the libraries](https://circuitpython.org/libraries).** However, if for some reason you cannot update, links to the previous bundles are available in the [FAQ](https://learn.adafruit.com/welcome-to-circuitpython/frequently-asked-questions#faq-3105289).
# macOS Sonoma before 14.4: Errors Writing to CIRCUITPY macOS 14.4 - 15.1: Slow Writes to CIRCUITPY
macOS Sonoma before 14.4 took many seconds to complete writes to small FAT drives, 8MB or smaller. This causes errors when writing to CIRCUITPY. The best solution was to remount the CIRCUITPY drive after it is automatically mounted. Or consider downgrading back to Ventura if that works for you. This problem was tracked in [CircuitPython GitHub issue 8449](https://github.com/adafruit/circuitpython/issues/8449).
Below is a shell script to do this remount conveniently (courtesy [@czei in GitHub](https://github.com/adafruit/circuitpython/issues/8449#issuecomment-1779981373)). Copy the code here into a file named, say, **remount-CIRCUITPY.sh**. Place the file in a directory on your PATH, or in some other convenient place.
macOS Sonoma 14.4 and versions of macOS before Sequoia 15.2 did not have the problem above, but did take an inordinately long time to write to FAT drives of size 1GB or less (40 times longer than 2GB drives). As of macOS 15.2, writes are no longer very slow. This problem was tracked in [CircuitPython GitHub issue 8918](https://github.com/adafruit/circuitpython/issues/8918).
```auto
#!/bin/sh
#
# This works around bug where, by default,
# macOS 14.x before 14.4 writes part of a file immediately,
# and then doesn't update the directory for 20-60 seconds, causing
# the file system to be corrupted.
#
disky=`df | grep CIRCUITPY | cut -d" " -f1`
sudo umount /Volumes/CIRCUITPY
sudo mkdir /Volumes/CIRCUITPY
sleep 2
sudo mount -v -o noasync -t msdos $disky /Volumes/CIRCUITPY
```
Then in a Terminal window, do this to make this script executable:
```terminal
chmod +x remount-CIRCUITPY.sh
```
Place the file in a directory on your `PATH`, or in some other convenient place.
Now, each time you plug in or reset your CIRCUITPY board, run the file **remount-CIRCUITPY.sh**. You can run it in a Terminal window or you may be able to place it on the desktop or in your dock to run it just by double-clicking.
This will be something of a nuisance but it is the safest solution.
This problem is being tracked in [this CircuitPython issue](https://github.com/adafruit/circuitpython/issues/8449).
# Bootloader (_boardname_BOOT) Drive Not Present
### **You may have a different board.**
Only Adafruit Express boards and the SAMD21 non-Express boards ship with the [UF2 bootloader](../../../adafruit-feather-m0-express-designed-for-circuit-python-circuitpython/uf2-bootloader?view=all#uf2-bootloader)installed. The Feather M0 Basic, Feather M0 Adalogger, and similar boards use a regular Arduino-compatible bootloader, which does not show a **_boardname_BOOT** drive.
### **MakeCode**
If you are running a [MakeCode](../../../makecode/sharing-and-saving?view=all#step-1-bootloader-mode) program on Circuit Playground Express, press the reset button just once to get the **CPLAYBOOT** drive to show up. Pressing it twice will not work.
### **macOS**
**DriveDx** and its accompanything **SAT SMART Driver** can interfere with seeing the BOOT drive. [See this forum post](https://forums.adafruit.com/viewtopic.php?f=58&t=161917&p=799309#p799215) for how to fix the problem.
### **Windows 10 or later**
Did you install the Adafruit Windows Drivers package by mistake, or did you upgrade to Windows 10 or later with the driver package installed? You don't need to install this package on Windows 10 or 11for most Adafruit boards. The old version (v1.5) can interfere with recognizing your device. Go to **Settings** -\> **Apps** and uninstall all the "Adafruit" driver programs.
### **Windows 7 or 8.1**
Windows 7 and 8.1 have reached end of life. It is [recommended](https://learn.adafruit.com/welcome-to-circuitpython/installing-circuitpython#windows-7-and-8-dot-1-drivers-2977910-9) that you upgrade to Windows 10 or 11 if possible. Drivers are available for some older CircuitPython boards, but there are no plans to release drivers for newer boards.
Info: The Windows Drivers installer was last updated in November 2020 (v2.5.0.0) . Windows 7 drivers for CircuitPython boards released since then, including RP2040 boards, are not available. There are no plans to release drivers for newer boards. The boards work fine on Windows 10 and later.
You should now be done! Test by unplugging and replugging the board. You should see the **CIRCUITPY** drive, and when you double-click the reset button (single click on Circuit Playground Express running MakeCode), you should see the appropriate **_boardname_BOOT** drive.
Let us know in the [Adafruit support forums](https://forums.adafruit.com) or on the [Adafruit Discord](https://adafru.it/discord) if this does not work for you!
# Windows Explorer Locks Up When Accessing **_boardname_BOOT** Drive
On Windows, several third-party programs that can cause issues. The symptom is that you try to access the **_boardname_BOOT** drive, and Windows or Windows Explorer seems to lock up. These programs are known to cause trouble:
- **AIDA64** : to fix, stop the program. This problem has been reported to AIDA64. They acquired hardware to test, and released a beta version that fixes the problem. This may have been incorporated into the latest release. Please let us know in the forums if you test this.
- **BitDefender anti-virus**
- **Hard Disk Sentinel**
- **Kaspersky anti-virus** : To fix, you may need to disable Kaspersky completely. Disabling some aspects of Kaspersky does not always solve the problem. This problem has been reported to Kaspersky.
- **ESET NOD32 anti-virus** : There have been problems with at least version 9.0.386.0, solved by uninstallation.
# Copying UF2 to **_boardname_BOOT** Drive Hangs at 0% Copied
On Windows, a **Western DIgital (WD) utility** that comes with their external USB drives can interfere with copying UF2 files to the **_boardname_BOOT** drive. Uninstall that utility to fix the problem.
# CIRCUITPY Drive Does Not Appear or Disappears Quickly
**BitDefender anti-virus has been reported to block access to** **CIRCUITPY**. You can set an exception for the drive letter.
Kaspersky **anti-virus** can block the appearance of the **CIRCUITPY** drive. There has not yet been settings change discovered that prevents this. Complete uninstallation of Kaspersky fixes the problem.
**Norton anti-virus** can interfere with **CIRCUITPY**. A user has reported this problem on Windows 7. The user turned off both Smart Firewall and Auto Protect, and **CIRCUITPY** then appeared.
**Sophos Endpoint** security software [can cause CIRCUITPY to disappear](https://forums.adafruit.com/viewtopic.php?f=60&t=187629) and the BOOT drive to reappear. It is not clear what causes this behavior.
**Samsung Magician** can cause CIRCUITPY to disappear (reported [here](https://forums.adafruit.com/viewtopic.php?t=205159) and [here](https://forums.adafruit.com/viewtopic.php?p=987596#p987596)).
## "M105" Seen on Display, Crashes, Missing CIRCUITPY
The **Cura** 3D printing program sends 3D printing GCODE commands to unused serial ports to try to find 3D printers connected over serial. This causes a variety of problems. Disable (uncheck) **USB Printing** in Cura in the **Market** -\> **Installed** menu, or uninstall Cura. For more information see [this forum post](https://forums.adafruit.com/viewtopic.php?t=192784), [this CircuitPython issue](https://github.com/adafruit/circuitpython/issues/2585), and [this Cura issue](https://github.com/Ultimaker/Cura/issues/5207).
# Device Errors or Problems on Windows
Windows can become confused about USB device installations. Try cleaning up your USB devices. Use [Uwe Sieber's Device Cleanup Tool](https://www.uwe-sieber.de/misc_tools_e.html) (on that page, scroll down to "Device Cleanup Tool"). Download and unzip the tool. Unplug all the boards and other USB devices you want to clean up. Run the tool as Administrator. You will see a listing like this, probably with many more devices. It is listing all the USB devices that are _not_ currently attached.
Select all the devices you want to remove, and then press Delete. It is usually safe just to select everything. Any device that is removed will get a fresh install when you plug it in. Using the Device Cleanup Tool also discards all the COM port assignments for the unplugged boards. If you have used many Arduino and CircuitPython boards, you have probably seen higher and higher COM port numbers used, seemingly without end. This will fix that problem.
# Serial Console in Mu Not Displaying Anything
There are times when the serial console will accurately not display anything, such as, when no code is currently running, or when code with no serial output is already running before you open the console. However, if you find yourself in a situation where you feel it should be displaying something like an error, consider the following.
Depending on the size of your screen or Mu window, when you open the serial console, the serial console panel may be very small. This can be a problem. A basic CircuitPython error takes 10 lines to display!
```
Auto-reload is on. Simply save files over USB to run them or enter REPL to disable.
code.py output:
Traceback (most recent call last):
File "code.py", line 7
SyntaxError: invalid syntax
Press any key to enter the REPL. Use CTRL-D to reload.
```
More complex errors take even more lines!
Therefore, if your serial console panel is five lines tall or less, you may only see blank lines or blank lines followed by `Press any key to enter the REPL. Use CTRL-D to reload.`. If this is the case, you need to either mouse over the top of the panel to utilise the option to resize the serial panel, or use the scrollbar on the right side to scroll up and find your message.
This applies to any kind of serial output whether it be error messages or print statements. So before you start trying to debug your problem on the hardware side, be sure to check that you haven't simply missed the serial messages due to serial output panel height.
# code.py Restarts Constantly
CircuitPython will restart **code.py** if you or your computer writes to something on the CIRCUITPY drive. This feature is called _auto-reload_, and lets you test a change to your program immediately.
Some utility programs, such as backup, anti-virus, or disk-checking apps, will write to the CIRCUITPY as part of their operation. Sometimes they do this very frequently, causing constant restarts.
**Acronis True Image** and related Acronis programs on Windows are known to cause this problem. It is possible to prevent this by [disabling the "](https://forum.acronis.com/forum/acronis-true-image-2018-forum/acronis-ati-2018-contantly-touch-usb-port-causing-issue-adafruit-circuitpython-folder)[Acronis Managed Machine Service Mini"](https://forum.acronis.com/forum/acronis-true-image-2018-forum/acronis-ati-2018-contantly-touch-usb-port-causing-issue-adafruit-circuitpython-folder).
If you cannot stop whatever is causing the writes, you can disable auto-reload by putting this code in **boot.py** or **code.py** :
```python
import supervisor
supervisor.runtime.autoreload = False
```
# CircuitPython RGB Status Light
Nearly all CircuitPython-capable boards have a single NeoPixel or DotStar RGB LED on the board that indicates the status of CircuitPython. A few boards designed before CircuitPython existed, such as the Feather M0 Basic, do not.
**Circuit Playground Express and Circuit Playground Bluefruit have multiple RGB LEDs, but do NOT have a status LED. The LEDs are all green when in the bootloader. In versions before 7.0.0, they do NOT indicate any status while running CircuitPython.**
## **CircuitPython 7.0.0 and Later**
The status LED blinks were changed in CircuitPython 7.0.0 in order to save battery power and simplify the blinks. These blink patterns will occur on single color LEDs when the board does not have any RGB LEDs. Speed and blink count also vary for this reason.
On start up, the LED will blink **YELLOW** multiple times for 1 second. Pressing the RESET button (or on Espressif, the BOOT button) during this time will restart the board and then enter safe mode. On Bluetooth capable boards, after the yellow blinks, there will be a set of faster blue blinks. Pressing reset during the **BLUE** blinks will clear Bluetooth information and start the device in discoverable mode, so it can be used with a BLE code editor.
Once started, CircuitPython will blink a pattern every 5 seconds when no user code is running to indicate why the code stopped:
- 1 **GREEN** blink: Code finished without error.
- 2 **RED** blinks: Code ended due to an exception. Check the serial console for details.
- 3 **YELLOW** blinks: CircuitPython is in safe mode. No user code was run. Check the serial console for safe mode reason.
When in the REPL, CircuitPython will set the status LED to **WHITE**. You can change the LED color from the REPL. The status indicator will not persist on non-NeoPixel or DotStar LEDs.
## **CircuitPython 6.3.0 and earlier**
Here's what the colors and blinking mean:
- steady **GREEN** : **code.py** (or **code.txt** , **main.py** , or **main.txt** ) is running
- pulsing **GREEN** : **code.py** (etc.) has finished or does not exist
- steady **YELLOW** at start up: (4.0.0-alpha.5 and newer) CircuitPython is waiting for a reset to indicate that it should start in safe mode
- pulsing **YELLOW** : Circuit Python is in safe mode: it crashed and restarted
- steady **WHITE** : REPL is running
- steady **BLUE** : **boot.py** is running
Colors with multiple flashes following indicate a Python exception and then indicate the line number of the error. The color of the first flash indicates the type of error:
- **GREEN** : IndentationError
- **CYAN** : SyntaxError
- **WHITE** : NameError
- **ORANGE** : OSError
- **PURPLE** : ValueError
- **YELLOW** : other error
These are followed by flashes indicating the line number, including place value. **WHITE** flashes are thousands' place, **BLUE** are hundreds' place, **YELLOW** are tens' place, and **CYAN** are one's place. So for example, an error on line 32 would flash **YELLOW** three times and then **CYAN** two times. Zeroes are indicated by an extra-long dark gap.
# Serial console showing `ValueError: Incompatible .mpy file`
This error occurs when importing a module that is stored as a **.mpy** binary file that was generated by a different version of CircuitPython than the one its being loaded into. In particular, the mpy binary format changed between CircuitPython versions 6.x and 7.x, 2.x and 3.x, and 1.x and 2.x.
So, for instance, if you upgraded to CircuitPython 7.x from 6.x you’ll need to download a newer version of the library that triggered the error on `import`. All libraries are available in the [Adafruit bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases/latest).
# CIRCUITPY Drive Issues
You may find that you can no longer save files to your **CIRCUITPY** drive. You may find that your **CIRCUITPY** stops showing up in your file explorer, or shows up as **NO\_NAME**. These are indicators that your filesystem has issues. When the **CIRCUITPY** disk is not safely ejected before being reset by the button or being disconnected from USB, it may corrupt the flash drive. It can happen on Windows, Mac or Linux, though it is more common on Windows.
Be aware, if you have used Arduino to program your board, CircuitPython is no longer able to provide the USB services. You will need to reload CircuitPython to resolve this situation.
The easiest first step is to reload CircuitPython. Double-tap reset on the board so you get a **_boardname_BOOT** drive rather than a **CIRCUITPY** drive, and copy the latest version of CircuitPython ( **.uf2** ) back to the board. This may restore **CIRCUITPY** functionality.
If reloading CircuitPython does not resolve your issue, the next step is to try putting the board into safe mode.
## Safe Mode
Whether you've run into a situation where you can no longer edit your **code.py** on your **CIRCUITPY** drive, your board has gotten into a state where **CIRCUITPY** is read-only, or you have turned off the **CIRCUITPY** drive altogether, safe mode can help.
**Safe mode** in CircuitPython does not run any user code on startup, and disables auto-reload. This means a few things. First, safe mode _bypasses any code in_ **boot.py** (where you can set **CIRCUITPY** read-only or turn it off completely). Second, _it does not run the code in_ **code.py**. And finally, _it does not automatically soft-reload when data is written to the_ **CIRCUITPY** _drive_.
Therefore, whatever you may have done to put your board in a non-interactive state, safe mode gives you the opportunity to correct it without losing all of the data on the **CIRCUITPY** drive.
### Entering Safe Mode in CircuitPython 7.x and Later
You can enter safe by pressing reset during the right time when the board boots. Immediately after the board starts up or resets, it waits one second. On some boards, the onboard status LED will blink yellow during that time. If you press reset during that one second period, the board will start up in safe mode. It can be difficult to react to the yellow LED, so you may want to think of it simply as a "slow" double click of the reset button. (Remember, a fast double click of reset enters the bootloader.)
### Entering Safe Mode in CircuitPython 6.x
You can enter safe by pressing reset during the right time when the board boots.. Immediately after the board starts up or resets, it waits 0.7 seconds. On some boards, the onboard status LED (highlighted in green above) will turn solid yellow during this time. If you press reset during that 0.7 seconds, the board will start up in safe mode. It can be difficult to react to the yellow LED, so you may want to think of it simply as a slow double click of the reset button. (Remember, a fast double click of reset enters the bootloader.)
### In Safe Mode
Once you've entered safe mode successfully in CircuitPython 6.x, the LED will pulse yellow.
If you successfully enter safe mode on CircuitPython 7.x, the LED will intermittently blink yellow three times.
If you connect to the serial console, you'll find the following message.
```terminal
Auto-reload is off.
Running in safe mode! Not running saved code.
CircuitPython is in safe mode because you pressed the reset button during boot. Press again to exit safe mode.
Press any key to enter the REPL. Use CTRL-D to reload.
```
You can now edit the contents of the **CIRCUITPY** drive. Remember, _your code will not run until you press the reset button, or unplug and plug in your board, to get out of safe mode._
At this point, you'll want to remove any user code in **code.py** and, if present, the **boot.py** file from **CIRCUITPY**. Once removed, tap the reset button, or unplug and plug in your board, to restart CircuitPython. This will restart the board and may resolve your drive issues. If resolved, you can begin coding again as usual.
If safe mode does not resolve your issue, the board must be completely erased and CircuitPython must be reloaded onto the board.
Danger:
## To erase CIRCUITPY: `storage.erase_filesystem()`
CircuitPython includes a built-in function to erase and reformat the filesystem. If you have a version of CircuitPython older than 2.3.0 on your board, you can [update to the newest version](../../../../welcome-to-circuitpython/installing-circuitpython) to do this.
1. [Connect to the CircuitPython REPL](../../../../welcome-to-circuitpython/kattni-connecting-to-the-serial-console) using Mu or a terminal program.
2. Type the following into the REPL:
```terminal
>>> import storage
>>> storage.erase_filesystem()
```
CIRCUITPY will be erased and reformatted, and your board will restart. That's it!
## Erase CIRCUITPY Without Access to the REPL
If you can't access the REPL, or you're running a version of CircuitPython previous to 2.3.0 and you don't want to upgrade, there are options available for some specific boards.
**The options listed below are considered to be the "old way" of erasing your board. The method shown above using the REPL is highly recommended as the best method for erasing your board.**
Warning:
## For the specific boards listed below:
If the board you are trying to erase is listed below, follow the steps to use the file to erase your board.
1. Download the correct erase file:
[Circuit Playground Express](https://cdn-learn.adafruit.com/assets/assets/000/048/745/original/flash_erase_express.ino.circuitplay.uf2?1512152080)
[Feather M0 Express](https://cdn-learn.adafruit.com/assets/assets/000/048/746/original/flash_erase_express.ino.feather_m0_express.uf2?1512152098)
[Feather M4 Express](https://cdn-learn.adafruit.com/assets/assets/000/076/217/original/flash_erase.ino.feather_m4.uf2)
[Metro M0 Express](https://cdn-learn.adafruit.com/assets/assets/000/048/747/original/flash_erase_express.ino.metro_m0.uf2?1512152103)
[Metro M4 Express QSPI Eraser](https://cdn-learn.adafruit.com/assets/assets/000/073/820/original/Metro_M4_QSPI_Eraser.UF2?1553805937)
[Trellis M4 Express (QSPI)](https://cdn-learn.adafruit.com/assets/assets/000/067/535/original/Trellis_M4_QSPI_Eraser.UF2?1544719380)
[Grand Central M4 Express (QSPI)](https://cdn-learn.adafruit.com/assets/assets/000/069/314/original/GC_M4_QSPI_Erase.UF2?1547404471)
[PyPortal M4 Express (QSPI)](https://cdn-learn.adafruit.com/assets/assets/000/072/252/original/PYPORTAL_QSPI_Eraser.UF2?1551738305)
[Circuit Playground Bluefruit (QSPI)](https://cdn-learn.adafruit.com/assets/assets/000/082/950/original/CP_Bluefruit_QSPI_Erase.UF2?1572026649)
[Monster M4SK (QSPI)](https://cdn-learn.adafruit.com/assets/assets/000/083/330/original/M4SK_QSPI_Eraser.UF2?1572551433)
[PyBadge/PyGamer QSPI Eraser.UF2](https://cdn-learn.adafruit.com/assets/assets/000/083/331/original/PyBadge_QSPI_Eraser.UF2?1572551613)
[CLUE_Flash_Erase.UF2](https://cdn-learn.adafruit.com/assets/assets/000/088/454/original/CLUE_Flash_Erase.UF2?1581873830)
[Matrix_Portal_M4_(QSPI).UF2](https://cdn-learn.adafruit.com/assets/assets/000/098/741/original/Matrix_Portal_M4_%28QSPI%29.UF2?1611076081)
[RP2040 boards (flash_nuke.uf2)](https://cdn-learn.adafruit.com/assets/assets/000/101/659/original/flash_nuke.uf2)
2. Double-click the reset button on the board to bring up the **_boardname_BOOT** drive.
3. Drag the erase **.uf2** file to the **_boardname_BOOT** drive.
4. The status LED will turn yellow or blue, indicating the erase has started.
5. After approximately 15 seconds, the status LED will light up green. On the NeoTrellis M4 this is the first NeoPixel on the grid
6. Double-click the reset button on the board to bring up the **_boardname_BOOT** drive.
7. [Drag the appropriate latest release of CircuitPython](https://circuitpython.org/downloads) **.uf2** file to the **_boardname_BOOT** drive.
It should reboot automatically and you should see **CIRCUITPY** in your file explorer again.
If the LED flashes red during step 5, it means the erase has failed. Repeat the steps starting with 2.
[If you haven't already downloaded the latest release of CircuitPython for your board, check out the installation page](../../../../welcome-to-circuitpython/installing-circuitpython). You'll also need to load your code and reinstall your libraries!
## For SAMD21 non-Express boards that have a UF2 bootloader:
Any SAMD21-based microcontroller that does not have external flash available is considered a SAMD21 non-Express board. Non-Express boards that have a UF2 bootloader include Trinket M0, GEMMA M0, QT Py M0, and the SAMD21-based Trinkey boards.
If you are trying to erase a SAMD21 non-Express board, follow these steps to erase your board.
1. Download the erase file:
[SAMD21 non-Express Boards](https://cdn-learn.adafruit.com/assets/assets/000/048/748/original/erase_m0.uf2)
2. Double-click the reset button on the board to bring up the **_boardname_BOOT** drive.
3. Drag the erase **.uf2** file to the **_boardname_BOOT** drive.
4. The boot LED will start flashing again, and the **_boardname_BOOT** drive will reappear.
5. [Drag the appropriate latest release CircuitPython](https://circuitpython.org/downloads) **.uf2** file to the _boardname_BOOT drive.
It should reboot automatically and you should see **CIRCUITPY** in your file explorer again.
[If you haven't already downloaded the latest release of CircuitPython for your board, check out the installation page](../../../../welcome-to-circuitpython/installing-circuitpython) YYou'll also need to load your code and reinstall your libraries!
## For SAMD21 non-Express boards that do not have a UF2 bootloader:
Any SAMD21-based microcontroller that does not have external flash available is considered a SAMD21 non-Express board. Non-Express boards that do **not** have a UF2 bootloader include the Feather M0 Basic Proto, Feather Adalogger, or the Arduino Zero.
If you are trying to erase a non-Express board that does not have a UF2 bootloader, [follow these directions to reload CircuitPython using `bossac`](../../../../welcome-to-circuitpython/non-uf2-installation), which will erase and re-create **CIRCUITPY**.
# Running Out of File Space on SAMD21 Non-Express Boards
Any SAMD21-based microcontroller that does not have external flash available is considered a SAMD21 non-Express board. This includes boards like the Trinket M0, GEMMA M0, QT Py M0, and the SAMD21-based Trinkey boards.
The file system on the board is very tiny. (Smaller than an ancient floppy disk.) So, its likely you'll run out of space but don't panic! There are a number of ways to free up space.
## Delete something!
The simplest way of freeing up space is to delete files from the drive. Perhaps there are libraries in the **lib** folder that you aren't using anymore or test code that isn't in use. Don't delete the **lib** folder completely, though, just remove what you don't need.
The board ships with the Windows 7 serial driver too! Feel free to delete that if you don't need it or have already installed it. It's ~12KiB or so.
## Use tabs
One unique feature of Python is that the indentation of code matters. Usually the recommendation is to indent code with four spaces for every indent. In general, that is recommended too. **However** , one trick to storing more human-readable code is to use a single tab character for indentation. This approach uses 1/4 of the space for indentation and can be significant when you're counting bytes.
## On macOS?
MacOS loves to generate hidden files. Luckily you can disable some of the extra hidden files that macOS adds by running a few commands to disable search indexing and create zero byte placeholders. Follow the steps below to maximize the amount of space available on macOS.
## Prevent & Remove macOS Hidden Files
First find the volume name for your board. With the board plugged in run this command in a terminal to list all the volumes:
```
ls -l /Volumes
```
Look for a volume with a name like **CIRCUITPY** (the default for CircuitPython). The full path to the volume is the **/Volumes/CIRCUITPY** path.
Now follow the [steps from this question](http://apple.stackexchange.com/questions/6707/how-to-stop-os-x-from-writing-spotlight-and-trash-files-to-memory-cards-and-usb/7135#7135) to run these terminal commands that stop hidden files from being created on the board:
```terminal
mdutil -i off /Volumes/CIRCUITPY
cd /Volumes/CIRCUITPY
rm -rf .{,_.}{fseventsd,Spotlight-V*,Trashes}
mkdir .fseventsd
touch .fseventsd/no_log .metadata_never_index .Trashes
cd -
```
Replace **/Volumes/CIRCUITPY** in the commands above with the full path to your board's volume if it's different. At this point all the hidden files should be cleared from the board and some hidden files will be prevented from being created.
Alternatively, with CircuitPython 4.x and above, the special files and folders mentioned above will be created automatically if you erase and reformat the filesystem. **WARNING: Save your files first!** Do this in the REPL:
`>>> import storage`
`>>> storage.erase_filesystem()`
However there are still some cases where hidden files will be created by MacOS. In particular if you copy a file that was downloaded from the internet it will have special metadata that MacOS stores as a hidden file. Luckily you can run a copy command from the terminal to copy files **without** this hidden metadata file. See the steps below.
## Copy Files on macOS Without Creating Hidden Files
Once you've disabled and removed hidden files with the above commands on macOS you need to be careful to copy files to the board with a special command that prevents future hidden files from being created. Unfortunately you **cannot** use drag and drop copy in Finder because it will still create these hidden extended attribute files in some cases (for files downloaded from the internet, like Adafruit's modules).
To copy a file or folder use the **-X** option for the **cp** command in a terminal. For example to copy a **file\_name.mpy** file to the board use a command like:
```terminal
cp -X file_name.mpy /Volumes/CIRCUITPY
```
(Replace **file\_name.mpy** with the name of the file you want to copy.)
Or to copy a folder and all of the files and folders contained within, use a command like:
```terminal
cp -rX folder_to_copy /Volumes/CIRCUITPY
```
If you are copying to the **lib** folder, or another folder, make sure it exists before copying.
```terminal
# if lib does not exist, you'll create a file named lib !
cp -X file_name.mpy /Volumes/CIRCUITPY/lib
# This is safer, and will complain if a lib folder does not exist.
cp -X file_name.mpy /Volumes/CIRCUITPY/lib/
```
## Other macOS Space-Saving Tips
If you'd like to see the amount of space used on the drive and manually delete hidden files here's how to do so. First, move into the **Volumes/** directory with `cd /Volumes/`, and then list the amount of space used on the **CIRCUITPY** drive with the `df` command.
That's not very much space left! The next step is to show a list of the files currently on the **CIRCUITPY** drive, _including_ the hidden files, using the `ls` command. You cannot use Finder to do this, you must do it via command line!
There are a few of the hidden files that MacOS loves to generate, all of which begin with a **.\_** before the file name. Remove the **.\_** files using the `rm` command. You can remove them all once by running `rm CIRCUITPY/._*`. The `*` acts as a _wildcard_ to apply the command to everything that begins with **.\_** at the same time.
Finally, you can run `df` again to see the current space used.
Nice! You have 12Ki more than before! This space can now be used for libraries and code!
# Device Locked Up or Boot Looping
In rare cases, it may happen that something in your **code.py** or **boot.py** files causes the device to get locked up, or even go into a boot loop. A _boot loop_ occurs when the board reboots repeatedly and never fully loads. These are not caused by your everyday Python exceptions, typically it's the result of a deeper problem within CircuitPython. In this situation, it can be difficult to recover your device if **CIRCUITPY** is not allowing you to modify the **code.py** or **boot.py** files. Safe mode is one recovery option. When the device boots up in safe mode it will not run the **code.py** or **boot.py** scripts, but will still connect the **CIRCUITPY** drive so that you can remove or modify those files as needed.
For more information on safe mode and how to enter safe mode, see the [Safe Mode section on this page](https://learn.adafruit.com/welcome-to-circuitpython/troubleshooting#safe-mode-3105351).
# Adafruit Fruit Jam
## Frequently Asked Questions
These are some of the common questions regarding CircuitPython and CircuitPython microcontrollers.
###
What are some common acronyms to know?
CP or CPy = [CircuitPython](https://circuitpython.org)
CPC = [Circuit Playground Classic](https://www.adafruit.com/product/3000) (does not run CircuitPython)
CPX = [Circuit Playground Express](https://www.adafruit.com/product/3333)
CPB = [Circuit Playground Bluefruit](https://www.adafruit.com/product/4333)
## Using Older Versions
Danger:
### I have to continue using CircuitPython 8.x or earlier. Where can I find compatible libraries?
**We are no longer building or supporting the CircuitPython 8.x or earlier library bundles. We highly encourage you to [update CircuitPython to the latest version](https://circuitpython.org/downloads) and use [the current version of the libraries](https://circuitpython.org/libraries).** However, if for some reason you cannot update, here are the last available library bundles for older versions:
- [2.x bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases/download/20190903/adafruit-circuitpython-bundle-2.x-mpy-20190903.zip)
- [3.x bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases/download/20190903/adafruit-circuitpython-bundle-3.x-mpy-20190903.zip)
- [4.x bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases/download/20200707/adafruit-circuitpython-bundle-4.x-mpy-20200707.zip)
- [5.x bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases/download/20210129/adafruit-circuitpython-bundle-5.x-mpy-20210129.zip)
- [6.x bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases/download/20211213/adafruit-circuitpython-bundle-6.x-mpy-20211213.zip)
- [7.x bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases/download/20231003/adafruit-circuitpython-bundle-7.x-mpy-20231003.zip)
- [8.x bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases/download/20250213/adafruit-circuitpython-bundle-8.x-mpy-20250213.zip)
## Python Arithmetic
###
Does CircuitPython support floating-point numbers?
All CircuitPython boards support floating point arithmetic, even if the microcontroller chip does not support floating point in hardware. Floating point numbers are stored in 30 bits, with an 8-bit exponent and a 22-bit mantissa. Note that this is two bits less than standard 32-bit single-precision floats. You will get about 5-1/2 digits of decimal precision.
(The **broadcom** port may provide 64-bit floats in some cases.)
###
Does CircuitPython support long integers, like regular Python?
Python long integers (integers of arbitrary size) are available on most builds, except those on boards with the smallest available firmware size. On these boards, integers are stored in 31 bits.
Boards without long integer support are mostly SAMD21 ("M0") boards without an external flash chip, such as the Adafruit Gemma M0, Trinket M0, QT Py M0, and the Trinkey series. There are also a number of third-party boards in this category. There are also a few small STM third-party boards without long integer support.
`time.localtime()`, `time.mktime()`, `time.time()`, and `time.monotonic_ns()` are available only on builds with long integers.
## Wireless Connectivity
###
How do I connect to the Internet with CircuitPython?
If you'd like to include WiFi in your project, your best bet is to use a board that is running natively on ESP32 chipsets - those have WiFi built in!
If your development board has an SPI port and at least 4 additional pins, you can check out [this guide](https://learn.adafruit.com/adafruit-io-basics-airlift) on using AirLift with CircuitPython - extra wiring is required and some boards like the MacroPad or NeoTrellis do not have enough available pins to add the hardware support.
For further project examples, and guides about using AirLift with specific hardware, check out [the Adafruit Learn System](https://learn.adafruit.com/search?q=airlift).
### How do I do BLE (Bluetooth Low Energy) with CircuitPython?
nRF52840, nRF52833, and **as of CircuitPython 9.1.0** , ESP32, ESP32-C3, and ESP32-S3 boards (with 8MB) have the most complete BLE implementation. Your program can act as both a BLE central and peripheral. As a central, you can scan for advertisements, and connect to an advertising board. As a peripheral, you can advertise, and you can create services available to a central. Pairing and bonding are supported.
**Most Espressif boards with only 4MB of flash do not have enough room to include BLE in CircuitPython 9.** Check the [Module Support Matrix](https://docs.circuitpython.org/en/latest/shared-bindings/support_matrix.html) to see if your board has support for `_bleio`. CircuitPython 10 is planned to support `_bleio` on Espressif boards with 4MB flash.
Note that the ESP32-S2 does not have Bluetooth capability.
On most other boards with adequate firmware space, [BLE is available for use with AirLift](https://learn.adafruit.com/adafruit-airlift-breakout/circuitpython-ble) or other NINA-FW-based co-processors. Some boards have this coprocessor on board, such as the [PyPortal](https://learn.adafruit.com/adafruit-pyportal/circuitpython-ble). Currently, this implementation only supports acting as a BLE peripheral. Scanning and connecting as a central are not yet implemented. Bonding and pairing are not supported.
###
Are there other ways to communicate by radio with CircuitPython?
Check out [Adafruit's RFM boards](https://www.adafruit.com/?q=rfm&sort=BestMatch)for simple radio communication supported by CircuitPython, which can be used over distances of 100m to over a km, depending on the version. The RFM SAMD21 M0 boards can be used, but they were not designed for CircuitPython, and have limited RAM and flash space; using the RFM breakouts or FeatherWings with more capable boards will be easier.
## Asyncio and Interrupts
###
Is there asyncio support in CircuitPython?
There is support for asyncio starting with CircuitPython 7.1.0, on all boards except the smallest SAMD21 builds. Read about using it in the [Cooperative Multitasking in CircuitPython](https://learn.adafruit.com/cooperative-multitasking-in-circuitpython) Guide.
###
Does CircuitPython support interrupts?
No. CircuitPython does not currently support interrupts - please use asyncio for multitasking / 'threaded' control of your code
## Status RGB LED
###
My RGB NeoPixel/DotStar LED is blinking funny colors - what does it mean?
The status LED can tell you what's going on with your CircuitPython board. [Read more here for what the colors mean!](https://learn.adafruit.com/welcome-to-circuitpython/troubleshooting#circuitpython-rgb-status-light-2978455-24)
## Memory Issues
###
What is a MemoryError?
Memory allocation errors happen when you're trying to store too much on the board. The CircuitPython microcontroller boards have a limited amount of memory available. You can have about 250 lines of code on the M0 Express boards. If you try to `import` too many libraries, a combination of large libraries, or run a program with too many lines of code, your code will fail to run and you will receive a `MemoryError` in the serial console.
###
What do I do when I encounter a MemoryError?
Try resetting your board. Each time you reset the board, it reallocates the memory. While this is unlikely to resolve your issue, it's a simple step and is worth trying.
Make sure you are using **.mpy** versions of libraries. All of the CircuitPython libraries are available in the bundle in a **.mpy** format which takes up less memory than **.py** format. Be sure that you're using [the latest library bundle](https://github.com/adafruit/Adafruit_CircuitPython_Bundle/releases) for your version of CircuitPython.
If that does not resolve your issue, try shortening your code. Shorten comments, remove extraneous or unneeded code, or any other clean up you can do to shorten your code. If you're using a lot of functions, you could try moving those into a separate library, creating a **.mpy** of that library, and importing it into your code.
You can turn your entire file into a **.mpy** and `import` that into **code.py**. This means you will be unable to edit your code live on the board, but it can save you space.
###
Can the order of my .mpy files?
You can make your own **.mpy** versions of files with `mpy-cross`.
You can download **mpy-cross** for your operating system from [here](https://adafruit-circuit-python.s3.amazonaws.com/index.html?prefix=bin/mpy-cross/). Builds are available for Windows, macOS, x64 Linux, and Raspberry Pi Linux. Choose the latest **mpy-cross** whose version matches the version of CircuitPython you are using.
On macOS and Linux, after you download **mpy-cross** , you must make the the file executable by doing `chmod +x name-of-the-mpy-cross-executable`.
To make a **.mpy** file, run `./mpy-cross path/to/yourfile.py` to create a **yourfile.mpy** in the same directory as the original file.
###
How do I check how much memory I have free?
Run the following to see the number of bytes available for use:
`import gc`
`gc.mem_free()`
## Unsupported Hardware
###
Is ESP8266 or ESP32 supported in CircuitPython? Why not?
We dropped ESP8266 support as of 4.x - For more information please read about it [here](https://learn.adafruit.com/welcome-to-circuitpython/circuitpython-for-esp8266)!
[As of CircuitPython 8.x we have started to support ESP32 and ESP32-C3 and have added a WiFi workflow for wireless coding!](https://learn.adafruit.com/circuitpython-with-esp32-quick-start)
We also support ESP32-S2 & ESP32-S3, which have native USB.
###
Does Feather M0 support WINC1500?
No, WINC1500 will not fit into the M0 flash space.
###
Can AVRs such as ATmega328 or ATmega2560 run CircuitPython?
No.
# Adafruit Fruit Jam
## Welcome to the Community!
CircuitPython is a programming language that's super simple to get started with and great for learning. It runs on microcontrollers and works out of the box. You can plug it in and get started with any text editor. The best part? CircuitPython comes with an amazing, supportive community.
Everyone is welcome! CircuitPython is Open Source. This means it's available for anyone to use, edit, copy and improve upon. This also means CircuitPython becomes better because of you being a part of it. Whether this is your first microcontroller board or you're a seasoned software engineer, you have something important to offer the Adafruit CircuitPython community. This page highlights some of the many ways you can be a part of it!
## Adafruit Discord
The Adafruit Discord server is the best place to start. Discord is where the community comes together to volunteer and provide live support of all kinds. From general discussion to detailed problem solving, and everything in between, Discord is a digital maker space with makers from around the world.
There are many different channels so you can choose the one best suited to your needs. Each channel is shown on Discord as "#channelname". There's the #help-with-projects channel for assistance with your current project or help coming up with ideas for your next one. There's the #show-and-tell channel for showing off your newest creation. Don't be afraid to ask a question in any channel! If you're unsure, #general is a great place to start. If another channel is more likely to provide you with a better answer, someone will guide you.
The help with CircuitPython channel is where to go with your CircuitPython questions. #help-with-circuitpython is there for new users and developers alike so feel free to ask a question or post a comment! Everyone of any experience level is welcome to join in on the conversation. Your contributions are important! The #circuitpython-dev channel is available for development discussions as well.
The easiest way to contribute to the community is to assist others on Discord. Supporting others doesn't always mean answering questions. Join in celebrating successes! Celebrate your mistakes! Sometimes just hearing that someone else has gone through a similar struggle can be enough to keep a maker moving forward.
The Adafruit Discord is the 24x7x365 hackerspace that you can bring your granddaughter to.
Visit [https://adafru.it/discord](https://adafru.it/discord)to sign up for Discord. Everyone is looking forward to meeting you!
## CircuitPython.org
Beyond the Adafruit Learn System, which you are viewing right now, the best place to find information about CircuitPython is [circuitpython.org](https://circuitpython.org). Everything you need to get started with your new microcontroller and beyond is available. You can do things like [download CircuitPython for your microcontroller](https://circuitpython.org/downloads) or [download the latest CircuitPython Library bundle](https://circuitpython.org/libraries), or check out [which single board computers support Blinka](https://circuitpython.org/blinka). You can also get to various other CircuitPython related things like Awesome CircuitPython or the Python for Microcontrollers newsletter. This is all incredibly useful, but it isn't necessarily community related. So why is it included here? The [Contributing page](https://circuitpython.org/contributing).
CircuitPython itself is written in C. However, all of the Adafruit CircuitPython libraries are written in _Python_. If you're interested in contributing to CircuitPython on the Python side of things, check out [circuitpython.org/contributing](https://circuitpython.org/contributing). You'll find information pertaining to every Adafruit CircuitPython library GitHub repository, giving you the opportunity to join the community by finding a contributing option that works for you.
Note the date on the page next to **Current Status for** :
If you submit any contributions to the libraries, and do not see them reflected on the Contributing page, it could be that the job that checks for new updates hasn't yet run for today. Simply check back tomorrow!
Now, a look at the different options.
### Pull Requests
The first tab you'll find is a list of **open pull requests**.
GitHub pull requests, or PRs, are opened when folks have added something to an Adafruit CircuitPython library GitHub repo, and are asking for Adafruit to add, or merge, their changes into the main library code. For PRs to be merged, they must first be reviewed. Reviewing is a great way to contribute! Take a look at the list of open pull requests, and pick one that interests you. If you have the hardware, you can test code changes. If you don't, you can still check the code updates for syntax. In the case of documentation updates, you can verify the information, or check it for spelling and grammar. Once you've checked out the update, you can leave a comment letting us know that you took a look. Once you've done that for a while, and you're more comfortable with it, you can consider joining the CircuitPythonLibrarians review team. The more reviewers we have, the more authors we can support. Reviewing is a crucial part of an open source ecosystem, CircuitPython included.
### Open Issues
The second tab you'll find is a list of **open issues**.
GitHub issues are filed for a number of reasons, including when there is a bug in the library or example code, or when someone wants to make a feature request. Issues are a great way to find an opportunity to contribute directly to the libraries by updating code or documentation. If you're interested in contributing code or documentation, take a look at the open issues and find one that interests you.
If you're not sure where to start, you can search the issues by label. Labels are applied to issues to make the goal easier to identify at a first glance, or to indicate the difficulty level of the issue. Click on the dropdown next to "Sort by issue labels" to see the list of available labels, and click on one to choose it.
If you're new to everything, new to contributing to open source, or new to contributing to the CircuitPython project, you can choose "Good first issue". Issues with that label are well defined, with a finite scope, and are intended to be easy for someone new to figure out.
If you're looking for something a little more complicated, consider "Bug" or "Enhancement". The Bug label is applied to issues that pertain to problems or failures found in the library. The Enhancement label is applied to feature requests.
Don't let the process intimidate you. If you're new to Git and GitHub, there is [a guide](https://learn.adafruit.com/contribute-to-circuitpython-with-git-and-github) to walk you through the entire process. As well, there are always folks available on [Discord](https:adafru.it/discord) to answer questions.
### Library Infrastructure Issues
The third tab you'll find is a list of **library infrastructure issues**.
This section is generated by a script that runs checks on the libraries, and then reports back where there may be issues. It is made up of a list of subsections each containing links to the repositories that are experiencing that particular issue. This page is available mostly for internal use, but you may find some opportunities to contribute on this page. If there's an issue listed that sounds like something you could help with, mention it on Discord, or file an issue on GitHub indicating you're working to resolve that issue. Others can reply either way to let you know what the scope of it might be, and help you resolve it if necessary.
### CircuitPython Localization
The fourth tab you'll find is the **CircuitPython Localization** tab.
If you speak another language, you can help translate CircuitPython! The translations apply to informational and error messages that are within the CircuitPython core. It means that folks who do not speak English have the opportunity to have these messages shown to them in their own language when using CircuitPython. This is incredibly important to provide the best experience possible for all users. CircuitPython uses Weblate to translate, which makes it much simpler to contribute translations. You will still need to know some CircuitPython-specific practices and a few basics about coding strings, but as with any CircuitPython contributions, folks are there to help.
Regardless of your skill level, or how you want to contribute to the CircuitPython project, there is an opportunity available. The [Contributing page](https://circuitpython.org/contributing) is an excellent place to start!
## Adafruit GitHub
Whether you're just beginning or are life-long programmer who would like to contribute, there are ways for everyone to be a part of the CircuitPython project. The CircuitPython core is written in C. The libraries are written in Python. GitHub is the best source of ways to contribute to the [CircuitPython core](https://github.com/adafruit/circuitpython), and the [CircuitPython libraries](https://circuitpython.org/contributing/open-issues). If you need an account, visit [https://github.com/](https://github.com/) and sign up.
If you're new to GitHub or programming in general, there are great opportunities for you. For the CircuitPython core, head over to the CircuitPython repository on GitHub, click on "[Issues](https://github.com/adafruit/circuitpython/issues)", and you'll find a list that includes issues labeled "[good first issue](https://github.com/adafruit/circuitpython/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)". For the libraries, head over to the [Contributing page Issues list](https://circuitpython.org/contributing/open-issues), and use the drop down menu to search for "[good first issue](https://circuitpython.org/contributing/open-issues?label=good-first-issue)". These issues are things that have been identified as something that someone with any level of experience can help with. These issues include options like updating documentation, providing feedback, and fixing simple bugs. If you need help getting started with GitHub, there is an excellent guide on [Contributing to CircuitPython with Git and GitHub](https://learn.adafruit.com/contribute-to-circuitpython-with-git-and-github).
Already experienced and looking for a challenge? Checkout the rest of either issues list and you'll find plenty of ways to contribute. You'll find all sorts of things, from new driver requests, to library bugs, to core module updates. There's plenty of opportunities for everyone at any level!
When working with or using CircuitPython or the CircuitPython libraries, you may find problems. If you find a bug, that's great! The team loves bugs! Posting a detailed issue to GitHub is an invaluable way to contribute to improving CircuitPython. For CircuitPython itself, file an issue [here](https://github.com/adafruit/circuitpython/issues). For the libraries, file an issue on the specific library repository on GitHub. Be sure to include the steps to replicate the issue as well as any other information you think is relevant. The more detail, the better!
Testing new software is easy and incredibly helpful. Simply load the newest version of CircuitPython or a library onto your CircuitPython hardware, and use it. Let us know about any problems you find by posting a new issue to GitHub. Software testing on both stable and unstable releases is a very important part of contributing CircuitPython. The developers can't possibly find all the problems themselves! They need your help to make CircuitPython even better.
On GitHub, you can submit feature requests, provide feedback, report problems and much more. If you have questions, remember that Discord and the Forums are both there for help!
## Adafruit Forums
The [Adafruit Forums](https://forums.adafruit.com) are the perfect place for support. Adafruit has wonderful paid support folks to answer any questions you may have. Whether your hardware is giving you issues or your code doesn't seem to be working, the forums are always there for you to ask. You need an Adafruit account to post to the forums. You can use the same account you use to order from Adafruit.
While Discord may provide you with quicker responses than the forums, the forums are a more reliable source of information. If you want to be certain you're getting an Adafruit-supported answer, the forums are the best place to be.
There are forum categories that cover all kinds of topics, including everything Adafruit. The [Adafruit CircuitPython](https://forums.adafruit.com/viewforum.php?f=60) category under "Supported Products & Projects" is the best place to post your CircuitPython questions.
Be sure to include the steps you took to get to where you are. If it involves wiring, post a picture! If your code is giving you trouble, include your code in your post! These are great ways to make sure that there's enough information to help you with your issue.
You might think you're just getting started, but you definitely know something that someone else doesn't. The great thing about the forums is that you can help others too! Everyone is welcome and encouraged to provide constructive feedback to any of the posted questions. This is an excellent way to contribute to the community and share your knowledge!
## Read the Docs
[Read the Docs](https://circuitpython.readthedocs.io/) is a an excellent resource for a more detailed look at the CircuitPython core and the CircuitPython libraries. This is where you'll find things like API documentation and example code. For an in depth look at viewing and understanding Read the Docs, check out the [CircuitPython Documentation](https://learn.adafruit.com/welcome-to-circuitpython/circuitpython-documentation) page!
# Adafruit Fruit Jam
## CircuitPython Essentials
You've been introduced to CircuitPython, and worked through getting everything set up. What's next? CircuitPython Essentials!
There are a number of core modules built into CircuitPython, which can be used along side the many CircuitPython libraries available. The following pages demonstrate some of these modules. Each page presents a different concept including a code example with an explanation. All of the examples are designed to work with your microcontroller board.
Time to get started learning the CircuitPython essentials!
Some examples require external components, such as switches or sensors. You'll find wiring diagrams where applicable to show you how to wire up the necessary components to work with each example.
The following components are needed to complete all of the examples:
### STEMMA Wired Potentiometer Breakout Board - 10K ohm Linear
[STEMMA Wired Potentiometer Breakout Board - 10K ohm Linear](https://www.adafruit.com/product/4493)
For the easiest way possible to measure twists, turn to this STEMMA potentiometer breakout (ha!). This plug-n-play pot comes with a JST-PH 2mm connector and a matching [JST PH 3-Pin to Male Header Cables - 200mm](https://www.adafruit.com/product/3893), so wiring up is a cinch....
Out of Stock
[Buy Now](https://www.adafruit.com/product/4493)
[Related Guides to the Product](https://learn.adafruit.com/products/4493/guides)
### HDMI Cable - 1 meter
[HDMI Cable - 1 meter](https://www.adafruit.com/product/608)
Connect two HDMI devices together with this basic HDMI cable. It has nice molded grips for easy installation, and is 1 meter long (about 3 feet). This is a HDMI 1.3 cable.
We're now stocking a very fancy Official Raspberry Pi cable with overmolding and a Pi logo. Please note...
In Stock
[Buy Now](https://www.adafruit.com/product/608)
[Related Guides to the Product](https://learn.adafruit.com/products/608/guides)
### Mini Chiclet Keyboard - USB Wired - Black
[Mini Chiclet Keyboard - USB Wired - Black](https://www.adafruit.com/product/1736)
Add a good quality, slim keyboard to your Raspberry Pi, Beagle Bone Black, or other single-board-computer with this sleek black chiclet keyboard. It's a full QWERTY keyboard with a USB cable and is compatible with all operating systems. We tried many keyboards to find one that felt...
In Stock
[Buy Now](https://www.adafruit.com/product/1736)
[Related Guides to the Product](https://learn.adafruit.com/products/1736/guides)
### Adafruit AHT20 - Temperature & Humidity Sensor Breakout Board
[Adafruit AHT20 - Temperature & Humidity Sensor Breakout Board](https://www.adafruit.com/product/4566)
The AHT20 is a nice but inexpensive temperature and humidity sensor [from the same folks that brought us the DHT22](https://www.adafruit.com/product/385). You can take sensor readings as often as you like, and it uses standard I2C so its super easy to use with any Arduino or...
In Stock
[Buy Now](https://www.adafruit.com/product/4566)
[Related Guides to the Product](https://learn.adafruit.com/products/4566/guides)
### STEMMA QT / Qwiic JST SH 4-Pin Cable - 50mm Long
[STEMMA QT / Qwiic JST SH 4-Pin Cable - 50mm Long](https://www.adafruit.com/product/4399)
This 4-wire cable is 50mm / 1.9" long and fitted with JST SH female 4-pin connectors on both ends. Compared with the chunkier JST PH these are 1mm pitch instead of 2mm, but still have a nice latching feel, while being easy to insert and remove.
Out of Stock
[Buy Now](https://www.adafruit.com/product/4399)
[Related Guides to the Product](https://learn.adafruit.com/products/4399/guides)
### 64MB Micro SD Memory Card
[64MB Micro SD Memory Card](https://www.adafruit.com/product/5249)
Add storage in a jiffy using this **64MB microSD card**. Preformatted to FAT32, so it works out of the packaging with our projects. Works great with any device in the Adafruit shop that uses microSD cards. Ideal for use with Feathers, data loggers, or small Linux SBCs (not good...
In Stock
[Buy Now](https://www.adafruit.com/product/5249)
[Related Guides to the Product](https://learn.adafruit.com/products/5249/guides)
# Adafruit Fruit Jam
## Blink
In learning any programming language, you often begin with some sort of `Hello, World!` program. In CircuitPython, Hello, World! is blinking an LED. Blink is one of the simplest programs in CircuitPython. It involves three built-in modules, two lines of set up, and a short loop. Despite its simplicity, it shows you many of the basic concepts needed for most CircuitPython programs, and provides a solid basis for more complex projects. Time to get blinky!
## LED Location
The built-in red LED is between the USB C plug and the SDCard slot.
## Blinking an LED
In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, open the directory **CircuitPython\_Templates/blink/** and then click on the directory that matches the version of CircuitPython you're using and copy the contents of that directory to your **CIRCUITPY** drive.
Your **CIRCUITPY** drive should now look similar to the following image:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/CircuitPython_Templates/blink/code.py
The built-in LED begins blinking!
Note that the code is a little less "Pythonic" than it could be. It could also be written as `led.value = not led.value` with a single `time.sleep(0.5)`. That way is more difficult to understand if you're new to programming, so the example is a bit longer than it needed to be to make it easier to read.
It's important to understand what is going on in this program.
First you `import` three modules: `time`, `board` and `digitalio`. This makes these modules available for use in your code. All three are built-in to CircuitPython, so you don't need to download anything to get started.
Next, you set up the LED. To interact with hardware in CircuitPython, your code must let the board know where to look for the hardware and what to do with it. So, you create a `digitalio.DigitalInOut()` object, provide it the LED pin using the `board` module, and save it to the variable `led`. Then, you tell the pin to act as an `OUTPUT`.
Finally, you create a `while True:` loop. This means all the code inside the loop will repeat indefinitely. Inside the loop, you set `led.value = True` which powers on the LED. Then, you use `time.sleep(0.5)` to tell the code to wait half a second before moving on to the next line. The next line sets `led.value = False` which turns the LED off. Then you use another `time.sleep(0.5)` to wait half a second before starting the loop over again.
With only a small update, you can control the blink speed. The blink speed is controlled by the amount of time you tell the code to wait before moving on using `time.sleep()`. The example uses `0.5`, which is one half of one second. Try increasing or decreasing these values to see how the blinking changes.
That's all there is to blinking an LED using CircuitPython!
# Adafruit Fruit Jam
## Digital Input
The CircuitPython `digitalio` module has many applications. The basic Blink program sets up the LED as a digital output. You can just as easily set up a **digital input** such as a button to control the LED. This example builds on the basic Blink example, but now includes setup for a button switch. Instead of using the `time` module to blink the LED, it uses the status of the button switch to control whether the LED is turned on or off.
## LED and Button
## Controlling the LED with a Button
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_Digital_Input/code.py
Now, press the button. The LED lights up! Let go of the button and the LED turns off.
Note that the code is a little less "Pythonic" than it could be. It could also be written as `led.value = not button.value`. That way is more difficult to understand if you're new to programming, so the example is a bit longer than it needed to be to make it easier to read.
First you `import` two modules: `board` and `digitalio`. This makes these modules available for use in your code. Both are built-in to CircuitPython, so you don't need to download anything to get started.
Next, you set up the LED. To interact with hardware in CircuitPython, your code must let the board know where to look for the hardware and what to do with it. So, you create a `digitalio.DigitalInOut()` object, provide it the LED pin using the `board` module, and save it to the variable `led`. Then, you tell the pin to act as an `OUTPUT`.
You include setup for the button as well. It is similar to the LED setup, except the button is an `INPUT`, and requires a pull up.
Inside the loop, you check to see if the button is pressed, and if so, turn on the LED. Otherwise the LED is off.
That's all there is to controlling an LED with a button switch!
# Adafruit Fruit Jam
## Analog Input
Your microcontroller board has both digital and analog signal capabilities. Some pins are analog, some are digital, and some are capable of both. Check the **Pinouts** page in this guide for details about your board.
Analog signals are different from digital signals in that they can be _any_ voltage and can vary continuously and smoothly between voltages. An analog signal is like a dimmer switch on a light, whereas a digital signal is like a simple on/off switch.
Digital signals only can ever have two states, they are either are **on** (high logic level voltage like 3.3V) or **off** (low logic level voltage like 0V / ground).
By contrast, analog signals can be any voltage in-between on and off, such as 1.8V or 0.001V or 2.98V and so on.
Analog signals are continuous values which means they can be an _infinite_ number of different voltages. Think of analog signals like a floating point or fractional number, they can smoothly transiting to _any_ in-between value like 1.8V, 1.81V, 1.801V, 1.8001V, 1.80001V and so forth to infinity.
Many devices use analog signals, in particular sensors typically output an analog signal or voltage that varies based on something being sensed like light, heat, humidity, etc.
## Analog to Digital Converter (ADC)
An analog-to-digital-converter, or ADC, is the key to reading analog signals and voltages with a microcontroller. An ADC is a device that reads the voltage of an analog signal and converts it into a digital, or numeric, value. The microcontroller can’t read analog signals directly, so the analog signal is first converted into a numeric value by the ADC.
The black line below shows a digital signal over time, and the red line shows the converted analog signal over the same amount of time.
Once that analog signal has been converted by the ADC, the microcontroller can use those digital values any way you like!
## Potentiometers
A potentiometer is a small variable resistor that you can twist a knob or shaft to change its resistance. It has three pins. By twisting the knob on the potentiometer you can change the resistance of the middle pin (called the wiper) to be anywhere within the range of resistance of the potentiometer.
By wiring the potentiometer to your board in a special way (called a voltage divider) you can turn the change in resistance into a change in voltage that your board’s analog to digital converter can read.
To wire up a potentiometer as a voltage divider:
- Connect **one outside pin** to **ground**
- Connect **the other outside pin** to **voltage in (e.g. 3.3V)**
- Connect **the middle pin** to **an analog pin (e.g. A0)**
## Hardware
In addition to your microcontroller board, you will need the following hardware to follow along with this example.
**Potentiometer**
### STEMMA Wired Potentiometer Breakout Board - 10K ohm Linear
[STEMMA Wired Potentiometer Breakout Board - 10K ohm Linear](https://www.adafruit.com/product/4493)
For the easiest way possible to measure twists, turn to this STEMMA potentiometer breakout (ha!). This plug-n-play pot comes with a JST-PH 2mm connector and a matching [JST PH 3-Pin to Male Header Cables - 200mm](https://www.adafruit.com/product/3893), so wiring up is a cinch....
Out of Stock
[Buy Now](https://www.adafruit.com/product/4493)
[Related Guides to the Product](https://learn.adafruit.com/products/4493/guides)
## Wire Up the Potentiometer
Connect the potentiometer to your board as follows.
- **Potentiometer GND** to **Fruit Jam GND (black wire)**
- **Potentiometer wiper** to **Fruit Jam A0 (white wire)**
- **Potentiometer positive** to **Fruit Jam 3.3V (red wire)**
## Reading Analog Pin Values
CircuitPython makes it easy to read analog pin values. Simply import two modules, set up the pin, and then print the value inside a loop.
You'll need to [connect to the serial console](https://learn.adafruit.com/welcome-to-circuitpython/kattni-connecting-to-the-serial-console) to see the values printed out.
In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, open the directory **CircuitPython\_Templates/analog\_pin\_values/** and then click on the directory that matches the version of CircuitPython you're using and copy the contents of that directory to your **CIRCUITPY** drive.
Your **CIRCUITPY** drive should now look similar to the following image:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/CircuitPython_Templates/analog_pin_values/code.py
Now, rotate the potentiometer to see the values change.
What do these values mean? In CircuitPython ADC values are put into the range of 16-bit unsigned values. This means the possible values you’ll read from the ADC fall within the range of 0 to 65535 (or 2^16 - 1). When you twist the potentiometer knob to be near ground, or as far to the left as possible, you see a value close to zero. When you twist it as far to the right as possible, near 3.3 volts, you see a value close to 65535. You’re seeing almost the full range of 16-bit values!
The code is simple. You begin by importing three modules: `time`, `board` and `analogio`. All three modules are built into CircuitPython, so you don't need to download anything to get started.
Then, you set up the analog pin by creating an `analogio.AnalogIn()` object, providing it the desired pin using the `board` module, and saving it to the variable `analog_pin`.
Finally, in the loop, you print out the analog value with `analog_pin.value`, including a `time.sleep()` to slow down the values to a human-readable rate.
## Reading Analog Voltage Values
These values don't necessarily equate to anything obvious. You can get an idea of the rotation of the potentiometer based on where in the range the value falls, but not without doing some math. Remember, you wired up the potentiometer as a voltage divider. By adding a simple function to your code, you can get a more human-readable value from the potentiometer.
You'll need to [connect to the serial console](https://learn.adafruit.com/welcome-to-circuitpython/kattni-connecting-to-the-serial-console) to see the values printed out.
In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, open the directory **CircuitPython\_Templates/analog\_voltage\_values/** and then click on the directory that matches the version of CircuitPython you're using and copy the contents of that directory to your **CIRCUITPY** drive.
Your **CIRCUITPY** drive should now look similar to the following image:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/CircuitPython_Templates/analog_voltage_values/code.py
Now, rotate the potentiometer to see the values change.
Now the values range from around 0 to 3.3! Note that you may not get all the way to 0 or 3.3. This is normal.
The example code begins with the same imports and pin setup.
This time, you include the `get_voltage` helper. This function requires that you provide an analog pin. It then maps the raw analog values, `0` to `65535`, to the voltage values, `0` to `3.3`. It does the math so you don't have to!
Finally, inside the loop, you provide the function with your `analog_pin`, and print the resulting values.
That's all there is to reading analog voltage values using CircuitPython!
# Adafruit Fruit Jam
## NeoPixels
Your board has built-in RGB NeoPixel status LEDs. You can use CircuitPython code to control the color and brightness of these LEDs. They are also used to indicate the bootloader status and errors in your CircuitPython code.
A NeoPixel is what Adafruit calls the WS281x family of addressable RGB LEDs. It contains three LEDs - a red one, a green one and a blue one - along side a driver chip in a tiny package controlled by a single pin. They can be used individually or chained together in strips (as in the built-in LEDs on your board) or other creative form factors. NeoPixels do not light up on their own; they require a microcontroller. So, it's super convenient that the NeoPixels are built in to your microcontroller board!
This page will cover using CircuitPython to control the status RGB NeoPixels built into your microcontroller. You'll learn how to change the color and brightness, and how to make a rainbow. Time to get started!
## NeoPixels Location
## NeoPixel Color and Brightness
To use with CircuitPython, you need to first install a few libraries, into the **lib** folder on your **CIRCUITPY** drive. Then you need to update **code.py** with the example script.
Thankfully, we can do this in one go. In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, open the directory **CircuitPython\_Templates/status\_led\_multi\_neopixel\_rgb/** and then click on the directory that matches the version of CircuitPython you're using and copy the contents of that directory to your **CIRCUITPY** drive.
Your **CIRCUITPY** drive should now look similar to the following image:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_NeoPixels_RGB/code.py
The built-in NeoPixel begins blinking red, then green, then blue, and repeats!
First you import two modules, `time` and `board`, and one library, `neopixel`. This makes these modules and libraries available for use in your code. The first two are modules built-in to CircuitPython, so you don't need to download anything to use those. The `neopixel` library is separate, which is why you needed to install it before getting started.
Next, you set up the NeoPixel LED. To interact with hardware in CircuitPython, your code must let the board know where to look for the hardware and what to do with it. So, you create a `neopixel.NeoPixel()` object, provide it the NeoPixel LED pin using the `board` module, and tell it the number of LEDs. You save this object to the variable `pixel`.
Then, you set the NeoPixel brightness using the `brightness` attribute. `brightness` expects float between `0` and `1.0`. A _float_ is essentially a number with a decimal in it. The brightness value represents a percentage of maximum brightness; `0` is 0% and `1.0` is 100%. Therefore, setting `pixel.brightness = 0.3` sets the brightness to 30%. The default brightness, which is to say the brightness if you don't explicitly set it, is `1.0`. The default is really bright! That is why there is an option available to easily change the brightness.
Inside the loop, you turn the NeoPixels red for 0.5 seconds, green for 0.5 seconds, and blue for 0.5 seconds.
To turn the NeoPixels red, you "fill" it with an RGB value. Check out the section below for details on RGB colors. The RGB value for red is `(255, 0, 0)`. Note that the RGB value includes the parentheses. The `fill()` attribute expects the full RGB value including those parentheses. That is why there are two pairs of parentheses in the code.
You can change the RGB values to change the colors that the NeoPixel cycles through. Check out the list below for some examples. You can make any color of the rainbow with the right RGB value combination!
That's all there is to changing the color and setting the brightness of the built-in NeoPixel LEDs!
## RGB LED Colors
RGB LED colors are set using a combination of **r** ed, **g** reen, and **b** lue, in the form of an ( **R** , **G** , **B** ) tuple. Each member of the tuple is set to a number between 0 and 255 that determines the amount of each color present. Red, green and blue in different combinations can create all the colors in the rainbow! So, for example, to set an LED to red, the tuple would be `(255, 0, 0)`, which has the maximum level of red, and no green or blue. Green would be `(0, 255, 0)`, etc. For the colors between, you set a combination, such as cyan which is `(0, 255, 255)`, with equal amounts of green and blue. If you increase all values to the same level, you get white! If you decrease all the values to 0, you turn the LED off.
Common colors include:
- red: `(255, 0, 0)`
- green: `(0, 255, 0)`
- blue: `(0, 0, 255)`
- cyan: `(0, 255, 255)`
- purple: `(255, 0, 255)`
- yellow: `(255, 255, 0)`
- white: `(255, 255, 255)`
- black (off): `(0, 0, 0)`
## NeoPixel Rainbow
You should have already installed the library necessary to use the built-in NeoPixel LEDs. If not, follow the steps at the beginning of the NeoPixel Color and Brightness section to install it.
In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, open the directory **CircuitPython\_Templates/status\_led\_multi\_neopixel\_rainbow/** and then click on the directory that matches the version of CircuitPython you're using and copy the contents of that directory to your **CIRCUITPY** drive.
Your **CIRCUITPY** drive should now look similar to the following image:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_NeoPixels_Rainbow/code.py
The NeoPixels display a rainbow cycle!
This example builds on the previous example.
First, you import the same three modules and libraries. In addition to those, you import `colorwheel`.
The NeoPixel hardware setup and brightness setting are the same.
Next, you have the `rainbow()` helper function. This helper displays the rainbow cycle. It expects a `delay` in seconds. The higher the number of seconds provided for `delay`, the slower the rainbow will cycle. The helper cycles through the values of the color wheel to create a rainbow of colors.
Inside the loop, you call the rainbow helper with a 0.2 second delay, by including `rainbow(0.2)`.
That's all there is to making rainbows using the built-in NeoPixel LEDs!
# Adafruit Fruit Jam
## I2C
The **I2C** , or [inter-integrated circuit](https://en.wikipedia.org/wiki/I%C2%B2C), is a 2-wire protocol for communicating with simple sensors and devices, which means it uses two connections, or wires, for transmitting and receiving data. One connection is a clock, called **SCL**. The other is the data line, called **SDA**. Each pair of clock and data pins are referred to as a **bus**.
Typically, there is a device that acts as a **controller** and sends requests to the **target** devices on each bus. In this case, your microcontroller board acts as the controller, and the sensor breakout acts as the target. Historically, the controller is referred to as the master, and the target is referred to as the slave, so you may run into that terminology elsewhere. The official terminology is [controller and target](https://adafruit.com/controller-peripheral).
**Multiple I2C devices can be connected to the same clock and data lines.** Each I2C device has an address, and as long as the addresses are different, you can connect them at the same time. This means you can have many different sensors and devices all connected to the same two pins.
**Both I2C connections require pull-up resistors** , and most Adafruit I2C sensors and breakouts have pull-up resistors built in. If you're using one that does not, you'll need to add your own 2.2-10kΩ pull-up resistors from SCL and SDA to 3.3V.
## I2C and CircuitPython
CircuitPython supports many I2C devices, and makes it super simple to interact with them. There are libraries available for many I2C devices in the [CircuitPython Library Bundle](https://circuitpython.readthedocs.io/projects/bundle/en/latest/#table-of-contents). (If you don't see the sensor you're looking for, keep checking back, more are being written all the time!)
In this section, you'll learn how to scan the I2C bus for all connected devices. Then you'll learn how to interact with an I2C device.
## Necessary Hardware
You'll need the following additional hardware to complete the examples on this page.
### Adafruit AHT20 - Temperature & Humidity Sensor Breakout Board
[Adafruit AHT20 - Temperature & Humidity Sensor Breakout Board](https://www.adafruit.com/product/4566)
The AHT20 is a nice but inexpensive temperature and humidity sensor [from the same folks that brought us the DHT22](https://www.adafruit.com/product/385). You can take sensor readings as often as you like, and it uses standard I2C so its super easy to use with any Arduino or...
In Stock
[Buy Now](https://www.adafruit.com/product/4566)
[Related Guides to the Product](https://learn.adafruit.com/products/4566/guides)
### STEMMA QT / Qwiic JST SH 4-Pin Cable - 50mm Long
[STEMMA QT / Qwiic JST SH 4-Pin Cable - 50mm Long](https://www.adafruit.com/product/4399)
This 4-wire cable is 50mm / 1.9" long and fitted with JST SH female 4-pin connectors on both ends. Compared with the chunkier JST PH these are 1mm pitch instead of 2mm, but still have a nice latching feel, while being easy to insert and remove.
Out of Stock
[Buy Now](https://www.adafruit.com/product/4399)
[Related Guides to the Product](https://learn.adafruit.com/products/4399/guides)
While the examples here will be using the [Adafruit AHT20](https://www.adafruit.com/product/4566), a temperature and humidity sensor, the overall process is the same for just about any I2C sensor or device.
The first thing you'll want to do is get the sensor connected so your board has I2C to talk to.
## Wiring the AHT20
The AHT20 comes with a STEMMA QT connector, which makes wiring it up quite simple and solder-free.
Simply connect the STEMMA QT cable from **the STEMMA QT port on your Fruit Jam** to **the STEMMA QT port on the AHT20**.
## Find Your Sensor
The first thing you'll want to do after getting the sensor wired up, is make sure it's wired correctly. You're going to do an I2C scan to see if the board is detected, and if it is, print out its I2C address.
Save the following to your **CIRCUITPY** drive as **code.py**.
Click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, find your CircuitPython version, and copy the matching **code.py** file to your **CIRCUITPY** drive.
Your **CIRCUITPY** drive should now look similar to the following image:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/CircuitPython_Templates/i2c_scan/code.py
The Fruit Jam comes with a few I2C devices built in: the **TLV320DAC3100** , and up to 3 EDID I2C devices depending on the display connected to the DVI port. The I2C scan code will show the address from the built-in TLV320DAC3100 DAC ( **0x18** ), the AHT20 ( **0x38** ), and possibly EDID addresses ( **0x50** ), ( **0x3a** ), and ( **0x54** ).
Primary: The EDID (Extended Display Identification Data) was developed by industry to help computers figure out if the display can support certain resolutions. In each monitor that supports EDID is a chip accessible by I2C via DVI/HDMI and later display standards. One can simply look to see if device **0x50** is on that I2C bus and if so, read the data structure defined by the standard. With the EDID data, a program can try to set the graphics to a particular resolution to use or give a message that the resolution the program wants isn't one the display can support. For more on EDID and CircuitPython, see [this guide](https://learn.adafruit.com/using-dvi-video-in-circuitpython/monitor-display-capabilities).
Info: The Fruit Jam comes with a few I2C devices built in: the TLV320DAC3100 DAC for audio, and possible EDID I2C devices. The I2C scan code will show the addresses from the built in DAC, the AHT20, and possibly EDID.
If you run this and it seems to hang, try manually unlocking your I2C bus by running the following two commands from the REPL.
```python
import board
board.I2C().unlock()
```
First you create the `i2c` object, using `board.I2C()`. This convenience routine creates and saves a `busio.I2C` object using the default pins `board.SCL` and `board.SDA`. If the object has already been created, then the existing object is returned. No matter how many times you call `board.I2C()`, it will return the same object. This is called a _singleton_.
To be able to scan it, you need to lock the I2C down so the only thing accessing it is the code. So next you include a loop that waits until I2C is locked and then continues on to the scan function.
Last, you have the loop that runs the actual scan, `i2c_scan()`. Because I2C typically refers to addresses in hex form, the example includes this bit of code that formats the results into hex format: `[hex(device_address) for device_address in i2c.scan()]`.
Open the serial console to see the results! The code prints out an array of addresses. You've connected the AHT20 which has a 7-bit I2C address of 0x38. The result for these sensors is `I2C addresses found: ['0x38', '0x3a', '0x50', '0x54']`. If `0x38` is not in the list returned, refer back to the wiring diagrams to make sure you've wired up your sensor correctly.
## I2C Sensor Data
Now you know for certain that your sensor is connected and ready to go. Time to find out how to get the data from the sensor!
Save the following to your **CIRCUITPY** drive as **code.py**.
Click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, find your CircuitPython version, and copy the matching **entire** **lib** **folder** and **code.py** file to your **CIRCUITPY** drive.
Your **CIRCUITPY** drive should now look similar to the following image:
https://github.com/adafruit/Adafruit_CircuitPython_AHTx0/blob/main/examples/ahtx0_simpletest.py
This code begins the same way as the scan code, except this time, you create your sensor object using the sensor library. You call it `sensor` and provide it the `i2c` object.
Then you have a simple loop that prints out the temperature reading using the sensor object you created. Finally, there's a `time.sleep(2)`, so it only prints once every two seconds. Connect to the serial console to see the results. Try touching the AHT20 with your finger to see the values change!
## Where's my I2C?
On many microcontrollers, you have the flexibility of using a wide range of pins for I2C. On some types of microcontrollers, any pin can be used for I2C! Other chips require using `bitbangio`, but can also use any pins for I2C. There are further microcontrollers that may have fixed I2C pins.
Given the many different types of microcontroller boards available, it's impossible to guarantee anything other than the labeled 'SDA' and 'SCL' pins. So, if you want some other setup, or multiple I2C interfaces, how will you find those pins? Easy! Below is a handy script.
Save the following to your **CIRCUITPY** drive as **code.py**.
Click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, find your CircuitPython version, and copy the matching **code.py** file to your **CIRCUITPY** drive.
Your **CIRCUITPY** drive should now look similar to the following image:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_I2C_Find_Pins/code.py
Now, connect to the serial console and check out the output! The results print out a nice handy list of SCL and SDA pin pairs that support I2C.
Primary: The output for the Fruit Jam is extremely long! The screenshot shows only the beginning. Run the script yourself to see the full output!
Info:
# Adafruit Fruit Jam
## I2S Audio
It's easy to play audio on the Fruit Jam with CircuitPython thanks to the built-in **TLV320DAC3100** DAC and the [Adafruit\_CircuitPython\_FruitJam](https://github.com/adafruit/Adafruit_CircuitPython_FruitJam) module. This module allows you to easily write Python code to play audio and wave files (.wav) from the headphone jack or speaker connector.
## Fruit Jam Speaker Wiring
The Fruit Jam supports playing audio out of the 3.5mm stereo jack to headphones or powered speakers, or using a small mono 4-8Ω speaker connected to the JST-SH speaker connector.
### USB Powered Speakers
[USB Powered Speakers](https://www.adafruit.com/product/1363)
Add some extra boom to your audio project with these powered loudspeakers. We sampled half a dozen different models to find ones with a good frequency response, so you'll get quality audio output for music playback. Simply connect the standard 3.5mm stereo plug into your Raspberry Pi model...
In Stock
[Buy Now](https://www.adafruit.com/product/1363)
[Related Guides to the Product](https://learn.adafruit.com/products/1363/guides)
### Mini Oval Speaker - 8 Ohm 1 Watt
[Mini Oval Speaker - 8 Ohm 1 Watt](https://www.adafruit.com/product/3923)
Hear the good news! This wee speaker is a great addition to any audio project where you need 8 ohm impedance and 1W or less of power. We particularly like this speaker as it is small and comes with nice skinny wires with a connector on the end. It has a handy...
In Stock
[Buy Now](https://www.adafruit.com/product/3923)
[Related Guides to the Product](https://learn.adafruit.com/products/3923/guides)
## CircuitPython Usage
To use with CircuitPython, you need to first install the **Adafruit\_CircuitPython\_FruitJam** library, and its dependencies, into the **lib** folder on your **CIRCUITPY** drive. Then you need to update **code.py** with the example script.
Thankfully, we can do this in one go. In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, and copy the **entire** **lib** **folder** and the **code.py** file to your **CIRCUITPY** drive.
Your **CIRCUITPY/lib** folder should contain the following folders and files:
- **adafruit\_bitmap\_font/**
- **adafruit\_bus\_device/**
- **adafruit\_display\_text/**
- **adafruit\_esp32spi/**
- **adafruit\_fruitjam/**
- **adafruit\_imageload/**
- **adafruit\_io/**
- **adafruit\_minimqtt/**
- **adafruit\_portalbase/**
- **adafruit\_connection\_manager.mpy**
- **adafruit\_fakerequests.mpy**
- **adafruit\_miniqr.mpy**
- **adafruit\_ntp.mpy**
- **adafruit\_pixelbuf.mpy**
- **adafruit\_requests.mpy**
- **adafruit\_sdcard.mpy**
- **adafruit\_ticks.mpy**
- **neopixel.mpy**
- **simpleio.mpy**
- **adafruit\_simplemath.mpy**
- **adafruit\_tlv320.mpy**
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_I2S_Audio_Tone/code.py
Once the code starts running, you'll begin hearing a one second 440Hz tone, every other second.
## WAV Playback
Download and copy this WAV audio file to your **CIRCUITPY** drive.
[StreetChicken.wav](https://cdn-learn.adafruit.com/assets/assets/000/138/640/original/StreetChicken.wav?1753992461)
Then, update the **code.py** file with the code below:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_I2S_Audio_Wave_File/code.py
Once the code starts running, you'll hear the Street Chicken WAV file play once.
# Adafruit Fruit Jam
## SD Card
Warning: As of CircuitPython 9, a mount point (folder) named **/sd** is required on the **CIRCUITPY** drive. Make sure to create that directory after upgrading CircuitPython.
[Follow these steps to create the /sd directory](https://learn.adafruit.com/adafruit-memento-camera-board/circuitpython-memento-starter-projects)
Your board comes with a built in MicroSD card slot! Adding a MicroSD card allows you to include more files, music, images, videos etc. than the flash on the board can hold. You can use a MicroSD card with CircuitPython and the [Adafruit\_CircuitPython\_SD](https://github.com/adafruit/Adafruit_CircuitPython_SD) module. This module allows you to easily write Python code that lets you read and write to an attached MicroSD card.
## MicroSD Card Slot
The SD card slot is located next to the USB C connector.
Info:
### 512MB micro SD Memory Card
[512MB micro SD Memory Card](https://www.adafruit.com/product/5252)
Add storage in a jiffy using this **512MB** microSD card. Preformatted to FAT32, so it works out of the packaging with our projects. Works great with any device in the Adafruit shop that uses microSD cards. Ideal for use with Feathers, data loggers, or small Linux SBCs (not good...
In Stock
[Buy Now](https://www.adafruit.com/product/5252)
[Related Guides to the Product](https://learn.adafruit.com/products/5252/guides)
## CircuitPython Usage
To use with CircuitPython, you need to first install the **adafruit\_sdcard** library, and its dependencies, into the **lib** folder on your **CIRCUITPY** drive. Then you need to update **code.py** with the example script.
Thankfully, we can do this in one go. In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, and copy the **entire lib folder** and the **code.py** file to your **CIRCUITPY** drive.
Your **CIRCUITPY/lib** folder should contain the following folders and files:
- **/adafruit\_bus\_device**
- **adafruit\_sdcard.mpy**
## SD Card Read Test
Once everything is saved to the **CIRCUITPY** drive, [connect to the serial console](https://learn.adafruit.com/welcome-to-circuitpython/kattni-connecting-to-the-serial-console) to see the data printed out!
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_SD_Card_Read/code.py
In this read test for the SD card, the filesystem on the SD card is mounted and read. Then, the contents of the filesystem are printed to the REPL.
## SD Card Write Test
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_SD_Card_Write/code.py
In this example, the code is writing data to the SD card. The microcontroller CPU temperature is printed to the REPL and logged to a text file on the SD card. After running the code, you can read the text file from the SD card. You'll see that the text file matches what was printed to the REPL.
# Adafruit Fruit Jam
## HSTX DVI Output
It's easy to use the Fruit Jam to output DVI video with the RP2350's HSTX peripheral using CircuitPython and the [PicoDVI](https://docs.circuitpython.org/en/latest/shared-bindings/picodvi/index.html) core module.
## Video Connection
Connect the Fruit Jam to an DVI compatible display using a standard HDMI cable. One such cable and display that we stock can be found below.
### HDMI Cable - 1 meter
[HDMI Cable - 1 meter](https://www.adafruit.com/product/608)
Connect two HDMI devices together with this basic HDMI cable. It has nice molded grips for easy installation, and is 1 meter long (about 3 feet). This is a HDMI 1.3 cable.
We're now stocking a very fancy Official Raspberry Pi cable with overmolding and a Pi logo. Please note...
In Stock
[Buy Now](https://www.adafruit.com/product/608)
[Related Guides to the Product](https://learn.adafruit.com/products/608/guides)
### 7" Display 1280x800 (720p) IPS + Speakers - HDMI/VGA/NTSC/PAL
[7" Display 1280x800 (720p) IPS + Speakers - HDMI/VGA/NTSC/PAL](https://www.adafruit.com/product/1667)
Yes, this is an adorable small HDMI television with incredibly high resolution **and built in 3W stereo speakers**! We tried to get the smallest possible HDMI/VGA display with high-res, high-contrast visibility. The visible display measures only 7" (17.8cm) diagonal, and the TFT comes...
In Stock
[Buy Now](https://www.adafruit.com/product/1667)
[Related Guides to the Product](https://learn.adafruit.com/products/1667/guides)
## CircuitPython Usage
To use with CircuitPython, you need to first install the PicoDVI dependencies into the **lib** folder onto your **CIRCUITPY** drive. Then you need to update **code.py** with the example script.
Thankfully, we can do this in one go. In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file.
Connect your Fruit Jam board to your computer via a known good data+power USB cable. The board should show up in your File Explorer/Finder (depending on your operating system) as a flash drive named **CIRCUITPY**.
Extract the contents of the zip file, and copy the **entire lib folder** , the **Helvetica-Bold-16.pcf** font file, **blinka\_computer.bmp** bitmap file as well as the **code.py** files to your **CIRCUITPY** drive.
Your **CIRCUITPY/lib** folder should contain the following folders and file:
- **adafruit\_bitmap\_font/**
- **adafruit\_display\_shapes/**
- **adafruit\_display\_text/**
- **adafruit\_ticks/**
- **simpleio.mpy**
## Hello World DVI Output Example
Once everything is saved to the **CIRCUITPY** drive, you can connect the Fruit Jam to an HDMI monitor and to USB power. You'll see the Hello World example display on the screen.
## **code.py**
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_HSTX_DVI/code.py
This example is a port of the [Arduino **16bit\_hello** code written by Phil B](https://github.com/adafruit/PicoDVI/blob/master/examples/16bit_hello/16bit_hello.ino). with some slight variation to show off some of the unique abilities of **displayio**.
The example begins by showing a rectangle, circle, triangle and rounded rectangle and changing the fill attribute from `None` to a color.
Then, a few chart variations are shown, including a sine wave pattern, line graph and bar graph.
Next is a text alignment example, showing how to use the `anchor_point` and `anchor_position` functions in the **adafruit\_display\_text** library.
Following that is a custom text example, loading a bitmap font instead of the built-in **terminalio** font.
Then there is a quick break from fonts to show off a bitmap image, specifically Blinka happily using her computer.
Finally, an example shows how to update the text in a `Label` object for projects where you want to display text information that updates over time.
It's important to note that the example code is optimized to be able to run all of the examples in a loop, which you more than likely won't want to do for your projects. As a result, the `clean_up(group)` function is run after each example to use `pop()` to remove all of the graphical elements of the **displayio** `group`. [Garbage collection](https://learn.adafruit.com/Memory-saving-tips-for-CircuitPython?view=all#overview) (`gc.collect()`) is also run to conserve memory. Additionally, each graphical element is created and deleted each time in each of the functions.
If you were to run, for example, the `sensor_values()` function on its own for a project, you would instantiate the graphical elements _once_, before the loop, and then update the text with the "values" in the loop:
```auto
...
text_x = "X: %d" % randint(-25, 25)
text_y = "Y: %d" % randint(-25, 25)
text_z = "Z: %d" % randint(-25, 25)
x_text = label.Label(terminalio.FONT, text=text_x, color=red)
x_text.anchor_point = (0.0, 0.0)
x_text.anchored_position = (2, 0)
y_text = label.Label(terminalio.FONT, text=text_y, color=green)
y_text.anchor_point = (0.0, 0.0)
y_text.anchored_position = (2, 10)
z_text = label.Label(terminalio.FONT, text=text_z, color=blue)
z_text.anchor_point = (0.0, 0.0)
z_text.anchored_position = (2, 20)
group.append(x_text)
group.append(y_text)
group.append(z_text)
while True:
for i in range(40):
if i == 10:
group.scale = 2
elif i == 20:
group.scale = 3
elif i == 30:
group.scale = 4
x_text.text = "X: %d" % randint(-50, 50)
y_text.text = "Y: %d" % randint(-50, 50)
z_text.text = "Z: %d" % randint(-50, 50)
time.sleep(0.1)
```
## More on Video
See the guide below for more on using video with CircuitPython.
### Using DVI Video in CircuitPython - Overview
[Using DVI Video in CircuitPython](https://learn.adafruit.com/using-dvi-video-in-circuitpython)
[Overview](https://learn.adafruit.com/using-dvi-video-in-circuitpython/overview)
# Adafruit Fruit Jam
## USB Host
The Fruit Jam has a built-in USB hub with two exposed USB Host ports which makes it easy to take input from USB keyboard, mice, and game controllers.
## Keyboard
### Mini Chiclet Keyboard - USB Wired - Black
[Mini Chiclet Keyboard - USB Wired - Black](https://www.adafruit.com/product/1736)
Add a good quality, slim keyboard to your Raspberry Pi, Beagle Bone Black, or other single-board-computer with this sleek black chiclet keyboard. It's a full QWERTY keyboard with a USB cable and is compatible with all operating systems. We tried many keyboards to find one that felt...
In Stock
[Buy Now](https://www.adafruit.com/product/1736)
[Related Guides to the Product](https://learn.adafruit.com/products/1736/guides)
There are two possible ways to read data from a keyboard in CircuitPython. The less complex way is utilizing `sys.stdin`. Python has the concept of standard input and output streams, similar to those in Linux/Unix and other operating systems. CircuitPython has this capability and through a lot of behind the scenes code, presents a USB keyboard as a `sys.stdin` input device. Due to the way this works, it is only possible to know when a key is pressed, not how long it remains pressed, nor when it is released.
The `sys.stdin` method defaults to using the standard US layout for the keyboard. You can set a custom layout using the `set_user_keymap()`function [documented here.](https://docs.circuitpython.org/en/latest/shared-bindings/usb_host/index.html#usb_host.set_user_keymap)
The code to get USB Host Keyboard characters and echo them to serial out is as follows:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/USB_Host_Examples/CircuitPython_Keyboard_Stdin/code.py
For the more advanced and manual method for reading from USB keyboards see the [Demo Code: USB Host](https://learn.adafruit.com/using-a-keyboard-with-usb-host/circuitpython#demo-code-usb-host-3197513) section of USB Host keyboard Learn Guide.
## Mouse Demo Code: Read Data
### USB Wired Mouse - Two Buttons plus Wheel
[USB Wired Mouse - Two Buttons plus Wheel](https://www.adafruit.com/product/2025)
This is a mouse. A nice, simple mouse. No bells or whistles. Just a mouse.
But that doesn't mean it's not the best simple mouse! We compared a few and liked this one quite a bit. It's optical for good resolution and precision, has two...
In Stock
[Buy Now](https://www.adafruit.com/product/2025)
[Related Guides to the Product](https://learn.adafruit.com/products/2025/guides)
This example uses the USB Host API to read data from the mouse and prints out the relevant values to the serial console. The CircuitPython USB Host API is made to mimic PyUSB from CPython.
To read data from the mouse, the code must first scan the connected devices and find one with a boot mouse endpoint. Once a mouse device and endpoint are found, the code will try to read data from them in the main loop. If no data is sent, it will timeout and simply keep trying again until data is present. Once it reads data from the mouse, it will print any buttons that are pressed along with the delta X and delta Y values that represent how far the mouse has been moved and in which directions.
The list `BUTTONS` is created with values `"left"`, `"right"`, and `"middle"`. The order and indexes of these values align with the mouse protocol, which will use bits in the same positions to denote whether each button is being pressed or not.
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/USB_Host_Examples/CircuitPython_Mouse_Basic/code.py
Here is a sample output using the Adafruit mouse. If you have a different mouse, the identification information will likely be different, but the functionality should be the same.
## SNES-Like Game Controller Demo Code: Read Data
### USB Game Controller with SNES-like Layout
[USB Game Controller with SNES-like Layout](https://www.adafruit.com/product/6285)
This is a generic USB game controller, which plugs into to provide a two-handed gaming experience for retro gaming, or really any game you want to use a handheld rather than keyboard controller! Use it with your Raspberry Pi or desktop computer while playing emulated games, or as a...
In Stock
[Buy Now](https://www.adafruit.com/product/6285)
[Related Guides to the Product](https://learn.adafruit.com/products/6285/guides)
Connect the USB game controller while the microcontroller is unplugged from power. Only power up the microcontroller once the USB host connections are made securely.
Press the 'Download Project Bundle' button below to download a zip file containing the demo code. Connect your computer to your Fruit Jam via a known good data+power USB C cable. Copy **code.py** and the required libraries to the **CIRCUITPY** drive on your device which appears when the board is connected to your computer via good USB cable.
The code will scan for connected USB devices, printing out information about each one it finds.
Then it will start a loop reading from the first device it found and printing messages when each of the gamepad buttons are pressed. Check the serial console to see the output.
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/USB_SNES_Gamepad/CircuitPython_USB_Host/code.py
# Adafruit Fruit Jam
## Create Your settings.toml File
CircuitPython works with WiFi-capable boards to enable you to make projects that have network connectivity. This means working with various passwords and API keys. As of [CircuitPython 8](https://circuitpython.org/downloads), there is support for a **settings.toml** file. This is a file that is stored on your **CIRCUITPY** drive, that contains all of your secret network information, such as your SSID, SSID password and any API keys for IoT services. It is designed to separate your sensitive information from your **code.py** file so you are able to share your code without sharing your credentials.
CircuitPython previously used a **secrets.py** file for this purpose. The **settings.toml** file is quite similar.
Warning: Your **settings.toml** file should be stored in the main directory of your **CIRCUITPY** drive. It should not be in a folder.
## CircuitPython **settings.toml** File
This section will provide a couple of examples of what your **settings.toml** file should look like, specifically for CircuitPython WiFi projects in general.
The most minimal **settings.toml** file must contain your WiFi SSID and password, as that is the minimum required to connect to WiFi. Copy this example, paste it into your **settings.toml** , and update:
- `your_wifi_ssid`
- `your_wifi_password`
```auto
CIRCUITPY_WIFI_SSID = "your_wifi_ssid"
CIRCUITPY_WIFI_PASSWORD = "your_wifi_password"
```
Many CircuitPython network-connected projects on the Adafruit Learn System involve using Adafruit IO. For these projects, you must _also_ include your Adafruit IO username and key. Copy the following example, paste it into your settings.toml file, and update:
- `your_wifi_ssid`
- `your_wifi_password`
- `your_aio_username`
- `your_aio_key`
```auto
CIRCUITPY_WIFI_SSID = "your_wifi_ssid"
CIRCUITPY_WIFI_PASSWORD = "your_wifi_password"
ADAFRUIT_AIO_USERNAME = "your_aio_username"
ADAFRUIT_AIO_KEY = "your_aio_key"
```
Some projects use different variable names for the entries in the **settings.toml** file. For example, a project might use `ADAFRUIT_AIO_ID` in the place of `ADAFRUIT_AIO_USERNAME`. **If you run into connectivity issues, one of the first things to check is that the names in the settings.toml file match the names in the code.**
Warning: Not every project uses the same variable name for each entry in the **settings.toml** file! Always verify it matches the code.
## **settings.toml** File Tips
Here is an example **settings.toml** file.
```auto
# Comments are supported
CIRCUITPY_WIFI_SSID = "guest wifi"
CIRCUITPY_WIFI_PASSWORD = "guessable"
CIRCUITPY_WEB_API_PORT = 80
CIRCUITPY_WEB_API_PASSWORD = "passw0rd"
test_variable = "this is a test"
thumbs_up = "\U0001f44d"
```
In a **settings.toml** file, it's important to keep these factors in mind:
- Strings are wrapped in double quotes; ex: `"your-string-here"`
- Integers are _ **not** _ quoted and may be written in decimal with optional sign (`+1`, `-1`, `1000`) or hexadecimal (`0xabcd`).
- Floats (decimal numbers), octal (`0o567`) and binary (`0b11011`) are not supported.
- Use `\u` escapes for weird characters, `\x` and `\ooo` escapes are not available in **.toml** files
- Example: `\U0001f44d` for 👍 (thumbs up emoji) and `\u20ac` for € (EUR sign)
- Unicode emoji, and non-ASCII characters, stand for themselves as long as you're careful to save in "UTF-8 without BOM" format
When your **settings.toml ** file is ready, you can save it in your text editor with the **.toml** extension.
## Accessing Your **settings.toml** Information in **code.py**
In your **code.py** file, you'll need to `import` the `os` library to access the **settings.toml** file. Your settings are accessed with the `os.getenv()` function. You'll pass your settings entry to the function to import it into the **code.py** file.
```python
import os
print(os.getenv("test_variable"))
```
In the upcoming CircuitPython WiFi examples, you'll see how the **settings.toml ** file is used for connecting to your SSID and accessing your API keys.
# Adafruit Fruit Jam
## WiFi
It's easy to use the Adafruit AirLift breakout with CircuitPython and the [Adafruit CircuitPython ESP32SPI](https://github.com/adafruit/Adafruit_CircuitPython_ESP32SPI) module. This module allows you to easily add WiFi to your project.
Danger:
## CircuitPython Microcontroller Pinout
The WiFi capability uses an **Espressif ESP32-C6 Wi-Fi coprocessor,** aka the **AirLift,** with TLS/SSL support built-in. Communication is over SPI and it has CircuitPython library support ready to go for fast wireless integration with the following pins:
- **MOSI** pin (`board.MOSI`)
- **MISO** pin (`board.MISO`)
- **SCK** pin (`board.SCK`)
- **CS** pin (`board.ESP_CS`)
- **Interrupt** pin (`board.ESP_IRQ`)
- **Ready/Busy** pin (`board.ESP_BUSY`)
- **Reset** pin (`board.ESP_RESET`)
- ESP **RX** / **TX** pins (`board.RX` and `board.TX`) are shared with the RP2350 **RX** / **TX** pins.
- The ESP **RTS** pin (used in some serial contexts) is a shared peripheral reset pin on `board.PERIPH_RST` that is also used by the TLV320 I2S DAC.
- The ESP **GPIO0** pin for bootloader enable is connected to `board.BUTTON1`
## Add Your **settings.toml** File
Remember to add your **settings.toml** file as described in the [Create Your settings.toml File page](https://learn.adafruit.com/pico-w-wifi-with-circuitpython/create-your-settings-toml-file) earlier in the guide. You'll need to include your `CIRCUITPY_WIFI_SSID` and `CIRCUITPY_WIFI_PASSWORD` in the file.
```auto
CIRCUITPY_WIFI_SSID = "your-ssid-here"
CIRCUITPY_WIFI_PASSWORD = "your-ssid-password-here"
```
## CircuitPython Setup
First make sure you are running the [latest version of Adafruit CircuitPython](https://learn.adafruit.com/welcome-to-circuitpython/installing-circuitpython) for your board.
Next you'll need to install the necessary libraries to use the hardware. Thankfully, we can do this in one go. In the example below, click the **Download Project Bundle** button below to download the necessary libraries and the **code.py** file in a zip file. Extract the contents of the zip file, and copy the **entire lib folder** and the **code.py** file to your **CIRCUITPY** drive.
Your **CIRCUITPY/lib** folder should contain the following folders and files:
- **/adafruit\_bus\_device**
- **/adafruit\_esp32spi**
- **adafruit\_requests.mpy**
## CircuitPython Usage
Copy the following code to your **code.py** file on your microcontroller:
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/CircuitPython_WIFI/code.py
[Connect to the serial console](https://learn.adafruit.com/welcome-to-circuitpython/interacting-with-the-serial-console) to see the output. It should look something like the following:
Make sure you see the same output! If you don't, check your wiring. Note that we've changed the pinout in the code example above to reflect the CircuitPython Microcontroller Pinout at the top of this page.
Once you've succeeded, continue onto the next page!
Warning: If you can read the Firmware and MAC address but fails on scanning SSIDs, check your power supply, you may be running out of juice to the ESP32 and it's resetting.
# Adafruit Fruit Jam
## Fruit Jam Library
The [Adafruit\_CircuitPython\_FruitJam](https://github.com/adafruit/Adafruit_CircuitPython_FruitJam) library is a helper library based on the [Portal Base library](https://github.com/adafruit/Adafruit_CircuitPython_PortalBase). It initializes the built-in hardware peripherals on the Fruit Jam and provides a single interface for project code to access them. It also contains various helpers for fetching and displaying information from internet sources. Similar libraries exist for the Adafruit PyPortal, MagTag, MatrixPortal and other devices.
Info: Using the Fruit Jam library is optional. The examples on other pages in the CircuitPython Essentials section of this guide document interacting more directly with the Fruit Jam hardware peripherals and WiFi capabilities. The Fruit Jam library provides a single point of import and setup for the same capabilities.
The Fruit Jam library handles the internet access and `PortalBase` helper functions on the `FruitJam` object. The on-board peripherals on the Fruit Jam, like buttons, NeoPixels, DAC, and SD card, are available using a `Peripherals` object. If you're not using any of the internet or `PortalBase` functions you can import and create the `Peripherals` object directly.
```python
# use Peripherals object without internet helpers
from adafruit_fruitjam.peripherals import Peripherals
fruitjam_peripherals = Peripherals()
```
Or, if you are using `PortalBase` helpers, you can initialize the full `FruitJam` object and then access `fruitjam.peripherals` to interact with the built-in hardware.
```auto
# use full FruitJam object with PortalBase internet helpers and peripherals
from adafruit_fruitjam import FruitJam
TEXT_URL = "http://wifitest.adafruit.com/testwifi/index.html"
fruitjam = FruitJam(url=TEXT_URL, text_position=(10, 20))
fruitjam_peripherals = fruitjam.peripherals
```
## NeoPixels
The Fruit Jam's 5 built-in NeoPixels are available at `peripherals.neopixels`.
https://github.com/adafruit/Adafruit_CircuitPython_FruitJam/blob/main/examples/fruitjam_neopixels.py
## Buttons
The 3 built-in button states are available as `peripherals.button1`, `peripherals.button2`, and `peripherals.button3`. There is also the `peripherals.any_button_pressed` property which will be `True` if any of the hardware buttons are pressed.
```python
import time
from adafruit_fruitjam.peripherals import Peripherals
fruitjam = Peripherals()
while True:
if fruitjam.any_button_pressed:
print("Button(s) Pressed: ", end="")
if fruitjam.button1:
print("Button 1, ", end="")
if fruitjam.button2:
print("Button 2, ", end="")
if fruitjam.button3:
print("Button 3", end="")
print()
time.sleep(0.01)
```
## Audio
There are several properties and functions that assist with various audio related tasks.
- `peripherals.dac` - An instance of the [TLV320 driver](https://github.com/adafruit/Adafruit_CircuitPython_TLV320). Use higher level helpers instead of this unless you want very fine grained control over the DAC behavior, the capabilities of the DAC are extensive and the API is rather complex.
- `peripherals.audio` - An instance of [audiobusio.I2SOut](https://docs.circuitpython.org/en/latest/shared-bindings/audiobusio/index.html#audiobusio.I2SOut) ready to play sounds out of the 3.5mm jack or JST speaker connector on the Fruit Jam
- `peripherals.volume` - A property holding a float value between `0.0` and `1.0` that acts as a high level volume control without having to dive into the more complex DAC volume APIs.
- `peripherals.safe_volume_limit` - This float property controls the maximum allowed volume. By default it is `0.75`. Attempting to set `peripherals.volume` over the limit results in an exception. You can change the limit by setting `peripherals.safe_volume_limit` to any desired value between `0.0` and `1.0`. Operating above the limit could damage small speakers.
- `peripherals.audio_output` - A string property that controls where audio will play from. `"headphone"` for the 3.5mm jack and `"speaker"` for the JST connector.
- `peripherals.play_file()` - This function matches functionality found in PyPortal and other PortalBase libraries. It plays a **.wav** file from the attached headphones or speaker(s).
- `peripherals.stop_play()` - The `play_file()` function accepts a `wait_to_finish` boolean argument that is `True` by default. If you pass `False` for that value instead, the function will return immediately freeing up the code to do other things while the wave file is playing. The `stop_play()` function can be called to end the playback of a wave file that was started this way.
- `peripherals.play_mp3_file()` - Similar to `play_file()`, but this one is for **.mp3** files instead of **.wav**.
### Headphone Output Synthio
https://github.com/adafruit/Adafruit_CircuitPython_FruitJam/blob/main/examples/fruitjam_synthio_headphone.py
### JST Speaker Output Wave Audio Files
Download the [**.wav** files from the examples](https://github.com/adafruit/Adafruit_CircuitPython_FruitJam/tree/main/examples/wav)folder in the Fruit Jam repo and save them inside of **CIRCUITPY/wav/** , or swap in your own wave audio files on your drive and in the source code.
https://github.com/adafruit/Adafruit_CircuitPython_FruitJam/blob/main/examples/fruitjam_speaker.py
## HSTX/DVI Display Configuration
The peripherals module in the Fruit Jam library provides helper functions for checking the display configuration and requesting changes to the configured resolution and color depth.
`get_display_config()` will get a tuple containing the width, height, and color depth that the display is currently configured for.
`request_display_config()` allows accepts desired width, height, and color depth arguments to configure the display. See the [PicoDVI section of the Environment Variables docs](https://docs.circuitpython.org/en/latest/docs/environment.html#circuitpy-display-width-circuitpy-display-height-and-circuitpy-display-color-depth-rp2350-boards-with-dvi-or-hstx-connector) for supported configuration values
Note that both of these functions are imported from the `adafruit_fruitjam.peripherals` module, but they do not require an instance of the Peripherals object.
```auto
from adafruit_fruitjam.peripherals import request_display_config, get_display_config
print("before: ")
print(get_display_config())
request_display_config(320, 240)
print("after: ")
print(get_display_config())
```
## PortalBase Internet Helpers
The Fruit Jam library inherits all of the internet helpers provided by the PortalBase library. These make it easy to `fetch()` information from the internet and display it on the screen. Using this functionality it is possible to adapt many projects that were [originally made for the PyPortal](https://learn.adafruit.com/search?q=PyPortal) to work on the Fruit Jam simply by changing `PyPortal` initialization to `FruitJam`.
To use the WiFi features, you must set up a [settings.toml file as shown on this page.](https://learn.adafruit.com/adafruit-fruit-jam/create-your-settings-toml-file)
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Quotes/code.py
# Adafruit Fruit Jam
## Arduino IDE Setup
The [**Arduino** **Philhower core**](https://github.com/earlephilhower/arduino-pico) provides support for RP2350 microcontroller boards. This page covers getting your Arduino IDE set up to include your board.
## Arduino IDE Download
The first thing you will need to do is to download the latest release of the Arduino IDE. The Philhower core requires **version 1.8** or higher.
[Arduino IDE Download](https://www.arduino.cc/en/software)
Download and install it to your computer.
Once installed, open the Arduino IDE.
## Adding the Philhower Board Manager URL
In the Arduino IDE, and navigate to the **Preferences** window. You can access it through **File \> Preferences** on Windows or Linux, or **Arduino \> Preferences** on OS X.
The **Preferences** window will open.
In the **Additional Boards Manager URLs** field, you'll want to add a new URL. The list of URLs is comma separated, and _you will only have to add each URL once._ The URLs point to index files that the Board Manager uses to build the list of available & installed boards.
Copy the following URL.
`https://github.com/earlephilhower/arduino-pico/releases/download/global/package_rp2040_index.json`
Add the URL to the the **Additional Boards Manager URLs** field (highlighted in red below). If you already have a board support package in that field, type a comma at the end then add the address above. Both will then be loaded by the Arduino IDE.
Click **OK** to save and close **Preferences**.
## Add Board Support Package
In the Arduino IDE, click on **Tools \> Board \> Boards Manager**. If you have previously selected a board, the **Board** menu item may have a board name after it.
In the **Boards Manager** , search for RP2040. Scroll down to the **Raspberry Pi Pico/RP2040/RP2350 by Earle F Philhower, III** entry. Click **Install** to install it.
Warning:
Once installation is complete, click **Close** to close the Boards Manager.
## Choose Your Board
In the **Tools \> Boards** menu, you should now see **Raspberry Pi RP2040/RP2350 Boards (in sketchbook)**.
Navigate to the **Raspberry Pi RP2040/RP2350 Boards** menu. You will see the available boards listed.
In the **Raspberry Pi Pico/RP2040/RP2350 Boards** menu choose **Adafruit Fruit Jam RP2350**.
Danger: If there is no serial Port available in the dropdown, or an invalid one appears - don't worry about it! The RP2350 does not actually use a serial port to upload, so its OK if it does not appear if in manual bootloader mode. You will see a serial port appear after uploading your first sketch.
Now you're ready to begin using Arduino with your RP2350 board!
# Adafruit Fruit Jam
## Arduino Usage
Now that you've set up the Arduino IDE with the Philhower Arduino core, you're ready to start using Arduino with your RP2350-based device.
## RP2350 Arduino Pins
There is no pin remapping for Arduino on the RP2350. The Arduino pin names are the RP2350 GPIO pin names. These pins match the labels on the board silk.
## Choose Your Board
Navigate to the **Tools \> Boards \>** **Raspberry Pi Pico/RP2040/RP2350** menu.
Choose **Adafruit Fruit Jam RP2350** from the menu.
## Load the Blink Sketch
Begin by plugging in your board to your computer, and wait a moment for it to be recognised by the OS. It will create a COM/serial port that you can now select from the **Tools \> Port** menu dropdown.
Open the Blink sketch by clicking through **File \> Examples \> 01.Basics \> Blink**.
Click Upload. A successful upload will result in text similar to the following.
Once complete, the little red LED will begin blinking once every second! Try changing up the `delay()` timing to change the rate at which the LED blinks.
## Manually Enter the Bootloader
If you get into a state with the bootloader where you can no longer upload a sketch, or you have uploaded code that crashes and doesn't auto-reboot into the bootloader, you may have to manually enter the bootloader.
To enter the bootloader, hold down the **Button 1** , and while continuing to hold it (don't let go!), press and release the **reset button**. **Continue to hold the Button 1 until the RP2350 drive appears!**
Once the RPI-RP2 drive shows up, your board is in bootloader mode. There will not be a port available in bootloader mode, this is expected.
Once you see RPI-RP2 drive, make sure you are no longer holding down any buttons (reset or boot button).
Now, click Upload on your sketch to try again.
# Adafruit Fruit Jam
## Blink
The first and most basic program you can upload to your Arduino is the classic Blink sketch. This takes something on the board and makes it, well, blink! On and off. It's a great way to make sure everything is working and you're uploading your sketch to the right board and right configuration.
When all else fails, you can always come back to Blink!
# Pre-Flight Check: Get Arduino IDE & Hardware Set Up
This lesson assumes you have Arduino IDE set up. This is a generalized checklist, some elements may not apply to your hardware. If you haven't yet, check the previous steps in the guide to make sure you:
- **Install the very latest Arduino IDE for Desktop** (not all boards are supported by the Web IDE so we don't recommend it).
- **Install any board support packages (BSP) required for your hardware.** Some boards are built in defaults on the IDE, but lots are not! You may need to install plug-in support which is called the BSP.
- **Get a Data/Sync USB cable for connecting your hardware.** A _significant_ amount of problems folks have stem from not having a USB cable with data pins. Yes, these cursed cables roam the land, making your life hard. If you find a USB cable that doesn't work for data/sync, _throw it away immediately_! There is no need to keep it around, cables are very inexpensive these days.
- **Install any drivers required** - If you have a board with a FTDI or CP210x chip, you may need to get separate drivers. If your board has native USB, it probably doesn't need anything. After installing, reboot to make sure the driver sinks in.
- **Connect the board to your computer.** If your board has a power LED, make sure its lit. Is there a power switch? Make sure its turned On!
### Inverted Wiring
The built-in LED on the Fruit Jam is wired with its **anode** connected to **3.3V** , and its **cathode** connected to the **LED\_BUILTIN** pin. That means that setting the pin to `LOW` results in the LED turning on, and setting the pin to `HIGH` results in the LED turning off.
# Start up Arduino IDE and Select Board/Port
OK now you are prepared! Open the Arduino IDE on your computer. Now you have to tell the IDE what board you are using, and how you want to connect to it.
In the IDE find the **Tools** menu. You will use this to select the board. If you switch boards, you _must switch the selection!_ So always double-check before you upload code in a new session.
# New Blink Sketch
OK lets make a new blink sketch! From the **File** menu, select **New**
Then in the new window, copy and paste this text:
```auto
int led = LED_BUILTIN;
void setup() {
// Some boards work best if we also make a serial connection
Serial.begin(115200);
// set LED to be an output pin
pinMode(led, OUTPUT);
}
void loop() {
// Say hi!
Serial.println("Hello!");
digitalWrite(led, HIGH); // turn the LED on (HIGH is the voltage level)
delay(500); // wait for a half second
digitalWrite(led, LOW); // turn the LED off by making the voltage LOW
delay(500); // wait for a half second
}
```
Info:
One note you'll see is that we reference the LED with the constant `LED_BUILTIN` rather than a number. That's because, historically, the built in LED was on pin 13 for Arduinos. But in the decades since, boards don't always have a pin 13, or maybe it could not be used for an LED. So the LED could have moved to another pin. It's best to use `LED_BUILTIN` so you don't get the pin number confused!
# Verify (Compile) Sketch
OK now you can click the Verify button to convert the sketch into binary data to be uploaded to the board.
Note that Verifying a sketch is the same as Compiling a sketch - so we will use the words interchangeably
During verification/compilation, the computer will do a bunch of work to collect all the libraries and code and the results will appear in the bottom window of the IDE.
If something went wrong with compilation, you will get red warning/error text in the bottom window letting you know what the error was. It will also highlight the line with an error.
For example, here I had the wrong board selected - and the selected board does not have a built in LED!
Here's another common error, in my haste I forgot to add a `;` at the end of a line. The compiler warns me that it's looking for one - note that the error is actually a few lines up!
Info:
On success you will see something like this white text output and the message **Done compiling.** in the message area.
# Upload Sketch
Once the code is verified/compiling cleanly you can upload it to your board. Click the **Upload** button.
The IDE will try to compile the sketch again for good measure, then it will try to connect to the board and upload a the file.
**This is actually one of the hardest parts for beginners because it's where a lot of things can go wrong.**
However, lets start with what it looks like on success! Here's what your board upload process looks like when it goes right:
Often times you will get a warning like this, which is kind of vague:
`No device found on COM66` (or whatever port is selected)
`An error occurred while uploading the sketch`
This could be a few things.
**First up, check again that you have the correct board selected!** Many electronics boards have very similar names or look, and often times folks grab a board different from what they thought.
If you're positive the right board is selected, we recommend the next step is to put the board into manual bootloading mode.
## Native USB and manual bootloading
Historically, microcontroller boards contained two chips: the main micro chip (say, ATmega328 or ESP8266 or ESP32) and a separate chip for USB interface that would be used for bootloading (a CH430, FT232, CP210x, etc). With these older designs, the microcontroller is put into a bootloading state for uploading code by the separate chip. It allows for easier uploading but is more expensive as two chips are needed, and also the microcontroller can't act like a keyboard or disk drive.
Modern chips often have 'native' USB - that means that there is no separate chip for USB interface. It's all in one! Great for cost savings, simplicity of design, reduced size and more control. However, it means the chip must be self-aware enough to be able to put _itself_ into bootload/upload mode on its own. That's fine 99% of the time but is very likely you will at some point get the board into an odd state that makes it too confused to bootload.
Warning:
Before continuing we _really, really_ suggest turning on **Verbose Upload** messages, it will help in this process because you will be able to see what the IDE is trying to do. It's a checkbox in the **Preferences** menu.
## Enter Manual Bootload Mode
OK now you know it's probably time to try manual bootloading. No problem! Here is how you do that for this board:
To enter the bootloader, hold down the **Button 1** , and while continuing to hold it (don't let go!), press and release the **reset button**. **Continue to hold the Button 1 until the RP2350 drive appears!**
Once you are in manual bootload mode, go to the Tools menu, and make sure you have selected the bootloader serial port. **It is almost certain that the serial port has changed now that the bootloader is enabled**
Now you can try uploading again!
Info:
This time, you should have success!
After uploading this way, be sure to **click the reset button** - it sort of makes sure that the board got a good reset and will come back to life nicely.
Warning:
It's also a good idea to try to re-upload the sketch again now that you've performed a manual bootload to get the chip into a good state. It should perform an auto-reset the second time, so you don't have to manually bootload again.
# Finally, a Blink!
OK it was a journey but now we're here and you can enjoy your blinking LED. Next up, try to change the delay between blinks and re-upload. It's a good way to make sure your upload process is smooth and practiced.
# Adafruit Fruit Jam
## NeoPixels
Your board has a built-in RGB NeoPixel status LED. You can use Arduino code to control the color and brightness of this LED. It is also used to indicate the bootloader status.
A NeoPixel is what Adafruit calls the WS281x family of addressable RGB LEDs. It contains three LEDs - a red one, a green one and a blue one - along side a driver chip in a tiny package controlled by a single pin. They can be used individually (as in the built-in LED on your board), or chained together in strips or other creative form factors. NeoPixels do not light up on their own; they require a microcontroller. So, it's super convenient that the NeoPixel is built in to your microcontroller board!
This page will cover using Arduino to control the status RGB NeoPixel built into your microcontroller. Time to get started!
## NeoPixel Location
## Arduino Library Installation
You can install the necessary libraries from the Library Manager. To open, click **Sketch \> Include Library \> Manage Libraries...**
Search for **NeoPixel** , and install the **Adafruit** **NeoPixel** library.
Info: There are no additional library dependencies for the Adafruit NeoPixel library.
## Rainbow Swirl Demo
```cpp
// SPDX-FileCopyrightText: 2024 ladyada for Adafruit Industries
//
// SPDX-License-Identifier: MIT
#include <Adafruit_NeoPixel.h>
#define NUMPIXELS 1
Adafruit_NeoPixel pixel(NUMPIXELS, PIN_NEOPIXEL, NEO_GRB + NEO_KHZ800);
void setup() {
Serial.begin(115200);
pixel.begin();
pixel.setBrightness(25);
pixel.show();
}
uint16_t firstPixelHue = 0;
void loop() {
firstPixelHue += 256;
for(int i=0; i<pixel.numPixels(); i++) {
int pixelHue = firstPixelHue + (i * 65536L / pixel.numPixels());
pixel.setPixelColor(i, pixel.gamma32(pixel.ColorHSV(pixelHue)));
}
pixel.show();
delay(10);
}
```
Upload the sketch to your board. You'll see the onboard NeoPixel run through a looping rainbow animation.
# Adafruit Fruit Jam
## I2C Scan
A lot of sensors, displays, and devices can connect over I2C. I2C is a 2-wire 'bus' that allows multiple devices to all connect on one set of pins so it's very convenient for wiring!
When using your board, you'll probably want to connect up I2C devices, and it can be a little tricky the first time. The best way to debug I2C is go through a checklist and then perform an I2C scan.
# Common I2C Connectivity Issues
- **Have you connected four wires (at a minimum) for each I2C device? **Power the device with whatever is the logic level of your microcontroller board (probably 3.3V), then a ground wire, and a SCL clock wire, and and a SDA data wire.
- **If you're using a STEMMA QT board - check if the power LED is lit.** It's usually a green LED to the left side of the board.
- **Does the STEMMA QT/I2C port have switchable power or pullups?** To reduce power, some boards have the ability to cut power to I2C devices or the pullup resistors. Check the documentation if you have to do something special to turn on the power or pullups.
- **If you are using a DIY I2C device, do you have pullup resistors? ** Many boards do _not_ have pullup resistors built in and they are _required! _We suggest any common 2.2K to 10K resistors. You'll need two: one each connects from SDA to positive power, and SCL to positive power. Again, positive power (a.k.a VCC, VDD or V+) is often 3.3V
- **Do you have an address collision? ** You can only have _one_ board per address. So you cannot, say, connect two AHT20's to one I2C port because they have the same address and will interfere. Check the sensor or documentation for the address. Sometimes there are ways to adjust the address.
- **Does your board have multiple I2C ports? ** Historically, boards only came with one. But nowadays you can have two or even three! This can help solve the "hey, but what if I want two devices with the same address" problem: just put one on each bus.
- **Are you hot-plugging devices?** I2C does _not_ support dynamic re-connection, you cannot connect and disconnect sensors as you please. They should all be connected on boot and not change. ([Only exception is if you're using a hot-plug assistant but that'll cost you](https://www.adafruit.com/product/5159)).
- **Are you keeping the total bus length reasonable?** I2C was designed for maybe 6" max length. We like to push that with plug-n-play cables, but really please keep them as short as possible! ([Only exception is if you're using an active bus extender](https://www.adafruit.com/product/4756)).
The Fruit Jam comes with a few I2C devices built in: the TLV320DAC3100 audio DAC and up to 3 video EDID I2C devices depending on the display connected to the DVI port. The I2C scan code will show the address from the built in DAC ( **0x18** ), the AHT20 ( **0x38** ), and possibly EDID addresses ( **0x50** ), ( **0x3a** ), and ( **0x54** ).
Info: The Fruit Jam comes with a few I2C devices built in: the TLV320DAC3100 audio DAC and possible video monitor EDID I2C devices. The I2C scan code will show the addresses from the built in DAC, the AHT20, and possibly EDID. If HDMI/DVI video is not used, there will not be EDID I2C connections from a monitor.
### Wire up I2C device
While the examples here will be using the [Adafruit AHT20](https://www.adafruit.com/product/4566), a temperature and humidity sensor, the overall process is the same for just about any I2C sensor or device.
The first thing you'll want to do is get the sensor connected so your board has I2C to talk to.
### Adafruit AHT20 - Temperature & Humidity Sensor Breakout Board
[Adafruit AHT20 - Temperature & Humidity Sensor Breakout Board](https://www.adafruit.com/product/4566)
The AHT20 is a nice but inexpensive temperature and humidity sensor [from the same folks that brought us the DHT22](https://www.adafruit.com/product/385). You can take sensor readings as often as you like, and it uses standard I2C so its super easy to use with any Arduino or...
In Stock
[Buy Now](https://www.adafruit.com/product/4566)
[Related Guides to the Product](https://learn.adafruit.com/products/4566/guides)
### STEMMA QT / Qwiic JST SH 4-Pin Cable - 50mm Long
[STEMMA QT / Qwiic JST SH 4-Pin Cable - 50mm Long](https://www.adafruit.com/product/4399)
This 4-wire cable is 50mm / 1.9" long and fitted with JST SH female 4-pin connectors on both ends. Compared with the chunkier JST PH these are 1mm pitch instead of 2mm, but still have a nice latching feel, while being easy to insert and remove.
Out of Stock
[Buy Now](https://www.adafruit.com/product/4399)
[Related Guides to the Product](https://learn.adafruit.com/products/4399/guides)
## Wiring the AHT20
The AHT20 comes with a STEMMA QT connector, which makes wiring it up quite simple and solder-free.
# Perform an I2C scan!
### Install TestBed Library
To scan I2C, the Adafruit TestBed library is used. This library and example just makes the scan a little easier to run because it takes care of some of the basics. You will need to add support by installing the library. Good news: it is _very easy_ to do it. Go to the **Arduino Library Manager.**
Search for **TestBed** and install the **Adafruit TestBed** library.
Now open up the I2C Scan example.
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/I2C_Scanners/arduino/i2c_scanner/i2c_scanner.ino
Now upload the scanning sketch to your microcontroller and open the serial port to see the output. You should see something like this:
# Adafruit Fruit Jam
## SD Card
Using the built in MicroSD card slot with Arduino involves installing the [Adafruit Fork of the SdFat library](https://github.com/adafruit/SdFat), and running the provided example code.
## MicroSD Card Slot
Info:
### 512MB micro SD Memory Card
[512MB micro SD Memory Card](https://www.adafruit.com/product/5252)
Add storage in a jiffy using this **512MB** microSD card. Preformatted to FAT32, so it works out of the packaging with our projects. Works great with any device in the Adafruit shop that uses microSD cards. Ideal for use with Feathers, data loggers, or small Linux SBCs (not good...
In Stock
[Buy Now](https://www.adafruit.com/product/5252)
[Related Guides to the Product](https://learn.adafruit.com/products/5252/guides)
## Library Installation
You can install the **Adafruit Fork of the SDFat**** **library for Arduino using the Library Manager in the Arduino IDE.
Click the **Manage Libraries ...** menu item, search for **Adafruit SDFat** and select the **SDFat - Adafruit Fork** library:
Info:
## Read/Write Example
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Fruit_Jam/Fruit_Jam_Examples/Arduino_SD_Card_Read_Write/Arduino_SD_Card_Read_Write.ino
Upload the sketch to your board and open up the Serial Monitor ( **Tools -\> Serial Monitor** ) at 115200 baud. A test text file will be created and written to on the SD card. Then, the text file will be read back with its contents printed to the Serial Monitor.
# Adafruit Fruit Jam
## SDIO Usage
Using the RP2040/RP2350's PIO peripheral, SDIO support has been added to the [SdFat library](https://github.com/greiman/SdFat/releases/tag/2.3.0). The [Adafruit Fork of the SdFat library](https://github.com/adafruit/SdFat) has [merged in these changes as well](https://github.com/adafruit/SdFat/releases/tag/2.3.50).
SDIO provides a generally faster transfer rate than using generic SPI, but it has some special requirements:
- Four **consecutive** GPIO pins of the RP2040/RP2350 must be used.
- The SD card itself must be wired for SDIO support.
- The [PID 254](https://www.adafruit.com/product/254) SD breakout does **NOT** support SDIO
- The [PID 2922](https://www.adafruit.com/product/2922) Adalogger FeatherWing does **NOT** support SDIO
- The [PID 4682](https://www.adafruit.com/product/4682) SD breakout does support SDIO
- Adafruit RP2040/RP2350 based Metros and Feather Adaloggers with an SD card slot support SDIO
- [Adafruit Fruit Jam - Mini RP2350 Computer](https://www.adafruit.com/product/6200) does support SDIO.
Danger: The SDIO support shown here is for RP2040 or RP2350 based boards only.
## MicroSD Card Slot
The SD card slot is located next to the USB C connector.
Info:
### 512MB micro SD Memory Card
[512MB micro SD Memory Card](https://www.adafruit.com/product/5252)
Add storage in a jiffy using this **512MB** microSD card. Preformatted to FAT32, so it works out of the packaging with our projects. Works great with any device in the Adafruit shop that uses microSD cards. Ideal for use with Feathers, data loggers, or small Linux SBCs (not good...
In Stock
[Buy Now](https://www.adafruit.com/product/5252)
[Related Guides to the Product](https://learn.adafruit.com/products/5252/guides)
## Library Installation
You can install the **Adafruit Fork of the SDFat**** **library for Arduino using the Library Manager in the Arduino IDE.
Click the **Manage Libraries ...** menu item, search for **Adafruit SDFat** and select the **SDFat - Adafruit Fork** library:
Info:
## Run Setup Example
https://github.com/adafruit/SdFat/blob/master/examples/Rp2040SdioSetup/Rp2040SdioSetup.ino
Upload the sketch to your board and open up the Serial Monitor ( **Tools -\> Serial Monitor** ) at 9600 baud. Press \ in the input area of the Serial Monitor:
If successful, the board name will be shown (variant symbol) as well as a listing of the SD card contents.
## Speed Test
The [bench](https://github.com/adafruit/SdFat/tree/master/examples/bench) example in the [SDFat library](https://github.com/adafruit/SdFat) can be used to benchmark the resulting speed of SD card access.
https://github.com/adafruit/SdFat/blob/master/examples/bench/bench.ino
Upload the sketch to your board and open up the Serial Monitor ( **Tools -\> Serial Monitor** ) at 9600 baud. Press in the input area of the Serial Monitor:
The sketch will then perform various read/write access tests and output the results. Different setups will have different values, but the SDIO results should be faster than the SPI results.
Here we show example output comparing SDIO speed vs SPI speed:
Example benchmark results when using **SDIO**.
- write = 10060 KB/Sec
- read = 19011 KB/Sec
Example benchmark results when using **SPI**.
- write = 2043 KB/Sec
- read = 2421 KB/Sec
The results indicate that **SDIO is ~5x faster than SPI**.
# Adafruit Fruit Jam
## HSTX DVI Output
The Fruit Jam makes it easy to output DVI signal out of the built-in port with the **Adafruit DVI HSTX** library.
### **Note:**
This page demonstrates basic usage of a single piece of hardware on the Fruit Jam. The device can be picky about the order that things are initialized when using multiple of the peripherals. If you're doing something involving the display, DAC, WiFi, or USB ports we recommend to start from the [factory demo Arduino code](https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Factory_Tests/Fruit_Jam_Factory_Test/Fruit_Jam_Factory_Test.ino) and remove anything you don't need, rather than starting from these basic individual examples.
### Library Installation
You can install the **Adafruit DVI HSTX** library for Arduino using the Library Manager in the Arduino IDE.
Click the **Tools** -\> **Manage Libraries ...** menu item, search for **Adafruit DVI HSTX** and select the **Adafruit DVI HSTX** library
If asked about dependencies for any of the libraries, click "Install all".
If the "Dependencies" window does not come up, then you already have the dependencies installed.
Warning: If the dependencies are already installed, you must make sure you update them through the Arduino Library Manager before loading the example!
## Example Code
https://github.com/adafruit/Adafruit-DVI-HSTX/blob/main/examples/00simpletest/00simpletest.ino
# Adafruit Fruit Jam
## USB Host
The Fruit Jam has a built-in USB hub with two exposed USB Host ports which makes it easy to take input from USB keyboard, mice, and game controllers.
###
### **Note:**
This page demonstrates basic usage of a single piece of hardware on the Fruit Jam. The device can be picky about the order that things are initialized when using multiple of the peripherals. If you're doing something involving the display, DAC, WiFi, or USB ports we recommend to start from the [factory demo Arduino code](https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Factory_Tests/Fruit_Jam_Factory_Test/Fruit_Jam_Factory_Test.ino) and remove anything you don't need, rather than starting from these basic individual examples.
## Install the Libraries
You can install the libraries for this project using the Library Manager in the Arduino IDE.
Click the Library Manager icon, search for Adafruit TinyUSB Arduino, and select the Adafruit TinyUSB Library.
If asked about dependencies click "Install All".
Then install the Pico PIO USB library. Click the **Library Manager** icon menu item again, search for **PIO USB** , and select the **Pico PIO USB** library by sekigon-gonnoc.
## Code Prep
The code consists of a main **usbhost\_keyboard\_simpletest.ino** program file and a separate header file **usbh\_helper.h**. The header file stores configuration for USB host on the RP2040/RP2350. You'll need both of these files to properly compile and run the project.
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/USB_Host_Examples/Arduino_Metro_RP2350_USB_Host_Keyboard/usbhost_keyboard_simpletest.ino
Warning: The character mapping in the code above is for a US 104 key QWERTY keyboard. Other keyboard layouts have different mappings. You can often get the USB value map for other keyboards online or just hook up your keyboard and enter keys to determine which key maps to which character.
https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/USB_Host_Examples/Arduino_Metro_RP2350_USB_Host_Keyboard/usbh_helper.h
## Upload and Test
Before uploading, you'll need to update some settings in the Boards menu. Select the **Adafruit Fruit Jam RP2350** as the board. Under **USB Stack** select **Adafruit TinyUSB**. Then, upload the sketch to your board. You can use the Serial Monitor in the Arduino IDE for debugging any errors.
## Serial Output
The code will connect to the USB keyboard and read data coming from it. The keys pressed along with any modifier keys applied will be printed to the serial monitor.
# Adafruit Fruit Jam
## WiFi Test
### **Note:**
This page demonstrates basic usage of a single piece of hardware on the Fruit Jam. The device can be picky about the order that things are initialized when using multiple of the peripherals. If you're doing something involving the display, DAC, WiFi, or USB ports we recommend to start from the [factory demo Arduino code](https://github.com/adafruit/Adafruit_Learning_System_Guides/blob/main/Factory_Tests/Fruit_Jam_Factory_Test/Fruit_Jam_Factory_Test.ino) and remove anything you don't need, rather than starting from these basic individual examples.
# Library Install
We're using a variant of the Arduino WiFiNINA library, which is amazing and written by the Arduino team! We made a fork that you can install.
Click here to download the library:
[Download Adafruit's version of WiFiNINA](https://github.com/adafruit/WiFiNINA/archive/master.zip)
Within the Arduino IDE, select **Install library from ZIP...**
And select the zip you just downloaded.
# First Test
OK now you have it wired and library installed, time to test it out!
Lets start by scanning the local networks. Load up the **ScanNetworks** example
At the top you'll see an include for `pin_config.h`, in that file iswhere the GPIO pins are defined.
If you don't see this, you may have the wrong WiFiNINA library installed. Uninstall it and re-install the Adafruit one linked above.
**You do not need to change any of these pins** - they're pre-defined in the board definition for the Metro M4 WiFi but you still will want to have our version of the library installed because you can switch to the AirLift shield or breakout.
Make sure you select **Adafruit Fruit Jam RP2350**
Compile and upload to your board.
If you don't even get the MAC address printed out, check your wiring.
If you get the MAC address but cannot scan any networks, check your power supply. You need a solid 3-5VDC into **Vin** in order for the ESP32 not to brown out.
# WiFi Connection Test
Now that you have your wiring checked, time to connect to the Internet!
Open up the **WiFiWebClient** example
Open up the secondary tab, **arduino\_secrets.h**. This is where you will store private data like the SSID/password to your network.
You must change these string values before updating to your board!
After you've set it correctly, upload and check the serial monitor. You should see the following. If not, go back, check wiring, power and your SSID/password
You must change these string values before updating to your board!
After you've set it correctly, upload and check the serial monitor. You should see the following. If not, go back, check wiring, power and your SSID/password
# Secure Connection Example
Many servers today do not allow non-SSL connectivity. Lucky for you the ESP32 has a great TLS/SSL stack so you can have that all taken care of for you. Here's an example of a secure WiFi connection:
Note we use `WiFiSSLClient client;` instead of `WiFiClient client;` to require an SSL connection!
# Adafruit Fruit Jam
## WipperSnapper Setup
Warning:
Danger: WipperSnapper is incompatible with the AirLift version shipped with the Adafruit FunHouse as of 2025.
WipperSnapper on Adafruit FruitJam REQUIRES the FruitJam's AirLift (ESP32-C6) firmware to be updated to the latest version.
To do this, follow this guide page, first: https://learn.adafruit.com/adafruit-fruit-jam/upgrading-airlift-firmware
Then, come back to this page after you've updated the AirLift's firmware
The Fruit Jam comes with two microcontrollers on board, the main Raspberry Pi RP2350 (same as the Pico 2W), and an ESP32-C6 co-processor used for networking (WiFi/Bluetooth/Thread).
WipperSnapper gets installed and run on the main RP2350, but you might find the ESP32-C6 needs occasionally updating with the latest AirLift firmware (containing SSL certificates and any bug fixes / new functionality).
If you ever have internet connectivity issues then check if you're using the [latest AirLift firmware version](https://github.com/adafruit/nina-fw/releases). It's displayed at boot and during wifi reconnection over the serial port (along with other diagnostic info), and added to the wipper\_boot\_out.txt file on the WIPPER drive.
See [this page](https://learn.adafruit.com/adafruit-fruit-jam/upgrading-airlift-firmware) for details on the update process, where you'll temporarily setup the RP2 chip to act as a passthrough device so you can speak to the C6 to update its firmware, then afterwards come back and reinstall WipperSnapper.
## What is WipperSnapper
WipperSnapper is a firmware designed to turn any WiFi-capable board into an Internet-of-Things device without programming a single line of code. WipperSnapper connects to [Adafruit IO](https://io.adafruit.com/), a web platform designed ([by Adafruit!](https://www.adafruit.com/about)) to _display_, _respond_, and _interact_ with your project's data.
Simply load the WipperSnapper firmware onto your board, add credentials, and plug it into power. Your board will automatically register itself with your Adafruit IO account.
From there, you can add _components_ to your board such as buttons, switches, potentiometers, sensors, and more! Components are _dynamically _added to hardware, so you can immediately start interacting, logging, and streaming the data your projects produce without writing code.
## Sign up for Adafruit.io
You will need an Adafruit IO account to use WipperSnapper on your board. If you do not already have one, head over to [io.adafruit.com](https://io.adafruit.com/) to create a _free_ account.
## Add a New Device to Adafruit IO
Log into your [Adafruit IO](https://io.adafruit.com/) account. Click the _New Device_ button at the top of the page.
After clicking New Device, you should be on the _board selector_ page. This page displays every board that is compatible with the WipperSnapper firmware.
In the board selector page's search bar, search for the **Fruit Jam** _. _Once you've located the board you'd like to install WipperSnapper on,_ _click the **Choose Board** button to bring you to the self-guided installation wizard.
Follow the step-by-step instructions on the page to install Wippersnapper on your device and connect it to Adafruit IO.
### Installation Issues?
During the installation, if your board doesn't appear as a USB drive when rebooted then it may need the [Flash memory erasing first with this UF2](https://github.com/Gadgetoid/pico-universal-flash-nuke/releases/download/v1.0.1/universal_flash_nuke.uf2) (there's also a page in this guide with details).
If you launch a serial monitor and connect to the USB Serial/COM port you'll see the diagnostic messages and a repeating failure message like:
`Fatal Error: Halted execution!ERROR Initializing Filesystem`
If you see a different message related to internet connectivity,
`ERROR: No WiFi networks found!ERROR: Unable to find WiFi network, rebooting soon...` or if the AirLift firmware version is problematic then [update the onboard ESP32-C6](https://learn.adafruit.com/adafruit-fruit-jam/upgrading-airlift-firmware).
Afterwards just repeat the WipperSnapper installation process.
If the installation was successful, a popover should appear displaying that your board has successfully been detected by Adafruit IO.
Give your board a name and click "Continue to Device Page".
You should be brought to your board's device page.
## Feedback
Adafruit.io WipperSnapper is in **beta** and you can help improve it!
If you have suggestions or general feedback about the installation process - visit [https://io.adafruit.com/support](https://io.adafruit.com/support), click _"Contact Adafruit IO Support"_ and select _"I have feedback or suggestions for the WipperSnapper Beta"._
## Troubleshooting
If you encountered an issue during installation, please try the steps below first.
If you're still unable to resolve the issue, or if your issue is not listed below, get in touch with us directly at [https://io.adafruit.com/support](https://io.adafruit.com/support "https://io.adafruit.com/support"). Make sure to click _"Contact Adafruit IO Support"_ and select "_There is an issue with WipperSnapper. Something is broken!"_
###
First, make sure that you selected the correct board on the board selector.
Next, please make sure that you entered your WiFi credentials properly, there are no spaces/special characters in either your network name (SSID) or password, and that you are connected to a 2.4GHz wireless network.
If you're still unable to connect your board to WiFi, please [make a new post on the WipperSnapper technical support forum with the error you're experiencing, the LED colors which are blinking, and the board you're using.](https://forums.adafruit.com/viewforum.php?f=66)
###
Try hard-resetting your board by unplugging it from USB power and plugging it back in.
If the error is still occurring, please [make a new post on the WipperSnapper technical support forum with information about what you're experiencing, the LED colors which are blinking (if applicable), and the board you're using.](https://forums.adafruit.com/viewforum.php?f=66)
## "Uninstalling" WipperSnapper
WipperSnapper firmware is an application that is loaded onto your board. There is nothing to "uninstall". However, you may want to "move" your board from running WipperSnapper to running Arduino or CircuitPython. You also may need to restore your board to the state it was shipped to you from the Adafruit factory.
### Moving from WipperSnapper to CircuitPython
Follow the steps on the [Installing CircuitPython page](https://learn.adafruit.com/welcome-to-circuitpython/installing-circuitpython) to install CircuitPython on your board running WipperSnapper.
- If you are unable to double-tap the RST button to enter the UF2 bootloader, follow the _"Factory Resetting a WipperSnapper Board"_ instructions below.
Uploading this sketch will overwrite WipperSnapper. If you want to re-install WipperSnapper, follow the instructions at the top of this page.
### Moving from WipperSnapper to Arduino
If you want to use your board with Arduino, you will use the Arduino IDE to load _any_ sketch onto your board.
First, follow the page below to set up your Arduino IDE environment for use with your board.
[Setup Arduino IDE](https://learn.adafruit.com/adafruit-fruit-jam/arduino-ide-setup)
Then, follow the page below to upload the "Arduino Blink" sketch to your board.
[Upload Arduino Blink Sketch](https://learn.adafruit.com/adafruit-fruit-jam/blink-2)
Uploading this sketch will overwrite WipperSnapper. If you want to re-install WipperSnapper, follow the instructions at the top of this page.
### Factory Resetting a WipperSnapper Board
Sometimes, hardware gets into a state that requires it to be "restored" to the original state it shipped in. If you'd like to get your board back to its original factory state, follow the guide below.
[Factory Reset Page](https://learn.adafruit.com/adafruit-fruit-jam/factory-reset)
# Adafruit Fruit Jam
## WipperSnapper Essentials
You've installed WipperSnapper firmware on your board and connected it to Adafruit IO. Next, let's learn how to use Adafruit IO!
The Adafruit IO supports a large number of _components. Components_ are physical parts such as buttons, switches, sensors, servos, LEDs, RGB LEDs, and more.
The following pages will get you up and running with WipperSnapper as you interact with your board's LED, read the value of a push button, send the value of an I2C sensor to the internet, and wirelessly control colorful LEDs.
### Parts
The following parts are **required** to complete the WipperSnapper essentials pages for this board:
- An I2C sensor like the MCP9808 temperature sensor.
### Adafruit MCP9808 High Accuracy I2C Temperature Sensor Breakout
[Adafruit MCP9808 High Accuracy I2C Temperature Sensor Breakout](https://www.adafruit.com/product/5027)
The MCP9808 digital temperature sensor is one of the more accurate/precise we've ever seen, with a typical accuracy of ±0.25°C over the sensor's -40°C to +125°C range and precision of +0.0625°C. They work great with any microcontroller using standard I2C. With...
In Stock
[Buy Now](https://www.adafruit.com/product/5027)
[Related Guides to the Product](https://learn.adafruit.com/products/5027/guides)
Info: You can substitute your sensor for the suggested MCP9808 used in this guide, see your product's learn guide for WipperSnapper instructions tailored specifically to that sensor / component.
If you don't have one then you can test I2C functionality by running an I2C Scan and checking for the built in TLV320DAC3100 audio DAC (I2C address 0x18).
- Cable or set of wires to connect your I2C component (like our handy StemmaQT cables for I2C)
### STEMMA QT / Qwiic JST SH 4-pin Cable - 100mm Long
[STEMMA QT / Qwiic JST SH 4-pin Cable - 100mm Long](https://www.adafruit.com/product/4210)
This 4-wire cable is a little over 100mm / 4" long and fitted with JST-SH female 4-pin connectors on both ends. Compared with the chunkier JST-PH these are 1mm pitch instead of 2mm, but still have a nice latching feel, while being easy to insert and remove.
Out of Stock
[Buy Now](https://www.adafruit.com/product/4210)
[Related Guides to the Product](https://learn.adafruit.com/products/4210/guides)
- A variable resistance component, like a rotary potentiometer or light-dependent resistor. We recommend using this 10K variable resistor (potentiometer) which comes with an appropriate cable (JST-PH 3pin male).
### STEMMA Wired Potentiometer Breakout Board - 10K ohm Linear
[STEMMA Wired Potentiometer Breakout Board - 10K ohm Linear](https://www.adafruit.com/product/4493)
For the easiest way possible to measure twists, turn to this STEMMA potentiometer breakout (ha!). This plug-n-play pot comes with a JST-PH 2mm connector and a matching [JST PH 3-Pin to Male Header Cables - 200mm](https://www.adafruit.com/product/3893), so wiring up is a cinch....
Out of Stock
[Buy Now](https://www.adafruit.com/product/4493)
[Related Guides to the Product](https://learn.adafruit.com/products/4493/guides)
# Adafruit Fruit Jam
## Auto-Config
Your board probably has a WS281x RGB LED ( **NeoPixel** , in Adafruit jargon), or a normal Light Emitting Diode, built in. Chances are high that it has a **button** too!
Setting up components on your WipperSnapper device is easy, but to make life even easier we've added the ability to **automatically configure** the built-in components for all the supported boards! ([Let us know](https://github.com/adafruit/Wippersnapper_Boards/issues) if we're missing any)
On this page, you'll learn how to use the Auto-Config dialog, along with importing and exporting WipperSnapper device configurations for easy project duplication.
Later pages show details of the individual components and their specific use.
## Where are the Automatic Component Configuration options?
On the device page for your board, make sure the status of the device is **Online** , then click the **Auto Config button** at the top next to the New Component button.
From here you can **export** your boards configuration (all the components and settings), backing it up for later. Allowing you to easily recreate, duplicate, or share your project with others. It's human readable JSON!
**Importing** backed up config files, or from a project learn guide, completes the process. Just note that you may have to unselect any incompatible components to successfully complete the import. Try first then adjust if required.
Lastly is the option for **Magic Config** , which loads the default configuration for your board, adding all the built in components in just a couple of clicks!
## Magic Config
Click the **Magic Config button** shown above, and the dialog for adding all your built-in components will load.
Some components may be unselected, due to being less popular, possibly conflicting, or included on older board models.
You can select any of the unselected components, and revisit the magic config dialog any time in the future.
Other components may warn of pin or address incompatibilities, like the warning shown for an I2C address conflict in this image.
Unselect any conflicting components, then the **Auto Configure button** will appear, click it to proceed.
Your components will be immediately added, and start reporting data right away!
If your board has two of the same type of component, only one may successfully initialise and the other will fail, but that's expected!
It's usually the case when there is a legacy battery charger and a more modern alternative, and whichever is present on your board will successfully get added (while the other fails to add).
That's it! Now you can adjust the NeoPixel, setup a reactive Action on button press, or track the battery level with a notification email in just a couple more clicks.
Read over the next few pages to see how you use the components...
# Adafruit Fruit Jam
## LED Blink
Info: This demo shows controlling an LED from Adafruit IO. The same kind of control can be used for relays, lights, motors, or solenoids.
One of the first programs you typically write to get used to embedded programming is a sketch that repeatably blinks an LED. IoT projects are _wireless,_ so after completing this section, you'll be able to turn on (or off) the LED built into your board from anywhere in the world.
## Where is the LED on my board?
The Adafruit Fruit Jam has an onboard Red LED located in the top middle of the image (highlighted RED), to the left of the USB-C connector.
It is attached to **GPIO29**.
Take note that it uses an inverted signal, where `0` means On instead of usually meaning Off.
## Create a LED Component on Adafruit IO
On the device page, click the New Component (or "+") button to open the component picker.
Search for the component name by entering `LED` into the text box on the component picker, the list of components should update as soon as you stop typing.
### Filtering and searching for components
Since WipperSnapper supports such a large number of components, there is keyword filtering. Try searching for various keywords, like:
- component names: `aht20`, `servo`, `buzzer`, `button`, `led`, etc
- sensor types: `light`, `temperature`, `pressure`, `humidity`, etc
- interface: `i2c`, `uart`, `ds18x20`, `pin`, etc (also I2C addresses e.g. `0x44`)
- vendor: `Adafruit`, `ASAIR`, `Infineon`, `Bosch`, `Honeywell`, `Sensirion`, etc
There are also product and documentation links to every component. Follow the links beneath the component descriptions to be taken to the appropriate product page or Learn Guide
Select the **LED** from the list of components.
On the Create LED Component form, the board's LED pin is pre-selected.
Click Create Component.
Behind the scenes, Adafruit IO sends send a command to your board running WipperSnapper telling it to configure "LED Pin" as a digital output.
Your board's page on Adafruit IO shows a new LED component.
You'll notice that the LED component shows as having the status Off, but the Red LED is actually _On_ right now!
Toggling the component to On switches the LED to Off. To fix the labels click the settings cog for the LED.
Then update the labels for the Off and On state and click **Update Component**. You can also change the Icons! There are two types of icons, the first supports a weight setting like regular or light, and the second uses the full color Font-Awesome icons (emoji's, etc).
That's better, now it looks correct, even if _in-reality_ it's still sending a 0 to the feed to turn _On_ the LED.
## Usage
On the board page, toggle the LED component by clicking the toggle switch. This should turn your board's built-in LED on or off.
# Adafruit Fruit Jam
## Read a Push-button
Info: This demo shows reading the state of a push-button from WipperSnapper. But the same kind of control can be used for reading switches, break beam sensors, and other digital sensors.
You can configure a board running WipperSnapper to read data from standard input buttons, switches, or digital sensors, and send the value to Adafruit IO.
From Adafruit IO, you will configure one of the pushbuttons on your board as a push button component. Then, when the button is pressed (or released), a value will be published to Adafruit IO.
## Button Location
This example uses the board's built-in push-button and internal pull-up resistor instead of wiring a push-button up.
There are three buttons available on the right edge of the board:
- **Button #1** - Located on GPIO0.
It is also the UF2 BOOT button and is broken out on the 2x16 header.
- **Button #2** - Located on GPIO4.
- **Button #3** - Located on GPIO5.
For this example we'll be using Button #1 towards the bottom right corner of the board.
## Create a Push-button Component on Adafruit IO
On the device page, click the New Component (or "+") button to open the component picker.
Search for the component name by entering `push` into the text box on the component picker, the list of components should update as soon as you stop typing.
### Filtering and searching for components
Since WipperSnapper supports such a large number of components, you can use filtering. Try searching for various keywords, like:
- component names:` aht20`, `servo`, `buzzer`, `button`, `potentiometer`, etc
- sensor types: `light`, `temperature`, `pressure`, `humidity`, etc
- interface: `i2c`, `uart`, `ds18x20`, `pin`, etc (also I2C addresses e.g. `0x44`)
- vendor: `Adafruit`, `ASAIR`, `Infineon`, `Bosch`, `Honeywell`, `Sensirion`, etc
There are also added product and documentation links for every component. Follow the links beneath the component descriptions to be taken to the appropriate product page or Learn Guide.
Select the **Push Button** from the list of results to go to the component configuration page.
There will be a back button if you select the wrong component, and you can use the Edit component icon (⚙️) on the device page to update the component configuration in the future.
The "Create Push Button Component" form presents you with options for configuring the push button.
Start by selecting the board's pin connected to the push button.
In this example the automatically selected "Button" labelled pin is the correct pin, so just update the label.
The _Return Interval_ dictates how frequently the value of the push-button will be sent from the board to Adafruit IO.
For this example, you will configure the push button's value to be only sent when the value changes (i.e. when it's either pressed or depressed).
Finally, check the **Specify Pin Pull Direction ** checkbox and select the pull direction.
Make sure the form's settings look like the following screenshot. Then, click **Create Component**.
Adafruit IO sends a command to your WipperSnapper board, telling it to configure the GPIO pin you selected to behave as a digital input pin and to enable it to pull up the internal resistor.
Your board's page should also show the new push-button component.
Push the button on your board to change the value of the push-button component on Adafruit IO.
# Adafruit Fruit Jam
## NeoPixel LED
Your board has a WS281x RGB LED (NeoPixel, in Adafruit jargon) built in. Boards running the WipperSnapper firmware can be wirelessly controlled by Adafruit IO to interact with NeoPixels.
On this page, you'll learn how to change the color and brightness of the NeoPixel built into your board from Adafruit IO.
## Where is the NeoPixel on my board?
Located on the left hand side of the board are the 5 NeoPixels (RGB LEDs), highlighted here in red. It's a single chain of 5 pixels, using GPIO Pin 32.
It's initially used to flash the changes in board status while connecting, but after the device comes online it can be used for whatever you like by simply adding the NeoPixel component to your device.
## Create the NeoPixel Component
Primary: If you used the Magic Config button to automatically configure the components on your board, then the NeoPixel component will already be configured. Skip ahead to the **Usage** section.
Don't know about Magic Config? Click the Auto-Config button on the device page for further details!
On the device page, click the New Component (or "+") button to open the component picker.
Search for the component name by entering `neopixel` into the text box on the component picker, the list of components should update as soon as you stop typing
### Filtering and searching for components
Since WipperSnapper supports such a large number of components, you can use keyword filtering. Try searching for various keywords, like:
- component names: `aht20`, `servo`, `buzzer`, `button`, `neopixel`, etc
- sensor types: `light`, `temperature`, `pressure`, `humidity`, etc
- interface: `i2c`, `uart`, `ds18x20`, `pin`, etc (also I2C addresses e.g. `0x44`)
- vendor: `Adafruit`, `ASAIR`, `Infineon`, `Bosch`, `Honeywell`, `Sensirion`, etc
There is also added product and documentation links for every component, follow the links beneath the component descriptions to be taken to the appropriate product page or Learn Guide
Select the **NeoPixel** from the list of results to go to the component configuration page.
There will be a back button if you select the wrong component, and you can use the Edit component icon (⚙️) on the device page to update the component configuration in the future.
The board NeoPixel pin is automatically found and selected.
Update the **Number of Pixels** to `5`, and leave the brightness at 255 (full) unless you prefer things more dim.
Click **Create Component**
Behind the scenes, Adafruit IO sends a command to your board running WipperSnapper firmware telling it to configure the pin as a NeoPixel component with the settings from the form.
The Device page shows the NeoPixel component.
## Set the NeoPixel's RGB Color
Since no colors have been set yet, the color picker's default value is `#000000` (black in hex color code) and appears "off". You can change that to make the NeoPixel shine brightly!
On the NeoPixel component, click the color dropper at the end of the color swatch list.
A color picker pops open! Next: learning how Adafruit IO uses hex color codes to represent the colors on your NeoPixel.
### Hex Colors 101
The color picker on Adafruit IO uses hex color codes to represent Red, Green, and Blue values. For example, `#FF0000` is the hex color code for the color red. The colors (`#FF0000`) red component is `FF` (255 translated to decimal), the green component is `00` and the blue component is `00`. Translated to RGB format, the color is `RGB (255, 0, 0)`.
Using the color picker, or by manually entering a hex color code, select a color.
When you're ready to set the color of your device's NeoPixel, click **FILL WITH COLOR**. The NeoPixel will immediately glow!
## Set NeoPixel Brightness
If the NeoPixel is too bright (or too dim), you can change the overall brightness. Click the gear/cog icon on the NeoPixel component to open its settings.
On the NeoPixel component form, set Brightness to a value between 0 (fully off) and 255 (full brightness).
Click the **Update Component ** button to send the updated configuration to your device.
# Adafruit Fruit Jam
## I2C Sensors
Info:
Inter-Integrated Circuit, aka **I2C** , is a two-wire protocol for connecting sensors and "devices" to a microcontroller. A large number of sensors, including the ones sold by Adafruit, use I2C to communicate.
**Typically, using I2C with a microcontroller involves programming. Adafruit IO and WipperSnapper let you configure a microcontroller to read data from an I2C sensor and publish that data to the internet without writing code.**
The WipperSnapper firmware supports a number of I2C sensors, [viewable in list format here](https://github.com/adafruit/Wippersnapper_Components/tree/main/components/i2c).
- If you do not see the I2C sensor you're attempting to use with WipperSnapper, [Adafruit has a guide on adding a component to Adafruit IO WipperSnapper here](https://learn.adafruit.com/how-to-add-a-new-component-to-adafruit-io-wippersnapper).
On this page, you'll learn how to wire up an I2C sensor to your board. Then, you'll create a new component on Adafruit IO for your I2C sensor and send the sensor values to Adafruit IO. Finally, you'll learn how to locate, interpret, and download the data produced by your sensors.
## Parts
You will need the following parts to complete this page:
### Adafruit MCP9808 High Accuracy I2C Temperature Sensor Breakout
[Adafruit MCP9808 High Accuracy I2C Temperature Sensor Breakout](https://www.adafruit.com/product/5027)
The MCP9808 digital temperature sensor is one of the more accurate/precise we've ever seen, with a typical accuracy of ±0.25°C over the sensor's -40°C to +125°C range and precision of +0.0625°C. They work great with any microcontroller using standard I2C. With...
In Stock
[Buy Now](https://www.adafruit.com/product/5027)
[Related Guides to the Product](https://learn.adafruit.com/products/5027/guides)
### STEMMA QT / Qwiic JST SH 4-pin Cable - 100mm Long
[STEMMA QT / Qwiic JST SH 4-pin Cable - 100mm Long](https://www.adafruit.com/product/4210)
This 4-wire cable is a little over 100mm / 4" long and fitted with JST-SH female 4-pin connectors on both ends. Compared with the chunkier JST-PH these are 1mm pitch instead of 2mm, but still have a nice latching feel, while being easy to insert and remove.
Out of Stock
[Buy Now](https://www.adafruit.com/product/4210)
[Related Guides to the Product](https://learn.adafruit.com/products/4210/guides)
## Wiring
The MCP9808 comes with a STEMMA QT connector, which makes wiring it up quite simple and solder-free.
Simply connect the STEMMA QT cable from **the STEMMA QT port on your Fruit Jam** to **the STEMMA QT port on the MCP9808**.
If you prefer to use jumper wires, then connect to the double row female pin header port on the Fruit Jam. Check the Pinouts page of this guide or refer to the top cover plate silkscreen label.
- **Board power (3V or 5V) **to ** MCP9808 VIN**
- **Board ground ** to ** MCP9808 GND**
- **Board SCL ** to ** MCP9808 SCL**
- **Board SDA ** to ** MCP9808 SDA**
## Add an MCP9808 Component
On the device page, click the New Component (or "+") button to open the component picker.
Search for the component name by entering `MCP9808` into the text box on the component picker, the list of components should update as soon as you stop typing.
### Filtering and searching for components
Since WipperSnapper supports such a large number of components, there is keyword filtering. Try searching for various keywords, like:
- component names: `aht20`, `servo`, `buzzer`, `button`, `potentiometer`, etc
- sensor types: `light`, `temperature`, `pressure`, `humidity`, etc
- interface: `i2c`, `uart`, `ds18x20`, `pin`, etc (also I2C addresses e.g. `0x44`)
- vendor: `Adafruit`, `ASAIR`, `Infineon`, `Bosch`, `Honeywell`, `Sensirion`, etc
There are added product and documentation links for every component, follow the links beneath the component descriptions to be taken to the appropriate product page or Learn Guide.
Select the **MCP9808** from the list of results to go to the component configuration page.
There will be a back button if you select the wrong component, and you can use the Edit component icon (⚙️) on the device page to update the component configuration in the future.
On the component configuration page, the MCP9808's I2C sensor address should be listed along with the sensor's settings.
Warning: The onboard TLV320DAC3100 uses the same I2C address as the default MCP9808 address (`0x18`). To avoid this conflict you must solder a jumper closed on the back of the MCP9808 to switch it to using an alternative address. See the [MCP9808 Learn Guide's Pinout page](https://learn.adafruit.com/adafruit-mcp9808-precision-i2c-temperature-sensor-guide/pinouts#optional-pins-2958189) for more details on the address pins.
In the New Component dialog, click the **Select I2C Address** drop-down, then select the other drop-down option (alternative address) instead of the default address of 0x18, shown as `0x1c` here.
The remaining images of the **New Component** dialog are templated and show the default address of 0x18.
The MCP9808 sensor can measure ambient temperature. This page has individual options for reading the ambient temperature, in either Celsius or Fahrenheit. You may select the readings which are appropriate to your application and region.
The **Send Every** option is specific to each sensor measurement. This option will tell the board how often it should read from the sensor and send the data to Adafruit IO. Measurements can range from every 30 seconds to every 24 hours.
For this example, set the **Send Every ** interval for both seconds to **Every 30 seconds. ** Click **Create Component**.
The board page should now show the MCP9808 component you created. After the interval you configured elapses, the WipperSnapper firmware running on your board automatically reads values from the sensor and sends them to Adafruit IO.
## Read I2C Sensor Values
Now to look behind the scenes at a powerful element of using Adafruit IO and WipperSnapper. When a new component is created on Adafruit IO, an [Adafruit IO Feed](https://learn.adafruit.com/adafruit-io-basics-feeds) is also created. This Feed holds your sensor component values for long-term storage (30 days of storage for Adafruit IO Free and 60 days for Adafruit IO Plus plans).
Aside from holding the **values** read by a sensor, the component's feed also holds **metadata** about the data pushed to Adafruit IO. This includes settings for whether the data is public or private, what license the stored sensor data falls under, and a general description of the data.
Next, to look at the sensor temperature feed. To navigate to a component's feed, click on the chart icon in the upper-right-hand corner of the component.
On the component's feed page, you'll each data point read by your sensor and when they were reported to Adafruit IO.
### Doing more with your sensor's Adafruit IO Feed
This only scratches the surface of what Adafruit IO Feeds can accomplish for your IoT projects. For a complete overview of Adafruit IO Feeds, including tasks like downloading feed data, sharing a feed, removing erroneous data points from a feed, and more, [head over to the "Adafruit IO Basics: Feed" learning guide](https://learn.adafruit.com/adafruit-io-basics-feeds).
# Adafruit Fruit Jam
## Analog Input
Your microcontroller board has both digital and analog signal capabilities. Some pins are analog, some are digital, and some are capable of both. Check the **Pinouts** page in this guide for details about your board.
Analog signals are different from digital signals in that they can be _any_ voltage and can vary continuously and smoothly between voltages. An analog signal is like a dimmer switch on a light, whereas a digital signal is like a simple on/off switch.
Digital signals only can ever have two states, they are either are **on** (high logic level voltage like 3.3V) or **off** (low logic level voltage like 0V / ground).
By contrast, analog signals can be any voltage in-between on and off, such as 1.8V or 0.001V or 2.98V and so on.
Analog signals are continuous values which means they can be an _infinite_ number of different voltages. Think of analog signals like a floating point or fractional number, they can smoothly transiting to _any_ in-between value like 1.8V, 1.81V, 1.801V, 1.8001V, 1.80001V and so forth to infinity.
Many devices use analog signals, in particular sensors typically output an analog signal or voltage that varies based on something being sensed like light, heat, humidity, etc.
## Analog to Digital Converter (ADC)
An analog-to-digital-converter, or ADC, is the key to reading analog signals and voltages with a microcontroller. An ADC is a device that reads the voltage of an analog signal and converts it into a digital, or numeric, value. The microcontroller can’t read analog signals directly, so the analog signal is first converted into a numeric value by the ADC.
The black line below shows a digital signal over time, and the red line shows the converted analog signal over the same amount of time.
Once that analog signal has been converted by the ADC, the microcontroller can use those digital values any way you like!
## Potentiometers
A potentiometer is a small variable resistor that you can twist a knob or shaft to change its resistance. It has three pins. By twisting the knob on the potentiometer you can change the resistance of the middle pin (called the wiper) to be anywhere within the range of resistance of the potentiometer.
By wiring the potentiometer to your board in a special way (called a voltage divider) you can turn the change in resistance into a change in voltage that your board’s analog to digital converter can read.
To wire up a potentiometer as a voltage divider:
- Connect **one outside pin** to **ground**
- Connect **the other outside pin** to **voltage in (e.g. 3.3V)**
- Connect **the middle pin** to **an analog pin (e.g. A0)**
## Hardware
In addition to your microcontroller board, you will need the following hardware to follow along with this example.
**Potentiometer**
### STEMMA Wired Potentiometer Breakout Board - 10K ohm Linear
[STEMMA Wired Potentiometer Breakout Board - 10K ohm Linear](https://www.adafruit.com/product/4493)
For the easiest way possible to measure twists, turn to this STEMMA potentiometer breakout (ha!). This plug-n-play pot comes with a JST-PH 2mm connector and a matching [JST PH 3-Pin to Male Header Cables - 200mm](https://www.adafruit.com/product/3893), so wiring up is a cinch....
Out of Stock
[Buy Now](https://www.adafruit.com/product/4493)
[Related Guides to the Product](https://learn.adafruit.com/products/4493/guides)
## Wire Up the Potentiometer
Connect the potentiometer to your board as follows.
- **Potentiometer GND** to **Fruit Jam GND (black wire)**
- **Potentiometer wiper** to **Fruit Jam A0 (white wire)**
- **Potentiometer positive** to **Fruit Jam 3.3V (red wire)**
## Create a Potentiometer Component on Adafruit IO
On the device page, click the New Component (or "+") button to open the component picker.
Search for the component name by entering `potentiometer` into the text box on the component picker, the list of components should update as soon as you stop typing.
### Filtering and searching for components
Since WipperSnapper supports such a large number of components, there is keyword filtering. Try searching for various keywords, like:
- component names: `aht20`, `servo`, `buzzer`, `button`, `potentiometer`, etc
- sensor types: `light`, `temperature`, `pressure`, `humidity`, etc
- interface: `i2c`, `uart`, `ds18x20`, `pin`, etc (also I2C addresses e.g. `0x44`)
- vendor: `Adafruit`, `ASAIR`, `Infineon`, `Bosch`, `Honeywell`, `Sensirion`, etc
There are also added product and documentation links for every component, follow the links beneath the component descriptions to be taken to the appropriate product page or Learn Guide.
Select the **Potentiometer** from the list of results to go to the component configuration page.
There will be a back button if you select the wrong component, and you can use the Edit component icon (⚙️) on the device page to update the component configuration in the future.
On the _Create Potentiometer Component_ form:
- Set **Potentiometer Pin** to **A0**
- Select **"On Change"** as the **Return Interval**
- Select **Raw Analog Value** as the **Return Type**
Then, click Create Component
The potentiometer component appears on your board page! Next, learning to read values from it.
## Read Analog Pin Values
Rotate the potentiometer to see the value change.
_What do these values mean?_
WipperSnapper reports ADC "raw values" as 16-bit unsigned integer values. Your potentiometer will read between 0 (twisting the pot to the leftmost position) and 65535 (twisting the pot to the rightmost position).
## Read Analog Pin Voltage Values
You can update the potentiometer component (or any analog pin component in WipperSnapper) to report values in Volts. To do this, on the right-hand side of the potentiometer component, click the cog button.
Under **Return Type** , click Voltage.
Click Update Component to send the updated component settings to your board running WipperSnapper.
Now, twist the potentiometer to see the value reported to Adafruit IO in Volts!
# Adafruit Fruit Jam
## Factory Reset
The Adafruit Fruit Jam microcontroller ships running a NeoPixel rainbow swirl. It's lovely, but you probably had other plans for the board. As you start working with your board, you may want to return to the original code to begin again, or you may find your board gets into a bad state. Either way, this page has you covered.
Danger: Completing a factory reset will erase your board's firmware which is also used for storing CircuitPython/Arduino/Files! Be sure to back up your data first just in case.
# Step 1. Download the factory-reset.uf2 file
Save the following file wherever is convenient for you. You will need to access it to copy it to your board.
[Click to download the Adafruit Fruit Jam Factory Reset UF2](https://github.com/adafruit/Adafruit-Fruit-Jam-PCB/raw/main/factory-reset/Adafruit_Fruit_Jam_Factory_Reset.uf2)
# Step 2. Enter RP2350 bootloader mode
Entering the RP2350 bootloader is easy. Complete the following steps.
**Before you start, make sure your microcontroller is plugged into USB port to your computer using a data/sync cable.** Charge-only cables will not work!
**Turn on the On/Off switch** - check that you see the ON light on so you know the board is powered, a prerequisite!
To enter the bootloader:
1. **Press and hold the BOOT/BUTTON1 button down.** Don't let go of it yet!
2. **Press and release the Reset button.** You should still have the BOOT/BUTTON1 button pressed while you do this.
3. **Continue holding the BOOT/BUTTON1 button until you see the RP2350 drive appear.**
4. You can now release but BOOT/BUTTON1 button.
# Step 3. Drag UF2 file to RP2350
Navigate to the folder where you downloaded the **factory-reset.uf2** file from Step 1.
Drag the **factory-reset.uf2** file to the **RP2350** drive.
The **RP2350** drive will disappear.
The board will automatically reboot.
The onboard NeoPixels on the Fruit Jam will light up in a rainbow swirl.
You've successfully returned your board to a factory reset state!
## Flash Resetting UF2
If your board ever gets into a really _weird_ state and doesn't even show up when loading code, try loading this 'nuke' UF2 which will do a 'deep clean' on your Flash Memory. **You will lose all the files on the board** , but at least you'll be able to revive it! Download the file below, and follow the instructions in Step 2 and Step 3 above to load this UF2. Then, start again at Step 1 to return your board to factory reset state.
[Download flash erasing "nuke" UF2 for RP2350](https://cdn-learn.adafruit.com/assets/assets/000/132/526/original/rp2350_flash_nuke.uf2?1726692324)
# Adafruit Fruit Jam
## Upgrading AirLift Firmware
Occasionally new firmware for the ESP32-C6 WiFi coprocessor onboard your board may become available to provide bug fixes or enhanced capabilities. The steps below show how to upgrade that firmware.
### Step 1. Download nina-fw-upgrade.uf2 File
Save the following file wherever is convenient for you. You will need to access it to copy it to your board.
Danger: The UF2 BELOW IS NOT CURRENTLY WORKING AS DESCRIBED. It does not contain the updating code. For now, install the UF2, and then download [nina-fw-upgrade-fruitjam.py](https://github.com/adafruit/Adafruit_Learning_System_Guides/raw/refs/heads/main/Adafruit_ESP32_Arduino_Demos/ESP32_C6_Firmware_Updater/nina-fw-upgrade-fruitjam.py). Rename the downloaded file to **code.py** and replace the **code.py** on CIRCUITPY with the new **code.py**. Then install the **neopixel.mpy** and **adafruit_miniesptool.mpy** library files to **lib/** on CIRCUITPY. Then continue with the procedure below.
[Download nina-fw-upgrade.uf2 ](https://github.com/adafruit/Adafruit_Learning_System_Guides/raw/refs/heads/main/Adafruit_ESP32_Arduino_Demos/ESP32_C6_Firmware_Updater/nina-fw-upgrade.uf2)
## Step 2. Download NINA Firmware
This firmware runs on the ESP32-C6 co-processor. Save the following file to a location on your computer that is convenient for you. You will need to access it during a later step.
For the Adafruit Fruit Jam, you will want to download the file which is named something like _NINA\_ADAFRUIT- **fruitjam\_c6** -3.3.0.bin._
[Download Latest NINA-FW](https://github.com/adafruit/nina-fw/releases/latest)
## Step 3. Enter Bootloader Mode
To enter the bootloader, hold down the **BOOT/**** BOOTSEL button **(highlighted in red above), and while continuing to hold it (don't let go!), press and release the **reset button **(highlighted in blue above).**Continue to hold the BOOT/BOOTSEL button until the RP2350 drive appears!**
### Step 4. Drag UF2 File to RP2350
1. Navigate to the folder where you downloaded the **nina-fw-upgrade.uf2** file from Step 1.
2. Drag the **nina-fw-upgrade.uf2** file to the RP2350 drive.
3. The RP2350 drive will disappear and the board will automatically reboot.
- After the Fruit Jam reboots, a **CIRCUITPY** and **CPSAVES** volumes should be mounted on your computer.
### Step 4. Drag BIN file to CIRCUITPY
- Navigate to where you downloaded the nina fw bin file from Step 2
- Drag the .bin file to the **CIRCUITPY** drive
- **Rename ** the .bin file to **nina.bin**
Yellow: Ensure the .bin file on the **CIRCUITPY** drive is named **nina.bin** before proceeding to the next step.
### Step 4. Start Updater
**To start the updater for the Fruit Jam:**
- Ensure the Fruit Jam NeoPixels are glowing blue (you may need to reset the board)
- Press the Fruit Jam's Button #3
- Your Fruit Jam's NeoPixels will glow yellow while the board updates the ESP32-C6's firmware
- After the firmware is updated, the NeoPixels should blink green.
### Fruit Jam NeoPixels are flashing red after I press the button
Ensure you downloaded the correct .bin file, renamed it to **nina.bin** , and placed it on the root of your **CIRCUITPY** drive (not in a folder).
The firmware updating process is finished! You can delete **nina.bin** from the **CIRCUITPY** drive.
## **Alternative Update Method: Passthrough**
If the method above does not work, or you are experiencing errors, try this alternative method of updating your C6 module which allows your board to act as a programmer for the ESP32-C6 AirLift module.
## Upload Passthrough Code
First, you'll need to upload the code below to allow your board to act as a programmer for the ESP32-C6 AirLift module.
**Back up any code and files on your CIRCUITPY drive**. The code will overwrite the drive's contents. You should not end up losing any files on the QSPI flash, but it's a good idea to back them up anyways.
Download the **UF2** file for your board and save it to your computer's Desktop.
[Adafruit Fruit Jam Serial ESP32-C6 Passthrough UF2](https://cdn-learn.adafruit.com/assets/assets/000/138/701/original/SerialESPPassthrough.ino.uf2?1754326310)
## Enter Bootloader Mode
To enter the bootloader, hold down the **BOOT/**** BOOTSEL button **(highlighted in red above), and while continuing to hold it (don't let go!), press and release the **reset button **(highlighted in blue above). **Continue to hold the BOOT/BOOTSEL button until the RP2350 drive appears!**
Find the **.UF2** file you downloaded and drag that file to the new drive on your computer.
The board's LED should flash and the drive will disappear. Your board should re-enumerate USB and appear as a COM or Serial port on your computer. Make a note of the serial port by checking the **Device Manager** (Windows) or **typing `ls /dev/cu*` or `/dev/tty*`** (Mac or Linux) **in a terminal.**
## **Download NINA Firmware**
**Click the link below** to download the latest version of the NINA firmware for the ESP32-C6. **Unzip** it **and save the .bin file to your desktop**.
[Download the latest nina-fw .bin file](https://github.com/adafruit/nina-fw/releases/latest)
Next, you'll need to flash the firmware to your ESP32-C6 AirLift module.
If you're using the Google Chrome browser or Microsoft Edge (version 89 or later), you may follow the instructions below for programming using your board.
For advanced users who have **esptool.py** installed, skip to the bottom of the page.
## Upload NINA Firmware
Next, you'll need to upload the new version of NINA firmware to your ESP32-C6 AirLift. To do this, we'll use the web-based implementation of the flasher tool for Espressif chips, ESPTool. You will need to be running Google Chrome or Microsoft Edge (version 89 or later) to follow the steps below.
**Safari and Firefox, etc. are _not_**** supported **because we need Web Serial and only Chrome is supporting it to the level needed.** If you're using an unsupported browser **, you'll need to either switch to Google Chrome or upload NINA firmware using the Python** esptool.py** program from your computer (Scroll down to _Upload NINA Firmware with esptool.py,_)
Warning:
On your Google Chrome browser, navigate to [https://adafruit.github.io/Adafruit\_WebSerial\_ESPTool/](https://adafruit.github.io/Adafruit_WebSerial_ESPTool/)
Turn _ **on** _ the toggle labeled **No reset for Passthrough updates** :
In the top-right corner, select 115200 as the baud rate and click the **Connect** button.
You will get a pop-up asking you to select the board's COM or Serial port.
- If there are a lot of boards and ports appearing in this list and you're not sure what to select - remove all other USB devices so only your board is attached, that way there's no confusion over multiple ports!
Click **Connect**.
Upon success, you will see that it is connected and will print out a unique MAC address identifying the board.
Once you have successfully connected, a command toolbar will appear at the top of the screen.
Verify that the offset is **0x0** and choose the **NINA\_....bin** file you downloaded above.
Click the **program** button to flash the firmware to your ESP32-C6 AirLift.
ESPTool will take a few minutes to write firmware to your device. After it's complete, the progress bar will disappear and the console will print _"To run the new firmware,..."_
Press the Reset button (or, on the RP2040 Pico, unplug your device from USB power) to get out of the ROM bootloader.
# Verify the New Firmware Version
To verify everything is working correctly, we'll load up some CircuitPython code.
**If you were previously using your ESP32-C6 project with CircuitPython** , you'll need to first reinstall CircuitPython firmware for your board. The QSPI flash should have retained its contents. If you don't see anything on the **CIRCUITPY** volume, copy files from the backup you made earlier to **CIRCUITPY**.
To verify the new ESP32-C6 WiFi firmware version is correct, [follow the Connect to WiFi step in this guide](https://learn.adafruit.com/adafruit-pyportal/internet-connect#connect-to-wifi-17-4) and come back here when you've successfully run the code. The REPL output should display the firmware version you flashed.
## (Advanced) Upload NINA Firmware with ESPTool.py
For advanced users who have **esptool.py** installed, run the following commands on your command line:
**If you're using macOS or Linux** - run the following command, replacing `/dev/ttyACM0` with the serial port of your board and `NINA_BIN` with the binary file you're flashing to the ESP32-C6.
`esptool --before no_reset -p /dev/ttyACM0 -b 115200 -c esp32-c6 chip_id`
`esptool --before no_reset -p /dev/ttyACM0 -b 115200 -c esp32-c6 write_flash 0 NINA_BIN.bin`
**If you're using Windows** - run the following command, replacing `COM7` with the serial port of your board and `NINA_BIN` with the binary file you're flashing to the ESP32
`esptool.py --port COM7 --before no_reset -b 115200 -c esp32-c6 write_flash 0 NINA_BIN.bin`
The command should detect the ESP32-C6 and will take a minute or two to upload the firmware.
- If ESPTool doesn't detect the ESP32-C6, make sure you've uploaded the correct **.UF2** file to the bootloader and are using the correct serial port.
Once the firmware is fully uploaded, press the Reset button (or, on the RP2040 Pico, unplug your device from USB power) to get out of the ROM bootloader mode.
# Adafruit Fruit Jam
## Downloads
## Files
- [RP2350 Datasheet](https://cdn-learn.adafruit.com/assets/assets/000/132/246/original/rp2350-datasheet.pdf?1725991815)
- [EagleCAD PCB Files on GitHub](https://github.com/adafruit/Adafruit-Fruit-Jam-PCB)
- [3D models on GitHub](https://github.com/adafruit/Adafruit_CAD_Parts/tree/main/6200%20Fruit%20Jam "3D models on GitHub")
- [Fritzing object in the Adafruit Fritzing Library](https://github.com/adafruit/Fritzing-Library/blob/master/parts/Adafruit%20Fruit%20Jam.fzpz)
- [PrettyPins PDF on GitHub](https://github.com/adafruit/Adafruit-Fruit-Jam-PCB/blob/main/Adafruit_Fruit_Jam_PrettyPins.pdf)
- [PrettyPins SVG](https://github.com/adafruit/Adafruit-Fruit-Jam-PCB/blob/main/Adafruit_Fruit_Jam_PrettyPins.svg)
## Schematic and Fab Print
## Primary Products
### Adafruit Fruit Jam - Mini RP2350 Computer
[Adafruit Fruit Jam - Mini RP2350 Computer](https://www.adafruit.com/product/6200)
We were catching up on a recent [hackaday hackchat with eben upton](https://hackaday.io/event/202122-raspberry-pi-hack-chat-with-eben-upton) and learned some fun facts: such as the DVI hack for the RP2040 was inspired by
Out of Stock
[Buy Now](https://www.adafruit.com/product/6200)
[Related Guides to the Product](https://learn.adafruit.com/products/6200/guides)
## Featured Products
### USB Type A to Type C Cable - approx 1 meter / 3 ft long
[USB Type A to Type C Cable - approx 1 meter / 3 ft long](https://www.adafruit.com/product/4474)
As technology changes and adapts, so does Adafruit. This **USB Type A to Type C** cable will help you with the transition to USB C, even if you're still totin' around a USB Type A hub, computer or laptop.
USB C is the latest industry-standard connector for...
In Stock
[Buy Now](https://www.adafruit.com/product/4474)
[Related Guides to the Product](https://learn.adafruit.com/products/4474/guides)
## Related Guides
- [Adafruit Qwiik/STEMMA QT 5 Port Hub](https://learn.adafruit.com/qwiik-stemma-qt-5-port-hub.md)
- [DC & USB Boarduino Kits](https://learn.adafruit.com/boarduino-kits.md)
- [Programmable 12v Outdoor Cafe Lights](https://learn.adafruit.com/programmable-12v-outdoor-cafe-lights.md)
- [Adafruit Arcade Bonnet for Raspberry Pi](https://learn.adafruit.com/adafruit-arcade-bonnet-for-raspberry-pi.md)
- [NeoKey Socket Breakout with NeoPixel for MX and CHOC Key Switches](https://learn.adafruit.com/neokey-breakout.md)
- [Improve Your Code with Pylint and Black](https://learn.adafruit.com/improve-your-code-with-pylint.md)
- [Where's My Friend? A Location-Aware Display with PyPortal and ItsASnap](https://learn.adafruit.com/where-s-my-friend-a-location-display-frame-with-pyportal.md)
- [NeoPixel Run LED Arcade Game](https://learn.adafruit.com/pixel-chase-game.md)
- [Using the CircuitPython Extension for Visual Studio Code](https://learn.adafruit.com/using-the-circuitpython-extension-for-visual-studio-code.md)
- [Adafruit CircuitPython Wii Classic Controller Library](https://learn.adafruit.com/adafruit-circuitpython-wii-classic-controller-library.md)
- [74HC595 Shift Register](https://learn.adafruit.com/74hc595.md)
- [CircuitPython Hardware: SD Cards](https://learn.adafruit.com/micropython-hardware-sd-cards.md)
- [Fisher-Price USB Foot Pedal](https://learn.adafruit.com/fisher-price-usb-foot-pedal.md)
- [Split Ortho Keyboard with TCA8418 Matrix Expanders](https://learn.adafruit.com/split-ortho-keyboard.md)
- [Adafruit SGP41 Multi-Pixel Gas Sensor Breakout](https://learn.adafruit.com/adafruit-sgp41-multi-pixel-gas-sensor-breakout.md)