v0.4.1

Released: 2026-04-01

Non-Nordic device detection — devices connected via J-Link are no longer misidentified as Nordic chips. Previously, an STM32 or EFR32 could be detected as “nRF52832,” causing device resets and connection failures. Now uses safe generic core names (Cortex-M33/M4/M7/M0+) for non-Nordic targets. (Fixes #3)
RTT on non-Nordic devices — explicitly sets RTT search ranges via J-Link, enabling RTT on any device with standard ARM SRAM layout. Tested on Silicon Labs EFR32MG24.
NO_RTT error handling — when firmware lacks RTT, LogScope now fails immediately (no pointless retries), shows a clear error card explaining the issue, and does not display a persistent toast notification
Panel visibility on connect — the log viewer panel now opens as soon as you click Connect, so connection status and error cards are always visible
CSP connect-src — resolved Content Security Policy warning in developer console

Log messages now use monospace font (matches your VS Code editor font) for better alignment of structured output (thanks @kartben)
Improved “No RTT control block found” error message with actionable guidance about RTT search ranges
User’s logscope.jlink.device setting is now respected when set to a non-default value