Skip to content

Release 26.10.1

JP150PCB 1.3PCB 1.4Jan PřibyslavskýThis page does not apply to the product or PCB revision chosen in the header.

Released 2026-10-18. Changes since release 26.8.0; the intermediate versions 26.9.0 and 26.10.0 were not published. The first release with the improved bootloader and firmware updates from MuraLink, PCB 1.4 support, Bluetooth TWS with a remembered partner, safer settings, a faster start-up and MURA LABS' own USB identity.

Before you update

Modules with PCB revision 1.4 are delivered with firmware 26.10.1. A module with PCB revision 1.3 that runs 26.8.0 cannot install this release over USB by itself: contact support, the first update is arranged individually. Never use the old FirmwareUpdater or DIP switch 3 on a module that runs 26.10.1 or later.

New features

The module now runs an improved bootloader that installs the update bundles MuraLink provides. The bootloader checks each package before it changes anything, installs the firmware and verifies it at every start-up. An update that is interrupted, by a pulled cable or a power loss, leaves the module waiting in update mode: repeat the update and nothing is lost.

  • Updating with MuraLink. Open the update bundle (JPx_Update_26.10.1.zip) on MuraLink's firmware update page. MuraLink checks the bundle against the module, restarts the module into update mode, installs the package and reconnects when the module has restarted. The whole update takes about a minute. No driver, no DIP switch and no separate updater are needed. See Update with MuraLink.
  • Indication on the module. In update mode the status LED blinks amber; during the transfer the level meter fills blue; steady green means installed and restarting; blinking red means the update failed and can be repeated. See LED indication.
  • Recovery without a PC command. Holding the encoder button while switching the module on enters update mode. A module without valid firmware, or one whose firmware failed to start three times in a row, waits in update mode by itself. A module sent into update mode by command returns to its firmware after 5 minutes if no update follows.
  • Rollback protection. A package older than the module's security floor is refused. Production modules are sealed (read-out protection level 2): their debug port and the ST ROM bootloader are closed, so the update bundle is the only way to change the firmware.

PCB revision 1.4 supported, one firmware for both revisions

26.10.1 runs on PCB revision 1.3 and 1.4 and recognises the board from its factory record. What revision 1.4 adds, as far as the firmware is concerned:

  • 12 V trigger input. A 3.3 V to 12 V signal on the new trigger connector, with the modes OFF, FOLLOW and ONOFF, a target level and a priority over the automatic power decisions. See 12 V trigger.
  • Accurate supply monitoring. Voltage and current come from a dedicated power monitor, and a power reading (SYS:MEAS:POW?) joins them. On PCB 1.3 the readings stay as before.
  • USB-C power sensing (SYS:POWER:USBC?). The firmware reports whether a USB-C power source is present.
  • DSP boot memory written from the PC. The DSP program memory of PCB 1.4 is written over the module's USB connection, by MuraLink or as part of a firmware update, so a USBi programmer is no longer required to install the default DSP program.
  • No configuration DIP switch. Its three functions moved: the DSP self-boot setting is a stored firmware setting (DSP:SELFBOOT), the master clock is selected by the firmware, and the MCU boot pin is a factory-only solder jumper. The hardware differences, connector pinouts included, are on Connectors and pinouts.

Board identity from the factory record

Every provisioned module carries its product, PCB revision, serial number and production date in a write-once record. *IDN? now reports that serial number (for example JP150-0001-0005), and MuraLink shows the board type next to it. A module without a supported record, for example a bare development board, starts in a safe state: outputs muted, status LED red with a dim white step every second, and only the identification and update commands available, so that it can still be updated.

Bluetooth TWS remembers its partner

A TWS pair now survives power cycles. The two modules reconnect automatically when they are switched on, in any order, and the roles are called Primary (the module the phone connects to) and Secondary instead of master and slave. The stored role became the Fallback Role: it is used only when no partner is remembered. MuraLink's Bluetooth section gained a TWS page with the pairing status, the remembered devices and the actions Start New Pairing, Disconnect, Reconnect and Forget Peer. The complete procedure is in TWS: pairing two units. The status LED patterns are unchanged: green accent for the Primary, purple-red for the Secondary.

Settings: safer autosave and a settings reset

Settings are saved automatically as before, and a change made right before a restart or a firmware update is now written first instead of being lost. A new command, SYS:NVM:DEFAULTS (MuraLink: Reset settings), returns the user settings to their defaults and restarts the module: the volumes, the input enable mask, the automatic power-down, the DSP self-boot setting and the trigger settings. The selected input, the TWS Fallback Role, the Bluetooth and Wi-Fi pairings and the DSP program are kept.

Faster, cleaner start-up

The module no longer waits up to six seconds for the DSP before anything else runs: the LEDs, the encoder and the control interface respond immediately after power-on, and the level meter no longer shows random colours meanwhile. Audio starts as soon as the DSP has loaded its program, about 50 ms after power-on on PCB 1.4 and 200 to 250 ms on PCB 1.3. Waking from sleep or standby restarts the DSP the same way, so audio returns within about a second.

