# Chrysalis 0.11.8 firmware flashing is unreliable
**URL:** https://community.keyboard.io/t/chrysalis-0-11-8-firmware-flashing-is-unreliable/5744
**Category:** Uncategorized
**Created:** [October 11, 2022, 6:24am UTC](https://community.keyboard.io/t/chrysalis-0-11-8-firmware-flashing-is-unreliable/5744 "2022-10-11T06:24:19Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@hupfdule](https://community.keyboard.io/u/hupfdule)
#### Post date: [October 11, 2022, 6:24am UTC](https://community.keyboard.io/t/chrysalis-0-11-8-firmware-flashing-is-unreliable/5744/1 "2022-10-11T06:24:19Z")
Chrysalis 0.11.6 firmware flashing worked correctly for me. I had to press the `Prog` key when hitting “Continue” and had to release it as soon as the keys started flashing green.
Now with Chrysalis 0.11.8 I need several retries to be able to flash the firmware. Holding `Prog` while hitting “Continue” doesn’t have an immediate result. It takes a long time until the `Prog` keys lights up in red. Shortly after that Chrysalis disconnects from the keyboard with the error message “Error flashing the Firmware”. When logging in again it tells me that the firmware must be flashed. So I select it again and start the flashing process again. If enough time elapsed between these two steps the keys start flashing green immediately after hitting “Continue”. If not, the process will fail again and the keyboard is disconnected again. Sometimes I have to do that several times until the flashing succeeds.
I am flashing a custom firmware and always reset to factory defaults, if that matters.
The flashing process with Chrysalis 0.11.6 was way more reliable and straight forward.
---
### Author:  [@merlin](https://community.keyboard.io/u/merlin)
#### Post date: [October 11, 2022, 1:13pm UTC](https://community.keyboard.io/t/chrysalis-0-11-8-firmware-flashing-is-unreliable/5744/2 "2022-10-11T13:13:35Z")
It would help to know which device you’re having trouble with.
---
### Author:  [@Moilleadoir](https://community.keyboard.io/u/Moilleadoir)
#### Post date: [October 11, 2022, 1:57pm UTC](https://community.keyboard.io/t/chrysalis-0-11-8-firmware-flashing-is-unreliable/5744/3 "2022-10-11T13:57:31Z")
Haven’t tried the latest, but this seemed to happen more for me if the Arduino IDE was open, particularly the Monitor window.
---
### Author:  [@hupfdule](https://community.keyboard.io/u/hupfdule)
#### Post date: [October 11, 2022, 2:51pm UTC](https://community.keyboard.io/t/chrysalis-0-11-8-firmware-flashing-is-unreliable/5744/4 "2022-10-11T14:51:59Z")
> [@merlin](#):
>
> It would help to know which device you’re having trouble with.
Oh, you are right. I have a Model 100.
---
### Author:  [@hupfdule](https://community.keyboard.io/u/hupfdule)
#### Post date: [October 11, 2022, 2:53pm UTC](https://community.keyboard.io/t/chrysalis-0-11-8-firmware-flashing-is-unreliable/5744/5 "2022-10-11T14:53:20Z")
> [@Moilleadoir](#):
>
> Haven’t tried the latest, but this seemed to happen more for me if the Arduino IDE was open, particularly the Monitor window.
I do have the Arduino IDE open, but inside a virtual machine. It is not connected to the keyboard (as I am not able to get the seriel port into the VM). That’s the reason why I am using Chrysalis for the flashing of the firmware I generate with the Arduino IDE.
---
### Author:  [@algernon](https://community.keyboard.io/u/algernon)
#### Post date: [October 13, 2022, 10:16am UTC](https://community.keyboard.io/t/chrysalis-0-11-8-firmware-flashing-is-unreliable/5744/6 "2022-10-13T10:16:38Z")
I can reproduce the problem. Don’t have a fix yet, but I discovered a workaround: during the flashing process, don’t press and hold the `Prog` key at the start. Push it a few seconds _after_ Chrysalis enters the “Entering programmable mode” stage.
It looks like things will go sideways unless the first reboot to bootloader mode fails, so the workaround is to wait until the keyboard reboots once, and then press `Prog`.
I’ll try to get a fix out for this quick.