Who else could pack a 600 MHz microcontroller into such a Teensy little board? The Teensy 4.0 features an ARM Cortex-M7 processor at 600 MHz, with a NXP iMXRT1062 chip, the fastest microcontroller available today - ten times faster than the Teensy 3.2! The NXP iMXRT1062 is a ‘cross-over’ processor, which has the functionality of a microcontroller, at the speeds of a microcomputer. It’s perfect for when you need tons of flash, RAM and, to crunch lots of data, or when you need two full speed USB ports. It even has a graphics processor! All this for two sawbucks.
Teensy 4.0 can be programmed using the Arduino IDE with Teensyduino add-on.
Power Consumption & Management When running at 600 MHz, Teensy 4.0 consumes approximately 100 mA current, considerably more than most microcontrollers. To help reduce power, Teensy 4.0 provides support for dynamic clock scaling. Unlike traditional microcontrollers, where changing the clock speed causes wrong baud rates and other issues, Teensy 4.0 hardware and Teensyduino’s software support for Arduino timing functions are designed to allow dynamically speed changes. Serial baud rates, audio streaming sample rates, and Arduino functions like delay() and millis(), and Teensyduino’s extensions like IntervalTimer and elapsedMillis, continue to work properly while the CPU changes speed.
Teensy 4.0 also provides a power shut off feature. By connecting a pushbutton to the On/Off pin, the 3.3V power supply can be completely disabled by holding the button for 5 seconds, and turned back on by a brief button press. If a coin cell is connected to VBAT, Teensy 4.0’s RTC also continues to keep track of date & time while the power is off.
Teensy 4.0 also can also be overclocked, well beyond 600 MHz!
- ARM Cortex-M7 at 600 MHz
- 1024K RAM (512K is tightly coupled)
- 2048K Flash (64K reserved for recovery & EEPROM emulation)
- 2 USB ports, both 480 MBit/sec
- 3 CAN Bus (1 with CAN FD)
- 2 I2S Digital Audio
- 1 S/PDIF Digital Audio
- 1 SDIO (4 bit) native SD
- 3 SPI, all with 16 word FIFO
- 3 I2C, all with 4 byte FIFO
- 7 Serial, all with 4 byte FIFO
- 32 general purpose DMA channels
- 31 PWM pins
- 40 digital pins, all interrrupt capable
- 14 analog pins, 2 ADCs on chip
- Cryptographic Acceleration
- Random Number Generator
- RTC for date/time
- Programmable FlexIO
- Pixel Processing Pipeline
- Peripheral cross triggering
- Power On/Off management
Have some info to add for this board? Edit the source for this page here.
This is the latest stable release of CircuitPython that will work with the Teensy 4.0.
Start here if you are new to CircuitPython.
Built-in modules available: _bleio, adafruit_bus_device, adafruit_pixelbuf, aesio, analogio, atexit, binascii, bitbangio, bitmaptools, board, busio, digitalio, displayio, errno, fontio, framebufferio, getpass, gifio, json, keypad, math, microcontroller, msgpack, neopixel_write, onewireio, os, pwmio, rainbowio, random, re, rtc, sdcardio, sharpdisplay, storage, struct, supervisor, terminalio, time, touchio, traceback, ulab, usb_cdc, usb_hid, usb_midi, vectorio, zlib
This is the latest unstable release of CircuitPython that will work with the Teensy 4.0.
Unstable builds have the latest features but are more likely to have critical bugs.
Built-in modules available: _bleio, adafruit_bus_device, adafruit_pixelbuf, aesio, analogio, atexit, binascii, bitbangio, bitmaptools, board, busio, digitalio, displayio, dotenv, errno, fontio, framebufferio, getpass, json, keypad, math, microcontroller, msgpack, neopixel_write, onewireio, os, pwmio, rainbowio, random, re, rtc, sdcardio, sharpdisplay, storage, struct, supervisor, terminalio, time, touchio, traceback, ulab, usb_cdc, usb_hid, usb_midi, vectorio, zlib
Every time we commit new code to CircuitPython we automatically build binaries for each board and language. The binaries are stored on Amazon S3, organized by board, and then by language. Try them if you want the absolute latest and are feeling daring or want to see if a problem has been fixed.
All previous releases are listed on GitHub, with release notes, and are available for download from Amazon S3. They are handy for testing, but otherwise we recommend using the latest stable release. Some older GitHub release pages include the same binaries for downloading. But we have discontinued including binaries as assets on newer release pages because of the large number of files for each release.