- Home
- Product Categories
- Teensy
- Teensy 3.2
Export Restrictions
This product has some level of export control/restriction, so may be delayed by 2-3 business days when shipping outside the United States. Contact us with questions, or we will contact you after you place your order.
images are CC BY-NC-SA 3.0
Description: The Teensy is a breadboard-friendly development board with loads of features in a, well, teensy package. Each Teensy 3.2 comes pre-flashed with a bootloader so you can program it using the on-board USB connection: No external programmer needed! You can program for the Teensy in your favorite program editor using C or you can install the Teensyduino add-on for the Arduino IDE and write Arduino sketches for Teensy!
The processor on the Teensy also has access to the USB and can emulate any kind of USB device you need it to be, making it great for USB-MIDI and other HID projects. The 32 bit processor brings a few other features to the table as well, such as multiple channels of Direct Memory Access, several high-resolution ADCs and even an I2S digital audio interface! There are also 4 separate interval timers plus a delay timer! Oh yeah, and all pins have interrupt capability. Also, it can provide system voltage of 3.3V to other devices at up to 100mA.
All of this functionality is jammed into a 1.4 x 0.7 inch board with all headers on a 0.1" grid so you can slap in on a breadboard and get to work! The Teensy 3.2 adds a more powerful 3.3 volt regulator, with the ability to directly power an ESP8266 Wifi, WIZ820io Ethernet, and other 3.3V add-on boards that require a little more power. Additionally, if it is used within the Teensy 3.1 limits of operation, the Teensy 3.2 and 3.1 are interchangeable!
Note: This does not come with a USB cable, please check below for an appropriate one.
Dimensions: 1.4 x 0.7" (~35 x 18 mm)
Features:
- 32 bit ARM Cortex-M4 72 MHz CPU (M4 = DSP extensions)
- 256K Flash Memory, 64K RAM, 2K EEPROM
- 21 High Resolution Analog Inputs (13 bits usable, 16 bit hardware)
- 34 Digital I/O Pins (5V tolerance on Digital Inputs)
- 12 PWM outputs
- 7 Timers for intervals/delays, separate from PWM
- USB with dedicated DMA memory transfers
- 3 UARTs (serial ports)
- SPI, I2C, I2S,CAN Bus, IR modulator
- I2S (for high quality audio interface)
- Real Time Clock (with user-added 32.768 crystal and battery)
- 16 DMA channels (separate from USB)
- Touch Sensor Inputs
Documents:
- Schematic
- Datasheet (MK20DX256VLH7)
- Teensy Quickstart
- Teensyduino Software
- Pin Assignment Charts
- Using the RTC
- Product Page
Customer Reviews
5 out of 5
Based on 3 ratings:
Amazing
It’s a flexible and powerful board, with huge capacity and small size, for me it is the best option for make projects.
Not your grandfather's Arduino
My video review: https://www.youtube.com/watch?v=4AWbB15eiJY
Cheers Joe
The second paragraph says that the Teensy can supply up to 100mA - the bigger regulator is supposed to be able to supply 250mA https://forum.pjrc.com/threads/29774-Teensy-3-2.
The new dedicated regulator is the ONLY difference between 3.1 and 3.2. (Version 3.1 used the regulator that is built into the microcontroller.) They are otherwise identical, so there should be no compatibility issues if you are putting these into something designed for version 3.1.
Shirley: In terms of compatibility, evidently the pad for the reset pin changed location in the Teensy 3.2 compared to the 3.1 In addition, the pads for USB D-/D+ also changed location. Unless you actually use the 3 pads or use one of the third party shields that had a pogo pin to bring out the reset pad to a pin, it should not present a compatibility problem.
RobBrownNZ, you might ask the same question at the forums at pjrc.com, which are the development forums for the Teensies.
I tried Teensy 3.1, and found that it didn’t reset reliably when it was powered straight from 3.3V (rather than from USB). Adding a capacitor on the reset pin helped but it still wasn’t 100%, and then I accidentally ripped the ‘R’ pad off the PCB and gave up on the board as a result. Has anyone else experienced unreliable resetting with these things? Any advice on how to improve it?