Task watchdog

A watchdog now supervises every firmware task. A module that stops responding restarts itself instead of staying silent, and the cause is visible afterwards (SYS:RESET:CAUSE? answers IWDG).

New USB identity

The module identifies itself with MURA LABS' own USB IDs: 16D0:15B8 for the application (USB Audio and the virtual COM port) and 16D0:15B7 for update mode; 26.8.0 used 0483:5741. Windows installs no driver for either. After the change the PC sees a new device, and the COM port number can change.

Diagnostics for support

New read-only queries report the cause of the last reset, how the bootloader started the firmware, the installed package (release, special build or development, with its security counter), the protection state of the module, the DSP boot result and core state, and the health of the operating system. See Changes by release.

Fixed issues

  • KI-07 A setting changed right before a restart or an update could be lost
  • KI-06 Wrong input after waking from sleep or standby
  • KI-03 Supply current reading is indicative only
  • KI-02 Seconds of random level-meter colours at power-up
  • KI-01 TWS pairing sometimes unstable confirmation pending
  • Wrong input after waking from sleep or standby (PCB 1.4). The DSP of PCB 1.4 reloads its program on every wake, and the module re-sent the selected input before the program was ready, so the DSP played its default source, the test tone, while the status LED showed the right input. The input is now sent once the DSP program is running.
  • Seconds of random level-meter colours at power-up. Before the firmware responded to anything, the level meter showed whatever its LEDs latched at power-on, for up to six seconds, because the start-up waited for the DSP. The wait is gone. This also applied to PCB 1.3.
  • A setting changed right before a restart or an update could be lost. Settings are written a few seconds after a change. A restart, the entry into update mode or a reset command that came within that time lost the change. Pending changes are now written first.
  • Supply current reading was indicative only. Fixed on PCB 1.4 by the new power monitor. The PCB 1.3 reading is unchanged and stays indicative.
  • TWS pairing was sometimes unstable. The Bluetooth firmware no longer clears the pairing at every start and re-pairs from scratch, which is what made a pair fail to form or misbehave. The modules keep their pairing and reconnect to it.

Audio processing (DSP)

  • Default DSP program delivered with the firmware. The basic pass-through design of 26.8.0 is unchanged and is now part of the firmware update bundle for PCB 1.4, exported for the module's SPI boot memory with a boot read clock of 5 MHz. During a firmware update MuraLink asks whether to write it and never writes it unasked, so an own DSP design stays in place unless you choose otherwise. The same program is written at the factory.
  • Writing your own design on PCB 1.4. A SigmaStudio project is downloaded to the running DSP through the USBi as before. To write it into the boot memory of PCB 1.4, either let MuraLink write the SigmaStudio self-boot export, or write it from SigmaStudio through the DSP with the new memory settings. See Writing the boot memory.
  • Dedicated DSP bus on PCB 1.4. On PCB 1.4 the DSP has its own control bus, separate from the power stages and the settings memory. The programmer detection of 26.8.0 applies to that bus.

Updating to 26.10.1

  • PCB revision 1.4. Modules are delivered with firmware 26.10.1 and the default DSP program. Later releases are installed with MuraLink from their update bundle.
  • PCB revision 1.3. A PCB 1.3 module on 26.8.0 cannot install 26.10.1 or any later release over USB by itself. The first update is arranged with support; afterwards the module updates with MuraLink like a PCB 1.4 module.
  • MuraLink. Use MuraLink 26.10.1, delivered with this release as MuraLink_26.10.1.zip. The executable now brings its .NET runtime along, so nothing has to be installed first (Install). Older versions connect, but they do not know the update bundle, the DSP boot memory or the new TWS controls.

Known issues

The living list is on Known issues. Open at the time of this release: the control bus guard after a SigmaStudio session (PCB 1.4), the module not knowing which DSP program it runs, the front LEDs on some PCB 1.4 modules, the lone TWS unit not reconnecting the phone, the external master clock, and the carried-over USB and power-down behaviours.

Control interface

52 commands added, 4 removed (DSP:AUTOLOAD, DSP:AUTOLOAD?, BT:BOOTROLE, BT:BOOTROLE?), 10 with changed behaviour. The list is on Changes by release; what a host must handle is on Integration notes.

Stored settings

The settings-memory layout changed from version 3 to version 6. On the first start of 26.10.1 the stored settings are rebuilt once (SYS:NVM:EEPROM:STATE? answers NODATA on that start, OK from the next one): the input enable mask returns to all inputs enabled, the automatic power-down to its defaults (off, 1800 s, PWRSTAGE_OFF, threshold 5), the DSP self boot to on and the 12 V trigger to OFF / SLEEP / priority 1. Master volume, channel volumes, the selected input and the TWS fallback role are kept.