Skip to content

Instantly share code, notes, and snippets.

Last active January 28, 2023 04:10
Show Gist options
  • Save nicinabox/3582fc89470a3f4efc9ed194f12fabfb to your computer and use it in GitHub Desktop.
Save nicinabox/3582fc89470a3f4efc9ed194f12fabfb to your computer and use it in GitHub Desktop.
This guide covers building a Let's Split v2.

This guide has moved

To improve collaboration this guide is now available on GitHub.

Continue reading

Copy link

necropsyuk commented Jul 7, 2017

Pretty sure it need to be soldered as you see it, on the same side of the Jack. I made the same mistake, I used the desolder pump to remove it, took a couple of tries to get it all, I really had to create a seal to get all the solder out. It was tricky and the jack needed a little wiggling, but I manged it. Maybe give it another go?

Copy link

This is a heads-up to any future readers

While this guide does work to explain the build process for the Let's Split keyboard, I recommend viewing the updated guide linked at the top of the page. The difference that made me notice that this guide is out-of-date is the wiring for the RGB underglow. In this section, there is no reason to wire both sides of the LED strip to the VCC and GND-- using either the unused jumper pads (or the jumpers themselves) will work. Additionally, though there may be a reason behind this, the guide here defines the number of LEDs as "10" but only shows 8 being wired. There may be other differences but those two stood out.

@tybenz - I had a similar issue on Linux so this may not work for you, but my solution was to run the avrdude command separately with sudo. I think the issue is that the make command wasn't capitalizing the portion after /dev/tty (in my case, "ACM1"). I copied the .hex file to my keymap folder, reset my pro-micro manually, then quickly ran the "extended" avrdude command: sudo avrdude -p atmega32u4 -P /dev/ttyACM1 -c avr109 -U flash:w:lets_split_rev2_custom.hex

Copy link

Sorry everyone! I didn't realize people were still coming here after the new guide was setup. Here's the updated guide!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment