Troubleshooting

Troubleshooting

The analyzer does not appear in the device list

The list deliberately shows only boards that run the analyzer firmware (USB VID 0x1209, PID 0x3020) — other serial ports are left out.

• Press Refresh after plugging the board in.
• Linux: are you in the dialout group? sudo usermod -aG dialout "$USER", then log in again.
• Is the firmware installed at all? A fresh Pico shows up under Device → Install or update firmware… as a board in bootloader mode or as a board running other firmware.
• A board with the firmware but without a working trigger link fails Device → Board self-test… with TRIGGER_LINK: FAIL.

The trigger never fires

• A pattern trigger compares levels, not edges: it fires as soon as the channels match. If the condition is already true when the capture starts, it triggers immediately.
• Check the channel numbers: the pattern starts at First channel and runs upwards, and all its channels have to be consecutive trigger inputs of one board.
• For an external trigger, remember the 3.3 V limit of the input.
• In a multi device set only the board of the trigger channel evaluates the trigger, and it has to capture at least one channel itself.

Values on the bus look wrong or unstable

• The C64 bus decoder marks cycles whose lines change right at the read point in the Warnings row (unstable: A5 A9). Capture at a higher rate, or take the clock from the same board as the bus.
• Check the decoder option Read the bus: the 6510 takes the data at the falling Φ2 edge, and this application reads the last sample before that edge.
• Reads of the 6510 processor port ($0000/$0001) do not show the written value on the bus — those registers live inside the CPU.

Boards of a set start at slightly different times

That is expected; see alignment. A reference line makes it exact.

A multi device set is refused

All boards need the same firmware version. Flash them all from Device → Install or update firmware… — the image list shows the version each image contains.

A decoder is missing

Help → Decoder search paths lists the directories that were searched and how many decoders were loaded. Own decoders belong in <settings directory>/decoders/<id>/.

Settings, profiles or the window layout are gone

Up to version 7.0 the project was called LogicAnalyzer and used a settings directory of that name. Version 7.1 takes those settings over on the first start. If something is missing, the old directory is still there (~/.config/LogicAnalyzer, ~/Library/Application Support/LogicAnalyzer or %APPDATA%\LogicAnalyzer) and can be copied over by hand.

Reporting a problem

Device → Device information… → Copy to clipboard collects board, firmware, chip and SDK version for the issue. A capture file (.lac) that shows the problem helps a lot. pipilogicanalyzer --debug-driver logs the device communication to driver_debug.log in the settings directory.

Security problems do not belong in an issue — see SECURITY.md.