# QMK port for Atreus 44 keys

**URL:** <https://community.keyboard.io/t/qmk-port-for-atreus-44-keys/4244>\
**Category:** Programming\
**Tags:** question\
**Created:** [October 14, 2020, 7:34am UTC](https://community.keyboard.io/t/qmk-port-for-atreus-44-keys/4244 "2020-10-14T07:34:24Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [October 16, 2020, 4:30pm UTC](https://community.keyboard.io/t/qmk-port-for-atreus-44-keys/4244/5 "2020-10-16T16:30:13Z")

</div>

Chrysalis detects the Atreus by its USB Vendor and Product ID. If those remain intact when flashing a QMK firmware onto it (and as far as I remember, they do), Chrysalis will be able to detect the keyboard. However, it will _not_ be able to talk to it, and will guide you to the Firmware Update screen.

It is technically possible to teach QMK to talk the same protocol as Kaleidoscope, and work with Chrysalis just as well as Kaleidoscope does, but there will be certain incompatibilities (ie, keycodes are different between QMK and Kaleidoscope, for pretty much all keys outside of the standard USB keyboard set) that make this impractical at this time.

---

_[View the full topic](https://community.keyboard.io/t/qmk-port-for-atreus-44-keys/4244)._