If you’re ready to step up your Arduino game from older 8-bit/16MHz microcontrollers, the SparkFun RedBoard Turbo is a formidable alternative. At its heart, the RedBoard Turbo uses the ATSAMD21G18, which is an ARM Cortex M0+, 32-bit microcontroller that can run at up to 48MHz. With an impressive 4MB of external flash memory and a UF2 (USB Flashing Format) bootloader, the RedBoard Turbo provides you with an economical and easy to use development platform if you're needing more power than the classic RedBoard.
The SparkFun RedBoard Turbo has been equipped with a USB interface for programming and power, a Qwiic connector, an RTC crystal, WS2812-based addressable RGB LED, 600mA 3.3V regulator, and a variety of other components. To power the RedBoard Turbo, just plug it into a USB port on your computer via the micro-B port or directly into the wall with the 5V tolerant barrel jack. Not near a USB port? No problem, the SparkFun RedBoard Turbo is also equipped with a LiPo Battery connector (for a single-cell 3.7-4.2V litium-polymer battery). The MCP73831's charge current is configured by a resistor value between 66kΩ and 2kΩ, to charge the battery at a rate between 15mA and 500mA, respectively. By default, the board is configured to charge the battery at around 250mA. If you’ve used any Arduino before, this pinout shouldn’t surprise you – the layout meets the Arduino 1.0 footprint standard, including a separate SPI header and additional I2C header.
The RedBoard Turbo can even be flashed over the Mass Storage Class (MSC) just like a removable flash drive, thanks the the UF2 bootloader. With this bootloader, the RedBoard Turbo shows up on your computer as a USB storage device without having to install drivers! From the Arduino IDE, you’ll still need to select the correct port on your machine, but you can just as easily use another programming language such as CircuitPython or MakeCode.
Note: The barrel jack connection on the RedBoard Turbo has a lower input voltage than most Arduino development boards. Make sure that you are using a power supply below 6V. Please be aware that the RedBoard Turbo is also a 3.3V device and not a 5V one like the original RedBoard.
If a board needs code or communicates somehow, you're going to need to know how to program or interface with it. The programming skill is all about communication and code.
Skill Level: Rookie - You will need a better fundamental understand of what code is, and how it works. You will be using beginner-level software and development tools like Arduino. You will be dealing directly with code, but numerous examples and libraries are available. Sensors or shields will communicate with serial or TTL.
See all skill levels
If it requires power, you need to know how much, what all the pins do, and how to hook it up. You may need to reference datasheets, schematics, and know the ins and outs of electronics.
Skill Level: Rookie - You may be required to know a bit more about the component, such as orientation, or how to hook it up, in addition to power requirements. You will need to understand polarized components.
See all skill levels
Based on 6 ratings:
2 of 2 found this helpful:
Just starting to use the board. I'm working on a problem with connecting a shifting uSD breakout board. After updating an SD library example sketch for the Serial port name change, I found that the standard SD library has some Serial.print statement embedded. A couple src/utilities/~.cpp files have these Serial.print statements embedded. This could get complicated if other libraries do the same. Otherwise the board is performing as advertised. The hookup guide is quite accurate and complete and excellent for getting up and going.
What's not to like!? UNO form factor with Qwiic and a LiPo battery connector. Now if i could figure out a way to dis-able the comm LEDs with something other than a chisel... It would be nice, for boards with battery power, to have a jumper that disables the LED. Just my thoughts on that. I like the SAMD21, as they seem to compile faster than, for example, the ESP8266. So i can make mistakes way faster with this board. Haven't used the Python yet. It's very easy to find when setting up the Arduino application. The board pops up on the list of ports in the Arduino application with the correct name for easy identification. The SerialUSB issue is similar, i think to the other SAMD21 boards i have. Definitely a win for me!
Taking one star as it does not work reliably with the OpenLog. This is a known issue - check the forums for progress,
It’s a nice board and works well. Make sure you read the page the board is on for some important info about setup. It’s not plug ‘n play but very easy to setup for the Arduino IDE. Also serial is different. You have to change it for it to work. All on the info page for the board.
As a novice tinkerer, this board is fun to use. I'm excited to learn how to program it to do the things I want. As of now, I have only used the pre written examples. They were written for the non-turbo board, but with a few Serial word replacements(check the forum for specifics "red board turbo") I was up and blinking. Quality looks good, and I am happy with the purchase.
I'm pretty impressed with this so far in most aspects, except one. Uploading sketches is pretty much a crapshoot. Sometimes works, sometimes not, tried it on three different computers, without hub. Usually uploads work, but sometimes it takes 10 to 20 tries.. I'm totally LOVING the Qwiic interface, using the small OLED display and the twist has been far easier than I would have thought. I'd actually like to see a version without the arduino headers, and maybe multiple Qwiic ports.
I've tried so many microcontrollers, including AVR and Arduino variants and shields, this board offered so many options with the mememory, speed and ports...I tried the blinking led with no problem whatsoever, BUT once I tried the serial communications and I coouldnt compile it! So I tried the serial communication example and the same issue, so I research the problem but I found that others havehad the same issue from the start and no answer has been given. It's not a hardware or installation issue, lack of suppor to solve this.