# Unofficial Firmware

**URL:** <https://squarp.community/t/unofficial-firmware/16520>\
**Category:** Pyramid\
**Created:** [October 12, 2026, 10:29am UTC](https://squarp.community/t/unofficial-firmware/16520 "2026-10-12T10:29:32Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![neddac](https://squarp.community/letter_avatar_proxy/v4/letter/n/c2a13f/32.png) [@neddac](https://squarp.community/u/neddac)\
**Post date:** [October 12, 2026, 10:29am UTC](https://squarp.community/t/unofficial-firmware/16520/1 "2026-10-12T10:29:32Z")

</div>

With all this recent chat about vibecoded firmware for various bits of kit, do you think someone might be able to fix the bugs (mentioned here) with Pyramid’s OS?

---

<div class="post-metadata">

**Author:** ![pyro\_squarp](https://squarp.community/letter_avatar_proxy/v4/letter/p/34f0e0/32.png) [@pyro\_squarp](https://squarp.community/u/pyro_squarp)\
**Post date:** [October 27, 2026, 4:08pm UTC](https://squarp.community/t/unofficial-firmware/16520/2 "2026-10-27T16:08:27Z")

</div>

It would be great if Squarp released the firmware opened.

---

<div class="post-metadata">

**Author:** ![kirill](https://squarp.community/letter_avatar_proxy/v4/letter/k/a9a28c/32.png) [@kirill](https://squarp.community/u/kirill)\
**Post date:** [November 3, 2026, 8:39pm UTC](https://squarp.community/t/unofficial-firmware/16520/3 "2026-11-03T20:39:44Z")

</div>

Squarp, open source pyra os for gods sake!

---

<div class="post-metadata">

**Author:** ![Patrick](https://squarp.community/letter_avatar_proxy/v4/letter/p/b2d939/32.png) [@Patrick](https://squarp.community/u/Patrick)\
**Post date:** [November 8, 2026, 9:21am UTC](https://squarp.community/t/unofficial-firmware/16520/4 "2026-11-08T09:21:43Z")

</div>

Yes please that would be really great.

Just found a bug at a very basic operation. There are still issues just with the latest firmware as it is. Being such a expensive gear at the time and now no support. It would be really great to see squarp doing something.

---

<div class="post-metadata">

**Author:** ![hoofjaw](https://squarp.community/letter_avatar_proxy/v4/letter/h/a9a28c/32.png) [@hoofjaw](https://squarp.community/u/hoofjaw)\
**Post date:** [November 8, 2026, 10:59am UTC](https://squarp.community/t/unofficial-firmware/16520/5 "2026-11-08T10:59:02Z")

</div>

Can you give us some details about that bug you have discovered?

---

<div class="post-metadata">

**Author:** ![Patrick](https://squarp.community/letter_avatar_proxy/v4/letter/p/b2d939/32.png) [@Patrick](https://squarp.community/u/Patrick)\
**Post date:** [November 8, 2026, 11:51am UTC](https://squarp.community/t/unofficial-firmware/16520/6 "2026-11-08T11:51:23Z")

</div>

I created another post for the bug. But basically my unit constantly crashes when trying to move very long notes at once around (a 4 note chord). Step mode, display, rec on, hold step down + arrow left or right. Instant freeze.

Track settings, zoom 1, bars 32, note lengths 16. What results in each note being 16\*4 steps long. But still the unit should really handle that extremely easy and well

---

<div class="post-metadata">

**Author:** ![hoofjaw](https://squarp.community/letter_avatar_proxy/v4/letter/h/a9a28c/32.png) [@hoofjaw](https://squarp.community/u/hoofjaw)\
**Post date:** [November 8, 2026, 5:56pm UTC](https://squarp.community/t/unofficial-firmware/16520/7 "2026-11-08T17:56:23Z")

</div>

Thank you. Here’s a link to that post.

> [@Crash, moving 4 notes in step mode](https://squarp.community/t/crash-moving-4-notes-in-step-mode/16613):
>
> Hi everyone, I’ve found a reproducible crash on my Pyramid running PyraOS 4.03. It happens when shifting a chord in STEP mode, and I’ve reproduced it in a completely new project. Steps to reproduce: Start a new project. Select track 4 and set its length to 32 bars, with zoom set to 1. Enter four simultaneous notes at step 2, each with note length set to 16—four bars in this setup. The notes extend beyond the current display page. Enable REC to edit multiple notes together. Hold step 2 and pr…

---

<div class="post-metadata">

**Author:** ![matthewmiller](https://squarp.community/letter_avatar_proxy/v4/letter/m/ac8455/32.png) [@matthewmiller](https://squarp.community/u/matthewmiller)\
**Post date:** [November 18, 2026, 9:46am UTC](https://squarp.community/t/unofficial-firmware/16520/8 "2026-11-18T09:46:57Z")

</div>

That crash sounds like a step-edit edge case rather than something open sourcing alone would immediately solve. If you can reproduce it, try the same move with zoom \>1 or shorter note lengths to isolate whether it is tied to the long note lengths, and send Squarp the exact project. Unofficial firmware would only help if Squarp published buildable sources and a safe flashing path; otherwise a workaround and a precise report are the practical route.
