# Patcher firmware

**URL:** <https://ksoloti.discourse.group/t/patcher-firmware/240>\
**Category:** Software\
**Created:** [February 28, 2025, 3:40pm UTC](https://ksoloti.discourse.group/t/patcher-firmware/240 "2025-02-28T15:40:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaos](https://yyz2.discourse-cdn.com/free1/user_avatar/ksoloti.discourse.group/kaos/32/260_2.png) [@kaos](https://ksoloti.discourse.group/u/kaos)\
**Post date:** [February 28, 2025, 3:40pm UTC](https://ksoloti.discourse.group/t/patcher-firmware/240/1 "2025-02-28T15:40:16Z")

</div>

Hi,

when switching between computers, is it normal I have to reflash the firmware? Is it because I compiled the firmware on linux\_arm64 and on linux\_amd64 for my other computer?

The problem is, every time I switch computers to program my big genes, it asks to reflash the software

on the arm I get:

```auto
Firmware version 1.0.0.4 | CRC 0xEB8B6CD0

Firmware CRC mismatch! Please flash the firmware first!
Hardware CRC EB8B6CD0 <-> Software CRC B412D8FF

```

and on the amd64 (not surprisingly):

```auto
Firmware version 1.0.0.4 | CRC 0xB412D8FF

Firmware CRC mismatch! Please flash the firmware first!
Hardware CRC B412D8FF <-> Software CRC EB8B6CD0

```

I remember programming my old axolotis from multiple computers without problems…  
what is going on?

should I just copy the firmware from one computer to the other?

---

<div class="post-metadata">

**Author:** ![Ksoloti](https://yyz2.discourse-cdn.com/free1/user_avatar/ksoloti.discourse.group/ksoloti/32/71_2.png) [@Ksoloti](https://ksoloti.discourse.group/u/Ksoloti)\
**Post date:** [March 1, 2025, 8:15am UTC](https://ksoloti.discourse.group/t/patcher-firmware/240/2 "2025-03-01T08:15:56Z")

</div>

It might be due to differences between the 1.0.12-8 release package and the 1.0.12-8 tag on github - releases on Github are a convoluted process and a “release” is frozen in time, and to add the most minor change you’d have to delete the current “release” and/or make a new “release”.

You could copy the firmware folder over from one package to another - possibly copy the “newer” version of the firmware folder (which is from the git cloned repo) to the Patcher from the “release zip” as there will definitely be some nice-to-have fixes there.

Or to make it easier, you could download the 1.0.12-8 tagged repo and extract the firmware folder from there, instead of pulling it from your arm system. Good practice to keep the original firmware folder as a backup!