v0.5.8
Released: 2026-04-27
Diagnostics and documentation release. Triggered by #11 — a user whose probe was visible in nRF Connect but not in LogScope, with no diagnostic info to explain why.
- Friendly “SEGGER J-Link Software not found” error — when
libjlinkarm.dylib(macOS) orJLink_x64.dll(Windows) is missing from the standard install path, LogScope now shows a clear error card with a “Download SEGGER J-Link” button instead of an empty “No J-Link devices found” message - Helper stderr forwarded to the LogScope output channel — discovery and connection errors from the Python RTT helper now appear in
View → Output → LogScope, so failures are self-diagnosing instead of silent - Diagnostic detail in the device picker empty state — when discovery returns no probes, the QuickPick now shows the underlying reason (e.g., “SEGGER J-Link Software not found at /Applications/SEGGER/“)
Changed
Section titled “Changed”- README and docs prerequisites — SEGGER J-Link Software is now listed alongside nrfutil as a required dependency for J-Link RTT, with install paths and a download link. Troubleshooting page updated to call out the SEGGER vs. nRF-Connect-bundled-libs discrepancy.