Search
1000 results for “adafruit”
-
Adafruit Blog: 10,000 Drum Machines. “10,000 Drum Machines is a collection of browser-based drum sequencing experiments created by Maxwell Neely-Cohen and other contributors.”
https://rbfirehose.com/2025/05/17/adafruit-blog-10000-drum-machines/
-
New York begins cargo drone trial between Manhattan and Brooklyn, deep dive with all we could find!
http://adafruit.com/nycdrones -
New York begins cargo drone trial between Manhattan and Brooklyn, deep dive with all we could find!
http://adafruit.com/nycdrones -
New York begins cargo drone trial between Manhattan and Brooklyn, deep dive with all we could find!
http://adafruit.com/nycdrones -
New York begins cargo drone trial between Manhattan and Brooklyn, deep dive with all we could find!
http://adafruit.com/nycdrones -
New York begins cargo drone trial between Manhattan and Brooklyn, deep dive with all we could find!
http://adafruit.com/nycdrones -
SHT41 is not too hot, not to cold - just right! 🌡️👌🔄🔗📚🐻🐻🐻👧
the SHT41 sits right between the SHT40 https://www.adafruit.com/product/4885 and the SHT45 https://www.adafruit.com/product/5665 with the same typical +-1.8% humidity accuracy as the SHT40 but better guaranteed performance at the edges of functionality: +-2.5% instead of 3.5%. Given its the same footprint as the SHT40 it's an easy respin, so here ya go
#SHT41 #JustRight #TemperatureSensor #HumidityAccuracy #Adafruit #Electronics #EasyReSpin NotTooHot #NotTooCold
-
SHT41 is not too hot, not to cold - just right! 🌡️👌🔄🔗📚🐻🐻🐻👧
the SHT41 sits right between the SHT40 https://www.adafruit.com/product/4885 and the SHT45 https://www.adafruit.com/product/5665 with the same typical +-1.8% humidity accuracy as the SHT40 but better guaranteed performance at the edges of functionality: +-2.5% instead of 3.5%. Given its the same footprint as the SHT40 it's an easy respin, so here ya go
#SHT41 #JustRight #TemperatureSensor #HumidityAccuracy #Adafruit #Electronics #EasyReSpin NotTooHot #NotTooCold
-
SHT41 is not too hot, not to cold - just right! 🌡️👌🔄🔗📚🐻🐻🐻👧
the SHT41 sits right between the SHT40 https://www.adafruit.com/product/4885 and the SHT45 https://www.adafruit.com/product/5665 with the same typical +-1.8% humidity accuracy as the SHT40 but better guaranteed performance at the edges of functionality: +-2.5% instead of 3.5%. Given its the same footprint as the SHT40 it's an easy respin, so here ya go
#SHT41 #JustRight #TemperatureSensor #HumidityAccuracy #Adafruit #Electronics #EasyReSpin NotTooHot #NotTooCold
-
Welcome to KAMPi! My Self-Built Digital Camera
Hello everyone! I have always wanted to build my own digital camera. But not just any digital camera, one I would actually use like a regular point-and-shoot camera. I wanted something that would give me traditional feel, but still shoot in 4K. A tall order for sure, and to top it all off, I wanted to build everything myself. Well the time has come. . . Please join me in welcoming KAMPi! Check out my build below.
Why KAMPi?
KAMPi is short for “Kampay” which is Tagalog slang for “Kanpai” the Japanese word for cheers. It also sounds like CAMPi another way of saying Pi Cam, which is exactly what it is – a digital camera built using a Raspberry Pi mini computer.
What’s Inside?
I built KAMPi from the ground up: selected, wired, and soldered the hardware electronics, 3D printed the parts, and prepared the software.
For the computer internals, I chose to use a Raspberry Pi Compute Module 5 which rides on a Waveshare Nano A. The camera imager and lens are from Raspberry Pi as well, the Raspberry Pi High Quality Camera with the 16mm Telephoto Lens. For the display I used a Pimoroni HyperPixel 4.0″ Hi-Res Display. The display is connected to the Waveshare Nano A via GPIO pins (the header of the Nano I soldered myself). Everything is packed together in a tight package shown above.
For the power electronics I chose to use a Pimoroni LiPo SHIM I purchased from Adafruit. I wired it up with a on/off switch and connected it to a USB-C plug.
For the trigger mechanism I chose to use Adafruit’s KB 2040 electronic board due to it’s small form factor, and also that it works over USB-C / USB serial. I also chose to use the KB 2040 because the HyperPixel 4.0 uses all the GPIO pins of the Waveshare Nano A and USB-C / USB serial seemed like a more straightforward alternative. Alternatively I could have used I2C, via the HyperPixel 4.0, but I didn’t have enough time to go that direction before the convention. The trigger itself is an illuminated pushbutton switch also from Adafruit.
I’m no expert in 3D printing and I originally wanted the form factor to be smaller. But since the camera cable stuck out from the top, I needed to make extend the base.
So I designed and 3D printed a cap portion to hold it all together.
I even added a hinge and latch lock to for easy access.
For the software, I wanted something simple. I’m running python script to take the photos. One thing to note is that the camera does not have any autofocus (which is exactly how I wanted it). That meant I needed to see what I’m shooting before taking the photo. I added a preview in the software, so I could focus the lens, and then take the shot.
The desktop above shows the camera python script and the folder where the photos are saved. You can also see the Circuitpython mounted “disk” of the KB 2040 on the desktop. I’m also a space nerd so I chose a James Webb galaxy image as a backdrop to show off the beautiful Pimironi display. I included a fun logo and added a nice rectangle so I could easily see the program icons on the desktop too.
KAMPi in Action
KAMPi is so new, I haven’t been able to test it in the wild yet. But here are some raw unprocessed photos from my home test shots.
https://www.instagram.com/reel/DMR6OegOWSn/?utm_source=ig_web_copy_link&igsh=MzRlODBiNWFlZA==
More to come from Opensaucelive!*
Tomorrow is Opensaucelive 2025 and I thought what better place to test and share my build there. Wow, I’m so excited to share KAMPi with everyone at Opensauce. If you see me, please do say hello. I’ll also upload some photos from KAMPi at Opensauce below:
[*UPDATED July 20, 2025] See above sample photos I took at Opensaucelive 2025 using KAMPi. I chose the sharpest in focus images to share. Since it was my first time shooting with it, many of the photos came out blurry – which was exactly what I was expecting! I wanted KAMPi to emulate the feel of a film camera, capturing the moment. And KAMPi did just that. I’m also sure I’ll get better at taking photos with KAMPi with a litter more practice 🙂
[*UPDATED Sept 20, 2025] Updated the description of the KB 2040 to provide additional info on why I decided to use it over I2C.
Kampay (Cheers) for now!
Did you like my build? Would you like to learn more about it? Let me know at the comments below!
If you enjoyed reading this post please be sure to like, and follow us here at SKKAW.BLOG (IG: @skkaw) for more geek and pop-culture goodness.
#Adafruit #camera #CamPi #ComputeModule5 #digitalCamera #DIY #DIYCamera #DIYDigitalCamera #KAMPi #Opensauce #OpenSauceLive #PiCam #RaspberryPi #RaspberryPiCamera #RaspberryPiComputeModule5 #RaspberryPiComputeModule5Camera #SelfMade #selfMadeDigitalCamera #selfBuilt #SelfMade #Waveshare
-
Adafruit Trinket M0 Moving COM Ports in Arduino
I’ve been playing around with the Adafruit Trinket M0 board in an effort to a) move over to 32-bit Cortex M processors from 8-bit AVRs; and b) get to know CircuitPython a little more. I know there are more powerful boards, but I liked the small form factor of the Trinket M0 and see it as a good way into some of the other SAMD based boards supported by the Arduino IDE in the future too.
But the thing I want to do right now isn’t supported in CircuitPython, so I’m using the Arduino IDE.
It’s great how the board can support either, and it all started out fine, but somehow I’ve managed to get into the position where the board keeps coming up as two different serial ports under Windows. It is COM35 when in bootloader mode (when you can see the TRINKETBOOT drive) but once I load in a sketch from the Arduino IDE and it starts running it it switches over to COM36. It was starting to get really irritating, especially when I wanted to use the serial monitor, as I was constantly telling the IDE which port to use!
There does seem to be a fix though. I don’t know if this is a universal fix and it might cause problems further down the line, but it worked for me for now. I also don’t know if this is a common thing for SAMD M0 boards – I can imagine it being a common issue for any board that re-uses the USB port as a serial port but under a different environment (like the Trinket does in the two modes).
In Device Manager you should be able to see the Trinket under “Ports” with the two COM port assignments as it changes.
But you can tell Windows what port assignment to use, so to make them the same do the following:
- Check you see which COM port is in use in bootloader mode and then load a sketch and check the COM port number when running a sketch. For me these were 35 and 36 respectively, but it will depend what other devices you’ve used (I used a lot of different microcontrollers!)
- In Device Manager right click on the sketch COM port under “ports” and select Properties.
- In Properties, if you aren’t already admin on your machine, you need to select “Change Settings” which has the admin icon.
- Under Port Settings, select Advanced.
- At the bottom you will see COM Port Number – you can select this and swap it from the sketch COM port to the same as the bootloader COM port. Windows will show it as “in use” and check that you are sure you know what you are doing. I just pretended I did and hit “ok”.
You must be sure to get the right COM port here, I don’t know what happens if you choose the wrong one! Presumably you’ll get weird things going on if you ever plug in both devices Windows things are that COM port at the same time.
Assuming you chose wisely, at this point whichever mode the Trinket is in – bootloader or running sketches, it should be recognised by Windows as the same COM port and you no longer need to change anything in the Arduino IDE, although I still have to “double click” reset to enter bootloader mode to upload sketches. I don’t know if this is typical – I guess so, but I can live with that.
Note that dropping the CircuitPython bootloader back onto the Trinket sets it back to a different COM port again, but that just seems to be what it does… I’ll update this post as I discover more and if I uncover and weird side effects…
Kevin
-
I made a small web ui for my TrueType font to #adafruit's GFX font tool: https://ttf2gfx.crafting-labs.fr/
-
I was browsing some of the newer ATtiny chips the other day and started to make a note of some of their properties and it made me realise I actually have quite a few different microcontrollers at my disposal and many more I could be having a look at.
But having committed to not attempting to get hold of every variant of every device to put a MIDI interface on it, I thought it would still be worth a post summarising some of the features to make selecting them in the future a little easier.
There are many comparison charts and tables online, but this is my own summary of the things that are important to me right now in terms of using them for musical purposes.
Note: I think the data is correct at the time of writing. Feel free to let me know of any mistakes. Also feel free to let me know what microcontrollers you use for music, and why, in the comments.
8-bit Microcontrollers
MCUFreqPWRGPIOADCPWMDACCommsRAMFlashATmega328P16MHz2.7-5.5V236/860UART, I2C, SPI2K32KATmega32U416MHz2.7-5.5V261280UART, I2C, SPI, USB2.5K32KATtiny858/20MHz2.7-5.5V6460USI5128KATtiny8812MHz2.7-5.5V28620I2C, SPI5128KATtiny21(2|4)
ATtiny41(2|4|6)20MHz1.8-5.5V6|12
6|12|186|10
6|10|1261UART, I2C, SPI128
2562K
4K32-bit Microcontrollers
MCUFreqPWRFPUGPIOADCPWMDACCommsRAMFlashSAMD21 (M0+)48MHz1.6-3.6VN30/381430?1SERCOM, I2S, USB4-32K32-256KSAMD51 (M4)120MHz1.6-3.6VY513237?1SERCOM, I2S, USB128-256256-1024KRP2040 (2xM0+)133MHz3.3VN304110UART, I2C, SPI, USB, PIO264KexternalESP32 (LX6)160MHz3.0-3.6VY3418162UART, I2C, SPI, I2S, Wi-Fi, BT0-2M0-4MESP32-S2 (LX7)240MHz2.8-3.6VN?432080UART, I2C, SPI, I2S, Wi-Fi0-2M0-2-4MESP32-S3 (2xLX7)240MHz3.0-3.6VY452080UART, I2C, SPI, I2S, Wi-Fi, BT0-2-8-16M0-4-8MESP32-A1S (2xLX6)240MHx3.0-3.6VY?14??2UART, I2C, SPI, I2S520K+4M0?Points of Note
- The ATmega and ATtiny devices are all 8-bit AVR architecture and might be either 3V3 or 5V operation depending on the device. Whereas the others are all 32-bit, 3V3 operation, and either ARM or Tensilica Xtensa architectures.
- The SAMD51, ESP32 and ESP32-S3 are all interesting as they include a floating point unit, which might be useful if I get into requiring mathematical synthesis.
- ATtiny2xx, ATtiny4xx, SAMD21, SAMD51, ESP32 all include a DAC which would be really useful for generating control voltages.
- ATmega32U4, SAMD21, SAMD51, RP2040 all support USB directly.
- The last one is an interesting device. The ESP32-A1S is a single module that includes an ESP32 and a CODEC module. More recent versions use the ES8388 and support two audio in/out channels. There is an Espressif Audio Development Framework for use with all ESP32-based devices.
Other MCUs of possible interest might include some of the newer RISC-V devices (e.g. ESP32-C3), the STM32 device range (the higher performing devices include floating point support, for example), the Teensy boards (which have a strong following for audio applications), and even running with the broadcom devices used on the various Raspberry Pis in “bare metal” mode.
A key tradeoff already would be choosing between a more powerful, probably 32-bit, 3V3 logic devices or a less capable 5V device.
Development Boards
I’m unlikely to be working with a microcontroller directly though, given my own level of knowledge, so I’m probably going to be looking at some kind of development board.
The following could all be possibilities if I’m happy running at 3V3.
Note, many of the form-factors, e.g. Adafruit’s QT Py or Feather, support most of the architectures – but not all are listed – just those I have or might consider. I’ve also added in some other boards that I know are often used (or shout about being used) for audio applications.
Prices are approximate at time of writing (Feb 2024).
BoardMCUArchSpeedRAM/FlashFPUGPIOADCPWMI2SDACCostRPi PicoRP20402xM0+133MHz264K/2MN27316PIO0£4XIAOSAMD21M0+48MHz32K/256KN14111111£6XIAORP20402xM0+133MHz264K/2MN11411PIO0£6XIAOESP32-S32xLX7240MHz8M/8MY1191110£8XIAOESP32-C3RISC-V160MHz4K/4M?114110£6QT PySAMD21M0+48MHz32K/256KN119911£9QT PyRP20402xM0+125MHz264K/8MN13413PIO0£10QT PyESP32-S32xLX7240MHz512K+2M/4MY13101310£15TrinketSAMD21M0+48MHz32K/256KN55211£9ItsyBitsySAMD21M0+48MHz32K/256KN23111311£12ItsyBitsySAMD51M4120MHz192K/512K+2MN2371812£15FeatherSAMD21M0+48MHz32K/256KN2062011£19FeatherSAMD51M4120MHz192K/512K+2MY2161612£23FeatherRP20402xM0+125MHz264K/8MN21416PIO0£12FeatherESP32-S32xLX7240MHz2M/4MY2162110£17BananaPicoWESP32-S32xLX7240MHz512K/2M+8MY2718810£4WROOM32ESP322xLX6<240MHz500K/448K+4MY34152512£3Teensy 3.6MK66FX1M4F180MHz256K/1MY64252212N/ATeensy 4.0IMXRT1062M7600MHz1M/2MY40143120£26Teensy 4.1IMXRT1062M7600MHz1M/8MY55183520£30Arduino MKR ZeroSAMD21M0+48MHz32K/256KN2271311£30Arduino Giga R1STM32H747XM7
M4480MHz
240MHz1M/2M?761413?2£70It is interesting to note which boards support a DAC and which support I2S, both very useful for audio applications and the number of ADCs is relevant too.
Boards specifically designed for audio processing, which I’ve no direct experience of, include:
- Pico ADK – A RP2040 based “audio development kit” with 8 ADCs and SPI DAC.
- Daisy Seed – an ARM Cortex-M7 with audio IO designed for DSP and audio applications (£35)
- Bela and Bela Mini – designed for use with Beaglebone for real-time, low-latency audio processing (~£130-£160).
And it is worth noting that the Teensy has many features well suited to audio processing, including a dedicated software audio toolkit (see below).
Software Audio Frameworks
There are a number of software frameworks for use with some of the above for audio processing:
- Phil Schatzmann’s Arduino Audio Tools.
- Espressif’s Audio Development Framework.
- The Arduino Sound Library.
- Marcel-Licence’s ML Synth Tools for ESP32.
- Teensy Audio Library.
- Arduino Giga R1 Advanced ADCDAC Applications.
- Adafruit’s CircuitPython synthio.
There is a bit of discussion about these here: Arduino Audio and MIDI Frameworks.
Closing Thoughts
I expect this page will evolve with new information, but it will be good to have a single post to refer back to.
Kevin
https://diyelectromusic.wordpress.com/2024/05/07/selecting-microcontrollers-for-music/
#adafruit #arduino #attiny #esp32 #raspberryPi #raspberryPiPico #samd21 #samd51 #teensy
-
Updated the awesome-list for the #Adafruit #MacroPad this morning (just in case you may have got one for Christmas!) Especially check out the MacroPad Hotkeys II project by DeckerEgo, it's my new favorite: https://github.com/prcutler/awesome-macropad
-
Learn how to control the Adafruit NeoPixel (WS2812) with a few lines of MicroPython
https://www.makerspace-online.com/micropython-ws2812-aka-neopixel/?utm_source=mms
#AdafruitNeoPixel #WS2812 #LED #MicroPython #programming #OpenHardware -
It’s like those Pac Man joystick TV games but we are brave enough to do keyboard DOOM!
DoooooOOOOM
https://learn.adafruit.com/doom-keeb?view=all
#adafruit #gamingkeyboard #customkeyboards #keebs #keyboardmod #kb2040 #circuitpython #doomgame #neokey #retrogaming #usbmod #techhack #keyboardhacker #keyboardenthusiast #doombutton #gaminghack #zdgame #hiddenusb #flashstorage #keebcommunity #doom
-
It’s like those Pac Man joystick TV games but we are brave enough to do keyboard DOOM!
DoooooOOOOM
https://learn.adafruit.com/doom-keeb?view=all
#adafruit #gamingkeyboard #customkeyboards #keebs #keyboardmod #kb2040 #circuitpython #doomgame #neokey #retrogaming #usbmod #techhack #keyboardhacker #keyboardenthusiast #doombutton #gaminghack #zdgame #hiddenusb #flashstorage #keebcommunity #doom
-
It’s like those Pac Man joystick TV games but we are brave enough to do keyboard DOOM!
DoooooOOOOM
https://learn.adafruit.com/doom-keeb?view=all
#adafruit #gamingkeyboard #customkeyboards #keebs #keyboardmod #kb2040 #circuitpython #doomgame #neokey #retrogaming #usbmod #techhack #keyboardhacker #keyboardenthusiast #doombutton #gaminghack #zdgame #hiddenusb #flashstorage #keebcommunity #doom
-
@adafruit has 786 certified projects! A nice proof that open source hardware is viable. I can't imagine how many projects, startups, companies or research have been accelerated thanks to these! I take my hat off to them 🙏
-
here we test it on an RP2040 QT Py https://www.adafruit.com/product/4900 with CircuitPython to play each wav file on the SD card through a speaker hooked up to a molex picoblade connector. All open-source hardware ... sounds great! lets order them today...
#adafruit #electronics #opensource #opensourcehardware #AudioBFF #I2SAmplifier #MicroSD #SoundTest #CircuitPython #RP2040 #raspberrypi
-
here we test it on an RP2040 QT Py https://www.adafruit.com/product/4900 with CircuitPython to play each wav file on the SD card through a speaker hooked up to a molex picoblade connector. All open-source hardware ... sounds great! lets order them today...
#adafruit #electronics #opensource #opensourcehardware #AudioBFF #I2SAmplifier #MicroSD #SoundTest #CircuitPython #RP2040 #raspberrypi
-
here we test it on an RP2040 QT Py https://www.adafruit.com/product/4900 with CircuitPython to play each wav file on the SD card through a speaker hooked up to a molex picoblade connector. All open-source hardware ... sounds great! lets order them today...
#adafruit #electronics #opensource #opensourcehardware #AudioBFF #I2SAmplifier #MicroSD #SoundTest #CircuitPython #RP2040 #raspberrypi
-
😂 Surprise, surprise! Adafruit's mad because Arduino's "Open Source" is as open as a sealed jar of pickles! 🥒 Meanwhile, The New Stack is too busy collecting emails like it's a Pokémon game. 🎮📧
https://thenewstack.io/adafruit-arduinos-rules-are-incompatible-with-open-source/ #Adafruit #Arduino #OpenSource #Pickles #TheNewStack #HackerNews #ngated -
@adafruit
I should've posted this on your TRS-80 day.My (family's) first computer was a TRS80-compatible Dick Smith System 80.
https://www.classic-computers.org.nz/system-80/hardware_s80.htmFor a printer, we had an actual mechanical teletype with an interface box driven by the audio output.
I upgraded the RAM from 16kiB to 48kiB by stacking more chips on top of the existing ones, with IIRC chip select pins bent up and connected to some extra logic.
-
Adafruit’s Cheekmate gets to the bottom (ahem) of chess cheating controversy - The clever folks at Adafruit tested their Cheekmate chess-cheating prototype by em... - https://arstechnica.com/?p=1887540 #chesscheatingscandal #conspiracytheories #gaming&culture #internetmemes #chess
-
Adafruit AVRProg Grows UPDI Interface Support - Making a small number of things with an embedded application is pretty straightfor... - https://hackaday.com/2021/11/08/adafruit-avrprog-grows-updi-interface-support/ #arduinohacks #embedded #arduino #updi
-
Fans of Adafruit may recall a couple of months ago that one of the key people at the company made a series of posts on social media (including Mastodon and BlueSky) that looked awfully like online harassment. Besides some unprofessional stuff like name-calling, there were more serious accusations such as transphobia and doxxing.
Now, it seems there's been a falling-out between Adafruit and SparkFun Electronics. SparkFun has taken things seriously enough that they've ceased their business relationship with Adafruit. Here's the Official Response from SparkFun, citing a direct violation of their Code of Conduct:
https://www.sparkfun.com/official-responseThis is bad news for Adafruit, since SparkFun is a major supplier of electronic components, tools, and devices. SparkFun also manufactures their in-house range of products, as well as having the scale to manufacture products for other companies such as Teensy. It's potentially fatal for Adafruit to get cut-off from SparkFun.
The response from Adafruit has been confusing. Rather than explain how or why they destroyed their business-relationship with SparkFun, they made a public statement announcing they'll soon cease selling Teensy devices: "Discontinuing the Teensy at Adafruit" (https://blog.adafruit.com/2026/01/12/discontinuing-the-teensy-at-adafruit/)
To make matters even more strange and confusing, Adafruit announced they're making a Teensy-knockoff^h^h^h^h^h^h^h^hcompatible board.
But, surely the most bizarre twist is this same individual from Adafruit has gone onto the Teensy forum to advertise their new products meant to compete with Teensy: https://forum.pjrc.com/index.php?threads/open-source-teensy-compatible-what-features-do-you-want.77584/
I think it's fair to say that Paul Stoffregen, who runs/designs/engineers Teensy, has shown remarkable restraint since being dragged into this drama and having it jump tracks and go careering outrageously onto the Teensy forum. -
My family's first computer was an Atari 800. I used the hell out of that thing as a kid, eventually even adding an aftermarket floppy disk drive that was dual-sided and double-density, storing an incredible 360kb per disk, vs the Atari 810's 90kb / disk.
The interesting thing about the serial I/O system is that it was auto-configuring - plug and play, in 1978! - and supported many different types of peripherals without having to manually load drivers or extra software. It acted a lot like the first version of USB - and Joe Decuir, the guy who designed it, also did significant work on USB decades later.
PCs wouldn't get an interface this nice until USB hit the platform in the 1990s.
-
I wonder how well it would do on the pile of 8" floppies I have in the basement eh?
