# Issues uploading firmware to Model 100

**URL:** <https://community.keyboard.io/t/issues-uploading-firmware-to-model-100/5550>\
**Category:** Programming\
**Created:** [September 24, 2022, 4:31am UTC](https://community.keyboard.io/t/issues-uploading-firmware-to-model-100/5550 "2022-09-24T04:31:06Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![ngetal](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/ngetal/32/2937_2.png) [@ngetal](https://community.keyboard.io/u/ngetal)\
**Post date:** [September 30, 2022, 9:01am UTC](https://community.keyboard.io/t/issues-uploading-firmware-to-model-100/5550/10 "2022-09-30T09:01:31Z")

</div>

Since `make flash` still doesn’t work, is there a way to upload a fw created by `make compile` through Chrysalis?

Edit: got it. I made `make compile` [always print the build path](https://github.com/imrekoszo/Kaleidoscope/commit/f5118b5345052dd8139cd0fe9c68d2b9ddf657a7) then used the `.bin` file from that folder with Chrysalis’ custom firmware upload.

What was surprising at first is that the space cadet customizations went through almost fine but the keymap changes seemingly didn’t. I dug a bit here and there and realized EEPROM was messing with me and the keymap in there took priority over the hardcoded one so I ended up [disabling EEPROM settings altogether](https://github.com/imrekoszo/Kaleidoscope/commit/7d2c39bd8380ca3595c361c008c102d25ce4dfe7).

Now it works just like my Model 01 🎉

---

_[View the full topic](https://community.keyboard.io/t/issues-uploading-firmware-to-model-100/5550)._
