Liked the original Elite-C but think it’s a bit too tall for you? We heard you loud and clear, so we replaced the original USB-C port with a mid-mount version of it to produce a lower-profile board. It's even thinner than a Pro Micro!
Stock Notice: The 1.6mm version of the Elite-C is indefinitely out-of-stock now, due to rising chip prices and lack of availability. Only the 2.0mm version will be available (until stock runs out), and this version will be suitable for nearly all builds. Some more details below.
- Compatible with all Pro Micro-based PCBs
- USB-C port that can’t be ripped off
- ATmega32u4 controller
- DFU bootloader
- 6 additional ATmega32u4 pins and USB pins broken out
- On-board reset button (you can still use the reset button on the keyboard PCB if it has one)
- 1.6mm thick PCB for slimmer profile
- Comes with two 12-pin headers and one 5-pin header
- Total of 24 I/O pins to work with (6 more than the Pro Micro)
- New with V4: VBUS pin is now broken out and placed above the B0 pin
The B-Stock Elite-C is simply just 2.0mm thick instead of 1.6mm thick like the normal Elite-C.
B-Stock means that the end product does not completely conform to the original specifications in some way, but is otherwise fully functional. In the case of the Elite-C, the "B-Stock" boards were made to the incorrect thickness at the fabrication facility. They have been tested to function identically, and the USB-C port is sturdy and not in danger of bending or otherwise breaking due to the thickness increase. This is simply a superficial issue, and 99% of customers will not be affected. If you are going for an "ultra-slim" build, where this 0.4mm might effect you, please purchase the non-B-stock board(s), otherwise this is a cheaper way to get an Elite-C in your hands =).
Question: Can I use this on just the master half of a board and use the cheaper Pro Micro on the slave?
Answer: Yes! You can do this without any problems, just remember that the Pro Micro half is flashed using :avrdude, and the Elite-C half is flashed using :dfu.
Detection issues in QMK Toolbox on Windows: See info on installing the correct DFU driver using Zadig here: https://docs.qmk.fm/#/faq_build?id=unknown-device-for-dfu-bootloader