Chiptunes In An Altoids Tin

For [Dejan]’s entry to the Musical Instrument Challenge in this year’s Hackaday Prize, he’s tapping into some of the great work that has been done over the years to bring bleeps and bloops to the masses. He’s building a drum machine, a bass synth, and an arpeggiator that fits in your pocket, in a handy form factor that fits in an Altoids tin. It’s the FATCAT Altoids Tin Mod Tracker.

This is a simple build meant to fit in an Altoids tin, so you’re not getting a whole lot of hardware here. There’s a battery, there’s a boost circuit, and there’s a single chip, an ATtiny84. This tiny little microcontroller is the heart of the box, able to provide a drum track with a kick, snare, and a closed and open high hat. There’s a bass with a simple square wave and portamento, and an arp track that can be used as a lead or arpeggiated chords. All of this is programmed in C and uploaded straight to the chip.

The ATtiny series of microcontrollers are fairly popular for various means and methods of creating square wave bleeps and bloops. We’ve seen them become a MIDI synth that fits inside a MIDI jack, and we’ve seen how much chiptune goodness you can fit in thirty two bytes of RAM. Cornell even had a spat of rickroll vandalism with a coin cell throwie built on an ATtiny85. Anything that puts more ATtiny chiptunes into the hands of more people is great in our books, and this Altoids tin synth is just the thing.

You can check out a demo of the FATCAT below.

8 thoughts on “Chiptunes In An Altoids Tin

  1. This project has Software Flow Charts, full State Machine diagrams and an extensive construction manual. The schematic is actually a full schematic rather than a glorified netlist.

    This is how older and educated professionals document a project and is a good example of quality documentation.

    It’s a pity that the schematic isn’t available as and image and PDF because it is very good example of a “readable” schematic instead of the all to common glorified netlists I see all the time now.

    Well done.

    1. As an amateur, I am suddenly supremely self-conscious of my schematic layout skills. I do try, keeping wires as short as possible and connecting logically distinct sections via named labels instead of wires, but I haven’t spent much time with “real” schematics.

      My KiCad install isn’t liking the schematics linked in the documentation – I get a bunch of question marks.

      I really do like that flowchart, though!

      1. I agree. While it is nice that there is a diagram at all over not having one, since it follows some random convention the author decided upon and not how everyone else does them it is rather cumbersome to try and follow. In my opinion this is not the mark of an “older and educated professional”. I’d give an ‘A’ for effort though, but definitely not the gold standard of documentation that ROB is ascribing (disclaimer: not that I am great at documentation either lol).

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.