OpenNavo

SEGGER J-Link Command Line Tools

SEGGER Microcontroller GmbH · Software, manuals, and firmware updates for SEGGER J-Link and J-Trace debug probes, including command-line target inspection and flash programming tools.

CaskDeveloper ToolsApple silicon · Intel
Homepage
From homebrew/cask
30-day installs133#665 in App
1-year installs2.5KLast 365 days
Latest version9.842 days ago · Oct 7
Download size125MBarm64 / x86_64 · pkg
Release cadenceWeekly6 releases in 30 days

  1. 9.84

    LatestOct 7 · Wed

    OpenNavo editorialAdded to Homebrew Oct 7 19:51

    Adds device and flash-memory support, improves ST flash-programming speed and QSPI loader errors, fixes Flasher app-memory access, and fixes macOS SWO settings and a viewer crash.

    Version V9.84 (2026-10-07)

    Device Support

    DLL

    • Improved error code information for external QSPI flash loaders in case the flash loader detects an unknown flash ID.

    Firmware

    • Flasher ARM V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher ARM V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher ARM V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher ARM V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher Compact V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher Compact V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher Compact V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher Portable PLUS V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher Portable PLUS V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher Portable PLUS V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher PRO V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher PRO V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher PRO V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher PRO V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher Pro V8: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher PRO XL V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher PRO XL V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher PRO XL V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher PRO XL V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    • Flasher Pro XL V8: Reading or writing app memory prior to execution (e.g. via Flasher App Builder "w4" command) failed with error -5. Fixed.

    J-Flash

    • Improved error code information for external QSPI flash loaders in case the flash loader detects an unknown flash ID.

    J-Flash SPI

    • Giantec GT25Q32EB-H: Added flash programming support.

    • GigaDevice GD55B01GE: Added flash programming support.

    • Infineon CY15B116QN: Added FRAM memory support.

    • Infineon CY15V116QN: Added FRAM memory support.

    SWO Viewer

    • Manually configured SWO frequency settings could be overridden on macOS. Fixed.

    • The application could crash under special circumstances when closing the configuration dialog. Fixed.

    Official source: https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html

  2. 9.82

    Sep 30 · Wed

    OpenNavo editorialAdded to Homebrew Sep 30 14:13

    Expands device support and secure-installer erase, adds RISC-V and memory-cache command controls, and fixes debug authentication, flash programming, breakpoint detection, and probe firmware issues.

    Version V9.82 (2026-09-30)

    Highlights:

    Device Provisioner

    Device Support

    Other changes:

    Configurator

    • Added product images to configuration dialog.

    • Removed Flasher / J-Link banner from main window.

    Device Provisioner

    Device Support

    • BYT BY25FQ64EL: Added SPI flash programming support.

    • BYT BY25Q64ES: Added SPI flash programming support.

    • C*Core CCRC4086S: Added support for reset pin strategy.

    • C*Core CCRC4086S: Software breakpoints could fail. Fixed.

    • Nordic Semi nRF54L series: UICR programming failed when data was written to undefined addresses between the UICR registers. Fixed.

    • NXP i.MX RT1180: Flash programming failed when using loader "PortA_CLK@EMC_B1_41_nCS@EMC_B1_39_D0@EMC_B1_35_D1@EMC_B1_36_D2@EMC_B1_37_D3@EMC_B1_38". Introduced with v9.80. Fixed.

    • NXP MCXA173 & MCXA174: Flash programming consistently failed with a timeout during the preparation step. Introduced in v9.54. Fixed.

    • NXP MCXA343 & MCXA344: Flash programming for CMPA bank consistently failed with a timeout during the preparation step. Introduced in v9.54. Fixed.

    • Raspberry Pi: Added device names for RP2350A, RP2350B, RP2354A and RP2354B.

    • Renesas RA8: Flash programming in standalone mode could fail after changing the protection level / DLM state. Introduced in v9.40. Fixed.

    • ST SR6G3: Improved flash programming speed (https://kb.segger.com/ST_SR6G3#Flash_programming).

    • ST SR6G6: Improved flash programming speed (https://kb.segger.com/ST_SR6G6#Flash_programming).

    DLL

    Firmware

    • Flasher ARM V5-1: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher ARM V5: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher ARM V6: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher ARM V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher Compact V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher Compact V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher Compact V5: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher Compact V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher Compact V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher Compact V6: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher Compact V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher Compact V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher Compact V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher Portable PLUS V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher Portable PLUS V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher Portable PLUS V5: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher Portable PLUS V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher Portable PLUS V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher Portable PLUS V6: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher Portable PLUS V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher Portable PLUS V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher Portable PLUS V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO V5-1: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher PRO V5-1: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher PRO V5-1: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher PRO V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher PRO V5: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher PRO V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher PRO V6: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher PRO V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher PRO V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO XL V5-1: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher PRO XL V5-1: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher PRO XL V5-1: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO XL V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher PRO XL V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher PRO XL V5: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO XL V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher PRO XL V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher PRO XL V6: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO XL V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.

    • Flasher PRO XL V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.

    • Flasher PRO XL V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO XL V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • Flasher PRO XL V8: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link BASE/PLUS V12: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link BASE/PLUS V13: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link EDU Mini V1: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link EDU Mini V2: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link OB RA4M2-Full: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link PRO PoE V6: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link PRO PoE V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link PRO V5-1: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link PRO V5: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link PRO V6: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link PRO V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link Pro V8: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link Ultra V8: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link ULTRA+ V5-1: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link ULTRA+ V5: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link ULTRA+ V6: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link ULTRA+ V7: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link WiFi V2: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Link-OB-K22-CortexA: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Trace PRO V3 Cortex: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Trace PRO V3: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Trace PRO V4 Cortex: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    • J-Trace PRO V4: On ARMv8-A/R targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.

    J-Flash SPI

    • BYT BY25FQ64EL: Added SPI flash programming support.

    • BYT BY25Q64ES: Added SPI flash programming support.

    J-Link USB Web Server

    • Application always opened a terminal window on macOS. Fixed.

    Trace

    • Improved detection of wrongly sampled trace data due to e.g. signal integrity issues.

    Official source: https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html

  3. 9.80

    Sep 23 · Wed

    OpenNavo editorialAdded to Homebrew Sep 23 13:52

    Fixes J-Link Commander crashes on Linux and macOS, expands device and SPI flash support, and fixes flash erase, authorized flashing, and Windows path handling.

    Version V9.80 (2026-09-23)

    Commander

    • J-Link Commander crashed under certain circumstances on Linux/macOS. Fixed.

    Device Provisioner

    • Root-relative paths were not resolved correctly on Windows. Fixed.

    Device Support

    • Added additional Microchip part numbers for SAM9X family.

    • Added additional Microchip part numbers for SAMA5 family.

    • Added additional Microchip part numbers for SAMA7 family.

    • Added FlexSPI2 Port A flash programming support for pin config "CLK@EMC_B1_41_nCS@EMC_B1_39_D0@EMC_B1_35_D1@EMC_B1_36_D2@EMC_B1_37_D3@EMC_B1_38" (https://kb.segger.com/NXP_i.MX_RT1180).

    • BYT BY25D20FV: Added SPI flash programming support.

    • BYT BY25D40ES: Added SPI Flash programming support.

    • BYT BY25FQ128EL: Added SPI flash programming support.

    • BYT BY25FQ16EL: Added SPI flash programming support.

    • BYT BY25FQ16ES: Added SPI flash programming support.

    • BYT BY25FQ256ES: Added SPI flash programming support.

    • BYT BY25FQ32EL: Added SPI flash programming support.

    • BYT BY25FQ32ES: Added SPI flash programming support.

    • BYT BY25FQ64ES: Added SPI flash programming support.

    • BYT BY25Q16AW: Added SPI flash programming support.

    • BYT BY25Q16ES: Added SPI Flash programming support.

    • BYT BY25Q20AW: Added SPI flash programming support.

    • BYT BY25Q256FS: Added SPI Flash programming support.

    • BYT BY25Q32ES: Added SPI Flash programming support.

    • BYT BY25Q40GW: Added SPI flash programming support.

    • BYT BY25Q80AW: Added SPI flash programming support.

    • BYT BY25Q80BS: Added SPI flash programming support.

    • BYT BY25Q80ES: Added SPI Flash programming support.

    • CVA CHIP CVM011x: Added flash programming support for Info Region (https://kb.segger.com/CVA_CHIP_CVM011x).

    • CVA CHIP CVM011x: During flash programming watchdog was not fed correctly if windowed mode was active. Fixed.

    • Geehy G32M3101: Added debug and flash programming support (https://kb.segger.com/Geehy_G32M3101).

    • Giantec GT25Q16A: Added SPI flash programming support.

    • NXP i.MX RT1180: Renamed existing FlexSPI1/FlexSPI2 flashloaders (https://kb.segger.com/NXP_i.MX_RT1180).

    • Removed non-existant Microchip part number ATSAMA5D25C.

    • Renesas AT25QF0321C: Added SPI flash programming support.

    • Renesas AT25QF0641C: Added SPI flash programming support.

    • Renesas AT25SF0321C: Added SPI flash programming support.

    • Renesas AT25SF0641C: Added SPI flash programming support.

    • Renesas RA4E1, RA4M2, RA4M3: Flash erase operation on code flash memory could time out prematurely before the operation completed. Fixed.

    • Renesas RA6E1, RA6M4, RA4M5, RA6T2: Flash erase operation on code flash memory could time out prematurely before the operation completed. Fixed.

    • Renesas RX24T: Added debug and flash programming support for part numbers R5F524TB, R5F524TC and R5F524TE (https://kb.segger.com/Renesas_RX24T).

    • ST Stellar SR6 : Added new part numbers (SR6P6C6 and SR6G6C4).

    • TDK Micronas HVC4xxx: Flash programming on devices with small RAM failed. Introduced with V9.32. Fixed.

    • TDK Micronas HVC4xxx: Flash programming on NVRAM Page10 failed. Introduced with V9.32. Fixed.

    DLL

    • Root-relative paths were not resolved correctly on Windows. Fixed.

    Firmware

    • Flasher ARM V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher ARM V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher ARM V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher ARM V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Compact V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Compact V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Compact V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Portable PLUS V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Portable PLUS V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Portable PLUS V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher PRO V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher PRO V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher PRO V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher PRO V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Pro V8: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher PRO XL V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher PRO XL V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher PRO XL V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher PRO XL V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Pro XL V8: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.

    • Flasher Pro XL V8: Setting an adjustable target supply voltage of 1500mV could sometimes fail. Fixed.

    J-Flash SPI

    • BYT BY25D20FV: Added SPI flash programming support.

    • BYT BY25D40ES: Added SPI flash programming support.

    • BYT BY25FQ128EL: Added SPI flash programming support.

    • BYT BY25FQ16EL: Added SPI flash programming support.

    • BYT BY25FQ16ES: Added SPI flash programming support.

    • BYT BY25FQ256ES: Added SPI flash programming support.

    • BYT BY25FQ32EL: Added SPI flash programming support.

    • BYT BY25FQ32ES: Added SPI flash programming support.

    • BYT BY25FQ64ES: Added SPI flash programming support.

    • BYT BY25Q16AW: Added SPI flash programming support.

    • BYT BY25Q16ES: Added SPI flash programming support.

    • BYT BY25Q20AW: Added SPI flash programming support.

    • BYT BY25Q256FS: Added SPI flash programming support.

    • BYT BY25Q32ES: Added SPI flash programming support.

    • BYT BY25Q40GW: Added SPI flash programming support.

    • BYT BY25Q80AW: Added SPI flash programming support.

    • BYT BY25Q80BS: Added SPI flash programming support.

    • BYT BY25Q80ES: Added SPI flash programming support.

    • Giantec GT25Q16A: Added SPI flash programming support.

    • Renesas AT25QF0321C: Added SPI flash programming support.

    • Renesas AT25QF0641C: Added SPI flash programming support.

    • Renesas AT25SF0321C: Added SPI flash programming support.

    • Renesas AT25SF0641C: Added SPI flash programming support.

    RTT Logger

    • Root-relative paths were not resolved correctly on Windows. Fixed.

    Official source: https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html

An open-source interface for Homebrew. Installs run through the macOS app or the brew command.

© 2026 OpenNavo