Model 100 firmware update to fix corruption issues

Help and Getting Started
22

So sorry about that. What OS and OS version are you on? Is this the latest released version of Chrysalis or the latest development snapshot?

23

no worries, @jesse. i have 0.12.0 of Chrysalis installed and this is my OS version:
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 36 (Thirty Six)
Release: 36
Codename: ThirtySix

24

I’ve just built out a Fedora 36 box and confirmed that…it’s completely broken. The serialport library we’re relying on…isn’t doing what it’s supposed to be doing for me.

From the command line, what does this command get you?

npx @serialport/list -f jsonline
25

thanks a lot for looking into this, @jesse :pray:

i get the following output:

{"path":"/dev/ttyACM0","vendorId":"8086","productId":"51ed"}
{"path":"/dev/ttyS4","vendorId":"8086","productId":"51e3"}
{"path":"/dev/ttyS0"}
{"path":"/dev/ttyS1"}
{"path":"/dev/ttyS10"}
{"path":"/dev/ttyS11"}
{"path":"/dev/ttyS12"}
{"path":"/dev/ttyS13"}
{"path":"/dev/ttyS14"}
{"path":"/dev/ttyS15"}
{"path":"/dev/ttyS16"}
{"path":"/dev/ttyS17"}
{"path":"/dev/ttyS18"}
{"path":"/dev/ttyS19"}
{"path":"/dev/ttyS2"}
{"path":"/dev/ttyS20"}
{"path":"/dev/ttyS21"}
{"path":"/dev/ttyS22"}
{"path":"/dev/ttyS23"}
{"path":"/dev/ttyS24"}
{"path":"/dev/ttyS25"}
{"path":"/dev/ttyS26"}
{"path":"/dev/ttyS27"}
{"path":"/dev/ttyS28"}
{"path":"/dev/ttyS29"}
{"path":"/dev/ttyS3"}
{"path":"/dev/ttyS30"}
{"path":"/dev/ttyS31"}
{"path":"/dev/ttyS5"}
{"path":"/dev/ttyS6"}
{"path":"/dev/ttyS7"}
{"path":"/dev/ttyS8"}
{"path":"/dev/ttyS9"}
26

I’ve just verified that this appears to be a Fedora 36 specific issue in node-serialport, the library we depend on for serial communications with the keyboard… With the same hardware, everything appears to work ok on 37.

I’m going to file a bug with upstream, but I don’t know what their timeline will be for getting it sorted out.

1 Like
27

brilliant, @jesse. this was the nudge i needed to upgrade to 37. everything works like a charm. thank you so much! :blush:

28

I’m happy it’s working for you :slight_smile:

1 Like
29

Thank you,
holding down the PROG button when plugging in the keyboard allowed me to update the firmware on my newly arrived model 100

30

It’s a year and a half later. I’ve not upgraded the Model100 firmware, being lazy, and now that I try to, it fails. No version of Chrysalis (from 0.11.5 onward to 0.13.2 or the snapshot for 0.13.3 available today) manages to update the firmware.

If I follow the instructions (disconnect USB, press down Prog, connect USB) Chrysalis fails when trying to update the firmware. 0.11.5 shows a window with only white, no text, and doesn’t do anything else in the 15 minutes I wait. 0.12.0 and 0.13.2 pretty much instantly fail.

The keyboard works fine and I have little need to make any configuration, but I’m reporting this in case it’s helpful.

31

I ordered my Model 100 at the end of 2022. Due to various reasons I only now got around to finally try it.

As per the instructions (The Keyboardio Model 100), I wanted to update the firmware first.
After installing Chrysalis, I got the link to this thread and followed the instructions. Some screenshots were slightly outdated, but I think I managed to follow.

In particular, I did “Upgrading the firmware” and “Reset EEPROM to Factory Defaults” in two separate steps as advised above.

There are a few things however that make me question whether everything went successfully.

  1. After upgrading the firmware, Chrysalis only showed a white screen (similar to @liw).
  2. After waiting 15 minutes, I restarted Chrysalis and did the EEPROM factory reset.
  3. In the guide it says the the EEPROM factory reset “should take about 10 seconds”.
    When I did the reset, it took about 1 second. Afterwards, it said something like “Keyboard disconnected” in the lower left corner of Chrysalis.

When I select “Firmware Update” in Chrysalis, it says that the “Current firmware version” is 0.92.6+116.

Is there any way to check whether everything is alright now?

32

After not doing an update in a while I had the same experience. The firmware is updated, but Chrysalis goes white and fails to restore the EEPROM or reconnect.

After looking at Github I realised the Appimage version I’d been using has been discontinued and it’s now a web app only. You need to open https://chrysalis.keyboard.io/ in a Chrome-based browser.

Using the Web App, everything works as expected, but in the process I’ve lost some dynamic macros and there are some peculiarities in the interface, e.g. the keyboard chooser at the bottom of the screen is a bit cut off along the bottom row of keys and the sidebar font size is tiny.