Skip to content

Troubleshooting

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

This page lists the symptoms we are asked about most, each with the check to make and the page that resolves it. The commands named here can be sent from MuraLink's console or any terminal (Protocol); MuraLink shows the same values on its pages.

No sound

Symptom Check Page
The level meter follows the music, nothing from the speakers Volume 0 or a hardware mute; on PCB 1.4 a red FAULT LED. AMP:VOL?, AMP0:HWMUTE?, AMP0:FAULT? Volume and encoder
The level meter stays dark while the source plays Another input is selected, or the source is disabled. SYS:INPUT?, SYS:INPUT:ENABLE:LIST? Inputs and the enable mask
The DSP LED does not flash No DSP program runs: the boot memory is empty or holds an image for the other board, or the self boot is off. DSP:BOOT?, DSP:CORE:STATUS?, DSP:SELFBOOT? Writing the boot memory
The power LED blips only every two seconds The module is in a power-down level: the automatic power-down, or the 12 V trigger on PCB 1.4. A turn or press of the encoder wakes it; SYS:POWER:MODE?, SYS:POWER:AUTO:STATE?, SYS:TRIG? Power levels, Auto power-down, 12 V trigger
The status LED is red with a dim white step every second Safe state: the firmware does not support the board's factory record. SYS:BOARD:TYPE? Start-up and the safe state
Sound returns, then stops again after a while The automatic power-down's silence threshold, or Wi-Fi in STANDBY Auto power-down
A short burst of noise when USB audio resumes Known behaviour of the USB input after a long silence Known issues
Symptom Check Page
No COM port appears A charge-only USB cable; the module is in update mode (amber LED patterns), where it is a DFU device, not a COM port Install MuraLink, Recovery
MuraLink connects, but values read n/a The firmware is older than MuraLink and does not know the command Firmware compatibility
MuraLink shows a banner about the board and most pages are greyed Safe state of an unsupported board; the module can still be updated Start-up and the safe state
A command draws no answer while ping answers The firmware does not know the command, or the parameter is invalid: both are silent by design Command reference
Every command answers ERR:BOARD:UNSUPPORTED Safe state Start-up and the safe state
The Wi-Fi pages read n/a or time out The module is in STANDBY, where the Wi-Fi module is unpowered Power levels

Updates

Symptom Check Page
MuraLink refuses the bundle The message names the cause: board not listed, development package, below the security floor, bootloader missing Update with MuraLink
The update was interrupted The module waits in update mode and is listed under Units in update mode; repeat the update Recovery
The module shows amber LED patterns at power-up Update mode: three failed starts, or the encoder button held at power-up LED indication, Recovery
A PCB 1.3 module on 26.8.0 cannot be updated Its firmware predates the update bundles; the first update is arranged with support Contact
Settings were different after the update from 26.8.0 The stored settings are rebuilt once on the first start of 26.10.1; volumes, input and TWS role are kept Release 26.10.1

DSP and SigmaStudio

Symptom Check Page
The USB block in SigmaStudio does not turn green The USBi cable and driver Quick start
After a SigmaStudio session the module ignores input and power changes (PCB 1.4) The bus guard stayed active; reset or power-cycle the module Known issues
The program does not boot after a write to the boot memory The memory settings of the write, on PCB 1.4 the chip-erase time; an export made for the other board; the self boot setting Writing the boot memory
The DSP plays the test tone instead of the selected input The input mux entry of the starter project is missing from the design, or the program started after the firmware wrote the input IPAT and parameters

Bluetooth and TWS

Symptom Check Page
The phone does not find the module The Bluetooth input is selected (blue status LED) Connect a phone
A paired unit switched on alone does not reconnect the phone Connect from the phone; the partner joins when switched on Known issues
TWS status reads Unsupported The Bluetooth module's firmware has no TWS, or the module does not respond TWS status and troubleshooting
The partner is remembered but does not answer Start outcome PeerUnreachable: wait for the partner or pair again TWS: everyday use

LEDs

Symptom Check Page
White or random colours on the front LEDs of a PCB 1.4 module A known issue of part of the first batch; audio and control are not affected Known issues
Random colours on the level meter for a few seconds at power-up Fixed in 26.10.1; update Known issues

If the symptom is not here, contact support with the diagnostics listed there.