The Embedded Experts
Release notes for the J-Link Software and Documentation Package
Version V9.44 (2026-05-20)
Highlights:
Device Support
- ORITEK CJ300V1xx device series: Added debug & flash programming support (https://kb.segger.com/ORITEK_CJ300V1xx).
Other changes:
Device Support
- Infineon PSOC EDGE E8: Flash programming on PRAM_NS and PRAM_S flashbanks did not work properply. Introduced with V9.14. Fixed.
- Nations N32G003: J-Link didn't restore default values for option bytes properly after active read protection L1 level was detected and subsequently unsecured during connect. Fixed.
- Nations N32G03x: J-Link didn't restore default values for option bytes properly after active read protection L1 level was detected and subsequently unsecured during connect. Fixed.
- Nations N32G052: J-Link didn't restore default values for option bytes properly after active read protection L1 level was detected and subsequently unsecured during connect. Fixed.
- Nations N32H47x/N32H48/x: J-Link didn't restore default values for option bytes properly after active read protection L1 level was detected and subsequently unsecured during connect. Fixed.
- NXP iMX8MN: After attaching to the Cortex-M7 core, the PC register always pointed to a fixed address. Fixed.
- NXP iMXRT700 device series: Core reset would not work properly, leading to debugging issues. Introduced in V8.66. Fixed.
- NXP MCX A: Flash bank for CMPA separated from code flash.
- NXP MCX L: Flash bank for CMPA separated from code flash.
DLL
- Cadence Xtensa: DCR flag DebugSwActive was always set on connect to Xtensa cores which could lead to unexpected debug behavior. Fixed.
- SWO: Under certain circumstances SWO pin was not reinitialized after reset when doing SWO tracing. Fixed.
Firmware
- Flasher ARM V5-1: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher ARM V5: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher ARM V6: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher ARM V7: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher ATE2 V1: The #STATUS command did not work with the "ALL" module selection. Introduced in V9.40. Fixed.
- Flasher ATE2 V1: WebIF: Implemented autorelease option for flex mode, which automatically releases module positions when disconnected (https://kb.segger.com/Flasher_Hub_-_Module_Configuration#Flex_mode).
- Flasher Compact V5: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher Compact V6: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher Compact V7: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher Hub-12 V1: The #STATUS command did not work with the "ALL" module selection. Introduced in V9.40. Fixed.
- Flasher Hub-12 V1: WebIF: Implemented autorelease option for flex mode, which automatically releases module positions when disconnected (https://kb.segger.com/Flasher_Hub_-_Module_Configuration#Flex_mode).
- Flasher Hub-4 V1: The #STATUS command did not work with the "ALL" module selection. Introduced in V9.40. Fixed.
- Flasher Hub-4 V1: WebIF: Implemented autorelease option for flex mode, which automatically releases module positions when disconnected (https://kb.segger.com/Flasher_Hub_-_Module_Configuration#Flex_mode).
- Flasher Portable PLUS V5: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher Portable PLUS V6: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher Portable PLUS V7: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher PRO V5-1: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher PRO V5: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher PRO V6: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher PRO V7: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher PRO XL V5-1: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher PRO XL V5: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher PRO XL V6: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- Flasher PRO XL V7: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link EDU Mini V1: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link EDU Mini V2: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link EDU/BASE/PLUS V12: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link EDU/BASE/PLUS V13: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link Lite-S124: Added support for ARMv7-A/R via SWD.
- J-Link OB RA4M2-Full: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link PRO PoE V6: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link PRO PoE V7: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link PRO V5-1: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link PRO V5: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link PRO V6: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link PRO V7: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link Ultra V8: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link ULTRA+ V5-1: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link ULTRA+ V5: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link ULTRA+ V6: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link ULTRA+ V7: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link WiFi V2: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Link-OB-K22-CortexA: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Trace PRO V3 Cortex: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Trace PRO V3: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Trace PRO V4 Cortex: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
- J-Trace PRO V4: ARMv8-A/R (e.g. Cortex-R52): Debugging cores executing code in USR mode (AArch32) would lead to wrong register values (e.g. PC) being reported. Fixed.
Version V9.42 (2026-05-06)
Highlights:
Device Provisioner
- Infineon PSC3: Added support for debug port authentication (https://kb.segger.com/Infineon_PSOC_Control_C3_Debug_Port_Authentication).
- NXP MCX A: Added secure installer erase (https://kb.segger.com/NXP_MCX_A_SiErase).
Device Support
- Infineon PSC3P7xx, PSC3P8xx, PSC3M7xx, PSC3M8xx: Added debug and flash programming support (https://kb.segger.com/Infineon_PSC3_(P7,_P8,_M7,_M8)).
- Micronas HVC5220D: Added debug & flash programming support (https://kb.segger.com/TDK-Micronas_HVC_5x).
- Telink TL322: Added debug and flash programming support (https://kb.segger.com/Telink_TL322).
- TI AM13E23x series: Added debug and flash programming support (https://kb.segger.com/TI_AM13E23x).
Other changes:
DLL
- CFI-Flash programming: A flash unlock sequence issued by J-Link before an erase operation could be misinterpreted as data to program, leading to unintended flash programming operations. Fixed.
- Clearing all trace points may result in deadlock under certain circumstances. Fixed.
Firmware
- Flasher ARM V5-1: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher ARM V5: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher ARM V6: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher ARM V7: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher Compact V5: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher Compact V5: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher Compact V6: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher Compact V6: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher Compact V7: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher Compact V7: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher Portable PLUS V5: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher Portable PLUS V5: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher Portable PLUS V6: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher Portable PLUS V6: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher Portable PLUS V7: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher Portable PLUS V7: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher PRO V5-1: Apps: Added IP client interface.
- Flasher PRO V5-1: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher PRO V5-1: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher PRO V5: Apps: Added IP client interface.
- Flasher PRO V5: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher PRO V5: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher PRO V6: Apps: Added IP client interface.
- Flasher PRO V6: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher PRO V6: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher PRO V7: Apps: Added IP client interface.
- Flasher PRO V7: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher PRO V7: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher PRO XL V5-1: Apps: Added IP client interface.
- Flasher PRO XL V5-1: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher PRO XL V5-1: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher PRO XL V5: Apps: Added IP client interface.
- Flasher PRO XL V5: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher PRO XL V5: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher PRO XL V6: Apps: Added IP client interface.
- Flasher PRO XL V6: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher PRO XL V6: Improved the error message displayed if an imported function can not be found when loading an app.
- Flasher PRO XL V7: Apps: Added IP client interface.
- Flasher PRO XL V7: Apps: Certain use of TIF_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- Flasher PRO XL V7: Improved the error message displayed if an imported function can not be found when loading an app.
- J-Link EDU Mini V1: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link EDU Mini V2: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link EDU/BASE/PLUS V12: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link EDU/BASE/PLUS V13: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link OB RA4M2-CortexM: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link OB RA4M2-Full: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link OB RA4M2-RISCV: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link PRO PoE V6: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link PRO PoE V7: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link PRO V5-1: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link PRO V5: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link PRO V6: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link PRO V7: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link ULTRA+ V5-1: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link ULTRA+ V5: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link ULTRA+ V6: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link ULTRA+ V7: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link WiFi V2: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link-OB-K22-CortexA: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link-OB-K22-CortexM: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link-OB-K22-RISCV: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Link-OB-STM32F072-128KB-CortexM: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Trace PRO V3 Cortex: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Trace PRO V3 CortexM: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Trace PRO V3 RISC-V: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Trace PRO V3: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Trace PRO V4 Cortex: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Trace PRO V4 CortexM: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Trace PRO V4 RISC-V: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
- J-Trace PRO V4: PCode: Certain use of JLINK_JTAG API functions could, in rare cases, lead to a firmware crash. Fixed.
J-Flash
- Changed button names and descriptions from "...Wiki" to "...Knowledge Base" in help context menu.
- Removed "Flasher Hub Wiki" button from "Help" context menu.
J-Flash SPI
- Changed button names and descriptions from "...Wiki" to "...Knowledge Base" in help context menu.
- Removed "Flasher Hub Wiki" button from "Help" context menu.
Registration
- When more than 1 probe / programmer was connected, the values in the "Registered?" column were incorrect and registration did not work. Fixed.
Version V9.40 (2026-04-30)
Highlights:
Device Support
- Renesas AT25QL0321C: Added flash programming support.
- Renesas AT25QL0641C: Added flash programming support.
- Renesas AT25QL1281C: Added flash programming support.
- Renesas AT25QL2561C: Added flash programming support.
- Renesas AT25SL0321C: Added flash programming support.
- Renesas AT25SL1281C: Added flash programming support.
- Renesas AT25SL2561C: Added flash programming support.
- Renesas RA8D2: Added debug support for swapped cores in which case CPU1 (CM33) is the primary CPU (https://kb.segger.com/Renesas_RA8D2).
- Renesas RA8M2: Added debug support for swapped cores in which case CPU1 (CM33) is the primary CPU (https://kb.segger.com/Renesas_RA8M2).
- Renesas RA8P1: Added debug support for swapped cores in which case CPU1 (CM33) is the primary CPU (https://kb.segger.com/Renesas_RA8P1).
- Renesas RA8T2: Added debug support for swapped cores in which case CPU1 (CM33) is the primary CPU (https://kb.segger.com/Renesas_RA8T2).
- ST SR5E1 series: Added flash programming support for UTEST flash bank.
J-Flash SPI
- Renesas AT25QL0321C: Added flash programming support.
- Renesas AT25QL0641C: Added flash programming support.
- Renesas AT25QL1281C: Added flash programming support.
- Renesas AT25QL2561C: Added flash programming support.
- Renesas AT25SL0321C: Added flash programming support.
- Renesas AT25SL1281C: Added flash programming support.
- Renesas AT25SL2561C: Added flash programming support.
- ST M95256-A125: Added EEPROM programming support.
- ST M95256-A145: Added EEPROM programming support.
Other changes:
Device Support
- Device ID for supported SPI flash IS25WJ016F did not match the spec. Introduced with v9.18. Fixed.
- ESWIN EAM2011: Flash operations (write, erase) would not work as expected under certain circumstances. Fixed.
- Infineon CY8C4147xxx-Txxx: Programming could fail due to an incorrect RAM size. Fixed.
- Microchip PIC32CZxxxxCA80, PIC32CZxxxxCA90: Failed to connect to the device via JTAG. Fixed.
- Microchip SAMD5/E5: Programming internal flash may fail due to bootloader protection. Fixed.
- Nations N32G401, N32G43x: Chip erase operations on internal flash completed successfully, but the operation incorrectly returned an error status. Fixed.
- NordicSemi nRF54H20: Added flash programming support for BICR area (https://kb.segger.com/Nordic_Semiconductor_nRF54H20).
- NXP iMX94, iMX95: Failed to connect to the device via JTAG. Fixed.
- Renesas RA6E1, RA6M4, RA6M5, RA6T2, RA4M3, RA4L1, RA4C1: Restoration of flash breakpoints could fail due to cache inconsistencies if C-cache was enabled by user. Fixed.
- Renesas RA8 series: Device-specific pin reset did not configure core-specific wait setting properly. Introduced with V7.98b. Fixed.
- ST STM32WB05 device series: Flash operations failed with timeout error. Fixed.
- TI MSPM0 device series: Added mass erase and factory reset option.
- Tongxin THA6014: Added debug & flash programming support (https://kb.segger.com/Tongxin_THA6_Gen_2).
DLL
- JLINKARM_Reset() did not return an error if the Reset related J-Link script file functions reported an error. Fixed.
Firmware
- Flasher ARM V5-1: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher ARM V5: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher ARM V6: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher ARM V7: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher Compact V5: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher Compact V6: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher Compact V7: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher Portable PLUS V5: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher Portable PLUS V6: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher Portable PLUS V7: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher PRO V5-1: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher PRO V5: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher PRO V6: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher PRO V7: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher PRO XL V5-1: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher PRO XL V5: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher PRO XL V6: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
- Flasher PRO XL V7: When serial number programming was enabled, the serial number was also incremented when a non-programming action (e.g. #VERIFY) was taken. Fixed.
J-Flash
- No error was reported if the Reset related J-Link script file functions reported an error. Fixed.
- The warning "Flasher V4 or earlier detected." was incorrectly shown when downloading files to a Flasher Hub. Introduced in V9.34. Fixed.
J-Flash SPI
- The warning "Flasher V4 or earlier detected." was incorrectly shown when downloading files to a Flasher Hub. Introduced in V9.34. Fixed.
J-Link Package
- Reverted "Added high DPI support to installer.". Introduced in V9.30.
- Reverted: "Added high DPI support to installer."
J-Run
- No error was reported if the Reset related J-Link script file functions reported an error. Fixed.
J-Scope
- When a project was opened, the active variables were cleared when a new variable was added. Fixed.
Version V9.38a (2026-04-23)
Device Support
- Reverted device support for "Tongxin THA6412: Added flash programming support for PFLASH2 and PFLASH3 (https://kb.segger.com/Tongxin_THA6_Gen_2)" due to compatibility issues.
Version V9.38 (2026-04-22)
Highlights:
Device Provisioner
- NXP NCJ29D6 Plus: Added software update via SWUP (https://kb.segger.com/NXP_NCJ29D6Plus_Softwareupdate).
- NXP NCJ29D6: Added software update via SWUP. (https://kb.segger.com/NXP_NCJ29D6_Softwareupdate).
- Texas Instruments CC35xx series: Added support for opening debug access (https://kb.segger.com/TI_CC35xx_Device_Provisioning).
Device Support
- ISSI IS25LP01GG: Added flash programming support.
- Macronix MX25U25645G: Added flash programming support.
- NXP NCJ29D6 Plus: Added debug and flash programming support (https://kb.segger.com/NXP_NCJ29D6).
- NXP NCJ29D6: Added debug and flash programming support (https://kb.segger.com/NXP_NCJ29D6).
- ST STM32H7Rxxx/STM32H7Sxxx: Added flash programming support for XSPI1 (https://kb.segger.com/ST_STM32H7).
- ST STM32H7Rxxx/STM32H7Sxxx: Added flash programming support for XSPI2 pin config "CLK@PO4_nCS@PO0_D0@PP0_D1@PP1_D2@PP2_D3@PP3_D4@NA_D5@NA_D6@NA_D7@NA" on P1 of XSPIM (https://kb.segger.com/ST_STM32H7).
- Texas Instruments CC35xx series: Added debug support (https://kb.segger.com/TI_CC35xx).
J-Flash SPI
- ISSI IS25LP01GG: Added flash programming support.
- Macronix MX25U25645G: Added flash programming support.
Other changes:
Device Support
- Hilscher netX90: QSPI flashloader did not validate FIFO fill level before writing address bytes, potentially causing silent data loss. Fixed.
- Infineon PSOC EDGE E8: Flash programming on SMIF0_NS and SMIF0_S flashbanks did not work properply. Introduced with V9.14. Fixed.
- Micron MT25QU512ABB: Added flash programming support.
- Nations N32H78x device series: CM7 core would not halt after reset, leading to flash programming issues under certain circumstances. Fixed.
- NXP NCJ29D5: Programming of DSP flash bank failed under certain circumstances. Fixed.
- Renesas RZ/T2M: The QE bit was not restored after QSPI flash programming. Fixed.
- ST Stellar SR6 P/G: Under certain circumstances the debug connection stalled after device reset. Fixed.
- ST STM32H7Rxxx/STM32H7Sxxx: Flashloader for XSPI2 did not restore certain GPIO and XSPI registers properly after flash operations. Introduced with V7.96j. Fixed.
- ST STM32U5: QSPI Flashloader uses drive strength VERY HIGH instead of MEDIUM on QSPI pins, which can possibly be out of spec for some use cases. Fixed.
- TI LM3: Readout of completely blank flash failed on some devices with internal ROM bootloader. Fixed.
- Tongxin THA6412: Added flash programming support for PFLASH2 and PFLASH3 (https://kb.segger.com/Tongxin_THA6_Gen_2).
DLL
- Improved logging of RTT related background operations (e.g. searching for control block, ...).
Firmware
- Flasher ATE2 V1: WebIF: Dashboard: Added user interface for registration status of Flasher Hub.
- Flasher Compact V5: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher Compact V6: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher Compact V7: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher Hub-12 V1: WebIF: Dashboard: Added user interface for registration status of Flasher Hub.
- Flasher Hub-4 V1: WebIF: Dashboard: Added user interface for registration status of Flasher Hub.
- Flasher Portable PLUS V5: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher Portable PLUS V6: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher Portable PLUS V7: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher PRO V5-1: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher PRO V5: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher PRO V6: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher PRO V7: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher PRO XL V5-1: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher PRO XL V5: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher PRO XL V6: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
- Flasher PRO XL V7: Apps: TIF_JTAG_TransferBits(): Transferring longer JTAG sequences could lead to a firmware freeze. Fixed.
J-Flash SPI
- Micron MT25QU512ABB: Added flash programming support.
Version V9.36 (2026-04-15)
Highlights:
Device Support
- Renesas AT25QF2561C: Added flash programming support.
J-Flash SPI
- Renesas AT25QF2561C: Added flash programming support.
Other changes:
Device Support
- VORAGO VA416xx: Added knowledgebase article (https://kb.segger.com/VORAGO_VA416xx).
DLL
- JLINKARM_EMU_GetProductName() did not correctly return the names of Flasher Hub-4 and Flasher Hub-12. Fixed.
GDB Server
- The -USB and -IP parameter options would not always be included correctly in the commandline string generated by the GUI version of the server. Fixed.
Version V9.34b (2026-04-10)
DLL
- The J-Link DLL could crash when parsing J-Link device XML files with "Aliases" attribute. Fixed.
J-Link DSK
- Reverted "JLinkDevices.xml parsing: Added attribute InhertiSkipFlashBankInfo for excluding flash banks during inheritance (https://kb.segger.com/J-Link_Device_Support_Kit).". Introduced in V9.34.
Version V9.34a (2026-04-09)
GUI Applications
- Linux: Launching GUI applications failed due to an error while loading shared libraries. Fixed.
Version V9.34 (2026-04-08)
Highlights:
Device Support
- TI AM62xx series: Added debug support for Cortex-A53 and Cortex-R5 cores (https://kb.segger.com/TI_AM62xx).
Other changes:
Commander
- -NoGui command line option did not prevent unsecure dialogs from showing. Fixed.
Configurator
- Configuration dialog: VCOM: Added link to knowledge base (https://kb.segger.com/J-Link_-_Virtual_COM_Port / https://kb.segger.com/Flasher_-_Virtual_COM_Port).
Device Provisioner
- STM32C5 Device Provisioner: Improved script output by adapting messages regarding device power-on-reset.
Device Support
- Added native SWO support for Analog Devices ADuCM410 series.
- Infineon MB9AFxxxx, MB9BFxxxx series: Added option bytes programming support (https://kb.segger.com/Infineon_MB9xF).
- Nations N32G401, N32G43x, NS32G45x, NS32G4FR, N32WB4xx, N32L4xx, N32G003, N32A003, N32G052, N32A052, N32G03x device series: Flash lock setting was not restored correctly. Fixed.
- ST STM32H5: Added support for bank swap configuration during flash programming.
- ST STM32H5: Added support for chip erase.
- Telink TL32: Resetting the device may cause it to become unresponsive. Introduced in V9.32. Fixed.
DLL
- Executing SuppressGUI before JLINK_Open() would have no effect in certain circumstances. Fixed.
HSS
- The application crashed when passing zero as the 'Period_us' parameter to JLINK_HSS_Start(). Fixed.
J-Flash
- Added command line option "-generatetestdata".
J-Flash SPI
- Added command line option "-generatetestdata".
J-Flash SPI CL
- Added command line option "-generatetestdata".
J-Link DSK
- JLinkDevices.xml parsing: Added attribute InhertiSkipFlashBankInfo for excluding flash banks during inheritance (https://kb.segger.com/J-Link_Device_Support_Kit).
J-Scope
- The application crashed when using zero (fastest sampling speed) as the HSS sampling period. Fixed.
Trace
- TPIU flushing on Alif B1 devices was not working as intended. Fixed.
Version V9.32 (2026-04-01)
Highlights:
Device Support
- Alliance Memory AS25F3128MQ: Added flash programming support.
- Macronix MX25U12845G: Added flash programming support.
- ST STM32U5 device series: Added flash programming support for pin config "CLK@PB10_nCS@PA4_D0@PB1_D1@PB0_D2@PA7_D3@PA6_D4@PC1_D5@PC2_D6@PC3_D7@PC0" (https://kb.segger.com/ST_STM32U5).
- Telink TL323: Added flash programming support (https://kb.segger.com/Telink_TL323).
- TI AWR144x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_AWR144x).
- TI AWR164x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_AWR164x).
- TI AWR184x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_AWR184x).
- TI AWR2944P, AWR2944-ECO, AWR2944LC: Added device support (https://kb.segger.com/TI_AWR2944).
- TI AWR684x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_AWR684x).
- TI IWR144x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_IWR144x).
- TI IWR164x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_IWR164x).
- TI IWR184x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_IWR184x).
- TI IWR644x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_IWR644x).
- TI IWR684x: Added debug and QSPI flash programming support (https://kb.segger.com/TI_IWR684x).
- XMC XM25QH128D: Added flash programming support.
- XMC XM25QH32D: Added flash programming support.
- XMC XM25QH64D: Added flash programming support.
J-Flash SPI
- Alliance Memory AS25F3128MQ: Added flash programming support.
- Macronix MX25U12845G: Added flash programming support.
- XMC XM25QH128D: Added flash programming support.
- XMC XM25QH32D: Added flash programming support.
- XMC XM25QH64D: Added flash programming support.
Other changes:
Commander
- Added optional parameter "force" to the "reboot" command to force a reboot of the connected probe.
- Added WinUSBDisable and WinUSBEnable commands.
- Commander did not show added licenses on startup. Fixed.
- Execution of command file did not always stop on flash programming errors with ExitOnError set to 1. Fixed.
Device Provisioner
- STM32C5: Added the option to verify the OEMKEY.
Device Support
- AmbiqMicro Apollo4 series: Added out of the box SWO support.
- Microchip PIC24FJ16GA002: Wrong config word address definition. Fixed.
- Microchip PIC24FJ16GA004: Wrong config word address definition. Fixed.
- Nations N32G401, N32G430, NS32G452, NS32G455, NS32G457, NS32G4FR, N32WB4xx device series: Clock initialization during option byte or flash programming also occured when users changed clock settings from reset values. Fixed.
- Nations N32G4xx, N32WB4xx, N32L4xx device series: Added implicit erase before option byte programming and ensured that standalone option byte erasing is skipped to prevent unintended states.
- Nations N32G4xx, N32WB4xx, N32L4xx device series: Option byte programming did not work for more than 4 bytes. Fixed.
- NXP i.MX RT1180: J-Link prevented flash programming if external SPI flash exceeded 128MB on FlexSPI1 or 64MB on FlexSPI2. Fixed.
- ST STM32F401/405/407/410/411/412/413/415/417/423: Added flash programming support for OTP area (https://kb.segger.com/ST_STM32F4).
- ST STM32F4: Added chip erase operation support for internal flash bank (https://kb.segger.com/ST_STM32F4).
- ST STM32WB - FUS (WS upgrade): With the newest FUS version (v2.2.0), the wireless stack did not start after the update. Fixed.
DLL
- Implemented workaround for ESWIN devices that incorrectly reported memory access capability for RISC-V via System Bus Access.
- J-Link script files: Added API functions for handle-based file I/O operations (https://kb.segger.com/J-Link_script_files).
Firmware
- Flasher Portable PLUS V5: GUI: Long pressing the PROG button on the home screen now shows information on the currently selected projects jobs. Including the job types, name and the next serial number to be programmed.
- Flasher Portable PLUS V5: GUI: Unified top bar design for batch and managed projects with minor text improvements.
- Flasher Portable PLUS V5: When an executable app was alone in the root folder, the selected project would show as <empty>. Fixed.
- Flasher Portable PLUS V6: GUI: Long pressing the PROG button on the home screen now shows information on the currently selected projects jobs. Including the job types, name and the next serial number to be programmed.
- Flasher Portable PLUS V6: GUI: Unified top bar design for batch and managed projects with minor text improvements.
- Flasher Portable PLUS V6: When an executable app was alone in the root folder, the selected project would show as <empty>. Fixed.
- Flasher Portable PLUS V7: GUI: Long pressing the PROG button on the home screen now shows information on the currently selected projects jobs. Including the job types, name and the next serial number to be programmed.
- Flasher Portable PLUS V7: GUI: Unified top bar design for batch and managed projects with minor text improvements.
- Flasher Portable PLUS V7: When an executable app was alone in the root folder, the selected project would show as <empty>. Fixed.
J-Flash
- Reverted "Added a warning when trying to download a config file to a Flasher < V5.". Introduced in V9.24.
J-Flash SPI
- Reverted "Added a warning when trying to download a config file to a Flasher < V5.". Introduced in V9.24.
J-Scope
- A no timestamp warning was displayed when the RTT control block could not be found. Fixed.
- The RTT control block search dialog did not close when an error occurred. Fixed.
Version V9.30a (2026-03-30)
Firmware
- Flasher ATE2 V1: WebIF: After programming, the module status would sometimes not reset to idle. Introduced in V9.26. Fixed.
- Flasher Hub-12 V1: WebIF: After programming, the module status would sometimes not reset to idle. Introduced in V9.26. Fixed.
- Flasher Hub-4 V1: WebIF: After programming, the module status would sometimes not reset to idle. Introduced in V9.26. Fixed.
Version V9.30 (2026-03-25)
Highlights:
Device Support
- Added debug & flash programming support for Geehy G32A10xx device series (https://kb.segger.com/Geehy_G32A10xx).
- Macronix MX25LW25645G: Added flash programming support.
- OnMicro OM6x device family: Added debug & flash programming support (https://kb.segger.com/OnMicro_OM6x).
J-Flash SPI
- Macronix MX25LW25645G: Added flash programming support.
Other changes:
Commander
- Added product description and details to the executable file.
Configurator
- Added product description and details to the executable file.
Device Provisioner
- Added product description and details to the executable file.
- ST STM32MP25 series: Added programming support for OTP area (https://kb.segger.com/ST_STM32MP25x_OTP_programming).
Device Support
- Nations N32H47x/H48x: Programming twice would fail. Fixed.
- Renesas RZ/T2M xSPI flashloader: Initialization of xSPI1 pin configuration for 1S-1S-1S format did not match spec. Fixed.
- Renesas RZ/T2M, RZ/N2L xSPI flashloader: Added handling of fatal errors for the xSPI controller that might have occurred before calling J-Link.
- Reverted "TI MSPM0 device series: Added factory reset option" as it may lead to bricked devices in some circumstances. Introduced in V9.26.
- TI AWR2944: Under certain circumstances, connect did not work. Fixed.
DLL Updater
- Added product description and details to the executable file.
DnD Conditioner
- Added product description and details to the executable file.
Firmware
- Flasher Compact V5: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher Compact V6: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher Compact V7: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher Portable PLUS V5: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher Portable PLUS V6: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher Portable PLUS V7: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher PRO V5-1: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher PRO V5: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher PRO V6: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher PRO V7: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher PRO XL V5-1: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher PRO XL V5: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher PRO XL V6: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
- Flasher PRO XL V7: Apps: Use of the #CANCEL command while a App was executing could in rare cases fail and cause the Flasher to reboot. Fixed.
GDB Server
- Added product description and details to the executable file.
GUI Server
- Added product description and details to the executable file.
J-Flash
- Added product description and details to the executable file.
- Reverted "Added a warning when trying to download a config file to a Flasher < V5.". Introduced in V9.24.
J-Flash Lite
- Added product description and details to the executable file.
J-Flash SPI
- Added product description and details to the executable file.
- Reverted "Added a warning when trying to download a config file to a Flasher < V5.". Introduced in V9.24.
J-Link Connection Server
- Added product description and details to the executable file.
J-Link Package
- Added high DPI support to installer.
J-Mem
- Added product description and details to the executable file.
J-Run
- Added product description and details to the executable file.
J-Scope
- Added product description and details to the executable file.
JTAG Load
- Added product description and details to the executable file.
License Manager
- Added product description and details to the executable file.
Registration
- Added product description and details to the executable file.
Remote Server
- Added product description and details to the executable file.
Remote Server CL
- Added product description and details to the executable file.
RTT Client
- Added product description and details to the executable file.
RTT Logger
- Added product description and details to the executable file.
RTT Viewer
- Added product description and details to the executable file.
STM32 Utility
- Added product description and details to the executable file.
STR91x Utility
- Added product description and details to the executable file.
SWO Analyzer
- Added product description and details to the executable file.
SWO Viewer
- Added product description and details to the executable file.
SWO Viewer CL
- Added product description and details to the executable file.
XVCD Server
- Added product description and details to the executable file.
Version V9.28 (2026-03-18)
Highlights:
Device Provisioner
- ST STM32C5: Added support for life-cycle management and unlocking device.
Device Support
- NXP iMXRT1180: Added new part numbers for iMXRT1185 and iMXRT118C to the list of supported devices (https://kb.segger.com/NXP_i.MX_RT1180).
- Xilinx ZYNQ-7000 device series: Added new loader to work with hardware that uses 50MHz PSCLK external oscillator (e.g. PYNQ-Z2) (https://kb.segger.com/Xilinx_Zynq-7000).
Trace
- Published out-of-the-box trace example for Microchip PIC32CX1025SG41: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- "Failed to open DLL" instead of "Failed to connect to ..." was output if the default connect attempt failed. Fixed.
- When selecting a probe / programmer via the IP selection dialog generated by the J-Link library, connecting failed. Introduced in V9.14. Fixed.
Configurator
- Windows: Under some circumstances, the TCP/IP table displayed incorrect firmware strings in the "Probe/ programmer firmware" column. Fixed.
Device Support
- Analog Devices ADuCM36x device series: Added new part number ADuCM363 (https://kb.segger.com/Analog_ADuCM36x).
- Geehy G32R430: Flash erase of non-block-aligned sectors failed. Fixed.
- Nations N32H47x & N32H48x: Erasing after programming did not work. Fixed.
- Nations N32H47x & N32H48x: Implemented chip erase.
- Nations N32H47x & N32H48x: Only the first 64 bytes of the flash were getting programmed. Fixed.
- ST STM32F427, STM32429, STM32F437, STM32F439 devices: These devices do not feature a QSPI controller but J-Link configures a QSPI flash bank for them. Introduced in V7.92c. Fixed.
- ST STM32F446, STM32F469, STM32F479: Added watchdog handling during QSPI flash programming for IWDG and WWDG (https://kb.segger.com/ST_STM32F4).
- ST STM32F446, STM32F469, STM32F479: QSPI flash programming did not optimally initialized clocks and both clocks and the QSPI controller were not restored cleanly. Fixed.
- ST STM32F446: Added flash support for OTP area (https://kb.segger.com/ST_STM32F4).
- ST STM32F446: QSPI flashloader did not enable clock for QSPI controller. Introduced with V9.18. Fixed.
- ST STM32F446xC devices: Internal flash bank configured one 128KB sector more than allowed. Introduced in V7.92d. Fixed.
- Traveo T2G CYT2B9: Default reset via JTAG did not work properly. Fixed.
- Xilinx ZYNQ-7000 device series: QSPI flashes larger than maximum memory-mappable size could not be flashed. Fixed.
- Xilinx ZYNQ-7000 device series: Under certain cirumstances PLL was not correctly restored after flash programming. Fixed.
DLL
- If connecting to probe / programmer via IP failed, IP address 0.0.0.0 could be output in the error message. Fixed.
- Under certain circumstances DLL would crash when exiting a trace session. Fixed.
- Under certain circumstances, program & verify speed calculations were incorrect. Fixed.
Firmware
- Flasher ARM V5-1: Cortex-M: Improved memory read speed for SWD interface.
- Flasher ARM V5-1: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher ARM V5: Cortex-M: Improved memory read speed for SWD interface.
- Flasher ARM V5: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher ARM V6: Cortex-M: Improved memory read speed for SWD interface.
- Flasher ARM V6: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher ARM V7: Cortex-M: Improved memory read speed for SWD interface.
- Flasher ARM V7: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher ATE2 V1: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher Compact V5: Cortex-M: Improved memory read speed for SWD interface.
- Flasher Compact V5: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher Compact V5: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher Compact V6: Cortex-M: Improved memory read speed for SWD interface.
- Flasher Compact V6: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher Compact V6: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher Compact V7: Cortex-M: Improved memory read speed for SWD interface.
- Flasher Compact V7: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher Compact V7: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher Hub-12 V1: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher Hub-4 V1: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher Portable PLUS V5: Cortex-M: Improved memory read speed for SWD interface.
- Flasher Portable PLUS V5: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher Portable PLUS V5: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher Portable PLUS V6: Cortex-M: Improved memory read speed for SWD interface.
- Flasher Portable PLUS V6: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher Portable PLUS V6: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher Portable PLUS V7: Cortex-M: Improved memory read speed for SWD interface.
- Flasher Portable PLUS V7: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher Portable PLUS V7: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher PRO V5-1: Cortex-M: Improved memory read speed for SWD interface.
- Flasher PRO V5-1: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher PRO V5-1: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher PRO V5: Cortex-M: Improved memory read speed for SWD interface.
- Flasher PRO V5: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher PRO V5: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher PRO V6: Cortex-M: Improved memory read speed for SWD interface.
- Flasher PRO V6: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher PRO V6: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher PRO V7: Cortex-M: Improved memory read speed for SWD interface.
- Flasher PRO V7: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher PRO V7: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher PRO XL V5-1: Cortex-M: Improved memory read speed for SWD interface.
- Flasher PRO XL V5-1: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher PRO XL V5-1: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher PRO XL V5: Cortex-M: Improved memory read speed for SWD interface.
- Flasher PRO XL V5: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher PRO XL V5: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher PRO XL V6: Cortex-M: Improved memory read speed for SWD interface.
- Flasher PRO XL V6: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher PRO XL V6: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- Flasher PRO XL V7: Cortex-M: Improved memory read speed for SWD interface.
- Flasher PRO XL V7: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- Flasher PRO XL V7: Terminal: Executing the #FCRC command on an empty file could lead to a crash. Fixed.
- J-Link PRO PoE V6: Cortex-M: Improved memory read speed for SWD interface.
- J-Link PRO PoE V6: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link PRO PoE V7: Cortex-M: Improved memory read speed for SWD interface.
- J-Link PRO PoE V7: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link PRO V5-1: Cortex-M: Improved memory read speed for SWD interface.
- J-Link PRO V5-1: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link PRO V5: Cortex-M: Improved memory read speed for SWD interface.
- J-Link PRO V5: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link PRO V6: Cortex-M: Improved memory read speed for SWD interface.
- J-Link PRO V6: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link PRO V7: Cortex-M: Improved memory read speed for SWD interface.
- J-Link PRO V7: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link ULTRA+ V5-1: Cortex-M: Improved memory read speed for SWD interface.
- J-Link ULTRA+ V5-1: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link ULTRA+ V5: Cortex-M: Improved memory read speed for SWD interface.
- J-Link ULTRA+ V5: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link ULTRA+ V6: Cortex-M: Improved memory read speed for SWD interface.
- J-Link ULTRA+ V6: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link ULTRA+ V7: Cortex-M: Improved memory read speed for SWD interface.
- J-Link ULTRA+ V7: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Link WiFi V2: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Trace PRO V3 Cortex: Cortex-M: Improved memory read speed for SWD interface.
- J-Trace PRO V3 CortexM: Cortex-M: Improved memory read speed for SWD interface.
- J-Trace PRO V3 RISC-V: Cortex-M: Improved memory read speed for SWD interface.
- J-Trace PRO V3: Cortex-M: Improved memory read speed for SWD interface.
- J-Trace PRO V3: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
- J-Trace PRO V4 Cortex: Cortex-M: Improved memory read speed for SWD interface.
- J-Trace PRO V4 CortexM: Cortex-M: Improved memory read speed for SWD interface.
- J-Trace PRO V4 RISC-V: Cortex-M: Improved memory read speed for SWD interface.
- J-Trace PRO V4: Cortex-M: Improved memory read speed for SWD interface.
- J-Trace PRO V4: Resetting a Renesas RX target connected via FINE could fail in rare cases. Fixed.
GDB Server
- Armv8-A/R: Added full semihosting support for targets in AArch32 mode.
- Armv8-A/R: Added full semihosting support for targets in AArch64 mode.
- Semihosting: Command SYS_READC was not always being handled correctly in IOclient mode 2 & 3 (https://kb.segger.com/J-Link_GDB_Server#semihosting_IOClient). Fixed.
- When selecting a probe / programmer via the IP selection dialog generated by the J-Link library, connecting failed. Introduced in V9.14. Fixed.
J-Flash
- When selecting a probe / programmer via the IP selection dialog generated by the J-Link library, connecting failed. Introduced in V9.14. Fixed.
J-Link Package
- Installer: Added Unicode support, allowing special characters in paths.
J-Run
- Added command line option --nogui to suppress GUI dialogs.
Trace
- Added native trace pin support for Microchip PIC32CX1025SG41 series.
Version V9.26 (2026-03-11)
Highlights:
Device Support
- NordicSemi nRF5340: Added QSPI flash programming support (https://kb.segger.com/Nordic_Semiconductor_nRF5340).
- ST SR6G3xx: Added debug and flash programming support (https://wiki.segger.com/ST_SR6G3).
- ST SR6P3Exx: Added debug and flash programming support (https://kb.segger.com/ST_SR6P3E).
- ST STM32H5 device series: Added flash programming support for pin config "CLK@PA3_nCS@PE11_D0@PC3_D1@PB0_D2@PA7_D3@PA1_D4@NA_D5@NA_D6@NA_D7@NA" (https://kb.segger.com/ST_STM32H5).
Trace
- Published out-of-the-box trace example for Infineon PSOC Edge E84: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- ESWIN EMU32VL170: Added additional RTT search ranges to cover full RAM area.
- Infineon PSOC Edge E8 series, added support for additional reset types. (https://kb.segger.com/Infineon_PSoC_Edge_E8)
- Microchip PIC32CZ device series: Flashing of BOOT-CFG areas failed. Fixed.
- ST SR6xx: Flash programming speed increased.
- ST STM32F72xx series: Devices would be in a loop of being detected as protected and needing to be unsecured on connect. Fixed.
- TI MSPM0 device series: Added factory reset option.
Firmware
- Flasher ARM V5-1: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher ARM V5-1: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher ARM V5: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher ARM V5: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher ARM V6: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher ARM V6: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher ARM V7: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher ARM V7: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher ATE2 V1: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher ATE2 V1: Terminal: Expanded the #STATUS command to support retrieving the status of modules.
- Flasher ATE2 V1: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_Hub_-_Remote_control##HWINFO)
- Flasher Compact V5: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher Compact V5: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher Compact V6: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher Compact V6: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher Compact V7: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher Compact V7: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher Hub-12 V1: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher Hub-12 V1: Terminal: Expanded the #STATUS command to support retrieving the status of modules.
- Flasher Hub-12 V1: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_Hub_-_Remote_control##HWINFO)
- Flasher Hub-4 V1: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher Hub-4 V1: Terminal: Expanded the #STATUS command to support retrieving the status of modules.
- Flasher Hub-4 V1: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_Hub_-_Remote_control##HWINFO)
- Flasher Portable PLUS V5: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher Portable PLUS V5: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher Portable PLUS V6: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher Portable PLUS V6: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher Portable PLUS V7: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher Portable PLUS V7: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher PRO V5-1: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher PRO V5-1: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher PRO V5: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher PRO V5: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher PRO V6: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher PRO V6: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher PRO V7: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher PRO V7: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher PRO XL V5-1: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher PRO XL V5-1: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher PRO XL V5: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher PRO XL V5: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher PRO XL V6: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher PRO XL V6: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- Flasher PRO XL V7: Added #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size.
- Flasher PRO XL V7: Terminal: Introduced #HWINFO command to retrieve product and runtime information. Supports serial number, firmware, used disk size and total disk size. (https://kb.segger.com/Flasher_-_Remote_control##HWINFO)
- J-Link-OB-XMC4200 / iMOTION-Link: Added the ability to update the bootloader. For more information on why that might be necessary, please visit: https://kb.segger.com/J-Link-OB-XMC4200
- J-Link-OB-XMC4200 / iMOTION-Link: Added WinUSB (driverless) mode support.
J-Flash
- "Detect" and "Verify" buttons in JTAG are now disabled for gang programmers.
J-Link Package
- Removed discontinued "STM32 Utility" from package.
Version V9.24a (2026-03-05)
Highlights:
Device Support
- ST STM32C5: Added debug and flash programming support (https://kb.segger.com/ST_STM32C5).
Version V9.24 (2026-03-03)
Highlights:
Device Support
- Geehy APM32F4 device series: Added debug & flash programming support for APM32F42x subseries (https://kb.segger.com/Geehy_APM32F4xx).
- Geehy G32R430 device series: Added debug & flash programming support (https://kb.segger.com/Geehy_G32R430).
- Nordic NRF54LM20 device series: Added debug & flash programming support for new part number NRF54LM20B (https://kb.segger.com/Nordic_Semiconductor_nRF54Lxx).
- NXP iMX94 (Cortex-A55): Added flash programming support for external QSPI flash (https://kb.segger.com/NXP_i.MX_94).
- NXP iMX94 series: Added debug support for the Cortex-A55, Cortex-M33 and Cortex-M7 cores (https://kb.segger.com/NXP_i.MX_94).
- NXP PLC-IO-KIT board: Added flash programming support for Macronix MX25UM25345G octal SPI flash chip (https://kb.segger.com/NXP_i.MX_RT1180).
- ST STM32H5E4xx, STM32H5E5xx, STM32H5F4xx, STM32H5F5xx: Added debug and flash programming support (https://kb.segger.com/ST_STM32H5).
Other changes:
Commander
- Probes on the network were not found/discovered reliably, if more than 8 network adapters were present on the host computer. Introduced in V8.98. Fixed.
- Using the "hwinfo" command, some IP addresses were output incorrectly. Fixed.
Configurator
- Probes on the network were not found/discovered reliably, if more than 8 network adapters were present on the host computer. Introduced in V8.98. Fixed.
- Reverted replacing J-Link and Flasher specific applications with the "SEGGER Configurator" application. Introduced in V9.22.
Device Provisioner
- Infineon Traveo T2G: Added support for Debug access port authentication (https://kb.segger.com/Infineon_Traveo_T2G_Debug_Authentication).
Device Support
- Infineon Traveo T2G: Improved error handling to prevent programming of non-blank flash.
- NXP i.MX RT1180: Added watchdog handling during flash programming for WDOG module (https://kb.segger.com/NXP_i.MX_RT1180).
- NXP Kinetis K series: Flashloader did not restore HSRUN mode after flashing. Fixed.
- NXP Kinetis K series: Flashloader did not wait for target to enter RUN mode. Fixed.
- ST STM32U3B5/U3C5: Added debug and flash programming support.
- ST STM32WL3R: Added debug and flash programming support (https://kb.segger.com/ST_STM32WL3R).
DLL
- J-Link script file API function JLINK_FILE_Write() did not create a file if there is none. Fixed.
Firmware
- Flasher ARM V5-1: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher ARM V5-1: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher ARM V5-1: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher ARM V5: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher ARM V5: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher ARM V5: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher ARM V6: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher ARM V6: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher ARM V6: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher ARM V7: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher ARM V7: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher ATE2 V1: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Compact V5: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher Compact V5: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Compact V5: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher Compact V6: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher Compact V6: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Compact V6: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher Compact V7: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher Compact V7: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Compact V7: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher Hub-12 V1: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Hub-4 V1: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Portable PLUS V5: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher Portable PLUS V5: Managed projects: For new project management, starting a project without a Flasher.ini would sometimes fail. Fixed.
- Flasher Portable PLUS V5: The selected project on screen did not automatically update when changing the project files. Fixed.
- Flasher Portable PLUS V5: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Portable PLUS V5: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher Portable PLUS V6: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher Portable PLUS V6: Managed projects: For new project management, starting a project without a Flasher.ini would sometimes fail. Fixed.
- Flasher Portable PLUS V6: The selected project on screen did not automatically update when changing the project files. Fixed.
- Flasher Portable PLUS V6: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Portable PLUS V6: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher Portable PLUS V7: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher Portable PLUS V7: Managed projects: For new project management, starting a project without a Flasher.ini would sometimes fail. Fixed.
- Flasher Portable PLUS V7: The selected project on screen did not automatically update when changing the project files. Fixed.
- Flasher Portable PLUS V7: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher Portable PLUS V7: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher PRO V5-1: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher PRO V5-1: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher PRO V5-1: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher PRO V5-1: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher PRO V5: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher PRO V5: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher PRO V5: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher PRO V5: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher PRO V6: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher PRO V6: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher PRO V6: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher PRO V6: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher PRO V7: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher PRO V7: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher PRO V7: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher PRO XL V5-1: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher PRO XL V5-1: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher PRO XL V5-1: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher PRO XL V5-1: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher PRO XL V5: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher PRO XL V5: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher PRO XL V5: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher PRO XL V5: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher PRO XL V6: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher PRO XL V6: Establishing an FTP connection could fail when the Flasher was in standby mode. Introduced in V9.22. Fixed.
- Flasher PRO XL V6: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher PRO XL V6: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
- Flasher PRO XL V7: Apps: Minimal programming apps could sometimes falsely report insufficient heap size. Fixed.
- Flasher PRO XL V7: WebIF: Clicking the SEGGER logo in the navigation bar now leads to the dashboard.
- Flasher PRO XL V7: When executing a custom app (.pex) while Configurator was running and connecting to Flasher, the app execution could end prematurely. Fixed.
GDB Server
- Probes on the network were not found/discovered reliably, if more than 8 network adapters were present on the host computer. Introduced in V8.98. Fixed.
J-Flash
- Probes on the network were not found/discovered reliably, if more than 8 network adapters were present on the host computer. Introduced in V8.98. Fixed.
- Project settings: After removing all entries inside the tables for init or exit steps, some buttons were not disabled correctly, which could crash the application when clicked. Fixed.
J-Flash SPI
- Project settings: After removing all entries inside the tables for init or exit steps, some buttons were not disabled correctly, which could crash the application when clicked. Fixed.
J-Link Package
- Replaced USB Web Server with J-Link USB Web Server. Introduced in V9.22.
Version V9.22 (2026-02-24)
Highlights:
Device Support
- NXP MCX L device series: Added debug & flash programming support (https://kb.segger.com/NXP_MCX_L).
- Renesas RA0E3: Added debug & flash programming support (https://kb.segger.com/Renesas_RA0E3).
- ST STM32WBA2 : Added debug & flash programming support (https://kb.segger.com/ST_STM32WBA).
Other changes:
Configurator
- Replaced J-Link and Flasher specific applications with the "SEGGER Configurator" application.
Device Provisioner
- Added unlock function to STM32C0 DevPro script (https://kb.segger.com/ST_STM32C0_Option_Bytes_Programming).
- Added unlock script for STM32G0x0 (https://kb.segger.com/ST_STM32G0x0_Option_Bytes_Unlock).
- Added unlock script for STM32G0x1 (https://kb.segger.com/ST_STM32G0x1_Option_Bytes_Unlock).
- Added unlock script for STM32G4 (https://kb.segger.com/ST_STM32G4_Option_Bytes_Unlock).
- Added unlock script for STM32H743, STM32H753 and STM32H750 (https://kb.segger.com/ST_STM32H743_53_50_Option_Bytes_Unlock).
- Added unlock script for STM32H745, STM32H747, STM32H755 and STM32H757 (https://kb.segger.com/ST_STM32H745_47_55_57_Option_Bytes_Unlock).
- Added unlock script for STM32H7A3 and STM32H7B3 (https://kb.segger.com/ST_STM32H7A3_B3_Option_Bytes_Unlock).
- Added unlock script for STM32L0 (https://kb.segger.com/ST_STM32L0_Option_Bytes_Unlock).
- Added unlock script for STM32L1 (https://kb.segger.com/ST_STM32L1_Option_Bytes_Unlock).
- Added unlock script for STM32L4 (https://kb.segger.com/ST_STM32L4_Option_Bytes_Unlock).
- Added unlock script for STM32L5 (https://kb.segger.com/ST_STM32L5_Option_Bytes_Unlock).
- Added unlock script for STM32WB (https://kb.segger.com/ST_STM32WB_Option_Bytes_Unlock).
- Added unlock script for STM32WL (https://kb.segger.com/ST_STM32WL_Option_Bytes_Unlock).
- Renamed STM32F74/F75 unlock script to reflect compatibility with STM32F72 and STM32F73 (https://kb.segger.com/ST_STM32F72_F73_F74_F75_Option_Bytes_Unlock).
- ST STM32H5 series: Under certain circumstances Device Provisioner commands were terminated due to failed device identification. Fixed.
Device Support
- GigaDevice GD25LX256E: The first data byte during a read operation could have been skipped with certain flashloaders. Fixed. Introduced with v9.14.
- GigaDevice GD32H77 device series: Added debug & flash programming support (http://kb.segger.local/GigaDevice_GD32H77).
- Infineon EZPD PMG1 device family: Added debug & flash programming support for CYPM1216 (PMG1-B2 subfamily).
- Nordic NRF54L device series: Added flash programming and debug support for NRF54LS05x devices (https://kb.segger.com/Nordic_Semiconductor_nRF54Lxx).
- NXP iMXRT700: Memory access would lead to excessive calls of HandleBeforeMemAccessWrite(), HandleAfterMemAccessWrite() and HandleBeforeMemAccessRead() for cache handling. Fixed.
- NXP MCXE31 series: Added initialization of ITCM0 on the connection to the target.
- NXP S32K3xx: Added initialization of ITCM0 on the connection to the target.
- Renesas RZ/A3M: An incorrect reset sequence for this device caused corruption of the R0 and R1 registers. Fixed.
- Renesas RZ/A3UL: An incorrect reset sequence for this device caused corruption of the R0 and R1 registers. Fixed.
- Renesas RZ/N2L: An incorrect reset sequence for this device caused corruption of the R0 and R1 registers. Fixed.
- Renesas RZ/T2H: An incorrect reset sequence for this device caused corruption of the R0 and R1 registers. Fixed.
- Renesas RZ/T2N: An incorrect reset sequence for this device caused corruption of the R0 and R1 registers. Fixed.
- STM32N6 device series: Added new part numbers.
- Xilinx Zynq 7000: Flash programming did not work correctly with an IO voltage of 1.8V. Fixed.
- Xilinx Zynq 7000: Flash programming did not work correctly with SPI flashes operating in single (non-quad) SPI mode. Fixed.
DLL
- Connection to USB device may fail if SetAllowFlashCache command was used. Fixed.
Firmware
- Flasher Portable PLUS V7: Introduction of standby mode caused file system corruption on auto power off after 60s in battery driven mode. Introduced in V9.18. Fixed.
- Flasher Portable PLUS V7: Pressing the PROG button after a finished programming job, could sometimes lead to the filesystem being corrupted until the next action. Introduced in V.9.18. Fixed.
GDB Server
- Reading device memory during a semihosting operation could fail in some circumstances. Introduced in V9.14. Fixed.
J-Link USB Web Server
- Replaced by the "SEGGER USB Web Server" application.
Remote Server
- Under certain circumstances memory read and write could fail. Fixed.
Version V9.20 (2026-02-19)
Highlights:
J-Flash SPI
- Infineon FM25V05A: Added flash programming support.
Other changes:
Commander
- Added user error message if "exec" command is unknown.
- Some "exec" commands were incorrectly detected as invalid and silently ignored. Fixed.
Device Provisioner
- Added unlock script for STM32F74 and STM32F75.
- Added unlock script for STM32F76 and STM32F77.
- NordicSemi: Added support for life cycle state (LCS) transitions (https://kb.segger.com/nRF54H20_LCS_Transitions).
Device Support
- Nordic nRF91: Flash verification for the UICR area would fail. Fixed.
- Nordic nRF91: Merged "UICR User" and "UICR OTP" into one "UICR" flashbank.
- Silicon Labs SiWG917 device series: Added debug & flash programming support for SiWG917Yxxx part numbers (https://kb.segger.com/Silicon_Labs_SiWx917).
- Toshiba TMPM3x and TMPM4x series: Flash programming failed if IHOSC1 clock was off. Fixed.
DLL
- Added support for Flasher ATE2 (4 channel).
- Further attempts to open J-Link devices failed after unsuccessful connection in Embedded Studio. Fixed.
- J-Link Web Control Panel was crashing when opening the 'Flash' tab after adding an unnamed flash bank via JLinkScript. Fixed.
Firmware
- Flasher ARM V5-1: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher ARM V5: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher ARM V6: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher ARM V7: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher ATE2 V1: Added support for Flasher ATE2 (4 channel).
- Flasher ATE2 V1: WebIF: In flex mode, disabled Flashers counted towards the number of connected modules. Introduced in V7.96d. Fixed.
- Flasher Compact V5: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher Compact V5: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher Compact V6: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher Compact V6: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher Compact V7: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher Compact V7: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher Hub-12 V1: WebIF: In flex mode, disabled Flashers counted towards the number of connected modules. Introduced in V7.96d. Fixed.
- Flasher Hub-4 V1: WebIF: In flex mode, disabled Flashers counted towards the number of connected modules. Introduced in V7.96d. Fixed.
- Flasher Portable PLUS V5: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher Portable PLUS V5: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher Portable PLUS V6: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher Portable PLUS V6: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher Portable PLUS V7: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher Portable PLUS V7: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher PRO V5-1: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher PRO V5-1: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher PRO V5: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher PRO V5: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher PRO V6: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher PRO V6: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher PRO V7: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher PRO V7: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher PRO XL V5-1: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher PRO XL V5-1: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher PRO XL V5: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher PRO XL V5: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher PRO XL V6: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher PRO XL V6: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- Flasher PRO XL V7: Apps: Use of the #CANCEL command could cause the Flasher to reboot when used during a programming app. Fixed.
- Flasher PRO XL V7: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link PRO PoE V6: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link PRO PoE V7: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link PRO V5-1: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link PRO V5: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link PRO V6: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link PRO V7: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link ULTRA+ V5-1: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link ULTRA+ V5: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link ULTRA+ V6: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link ULTRA+ V7: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Link-OB-Apollo4-CortexM: Using SWO (e.g. with J-Link SWO Viewer) and the VCOM interface simultaneously would cause the firmware to crash. This was especially prevalent on linux systems. Fixed.
- J-Trace PRO V3 Cortex: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Trace PRO V3 Cortex: Under some circumstances trace performance could be significantly slowed down. Introduced in V9.18. Fixed.
- J-Trace PRO V3 CortexM: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Trace PRO V3 CortexM: Under some circumstances trace performance could be significantly slowed down. Introduced in V9.18. Fixed.
- J-Trace PRO V3 RISC-V: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Trace PRO V3 RISC-V: Under some circumstances trace performance could be significantly slowed down. Introduced in V9.18. Fixed.
- J-Trace PRO V3: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Trace PRO V3: Under some circumstances trace performance could be significantly slowed down. Introduced in V9.18. Fixed.
- J-Trace PRO V4 Cortex: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Trace PRO V4 Cortex: Under some circumstances trace performance could be significantly slowed down. Introduced in V9.18. Fixed.
- J-Trace PRO V4 CortexM: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Trace PRO V4 CortexM: Under some circumstances trace performance could be significantly slowed down. Introduced in V9.18. Fixed.
- J-Trace PRO V4 RISC-V: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Trace PRO V4 RISC-V: Under some circumstances trace performance could be significantly slowed down. Introduced in V9.18. Fixed.
- J-Trace PRO V4: In rare cases, the target communication with JTAG/SWD could lead to a timeout. Introduced in V9.18. Fixed.
- J-Trace PRO V4: Under some circumstances trace performance could be significantly slowed down. Introduced in V9.18. Fixed.
Version V9.18 (2026-02-11)
Highlights:
Device Support
- ISSI IS25WJ016F: Added flash programming support.
- PANCHIP PAN101x: Added debug & flash programming support (https://kb.segger.com/PANCHIP_PAN101x).
- PANCHIP PAN107x: Added debug & flash programming support (https://kb.segger.com/PANCHIP_PAN107x).
- ST STM32F469: Added QSPI flash programming support for pin config CLK@PA7_nCS@PB6_D0@PD11_D1@PD12_D2@PE2_D3@PA1 (https://kb.segger.com/ST_STM32F4).
- ST STM32F469: Added QSPI flash programming support for pin config CLK@PA7_nCS@PC11_D0@PE7_D1@PE8_D2@PE9_D3@PE10 (https://kb.segger.com/ST_STM32F4).
- TI MSPM0G1207, MSPM0G1218, MSPM0G3207, MSPM0G3218: Added debug and flash programming support (https://kb.segger.com/TI_MSPM0G).
J-Flash SPI
- ISSI IS25WJ016F: Added flash programming support.
- Puya PY25Q64HA: Added flash programming support.
Other changes:
Commander
- The application took an unusually long time (about 3 seconds) to quit when command-line argument parsing failed. Fixed.
Device Provisioner
- ST STM32U5 series: Added direct regression from RDP 0.5 to RDP 0 for convenience (https://kb.segger.com/ST_STM32U5_Option_Bytes_Programming).
Device Support
- Renamed device manufacturer name "TI" to "Texas Instruments".
- Renesas RA6E1, RA6M4, RA6M5, RA6T2, RA4M3, RA4L1, RA4C1: Flash operations could fail due to cache inconsistencies if S-cache was enabled by user and no reset occured before flash operations. Fixed.
- Renesas RZ/V2H: The connection to the CM33_0 core did not work when CM33 cold boot was selected. Fixed.
- TI AWR2944: Depending on the device's configuration flash programming could fail in the default RAM region. Added an option to choose a secondary RAM region (For more information, see: https://kb.segger.com/TI_AWR2944#Work_RAM_regions).
- TI AWR2944: Flash programming with the security variants of the device (HS-FS, HS-SE) would always fail. Fixed.
DLL
- Connection with USB device in Ozone may fail if SetResetType command is used. Fixed.
- J-Link Commander have crashed if AHB-AP index greater than 28 was used. Fixed.
- RTT: Selecting RTT auto detection (e.g. via command string "SetRTTAddr=0") during an active RTT session would unnecessarily restart RTT and the RTT Control Block scan. Fixed.
- RTT: Setting the RTT control block address (e.g. via command string "SetRTTAddr") would remove all search ranges except for RAM used by J-Link as work RAM. Fixed.
Firmware
- Flasher ARM V5-1: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher ARM V5-1: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher ARM V5-1: WebIF: Added file explorer.
- Flasher ARM V5: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher ARM V5: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher ARM V5: WebIF: Added file explorer.
- Flasher ARM V6: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher ARM V6: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher ARM V6: WebIF: Added file explorer.
- Flasher ARM V7: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher ARM V7: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher ARM V7: WebIF: Added file explorer.
- Flasher ATE2 V1: USB Web server connections could freeze when HTTP traffic caused by web interface was heavy enough. Fixed.
- Flasher ATE2 V1: WebIF: Files: Added type description for .adf files and ajusted description for .pex files.
- Flasher Compact V5: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher Compact V5: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher Compact V5: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher Compact V5: WebIF: Added file explorer.
- Flasher Compact V5: WebIF: Status > Flasher: Caption was "Network configuration" instead of "Flasher configuration" and took up more height than intended. Fixed.
- Flasher Compact V6: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher Compact V6: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher Compact V6: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher Compact V6: WebIF: Added file explorer.
- Flasher Compact V6: WebIF: Status > Flasher: Caption was "Network configuration" instead of "Flasher configuration" and took up more height than intended. Fixed.
- Flasher Compact V7: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher Compact V7: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher Compact V7: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher Compact V7: WebIF: Added file explorer.
- Flasher Compact V7: WebIF: Status > Flasher: Caption was "Network configuration" instead of "Flasher configuration" and took up more height than intended. Fixed.
- Flasher Hub-12 V1: USB Web server connections could freeze when HTTP traffic caused by web interface was heavy enough. Fixed.
- Flasher Hub-12 V1: WebIF: Files: Added type description for .adf files and ajusted description for .pex files.
- Flasher Hub-4 V1: USB Web server connections could freeze when HTTP traffic caused by web interface was heavy enough. Fixed.
- Flasher Hub-4 V1: WebIF: Files: Added type description for .adf files and ajusted description for .pex files.
- Flasher Portable PLUS V5: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher Portable PLUS V5: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher Portable PLUS V5: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher Portable PLUS V5: WebIF: Added file explorer.
- Flasher Portable PLUS V5: WebIF: Status > Flasher: Caption was "Network configuration" instead of "Flasher configuration" and took up more height than intended. Fixed.
- Flasher Portable PLUS V6: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher Portable PLUS V6: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher Portable PLUS V6: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher Portable PLUS V6: WebIF: Added file explorer.
- Flasher Portable PLUS V6: WebIF: Status > Flasher: Caption was "Network configuration" instead of "Flasher configuration" and took up more height than intended. Fixed.
- Flasher Portable PLUS V7: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher Portable PLUS V7: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher Portable PLUS V7: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher Portable PLUS V7: WebIF: Added file explorer.
- Flasher Portable PLUS V7: WebIF: Status > Flasher: Caption was "Network configuration" instead of "Flasher configuration" and took up more height than intended. Fixed.
- Flasher PRO V5-1: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher PRO V5-1: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher PRO V5-1: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher PRO V5-1: WebIF: Added file explorer.
- Flasher PRO V5: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher PRO V5: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher PRO V5: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher PRO V5: WebIF: Added file explorer.
- Flasher PRO V6: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher PRO V6: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher PRO V6: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher PRO V6: WebIF: Added file explorer.
- Flasher PRO V7: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher PRO V7: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher PRO V7: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher PRO V7: WebIF: Added file explorer.
- Flasher PRO XL V5-1: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher PRO XL V5-1: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher PRO XL V5-1: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher PRO XL V5-1: WebIF: Added file explorer.
- Flasher PRO XL V5: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher PRO XL V5: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher PRO XL V5: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher PRO XL V5: WebIF: Added file explorer.
- Flasher PRO XL V6: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher PRO XL V6: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher PRO XL V6: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher PRO XL V6: WebIF: Added file explorer.
- Flasher PRO XL V7: Apps: Use of the #CANCEL command did not always stop execution of an App. Fixed.
- Flasher PRO XL V7: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- Flasher PRO XL V7: Project management would be assumed active despite the Flasher.ini missing a valid [PROJECT] section. Fixed.
- Flasher PRO XL V7: WebIF: Added file explorer.
- J-Link PRO PoE V6: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link PRO PoE V6: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link PRO PoE V7: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link PRO PoE V7: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link PRO V5-1: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link PRO V5-1: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link PRO V5: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link PRO V5: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link PRO V6: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link PRO V6: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link PRO V7: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link PRO V7: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link ULTRA+ V5-1: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link ULTRA+ V5-1: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link ULTRA+ V5: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link ULTRA+ V5: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link ULTRA+ V6: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link ULTRA+ V6: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Link ULTRA+ V7: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Link ULTRA+ V7: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Trace PRO V3 Cortex: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Trace PRO V3 Cortex: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Trace PRO V3 CortexM: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Trace PRO V3 CortexM: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Trace PRO V3 RISC-V: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Trace PRO V3 RISC-V: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Trace PRO V3: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Trace PRO V3: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Trace PRO V4 Cortex: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Trace PRO V4 Cortex: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Trace PRO V4 CortexM: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Trace PRO V4 CortexM: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Trace PRO V4 RISC-V: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Trace PRO V4 RISC-V: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
- J-Trace PRO V4: Memory throughput for certain operations (e.g. RTT) was reduced due to unintended firmware changes. Introduced in V8.78. Fixed.
- J-Trace PRO V4: TIF pins were not released on debugger disconnect which could for example keep assert of reset pin active (keeping target in reset) outside of debug sessions. Fixed.
GDB Server
- The target.xml generated by the GDB Server contained a duplicate XML tag which caused the target description to be invalid. Introduced in V9.12. Fixed.
RTT
- RTT performance was reduced due to unintended firmware changes with some probes. Introduced in V8.78. Fixed.
RTT Logger
- The application took an unusually long time (about 3 seconds) to fully quit. Fixed.
STR91x Utility
- The application took an unusually long time (about 3 seconds) to quit when command-line argument parsing failed. Fixed.
Version V9.16a (2026-02-06)
Configurator
- Firmware versions were no longer displayed for devices connected via IP. Introduced in V9.14. Fixed
DLL
- Firmware versions were no longer queried from IP devices. Introduced in V9.14. Fixed
Firmware
- Flasher Portable PLUS V5: Firmware could potentially crash during flash programming. Fixed.
Version V9.16 (2026-02-04)
Highlights:
Device Support
- Infineon XMC5000 device series: Added debug & flash programming support (https://kb.segger.com/Infineon_XMC5000).
- Nordic nRF54H20: Added debug & flash programming support (https://kb.segger.com/Nordic_Semiconductor_nRF54H20).
- Nordic nRF54H20: Added debug support for RISC-V cores (FLPR, PPR) (https://kb.segger.com/Nordic_Semiconductor_nRF54H20).
- Tongxin Micro THA8620, THA8820: Added debug and flash programming support (https://kb.segger.com/Tongxin_THA8_Gen_3).
Other changes:
Device Support
- NXP Kinetis KL13: Flash programming could fail due to incorrect RAM size specification. Fixed.
- NXP LPC15xx: Under certain circumstances standalone flash programming could fail. Fixed.
DLL
- RISC-V Debug Spec V1.0: Added support for trigger type "mcontrol6".
- RISC-V Debug Spec V1.0: Hardware breakpoints were not detected properly. Fixed.
Firmware
- Flasher Compact V5: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher Compact V6: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher Compact V7: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher Portable PLUS V5: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher Portable PLUS V6: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher Portable PLUS V7: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher PRO V5-1: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher PRO V5: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher PRO V6: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher PRO V7: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher PRO XL V5-1: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher PRO XL V5: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher PRO XL V6: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
- Flasher PRO XL V7: The target interface was disabled unintentionally, if a USB client was disconnected during programming a U-Flash project. Fixed.
Version V9.14a (2026-01-28)
Firmware
- Minor fixes.
Version V9.14 (2026-01-28)
Highlights:
Device Support
- Alif Semiconductor E4/E6/E8 device family: Extended external OSPI flash support to OSPI0 instance (https://kb.segger.com/AlifSemi_CxEx).
- GigaDevice GD25LX256E: Added flash programming support.
- Microchip SAM9X7: Added external QSPI flash support (https://kb.segger.com/Microchip_SAM9X7).
- Renesas RA8P1 devices series: Added RAMLess flash programming support for SiP flash (https://kb.segger.com/Renesas_RA8P1).
- ST STM32U5 series devices: Added QSPI flash programming support for pin configuration "CLK@PE10_nCS@PE11_D0@PB1_D1@PB0_D2@PA7_D3@PA6" (https://kb.segger.com/ST_STM32U5).
J-Flash SPI
- GigaDevice GD25LX256E: Added flash programming support.
Other changes:
Commander
- Under very special circumstances, when connecting via JTAG and prompted for "Device position in JTAG chain" as well as TIF speed selection and not using defaults, Commander could throw an error or even crash. Fixed.
Device Support
- Added support for some unknown part numbers.
- Infineon PSC3P7xx, PSC3P8xx, PSC3M7xx, PSC3M8xx: Added second flash bank to be used in Dual Bank mode.
- Infineon PSC3P7xx, PSC3P8xx, PSC3M7xx, PSC3M8xx: Only the first 256KB of memory were accessible on 512KB devices. Fixed.
- Infineon PSoC Edge E8: Added SMIF0 secure flash bank.
- Infineon PSoC Edge E8: Removed flash loaders which handled the Extended Boot area.
- Infineon PSoC Edge E8: RRAM flash bank sizes and base addresses were incorrect. Fixed.
- Infineon S6J3360 and S6J3370 series: Flash programming could have failed due to RUN profile update issue. Fixed.
- Renesas RA6M3/RA6T1/S5D3/S5D5/S5D9: Programming/erasing/reading of option-setting memory could fail. Fixed.
- Renesas RA6M3/RA6T1/S5D3/S5D5/S5D9: Under certain circumstances PLL was restored incorrectly. Fixed.
- TI RM48 series: Added a flashloader without automatic ECC generation for internal flash and EEPROM banks (https://kb.segger.com/TI_RM48Lx).
Firmware
- Flasher ARM V5-1: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher ARM V5: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher ARM V6: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher ARM V7: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher ATE2 V1: WebIF: When uploading empty files (0 bytes) to the hub itself, no files were created. Fixed.
- Flasher Hub-12 V1: WebIF: When uploading empty files (0 bytes) to the hub itself, no files were created. Fixed.
- Flasher Hub-4 V1: WebIF: When uploading empty files (0 bytes) to the hub itself, no files were created. Fixed.
- Flasher Portable PLUS V5: Managed projects: Switching from legacy projects to project management did not immediately update the displayed projects. Fixed.
- Flasher Portable PLUS V6: Managed projects: Switching from legacy projects to project management did not immediately update the displayed projects. Fixed.
- Flasher Portable PLUS V7: Managed projects: Switching from legacy projects to project management did not immediately update the displayed projects. Fixed.
- Flasher PRO V5-1: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher PRO V5: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher PRO V6: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher PRO V7: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher PRO XL V5-1: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher PRO XL V5: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher PRO XL V6: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher PRO XL V7: Enabled support for Flasher USB Web Server (https://kb.segger.com/Flasher_USB_Web_Server).
GDB Server
- Added full debugging support for 64-bit address spaces.
Version V9.12 (2026-01-21)
Highlights:
Device Support
- ST STM32MP21x: Added debug support for all device cores. (https://kb.segger.com/ST_STM32MP21x).
- ST STM32U5: Added flash programming support for OCTOSPI2 (https://kb.segger.com/ST_STM32U5).
- ST STM32U5: Added SPI flash programming support for CLK@PF4_nCS@PD3_D0@PF0_D1@PF1_D2@PF2_D3@PF3 pin configuration (https://kb.segger.com/ST_STM32U5).
- TI MSPM33: Added debug and flash programming support (https://kb.segger.com/TI_MSPM33).
Other changes:
Configurator
- The product name of a Flasher PRO XL connected via TCP/IP was displayed as "Flasher PRO". Fixed.
Device Provisioner
- ST STM32U5 series: Unlocking the device (removing RDP protection) could have failed. Fixed.
Device Support
- Added native SWO trace support for Microchip PIC32CX SG6x series. For more information see here: https://kb.segger.com/Microchip_PIC32CX_S6x#SWO
- Nations N32G03x, N32G052, N32G033: Added dialog during connect to J-Link that prompts users to deactivate RDP1 protection level 1 if active.
- NXP KW47: Flash programming for NBU flash via secondary core failed. Fixed.
- NXP MCXW727: Flash programming for NBU flash via secondary core failed. Fixed.
Firmware
- Flasher ARM V5-1: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher ARM V5: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher ARM V6: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher ARM V7: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher Compact V5: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher Compact V5: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher Compact V5: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher Compact V5: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher Compact V6: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher Compact V6: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher Compact V6: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher Compact V6: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher Compact V7: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher Compact V7: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher Compact V7: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher Compact V7: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher Portable PLUS V5: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher Portable PLUS V5: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher Portable PLUS V5: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher Portable PLUS V5: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher Portable PLUS V6: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher Portable PLUS V6: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher Portable PLUS V6: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher Portable PLUS V6: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher Portable PLUS V7: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher Portable PLUS V7: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher Portable PLUS V7: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher Portable PLUS V7: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher PRO V5-1: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher PRO V5-1: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher PRO V5-1: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher PRO V5-1: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher PRO V5: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher PRO V5: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher PRO V5: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher PRO V5: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher PRO V6: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher PRO V6: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher PRO V6: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher PRO V6: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher PRO V7: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher PRO V7: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher PRO V7: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher PRO V7: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher PRO XL V5-1: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher PRO XL V5-1: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher PRO XL V5-1: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher PRO XL V5-1: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher PRO XL V5: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher PRO XL V5: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher PRO XL V5: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher PRO XL V5: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher PRO XL V6: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher PRO XL V6: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher PRO XL V6: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher PRO XL V6: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
- Flasher PRO XL V7: Closing the last DLL connection would close the target interface even if a standalone operation was running. Fixed.
- Flasher PRO XL V7: Flasher SDK: If an error was reported for a flash bank with insufficient heap size, UNI_Init() and UNI_DeInit() would still be called. Fixed.
- Flasher PRO XL V7: Target power supply was potentially deactivated after an operation, even though permanent target power supply was configured. Fixed.
- Flasher PRO XL V7: The use of the #CANCEL command could cause subsequent use of the #AUTO command to fail in certain conditions. Fixed.
Version V9.10 (2026-01-14)
Highlights:
Device Support
- GigaDevice GD32A7: Added debug and flash programming support (https://kb.segger.com/GigaDevice_GD32A7).
- GigaDevice GD32F50x: Added debug and flash programming support (https://kb.segger.com/GigaDevice_GD32F50).
- GigaDevice GD32H75E: Added debug and flash programming support (https://kb.segger.com/GigaDevice_GD32H7).
- ST STM32U5 series devices: Added QSPI flash programming support for pin configuration "CLK@PA3_nCS@PA2_D0@PB1_D1@PB0_D2@PA7_D3@PA6" (https://kb.segger.com/ST_STM32U5).
Other changes:
Device Support
- Infineon WLC1250: Added debug and flash programming support (https://kb.segger.com/Infineon_WLC).
- Infineon WLC1515: Added debug and flash programming support (https://kb.segger.com/Infineon_WLC).
- SiLabs SixG301: Flash loader was missing support for CRC verification. Fixed.
- ST STM32WB5: Increased programming speed of QSPI flashloader.
DLL
- J-Link did not set/clear software breakpoints correctly if the SetEnableFlashbank option was used to disable a flash bank. Introduced in V7.98b. Fixed.
Firmware
- Flasher ARM V5-1: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher ARM V5-1: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher ARM V5: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher ARM V5: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher ARM V6: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher ARM V6: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher ARM V7: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher ARM V7: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher ATE2 V1: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher Compact V5: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher Compact V5: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher Compact V5: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher Compact V6: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher Compact V6: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher Compact V6: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher Compact V7: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher Compact V7: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher Compact V7: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher Hub-12 V1: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher Hub-4 V1: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher Portable PLUS V5: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher Portable PLUS V5: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V5: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher Portable PLUS V6: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher Portable PLUS V6: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V6: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher Portable PLUS V7: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher Portable PLUS V7: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V7: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher PRO V5-1: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher PRO V5-1: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher PRO V5-1: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher PRO V5: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher PRO V5: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher PRO V5: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher PRO V6: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher PRO V6: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher PRO V6: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher PRO V7: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher PRO V7: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher PRO V7: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher PRO XL V5-1: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher PRO XL V5-1: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher PRO XL V5-1: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher PRO XL V5: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher PRO XL V5: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher PRO XL V5: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher PRO XL V6: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher PRO XL V6: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher PRO XL V6: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
- Flasher PRO XL V7: Apps: When mixing printf() and SYS_Reportf() calls, the combination printf-SYS_Reportf-printf could lead to the 1st printf output to be repeated. Fixed.
- Flasher PRO XL V7: Flasher SDK: SYS_LoadUNI() always returned an error when called. Introduced in V8.90. Fixed.
- Flasher PRO XL V7: Moving a file on the filesystem erased its "last modified" timestamp. Fixed.
Version V8.98 (2026-01-07)
Highlights:
Device Support
- Infineon CCG6_CFG device family: Added debug and flash programming support (https://kb.segger.com/Infineon_CCG6_CFP).
- Infineon CCG8_CFG device family: Added debug and flash programming support (https://kb.segger.com/Infineon_CCG8_CFP).
- Linko LKS32MC05x: Added debug and flash programming support (https://kb.segger.com/Linko_LKS32MC05x).
- Nations N32G003: Added debug and flash programming support (https://kb.segger.com/Nations_N32G003).
- Nations N32G033: Added debug and flash programming support (https://kb.segger.com/Nations_N32G03x).
- Nations N32G052: Added debug and flash programming support (https://kb.segger.com/Nations_N32G052).
Other changes:
Commander
- Added 64-bit support for erase command.
- Added 64-bit support for loadfile and loadbin commands.
- verifybin command: 64-bit addresses were not always displayed correctly. Fixed.
Configurator
- Configurator did not show the firmware string on Linux and macOS. Fixed.
Device Support
- NXP MCX N556: Flash programming of internal flash did not work. Fixed.
- Renesas RA6M3/RA6T1/S5D3/S5D5/S5D9: IDCODE programming could fail in rare cases, preventing proper device locking or unlocking. Fixed.
- Renesas S7G2: IDCODE programming could fail in rare cases, preventing proper device locking or unlocking. Fixed.
DLL
- Changed flash programming behavior so that no longer a retry is performed if first flash programming iteration failed. (Log message: "Restarting due to program error (possibly skipped erasure of half-way erased sector)").
Firmware
- Flasher ARM V5-1: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher ARM V5-1: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher ARM V5: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher ARM V5: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher ARM V6: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher ARM V6: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher ARM V7: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher ARM V7: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher Compact V5: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher Compact V5: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher Compact V6: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher Compact V6: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher Compact V7: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher Compact V7: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher Portable PLUS V5: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V5: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher Portable PLUS V6: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V6: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher Portable PLUS V7: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V7: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher PRO V5-1: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher PRO V5-1: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher PRO V5: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher PRO V5: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher PRO V6: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher PRO V6: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
- Flasher PRO V7: Terminal: Command "#AUTO PATCH" did not work anymore. Introduced in V8.90. Fixed.
- Flasher PRO V7: Terminal: Command #AUTO PATCH now returns an error when the selected project consists of multiple jobs, as the expected behavior could be ambiguous.
J-Flash
- Added a warning when SAddr is set for a filetype other than .bin when using -open.
- The warning "This RAM size does not match the default RAM size" could be displayed incorrectly. Fixed.
J-Flash SPI
- Added a warning when SAddr is set for a filetype other than .bin when using -open.
- Added functionality to ignore the second byte of the flash ID during ID verification in the flash settings.
- Flash ID verification could falsely fail when a flash was manually selected from the list. Fixed.
- Manual flash selection could be overridden when multiple flashes shared the same device ID in the flash database. Fixed.
- Manual flash settings were overridden on connect when the device ID was recognized in the flash database. Fixed.
Version V8.96 (2025-12-18)
Highlights:
Device Support
- NXP KW47: Added flash programming support for NBU flash via secondary core.
Trace
- Published out-of-the-box trace example for Alif Semi DK-E7 board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Provisioner
- ST STM32C0 series: Added support for option bytes programming (https://kb.segger.com/ST_STM32C0_Option_Bytes_Programming).
Device Support
- Infineon PSoC Edge E8: Connection with JTAG did not work. Fixed.
- NXP i.MX RT 1180: Memory accesses would cause performance issue due to excessive cache handling. Introduced with V8.69. Fixed.
- NXP MCXE31 series: Added flash programming support for the UTest OTP area (https://kb.segger.com/NXP_MCX_E31#Internal_Flash).
- Renesas RRQ61000: Flashloader for OQSPI flash executed programming operation at slow speed. Introduced in V8.78. Fixed.
- ST SR6G7xx: Flash programming did not work after reset. Fixed.
- ST SR6xxx: Access was not possible when device is not closest to TDO in a JTAG chain. Fixed.
- ST SR6xxx: Removed flash bank 'Boot Code Sector (OTP)' because it was neither readable nor writable.
- ST STM32WL3x series: Added debug and flash programming support for STM32WL30 and STM32WL31.
DLL
- HartSel option was not set for RISC-V architecture when using SWD interface. Fixed.
- J-Link did not handle writes to hardware correctly if the SetEnableFlashbank option was used to disable a flash bank. Introduced in V7.98b. Fixed.
- Monitor Mode Debugging: Added support for ARMv8-M.
Firmware
- Flasher ATE2 V1: WebIF: When using the "Remove all files and folders from all modules" button, a false-negative error could be displayed. Fixed.
- Flasher ATE2 V1: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- Flasher Compact V5: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- Flasher Compact V6: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- Flasher Compact V7: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- Flasher Hub-12 V1: WebIF: When using the "Remove all files and folders from all modules" button, a false-negative error could be displayed. Fixed.
- Flasher Hub-12 V1: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- Flasher Hub-4 V1: WebIF: When using the "Remove all files and folders from all modules" button, a false-negative error could be displayed. Fixed.
- Flasher Hub-4 V1: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- Flasher Portable PLUS V5: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- Flasher Portable PLUS V6: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- Flasher Portable PLUS V7: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- J-Link EDU Mini V1: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link EDU Mini V2: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link EDU/BASE/PLUS V12: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link EDU/BASE/PLUS V12: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- J-Link EDU/BASE/PLUS V13: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link EDU/BASE/PLUS V13: When using the USB Web Server, at some point, the firmware could hang up and reboot itself after some time. Fixed.
- J-Link OB RA4M2-CortexM: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link OB RA4M2-Full: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link OB RA4M2-Renesas: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link PRO PoE V6: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link PRO PoE V7: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link PRO V5-1: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link PRO V5: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link PRO V6: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link PRO V7: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link ULTRA+ V5-1: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link ULTRA+ V5: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link ULTRA+ V6: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link ULTRA+ V7: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link WiFi V2: Added Monitor Mode Debugging support for ARMv8-M.
- J-Link-OB-STM32F072-128KB-CortexM: Added Monitor Mode Debugging support for ARMv8-M.
- J-Trace PRO V3 Cortex: Added Monitor Mode Debugging support for ARMv8-M.
- J-Trace PRO V3 CortexM: Added Monitor Mode Debugging support for ARMv8-M.
- J-Trace PRO V3: Added Monitor Mode Debugging support for ARMv8-M.
- J-Trace PRO V4 Cortex: Added Monitor Mode Debugging support for ARMv8-M.
- J-Trace PRO V4 CortexM: Added Monitor Mode Debugging support for ARMv8-M.
- J-Trace PRO V4: Added Monitor Mode Debugging support for ARMv8-M.
GUI Applications
- Single line text input fields may not have updated correctly under certain circumstances on any OS except Windows 10. Fixed.
J-Flash
- The application could crash when opening the Project Settings in a project with outdated Target RAM settings. Fixed.
- Using J-Link script files with relative paths did not work. Fixed.
J-Scope
- Users can now choose between 4 different draw styles for each symbol.
Version V8.94 (2025-12-10)
Highlights:
Device Support
- AmbiqMicro Apollo510B: Added debug and flash programming support (https://kb.segger.com/AmbiqMicro_Apollo510).
- Analog MAX32657/32658: Added debug and flash programming support (https://kb.segger.com/Analog_MAX32657).
Trace
- Published out-of-the-box trace example for Alif Semi DK-E8 board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- Output for "hwinfo" command now properly labels all values.
Device Provisioner
- Nuvoton M25x series: Added support XOM region programming (https://kb.segger.com/Nuvoton_M25x_XOM_Programming).
- ST STM32H5 series: Added support for regression with password files (https://kb.segger.com/ST_STM32H5_Security_Product_Lifecycle).
Device Support
- ISSI IS25WP01G: Added flash programming support.
- ISSI IS25WP512MJ: Added flash programming support.
- Renesas RA6W1 device family: Added debug and flash programming support (https://kb.segger.com/Renesas_RA6W1).
- Renesas RA6W2 device family: Added debug and flash programming support (https://kb.segger.com/Renesas_RA6W2).
- Silan SC32F5: Added debug and flash programming support for SC32F57768 devices (https://kb.segger.com/Silan_SC32F5).
DLL
- J-Link script files: Added JLINK_FILE_Write() API function call (https://wiki.segger.com/J-Link_script_files#JLINK_FILE_Write.28.29).
- J-Link script files: Return value of JLINK_GetConfigData() API function call did not align with public documentation (https://kb.segger.com/J-Link_script_files#JLINK_GetConfigData.28.29). Fixed.
- Probe selection dialog: Reverted the hiding of gang programmers. Introduced in V8.41.
- Probe selection dialog: When multiple probes or programmers were available and some were gang programmers, the DLL sometimes selected the wrong device because the user's selection wasn't correctly mapped. Introduced in V8.41. Fixed.
Firmware
- Flasher ARM V5-1: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher ARM V5-1: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher ARM V5-1: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher ARM V5: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher ARM V5: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher ARM V5: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher ARM V6: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher ARM V6: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher ARM V6: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher ARM V7: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher ARM V7: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher ARM V7: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher Compact V5: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher Compact V5: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher Compact V5: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher Compact V6: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher Compact V6: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher Compact V6: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher Compact V7: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher Compact V7: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher Compact V7: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V5: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher Portable PLUS V5: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher Portable PLUS V5: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V6: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher Portable PLUS V6: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher Portable PLUS V6: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher Portable PLUS V7: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher Portable PLUS V7: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher Portable PLUS V7: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher PRO V5-1: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher PRO V5-1: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher PRO V5-1: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher PRO V5: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher PRO V5: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher PRO V5: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher PRO V6: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher PRO V6: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher PRO V6: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher PRO V7: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher PRO V7: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher PRO V7: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher PRO XL V5-1: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher PRO XL V5-1: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher PRO XL V5-1: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher PRO XL V5: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher PRO XL V5: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher PRO XL V5: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher PRO XL V6: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher PRO XL V6: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher PRO XL V6: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
- Flasher PRO XL V7: Executing a J-Flash or J-Flash SPI job as part of a managed project in stand-alone mode would fail if the .DAT file name was not the same as the .CFG file name. Fixed.
- Flasher PRO XL V7: Executing a J-Flash SPI job as part of a managed project in stand-alone mode always failed. Fixed.
- Flasher PRO XL V7: Terminal: "#RESULT" returned "#DONE" along with total time for all jobs instead of "#OK" along with job, programming, erasing and verification time summaries. Introduced in V8.90. Fixed.
J-Flash
- Menu action at Menu bar --> File --> "Download serial number file to Flasher" is now disabled when no project file is open.
- The open data file dialog now allows for AXF files.
- When no project was opened, closing the warning dialog shown on Menu bar --> File --> "Download serial number file to Flasher" would crash the application. Fixed.
J-Flash SPI
- ISSI IS25WP01G: Added flash programming support.
- ISSI IS25WP512MJ: Added flash programming support.
- The open data file dialog now allows for AXF files.
J-Run
- Added support for Semihosting special files :tt and :semihosting-features.
J-Scope
- Selecting "Reparse & Match" when a ELF file modification is noticed led to loss of some GUI config data. Fixed.
- Y-Offset of symbols was not properly saved. Fixed.
Version V8.92 (2025-12-03)
Highlights:
Device Support
- Infineon CYUSB308x: Added debug and flash programming support (https://kb.segger.com/Infineon_CYUSB308x).
Other changes:
Device Support
- Alif Semiconductor E4/E6/E8 device family: Added external OSPI flash support (https://kb.segger.com/AlifSemi_CxEx).
- Macronix MX66L51235F, MX25L51245G, MX25L51237G: Under certain circumstances 4-byte mode was handled incorrectly. Fixed.
- NXP iMX8ML: After attaching to the Cortex-M7 core, the PC register always pointed to a fixed address. Fixed.
- Renesas RA8P1: OTP, Configuration Flash flash loader: Restore routine was faulty. Fixed.
- Renesas RA8P1: Subsequent usage of SiP and MRAM flash loader sometimes returned with errors during initialization. Fixed.
- ST STM32H7S3/S7/R3/R7: Under certain circumstances writing external SPI memory via XSPI2 failed. Fixed.
Firmware
- Flasher ARM V5-1: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher ARM V5: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher ARM V6: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher ARM V7: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher Compact V5: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher Compact V5: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher Compact V6: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher Compact V6: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher Compact V7: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher Compact V7: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher Portable PLUS V5: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher Portable PLUS V5: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher Portable PLUS V6: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher Portable PLUS V6: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher Portable PLUS V7: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher Portable PLUS V7: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher PRO V5-1: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher PRO V5-1: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher PRO V5: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher PRO V5: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher PRO V6: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher PRO V6: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
- Flasher PRO V7: Increased performance of app API memcpy() from 256 MB/s to 1 GB/s.
- Flasher PRO V7: Stand-alone mode: RISC-V flash programming via JTAG did not work correctly. Fixed.
Trace
- In rare cases "Unexpected PC error" may appear on target devices with ETMv4 when tracing in program memory that has bit 31 set (e.g. 0x8000_0000). Fixed.
Version V8.90 (2025-11-26)
Highlights:
Device Support
- Nations N32H475: Added debug and flash programming support (https://kb.segger.com/Nations_N32H47x).
- ST STM32WB55xx, STM32WB35xx: Added external QSPI flash support (https://kb.segger.com/ST_STM32WB).
Other changes:
Commander
- The "hwinfo" command now also lists the measured target supply voltage (Pin 19) in all three measurement intervals (1m, 10ms, 100ms) if supported by the connected probe.
Device Support
- GigaDevice GD32E501 device series: Added debug & flash programming support for GD32E501KBQ7, GD32E501KCQ7, GD32E501KEQ7, GD32E501RBL7, GD32E501RCL7 (https://kb.segger.com/GigaDevice_GD32E5).
- Infineon Traveo T2G: Loader for work flash performed blank checks before flash erase operations, which might cause unintended ECC errors. Introduced with V8.62. Fixed.
- NXP Kinetis K32W series: Cortex-M0+ derivatives: "ETBIsPresent" was accidentally set which could lead to issues when doing buffer tracing via MTB. Fixed.
- NXP Kinetis L series: Cortex-M0+ derivatives: "ETBIsPresent" was accidentally set which could lead to issues when doing buffer tracing via MTB. Fixed.
- NXP Kinetis L28 series: Cortex-M0+ derivatives: "ETBIsPresent" was accidentally set which could lead to issues when doing buffer tracing via MTB. Fixed.
- NXP LPC845 series: Cortex-M0+ derivatives: "ETBIsPresent" was accidentally set which could lead to issues when doing buffer tracing via MTB. Fixed.
- NXP MCXC series: Cortex-M0+ derivatives: "ETBIsPresent" was accidentally set which could lead to issues when doing buffer tracing via MTB. Fixed.
- NXP MIMXRT1182: Changed the default flashloader for FlexSPI1 to PortB (https://kb.segger.com/NXP_i.MX_RT1180#QSPI_Flash).
- ONSemi RSL-15: Flasher could not connect to a target in stand-alone mode if it entered low-power mode. Fixed.
- Renesas RA0E1: Added flash programming support for option-setting memory (https://kb.segger.com/Renesas_RA0E1).
- Renesas RA0E2: Added flash programming support for option-setting memory (https://kb.segger.com/Renesas_RA0E2).
- Renesas RA0L1: Added flash programming support for option-setting memory (https://kb.segger.com/Renesas_RA0L1).
- Renesas RZ/N2H: Verify could fail when the cache was enabled. Fixed.
- Renesas RZ/T2H: Verify could fail when the cache was enabled. Fixed.
DLL
- Crash might occur if clear trace event command was called before set trace event command. Fixed.
- Erase range did not work on flash banks that included the highest 32-bit address.
Firmware
- Flasher ARM V5-1: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher ARM V5-1: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher ARM V5-1: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher ARM V5-1: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher ARM V5-1: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher ARM V5-1: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher ARM V5-1: Updated structure of messages in Flasher.log.
- Flasher ARM V5: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher ARM V5: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher ARM V5: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher ARM V5: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher ARM V5: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher ARM V5: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher ARM V5: Updated structure of messages in Flasher.log.
- Flasher ARM V6: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher ARM V6: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher ARM V6: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher ARM V6: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher ARM V6: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher ARM V6: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher ARM V6: Updated structure of messages in Flasher.log.
- Flasher ARM V7: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher ARM V7: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher ARM V7: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher ARM V7: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher ARM V7: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher ARM V7: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher ARM V7: Updated structure of messages in Flasher.log.
- Flasher Compact V5: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher Compact V5: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher Compact V5: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher Compact V5: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher Compact V5: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher Compact V5: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher Compact V5: Updated structure of messages in Flasher.log.
- Flasher Compact V6: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher Compact V6: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher Compact V6: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher Compact V6: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher Compact V6: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher Compact V6: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher Compact V6: Updated structure of messages in Flasher.log.
- Flasher Compact V7: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher Compact V7: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher Compact V7: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher Compact V7: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher Compact V7: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher Compact V7: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher Compact V7: Updated structure of messages in Flasher.log.
- Flasher Portable PLUS V5: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher Portable PLUS V5: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher Portable PLUS V5: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher Portable PLUS V5: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher Portable PLUS V5: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher Portable PLUS V5: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher Portable PLUS V5: The selected project was only saved when the power button was pressed. Fixed.
- Flasher Portable PLUS V5: Updated structure of messages in Flasher.log.
- Flasher Portable PLUS V6: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher Portable PLUS V6: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher Portable PLUS V6: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher Portable PLUS V6: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher Portable PLUS V6: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher Portable PLUS V6: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher Portable PLUS V6: The selected project was only saved when the power button was pressed. Fixed.
- Flasher Portable PLUS V6: Updated structure of messages in Flasher.log.
- Flasher Portable PLUS V7: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher Portable PLUS V7: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher Portable PLUS V7: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher Portable PLUS V7: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher Portable PLUS V7: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher Portable PLUS V7: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher Portable PLUS V7: The selected project was only saved when the power button was pressed. Fixed.
- Flasher Portable PLUS V7: Updated structure of messages in Flasher.log.
- Flasher PRO V5-1: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher PRO V5-1: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher PRO V5-1: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher PRO V5-1: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher PRO V5-1: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher PRO V5-1: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher PRO V5-1: Updated structure of messages in Flasher.log.
- Flasher PRO V5: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher PRO V5: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher PRO V5: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher PRO V5: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher PRO V5: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher PRO V5: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher PRO V5: Updated structure of messages in Flasher.log.
- Flasher PRO V6: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher PRO V6: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher PRO V6: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher PRO V6: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher PRO V6: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher PRO V6: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher PRO V6: Updated structure of messages in Flasher.log.
- Flasher PRO V7: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher PRO V7: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher PRO V7: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher PRO V7: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher PRO V7: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher PRO V7: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- Flasher PRO V7: Updated structure of messages in Flasher.log.
- Flasher PRO XL V5-1: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher PRO XL V5-1: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher PRO XL V5-1: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher PRO XL V5-1: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher PRO XL V5-1: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher PRO XL V5-1: Updated structure of messages in Flasher.log.
- Flasher PRO XL V5: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher PRO XL V5: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher PRO XL V5: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher PRO XL V5: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher PRO XL V5: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher PRO XL V5: Updated structure of messages in Flasher.log.
- Flasher PRO XL V6: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher PRO XL V6: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher PRO XL V6: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher PRO XL V6: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher PRO XL V6: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher PRO XL V6: Updated structure of messages in Flasher.log.
- Flasher PRO XL V7: Implemented support for new project management (https://kb.segger.com/Flasher_-_Working_with_Flasher#Multiple_File_Support).
- Flasher PRO XL V7: Terminal: #NEXTSN command now takes a project name for an optional parameter.
- Flasher PRO XL V7: Terminal: Added command #LISTJOBS (https://kb.segger.com/Flasher_-_Remote_control##LISTJOBS).
- Flasher PRO XL V7: Terminal: Added command #LISTPROJECTS (https://kb.segger.com/Flasher_-_Remote_control##LISTPROJECTS).
- Flasher PRO XL V7: Terminal: The end of programming operation commands (e.g. #AUTO, #PROGRAM, ...) is now indicated by a "#DONE" reply.
- Flasher PRO XL V7: Updated structure of messages in Flasher.log.
- J-Link PRO PoE V6: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link PRO PoE V7: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link PRO V5-1: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link PRO V5: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link PRO V6: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link PRO V7: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link ULTRA+ V5-1: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link ULTRA+ V5: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link ULTRA+ V6: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link ULTRA+ V7: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Link-OB-K22-NordicSemi: Hardware flow control (HWFC) setting is now set to 'Forced on' by default, if no other option has been configured. For more information, see: https://kb.segger.com/Using_J-Link_VCOM_functionality#Hardware_flow_control.
- J-Trace PRO V3 Cortex: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Trace PRO V3 CortexM: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Trace PRO V3 RISC-V: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Trace PRO V3: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Trace PRO V4 Cortex: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Trace PRO V4 CortexM: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Trace PRO V4 RISC-V: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
- J-Trace PRO V4: The continously measured target supply voltage (Pin 19) is now accessible by using the JLINKARM_GetHWInfo() DLL API call. It is available in 1ms, 10ms and 100ms measurement intervals.
Version V8.88 (2025-11-19)
Highlights:
Device Support
- Infineon PSoC Edge E8: Added debug & flash programming support (https://kb.segger.com/PSoC_Edge_E8).
- NXP MCXA18x: Added debug & flash programming support (https://kb.segger.com/NXP_MCX_A).
- NXP MCXA25x: Added debug & flash programming support (https://kb.segger.com/NXP_MCX_A).
- NXP MCXA265/266: Added debug & flash programming support (https://kb.segger.com/NXP_MCX_A).
- NXP MCXA343/344: Added debug & flash programming support (https://kb.segger.com/NXP_MCX_A).
- NXP MCXA365/366: Added debug & flash programming support (https://kb.segger.com/NXP_MCX_A).
Trace
- Published out-of-the-box trace example for Renesas RSK+RZN2L board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Renesas RSK+RZT2M board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Configurator
- Changed application title from "Configuration" to "Configurator".
Device Provisioner
- ST STM32H5 series: Added support for full option-byte keys area (OBK) provisioning (https://kb.segger.com/ST_STM32H5_Security_Product_Lifecycle).
Device Support
- NXP S32K3xx series: Connect would fail if SWD/JTAG pins were re-configured to another function by the target application. Fixed.
DLL
- Erase range did not work on flash banks that included the highest 32-bit address.
- JLinkScript Files: Added CORTEX_M52, CORTEX_M85, STAR_MC2 and STAR_MC3, which were previously missing, to known predefined __constants (https://kb.segger.com/J-Link_script_files#Global_DLL_constants).
Firmware
- Flasher ARM V5-1: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher ARM V5: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher ARM V6: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher ARM V7: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher Compact V5: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher Compact V6: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher Compact V7: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher Portable PLUS V5: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher Portable PLUS V6: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher Portable PLUS V7: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher PRO V5-1: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher PRO V5: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher PRO V6: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher PRO V7: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher PRO XL V5-1: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher PRO XL V5: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher PRO XL V6: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- Flasher PRO XL V7: Having certain applications from the package open (e.g. Configurator, Control Panel, Fasher Deployer) while a standalone operation was in progress could cause communication timeout messages. Fixed.
- J-Link EDU Mini V1: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link EDU Mini V2: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link EDU/BASE/PLUS V12: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link EDU/BASE/PLUS V13: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link OB RA4M2-CortexM: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link OB RA4M2-Full: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link OB RA4M2-Renesas: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link PRO PoE V6: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link PRO PoE V7: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link PRO V5-1: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link PRO V5: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link PRO V6: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link PRO V7: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link ULTRA+ V5-1: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link ULTRA+ V5: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link ULTRA+ V6: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link ULTRA+ V7: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link WiFi V2: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Link-OB-STM32F072-128KB-CortexM: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Trace PRO V3 Cortex: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Trace PRO V3 CortexM: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Trace PRO V3: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Trace PRO V4 Cortex: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Trace PRO V4 CortexM: Monitor Mode Debugging prevents halting core on reset. Fixed.
- J-Trace PRO V4: Monitor Mode Debugging prevents halting core on reset. Fixed.
J-Scope
- Windows process did not terminate after closing main window if previous connection attempt to target was not successful. Fixed.
Version V8.86 (2025-11-12)
Highlights:
Device Support
- NXP i.MX RT1180: Added support for FlexSPI2 Port A (https://kb.segger.com/NXP_i.MX_RT1180).
- NXP i.MX RT1186: Added debug support (https://kb.segger.com/NXP_i.MX_RT1180).
Other changes:
Device Provisioner
- ST STM32H5 series: OBK provisioning could have failed with a timeout error. Fixed.
Device Support
- Renesas R7KA8T2JF, R7JA8T2JR, R7JA8T2JS: Added debug & flash programming support (https://kb.segger.com/Renesas_RA8T2).
- Renesas R8AP1 J-Variants: Added flash programming support for SiP flash via secure or non-secure alias addresses (https://kb.segger.com/Renesas_RA8P1).
- Renesas RA8D2 J-Variants: Added debug & flash programming support (https://kb.segger.com/Renesas_RA8D2).
- Renesas RA8M2 J-Variants: Added debug & flash programming support (https://kb.segger.com/Renesas_RA8M2).
- SiLabs SixG301: Added debug and flash programming support for SixG301xxxxK, SixG301xxxxL, SixG301xxxxW, SixG301xxxxX.
- ST SR6xxx: Autodetection of JTAG chain did not work. Fixed
- ST SR6xxx: BCS was not executed after reset. Fixed.
DLL
- Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
Firmware
- Flasher ARM V5-1: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher ARM V5-1: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher ARM V5: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher ARM V5: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher ARM V6: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher ARM V6: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher ARM V7: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher ARM V7: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher Compact V5: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher Compact V5: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher Compact V6: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher Compact V6: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher Compact V7: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher Compact V7: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher Hub-12 V1: When connecting 24 modules using 2x SEGGER USB Hub-13, not all modules were recognized. Fixed.
- Flasher Hub-4 V1: When connecting 24 modules using 2x SEGGER USB Hub-13, not all modules were recognized. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher Portable PLUS V5: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher Portable PLUS V6: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher Portable PLUS V6: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher Portable PLUS V7: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher Portable PLUS V7: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher PRO V5-1: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher PRO V5: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher PRO V5: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher PRO V6: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher PRO V6: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher PRO V7: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher PRO V7: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher PRO XL V5-1: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher PRO XL V5: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher PRO XL V6: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher PRO XL V6: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- Flasher PRO XL V7: Stand-alone mode: Renesas RX66T: Connect via JTAG could fail under some circumstances. Fixed.
- Flasher PRO XL V7: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link EDU Mini V1: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link EDU Mini V2: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link EDU/BASE/PLUS V12: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link EDU/BASE/PLUS V13: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link PRO PoE V6: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link PRO PoE V7: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link PRO V5-1: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link PRO V5: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link PRO V6: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link PRO V7: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link ULTRA+ V5-1: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link ULTRA+ V5: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link ULTRA+ V6: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link ULTRA+ V7: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link WiFi V2: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link-OB-RA4M2-CortexM: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link-OB-RA4M2-Full: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Link-OB-RA4M2-RISCV: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Trace PRO V3 Cortex: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Trace PRO V3 CortexM: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Trace PRO V3 RISC-V: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Trace PRO V3: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Trace PRO V4 Cortex: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Trace PRO V4 CortexM: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Trace PRO V4 RISC-V: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
- J-Trace PRO V4: Under special circumstances and when using JTAG as the target interface, the firmware could crash when debugging or reading memory from a target. Fixed.
Version V8.84 (2025-11-05)
Highlights:
Device Support
- Alif Semiconductor E4/E6/E8 device family: Added debug and internal flash programming support (https://kb.segger.com/AlifSemi_CxEx).
Other changes:
Commander
- Command "ShowEmuList": When having multiple probes connected, the nickname of the first one in the list was shown for all probes in the list. Fixed.
Device Support
- Infineon XMC4xxx: Under certain circumstances, flash programming failed because the timeout was too short. Fixed.
- Microchip PIC32CM JH: After a reset the core did not immediately halt. Fixed.
- Renesas RX26T: The base address for the Internal Program Flash for the 128 KB and 256 KB versions was incorrect. Fixed.
J-Flash
- Flasher file dialog: Added type description for .adf files and ajusted description for .pex files.
- Removed top section containing info text and product picture of general tab in project settings dialog.
- Text in message box to show serial number and features of the connected Probe/Programmer now selectable to allow for copying the info.
- Updated the license dialog and the prompt if no valid license is found to link to the SEGGER knowledge base.
J-Flash SPI
- Flasher file dialog: Added type description for .adf files and ajusted description for .pex files.
Version V8.82 (2025-10-29)
Highlights:
Device Support
- NXP MCXA355/356: Updated list of supported part numbers.
- XuanTie E907, E906, E902: Added debug support (https://kb.segger.com/XuanTie).
Trace
- Added native pin trace support for Alif Baletto B1 series.
Other changes:
Device Support
- NXP i.MX RT1180: Flash programming failed on Cortex-M33. Introduced in V8.70. Fixed.
- NXP LPC15xx device series: Under certain circumstances Flasher standalone flash programming could fail. Fixed.
- NXP MCXE31 series: Programming did not work correctly. Fixed.
- NXP MCXE316: Code flash bank sizes were incorrect. Fixed.
- ST SR6Px / SR6Gx: Added debug support for Cluster 2 Core 1.
GDB Server
- Cadence Xtensa: Implemented core reset, which can be issued by using the command "monitor reset".
J-Link Package
- Installer: Updated images.
J-Scope
- In certain circumstances, J-Scope could freeze when a project was opened. Fixed.
- Installer: Updated images.
- Selecting the J-Link via serial number or nickname in the Options dialog did not work. Fixed.
- The J-Link connection did not work with the default settings. Fixed.
Version V8.80 (2025-10-22)
Highlights:
Device Support
- NXP S32K374, S32K376, S32K394: Added debug and flash programming support (https://kb.segger.com/NXP_S32K3xx).
- Renesas RA8D2: Added debug and flash programming support (https://kb.segger.com/Renesas_RA8D2).
- Renesas RA8M2: Added debug and flash programming support (https://kb.segger.com/Renesas_RA8M2).
Other changes:
Device Support
- NXP S32K341: Data flash was incorrectly set as 48 KB instead of 88 KB for the HSM FULL_MEM configuration. Fixed.
- Qorvo QPG6200: Extended search range for the RTT control block, now covering RAM address space 0x20000000 - 0x20048000.
- SiLabs EFR32MR21: Added debug and flash programming support for missing part number EFR32MR21AxxxF512.
- SinoWealth SH33F2 series: Flash banks reordered to ascending order by base address.
- SinoWealth SH33F2 series: Protection area now programmed with default values after mass erase.
- Some previously missing generic ARM Cortex device names used by Keil MDK, in the form of "ARMCxxx" (e.g. ARMCM52), are now mapped to the corresponding J-Link DLL names.
- ST Stellar SR6xxx: Attach (skipping reset & ECC RAM init) introduced for Cluster 0 Core 0.
DLL
- Added core support for Cadence Tensilica HiFi 1s/HiFi 5s.
- Flash download now aborts if the J-Link script file functions HandleBeforeFlashProg() or HandleAfterFlashProg() return an error.
Firmware
- J-Link EDU/BASE/PLUS V12: Added support for HiFi 1s/HiFi 5s core.
- J-Link EDU/BASE/PLUS V13: Added support for HiFi 1s/HiFi 5s core.
- J-Link PRO PoE V6: Added support for HiFi 1s/HiFi 5s core.
- J-Link PRO PoE V7: Added support for HiFi 1s/HiFi 5s core.
- J-Link PRO V5-1: Added support for HiFi 1s/HiFi 5s core.
- J-Link PRO V5: Added support for HiFi 1s/HiFi 5s core.
- J-Link PRO V6: Added support for HiFi 1s/HiFi 5s core.
- J-Link PRO V7: Added support for HiFi 1s/HiFi 5s core.
- J-Link ULTRA+ V5-1: Added support for HiFi 1s/HiFi 5s core.
- J-Link ULTRA+ V5: Added support for HiFi 1s/HiFi 5s core.
- J-Link ULTRA+ V6: Added support for HiFi 1s/HiFi 5s core.
- J-Link ULTRA+ V7: Added support for HiFi 1s/HiFi 5s core.
- J-Link WiFi V2: Added support for HiFi 1s/HiFi 5s core.
- J-Link-OB-STM32F072-128KB-CortexM: VCOM: Tx data could sometimes be corrupted when Rx data was simultaneously received. Fixed.
- J-Trace PRO V3: Added support for HiFi 1s/HiFi 5s core.
- J-Trace PRO V4: Added support for HiFi 1s/HiFi 5s core.
Trace
- Under certain circumstances branch packets with context were incorrectly handled on Cortex-R52 targets. Fixed.
Version V8.78 (2025-10-15)
Commander
- Added command to set the nickname (https://kb.segger.com/J-Link_Commander#SetNickname).
- ShowEMUList command now displays the nickname.
Device Provisioner
- ST STM32H5: After device regression, the device sometimes was not responsive. Fixed.
Device Support
- Microchip ATSAMRH71F20x, ATSAMRH707F18A: SWO did not work. Fixed.
- NXP S32K3xx: Resetting did not work on password protected devices via the JTAG interface. Fixed.
- Programming AT25SL0641C with Renesas RRQ61000 resulted in a timeout issue. Fixed.
- Renesas RA2T1 series: Sector erase could affect one additional subsequent sector. Fixed.
- Texas Instruments MSPM0C1103 and MSPM0C1103: NONMAIN programming range is extended to 1 KB.
DLL
- J-Link Commander: "macaddr" command did not work correctly for Flasher ARM V7, Flasher PRO V7 and Flasher PRO XL V7. Fixed.
- Under certain cirumstances custom licenses were not found. Fixed.
Firmware
- Flasher ARM V5-1: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher ARM V5: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher ARM V6: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher ARM V7: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher Compact V5: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher Compact V6: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher Compact V7: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher Portable PLUS V5: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher Portable PLUS V6: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher Portable PLUS V7: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher PRO V5-1: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher PRO V5: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher PRO V6: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher PRO V7: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher PRO XL V5-1: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher PRO XL V5: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher PRO XL V6: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- Flasher PRO XL V7: Under special circumstances, SPI and UART target interface communication could fail. Fixed.
- J-Link-OB-STM32F072-128KB-CortexM: Connecting to certain devices (e.g. Qorvo QM3582x) under some circumstances would cause the firmware to lockup / freeze. Fixed.
- J-Link-OB-STM32F072-Qorvo: Connecting to certain devices (e.g. Qorvo QM3582x) under some circumstances would cause the firmware to lockup / freeze. Fixed.
J-Run
- Added support for the semihosting SYS_EXIT_EXTENDED operation.
J-Scope
- Implemented -USB and -IP command line options to be in line with other J-Link / Flasher applications.
- Made it possible to use spaces between command line option and parameter.
Trace
- When tracing for longer periods of time error message "SWO PC buffer overflow" would appear. Introduced with V8.62. Fixed.
Version V8.76 (2025-10-08)
Highlights:
Device Support
- Microchip PIC32CZxxxxCA80, PIC32CZxxxxCA90: Added flash programming support for the Configuration Flash Memory (CFM) (https://wiki.segger.com/Microchip_PIC32CZ_CA).
- Nordic nRF54LV10A: Added debug & flash programming support (https://kb.segger.com/Nordic_Semiconductor_nRF54Lxx).
- NXP S32K356: Added debug and flash programming support (https://kb.segger.com/NXP_S32K3xx).
Other changes:
Device Provisioner
- ST STM32F2 series: Ported support for unlocking / resetting option bytes from the STM32 Utility to the Device Provisioner (https://kb.segger.com/ST_STM32F2_Option_Bytes_Unlock).
- ST STM32F4 series: Ported support for unlocking / resetting option bytes from the STM32 Utility to the Device Provisioner (https://kb.segger.com/ST_STM32F4_Option_Bytes_Unlock).
Device Support
- Infineon Traveo II (CYT4DN): Added support for some missing part numbers.
- ISSI IS25LP01GJ, IS25WP01GJ: Added flash programming support.
- Microchip PIC32CZxxxxCA80, PIC32CZxxxxCA90: Flash errors were not properly reported. Fixed.
- NXP i.MX RT1060: An active watchdog triggered an unexpected reset during flash operations. Fixed.
- Renesas RX26T: Not the full amount of RAM was specified. Fixed.
- SiLabs EFR32xG23: Added debug and flash programming support for missing part numbers EFR32FG23LxxxF128, EFR32SG23BxxxF512.
- SiLabs EFR32xG24: Added debug and flash programming support for missing part numbers BGM241SD22, EFR32BG24LxxxF768, EFR32MG24AxxxF768, MGM240L022, MGM240LA22, MGM240LD22.
- SiLabs EFR32xG25: Added debug and flash programming support for missing part number EFR32FG25AxxxF256.
- SiLabs EFR32xG27: Added debug and flash programming support for missing part numbers BGM270SC22, MGM270SC22, MGM270SC32.
- ST STM32G0x1x: Internal flash on dual bank devices is now accessed as if it was one continuous bank.
- ST STM32G0x1xC: Added flash programming support for devices in single-bank mode.
- ST STM32U5: Added support for bank swap option during flash programming.
DLL
- Renesas RX26T: Connection to the 48 KB RAM version failed. Fixed.
Firmware
- Flasher Compact V5: Added Flasher web server support via USB (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher Compact V6: Added Flasher web server support via USB (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher Compact V7: Added Flasher web server support via USB (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher Portable PLUS V5: Added Flasher web server support via USB (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher Portable PLUS V6: Added Flasher web server support via USB (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher Portable PLUS V7: Added Flasher web server support via USB (https://kb.segger.com/Flasher_USB_Web_Server).
J-Flash
- Connect and Disconnect action in Target tab in menubar are now combined into one to toggle between the two.
- Downloading files to a gang programmer module did not work. Introduced in V8.68. Fixed.
J-Flash SPI
- Connect and Disconnect action in Target tab in menubar are now combined into one to toggle between the two.
- Downloading files to a gang programmer module did not work. Introduced in V8.68. Fixed.
- ISSI IS25LP01GJ, IS25WP01GJ: Added flash programming support.
Version V8.74a (2025-10-02)
Firmware
- Flasher ARM V5-1: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher ARM V5: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher ARM V6: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher ARM V7: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher Compact V5: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher Compact V6: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher Compact V7: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher Portable PLUS V5: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher Portable PLUS V6: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher Portable PLUS V7: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher PRO V5-1: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher PRO V5: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher PRO V6: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher PRO V7: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher PRO XL V5-1: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher PRO XL V5: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher PRO XL V6: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
- Flasher PRO XL V7: Under special circumstances, PCodes could fail. Introduced in V8.72. Fixed.
Version V8.74 (2025-09-30)
Highlights:
Device Support
- Added support for Arm China STAR-MC3 core.
- Microchip PIC32CZ2051CA70: Added debug and flash programming support (https://kb.segger.com/Microchip_PIC32CZ_CA70).
- Nordic Semiconductor nRF54Lxx: Added flash programming support for UICR flash bank.
- NXP i.MX RT116x device series: Added support for B0 sample (https://kb.segger.com/NXP_i.MX_RT1160).
Other changes:
Device Support
- Macronix MX25V8035F: Added flash programming support.
- Nordic Semiconductor nRF54Lxx: Flash bank "Internal Flash" renamed to "RRAM".
- NXP i.MX RT118x: Added support for FlexSPI Port B.
- Renesas RA4C1: Added device support for R7FA4C1CD (https://kb.segger.com/Renesas_RA4C1).
- Renesas RZ/T2N: Verify could fail when the cache was enabled. Fixed.
- SiLabs EFR32xG22: Added debug and flash programming support for missing part numbers BGM220SC23, EFR32BG22ExxxF512, EFR32BG22LxxxF352, EFR32FG22ExxxF512, EFR32MG22ExxxF512.
DLL
- Added support for Arm China STAR-MC3 core.
Firmware
- Flasher ARM V5-1: Added support for Arm China STAR-MC3 core.
- Flasher ARM V5: Added support for Arm China STAR-MC3 core.
- Flasher ARM V6: Added support for Arm China STAR-MC3 core.
- Flasher ARM V7: Added support for Arm China STAR-MC3 core.
- Flasher Compact V5: Added support for Arm China STAR-MC3 core.
- Flasher Compact V6: Added support for Arm China STAR-MC3 core.
- Flasher Compact V7: Added support for Arm China STAR-MC3 core.
- Flasher Portable PLUS V5: Added support for Arm China STAR-MC3 core.
- Flasher Portable PLUS V6: Added support for Arm China STAR-MC3 core.
- Flasher Portable PLUS V7: Added support for Arm China STAR-MC3 core.
- Flasher PRO V5-1: Added support for Arm China STAR-MC3 core.
- Flasher PRO V5: Added support for Arm China STAR-MC3 core.
- Flasher PRO V6: Added support for Arm China STAR-MC3 core.
- Flasher PRO V7: Added support for Arm China STAR-MC3 core.
- Flasher PRO XL V5-1: Added support for Arm China STAR-MC3 core.
- Flasher PRO XL V5: Added support for Arm China STAR-MC3 core.
- Flasher PRO XL V6: Added support for Arm China STAR-MC3 core.
- Flasher PRO XL V7: Added support for Arm China STAR-MC3 core.
- J-Link EDU Mini V1: Added support for Arm China STAR-MC3 core.
- J-Link EDU Mini V2: Added support for Arm China STAR-MC3 core.
- J-Link EDU/BASE/PLUS V12: Added support for Arm China STAR-MC3 core.
- J-Link EDU/BASE/PLUS V13: Added support for Arm China STAR-MC3 core.
- J-Link PRO PoE V6: Added support for Arm China STAR-MC3 core.
- J-Link PRO PoE V7: Added support for Arm China STAR-MC3 core.
- J-Link PRO V5-1: Added support for Arm China STAR-MC3 core.
- J-Link PRO V5: Added support for Arm China STAR-MC3 core.
- J-Link PRO V6: Added support for Arm China STAR-MC3 core.
- J-Link PRO V7: Added support for Arm China STAR-MC3 core.
- J-Link ULTRA+ V5-1: Added support for Arm China STAR-MC3 core.
- J-Link ULTRA+ V5: Added support for Arm China STAR-MC3 core.
- J-Link ULTRA+ V6: Added support for Arm China STAR-MC3 core.
- J-Link ULTRA+ V7: Added support for Arm China STAR-MC3 core.
- J-Link WiFi V2: Added support for Arm China STAR-MC3 core.
- J-Trace PRO V3 Cortex: Added support for Arm China STAR-MC3 core.
- J-Trace PRO V3 CortexM: Added support for Arm China STAR-MC3 core.
- J-Trace PRO V3: Added support for Arm China STAR-MC3 core.
- J-Trace PRO V4 Cortex: Added support for Arm China STAR-MC3 core.
- J-Trace PRO V4 CortexM: Added support for Arm China STAR-MC3 core.
- J-Trace PRO V4: Added support for Arm China STAR-MC3 core.
GDB Server
- Added support for Arm China STAR-MC3 core.
- Added support for SEGGER specific GDB protocol extension for retrieving information of the connected debug probe (qSeggerJLINK:GetProbeInfo).
J-Flash
- "J-Link Work RAM settings" groupbox in MCU tab of project settings renamed to "Target work RAM settings".
- Erase as part of "Auto" was not skipped on devices that support auto erase (https://kb.segger.com/SEGGER_Flash_Loader#SEGGER_FL_FLAG_SUPPORT_AUTO_ERASE). Fixed.
- Negative return values from the J-Link script file functions HandleBeforeFlashProg() and HandleAfterFlashProg() were not detected. Fixed.
J-Flash SPI
- Macronix MX25V8035F: Added flash programming support.
J-Run
- Added SemiHosting support for RISC-V architecture.
J-Scope
- Added additional information to sampling rate group box in dialog for project settings.
- Added cJTAG to the selectable interfaces in the project settings.
- Filter input in Symbol Selection Dialog relocated above the effected symbol listing.
- The application could crash, under certain circumstances, when parsing an ELF file on Linux. Fixed.
Version V8.72a (2025-09-25)
Firmware
- Flasher Portable PLUS V6: Programming devices via U-Flash using UART interface did not work correctly. Fixed.
Version V8.72 (2025-09-24)
Highlights:
Device Support
- NXP iMXRT106x : Added debug and flash programming support for new parts of device family (https://kb.segger.com/NXP_i.MX_RT1060).
- Texas Instruments MSPM0G51xx: Added debug and flash programming support (https://kb.segger.com/TI_MSPM0G).
- Texas Instruments MSPM0L211x/112x: Added debug and flash programming support (https://kb.segger.com/TI_MSPM0L).
Other changes:
Device Provisioner
- TI CC2340: Added support for password authentication.
Device Support
- Alifsemi E1C series: Programming of some ISSI IS25LX, IS25WX flashes did not work. Introduced in V8.60. Fixed.
- ISSI IS25LX, IS25WX: Added flash programming support for the complete series.
- ISSI IS25LX128, IS25WX128: Flash size was incorrect. Fixed.
- ISSI IS25WJ032F: Quad read did not work beacuse the QE bit was not set correctly. Fixed.
- ST STM32N657: Added flash programming support for OTP memory.
- ST STM32U375xE: Added debug and flash programming support.
- ST STM32U575, STM32U585, STM32U599, STM32U5A9 device series: Added QSPI flash programming support for pin configuration "CLK@PB10_nCS@PE11_D0@PE12_D1@PE13_D2@PE14_D3@PE15" (https://kb.segger.com/ST_STM32U5).
- Texas Instruments MSPM0Gx51x: Flash bank "Internal Flash" renamed to "MAIN".
- Texas Instruments MSPM0Gx51x: Flash erase and programming of first sector failed. Fixed.
Firmware
- Flasher ARM V5-1: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher ARM V5: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher ARM V6: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher ARM V7: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher Compact V5: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher Compact V6: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher Compact V7: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher PRO V5-1: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher PRO V5: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher PRO V6: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher PRO V7: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher PRO XL V5-1: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher PRO XL V5: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher PRO XL V6: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
- Flasher PRO XL V7: The status LED did not stop blinking after programming via the J-Flash application. Introduced in V8.64. Fixed.
J-Flash
- "Addr" in MCU tab in project settings dialog was changed to "Address".
- The J-Link script file functions HandleBeforeFlashProg() and HandleAfterFlashProg() were not called. Fixed.
- When compilation of the user-specified script file failed, multiple misleading errors were reported. Fixed.
J-Flash SPI
- ISSI IS25LX, IS25WX: Added flash programming support for the complete series.
Version V8.70 (2025-09-17)
Highlights:
Device Support
- Espressif ESP32-C5: Added debug support (https://kb.segger.com/Espressif_ESP32-C5).
- Espressif ESP32-P4: Added debug support (https://kb.segger.com/Espressif_ESP32-P4).
- SiliconLabs EFR32xG29: Added debug and flash programming support (https://kb.segger.com/Silicon_Labs_EFR32xG29).
Other changes:
Device Support
- Infineon S6J3360 and S6J3370 series: Flash programming could have failed due to incomplete clock configuration. Fixed.
- NXP iMXRT1180: Implemented XCACHE handling.
- Renesas RA8T2: Added debug and flash programming support (https://kb.segger.com/Renesas_RA8T2).
- Silicon Labs EFM32PG26: Added debug and flash programming support.
DLL
- After J-Link log file reached its max size, empty-lines kept getting appended. Fixed.
Firmware
- J-Link-OB-STM32F072-Qorvo: VCOM: Tx data could sometimes be corrupted when Rx data was simultaneously received. Fixed.
J-Flash
- Actions under View tab in menubar are now checkable to allow for toggling the visibility of the Project information and the Log widget.
- Long names of flash banks were cut off in the GUI. Fixed.
- Script files stored without an absolute path in the project file were searched relative to the J-Flash executable file, instead of the project file. Fixed.
J-Flash SPI
- Actions under View tab in menubar are now checkable to allow for toggling the visibility of the Project information and the Log widget.
Version V8.68 (2025-09-10)
Highlights:
Device Support
- Nations N32H760, N32H762, N32H765: Added debug and flash programming support (https://kb.segger.com/Nations_N32H76x).
- Silergy SA32D series: Added debug and flash programming support (https://kb.segger.com/Silergy_SA32D).
Other changes:
Device Provisioner
- ST STM32WBA: The 'UnlockDevice' operation did not work. Fixed.
- STM32U0: Added check if unlocking device from RDP level 1 to level 0 was succsessful.
- STM32U0: When setting RDP to level 2 via option bytes, script could timeout under certain circumstances. Fixed.
Device Support
- AlifSemi B1/E1C device series: Flash programming did not work with flashes other than ISSI IS25LX128M, IS25WX128M, IS25LX256M, IS25WX256M, IS25LX512M, IS25WX512M, IS25LX01G, IS25WX01G, IS25LX02G, IS25WX02G. Fixed.
- AlifSemi B1/E1C device series: Improved flash operation speed.
- AlifSemi E3/E5/E7 device series: Flash programming did not work with flashes other than ISSI IS25LX128M, IS25WX128M, IS25LX256M, IS25WX256M, IS25LX512M, IS25WX512M, IS25LX01G, IS25WX01G, IS25LX02G, IS25WX02G. Fixed.
- AlifSemi E3/E5/E7 device series: Improved flash operation speed.
- Cmsemicon CMS32H6157: Verify via CRC did not work. Fixed.
- Infineon XMC1100 devices series: Added support for part numbers XMC1100-0128, XMC1100-0200.
- Infineon XMC1400 devices series: Added support for part numbers XMC1401-0032, XMC1401-0200.
- Nuvoton M03x, M05x, M07x, M0Ax, M25x device series: J-Link/Flasher could hang indefinitely while connecting to device. Fixed.
- Nuvoton MINI51x device series: J-Link/Flasher could hang indefinitely while connecting to device. Fixed.
- Nuvoton NANO1xx device series: J-Link/Flasher could hang indefinitely while connecting to device. Fixed.
- Nuvoton NUC029x, NUC1xx, NUC4xx device series: J-Link/Flasher could hang indefinitely while connecting to device. Fixed.
- NXP i.MX25 series: Added debug and flash programming support for MCIMX250.
- Renesas R8AP1 J-Variants: Added flash programming support for SiP flash (https://kb.segger.com/Renesas_RA8P1).
- Renesas R8AP1 K-Variants: Added flash programming support for external SPI flash using OSPI1 (https://kb.segger.com/Renesas_RA8P1).
- Renesas RA0L1: Added debug and flash programming support (https://kb.segger.com/Renesas_RA0L1).
Firmware
- Flasher ARM V5-1: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher ARM V5: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher ARM V6: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher ARM V7: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher Compact V5: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher Compact V6: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher Compact V7: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher Portable PLUS V5: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher Portable PLUS V6: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher Portable PLUS V7: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher PRO V5-1: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher PRO V5: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher PRO V6: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher PRO V7: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher PRO XL V5-1: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher PRO XL V5: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher PRO XL V6: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
- Flasher PRO XL V7: When ShowDatCRCAfterProgramming was enabled in Flasher.ini, the CRC displayed for U-Flash projects (.UNI) was incorrect. Introduced in V8.47. Fixed.
J-Flash
- "BaseAddr" in dialog for creating a new project was changed to "Base Address".
- Extended the "-ip" and "-usb" command line options to allow specifying the gang-programmer modules.
- The "Project Auto-Update" dialog is now shown if the project RAM info does not match the J-Link DLL.
J-Flash SPI
- Extended the "-ip" and "-usb" command line options to allow specifying the gang-programmer modules.
J-Link Package
- Removed RTT sources from package. The sources are now available on the SEGGER GitHub instead (https://github.com/SEGGERMicro/RTT).
Version V8.66 (2025-09-03)
Highlights:
Device Support
- Microchip PIC64GX: Added debug support (https://kb.segger.com/Microchip_PIC64GX).
- Nations N32H785, N32H787: Added debug and flash programming support (https://kb.segger.com/Nations_N32H78x).
- Renesas AT25SL0641C: Added flash programming support.
- Toshiba TB9M001FTG: Added debug and flash programming support (https://kb.segger.com/Toshiba_SmartMCD_Series).
J-Flash SPI
- Renesas AT25SL0641C: Added flash programming support.
Other changes:
CCS Plugin
- The plugin is now build and updated with every release.
Device Support
- GigaDevice GD32H7 flashloader: Clock initialization could get skipped when actually required. Fixed.
- GigaDevice GD32H7 flashloader: Clock was initialized with a higher frequency than the periphery officially supports. Fixed.
- Infineon CY8C4126, CY8C4127, CY8C4128: Improved programming speed.
- Infineon CY8C4146, CY8C4147, CY8C4148, CY8C4149: Improved programming speed.
- Infineon CY8C4546, CY8C4547, CY8C4548: Improved programming speed.
- Infineon CYPD7, CYPM1: Improved programming speed.
- Nordic Semi nRF54L15, nRF91x1 with Flasher in Stand-alone mode: Flash programming did not work without powercycling target. Fixed.
- NXP iMXRT700: Implemented handling for XCACHE0/XCACHE1
- SinoWealth SH32F26: Device name was incorrect. Fixed.
- ST: STM32F1 series: RDP was not reliably detected. Fixed.
Firmware
- Flasher ARM V5-1: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher ARM V5: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher ARM V6: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher ARM V7: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher ATE2 V1: Added support for emUSB-Web (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher Compact V5: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher Compact V6: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher Compact V7: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher Hub-12 V1: Added support for emUSB-Web (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher Hub-4 V1: Added support for emUSB-Web (https://kb.segger.com/Flasher_USB_Web_Server).
- Flasher Portable PLUS V5: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher Portable PLUS V6: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher Portable PLUS V7: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher PRO V5-1: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher PRO V5: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher PRO V6: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher PRO V7: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher PRO XL V5: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher PRO XL V6: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- Flasher PRO XL V7: Stand-alone mode: For J-Flash and U-Flash projects, target power was disabled before tri-stating the target interface. In combination with fixed VTref this could cause current feedback from Flasher TIF to the target and a false-positive "Target power still present after power down" error message. Fixed.
- J-Link PRO PoE V6: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
- J-Link PRO V5-1: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
- J-Link PRO V5: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
- J-Link PRO V6: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
- J-Link PRO V7: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
- J-Link ULTRA+ V5-1: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
- J-Link ULTRA+ V5: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
- J-Link ULTRA+ V6: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
- J-Link ULTRA+ V7: VCOM: Due to a scheduling issue and with baudrates higher than 1 MBaud, Rx data could sometimes be dropped by J-Link. Fixed.
J-Flash
- Removed ? button in "Fill Memory" dialog as it had no function.
J-Flash SPI
- Removed ? button in "Fill Memory" dialog as it had no function.
J-Mem
- Removed ? button in "Fill Memory" dialog as it had no function.
J-Scope
- J-Scope crashed when data was exported to file. Fixed.
- The selected variables were cleared each time the options dialog was closed. Fixed.
- Variable names in the main window were shown with a preceding dot. Fixed.
Manual
- UM08001: Reworked the manual and introduced a getting started guide.
Version V8.64a (2025-09-02)
Trace
- Under special circumstances the instruction and run counters could be incorrect. Introduced in V8.62. Fixed.
Version V8.64 (2025-08-28)
Highlights:
Device Support
- Nuvoton M03x device series: Added flash programming support for LDROM (https://kb.segger.com/Nuvoton_M03x).
- Nuvoton M05x device series: Added flash programming support for LDROM (https://kb.segger.com/Nuvoton_M05x).
- Nuvoton M25x device series: Added flash programming support for LDROM (https://kb.segger.com/Nuvoton_M25x).
- Nuvoton M48x device series: Added flash programming support for LDROM (https://kb.segger.com/Nuvoton_M48x).
- SinoWealth SH33F20 series: Added debug and flash programming support (https://kb.segger.com/SinoWealth_SH33F20).
- SinoWealth SH33F28 series: Added debug and flash programming support (https://kb.segger.com/SinoWealth_SH33F28).
Other changes:
Device Support
- Geehy G32R501 series: Added debug and flash programming support (https://kb.segger.com/Geehy_G32R501xx).
- NXP iMXRT700 device series: Added flash programming support for XSPI0 and XSPI1 in secure address space (https://kb.segger.com/NXP_i.MX_RT700).
- TI MSPM0Lx22x: Flashloader for NONMAIN could timeout under certain circumstances. Fixed.
- TI MSPM0x series: Flashloader could crash if RAM was previously used without ECC or parity checks. Fixed.
Firmware
- Flasher ARM V5-1: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher ARM V5: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher ARM V6: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher ARM V7: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher Compact V5: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher Compact V6: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher Compact V7: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher PRO V5-1: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher PRO V5: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher PRO V6: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher PRO V7: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher PRO XL V5-1: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher PRO XL V5: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher PRO XL V6: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- Flasher PRO XL V7: Status LED blink pattern (Erase, program, verify, ...) from stand-alone mode did not work properly when Flasher was controlled by U-Flash / Flasher Control application. Introduced in V8.58. Fixed.
- J-Link OB CALLIOPE MINI V2.1: Rebuilt firmware to apply fixes from V7.96e regarding drag & drop and macOS Sonoma.
Version V8.62 (2025-08-20)
Highlights:
Trace
- Added native trace pin support for Nordic Semi nRF54L15 series.
Other changes:
Device Support
- AlifSemi B1 device series: Added flash programming support for OSPI SS1 (https://kb.segger.com/AlifSemi_B1).
- AlifSemi E1C device series: Added flash programming support for OSPI SS1 (https://kb.segger.com/AlifSemi_E1C).
- Renesas R7FS5D3, R7FS5D5, R7FS5D9, R7FS7G2: OptMem programming failed. Introduced in V8.28. Fixed.
- Renesas RA4C1: Added debug and flash programming support (https://kb.segger.com/Renesas_RA4C1).
- Renesas RA6M1, RA6M2: OptMem programming failed. Introduced in V8.28. Fixed.
- ST STM32G0xx: Low power & watchdog freeze bits were not set on connect. Fixed.
DLL
- Expanded command string SWOSetHostBufferSize to also be able to overwrite the default buffer size for SWO trace via STRACE API.
- J-Link DLL incorrectly stated that J-Link bootloader version was invalid if the bootloader was compiled in December. Fixed.
GDB Server
- Checksums inside server response packets were being generated with uppercase characters, which caused problems in certain clients (e.g. Embedded Studio). Introduced in V8.42. Fixed.
- Semihosting: Command SYS_FLEN was not working correctly in IOclient mode 2 & 3 (https://kb.segger.com/J-Link_GDB_Server#semihosting_IOClient). Fixed.
- Semihosting: Commands SYS_READ, SYS_SEEK, SYS_ISTTY were not working correctly in IOclient mode 2 & 3 (https://kb.segger.com/J-Link_GDB_Server#semihosting_IOClient). Fixed.
Version V8.60 (2025-08-13)
Highlights:
Device Support
- Macronix MX25L2006E: Added flash programming support.
- Microchip SAMA7D65D4G, SAMA7D65D5M: Added debug support (https://kb.segger.com/Microchip_SAMA7).
- Nations N32H481, N32H482, N32H487, N32H488: Added debug and flash programming support (https://kb.segger.com/Nations_N32H48x).
- Nordic nRF54LM20A: Added debug & flash programming support (https://kb.segger.com/Nordic_Semiconductor_nRF54Lxx).
- TI CC2744R7-Q1: Added debug and flash programming support (https://kb.segger.com/TI_CC2744).
- TI CC2745R7-Q1: Added debug and flash programming support (https://kb.segger.com/TI_CC2745).
J-Flash SPI
- Macronix MX25L2006E: Added flash programming support.
Other changes:
Device Provisioner
- ST STM32F1 series: Ported support for unlocking / resetting option bytes from the STM32 Utility to the Device Provisioner (https://kb.segger.com/ST_STM32F1_Option_Bytes_Unlock).
- ST STM32F3 series: Ported support for unlocking / resetting option bytes from the STM32 Utility to the Device Provisioner (https://kb.segger.com/ST_STM32F3_Option_Bytes_Unlock).
Device Support
- NXP KW47: First connect after POR to core 1 failed. Fixed.
- NXP MCXW727: First connect after POR to core 1 failed. Fixed.
- Renesas RA6M3 QSPI Programming would result in a RAMCode timeout. Introduced in V8.28. Fixed.
- Renesas RA6M3: OptMem programming may fail. Fixed.
- Renesas RZ/N2H, RZ/T2L, RZ/T2H, RZ/T2N, RZ/T2M, RZ/T2ME: Connection to device may not work after reset. Fixed.
- Renesas RZ/N2H, RZ/T2L, RZ/T2H, RZ/T2N, RZ/T2M, RZ/T2ME: Debug authentication may not work after boot stage. Fixed.
- Renesas RZ/N2L: Connection to device may not work after reset. Fixed.
- Renesas RZ/N2L: Debug authentication may not work after boot stage. Fixed.
- Renesas RZ/V2H: Connection to the Cortex-M33 did not work via JTAG. Fixed.
DLL
- SiliconLabs EFx32 series 2 with Flasher in stand-alone mode: Not sector-aligned data were not programmed correctly. Fixed.
Firmware
- Flasher ARM V5-1: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher ARM V5: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher ARM V6: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher ATE2 V1: WebIF: Configuration > Network: The "Click to edit configuration" button did not indicate that administrator mode is required to click it. Fixed.
- Flasher Compact V5: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher Compact V6: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher Compact V7: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher Hub-12 V1: WebIF: Configuration > Network: The "Click to edit configuration" button did not indicate that administrator mode is required to click it. Fixed.
- Flasher Hub-4 V1: WebIF: Configuration > Network: The "Click to edit configuration" button did not indicate that administrator mode is required to click it. Fixed.
- Flasher Portable PLUS V5: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher Portable PLUS V6: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher PRO V5-1: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher PRO V5: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher PRO V6: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher PRO XL V5-1: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher PRO XL V5: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
- Flasher PRO XL V6: Stand-alone programming for certain Cortex-M targets failed if the first AHB-AP found was not usable (e.g. STM32WBA55 device family). Fixed.
J-Flash
- Added warning to project settings dialog for RAM sizes / RAM addresses that do not match the values in the J-Link DLL.
- Data window contents could be modified through the ASCII panel when in simplified mode. Fixed.
RTT Logger
- RTT Logger could only connect to a J-Link if it was specified with the -USB or -IP parameter. Introduced in V8.20. Fixed.
Version V8.58 (2025-08-06)
Highlights:
Device Support
- Infineon PSOC 4100T Plus: Added debug and flash programming support (https://kb.segger.com/Infineon_PSoC_4100T_PLUS).
- NXP MCX N247/526/527/536/537/556: Added debug and flash programming support (https://kb.segger.com/NXP_MCX_N).
Other changes:
Device Provisioner
- ST STM32F0 series: Ported support for unlocking / resetting option bytes from the STM32 Utility to the Device Provisioner (https://kb.segger.com/ST_STM32F0_Option_Bytes_Unlock).
- ST STM32WBA6 series: Added support for option bytes programming and RDP level change (https://kb.segger.com/ST_STM32WBA_Option_Bytes_Programming).
- Toshiba TB9M003: Script file name changed to: PCode_DevPro_Toshiba_TB9M.
Device Support
- Microchip PIC32CX-BZ2 device series: Flash verification for BCFG area could fail. Fixed.
- Microchip PIC32CX-BZ3 device series: Added support for B0 revision.
- Microchip PIC32CX-BZ3 device series: Flash verification for BCFG area could fail. Fixed.
- Microchip PIC32CX-BZ6 device series: Added debug & flash programming support (https://kb.segger.com/Microchip_PIC32CX_BZ6).
- NXP S32K142W: Wrong sector size led to only half of the flash being erased. Fixed.
Manual
- UM8037: Restructured the chapter "Command line options".
STM32 Utility
- Added a warning message about the discontinuation effective 01.01.2026. For more information, see: https://kb.segger.com/J-Link_STM32_Utility#Discontinuation
Version V8.56a (2025-08-01)
DLL
- Linux: In some cases issues occured when working with J-Link via TCP/IP. Introduced in V8.48. Fixed.
Version V8.56 (2025-07-30)
Highlights:
Device Support
- Renesas RZ/G3E: Added debug and flash programming support (https://kb.segger.com/Renesas_RZ/G3E).
Other changes:
Device Support
- GigaDevice GD32E23 series: Added programming support for OTP area.
- Nordic Semiconductor nRF54Lxx: Improved flash programming speed.
Firmware
- Flasher ARM V5-1: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher ARM V5: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher ARM V6: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher ARM V6: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher Compact V5: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher Compact V6: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher Compact V7: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher Portable PLUS V5: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher Portable PLUS V6: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher PRO V5-1: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher PRO V5: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher PRO V6: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher PRO XL V5-1: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher PRO XL V5: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- Flasher PRO XL V6: Return value of SEGGER_FL_Restore() was not evaluated. Fixed.
- J-Link EDU/BASE/PLUS V12: CMSIS-DAP: Added support for atomic commands.
- J-Link EDU/BASE/PLUS V13: CMSIS-DAP: Added support for atomic commands.
- J-Link PRO PoE V6: CMSIS-DAP: Added support for atomic commands.
- J-Link PRO V5-1: CMSIS-DAP: Added support for atomic commands.
- J-Link PRO V5: CMSIS-DAP: Added support for atomic commands.
- J-Link PRO V6: CMSIS-DAP: Added support for atomic commands.
- J-Link PRO V7: CMSIS-DAP: Added support for atomic commands.
- J-Link ULTRA+ V5-1: CMSIS-DAP: Added support for atomic commands.
- J-Link ULTRA+ V5: CMSIS-DAP: Added support for atomic commands.
- J-Link ULTRA+ V6: CMSIS-DAP: Added support for atomic commands.
- J-Link ULTRA+ V7: CMSIS-DAP: Added support for atomic commands.
- J-Link WiFi V2: CMSIS-DAP: Added support for atomic commands.
GDB Server
- Cortex-M: Setting even simple 8/16/32-bit watchpoints on devices that only implement 2 watchpoint units (e.g. NXP MCXA153) did not work. Fixed.
- Endianness was not honored in all cases when logging register values. Fixed.
- RTOS plugin embOS: Task names longer than 32 characters were not correctly supported by the plugin. Fixed.
- RTOS plugin embOS: The GDB Server could crash or the task information could contain erros if a task name crossed a 1kB address boundary in memory. Fixed.
- RTOS plugin: Cortex-M: When reading the PC of a suspended task, it could happen that an odd PC (bit 0 set) was shown. Fixed.
J-Flash
- Return value of SEGGER_FL_Restore was not evaluated. Fixed.
Version V8.54 (2025-07-23)
Highlights:
Device Provisioner
- ST STM32U3 series: Added support for life-cycle management and unlocking device.
- ST STM32U3 series: Added support for option bytes programming.
Device Support
- ESWIN EAM2011: Added flash programming support for PFLASH NVR and DFLASH NVR regions (https://kb.segger.com/ESWIN_EAM2011).
- Nations N32H473: Added debug and flash programming support (https://kb.segger.com/Nations_N32H47x).
- Nations N32H474: Added debug and flash programming support (https://kb.segger.com/Nations_N32H47x).
Other changes:
Device Support
- Nordic Semiconductor nRF54L05: Flash size was wrong. Fixed.
- Nordic Semiconductor nRF54L10: Flash size was wrong. Fixed.
- NordicSemi nRF52 series: Erase operations could fail due to an insufficient timeout. Fixed.
DLL
- Under rare circumstances (e.g. with target MCU Broadcom BCM89107), read/write accesses to peripheral memory region (0x40000000 - 0x5FFFFFFF) could fail due to cacheable attribute. Introduced in V7.86a. Fixed.
Version V8.52 (2025-07-16)
Highlights:
Device Support
- NXP S32K389: Added debug and flash programming support (https://kb.segger.com/NXP_S32K3xx).
- Puya P25Dxxx, P25Txxx, P25Qxxx, PY25Qxxx, PY25Fxxx, PY25Rxxx Series: Added flash programming support.
- Renesas RA4L1 devices series: Added RAMLess flash programming support (https://kb.segger.com/Renesas_RA4L1).
- TI MSPM0C1105/MSPM0C1106: Added debug and flash programming support (https://kb.segger.com/TI_MSPM0C).
J-Flash SPI
- Puya P25Dxxx, P25Txxx, P25Qxxx, PY25Qxxx, PY25Fxxx, PY25Rxxx Series: Added flash programming support.
Other changes:
Device Provisioner
- TI CC2745R10_PG2: Added support for the PG2.1 silicon revision.
- Toshiba TB9M003FG: Key register were not printed after erase or program. Fixed.
- Toshiba TB9M003FG: Script did not abort with error if no device is connected. Fixed.
Device Support
- NXP MCX E24 family: MCXE245 and MCXE246 were wrongfully defined as having a Cortex-M0 core instead of Cortex-M4. Fixed.
- Renesas RZ/A3UL: Under certain circumstances verification after flash programming could fail. Fixed.
- TI CC2745R10_PG2: Added support for the PG2.1 silicon revision.
- Tongxin Micro THA6206: Added debug support for second core (CPU1).
- Tongxin Micro THA6412: Added debug support for additional cores (CPU1-CPU3).
Firmware
- J-Link EDU/BASE/PLUS V12: The J-Link could lose its USB descriptor information after being connected to a PC for a while. Fixed.
- J-Link EDU/BASE/PLUS V13: The J-Link could lose its USB descriptor information after being connected to a PC for a while. Fixed.
- J-Link WiFi V2: The J-Link could lose its USB descriptor information after being connected to a PC for a while. Fixed.
J-Flash
- Target power supply was applied if "Discharge target on disconnect" option was previously checked. Fixed.
RTT Viewer
- Application would crash when reconnecting failed while a RTT read job was still active in the background. Fixed.
- Target connection would disconnect when Configuration Dialog was opened and then closed with cancel. Fixed.
Version V8.50 (2025-07-09)
Highlights:
Device Support
- Renesas RA2T1: Added debug and flash programming support (https://kb.segger.com/Renesas_RA2T1).
Trace
- Added native trace buffer support for Microchip SAMA7D6x and SAMA7G5x series.
Other changes:
Device Support
- TI MSPM0L1105/MSPM0L1106: Flash programming may fail. Fixed.
GDB Server
- RTOS plugin embOS: GDB Server would crash or task information could contain errors when debugging an application with more than 10 tasks. Fixed.
Version V8.48 (2025-07-02)
Highlights:
Device Support
- NXP MCX E24 family: Added debug and flash programming support (https://kb.segger.com/NXP_MCX_E24).
- Analog MAX32662: Added debug and flash programming support.
- Broadcom BCM2712: Added debug support (https://kb.segger.com/Broadcom_BCM2712).
- Renesas RA8P1: Added debug and flash programming support (https://kb.segger.com/Renesas_RA8P1).
Other changes:
Configurator
- Configurator did not show the firmware string on Linux and macOS. Fixed.
Device Support
- Infineon TLE9932: Flash programming and erasing of startup page failed. Fixed.
DLL
- Added support for ARM Cortex-A76.
- Toshiba TMPM037FWUG: Added flash programming support.
Firmware
- Flasher ARM V5-1: Added support for Cortex-A76 core.
- Flasher ARM V5: Added support for Cortex-A76 core.
- Flasher ARM V6: Added support for Cortex-A76 core.
- Flasher Compact V5: Added support for Cortex-A76 core.
- Flasher Compact V6: Added support for Cortex-A76 core.
- Flasher Compact V7: Added support for Cortex-A76 core.
- Flasher Portable PLUS V5: Added support for Cortex-A76 core.
- Flasher Portable PLUS V6: Added support for Cortex-A76 core.
- Flasher PRO V5-1: Added support for Cortex-A76 core.
- Flasher PRO V5: Added support for Cortex-A76 core.
- Flasher PRO V6: Added support for Cortex-A76 core.
- Flasher PRO XL V5-1: Added support for Cortex-A76 core.
- Flasher PRO XL V5: Added support for Cortex-A76 core.
- Flasher PRO XL V6: Added support for Cortex-A76 core.
- J-Link EDU Mini V2: Added support for Cortex-A76 core.
- J-Link EDU/BASE/PLUS V12: Added support for Cortex-A76 core.
- J-Link EDU/BASE/PLUS V13: Added support for Cortex-A76 core.
- J-Link PRO PoE V6: Added support for Cortex-A76 core.
- J-Link PRO V6: Added support for Cortex-A76 core.
- J-Link PRO V7: Added support for Cortex-A76 core.
- J-Link ULTRA+ V6: Added support for Cortex-A76 core.
- J-Link ULTRA+ V7: Added support for Cortex-A76 core.
- J-Link WiFi V2: Added support for Cortex-A76 core.
- J-Trace PRO V3 Cortex: Added support for Cortex-A76 core.
- J-Trace PRO V3: Added support for Cortex-A76 core.
- J-Trace PRO V4 Cortex: Added support for Cortex-A76 core.
- J-Trace PRO V4: Added support for Cortex-A76 core.
GDB Server
- Added RTOS plugin support for ARMv7-A/R based cores (e.g. Cortex-R4F).
J-Flash
- Double clicking a flash bank now opens the flash settings with that flash bank selected.
- When downloading files to the Flasher, the CRC-32 as well as CRC-32C (Castagnoli) are now logged.
J-Flash SPI
- When downloading files to the Flasher, the CRC-32 as well as CRC-32C (Castagnoli) are now logged.
Version V8.46 (2025-06-25)
Highlights:
Device Support
- GigaDevice GD32C2: Added debug and flash programming support (https://kb.segger.com/GigaDevice_GD32C2).
- NXP S32K348: Added debug and flash programming support (https://kb.segger.com/NXP_S32K3xx).
- Renesas RZ/A3M series: Added debug & flash programming support (https://kb.segger.com/Renesas_RZ/A3M).
- SiLabs SiWx917: Added debug and flash programming support (https://kb.segger.com/SiLabs_SiWx917).
- Tongxin Micro THA6 device series: Added flash programming support for DFLASH0 NVR region (https://kb.segger.com/Tongxin_THA6_Gen_2).
- Winbond W25Q10RL: Added flash programming support.
J-Flash SPI
- Winbond W25Q10RL: Added flash programming support.
Other changes:
Commander
- command "setwp": Added for 64-bit address space.
Device Support
- NXP MCX C: Setting of security protection was not possible. Fixed.
- RaspberryPi RP2040: Added loader with no PLL initialization (https://kb.segger.com/Raspberry_Pi_RP2040#QSPI_Flash).
- Renesas RZ/G3E: When cold booting via CA55 and using the JTAG interface, flash programming did not work due to a failing reset. Fixed.
- WIZnet W55RP20: Added loader with no PLL initialization (https://kb.segger.com/WIZnet_W55RP20#QSPI_Flash).
DLL
- ARMv8-A/R (e.g. Cortex-A53): Added support for data events/breakpoints (watchpoints) in 64-bit address space.
- RISC-V: RV64: Added support for data events/breakpoints (watchpoints) in 64-bit address space.
- The DLL would crash with devices that have more than 14 flash banks supported. Introduced in V7.68. Fixed.
Firmware
- Flasher ARM V5-1: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher ARM V5: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher ARM V6: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher Compact V5: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher Compact V6: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher Portable PLUS V5: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher Portable PLUS V6: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher PRO V5-1: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher PRO V5: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher PRO V6: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher PRO XL V5-1: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher PRO XL V5: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- Flasher PRO XL V6: Extended #VERBOSE command to allow override of UNI project output verbosity level (https://kb.segger.com/Flasher_-_Remote_control##VERBOSE).
- J-Link OB Apollo4-CortexM: VCOM hardware flow control pins (CTS, RTS) were swapped. Fixed.
- J-Link-OB-RA4M2-CortexM: FLMD0 pin (P206) is now actively driven low.
- J-Link-OB-RA4M2-Full: FLMD0 pin (P206) is now actively driven low.
- J-Link-OB-RA4M2-Renesas: FLMD0 pin (P206) is now actively driven low.
- J-Link-OB-RA4M2-RISCV: FLMD0 pin (P206) is now actively driven low.
GDB Server
- Setting breakpoints and watchpoints (data breakpoints) in 64-bit address space did not work properly. Fixed.
J-Flash
- Added support for opening and saving TI-TXT (*.txt) data files.
J-Flash SPI
- Added support for opening and saving TI-TXT (*.txt) data files.
J-Flash SPI CL
- Added support for opening and saving TI-TXT (*.txt) data files.
Version V8.44a (2025-06-18)
Version V8.44 (2025-06-18)
Device Provisioner
- ST STM32H5: Output of script version introduced.
- ST STM32H5: Under certain circumstances, reading the device ID when executing a command could fail. Affected commands: "SetDeviceState", "ReadOptionBytes" and "WriteOptionBytes". Fixed.
Firmware
- Flasher ATE2 V1: Terminal: Running the #FCRC command with an invalid path could lead to unexpected behavior (e.g., unresponsive terminal, reboot, ...). Fixed.
- Flasher Hub-12 V1: Terminal: Running the #FCRC command with an invalid path could lead to unexpected behavior (e.g., unresponsive terminal, reboot, ...). Fixed.
- Flasher Hub-4 V1: Terminal: Running the #FCRC command with an invalid path could lead to unexpected behavior (e.g., unresponsive terminal, reboot, ...). Fixed.
Version V8.42 (2025-06-11)
Highlights:
Device Support
- Micron MT35XU512ABA, MT35X256GABA: Added flash programming support.
- Micronas HVC5481G: Added debug & flash programming support (https://kb.segger.com/TDK-Micronas_HVC_5x).
J-Flash SPI
- Micron MT35XU512ABA, MT35X256GABA: Added flash programming support.
Other changes:
Device Support
- Renesas RZ/V2H: The unlock dialog appeared on non-secured devices. Fixed.
- TI CC2340 series: Added support for the PG2.1 silicon revision.
DLL
- Probe selection dialog: Gang programmers are now hidden.
GDB Server
- Monitor command "loadbin" did not work properly for 64-bit addresses (address was cut to 32-bit). Fixed.
- Monitor command "ReadMemAP" did not work properly for 64-bit addresses (address was cut to 32-bit). Fixed.
- Monitor command "reg <Name> (<MemAddr>)" did not work properly for 64-bit addresses (address was cut to 32-bit). Fixed.
- Monitor commands "WriteU8", "WriteU16", "WriteU32", "MemU8", "MemU16", "MemU32" did not work properly for 64-bit addresses (address was cut to 32-bit). Fixed.
- qSeggerSTRACE:read: GDB protocol extension: Improved performance.
- Reading / writing memory in 64-bit address space did not work properly (address was cut to 32-bit). Fixed.
- The GDB Server monitor commands setbp, bdb, bdh and bd for setting breakpoints and watchpoints returned "OK" if an error occurred. Fixed.
Version V8.40 (2025-06-04)
Highlights:
Device Support
- Nordic Semiconductor nRF54L05, nRF54L10: Added debug and flash programming support (https://kb.segger.com/Nordic_Semiconductor_nRF54Lxx).
- ESWIN EAM2011: Added debug & flash programming support (https://kb.segger.com/ESWIN_EAM2011).
- Infineon TLD4020: Added debug and flash programming support (https://kb.segger.com/Infineon_TLD4020).
- NordicSemi nRF52840: Added QSPI flash programming support.
- NXP MCXA345/346/355/356: Added debug and flash programming support (https://kb.segger.com/NXP_MCX_A).
- Renesas RA2L2: Added debug and flash programming support (https://kb.segger.com/Renesas_RA2L2).
Other changes:
Device Provisioner
- ST STM32H523/533: Under certain circumstances, DbgAuthProvision command ends with timeout. Fixed.
Device Support
- AmbiqMicro Apollo5 series: Device ID check was not implemented correctly as an incorrect address was used for reading the ID. Fixed.
- Renesas RZ/V2N: Added IDCode authentication support.
Firmware
- JLink-OB-E1-AlifSemi: VCOM port could become unresponsive in certain cases using the J-Link CDC driver. Fixed.
GDB Server
- Reading SWO data via SEGGER-specific GDB protocol extensions (qSeggerSWO:GetNumBytes, qSeggerSWO:read) did not work reliably. Fixed.
J-Flash
- The connection failed error message now lists a link to the general troubleshooting article of the SEGGER Knowledge Base (KB) and if available also a link to the specific device's KB article.
- When saving Flasher DAT files, the CRC-32 as well as CRC-32C (Castagnoli) are now logged.
J-Flash SPI
- Renesas AT25SF2561C: Flash name was incomplete. Fixed.
- ST M95512: Added flash programming support.
- When saving Flasher DAT files, the CRC-32 as well as CRC-32C (Castagnoli) are now logged.
Registration
- Copying the registration URL to clipboard via context menu did not work. Fixed.
Version V8.38 (2025-05-28)
Highlights:
Device Support
- Geehy APM32E03x8: Added debug and flash programming support (https://kb.segger.com/Geehy_APM32E0xx).
- NXP i.MX RT117x device series: Added support for B0 sample (https://kb.segger.com/NXP_i.MX_RT1170).
- NXP MCX W23 series: Added debug and flash programming support (https://kb.segger.com/NXP_MCX_W).
- TI AM263Px: Added debug support for all device cores. (https://kb.segger.com/TI_AM263Px).
- TI AM263Px: Added QSPI Flash programming support for Cortex R5_0 core.
- TI AM263x: Added debug support for all device cores. (https://kb.segger.com/TI_AM263x).
- TI AM263x: Added QSPI Flash programming support for Cortex R5_0 core.
Other changes:
Device Provisioner
- Linux: J-Link Commander was shipped instead of the Device Provisioner. Introduced in V8.26. Fixed.
- macOS: J-Link Commander was shipped instead of the Device Provisioner. Introduced in V8.26. Fixed.
Device Support
- ISSI IS25LX256/128, IS25WX256/128: Under certain circumstances, flash operation was handled incorrectly. Fixed.
- Macronix MX25R6435F: Flash programming could fail due to a timeout. Fixed.
- Renesas RX: Unified device names between U-Flash and J-Link.
- ST STM32H74x, STM32H75x device series: Added support for pin config "CLK@PF10_nCS@PG6_D0@PD11_D1@PF9_D2@PF7_D3@PA1".
- Tongxin Micro THA6 device series: Added halt timer configuration.
- Tongxin Micro THA6 device series: Added support for debug authentication.
GDB Server
- "IRPre" and "DRPre" were overriden to <0, 0> in certain conditions which could result in a failed connection with certain targets. Fixed.
J-Run
- J-Run would fail to connect to J-Link when executed without the --usb or --ip command line options. Introduced in V8.24. Fixed.
Version V8.36 (2025-05-21)
Highlights:
Device Support
- Geehy APM32F402xB: Added debug and flash programming support (https://kb.segger.com/Geehy_APM32F4xx).
- GigaDevice GD32E503RET7: Added debug and flash programming support (https://kb.segger.com/GigaDevice_GD32E5).
- NXP MCXE series: Added debug and flash programming support (https://kb.segger.com/NXP_MCX_E).
- TI AM261x: Added debug support for all device cores. (https://kb.segger.com/TI_AM261x).
- TI AM261x: Added QSPI Flash programming support for Cortex R5_0 core.
- Winbond W25Q02NW, W25Q02JV: Added flash programming support.
J-Flash SPI
- Winbond W25Q02NW, W25Q02JV: Added flash programming support.
Trace
- Added native trace buffer support for Renesas RZ/A3M device series.
- Published out-of-the-box trace example for Renesas RZ/A3M: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Configurator
- Added a dialog to indicate that a probe/ programmer configuration is being applied.
- Added user interface to enable/ disable the secure partition for Flashers (https://kb.segger.com/Flasher_-_Working_with_Flasher#Authorized_flashing).
Device Provisioner
- When given only a script file name DevPro would no longer automatically search the /Script folder in the install directory. Introduced with V8.26. Fixed.
Device Support
- GigaDevice GD32E50x device series: Under certain circumstances, flash programming did not work. Fix.
- Macronix MX25L25735F, MX25L25645G, MX25L25735E, MX25L25639F, MX25L25635F, MX25L25635E: Under certain circumstances 4-byte mode was handled incorrectly. Fixed.
- ST STM32H730: QSPI flash loader did not handle quad mode correctly. Fixed.
- Tongxin Micro THA6 device series: Added debug & flash programming support for SFLASH (https://kb.segger.com/Tongxin_THA6_Gen_2).
- Tongxin Micro THA6 device series: Added debug support for HSM core (https://kb.segger.com/Tongxin_THA6_Gen_2).
Firmware
- Flasher Hub-12 V1: WebIF: Files: Removing all files and folders from all modules when Status Port was enabled would make web server unresponsive. Fixed.
- Flasher Hub-4 V1: WebIF: Files: Removing all files and folders from all modules when Status Port was enabled would make web server unresponsive. Fixed.
STM32 Utility
- Added ST STM32H7A3/B3.
Version V8.34 (2025-05-14)
Highlights:
Device Support
- Qorvo QM3582x: Added debug and flash programming support (https://kb.segger.com/Qorvo_QM3582x).
- Renesas AT25SF2561/AT25QF2561: Added flash programming support.
- Silicon Labs EFR32xG26 series: Added debug and flash programming support (https://kb.segger.com/Silicon_Labs_EFR32xG26).
J-Flash SPI
- Renesas AT25SF2561/AT25QF2561: Added flash programming support.
Trace
- Added native trace buffer support for ST STM32N6xx device series.
- Published out-of-the-box trace example for ST STM32N657: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Provisioner
- Toshiba TB9M003FG: Password key FCKDAT1/MDEPWD1 register was not set correctly. Fixed.
Device Support
- Renesas RA2L2 series: Sector erase could affect one additional subsequent sector. Fixed.
- TI CC2745 series: Program flash size was incorrectly set as 896KB instead of 928KB. Fixed.
Firmware
- Flasher ARM V5-1: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher ARM V5-1: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher ARM V5: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher ARM V5: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher ARM V6: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher ARM V6: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher Compact V5: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher Compact V5: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher Compact V6: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher Compact V6: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher Compact V7: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher Compact V7: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher Hub-12 V1: Terminal: Added support for #VTREF command (https://kb.segger.com/Flasher_Hub_-_Remote_control#Command_#VTREF).
- Flasher Hub-12 V1: Terminal: Commands to Flasher Hub needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher Hub-12 V1: WebIF: Dashboard > Programming view: If a project file name contained "." (e.g. "My.Project.UNI") it was not selectable in the "Project" column. Fixed.
- Flasher Hub-12 V1: WebIF: Files: Files with ".ini" or ".uni" extension can now be viewed in the web interface.
- Flasher Hub-4 V1: Terminal: Added support for #VTREF command (https://kb.segger.com/Flasher_Hub_-_Remote_control#Command_#VTREF).
- Flasher Hub-4 V1: Terminal: Commands to Flasher Hub needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher Hub-4 V1: WebIF: Dashboard > Programming view: If a project file name contained "." (e.g. "My.Project.UNI") it was not selectable in the "Project" column. Fixed.
- Flasher Hub-4 V1: WebIF: Files: Files with ".ini" or ".uni" extension can now be viewed in the web interface.
- Flasher Portable PLUS V5: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher Portable PLUS V5: Leading zeros in the decimal part of the reference voltage were not displayed. Fixed.
- Flasher Portable PLUS V5: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher Portable PLUS V6: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher Portable PLUS V6: Leading zeros in the decimal part of the reference voltage were not displayed. Fixed.
- Flasher Portable PLUS V6: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher PRO V5-1: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher PRO V5-1: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher PRO V5: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher PRO V5: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher PRO V6: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher PRO V6: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher PRO XL V5-1: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher PRO XL V5-1: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher PRO XL V5: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher PRO XL V5: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
- Flasher PRO XL V6: For some devices (e.g. PIC24EP512GU810), running a programming operation would fail with "#ERR255:PCode internal error". Introduced in V8.26. Fixed.
- Flasher PRO XL V6: Terminal: Commands to Flasher needed to be terminated with either "\r" or "\r\n". Now "\n" can be used, too.
Version V8.32 (2025-05-07)
Highlights:
Device Support
- Allegro A892x: Added debug and flash programming support. (https://kb.segger.com/Allegro_A892x).
- Macronix MX25V1635F: Added flash programming support for SPIFI flash loaders.
- Silergy SA32B1 series: Added debug and flash programming support. (https://kb.segger.com/Silergy_SA32B1).
- Silergy SA32B2 series: Added debug and flash programming support. (https://kb.segger.com/Silergy_SA32B2).
- TI AWR2944: Added debug and flash programming support (https://kb.segger.com/TI_AWR2944).
- TI AWRL1432: Added debug and flash programming support (https://kb.segger.com/TI_AWRL1432).
J-Flash SPI
- Macronix MX25V1635F: Added flash programming support.
Trace
- Published out-of-the-box trace example for RaspberryPi RP2350: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- HPMicro HPM6E8Y, HPM6E84 and HPM6P81: Debug support for second core added.
GDB Server
- GDB Server monitor commands for setting breakpoints and watchpoints only returned "OK" instead of the newly created handle. Fixed.
Trace
- Added native trace pin support for RaspberryPi RP2350.
Version V8.30 (2025-04-30)
Highlights:
Device Support
- Silan SC32F5: Added debug and flash programming support (https://kb.segger.com/Silan_SC32F5).
- ST STM32MP25x: Added debug support for all device cores. (https://kb.segger.com/ST_STM32MP25x).
- ST STM32MP25x: Added QSPI Flash programming support for Cortex A35_0 core.
Other changes:
Device Provisioner
- TI CC2745 series: HSM section size was wrongly set as 128KB instead of 96KB. Fixed.
Device Support
- ArteryTek AT32F40x protect detection did not work correctly. Fixed.
- ArteryTek AT32F43x protect detection did not work correctly. Fixed.
- GigaDevice GD32C1xx, GD32E1xx: Connect with JTAG did not work. Fixed.
- Tongxin Micro THA6 device series: Added flash programming support for PFLASH NVM regions (https://kb.segger.com/Tongxin_THA6_Gen_2).
J-Link Package
- Installer: Windows: Link to release notes was faulty. Fixed.
J-Mem
- Extended the USB S/N input field to also work with a probe / programmer nickname.
- Implemented -USB and -IP command line option to be in line with other J-Link / Flasher applications.
Trace
- Added trace start and stop point support for ETMv4.
Version V8.28 (2025-04-23)
Highlights:
Device Support
- Indie Semiconductor iND87501: Added debug and flash programming support (https://kb.segger.com/IndieSemi_iND875xx).
- NXP iMXRT700 devices series: Added debug and flash programming support (https://kb.segger.com/NXP_i.MX_RT700).
- Renesas DA14533: Added debug and flash programming support (https://kb.segger.com/Renesas_DA1453x).
- Renesas RA0E2: Added debug and flash programming support (https://kb.segger.com/Renesas_RA0E2).
- Renesas RZ/V2N: Added debug and flash programming support. (https://kb.segger.com/Renesas_RZ/V2N).
J-Flash SPI
- Microchip EEPROM: Added support for AT25080 and AT25160.
Trace
- Published out-of-the-box trace example for NXP S32K358: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- Added support for Nations N32L402C8 / N32L402CB / N32L402RB.
- Microchip PIC32CZxxxxCA80, PIC32CZxxxxCA90: Updated list of supported part numbers / device names.
- NXP PN76x: Added explicit erase functionality.
- NXP S32K3xx series: Added programming support for OTP (UTest) area (https://kb.segger.com/NXP_S32K3xx).
- Renesas RA device series: With devices with large internal flashes, ALeRASE command could fail due to a timeout. Fixed.
- ST STM32G0 flash programming and erasing would fail. Introduced in V7.98b. Fixed.
- TI CC2340 series: Erase did not work in certain conditions. Fixed.
DLL
- Under certain circumstances, using the J-Link Command String "SetFlashDLNoRMWThreshold" could cause issues during flash programming. Fixed.
GDB Server
- Loading an application onto a target caused a buffer overflow in certain cases. Fixed.
GDB Server CL
- Loading an application onto a target caused a buffer overflow in certain cases. Fixed.
RTT Viewer
- Extended the USB S/N input field to also work with a probe / programmer nickname.
- Implemented a -USB command line option to be in line with other J-Link / Flasher applications.
- RTT control block vector detection could wrongfully assume a control block in the vector table, causing the connection to fail. Fixed.
Version V8.26 (2025-04-11)
Highlights:
Device Support
- Codasip A730: Added debug support (https://kb.segger.com/Codasip_A730).
- Codasip L110: Added debug support (https://kb.segger.com/Codasip_L110).
- Codasip L31AS: Added debug support (https://kb.segger.com/Codasip_L31).
Other changes:
Device Support
- Infineon TLE99x4: Erase of start up page was disabled due to device restrictions. Erase of start start up page is now enabled.
- ST STM32WLEx, STM32WL5x: Added additional RTT search range to cover the entire SRAM1 and SRAM2.
DLL
- EDBUG converted to J-Link OB were falsely flagged as clones. Fixed.
Firmware
- Flasher ARM V5-1: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher ARM V5: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher ARM V6: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher Compact V5: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher Compact V6: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher Compact V7: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher Portable PLUS V5: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher Portable PLUS V6: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher PRO V5-1: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher PRO V5: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher PRO V6: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher PRO XL V5-1: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher PRO XL V5: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
- Flasher PRO XL V6: NXP LPC553x: Standalone flash programming would fail after power-cycling the Flasher. Fixed.
J-Flash
- Added support for opening .out files.
- Added support for precompiled J-Link Script files (.pex).
Trace
- Native trace pin inits for some ST device would not allow less than 4 data pins. Fixed.
Version V8.24 (2025-03-26)
Highlights:
Device Support
- NXP S32K364: Added debug and flash programming support (https://kb.segger.com/NXP_S32K3xx).
- NXP S32K366: Added debug and flash programming support (https://kb.segger.com/NXP_S32K3xx).
Trace
- Published out-of-the-box trace example for NXP S32K396: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- Microchip ATSAME70 series: Added debug & flash programming support for silicon revision B chips (ATSAME70xxxB).
- ONSemiconductor RSL10: Programming of NVR flash did not work properly. Fixed.
Firmware
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Modules: Added user interface for programmer registration.
- Flasher Hub-4 V1: WebIF: Configuration > Flasher Modules: Added user interface for programmer registration.
GDB Server
- Implemented -USB and -IP command line options to be in line with other J-Link / Flasher applications.
GDB Server CL
- Implemented -USB and -IP command line options to be in line with other J-Link / Flasher applications.
J-Flash
- When opening data files, the size of data is now logged in decimal as well as hexadecimal notation.
- When opening or merging data files, the CRC-32 as well as CRC-32C (Castagnoli) are now logged.
J-Flash SPI
- When opening data files, the size of data is now logged in decimal as well as hexadecimal notation.
- When opening or merging data files, the CRC-32 as well as CRC-32C (Castagnoli) are now logged.
J-Run
- Extended the command line option '-USB' to also work with a probe / programmer nickname.
Version V8.22 (2025-03-19)
Highlights:
Device Provisioner
- Toshiba TB9M003FG: Added support for password key programming.
Device Support
- Renesas AT25EU0161A: Added flash programming support.
J-Flash SPI
- Renesas AT25EU0161A: Added flash programming support.
Other changes:
Device Support
- Infineon TLE988x/TLE989x device series: Reset did not work properly for AK design variant. Fixed.
- Renesas Synergy: Flash programming led to an interrupt when the Stack Pointer Monitoring was enabled. Fixed.
- Toshiba TB9M003FG: ANAC Trimming was not executed after reset. Fixed.
J-Flash
- Under certain circumstances the 32 bit version of J-Flash could crash. Fixed.
J-Flash SPI
- Programming of the Infineon S25FL256L did not work. Fixed.
Remote Server CL
- Remote Server CL would output an error saying it could not select the J-Link with nickname (blank) via USB if the -USB parameter wasn't used. Introduced in V8.20. Fixed.
Version V8.20 (2025-03-12)
Highlights:
Device Support
- Macronix MX25R2035F: Added flash programming support for SPIFI flash loaders.
- Renesas DA1453x: Added debug and flash programming support (https://kb.segger.com/Renesas_DA1453x).
- Tongxin Mico THA6 device series: Added debug & flash programming support (https://kb.segger.com/Tongxin_THA6_Gen_2).
J-Flash SPI
- Macronix MX25R2035F: Added flash programming support.
Other changes:
Commander
- Linux: Connecting to a Flasher Hub-4 or Flasher Hub-12 via USB did not work. Fixed.
- macOS: Connecting to a Flasher Hub-4 or Flasher Hub-12 via USB did not work. Fixed.
Configurator
- Linux: Connecting to a Flasher Hub-4 or Flasher Hub-12 via USB did not work. Fixed.
- macOS: Connecting to a Flasher Hub-4 or Flasher Hub-12 via USB did not work. Fixed.
Device Support
- HPMicro HPM device series: Updated third party device support package.
- HPMicro HPM5E device series: Added debug & falsh programming support (https://kb.segger.com/HPMicro_HPM5E).
- HPMicro HPM6P device series: Added debug & falsh programming support (https://kb.segger.com/HPMicro_HPM6P).
- NXP LPC55x3x device series: Under certain circumstances, Flasher standalone programming did not work. Fixed.
- Renesas RA4M2: Added support for pin config "CLK@P100_nCS@P207_D0@P102_D1@P101_D2@P104_D3@P103".
- Renesas RA6M5: Added support for pin config "CLK@P100_nCS@P207_D0@P102_D1@P101_D2@P104_D3@P103".
- Silan SC32F57256: Programming could fail in some cases. Fixed.
Firmware
- Flasher ARM V5-1: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher ARM V5: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher ARM V6: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher Compact V5: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher Compact V6: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher Compact V7: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher Portable PLUS V5: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher Portable PLUS V6: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher PRO V5-1: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher PRO V5: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher PRO V6: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher PRO XL V5-1: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher PRO XL V5: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
- Flasher PRO XL V6: #START and #READ would always fail with an error. Introduced in V8.18. Fixed.
J-Flash
- Extended the command line option '-USB' to also work with a probe / programmer nickname.
- Linux: Connecting to a Flasher Hub-4 or Flasher Hub-12 via USB did not work. Fixed.
- macOS: Connecting to a Flasher Hub-4 or Flasher Hub-12 via USB did not work. Fixed.
J-Flash SPI
- An error occurred when starting an operation after selecting UseQuadMode and then switching to auto-detect mode. Fixed.
- Extended the command line option '-USB' to also work with a probe / programmer nickname.
- Linux: Connecting to a Flasher Hub-4 or Flasher Hub-12 via USB did not work. Fixed.
- macOS: Connecting to a Flasher Hub-4 or Flasher Hub-12 via USB did not work. Fixed.
J-Flash SPI CL
- Extended the command line option '-USB' to also work with a probe / programmer nickname.
- Unified -USB and -IP command line options to be in line with other J-Link / Flasher applications.
J-Run
- Added support for semihosting file I/O operations. See https://kb.segger.com/J-Run.
- Added the option to redirect RTT channels over TCP. See https://kb.segger.com/J-Run.
- Added the option to specify a string to be send to the target either immediately or when the target outputs a specified trigger string. See https://kb.segger.com/J-Run.
- Added the option to specify wildcard strings, which, when read in the targets output, will cause J-Run to exit immediately with code 0 or -1.
- If the target application requested arguments via RTT, but J-Run was started without --args, J-Run would crash. Fixed.
- J-Run did not pass the exit code that a target sent with SEGGER_SEMIHOST_Exit(Exitcode) to the OS. Fixed.
J-Scope
- Added the option to start sampling without resetting the target in RTT-Plus mode.
JTAG Load
- Removed '-SelectEmuBySN' parameter as same functionality is implemented by '-USB' parameter. Also added more information to 'Help (?)' text.
Remote Server
- Implemented -USB and -IP command line options to be in line with other J-Link / Flasher applications.
Remote Server CL
- Implemented -USB and -IP command line options to be in line with other J-Link / Flasher applications.
RTT Logger
- Extended the command line option '-USB' to also work with a probe / programmer nickname.
SWO Viewer
- Extended the command line option '-USB' to also work with a probe / programmer nickname.
SWO Viewer CL
- Extended the command line option '-USB' to also work with a probe / programmer nickname.
Version V8.18 (2025-03-05)
Highlights:
Device Support
- Gaisler NOEL-V: Added debug support (https://kb.segger.com/Gaisler_NOEL-V).
- Silan SC32F57256: Added debug and flash programming support (https://kb.segger.com/Silan_SC32F5).
- TI MSPM0H: Added debug and flash programming support (https://kb.segger.com/TI_MSPM0H).
Trace
- Published out-of-the-box trace example for Ambiq Apollo4 Plus: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Infineon PSoC C3M5: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for ST STM32WBA65: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- Exit on error option did not work for errors during autoconnect. Fixed.
Device Support
- Analog ADuCM3027 / ADuCM3029: Wrong flash size was configured for device. Fixed.
- Analog ADuCM330: Erasing data flash using chip erase also erased program flash and vice versa even if not selected. Fixed.
- ArteryTek AT32A42x: Protect detection did not work correctly. Fixed.
- ArteryTek AT32F40x: Protect detection did not work correctly. Fixed.
- ArteryTek AT32F42x: Protect detection did not work correctly. Fixed.
- ArteryTek AT32M41x: Protect detection did not work correctly. Fixed.
- Nordic Semiconductor nRF54L15: Programming sectors filled with the erase value could lead to verify errors. Fixed.
- ST STM32U3: Added flash unlock functionality in case active read and/or write protection is detected.
- ST STM32U3: Added out of the box SWO support.
DLL
- Software breakpoints did not work for 64 bit addresses. Fixed.
- Under certain circumstances, the DLL could crash when using older J-Links. Fixed.
J-Scope
- New project dialog: TCP/IP input field was not accessible after losing focus. Fixed.
Version V8.16 (2025-02-26)
Highlights:
Device Support
- Infineon TLE99xx: Added debug and flash programming support (https://kb.segger.com/Infineon_TLE99xx).
- ST STM32U3: Added debug and flash programming support (https://kb.segger.com/ST_STM32U3).
- ZhiXin Z20K14xMS: Added debug and flash programming support (https://kb.segger.com/ZhiXin_Z20K14xMS).
Other changes:
Device Support
- AlifSemi E5/E7 device series: JLink WorkRAM was not accessible for Cortex-A32 devices. Introduced in V7.96l. Fixed.
- Microchip PIC32MK GPG/MCJ: A second boot sector was included in the address map that does not exist at all. Fixed.
- Microchip PIC32MK: If any watchdog was enabled, flash programming could fail. Fixed.
- NXP LPC54 device series: Ported flash loader to SFL.
- NXP LPC54016/LPC54018: Standalone flash programming did not work. Fixed.
- NXP S32K3xx: Under certain circumstances, the Cortex-M7_2 and Cortex-M7_3 core did not boot. Fixed.
- ST STM32H7Axx/STM32H7Bxx device series: Added QSPI flash programming support for pin config "CLK@PF10_nCS@PG6_D0@PF8_D1@PF9_D2@PE2_D3@PF6_D4@NA_D5@NA_D6@NA_D7@NA".
DLL
- Watchpoints did not work on Cortex-A32. Fixed.
Firmware
- Flasher ARM V5-1: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher ARM V5: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher ARM V6: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher Compact V5: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher Compact V6: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher Compact V7: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher Portable PLUS V5: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher Portable PLUS V6: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher PRO V5-1: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher PRO V5: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher PRO V6: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher PRO XL V5-1: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher PRO XL V5: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
- Flasher PRO XL V6: Some flash loaders have incorrectly failed with "ERR255:PCode mem access violation". Introduced in V8.12d. Fixed.
Version V8.14 (2025-02-21)
Highlights:
Device Support
- Renesas RX671: Added debug and flash programming support (https://kb.segger.com/Renesas_RX671).
Other changes:
Commander
- Added option to select a device via "device ?" command before target connection has been established.
Device Support
- AlifSemi Ensemble E7: Programming did not work due to failing reset. Introduced in V7.92j. Fixed.
- ST STM32L4P5xE: Flash size was set to 1MB instead of correct value of 512 KB. Fixed.
- TI CC2340: Under certain circumstances, chip erase was called multiple times. Fixed.
- TI CC2745: Under certain circumstances, chip erase was called multiple times. This could result in erasure of the HSM section independent of the retainSelMainSectors option. Fixed.
Firmware
- J-Link EDU Mini V1: TI CC2340: Flash programming did not work. Introduced in V8.12d. Fixed.
- J-Link EDU Mini V2: TI CC2340: Flash programming did not work. Introduced in V8.12d. Fixed.
- J-Link EDU/BASE/PLUS V11: TI CC2340: Flash programming did not work. Introduced in V8.12d. Fixed.
- J-Link EDU/BASE/PLUS V12: TI CC2340: Flash programming did not work. Introduced in V8.12d. Fixed.
- J-Link EDU/BASE/PLUS V13: TI CC2340: Flash programming did not work. Introduced in V8.12d. Fixed.
- J-Link WiFi V1: TI CC2340: Flash programming did not work. Introduced in V8.12d. Fixed.
- J-Link WiFi V2: TI CC2340: Flash programming did not work. Introduced in V8.12d. Fixed.
Version V8.12g (2025-02-19)
Highlights:
Device Support
- Nordic Semiconductor nRF54L15: Added debug support for RISC-V core (https://kb.segger.com/Nordic_Semiconductor_nRF54Lxx).
- NXP i.MX 6DP (DualPlus): Added debug support (https://kb.segger.com/NXP_i.MX_6DP)
- NXP i.MX 6QP (QuadPlus): Added debug support (https://kb.segger.com/NXP_i.MX_6QP)
- NXP i.MX 6ULZ: Added debug support and flash programming support (https://kb.segger.com/NXP_i.MX_6ULZ)
- NXP i.MX 7S: Added debug support and flash programming support (https://kb.segger.com/NXP_i.MX_7S)
- NXP i.MX 8ULP: Added debug support (https://kb.segger.com/NXP_i.MX_8ULP)
- NXP KW47: Added debug and flash programming support (https://kb.segger.com/NXP_KW47"
- NXP MCXW727: Added debug support for second (radio) core.
- Renesas RA4L1: Added debug and flash programming support (https://kb.segger.com/Renesas_RA4L13)
- ST STM32WBA62/63/64/65: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WBA).
- Toshiba TB9M003FG: Added debug and flash programming support (https://kb.segger.com/Toshiba_SmartMCD Series"
- ZhiXin Z20K11xM: Added debug and flash programming support (https://kb.segger.com/ZhiXin_Z20K11xM).
- ZhiXin Z20K11xN: Added debug and flash programming support (https://kb.segger.com/ZhiXin_Z20K11xN).
- ZhiXin Z20K14xMC: Added debug and flash programming support (https://kb.segger.com/ZhiXin_Z20K14xMC).
Other changes:
Device Support
- AmbiqMicro Apollo3 Blue: Added support for a new part number (AMA3B1KK-KQR).
- AmbiqMicro Apollo5: Erase of entire memory could fail. Fixed.
- NXP i.MX family: Updated list of supported part numbers / device names.
- ZhiXin Z20K14xMS: Added debug and flash programming support (https://kb.segger.com/ZhiXin_Z20K14xMS).
Firmware
- Flasher ARM V5-1: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher ARM V5: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher ARM V6: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher Compact V5: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher Compact V6: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher Portable PLUS V5: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher Portable PLUS V6: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher PRO V5-1: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher PRO V5: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher PRO V6: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher PRO XL V5-1: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher PRO XL V5: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
- Flasher PRO XL V6: Under some circumstances, error messages that occured during an operation for a .UNI project were output amidst other messages instead of at the end of the operation. Fixed.
Version V8.12f (2025-02-12)
Highlights:
Device Support
- NXP iMX95 (Cortex-M33): Added flash programming support for external QSPI NOR flash.
- Renesas RA8E2: Added debug and flash programming support (https://kb.segger.com/Renesas_RA8E2)
Other changes:
Device Support
- Nuvoton M031x / M032x / M0518x / M0564x / M071x / M0A2x / M25x: Added security lock detection and PCode unlocking sequence (chip erase).
- Renesas RZ/A3UL: Added background memory access support (used by e.g. RTT).
DLL
- RISC-V: RISC-V behind CoreSight DAP + AHB-AP: Added support for command string "CORESIGHT_SetAHBAP_SecOptOverride" to allow override of HPROT[4:0] + SProt flags used by J-Link.
- The DLL will now try to find the RTT control block address in the vector table.
Firmware
- Flasher Compact V5: Rebuilt firmware with RISC-V module version 5.
- Flasher Compact V6: Rebuilt firmware with RISC-V module version 5.
- Flasher Compact V7: Rebuilt firmware with RISC-V module version 5.
- Flasher Portable PLUS V5: Rebuilt firmware with RISC-V module version 5.
- Flasher Portable PLUS V6: Rebuilt firmware with RISC-V module version 5.
- Flasher PRO V5-1: Rebuilt firmware with RISC-V module version 5.
- Flasher PRO V5: Rebuilt firmware with RISC-V module version 5.
- Flasher PRO V6: Rebuilt firmware with RISC-V module version 5.
- Flasher PRO XL V5-1: Rebuilt firmware with RISC-V module version 5.
- Flasher PRO XL V5: Rebuilt firmware with RISC-V module version 5.
- Flasher PRO XL V6: Rebuilt firmware with RISC-V module version 5.
- J-Link EDU Mini V1: Rebuilt firmware with RISC-V module version 5.
- J-Link EDU Mini V2: Rebuilt firmware with RISC-V module version 5.
- J-Link EDU/BASE/PLUS V11: Rebuilt firmware with RISC-V module version 5.
- J-Link EDU/BASE/PLUS V12: Rebuilt firmware with RISC-V module version 5.
- J-Link EDU/BASE/PLUS V13: Rebuilt firmware with RISC-V module version 5.
- J-Link PRO PoE V6: Rebuilt firmware with RISC-V module version 5.
- J-Link PRO V5-1: Rebuilt firmware with RISC-V module version 5.
- J-Link PRO V5: Rebuilt firmware with RISC-V module version 5.
- J-Link PRO V6: Rebuilt firmware with RISC-V module version 5.
- J-Link PRO V7: Rebuilt firmware with RISC-V module version 5.
- J-Link ULTRA+ V5-1: Rebuilt firmware with RISC-V module version 5.
- J-Link ULTRA+ V5: Rebuilt firmware with RISC-V module version 5.
- J-Link ULTRA+ V6: Rebuilt firmware with RISC-V module version 5.
- J-Link ULTRA+ V7: Rebuilt firmware with RISC-V module version 5.
- J-Link WiFi V1: Rebuilt firmware with RISC-V module version 5.
- J-Link WiFi V2: Rebuilt firmware with RISC-V module version 5.
- J-Link-OB-K22-RISCV: Rebuilt firmware with RISC-V module version 5.
- J-Link-OB-nRF5340-NordicSemi: Rebuilt firmware with RISC-V module version 5.
- J-Link-OB-RA4M2-Full: Rebuilt firmware with RISC-V module version 5.
- J-Trace PRO V3 RISC-V: Rebuilt firmware with RISC-V module version 5.
- J-Trace PRO V3: Rebuilt firmware with RISC-V module version 5.
- J-Trace PRO V4 RISC-V: Rebuilt firmware with RISC-V module version 5.
- J-Trace PRO V4: Rebuilt firmware with RISC-V module version 5.
- RISC-V: Increased module version to 5: RISC-V behind CoreSight DAP + AHB-AP: Added support for command string "CORESIGHT_SetAHBAP_SecOptOverride" to allow override of HPROT[4:0] + SProt flags used by J-Link.
GDB Server
- Added support for Cortex-R52 core specific c6 registers.
J-Flash
- Improved feedback on errors for init/exit steps so that the step number is included in the error message.
- Renamed "selected sectors" erase option in production programming settings to "affected sectors" to better convey the actual behaviour behind the setting.
RTT
- SEGGER_RTT.h: GNUC / CLANG: File did not compile (introduced V8.10k). Fixed.
Version V8.12e (2025-02-05)
Highlights:
Device Provisioner
- ST STM32H5 series: Added support for Debug Authentication with certificate (TrustZone enabled).
- ST STM32H5 series: Added support for option bytes programming.
Device Support
- Indie Semiconductor iND83205: Added debug and flash programming support (https://kb.segger.com/IndieSemi_iND832xx).
- Indie Semiconductor iND83212: Added debug and flash programming support (https://kb.segger.com/IndieSemi_iND832xx).
- ISSI IS25LX064, IS25LX032: Added flash programming support.
- Microchip PIC32CK: Added debug and flash programming support (https://kb.segger.com/Microchip_PIC32CK).
- Microchip PIC32CM SG00/GC00: Added debug and flash programming support (https://kb.segger.com/Microchip_PIC32CM_SG00_GC00).
- NXP S32K144H: Added debug and flash programming support (https://wiki.segger.com/S32Kxxx)
- NXP S32K144U: Added debug and flash programming support (https://wiki.segger.com/S32Kxxx)
- ST STM32C091xx: Added debug and flash programming support (https://kb.segger.com/ST_STM32C0).
- ST STM32C092xx: Added debug and flash programming support (https://kb.segger.com/ST_STM32C0).
J-Flash SPI
- ISSI IS25LX064, IS25LX032: Added flash programming support.
Other changes:
Device Provisioner
- Added command line option -Module. (https://kb.segger.com/Device_Provisioner#Usage)
- Added log output of probe S/N and firmware info.
Device Support
- Microchip PIC32CZxxxxCA80, PIC32CZxxxxCA90: Connection to target may fail if devices flash memory is empty. Fixed.
- NXP Kinetis K8x: QSPI flash loader was using a non-standard endianness setting (32Bit LE) instead of standard byte ordering (64Bit LE). Fixed.
- Renesas N2H, T2H: Flash programming for Cortex-R52_1 core would fail during verification phase. Introduced with V8.12b. Fixed.
- Renesas N2H, T2H: Reset did not work when booting from Cortex-A55_0 core. Fixed.
- Renesas RZ/N2H: Added debug and flash programming support (https://kb.segger.com/Renesas_RZ/N2H).
- TI MSPM0Gx51x: Programming of NONMAIN region failed. Fixed.
DLL
- J-Link command string "SuppressGUI" now additionally sets the message box timeout to the preset timeout for batch mode or resets it to the default value.
- Modified J-Link command string "SuppressGUI" to take an optional argument to choose between suppressing or enabling GUI.
Firmware
- Flasher ARM V5-1: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher ARM V5: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher ARM V6: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher Compact V5: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher Compact V6: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher Compact V7: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher Portable PLUS V5: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher Portable PLUS V6: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher PRO V5-1: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher PRO V5: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher PRO V6: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher PRO XL V5-1: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher PRO XL V5: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- Flasher PRO XL V6: Microchip ATmega: Under very special circumstances, Flasher firmware could lockup / freeze during programming step. Introduced in V8.12b. Fixed.
- J-Link-OB-Apollo4-CortexM: SWO: A long pulse on SWO pin could lead to SWO transfers breaking. Fixed.
Trace
- Added unhandled Armv7 instruction corner cases to analyzer.
Version V8.12d (2025-01-29)
Highlights:
Device Support
- NXP MCXA20: Added debug and flash programming support (https://kb.segger.com/NXP_MCX_A).
- TI CC2745R10: Added debug and flash programming support (https://kb.segger.com/TI_CC2745).
- TI CC2745R10_PG2: Added debug and flash programming support (https://kb.segger.com/TI_CC2745).
Other changes:
Device Support
- Infineon CYPD21xxx, CYPD31xxx: Under certain circumstances (E.g. Erased flash), connect to target did not work. Fixed.
- Infineon CYT4DNDBHA_M0: flash programming did not work. Fixed.
- ST STM32F7 device series: Added SPI flash programming support for CLK@PB2_nCS@PB6_D0@PF8_D1@PF9_D2@PF7_D3@PF6 pin configuration.
- TI CC2340: Updated the flash loader to make use of the "retainSelMainSectors" on chip erase command.
- TI CC2745: Updated the flash loader to make use of the "retainSelMainSectors" on chip erase command.
DLL
- Repeated calls to JLINKARM_Close() could cause a memory leak. Introduced in V7.94l. Fixed.
J-Link Package
- Linux: Added CMSIS-DAPv2 PID to udev rules file.
J-Scope
- Added a new label that shows the current value of the Trigger symbol.
- J-Scope could crash when the reset button was pressed. Fixed.
Trace
- Added error handling to Arm instruction analyzer selector when tracing via ETMv4.
- Added error handling to Arm instruction analyzer selector when tracing via MTB.
Version V8.12c (2025-01-22)
Highlights:
Device Support
- TDK Micronas HVC5222D: Added debug and flash programming support.
- Toshiba TMPM471: Added debug and flash programming support for new device TMPM471F10FG (https://wiki.segger.com/Toshiba_TX04).
- Toshiba TMPM4K: Added debug and flash programming support for new devices of the series (https://wiki.segger.com/Toshiba_TMPM4K).
Trace
- Added native trace buffer support for Nordic nRF91x1 series devices.
- Published out-of-the-box trace example for Renesas RA0E1: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Renesas RA2E1: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- "usb" command did not reconnect to a J-Link via USB and used IP connection instead when previously a connection via IP was established. Fixed.
Device Support
- AmbiqMicro Apollo510: Wrong flash size was configured for device. Fixed.
Firmware
- J-Link-OB-RA4M2-CortexM: Under certain circumstances (e.g. RA8 target MCU running at 1 GHz speed + MD pin is closed) a memory read could sometimes fail. Fixed.
- J-Link-OB-RA4M2-Full: Under certain circumstances (e.g. RA8 target MCU running at 1 GHz speed + MD pin is closed) a memory read could sometimes fail. Fixed.
- J-Link-OB-RA4M2-Renesas: Under certain circumstances (e.g. RA8 target MCU running at 1 GHz speed + MD pin is closed) a memory read could sometimes fail. Fixed.
- J-Link-OB-RA4M2-RISCV: Under certain circumstances (e.g. RA8 target MCU running at 1 GHz speed + MD pin is closed) a memory read could sometimes fail. Fixed.
J-Flash Lite
- Added warning when trying to start a project without any flash banks selected.
- When selecting specific devices in new project dialog (e.g. STM32F407VE), the internal flash bank was deselected by default instead of selected. Fixed.
J-Scope
- Added a new sampling mode "RTT Plus", which combines symbol selection from HSS with sampling via RTT. For more information, refer to: https://wiki.segger.com/UM08028_J-Scope
- J-Scope could crash when opening an RTT project. Fixed.
- RTT sampling data could become corrupted after a while when the target RTT-Up buffer was large (e.g., 30,000 bytes). Fixed.
RTT
- SEGGER_RTT_printf: Added '*' precision support.
- SEGGER_RTT_printf: Added precision support for strings.
Trace
- Under certain circumstances target devices with an MTB will show that no MTB is present. Introduced with V8.10h. Fixed.
Version V8.12b (2025-01-15)
Highlights:
Device Support
- NXP S32K328: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
- NXP S32K338: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
- NXP S32K341: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
Other changes:
Device Support
- Infineon TLE98xx: Added additional RTT search range to cover the entire RAM.
Firmware
- J-Link-OB-RA4M2-CortexM: UART transmission with higher baud rates (>100000) could lead to a connection timeout. Fixed.
- J-Link-OB-RA4M2-Full: UART transmission with higher baud rates (>100000) could lead to a connection timeout. Fixed.
- J-Link-OB-RA4M2-Renesas: UART transmission with higher baud rates (>100000) could lead to a connection timeout. Fixed.
- J-Link-OB-RA4M2-RISCV: UART transmission with higher baud rates (>100000) could lead to a connection timeout. Fixed.
J-Flash
- The menu actions "Recent Projects" and "Recent Files" and the welcome dialog "Recent Projects" selection did not work on Linux and macOS. Fixed.
J-Flash SPI
- The menu actions "Recent Projects" and "Recent Files" and the welcome dialog "Recent Projects" selection did not work on Linux and macOS. Fixed.
J-Scope
- Added new columns to the TableWidget that display the value of the variables at the time measurement lines.
Trace
- On Armv8M target devices the LE instruction was not analyzed correctly when tracing. Fixed.
Version V8.12a (2025-01-09)
Highlights:
Device Support
- Nuvoton NPCX9: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_NPCX9).
- NXP MCX W72: Added debug and flash programming support (https://wiki.segger.com/NXP_MCX_W).
Trace
- Added native trace buffer support for Renesas RZ/A3UL device series.
Other changes:
Commander
- Added FFORMAT command.
Device Support
- Added support for MIMXRT1043 and MIMXRT1046.
- ArteryTek AT32 devices could falsely report being secured when connecting with JTAG. Fixed.
- GigaDevice: Updated list of supported part numbers / device names.
- HPMicro HPM62xx device series: Flash programming would fail. Introduced in V7.98c. Fixed.
- Qorvo QPG6200: Added support of reset type 2(Pin reset).
- Qorvo QPG6200: Several resets without valid application can disable debug connection. Fixed.
- Renesas RZ/N2H: Debug authentication for Cortex-R52_1 could fail in some cases. Fixed.
- Renesas RZ/T2H: Debug authentication for Cortex-R52_1 could fail in some cases. Fixed.
DLL
- NXP IMXRT117x device series: Added SPI flash programming support for nCS@EMCB211_CLK@EMCB210_D0@EMCB213_D1@EMCB214_D2@EMCB215_D3@EMCB216 pin configuration.
- Watchpoints did not work on ARMv8-M Targets that only have one comparison slot implemented. Fixed.
GDB Server
- GDBServer did not work with gdb-multiarch due to missing architecture tag in the target.xml. Introduced with V7.84e. Fixed.
- Thread information was not displayed when ThreadExtraInfo was requested before the RTOS was started.
J-Scope
- J-Scope could crash when the ELF-file was reparsed. Fixed.
Version V8.12 (2024-12-18)
Highlights:
Device Support
- AlifSemi B1 devices series: Added debug & OSPI flash programming support (https://wiki.segger.com/AlifSemi_B1).
- AlifSemi E1C devices series: Added debug & OSPI flash programming support (https://wiki.segger.com/AlifSemi_E1C).
Other changes:
Device Support
- Infineon TLE9842: Under certain circumstances flash programming could fail. Fixed.
- Infineon XMC1000 device series: Under certain circumstances Flasher standalone mode flash programming could fail. Fixed.
- NXP S32K3xx: Password authentication did not work. Introduced in V8.10g. Fixed.
DLL
- Added exec command SetSkipConsecutiveTraceInit so device specific trace init steps can be skipped on consecutive debug actions if necessary.
- Added J-Link command string "TRACE_SetAllowContinueOnInvalidPacket". (https://kb.segger.com/J-Link_Command_Strings#TRACE_SetAllowContinueOnInvalidPacket)
- Added J-Link command string "TRACE_SetSkipConsecutiveTraceInit". (https://kb.segger.com/J-Link_Command_Strings#TRACE_SetSkipConsecutiveTraceInit)
J-Flash
- J-Flash could crash when downloading a project to Flasher which contains a J-Link script file path that is not valid. Fixed.
Trace
- Trace: Changed default behaviour when unknown packets are sampled. Now on error case the analysis will stop. For more information see here: https://kb.segger.com/Unknown_Trace_Data_Packet_Error
- Trace: ETMv4: On some target devices single stepping may cause instructions to not be counted if the device output "discard" packets after the core was halted. Fixed.
Version V8.10l (2024-12-11)
Highlights:
Device Support
- Analog MAX78002: Added debug and flash programming support (https://wiki.segger.com/MAX78002).
- ST STM32N6: Added debug and flash programming support (https://wiki.segger.com/ST_STM32N6).
Other changes:
Commander
- J-Link Commander conf command was showing MAC address as FF:FF:FF:FF:FF:FF. Fixed.
Device Provisioner
- Added commandline options for host interface selection.
Device Support
- Infineon Traveo: Added flash programming support for S6J3360 and S6J3370 series devices.
- Nordic Semiconductor nRF54L15: Under special circumstances, erase chip did not work. Fixed.
DLL
- Microchip PIC32MK: Under certain circumstances option bytes programming could fail. Fixed.
Firmware
- Flasher ARM V5-1: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher ARM V5: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher ARM V6: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher Compact V5: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher Compact V6: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher Portable PLUS V5: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher Portable PLUS V6: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher PRO V5-1: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher PRO V5: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher PRO V6: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher PRO XL V5-1: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher PRO XL V5: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- Flasher PRO XL V6: TI RM57: Flash programming did not work in stand-alone mode. Fixed.
- J-Link PRO PoE V6: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link PRO V5-1: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link PRO V5: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link ULTRA+ V5-1: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link ULTRA+ V5: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V3 Cortex: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V3 CortexM: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V3 RISC-V: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V3: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
J-Scope
- Some types with prefixes were handled incorrectly. Fixed.
Version V8.10k (2024-12-05)
Highlights:
Device Support
- WIZnet W55RP20: Added debug and flash programming support (https://wiki.segger.com/WIZnet_W55RP20).
Other changes:
Commander
- Corrected typo in the syntax description of the write JTAG command (WJTAGIR).
Device Provisioner
- ST STM32U5 series: Under certain circumstances, option byte programming failed. Fixed.
Device Support
- AmbiqMicro Apollo4: Improved flash programming speed.
- AmbiqMicro Apollo5: Improved flash programming speed.
- WCH CH32F1 device series: Added debug and flash programming support.
Firmware
- Flasher Hub-12 V1: WebIF: When Status Port was enabled, the "Status" page was open and a module was disconnected, Flasher Hub-12 could crash. Fixed.
- Flasher Hub-4 V1: WebIF: When Status Port was enabled, the "Status" page was open and a module was disconnected, Flasher Hub-4 could crash. Fixed.
- J-Link EDU Mini V1: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link EDU Mini V2: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link EDU/BASE/PLUS V11: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link EDU/BASE/PLUS V12: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link PRO PoE V6: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link PRO V5-1: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link PRO V5: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link PRO V6: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link ULTRA+ V5-1: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link ULTRA+ V5: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link ULTRA+ V6: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link WiFi V1: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Link WiFi V2: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V2 Cortex: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V2 CortexM: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V3 Cortex: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V3 CortexM: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V3 RISC-V: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
- J-Trace PRO V3: Under certain circumstances repeated HSS Start/Stop cycles would fail. Fixed.
J-Flash
- For some devices, the sector addresses listed in the "Project settings" --> "Sector selection" dialog, were incorrectly displayed. Fixed.
J-Scope
- In the J-Scope options dialog the serial number was displayed in wrong label. Fixed.
- J-Scope could crash when the connection to the J-Link failed. Fixed.
- Under certain circumstances J-Scope could crash when changing the settings. Fixed.
RTT
- ARMv8-A/R: Added DMB support.
Version V8.10j (2024-12-02)
Highlights:
Device Support
- Artery AT32A42x: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32A42x).
- Artery AT32M41x: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32M41x).
Other changes:
Device Support
- Infineon Traveo II (CYT2CL): Added support for some missing part numbers.
Firmware
- Flasher Hub-12 V1: For some USB-C cables, Flasher Compacts connected directly to Flasher Hub-12 were not powered. Fixed.
- Flasher Hub-4 V1: For some USB-C cables, Flasher Compacts connected directly to Flasher Hub-4 were not powered. Fixed.
Version V8.10i (2024-11-27)
Highlights:
Device Support
- Infineon PSOC C3: Added debug and flash programming support (https://wiki.segger.com/Infineon_PSC3).
- Renesas RZ/T2H: Added debug and flash programming support (https://wiki.segger.com/Renesas_RZ/T2H).
- WCH CH32F2: Added debug and flash programming support (https://wiki.segger.com/WCH_CH32F2).
Other changes:
Device Provisioner
- ST STM32U5 series: Added read/write support for FLASH_SECWMxRx option bytes registers.
- ST STM32U5 series: UnlockDevice operation when performing regression RDP1->RDP0, disables TrustZone if "TZ=0" parameter specified.
Device Support
- Qorvo QM3582x: Improved flash programming speed.
- Qorvo QPG6200: First connect to a device with no valid application did reset the device 2 times. Fixed.
- Qorvo QPG6200: Improved flash programming speed.
- Renesas RX140 device series: HOCOFRQ bit field of OFS1 register was not programmed correctly. Fixed.
- Renesas RX260 device series: HOCOFRQ bit field of OFS1 register was not programmed correctly. Fixed.
DLL
- Improved log output for register reading and writing functions.
- Setting the CPSR.V flag in ARM simulation was handeled incorrectly. Introduced in V8.10f. Fixed.
- Trident T32CM11: Name scheme changed.
- Trident T32CZ20: Name scheme changed.
Firmware
- Flasher Hub-12 V1: When used in a network with a DHCP server that takes long (e.g. 350ms) to respond, Flasher Hub-12 was not reachable via DHCP anymore. Introduced with V7.98i. Fixed.
- Flasher Hub-4 V1: When used in a network with a DHCP server that takes long (e.g. 350ms) to respond, Flasher Hub-4 was not reachable via DHCP anymore. Introduced with V7.98i. Fixed.
Version V8.10h (2024-11-20)
Highlights:
Device Support
- Qorvo QPG6200L: Added debug and flash programming support (https://wiki.segger.com/Qorvo_QPG6200L).
- ST STM32C051: Added debug and flash programming support (https://wiki.segger.com/ST_STM32C0).
- ST STM32WL33: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WL3x).
- Trident T32CM11: Added debug and flash programming support (https://wiki.segger.com/Trident_T32CM11).
- Trident T32CZ20: Added debug and flash programming support (https://wiki.segger.com/Trident_T32CZ20).
Other changes:
Commander
- Command "Disassemble" did not accept 64-bit addreses as input parameters. Fixed.
- Command "IsHalted" did not print 64-bit addresses properly. Fixed.
- Command "StepOver" did not print 64-bit addresses properly. Fixed.
- Command "StepOver" did not work properly for 64-bit addresses. Fixed.
Device Provisioner
- ST STM32U5 series: Added GetAuthId operation to display device authentication ID stored in DBGMCU_DBG_AUTH_DEVICE register.
- ST STM32U5 series: UnlockDevice operation when performing regression RDP1->RDP0, now resets UNLOCK bit in all WRPx registers to 1.
Device Support
- NXP MCXA10: Reset did not halt at application after reset, but in BOOT ROM. Fixed.
- NXP MCXA18: Reset did not halt at application after reset, but in BOOT ROM. Fixed.
DLL
- BPs set on 64-bit addresses were only hit once. Fixed.
- RISC-V: JLINK_GetMOEs() did not work properly if core was halted on a code breakpoint in 64-bit address space. Fixed.
- ST STM32WB0x: Flash programming could fail in case of IWDT was enabled. Fixed.
Firmware
- Flasher Hub-12 V1: Added support for NTP (https://wiki.segger.com/Flasher_Hub_-_Configuration#System_time).
- Flasher Hub-12 V1: WebIF: Opening the "Status" page when Status Port was enabled but no module was connected could lead to unexpected behavior. Fixed.
- Flasher Hub-4 V1: Added support for NTP (https://wiki.segger.com/Flasher_Hub_-_Configuration#System_time).
- Flasher Hub-4 V1: WebIF: Opening the "Status" page when Status Port was enabled but no module was connected could lead to unexpected behavior. Fixed.
Trace
- On target devices where MTB and ETM were specified MTB error messages could pop up unexpectedly when doing trace via ETM. Fixed.
Version V8.10g (2024-11-13)
Highlights:
Device Support
- Qualcomm QCC711: Added debug and flash programming support (https://wiki.segger.com/Qualcomm_QCC711).
- ST SR6G6xx: Added debug and flash programming support (https://wiki.segger.com/ST_SR6G6).
Trace
- Published out-of-the-box trace example for TI AM3359: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for TI AM3517: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- NXP S32K3xx: Added support for attaching to a running target using the "ForceAttachTarget" command string (https://wiki.segger.com/NXP_S32K3xx#ECC_RAM).
DLL
- Coresight TMC detection incorrect, under certain circumstances ETB was detected. Fixed.
- Linux/macOS: J-Link software execution could fail if J-Link DLL was used with an application that is working with a lot (>1000) of opened files. Fixed.
Firmware
- Flasher ARM V5-1: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher ARM V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher ARM V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher Compact V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher Compact V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher Hub-12 V1: WebIF: Changed default for new configurations from "Administrator" to "Operator" mode.
- Flasher Hub-12 V1: WebIF: Dashboard: Added LED to "Last program result" in "General information" table.
- Flasher Hub-12 V1: WebIF: Improved display of links to documentation.
- Flasher Hub-12 V1: WebIF: When opening a tab, the page contents would sometimes take a few [ms] to show. Fixed.
- Flasher Hub-4 V1: WebIF: Changed default for new configurations from "Administrator" to "Operator" mode.
- Flasher Hub-4 V1: WebIF: Dashboard: Added LED to "Last program result" in "General information" table.
- Flasher Hub-4 V1: WebIF: Improved display of links to documentation.
- Flasher Hub-4 V1: WebIF: When opening a tab, the page contents would sometimes take a few [ms] to show. Fixed.
- Flasher Portable PLUS V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher Portable PLUS V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher PRO V5-1: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher PRO V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher PRO V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher PRO XL V5-1: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher PRO XL V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
- Flasher PRO XL V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
J-Flash
- The application crashed when downloading data and config to Flasher on macOS. Introduced with V7.98a. Fixed.
J-Scope
- Added editing of the Y-Resolution column.
- Added Measurement lines to show Time and Value differences.
- Added option to disable auto scale Y-Resolution.
- J-Scope could crash when filtering for a variable. Introduced with V8.10e. Fixed.
Trace
- Implemented native buffer trace support for TI AM3359.
- Implemented native buffer trace support for TI AM3517.
Version V8.10f (2024-11-06)
Highlights:
Device Support
- Microchip PIC32CX BZ3: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32CX_BZ3).
- Nordic Semiconductor nRF54L15: Added debug and flash programming support for Cortex-M33 core (https://wiki.segger.com/Nordic_Semiconductor_nRF54Lxx).
- ST STM32WB06: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB0).
- ST STM32WB1MMC: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB).
- ST STM32WBA50: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WBA).
- ST STM32WBA54: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WBA).
- ST STM32WL5MOC: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WL).
Other changes:
Device Support
- NXP S32K3xx: Added support for password authentication (https://wiki.segger.com/NXP_S32K3xx).
DLL
- The CPSR.V flag could get set wrong in certain cases when using the asm CMP function. Fixed.
Version V8.10e (2024-10-30)
Highlights:
Device Support
- TI CC2340R53: Added debug and flash programming support (https://wiki.segger.com/TI_CC2340).
Trace
- Published out-of-the-box trace example for Altera Arria10: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for NXP S32K388: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Control Panel
- RTT Tab: Event log would not log events happening before opening the Control Panel. Fixed.
DLL
- Logging of internal CPU_ReadMem() and CPU_WriteMem() calls did cut of the address at 32-bit in the log output. Fixed.
- RISC-V RV64: Single stepping in 64-bit address space could still cause a "failed to read current instruction" error (fix from V8.10c was incomplete). Fixed.
Firmware
- Flasher ARM V5-1: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher ARM V5-1: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher ARM V5: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher ARM V5: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher ARM V6: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher ARM V6: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher Compact V5: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher Compact V5: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher Compact V6: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher Compact V6: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher Portable PLUS V6: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher Portable PLUS V6: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher PRO V5-1: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher PRO V5-1: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher PRO V5: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher PRO V5: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher PRO V6: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher PRO V6: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher PRO XL V5: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher PRO XL V5: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
- Flasher PRO XL V6: Stand-alone mode: SFL: If multiple flash banks were programmed and target provided very little RAM for Flasher as temporary RAMCode data buffer (< 2 KB), it could happen that programming of the 2nd bank reported an error. Fixed.
- Flasher PRO XL V6: Stand-alone mode: SFL: Incorrect data could be passed to RAMCode if: algo provided SFL Init()/UnInit() functions and turbo mode was used (e.g. on Renesas RA8 series devices). Fixed.
J-Scope
- J-Scope could crash when using an ELF file containing large arrays (more than 10,000 elements). Fixed.
- Under certain circumstances triggering on a symbol value change did not work. Fixed.
RTT Viewer
- Configuration Dialog: Added link to SEGGER Wiki explaining the "Auto Detection" option.
Trace
- Implemented native buffer trace support for Altera Arria10.
- ST SR5E1 pin tracing did not work for Core 1. Fixed.
Version V8.10d (2024-10-24)
Highlights:
Device Provisioner
- ST STM32U5 series: Added support for option-bytes programming, password management and device locking/unlocking (https://wiki.segger.com/ST_STM32U5_Option_Bytes_Programming).
Device Support
- Added debug + flash programming support for Renesas RX260 series devices (R5F52606, R5F52607, R5F52608).
- Added debug + flash programming support for Renesas RX261 series devices (R5F52616, R5F52617, R5F52618).
- Renesas RA8E1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8E1).
- ST STM32WB07: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB0).
DLL
- Added general support for Renesas RX260 core.
- Added general support for Renesas RX261 core.
Other changes:
Commander
- FLIST command output could get cut off if there were too many files on the Flasher. Fixed.
Control Panel
- When loading the "General" tab for the first time, there was a delay in displaying some of the information. Fixed.
- While the "General" tab was open, the log was getting spammed with JLINK_EMU_FILE_GetVolumeInfo() calls. Fixed.
Device Support
- Aliased addresses for boot sectors did not work on PIC32MK devices. Fixed.
- AlifSemi E1/E3/E5/E7 device series: QSPI flash programming for more than 16 MB did not work. Fixed.
- Analog ADuCM360/ADuCM361: Under certain circumstances standalone flash programming could fail. Fixed.
- NXP iMXRT117x: Under certain circumstances external flash programming verify could fail. Fixed.
- NXP Kinetis V: Auto detection of the RTT block did not work properly. Fixed.
- NXP LPC54xx: Auto detection of the RTT block did not work properly. Fixed.
- NXP NCJ29D5: RTT auto detection range extended whole non-secure RAM.
- ST STM32G0 device series: Option bytes programming always programmed reserved areas with zeroes regardless of the actual data value. Fixed.
- ST STM32G4 CAT2 devices: Option bytes programming could fail for last option byte (SEC1R). Fixed.
- ST STM32H74xx/STM32H75xx: Added QSPI flash programming support for pin config CLK@PF10_nCS@PG6_D0@PF8_D1@PF9_D2@PF7_D3@PF6.
- ST STM32U5 device series: Under certain circumstances internal flash programming could fail. Fixed.
- When programming config bits on PIC32MK devices, verification did not work correctly in some cases. Fixed.
DLL
- Under special circumstances, the 32-bit J-Link DLL could crash during trace. Fixed.
Firmware
- Flasher ARM V5-1: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher ARM V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher ARM V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher Compact V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher Compact V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher Portable PLUS V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher Portable PLUS V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher PRO V5-1: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher PRO V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher PRO V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher PRO XL V5-1: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher PRO XL V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
- Flasher PRO XL V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
GDB Server
- Debugging devices in JTAG Daisy chain with default settings not worked. Fixed.
- embOS plugin: GDB Server could crash when used with the embOS plugin. Fixed.
J-Flash
- Some sample projects (e.g. AT91RM9200_EK.jflash) could not be loaded. Fixed.
Version V8.10c (2024-10-16)
Highlights:
Device Support
- Added device support for Microchip dsPIC33CKxxxMPxxx family.
- RaspberryPi RP2350: Added debug and QSPI flash programming support (https://wiki.segger.com/Raspberry_Pi_RP2350).
- ST STM32C071: Added debug and flash programming support (https://wiki.segger.com/ST_STM32C0).
- TI MSPM0Gx51x: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0G).
Other changes:
Device Support
- NXP K32/KW45/MCXW: Under certain circumstances flash operations failed. Fixed.
- NXP S32M241: Flash programming could fail due to incorrect sector size. Fixed.
- NXP S32M242: Flash programming could fail due to incorrect sector size. Fixed.
- NXP S32M243: Flash programming could fail due to incorrect sector size. Fixed.
- NXP S32M24x: Added support for the native block erase command.
DLL
- RISC-V RV64: Single stepping in 64-bit address space could cause a "failed to read current instruction" error. Fixed.
- Some log outputs with 64-bit arguments could cause crashes in 32-bit build of DLL (did not affect 64-bit builds of the DLL). Fixed.
Firmware
- Flasher ARM V5-1: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher ARM V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher ARM V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher Compact V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher Compact V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher Portable PLUS V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher Portable PLUS V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher PRO V5-1: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher PRO V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher PRO V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher PRO XL V5-1: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher PRO XL V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- Flasher PRO XL V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- J-Link PRO PoE V6: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- J-Link PRO V5-1: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- J-Link PRO V5: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- J-Link PRO V6: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- J-Link ULTRA+ V5-1: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- J-Link ULTRA+ V5: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
- J-Link ULTRA+ V6: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
J-Run
- Application exit value print incorrect. Fixed.
- Application exit wildcard parsing not robust for intermixed strings. Fixed.
- Improved output and logging (RTT wildcard commands visible in output, logging format unified).
J-Scope
- In some cases, the GUI was not loaded correctly when opening or creating a project. Fixed.
Version V8.10b (2024-10-09)
Highlights:
Device Support
- Microchip SAMA7G54: Added device support for SAMA7G54D4G.
Trace
- Published out-of-the-box trace example for Infineon XMC7200: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- Some message boxes (e.g. unlock dialogs) were shown although "-NoGui" option was active. Fixed.
Device Support
- AmbiqMicro Apollo5: Reset sequence did not work properly. Fixed.
- Infineon PSoC 4 HV: Added debug and flash programming support (https://wiki.segger.com/Infineon_PSoC_4_HV).
- NXP MCXN10: Initialization of FLEXSPI did not work when booting from FLEXSPI. Fixed.
- NXP MCXN10: Reset did not work when booting from FLEXSPI. Fixed.
- Renesas RA4E1, RA4L1, RA4M2, RA4M3, RA4T1 device series: No reset via reset pin was performed if confused core is detected. Fixed.
- Renesas RA6E1, RA6M4, RA6M5, RA6T2 device series: No reset via reset pin was performed if confused core is detected. Fixed.
- Renesas RA8D1, RA8M1, RA8T1 device series: No reset via reset pin was performed if confused core is detected. Fixed.
- TI CC1311R3: Added debug and flash programming support.
DLL
- Pressing the close button in the unsecure device dialog counted as pressing "Yes", while it should count as "No". Fixed.
- Windows: Under very special circumstances, randomly named (temp) file was accidentally created in current working directory. Fixed.
Firmware
- J-Link PRO PoE V6: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Link PRO V5-1: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Link PRO V5: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Link PRO V6: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Link WiFi V1: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Link WiFi V2: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Trace PRO V3 Cortex: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Trace PRO V3 CortexM: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Trace PRO V3 RISC-V: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
- J-Trace PRO V3: Added support for multiple connections via IP (e.g. IDE and SystemView in parallel). (Was only supported for USB so far)
GDB Server
- Windows: Under very special circumstances, randomly named (temp) file was accidentally created in current working directory. Fixed.
J-Flash
- Windows: Under very special circumstances, randomly named (temp) file was accidentally created in current working directory. Fixed.
J-Flash SPI
- Windows: Under very special circumstances, randomly named (temp) file was accidentally created in current working directory. Fixed.
Trace
- Fixed native trace support for Infineon XMC7000 series.
Version V8.10a (2024-10-02)
Highlights:
Device Support
- NXP NCJ29D5: Added flash programming support for DSP Firmware(https://wiki.segger.com/NXP_NCJ29D5).
- NXP OL23D0: Added debug and flash programming support(https://wiki.segger.com/NXP_OL23D0).
- TI CC2651P3: Added debug & flash programming support (https://wiki.segger.com/TI_CC26xx).
- TI CC2651R3: Added debug & flash programming support (https://wiki.segger.com/TI_CC26xx).
Trace
- Published out-of-the-box trace example for NXP iMX6ULL: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace examples for NXP MCXN947: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- "wreg" command did not work with 64-bit values (cut values to 32-bit) for architectures other than ARMv8-A (e.g. RISC-V RV64). Fixed.
Device Support
- NXP iMXRT117x: Flash verification failed when using MCUExpresso SDK 2.16 on MIMXRT1170-EVK (using SPI NOR flash ISSI IS25WP128). Fixed.
- NXP NCJ29D5: WorkRAM size adjusted to 6KB because of DSP Firmware update requirements.
- Renesas RA4E1, RA4L1, RA4M2, RA4M3, RA4T1 device series: Under certain circumstances target could lock up when resetting via reset pin and disconnecting afterwards. Fixed.
- Renesas RA6E1, RA6M4, RA6M5, RA6T2 device series: Under certain circumstances target could lock up when resetting via reset pin and disconnecting afterwards. Fixed.
- Renesas RA8D1, RA8M1, RA8T1 device series: Under certain circumstances target could lock up when resetting via reset pin and disconnecting afterwards. Fixed.
DLL
- Cadence Xtensa: Added support for HiFi 5 core.
- J-Link script files: Added JLINK_FILE_GetSize() API function call. (See https://wiki.segger.com/J-Link_script_files#JLINK_FILE_GetSize())
- J-Link would show the wrong reset type when setting through J-Link script file. Fixed.
- Log file output for memory accesses in 64-bit address space did not log target address properly (address was cut to 32-bit). Fixed.
- Memory accesses (R/W) beyond the 32-bit address space did not work properly and returned data for 32-bit cut address. Fixed.
Firmware
- ARMv8-A/R (e.g. Cortex-A53): Increased module version to 14: Memory R/W accesses beyond 32-bit address space did not work properly. Fixed.
- Cadence Xtensa: Increased module version to 5: Under special circumstances, Xtensa-behind-DAP setups did not work properly. Fixed.
- Flasher ARM V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher ARM V5: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher ARM V6: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher Compact V5: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher Compact V5: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher Compact V5: Rebuilt firmware with RISC-V module version 4.
- Flasher Compact V6: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher Compact V6: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher Compact V6: Rebuilt firmware with RISC-V module version 4.
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: After clicking "Reboot", some elements were still visible or accessible while Flasher Hub was rebooting. Fixed.
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: After uploading a Flasher firmware update file, the "New" / "Old" indicators in the "Apply Flasher firmware update" table were not updated. Fixed.
- Flasher Hub-12 V1: WebIF: Files: When uploading a folder with multiple files inside, not all files inside the folder were actually uploaded. Fixed.
- Flasher Hub-12 V1: WebIF: Files: When uploading files using the upload button, the destination folder was the root folder instead of the current folder. Fixed.
- Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: After clicking "Reboot", some elements were still visible or accessible while Flasher Hub was rebooting. Fixed.
- Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: After uploading a Flasher firmware update file, the "New" / "Old" indicators in the "Apply Flasher firmware update" table were not updated. Fixed.
- Flasher Hub-4 V1: WebIF: Files: When uploading a folder with multiple files inside, not all files inside the folder were actually uploaded. Fixed.
- Flasher Hub-4 V1: WebIF: Files: When uploading files using the upload button, the destination folder was the root folder instead of the current folder. Fixed.
- Flasher Portable PLUS V5: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher Portable PLUS V5: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher Portable PLUS V5: Rebuilt firmware with RISC-V module version 4.
- Flasher Portable PLUS V6: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher Portable PLUS V6: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher Portable PLUS V6: Rebuilt firmware with RISC-V module version 4.
- Flasher PRO V5-1: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher PRO V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher PRO V5-1: Rebuilt firmware with RISC-V module version 4.
- Flasher PRO V5: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher PRO V5: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher PRO V5: Rebuilt firmware with RISC-V module version 4.
- Flasher PRO V6: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher PRO V6: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher PRO V6: Rebuilt firmware with RISC-V module version 4.
- Flasher PRO XL V5-1: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher PRO XL V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher PRO XL V5-1: Rebuilt firmware with RISC-V module version 4.
- Flasher PRO XL V5: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher PRO XL V5: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher PRO XL V5: Rebuilt firmware with RISC-V module version 4.
- Flasher PRO XL V6: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
- Flasher PRO XL V6: Rebuilt firmware with ARMv8-A/R module version 14.
- Flasher PRO XL V6: Rebuilt firmware with RISC-V module version 4.
- J-Link EDU Mini V1: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link EDU Mini V1: Rebuilt firmware with RISC-V module version 4.
- J-Link EDU Mini V2: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link EDU Mini V2: Rebuilt firmware with RISC-V module version 4.
- J-Link EDU/BASE/PLUS V11: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link EDU/BASE/PLUS V11: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link EDU/BASE/PLUS V11: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link EDU/BASE/PLUS V11: Rebuilt firmware with RISC-V module version 4.
- J-Link EDU/BASE/PLUS V12: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link EDU/BASE/PLUS V12: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link EDU/BASE/PLUS V12: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link EDU/BASE/PLUS V12: Rebuilt firmware with RISC-V module version 4.
- J-Link PRO PoE V6: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link PRO PoE V6: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link PRO PoE V6: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link PRO PoE V6: Rebuilt firmware with RISC-V module version 4.
- J-Link PRO V5-1: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link PRO V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link PRO V5-1: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link PRO V5-1: Rebuilt firmware with RISC-V module version 4.
- J-Link PRO V5: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link PRO V5: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link PRO V5: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link PRO V5: Rebuilt firmware with RISC-V module version 4.
- J-Link ULTRA+ V5-1: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link ULTRA+ V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link ULTRA+ V5-1: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link ULTRA+ V5-1: Rebuilt firmware with RISC-V module version 4.
- J-Link ULTRA+ V5: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link ULTRA+ V5: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link ULTRA+ V5: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link ULTRA+ V5: Rebuilt firmware with RISC-V module version 4.
- J-Link ULTRA+ V6: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link ULTRA+ V6: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link ULTRA+ V6: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link ULTRA+ V6: Rebuilt firmware with RISC-V module version 4.
- J-Link WiFi V1: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link WiFi V1: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link WiFi V1: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link WiFi V1: Rebuilt firmware with RISC-V module version 4.
- J-Link WiFi V2: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link WiFi V2: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link WiFi V2: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link WiFi V2: Rebuilt firmware with RISC-V module version 4.
- J-Link-OB-K22-Cortex-A: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link-OB-K22-Full: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link-OB-K22-Full: Rebuilt firmware with RISC-V module version 4.
- J-Link-OB-K22-RISCV: Rebuilt firmware with RISC-V module version 4.
- J-Link-OB-RA4M2-Full: Cadence Xtensa: Added support for HiFi 5 core.
- J-Link-OB-RA4M2-Full: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link-OB-RA4M2-Full: Rebuilt firmware with Cadence Xtensa module version 5.
- J-Link-OB-RA4M2-Full: Rebuilt firmware with RISC-V module version 4.
- J-Link-OB-RA4M2-Renesas: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Link-OB-S124: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Trace PRO V3 Cortex: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Trace PRO V3 RISC-V: Rebuilt firmware with RISC-V module version 4.
- J-Trace PRO V3: Rebuilt firmware with ARMv8-A/R module version 14.
- J-Trace PRO V3: Rebuilt firmware with RISC-V module version 4.
- MCU-Link on-board: Cadence Xtensa: Added support for HiFi 5 core.
- MCU-Link on-board: Rebuilt firmware with Cadence Xtensa module version 5.
- MCU-Link Pro: Cadence Xtensa: Added support for HiFi 5 core.
- MCU-Link Pro: Rebuilt firmware with Cadence Xtensa module version 5.
- RISC-V (e.g. RV64): Increased module version to 4: Memory R/W accesses beyond 32-bit address space did not work properly. Fixed.
J-Flash SPI
- ISSI IS25LP02G: The reported flash size was incorrect (128 MB instead of 256 MB). Fixed.
- J-Flash SPI did not check if data actually fit in the selected flash when saving a Flasher DAT file. Fixed.
Trace
- Added native trace buffer support for NXP iMX6ULL series.
- Added native trace buffer support for NXP MCXN10 series.
Version V8.10 (2024-09-25)
Highlights:
Device Support
- Espressif ESP32-C2: Added debug support (https://wiki.segger.com/Espressif_ESP32-C2).
- Espressif ESP32-C3: Added debug support (https://wiki.segger.com/Espressif_ESP32-C3).
- Espressif ESP32-C6: Added debug support (https://wiki.segger.com/Espressif_ESP32-C6).
- Espressif ESP32-H2: Added debug support (https://wiki.segger.com/Espressif_ESP32-H2).
- Microchip PIC32MK: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32MK).
- TI MSPM0L111x: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0L).
Trace
- Added native pin and buffer trace support for the Xilinx/AMD Zynq UltraScale+ device family.
- Published out-of-the-box trace examples for Renesas RZ/G1M and RZ/G1E: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- ST STM32WBA55: Flash programming did not work. Introduced in V7.96t. Fixed.
DLL
- LPC-Link2 on-board (aka "LPCXpresso") was false-positively detected as clone. Introduced in V7.98i. Fixed.
Firmware
- Cadence Xtensa (e.g. HiFi 3): Increased module version to 3: Interrupts were not disabled during single step. Fixed.
- Cadence Xtensa (e.g. HiFi 3): Increased module version to 4: EXCCAUSE and EXCVADDR were not preserved properly on halt (could lead to issues when debugging exception entry/exit handlers). Fixed.
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: Improved page layout.
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: Removed redundant 'Product' column.
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: Table rows now show if a module firmware is invalidated, newer or older than the user-uploaded firmware.
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: When updating the firmware of a module, the table entry would flicker briefly. Fixed.
- Flasher Hub-12 V1: WebIF: Dashboard: Removed redundant 'Product' column from 'Overview' table.
- Flasher Hub-12 V1: WebIF: Dashboard: Removed redundant 'Status' column from 'Overview' table.
- Flasher Hub-12 V1: WebIF: Dashboard: The 'Last result' column now also shows the DAT file CRC, if available.
- Flasher Hub-12 V1: WebIF: Dashboard: The 'Project' column now shows plain text instead of a grayed out dropdown, if only a single project is available.
- Flasher Hub-12 V1: WebIF: Moved UI for module firmware update from "Dashboard" to "Configuration > Flasher Hub".
- Flasher Hub-12 V1: WebIF: Moved user interface of 'Programming' tab into the 'Dashboard' tab.
- Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: Improved page layout.
- Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: Removed redundant 'Product' column.
- Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: Table rows now show if a module firmware is invalidated, newer or older than the user-uploaded firmware.
- Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: When updating the firmware of a module, the table entry would flicker briefly. Fixed.
- Flasher Hub-4 V1: WebIF: Dashboard: Removed redundant 'Product' column from 'Overview' table.
- Flasher Hub-4 V1: WebIF: Dashboard: Removed redundant 'Status' column from 'Overview' table.
- Flasher Hub-4 V1: WebIF: Dashboard: The 'Last result' column now also shows the DAT file CRC, if available.
- Flasher Hub-4 V1: WebIF: Dashboard: The 'Project' column now shows plain text instead of a grayed out dropdown, if only a single project is available.
- Flasher Hub-4 V1: WebIF: Moved UI for module firmware update from "Dashboard" to "Configuration > Flasher Hub".
- Flasher Hub-4 V1: WebIF: Moved user interface of 'Programming' tab into the 'Dashboard' tab.
- J-Link EDU/BASE/PLUS V11: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link EDU/BASE/PLUS V11: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link EDU/BASE/PLUS V12: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link EDU/BASE/PLUS V12: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link PRO PoE V6: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link PRO PoE V6: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link PRO PoE V6: VCOM: For baudrates higher than 4 MBaud, Rx data could be dropped by J-Link because buffer was undersized. Fixed.
- J-Link PRO V5-1: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link PRO V5-1: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link PRO V5-1: VCOM: For baudrates higher than 4 MBaud, Rx data could be dropped by J-Link because buffer was undersized. Fixed.
- J-Link PRO V5: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link PRO V5: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link PRO V5: VCOM: For baudrates higher than 4 MBaud, Rx data could be dropped by J-Link because buffer was undersized. Fixed.
- J-Link ULTRA+ V5-1: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link ULTRA+ V5-1: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link ULTRA+ V5-1: VCOM: For baudrates higher than 4 MBaud, Rx data could be dropped by J-Link because buffer was undersized. Fixed.
- J-Link ULTRA+ V5: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link ULTRA+ V5: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link ULTRA+ V5: VCOM: For baudrates higher than 4 MBaud, Rx data could be dropped by J-Link because buffer was undersized. Fixed.
- J-Link ULTRA+ V6: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link ULTRA+ V6: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link ULTRA+ V6: VCOM: For baudrates higher than 4 MBaud, Rx data could be dropped by J-Link because buffer was undersized. Fixed.
- J-Link WiFi V1: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link WiFi V1: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link WiFi V2: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link WiFi V2: Rebuilt firmware with Cadence Xtensa module version 4.
- J-Link-OB-RA4M2-Full: Rebuilt firmware with Cadence Xtensa module version 3.
- J-Link-OB-RA4M2-Full: Rebuilt firmware with Cadence Xtensa module version 4.
- MCU-Link on-board: VCOM: Rebuilt firmware with Cadence Xtensa module version 3.
- MCU-Link on-board: VCOM: Rebuilt firmware with Cadence Xtensa module version 4.
- MCU-Link Pro: VCOM: Rebuilt firmware with Cadence Xtensa module version 3.
- MCU-Link Pro: VCOM: Rebuilt firmware with Cadence Xtensa module version 4.
GDB Server
- embOS Plugin: Updated the plugin to maintain compatibility with the latest version of embOS.
J-Flash SPI
- Added a new EEPROM selection "Custom" which allows all EEPROM settings to be edited.
- When creating a new project with EEPROM and manual settings the default settings were not applied. Fixed.
J-Run
- Added logging support. Added command line options --log and --fileonly.
- Change and enhance J-Run exit value handling (return -1 on error, application exit code provided by SYS_EXIT when available).
J-Scope
- In some cases, unnamed arrays were incorrectly displayed in the symbol selection tree. Fixed.
Version V7.98i (2024-09-18)
Device Support
- AmbiqMicro Apollo5: Re-programming of a sector could fail if the entire sector was not empty and the image to be programmed did not cover the entire sector. Fixed.
- AmbiqMicro Apollo5: Verify could erroneously fail when programming small payloads. Fixed.
- ST STM32F0xxxx, STM32F1xxxx, STM32F3xxx8, STM32F3xxxB, STM32F3xxxC: Under certain circumstances, the flash controller was not locked after flash programming. Fixed.
- STM32F7xxxx: Under certain circumstances, the flash controller was not locked after flash programming. Fixed.
Firmware
- Flasher ARM V5-1: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher ARM V5-1: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher ARM V5: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher ARM V5: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher ARM V6: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher ARM V6: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher Compact V5: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher Compact V5: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher Compact V6: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher Compact V6: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher Hub-12 V1: WebIF "About" tab: Updated contents.
- Flasher Hub-12 V1: WebIF "Status" tab: Renamed to "Dashboard".
- Flasher Hub-12 V1: WebIF "Terminal" tab: Renamed to "Status".
- Flasher Hub-12 V1: WebIF: Added "Terminal" tab, enabling Flasher terminal access from the web interface.
- Flasher Hub-12 V1: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher Hub-4 V1: WebIF "About" tab: Updated contents.
- Flasher Hub-4 V1: WebIF "Status" tab: Renamed to "Dashboard".
- Flasher Hub-4 V1: WebIF "Terminal" tab: Renamed to "Status".
- Flasher Hub-4 V1: WebIF: Added "Terminal" tab, enabling Flasher terminal access from the web interface.
- Flasher Hub-4 V1: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher Portable PLUS V6: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher Portable PLUS V6: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher PRO V5-1: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher PRO V5-1: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher PRO V5: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher PRO V5: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher PRO V6: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher PRO V6: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher PRO XL V5-1: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher PRO XL V5-1: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher PRO XL V5: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher PRO XL V5: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
- Flasher PRO XL V6: Programming SPI flashes in standalone mode using a .DAT file with address ranges outside of flash would not return an error. Fixed.
- Flasher PRO XL V6: When a host application (e.g. Flasher Deployer) requested the list of files in a folder on the Flasher, it would not list beyond 128 files. Fixed.
J-Flash
- Flasher file dialog progress dialog would flicker when transfering multiple small files in one go. Fixed.
- Transfering many (e.g. > 100) files from Flasher to PC at once using the Flasher file dialog could cause J-Flash to freeze. Fixed.
J-Flash SPI
- Flasher file dialog progress dialog would flicker when transfering multiple small files in one go. Fixed.
- Transfering many (e.g. > 100) files from Flasher to PC at once using the Flasher file dialog could cause J-Flash SPI to freeze. Fixed.
- When creating a new project with EEPROM and manual settings the default settings were not applied. Fixed.
J-Run
- Initialization of PC and SP was incorrect for certain targets (e.g. RP2040 or LPC55S16). Made configurable. Added command line options --pc and --sp.
- Removed --quit command line option. (Automatic exit is default anyway, so this option was never used)
RTT
- SEGGER_RTT_Conf.h: Handling for __ARM_ARCH_8_1M_MAIN__ was missing. Fixed.
Version V7.98h (2024-09-11)
Highlights:
Device Support
- AmbiqMicro Apollo5: Added debug and flash programming support (https://wiki.segger.com/AmbiqMicro_Apollo5).
- GigaDevice GD32F5: Added option bytes programming support (https://wiki.segger.com/GigaDevice_GD32F5)
- NXP MCXA13x: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXA10).
Trace
- Published out-of-the-box trace example for NXP iMX7D: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- Microchip PIC32CX BZ2: Added WBZ450 and WBZ451 module device names.
- STM32G0: Verification of option byte memory could fail. Fixed.
DLL
- Cortex-A15: PTM init did not work properly on certain devices (e.g. Renesas RZ/G1M series devices), resulting in trace not working. Fixed.
Firmware
- Flasher Hub-12 V1: In rare occasions, a false-positive result would be shown folllowing a programming operation. Fixed.
- Flasher Hub-12 V1: Removing a module (or the "All modules") folder when Status Port was enabled could cause Flasher Hub to lock up and become unresponsive until a power-cycle. Fixed.
- Flasher Hub-12 V1: WebIF: The project lists in the 'Programming' tab were not updated correctly on disconnect or after a module position change. Fixed.
- Flasher Hub-4 V1: In rare occasions, a false-positive result would be shown folllowing a programming operation. Fixed.
- Flasher Hub-4 V1: Removing a module (or the "All modules") folder when Status Port was enabled could cause Flasher Hub to lock up and become unresponsive until a power-cycle. Fixed.
- Flasher Hub-4 V1: WebIF: The project lists in the 'Programming' tab were not updated correctly on disconnect or after a module position change. Fixed.
- J-Link-OB-K22-NordicSemi: Max. 100mA power consumption was reported in USB config descriptor. Lifted to 500mA.
- J-Link-OB-nRF5340-NordicSemi: Max. 100mA power consumption was reported in USB config descriptor. Lifted to 500mA.
- J-Link-OB-SAM3U128-NordicSemi: Max. 100mA power consumption was reported in USB config descriptor. Lifted to 500mA.
Trace
- Added native trace buffer support for NXP iMX7D series.
Version V7.98g (2024-09-05)
Highlights:
Device Support
- Renesas RZ/T2ME: Added debug and flash programming support (https://wiki.segger.com/Renesas_RZ/T2ME).
Trace
- Added native trace buffer support for Renesas RZ/T2M and RZ/N2L series.
Other changes:
Control Panel
- Added J-Link bootloader version to the "General" tab.
Device Support
- Infineon PSoC4: Under certain circumstances, attach was not possible. Introduced in V7.98b. Fixed.
DLL
- Command string "ExcludeFromFlashCache" did not detect properly that the target application changed the data in a sector and programmed old cache data instead of merging with current target data, on sector reprogramming. Fixed.
- Probe selection dialog: Flasher Hub-4 showed incorrect picture. Fixed.
Firmware
- Flasher ARM V5-1: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher ARM V5-1: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher ARM V5-1: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher ARM V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher ARM V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher ARM V5: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher ARM V6: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher ARM V6: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher ARM V6: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher Compact V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher Compact V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher Compact V5: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher Compact V6: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher Compact V6: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher Portable PLUS V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher Portable PLUS V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher Portable PLUS V5: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher PRO V5-1: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher PRO V5-1: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher PRO V5-1: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher PRO V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher PRO V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher PRO V5: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher PRO V6: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher PRO V6: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher PRO V6: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher PRO XL V5-1: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher PRO XL V5-1: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher PRO XL V5-1: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher PRO XL V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher PRO XL V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher PRO XL V5: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- Flasher PRO XL V6: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
- Flasher PRO XL V6: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
- Flasher PRO XL V6: When programming the target via UART and there was no pull-up resistor on the Flasher Tx line (e.g. TI MSP430), a glitch could happen when changing the baudrate. Fixed.
- J-Link EDU/BASE/PLUS V11: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link EDU/BASE/PLUS V11: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link EDU/BASE/PLUS V11: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link EDU/BASE/PLUS V11: RISC-V: Rebuilt firmware with RISC-V module version 3.
GUI Applications
- Device selection dialog: Improved filtering by manufacturer.
J-Run
- Enhancement for passing parameters to target application using "--args" command line option.
- Semihosting SYS_EXIT application status not evaluated correctly. Fixed.
Trace
- Added trace support for Armv8-A/R architecture in AArch32 and AArch64 mode.
Version V7.98f (2024-08-29)
Highlights:
Device Support
- GigaDevice GD32E51x: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32E5).
- GigaDevice GD32G5: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32G5).
Trace
- Published out-of-the-box trace example for STM MP1 A7: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- Extended command "BootMode" to support CMSIS-DAPv2 (https://wiki.segger.com/J-Link_Commander#BootMode).
Control Panel
- Added J-Link firmware version to the "General" tab.
Device Support
- TI CC2340: Flash programming failed in case of the user record was not used thus the user record CRC was invalid. Fixed.
DLL
- Cortex-A7: ETM unlock sequence and version detection did not work properly, resulting in trace not working. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V12: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
- J-Link PRO PoE V6: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
- J-Link PRO V6: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
- J-Link ULTRA+ V6: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
- J-Link WiFi V2: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
J-Link Package
- Windows: Qt-DLL files were not signed. Fixed.
Version V7.98e (2024-08-21)
Highlights:
J-Flash SPI
- Added a device selection dialog to select a device from the list of supported devices.
- Introduced a welcome dialog and a new project dialog.
Trace
- Published out-of-the-box trace example for ST STM32H7S7: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- Andestech RISC-V: Added debug support for the D23, N225, N25F_SE, D25F_SE, D45_SE, AX65 and AX45MPV cores.
- Renesas RA2E1: Incorrect CPU frquency was reported during flash programming (500 KHz instead of actual 8 MHz). Fixed.
- Renesas RA2E1: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
- Renesas RA2L1: Incorrect CPU frquency was reported during flash programming (500 KHz instead of actual 8 MHz). Fixed.
- Renesas RA2L1: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
- Renesas RX140: The R5F51403 was not detected and handled properly. Fixed.
- Renesas S1JA: Incorrect CPU frequency was reported during flash programming (500 KHz instead of actual 8 MHz). Fixed.
- Renesas S1JA: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
- Renesas S5D9: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
- Renesas S7G2: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
GDB Server
- ARMv8-A/R: Data BPs (watchpoints) were not reported properly as halt reason to GDB which could lead to display errors and some GDB commands to not work properly. Fixed.
- Debug session could run wild (GDB ending up in endless halted-resume loop) in case an unknown data BP (watchpoint) was hit. Fixed.
Trace
- Buffer trace init on Renesas RZ/T1 series could fail. Fixed.
Version V7.98d (2024-08-14)
Highlights:
Device Support
- NXP iMX8X series: Added debug support for the Cortex-A35 cores (https://wiki.segger.com/NXP_i.MX_8X).
- Renesas RZ/N1 devices series: Added flash programming support for QSPI1 bank.
- ST STM32WB05: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB0).
- ST STM32WB09: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB0).
Other changes:
Device Support
- NXP MCXN10 series: Flash programming failed on devices marked with MCXNxxx. Device marked with PMCXNxxx are not affected. Fixed.
- TI CC2340: Flash programming failed in case of data file contained no data for the first sector of the program flash (e.g. in case of using VTOR). Fixed.
- TI CC2340: The device specific reset did not support VTOR (configured via CCFG area). Fixed.
DLL
- Mem access via AP other than AP0 fails for SoC-400. Introduced in V7.96r. Fixed.
Firmware
- Flasher ARM V5-1: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher ARM V5: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher ARM V6: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher Compact V5: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher Hub-12 V1: Commands that exceeded 64 characters in length (e.g. #AUTO PATCH) would be cut off when sent to the targeted module(s). Fixed.
- Flasher Hub-12 V1: Executing the #AUTO PATCH command with a syntax error would return the last result of the target module. Fixed.
- Flasher Hub-12 V1: The firmware version reported by #FWVERSIONMOD was cut off for modules at posistion 10 or above. Fixed.
- Flasher Hub-12 V1: When Status Port was enabled, some commands (i.e. #PROJECT and #SELECT) could cause Flasher Hub to lock up and become unresponsive until a power-cycle. Fixed.
- Flasher Hub-4 V1: Commands that exceeded 64 characters in length (e.g. #AUTO PATCH) would be cut off when sent to the targeted module(s). Fixed.
- Flasher Hub-4 V1: Executing the #AUTO PATCH command with a syntax error would return the last result of the target module. Fixed.
- Flasher Hub-4 V1: The firmware version reported by #FWVERSIONMOD was cut off for modules at posistion 10 or above. Fixed.
- Flasher Hub-4 V1: When Status Port was enabled, some commands (i.e. #PROJECT and #SELECT) could cause Flasher Hub to lock up and become unresponsive until a power-cycle. Fixed.
- Flasher Portable PLUS V5: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher PRO V5-1: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher PRO V5: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher PRO V6: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher PRO XL V5-1: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher PRO XL V5: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
- Flasher PRO XL V6: The durations reported by the response to an #AUTO command contained leading spaces instead of zeroes after the decimal point. Introduced in V7.98b. Fixed.
Version V7.98c (2024-08-07)
Highlights:
Device Support
- Nuvoton KM1M4BF6x: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M4BF).
- NXP iMX8M series: Added debug support for the Cortex-A53 cores (https://wiki.segger.com/NXP_i.MX_8M).
- NXP iMX8MMini series: Added debug support for the Cortex-A53 cores (https://wiki.segger.com/NXP_i.MX_8M_Mini).
DLL
- ARMv8-A: Added watchpoint support for AArch32 and AArch64 mode.
- ARMv8-R: Added watchpoint support for AArch32 and AArch64 mode.
J-Flash Lite
- Added option to disable/enable specific flash banks.
- Added option to select specific flash loader if multiple loaders are available.
Trace
- Published out-of-the-box trace example for ST STM32H7S3: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- CVA BlueWhale CVM012x: Updated device specific handling such as security detection on connect (https://wiki.segger.com/CVA_BlueWhale_CVM012x).
- HPMicro HPM device series: Updated third party device support package. Changes: Invalidate all ICACHE on the initialization of a flash loader, to make sure instructions are fetched from flash instead of ICACHE after the setting of flash breakpoints.
- Renesas RZ/N2L device series: CFI flash programming did not work for addresses ranges larger than 0x1FFFFF. Fixed.
- ST STM32H7x0: Chip erase could run into a timeout. Fixed.
DLL
- ST STM32H7: Connect with an older J-Link model (e.g. J-Link Ultra V4) erroneously failed with the error message "J-Link does not support requested memory access". Introduced in V7.96r. Fixed.
J-Flash
- SEGGER Flash Loader (SFL): Improved error handling in case of RAMCode could not be downloaded to the RAM.
J-Scope
- Increased maximum number of data points per symbol to ~8 million (8 * 1024 * 1024).
Trace
- Added native trace buffer support for ST SR5E1 device series.
- Added native trace buffer support for ST STM32H7S3 series.
Version V7.98b (2024-07-31)
Highlights:
Device Provisioner
- GigaDevice GD32F4(except GD32F403) and GD32A4 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32A4_GD32F4_Option_Bytes_Programming)
- GigaDevice GD32F5 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32F5_Option_Bytes_Programming)
- GigaDevice GD32H7 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32H7_Option_Bytes_Programming)
- GigaDevice GD32VW5 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32VW5_Option_Bytes_Programming)
- GigaDevice GD32W5 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32W5_Option_Bytes_Programming)
Device Support
- NXP iMX91 series: Added debug support (https://wiki.segger.com/NXP_i.MX_91).
Other changes:
Device Support
- AlifSemi AE302F40C1537_HP: Device name mistakenly connected to HE core instead of HP core. Fixed.
- Analog Devices (CM4xx): Added full part numbers to the device selection dialog.
- Infineon PSoC4 CY8C4046xxx: Work-RAM size not set correctly. Fixed.
- Infineon PSoC4: Under certain circumstances, connect could fail. Introduced in V7.96j. Fixed.
- NXP iMX8M Mini Cortex-M4: Attach to a running target caused memory rewrite. Fixed.
- Renesas RA4E1, RA4E2, RA4L1, RA4M2, RA4M3, RA4T1 device series: Reset was not handled correctly in NSECSD state. Fixed.
- Renesas RA6E1, RA6E2, RA6M4, RA6M5, RA6T2, RA6T3 device series: Reset was not handled correctly in NSECSD state. Fixed.
- Renesas RA8D1, RA8M1, RA8T1 device series: Reset was not handled correctly in NSECSD state. Fixed.
- Renesas RZ/T2 device series: CFI flash programming did not work for addresses ranges larger than 0x1FFFFF. Fixed.
- ST STM32G0: Under certain circumstances option byte programming could fail. Fixed.
- Xilinx Zynq UltraScale+: Added support for "attach to a running target" for Cortex-A53 and Cortex-R5 cores.
GDB Server
- In some cases GDB Server did not handle semihosting requests with ioclient 2 correctly.
J-Flash
- Depending on the command line, the process exit code could be 0 even if an error occurred (false positive). Fixed.
J-Flash SPI
- Added command line option "-hide" which starts J-Flash SPI hidden (https://wiki.segger.com/J-Flash_SPI#Command_line_options).
- Depending on the command line, the process exit code could be 0 even if an error occurred (false positive). Fixed.
Version V7.98a (2024-07-17)
Configurator
- Added support for CMSIS-DAPv2 boot mode.
Device Support
- Added debug support for Xilinx Zynq UltraScale+ Cortex-R5_1 core.
- Added device names for Xilinx Zynq UltraScale+ CG series: XCZU1CG_R5_0, XCZU3TCG_R5_0.
- Added device names for Xilinx Zynq UltraScale+ CG series: XCZU1CG_R5_1, XCZU2CG_R5_1, XCZU3CG_R5_1, XCZU3TCG_R5_1, XCZU4CG_R5_1, XCZU5CG_R5_1, XCZU6CG_R5_1, XCZU7CG_R5_1, XCZU9CG_R5_1.
- Added device names for Xilinx Zynq UltraScale+ DR series: XCZU21DR_R5_1, XCZU25DR_R5_1, XCZU27DR_R5_1, XCZU28DR_R5_1, XCZU29DR_R5_1, XCZU39DR_R5_1, XCZU42DR_R5_1, XCZU43DR_R5_1, XCZU46DR_R5_1, XCZU47DR_R5_1, XCZU48DR_R5_1, XCZU49DR_R5_1, XCZU63DR_R5_1, XCZU64DR_R5_1, XCZU65DR_R5_1, XCZU67DR_R5_1.
- Added device names for Xilinx Zynq UltraScale+ DR series: XCZU42DR_R5_0, XCZU43DR_R5_0, XCZU63DR_R5_0, XCZU64DR_R5_0, XCZU65DR_R5_0, XCZU67DR_R5_0.
- Added device names for Xilinx Zynq UltraScale+ EG series: XCZU1EG_R5_0, XCZU3TEG_R5_0.
- Added device names for Xilinx Zynq UltraScale+ EG series: XCZU1EG_R5_1, XCZU2EG_R5_1, XCZU3EG_R5_1, XCZU3TEG_R5_1, XCZU4EG_R5_1, XCZU5EG_R5_1, XCZU6EG_R5_1, XCZU7EG_R5_1, XCZU9EG_R5_1, XCZU11EG_R5_1, XCZU15EG_R5_1, XCZU17EG_R5_1, XCZU19EG_R5_1.
- Added device names for Xilinx Zynq UltraScale+ EV series: XCZU4EV_R5_1, XCZU4EV_R5_1, XCZU5EV_R5_1, XCZU7EV_R5_1
- Renesas RA8: Under special circumstances (non secure mode), flash programming failed. Introduced in V7.96n. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V12: Added support for CMSIS-DAPv2 boot mode.
- J-Link PRO PoE V6: Added support for CMSIS-DAPv2 boot mode.
- J-Link PRO V6: Added support for CMSIS-DAPv2 boot mode.
- J-Link ULTRA+ V6: Added support for CMSIS-DAPv2 boot mode.
- J-Link WiFi V2: Added support for CMSIS-DAPv2 boot mode.
Version V7.98 (2024-07-17)
Device Support
- Renesas RA8: OSPI flash erase could fail with S28HS512T flash. Fixed.
- STM32H743xx: Under special circumstances the erase operation could fail. Fixed.
J-Flash
- Files and folders uploaded to the root folder of a Flasher using the Flasher file dialog (File --> Show files on Flasher...) were stored with "(null)" placed in front of the actual file name. Introduced with V7.96s. Fixed.
J-Flash SPI
- Files and folders uploaded to the root folder of a Flasher using the Flasher file dialog (File --> Show files on Flasher...) were stored with "(null)" placed in front of the actual file name. Introduced with V7.96s. Fixed.
Version V7.96t (2024-07-11)
Commander
- After trying to connect with an unknown device, a device selection dialog box was shown. The selected device was only used for the current session and discarded in further connects. Fixed.
Control Panel
- SWV tab did not display the host buffer size correctly. Fixed.
Device Support
- NXP iMXRT1180: When connecting to the Cortex-M7, RAM init could fail under special circumstances. Fixed.
- SEGGER WireCheck: Did not start and raises "No flash banks defined in U-Flash project". Fixed.
DLL
- Added J-Link command string "SWOSetHostBufferSize". (https://wiki.segger.com/J-Link_Command_Strings#SWOSetHostBufferSize)
- Trying to set a data breakpoint (watchpoint) could indicate success, even if setting the data breakpoint failed (e.g. due to data breakpoints not being supported). Fixed.
J-Flash
- Downloading Flasher files to modules connected to a Flasher Hub-4 would fail with an error message 'The connected probe/ programmer is not a gang programmer [...]'. Fixed.
- Downloading Flasher files would store files with "(null)" placed in front of the actual file name on the Flasher. Introduced with V7.96s. Fixed.
- In project settings dialog changing the organization of for CFI banks (Bits/Chips) did not have any effect. Fixed.
- Under certain circumstances programming CFI NOR flashes could fail in Flasher standalone mode due to misconfigured configuration file. Fixed.
J-Flash SPI
- Added support for ST M95320 EEPROM.
- Downloading Flasher files to modules connected to a Flasher Hub-4 would fail with an error message 'The connected probe/ programmer is not a gang programmer [...]'. Fixed.
- Downloading Flasher files would store files with "(null)" placed in front of the actual file name on the Flasher. Introduced with V7.96s. Fixed.
J-Scope
- Interface dropdown menu was empty when selecting FINE interface. Fixed.
- Sampling speed input accepted characters. Fixed.
Trace
- Added StartNTRACEATB/StopNTRACEATB JLinkScript file functions to be able to replace internal generic trace related N-Trace ATB sink initialization.
- Added StartNTRACEPIB/StopNTRACEPIB JLinkScript file functions to be able to replace internal generic trace related N-Trace pin sink initialization.
- Added StartNTRACESRAM/StopNTRACESRAM JLinkScript file functions to be able to replace internal generic trace related N-Trace SRAM sink initialization.
- Added StartNTRACETE/StopNTRACETE JLinkScript file functions to be able to replace internal generic trace related N-Trace trace encoder initialization.
- Added StartNTRACETF/StopNTRACETF JLinkScript file functions to be able to replace internal generic trace related N-Trace trace funnel initialization.
Version V7.96s (2024-07-04)
Control Panel
- After submitting a form and refreshing the page in the browser, the last form was resubmitted. Fixed.
DLL
- macOS would segfault when starting DLL. Introduced in V7.96q. Fixed.
J-Scope
- Changes to settings were not being applied. Fixed.
Remote Server
- Added periodic keep alive sequence between remote server and tunnel server while no client is connected to the registered remote server instance.
- Clicking on menu items had no effect. Fixed.
Remote Server CL
- Added periodic keep alive sequence between remote server and tunnel server while no client is connected to the registered remote server instance.
Version V7.96r (2024-07-04)
Highlights:
Device Support
- Microchip PIC32CX BZ2: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32CX_BZ2).
Other changes:
Device Support
- TI CC2340: Under certain circumstances (e.g. target power removed while connecting to the target), connect step could hung. Fixed.
DLL
- Cortex-M (e.g. Cortex-M4): When streaming trace was active, the CYCCNT register could display incorrect/unexpected values displayed (e.g. in SEGGER Embedded Studio). Fixed.
- Under certain circumstances, selecting a device with a preselected loader (e.g. "MIMXRT685S?BankAddr=0x08000000&Loader=Port_A&BankAddr=0x18000000&Loader=Port_A") would fail. Fixed.
Firmware
- ARMvx-M (e.g. Cortex-M4/M33/...): Increased module version to 3: Added support for zoned memory accesses in CoreSight SoC-600 setups.
- Flasher ARM V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher ARM V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher ARM V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher Compact V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher Portable PLUS V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher PRO V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher PRO V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher PRO V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher PRO XL V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher PRO XL V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- Flasher PRO XL V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link EDU Mini V1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link EDU/BASE/PLUS V12: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link PRO PoE V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link PRO V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link PRO V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link PRO V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link ULTRA+ V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link ULTRA+ V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link ULTRA+ V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link WiFi V1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link WiFi V2: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link-OB-K22-CortexM: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link-OB-RA4M2-CortexM: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link-OB-RA4M2-Full: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link-OB-RA4M2-Renesas: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Link-OB-S124: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Trace PRO V3 Cortex: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Trace PRO V3 CortexM: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- J-Trace PRO V3: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
- MCU-Link on-board: Added support for second VCOM interface (VCOM1) on i.MX RT700 boards.
- MCU-Link Pro: Added support for second VCOM interface (VCOM1).
J-Flash
- When saving a Flasher config file for a project with a reference to an erroneous J-Link script file, J-Flash could crash. Fixed.
J-Flash SPI
- Project settings: Setup --> Init/ Exit steps: The "Value1" column showed cut off text for steps with a bytestream that exceeded 12 bytes in length. Fixed.
- Raised max. number of bytes for the "Write Data" custom init/ exit step from 15 to 16 bytes.
Version V7.96q (2024-06-28)
Highlights:
Configurator
- Added options to enable/disable the FTP, Web, and Telnet server.
Other changes:
Device Support
- Renesas RA4M2, RA4M3, RA6M4, RA6M5, RA6E1, RA4E1: Added out of the box SWO support.
DLL
- macOS would segfault when starting DLL. Introduced in V7.96o. Fixed.
Version V7.96p (2024-06-27)
Device Support
- ST STM32U5 devices series: Programming of internal flash memory could fail. Fixed.
J-Flash SPI
- Chip Erase could not be executed when using a manual configuration. Fixed.
Version V7.96o (2024-06-26)
Highlights:
Device Support
- GigaDevice GD32A490: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32A4).
- GigaDevice GD32F5: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32F5).
- NXP MCX C: Added debug and flash programming support (https://wiki.segger.com/NXP_MCX_C).
- NXP MCX W: Added debug and flash programming support (https://wiki.segger.com/NXP_MCX_W).
- XHCS HC32L19x: Added debug and flash programming support(https://wiki.segger.com/XHSC_HC32L19x).
Other changes:
Device Support
- CVA BlueWhale CVM012x: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM012x).
- Geehy G32A series: The device was detected as unkown device when connecting via JTAG. Fixed.
- Infineon Traveo T2G: Programming the flash memory could fail due to a timeout. Fixed.
- Renesas R9A02G021: Programming of config flash area did not work. Fixed.
- ST STM32H7Ax: Readout protection level was reset on every flash access by J-Flash. Fixed.
- TI CC2340: Connect to a locked device could fail. Fixed.
- TI CC2340: Under certain circumstances (e.g. target power removed while programming), flash programming could hung in stand-alone mode operation. Fixed.
Firmware
- ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): Increased module version to 13: AArch64: Wrong value could be returned for SP, SP_EL0, SP_EL1, SP_EL2, SP_EL3 depending on active exception level (EL) and stack pointer selection (PSTATE.SP). Fixed.
- Flasher ARM V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher ARM V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher ARM V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher Compact V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher Portable PLUS V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher PRO V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher PRO V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher PRO V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher PRO XL V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher PRO XL V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- Flasher PRO XL V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link EDU Mini V1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link EDU/BASE/PLUS V12: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link PRO PoE V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link PRO V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link PRO V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link PRO V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link ULTRA+ V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link ULTRA+ V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link ULTRA+ V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link WiFi V1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link WiFi V2: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link-OB-K22-Cortex-A: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link-OB-K22-NordicSemi: Added WinUSB (driverless) mode support.
- J-Link-OB-nRF5340-NordicSemi: Added WinUSB (driverless) mode support.
- J-Link-OB-RA4M2-Full: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Link-OB-SAM3U128-NordicSemi: Added WinUSB (driverless) mode support.
- J-Trace PRO V3 Cortex: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
- J-Trace PRO V3: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
GDB Server
- ARMv8.1-M (e.g. Cortex-M85): Added support for Pointer Authentication and Branch Target Identification Extension (PACBTI) registers.
Version V7.96n (2024-06-20)
Commander
- Added command "BootMode" (https://wiki.segger.com/J-Link_Commander#BootMode).
Device Support
- Cmsemicon CMS32H6157: Added debug and flash programming support.
- NXP NCJ29D5: Programming of TX configuration flash failed. Fixed.
DLL
- RISC-V: Added support for DSCRATCH1 register.
- RISC-V: J-Link would attempt to read optional register DSCRATCH0 even if it is not available. Fixed.
Firmware
- Flasher ARM V5-1: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher ARM V5-1: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher ARM V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher ARM V5: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher ARM V6: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher ARM V6: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher Compact V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher Compact V5: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher Portable PLUS V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher Portable PLUS V5: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher PRO V5-1: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher PRO V5-1: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher PRO V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher PRO V5: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher PRO V6: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher PRO V6: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher PRO XL V5-1: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher PRO XL V5-1: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher PRO XL V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher PRO XL V5: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
- Flasher PRO XL V6: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
- Flasher PRO XL V6: Terminal: #SELECT: The identification of project type (CFG/UNI) was inaccurate. Project files were always identified as UNI if the name contained a period. Fixed.
J-Flash
- Enabled the download of RAMLess based flash loaders to the Flasher.
- Parallel NOR flash: Numonyx M58WR series flash devices did not work correctly. Fixed.
J-Link Package
- Windows: Added Microsoft redistributable DLL files to shipment.
Version V7.96m (2024-06-19)
Highlights:
Device Support
- GigaDevice GD32L235: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32L235).
- HPMicro HPM6330xCEx, HPM6364xDCx: Added debug and (QSPI) flash programming support (https://wiki.segger.com/HPMicro_HPM63).
- HPMicro HPM6454, HPM64A0, HPM64G0: Added debug and (QSPI) flash programming support (https://wiki.segger.com/HPMicro_HPM64).
- HPMicro HPM6E devices series: Added debug and (QSPI) flash programming support (https://wiki.segger.com/HPMicro_HPM6E).
- TI CC2340R2: Added debug and flash programming support (https://wiki.segger.com/TI_CC2340).
Trace
- Published out-of-the-box trace example for NXP LPC1766: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Renesas RA4M3: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Renesas RA8D1: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- Microchip PIC32CX1025SG: Debugging / flash programming did not work in case of reset extension phase was active. Fixed.
- NXP iMX95 series: Incorrect AP map configuration for Cortex-M33 and Cortex-M7. Fixed.
- ST STM32H74x, STM32H75x devices series: Under certain circumstances standalone flash programming could fail. Fixed.
Firmware
- Flasher ARM V5-1: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher ARM V5-1: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher ARM V5-1: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher ARM V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher ARM V5: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher ARM V5: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher ARM V6: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher ARM V6: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher ARM V6: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher Compact V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher Compact V5: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher Compact V5: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher Hub-12 V1: Added terminal command #RMDIR: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23RMDIR .
- Flasher Hub-12 V1: Improved speed when removing files and folders from a module by removing the respective "MODULE.*" folder.
- Flasher Hub-12 V1: Removing the "All modules" folder now removes all files and folders from all connected modules.
- Flasher Hub-12 V1: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher Hub-12 V1: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher Hub-12 V1: Wrong contents were displayed for the 'MODULE.024' folder. Introduced in V7.96l. Fixed.
- Flasher Hub-4 V1: Added terminal command #RMDIR: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23RMDIR .
- Flasher Hub-4 V1: Improved speed when removing files and folders from a module by removing the respective "MODULE.*" folder.
- Flasher Hub-4 V1: Removing the "All modules" folder now removes all files and folders from all connected modules.
- Flasher Hub-4 V1: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher Hub-4 V1: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher Hub-4 V1: Wrong contents were displayed for the 'MODULE.024' folder. Introduced in V7.96l. Fixed.
- Flasher Portable PLUS V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher PRO V5-1: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher PRO V5-1: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher PRO V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher PRO V5: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher PRO V5: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher PRO V6: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher PRO V6: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher PRO V6: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher PRO XL V5-1: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher PRO XL V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher PRO XL V5: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- Flasher PRO XL V6: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
- Flasher PRO XL V6: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
- Flasher PRO XL V6: Stand-alone mode: Reset could erroneously fail on ARMv8-M based cores when using JTAG as target interface (e.g. Renesas RA8 series). Fixed.
- J-Link-OB-RA4M2-Full: RISC-V: Added support for Cadence Xtensa based cores.
Version V7.96l (2024-06-12)
Highlights:
Device Support
- AmbiqMicro Apollo4 Blue Lite AMA4B2KL-KXR: Added debug & flash programming support.
- AmbiqMicro Apollo4 Lite AMAP42KL-KBR: Added debug & flash programming support.
- NXP iMX93 series: Added debug support for the Cortex-A55 and Cortex-M33 cores (https://wiki.segger.com/NXP_i.MX_93).
- NXP iMX95 series: Added debug support for the Cortex-A55, Cortex-M33 and Cortex-M7 cores (https://wiki.segger.com/NXP_i.MX_95).
Other changes:
Device Support
- AlifSemi E3/E5/E7 device series: Changed J-Links WorkRAM to 0x20000000.
- GigaDevice GD32E235: Added debug and flash programming support(https://wiki.segger.com/GigaDevice_GD32E2).
- NXP S32K310: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
- Renesas RZ/T2M: Increased max. CFI NOR flash size to 32MB.
- TI TMS570LS10106/206: Flash functions (Erase, Programming, Verify, Read, ...) failed. Fixed.
DLL
- DLL could crash if an error occurred during the execution of JLINKARM_ExecCommand() (e.g., when a given script file was not found). Fixed.
Firmware
- Flasher ARM V5-1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher ARM V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher ARM V6: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher Compact V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher Hub-12 V1: Added terminal command #FCLOSE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FCLOSE .
- Flasher Hub-12 V1: Added terminal command #FCRC: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FCRC .
- Flasher Hub-12 V1: Added terminal command #FDELETE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FDELETE .
- Flasher Hub-12 V1: Added terminal command #FLIST: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FLIST .
- Flasher Hub-12 V1: Added terminal command #FOPEN: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FOPEN .
- Flasher Hub-12 V1: Added terminal command #FREAD: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FREAD .
- Flasher Hub-12 V1: Added terminal command #FSIZE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FSIZE .
- Flasher Hub-12 V1: Added terminal command #FWRITE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FWRITE .
- Flasher Hub-12 V1: Added terminal command #MKDIR: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23MKDIR .
- Flasher Hub-12 V1: FTP and Web clients ('Files' tab) can now work on the Flasher Hub file system without restrictions (e.g. upload files into root folder).
- Flasher Hub-12 V1: FTP and Web clients ('Files' tab) now see Flasher Hub file system contents unfiltered.
- Flasher Hub-12 V1: Implemented terminal command #FFORMAT: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FFORMAT .
- Flasher Hub-12 V1: Renamed feature from "Module terminal server" to "Status port".
- Flasher Hub-12 V1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher Hub-12 V1: Terminal: Running the #FCRC command on a file under "All modules" now calculates the CRC for the given file on each connected module.
- Flasher Hub-12 V1: WebIF: "Configuration > Flasher Hub": Uploading a firmware update file did not work correctly if a path other than the root path was selected in the "Files" tab. Fixed.
- Flasher Hub-12 V1: WebIF: "Files" tab: For some paths (e.g. root folder), uploading files and folders was not enabled. Fixed.
- Flasher Hub-12 V1: WebIF: "Files" tab: The "Logs" folder could not be removed. Fixed.
- Flasher Hub-12 V1: WebIF: "Files" tab: When the current folder was on a module that was busy (e.g. UART port enabled), no warning message was shown. Fixed.
- Flasher Hub-12 V1: WebIF: After submitting a form (e.g. saving the Flasher Hub configuration) and refreshing the page in the browser, the last form was resubmitted. Fixed.
- Flasher Hub-4 V1: Added terminal command #FCLOSE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FCLOSE .
- Flasher Hub-4 V1: Added terminal command #FCRC: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FCRC .
- Flasher Hub-4 V1: Added terminal command #FDELETE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FDELETE .
- Flasher Hub-4 V1: Added terminal command #FLIST: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FLIST .
- Flasher Hub-4 V1: Added terminal command #FOPEN: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FOPEN .
- Flasher Hub-4 V1: Added terminal command #FREAD: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FREAD .
- Flasher Hub-4 V1: Added terminal command #FSIZE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FSIZE .
- Flasher Hub-4 V1: Added terminal command #FWRITE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FWRITE .
- Flasher Hub-4 V1: Added terminal command #MKDIR: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23MKDIR .
- Flasher Hub-4 V1: FTP and Web clients ('Files' tab) can now work on the Flasher Hub file system without restrictions (e.g. upload files into root folder).
- Flasher Hub-4 V1: FTP and Web clients ('Files' tab) now see Flasher Hub file system contents unfiltered.
- Flasher Hub-4 V1: Implemented terminal command #FFORMAT: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FFORMAT .
- Flasher Hub-4 V1: Renamed feature from "Module terminal server" to "Status port".
- Flasher Hub-4 V1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher Hub-4 V1: Terminal: Running the #FCRC command on a file under "All modules" now calculates the CRC for the given file on each connected module.
- Flasher Hub-4 V1: WebIF: "Configuration > Flasher Hub": Uploading a firmware update file did not work correctly if a path other than the root path was selected in the "Files" tab. Fixed.
- Flasher Hub-4 V1: WebIF: "Files" tab: For some paths (e.g. root folder), uploading files and folders was not enabled. Fixed.
- Flasher Hub-4 V1: WebIF: "Files" tab: The "Logs" folder could not be removed. Fixed.
- Flasher Hub-4 V1: WebIF: "Files" tab: When the current folder was on a module that was busy (e.g. UART port enabled), no warning message was shown. Fixed.
- Flasher Hub-4 V1: WebIF: After submitting a form (e.g. saving the Flasher Hub configuration) and refreshing the page in the browser, the last form was resubmitted. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher PRO V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher PRO V6: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- Flasher PRO XL V6: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
- J-Link PRO PoE V6: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
- J-Link PRO V5-1: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
- J-Link PRO V5: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
- J-Link PRO V6: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
- J-Link ULTRA+ V5-1: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
- J-Link ULTRA+ V5: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
- J-Link ULTRA+ V6: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
J-Flash
- Added link to SEGGER Wiki to error message box that is shown when selected data does not fit into the selected sectors.
J-Flash SPI
- Host-based mode: Fixed timeouts were always used, although overwrite timeouts were configured. Fixed.
Version V7.96k (2024-06-05)
Highlights:
Device Support
- Infineon WLC: Added debug and flash programming support (https://wiki.segger.com/Infineon_WLC).
- Nuvoton KM1M0DF: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M0DF).
- Nuvoton KM1M7CF: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M7CF).
Other changes:
Device Support
- Puya P25Q32: QSPI flash loaders were using incorrect flash size (16 Mbit instead of 32 Mbit). Fixed.
- Puya PY25Q16HB: QSPI flash loaders did not detect the flash. Fixed.
DLL
- "SuppressGUI" command string did not suppress device selection dialog. Fixed.
- MacOS: In some cases, a J-Link could show a nickname even though no nickname is configured. Fixed.
Firmware
- Flasher ARM V5-1: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher ARM V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher ARM V6: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher Compact V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher Hub-12 V1: Enabled terminal via USB BULK (e.g. FlasherControl utility).
- Flasher Hub-4 V1: Enabled terminal via USB BULK (e.g. FlasherControl utility).
- Flasher Portable PLUS V5: Some PCode reports were forwarded to a file instead of an ASCII terminal. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher PRO V5-1: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher PRO V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher PRO V6: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher PRO XL V5-1: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher PRO XL V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
- Flasher PRO XL V6: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
Version V7.96j (2024-05-29)
Highlights:
Device Support
- Microchip PolarFire SOC series: Added debug support for RISC-V E51 and U54 cores (https://wiki.segger.com/Microchip_PolarFire_SOC).
- NXP QN9080D: Added flash programming support.
- ST STM32H7S3/S7/R3/R7: Added debug and flash (User & XSPI2) programming support (https://wiki.segger.com/ST_STM32H7).
Other changes:
Device Support
- Infineon PSoC4: Attach was not possible because the acquisition sequence (+ reset) was executed always on connect. Changed to execute it only if necessary (standard connect not possible).
- NXP S32K3xx: In multi-core setups with multiple sessions to different cores involved, flash programming could fail with "Failed to preserve target RAM @ 0x20000000-0x20007FFF" error. Fixed.
- ST STM32H7: Programming the internal program flash with D-Cache enabled could (erroneously) lead to verification errors caused by improper cache handling. Fixed.
DLL
- Microchip PolarFire RISC-V TAP was not detected as a known CPU-TAP. Fixed.
- RISC-V: Added support for RISC-V JTAG TAPs with != 5-bit IRLen.
- Using HSS with exactly 16 variables would cause a crash. Fixed.
DnD Conditioner
- Command-line description was incorrect. Fixed.
Firmware
- Flasher ARM V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher ARM V5-1: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher ARM V5-1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher ARM V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher ARM V5: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher ARM V5: U-Flash: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher ARM V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher ARM V6: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher ARM V6: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher Compact V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher Compact V5: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher Hub-12 V1: Added terminal command #RESTART: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23RESTART .
- Flasher Hub-12 V1: Implemented UART Port: https://wiki.segger.com/Flasher_Hub_-_UART_Port .
- Flasher Hub-12 V1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher Hub-4 V1: Added terminal command #RESTART: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23RESTART .
- Flasher Hub-4 V1: Implemented UART Port: https://wiki.segger.com/Flasher_Hub_-_UART_Port .
- Flasher Hub-4 V1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher Portable PLUS V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher Portable PLUS V5: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher PRO V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher PRO V5-1: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher PRO V5-1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher PRO V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher PRO V5: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher PRO V5: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher PRO V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher PRO V6: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher PRO V6: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher PRO XL V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher PRO XL V5-1: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher PRO XL V5-1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher PRO XL V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher PRO XL V5: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher PRO XL V5: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- Flasher PRO XL V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
- Flasher PRO XL V6: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
- Flasher PRO XL V6: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
- J-Link EDU Mini V1: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link EDU/BASE/PLUS V12: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link PRO PoE V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link PRO V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link PRO V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link PRO V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link ULTRA+ V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link ULTRA+ V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link ULTRA+ V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link WiFi V1: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link WiFi V2: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link-OB-K22-RISCV: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link-OB-RA4M2-Full: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Link-OB-RA4M2-Renesas: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Trace PRO V3 Cortex: RISC-V: Rebuilt firmware with RISC-V module version 3.
- J-Trace PRO V3: RISC-V: Rebuilt firmware with RISC-V module version 3.
- MCU-Link-OB: UART transfers with high baud rates (>= 115200) could lead to dropped bytes. Fixed.
- MCU-Link: UART transfers with high baud rates (>= 115200) could lead to dropped bytes. Fixed.
- RISC-V: Increased module version to 3: Added support for RISC-V JTAG TAPs with != 5-bit IRLen.
GDB Server
- Cortex-M: Registers s0-s31 could be exposed twice. Fixed.
J-Flash
- When uploading files from a Flasher to the host using the Flasher file dialog (File -> "Show files on Flasher..."), the progress dialog text was incorrect. Fixed.
J-Flash SPI
- GUI: When uploading files from a Flasher to the host using the Flasher file dialog (File -> "Show files on Flasher..."), the progress dialog text was incorrect. Fixed.
J-Link Package
- Linux: TGZ binary archive: J-Scope was missing. Fixed.
J-Run
- The PC and SP were not set in some cases. Fixed.
J-Scope
- When the sampling buffer was full while sampling with RTT, previous timestamps were overwritten. Fixed.
Version V7.96i (2024-05-22)
Highlights:
Device Support
- GigaDevice GD32A503/513x: Added flash programming support for Data Flash (https://wiki.segger.com/GigaDevice_GD32A5).
- GigaDevice GD32A503/513x: Added flash programming support for Option Byte 1 (https://wiki.segger.com/GigaDevice_GD32A5).
- NXP NCJ29D5: Added flash programming support for Rx, Tx and custom configuration(https://wiki.segger.com/NXP_NCJ29D5).
Trace
- Published out-of-the-box trace example for Silicon Labs EFR32MG24: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for ST STM32H757: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Provisioner
- PCode_DevPro_ST_STM32U0.pex script file was missing in shipment package. Fixed.
Device Support
- Geehy G32A1465: Program flash size was incorrect (512 KB instead of 1024 KB). Fixed.
- Renesas RZ/T2L: Flash programming for XSPI1 did not work. Fixed.
Firmware
- Flasher Hub-12 V1: NULL packet handling when communicating with modules was not correct, which could lead to USB timeouts. Fixed.
- Flasher Hub-12 V1: WebIF: Updated Flasher Compact picture.
- Flasher Hub-4 V1: NULL packet handling when communicating with modules was not correct, which could lead to USB timeouts. Fixed.
- Flasher Hub-4 V1: WebIF: Updated Flasher Compact picture.
- Flasher Hub-4 V1: WebIF: Updated Flasher Hub picture.
J-Flash Lite
- A white box was floating in the top left corner of the main window. Introduced in V7.96h. Fixed.
Version V7.96h (2024-05-15)
Highlights:
Device Provisioner
- ST STM32H523/533 series: Added life-cycle management and provisioning support (https://wiki.segger.com/ST_STM32H5_Security_Product_Lifecycle).
- ST STM32U031/073/083 series: Added support for option-bytes programming, password management and device locking/unlocking (https://wiki.segger.com/ST_STM32U0_Option_Bytes_Programming)
Device Support
- Infineon PMG1-B1 CYPM1115/1116: Added debug and flash programming support (https://wiki.segger.com/Infineon_PMG1).
- ISSI IS25LP02G: Added flash programming support.
- Macronix MX25V4035F: Added flash programming support.
- Microchip SAMA7D65: Added debug support.
J-Flash SPI
- Added support for SPI EEPROM with 3 address byte mode (e.g. M95M01).
- ISSI IS25LP02G: Added flash programming support.
- Macronix MX25V4035F: Added flash programming support.
Other changes:
Device Support
- AlifSemi E1: Previous fix for OSPI flash loader not handling flash sizes > 64 MB correctly was incomplete. Fixed.
- Qorvo QPG5072: Programming failed because chip was not correct identified. Fixed.
- Renesas RA2A2: Depending on the application running on the target, the data flash could not be programmed. Fixed.
- TI MSPM0: Connect failed in case of the low power mode was active (e.g. 10 second after reset release in case of flash was empty). Fixed.
J-Flash SPI
- When changing the flash type (e.g. SPI NOR flash --> SPI EEPROM), the default settings were not loaded. Fixed.
Version V7.96g (2024-05-08)
Highlights:
Device Support
- GigaDevice GD32A513: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32A5).
- GigaDevice GD32W515 : Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32W515).
- Macronix MX25UW25645G: Added flash programming support for SPIFI flash loaders.
- Macronix MX66UW1G45G: Added flash programming support for SPIFI flash loaders.
- Microchip SAMA7G54: Added device support for SAMA7G54D1G and SAMA7G54D2G.
- NXP iMX8MNano series: Added debug support for the Cortex-A53 cores (https://wiki.segger.com/NXP_i.MX_8M_Nano).
- ST STM32U031/073/083 series: Added debug and flash programming support (https://wiki.segger.com/ST_STM32U0).
Trace
- Published out-of-the-box trace example for Nuvoton KM1M4BF and KM1M7AF: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for ST STM32H563 series: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- Added support for Fidelix FM25M4AA.
- AlifSemi E1: OSPI flash loader did not handle flash sizes > 64 MB. Fixed.
- Artery AT32A403/F403/F407: Added RAM @ 0x20000000 (96 KB) to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in this RAM section.
- Artery AT32F413: Added RAM @ 0x20000000 (64 KB) to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in this RAM section.
- GigaDevice GD32F310/GD32F330/GD32F350: Added option byte flash programming support.
- GigaDevice GD32H7: In case of DTCM RAM was disabled, flash programming failed. Fixed.
- Microchip PIC32CX: Added debug and flash programming support for PIC32CX1025SG41064 (https://wiki.segger.com/Microchip_PIC32CX).
- NXP S32K396: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
- Renesas RA8x1: Under certain circumstances, reset failed in non-secure debug. Fixed.
- Renesas S7G2 device series: Blank checking of option-setting memory could return wrong result (Introduced with V7.92e). Fixed.
- ST SR5E1E5: Added debug and flash programming support (https://wiki.segger.com/J-Link_ST_SR5E1).
- ST STM32H74xx, STM32H75xx device series: Added QSPI flash programming support for pin configuration "CLK@PB2_nCS@PB6_D0@PD11_D1@PD12_D2@PE2_D3@PD13".
DLL
- ARMv8-M: In case of reset is not allowed (switching from non-secure debug to secure debug is prohibited and reset in non-secure debug is disabled), reset returned an error (https://wiki.segger.com/J-Link_ARMv8-M#Non-secure_debug_access). Fixed.
- ARMv8-M: Under special circumstances, the DLL erroneously assumed that the reset has confused the core. Fixed.
Firmware
- Flasher ARM V5-1: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher ARM V5: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher ARM V6: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher Compact V5: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher Hub-12 V1: WebIF: Saving a Flasher Hub configuration while one or more modules were busy could lead to some modules being stuck with "Configuration" as their activity. Fixed.
- Flasher Hub-4 V1: WebIF: Saving a Flasher Hub configuration while one or more modules were busy could lead to some modules being stuck with "Configuration" as their activity. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher PRO V5-1: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher PRO V5: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher PRO V6: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher PRO XL V5: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
- Flasher PRO XL V6: Stand-alone mode: Programming / Verifying could fail if target device had multiple flash banks and more than 1 bank was programmed (e.g. Renesas RA6M4 and RA series in general). Fixed.
GDB Server
- -noGUI command line option did not disable all J-Link DLL dialogs. Fixed.
- ARMv8.1-M (e.g. Cortex-M85): Added support for M-profile Vector Extension (also known as Helium) registers vpr, p0, q0-q7.
J-Flash
- Chip Erase did not work for STM32H7xxxI series dual bank devices. Fixed.
J-Flash SPI
- PC-based mode: Programming pages with single SPI failed if no "Init commands" were specified. Introduced with V7.96c. Fixed.
J-Flash SPI CL
- PC-based mode: Programming pages with single SPI failed if no "Init commands" were specified. Introduced with V7.96c. Fixed.
J-Run
- J-Run could have had unexpected behavior because it did not set the program counter. Fixed.
- J-Run was experiencing issues when Thumb-bit was set on Semihosting address. Fixed.
J-Scope
- J-Scope erroneously tried to halt the target MCU when sampling was stopped. Fixed.
STM32 Utility
- STM32L4: PCROP_RDP was not reset correctly. Fixed.
- STM32L4: STM32L4+ devices: PCROPxER was not reset correctly. Fixed.
- STM32U5 devices: Application would hang up on selection. Fixed.
Version V7.96f (2024-04-24)
Highlights:
Device Support
- ST STM32U5Fxxx device series: Added debug & flash programming support.
Other changes:
Device Support
- I2C_EEPROM: Alias names added for the all generic I2C devices.
- Microchip PIC32MZ: Programming could fail due to wrong cache handling. Fixed.
- Renesas S7G2 device series: Programming an application image with option-setting memory could lead to manipulated program flash memory. Fixed.
- ST STM32F7 devices series: Flash size for QSPI flashes was erroneously limited to 64 MB instead of 256 MB. Fixed.
- STM32F2xx: The erase operation could fail due too short timeout. Introduced with V7.94a. Fixed.
- TDK Micronas HVC5xxx device series: Improved erase speed for main flash.
DLL
- Setting the "SuppressControlPanel" command string did not work and the control panel was created nonetheless. Fixed.
- Setting the "SuppressGUI" command string did not suppress the control panel. Fixed.
Firmware
- ARMv8-A/R: Increased module version to 12 (CPU_CORTEX_AR_ARMV8.c): When making use of zoned memory accesses on the debug AP (e.g. for trace init), the debug session could be messed up (further go, halt, ... requests did no longer work). Fixed.
- Flasher ARM V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher ARM V5: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher ARM V6: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher Compact V5: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher Hub-12 V1: WebIF: Changed image that depicts a web session to show the Flasher product icon instead of Flasher Hub-12.
- Flasher Hub-12 V1: WebIF: Modules could be selected for firmware update when they were busy. Fixed.
- Flasher Hub-12 V1: WebIF: Updating the firmware of modules connected behind external USB hubs did not work. Fixed.
- Flasher Hub-4 V1: WebIF: Changed image that depicts a web session to show the Flasher product icon instead of Flasher Hub-12.
- Flasher Hub-4 V1: WebIF: Modules could be selected for firmware update when they were busy. Fixed.
- Flasher Hub-4 V1: WebIF: The Flasher Hub-12 image was displayed instead of that for Flasher Hub-4. Fixed.
- Flasher Hub-4 V1: WebIF: Updating the firmware of modules connected behind external USB hubs did not work. Fixed.
- Flasher Portable PLUS V5: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher PRO V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher PRO V5: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher PRO V6: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher PRO XL V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher PRO XL V5: Rebuilt firmware with ARMv8-A/R module version 12.
- Flasher PRO XL V6: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link EDU Mini V1: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link EDU/BASE/PLUS V12: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link PRO PoE V6: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link PRO V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link PRO V5: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link PRO V6: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link ULTRA+ V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link ULTRA+ V5: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link ULTRA+ V6: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link WiFi V1: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link WiFi V2: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link-OB-K22-CortexA: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link-OB-RA4M2-Full: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link-OB-RA4M2-Renesas: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Link-OB-S124: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Trace PRO V3 Cortex: Rebuilt firmware with ARMv8-A/R module version 12.
- J-Trace PRO V3: Rebuilt firmware with ARMv8-A/R module version 12.
J-Flash SPI
- Block protection was cleared even if it was cleared before already (e.g. by a prior Erase), wasting time. Fixed.
- Checking the data to be programmed if it fits into the target memroy was slow (especially for SPI flashes with many sectors), causing gaps between phases (e.g. before Program). Fixed.
- Programming in PC-based mode took more time (ca. 200ms) due to gaps between phases (e.g. between Erase and Program). Fixed.
J-Flash SPI CL
- Block protection was cleared even if it was cleared before already (e.g. by a prior Erase), wasting time. Fixed.
- Checking the data to be programmed if it fits into the target memroy was slow (especially for SPI flashes with many sectors), causing gaps between phases (e.g. before Program). Fixed.
J-Scope
- J-Scope: Added functionality to Highlight a symbol by selecting it in the symbol table.
Version V7.96e (2024-04-17)
Highlights:
Device Support
- SiliconLabs EFM32PG28: Added debug and flash programming support.
- ST STM32H523/533 series: Added debug and flash programming support (https://wiki.segger.com/ST_STM32H5).
Other changes:
Control Panel
- Commander tab: Improved visuals.
Device Support
- AmbiqMicro Apollo 1 devices series: Under certain circumstances, flash operation (erase, program) would fail. Fixed.
- MindMotion MM32SPIN028: Flash programming failed due to an incorrect target RAM size. Fixed.
- NXP JN5189 series: By erasing a single flash sector, the following sector was also erased. Fixed.
- NXP K32W061/41 series: Internal flash: By erasing a single flash sector, the following sector was also erased. Fixed.
- NXP QN9090 series: By erasing a single flash sector, the following sector was also erased. Fixed.
- NXP S32K3xx: Improved device specific handling to initialize the ECC RAM init only on first connect.
- NXP S32K3xx: Improved device specific handling to initialize the ECC RAM not only when connecting to the main core but also to the other cores.
- NXP S32K3xx: Improved device specific handling to support connecting to devices where the main core is disabled.
- Renesas DA1470x: Flash reading/verification did not work correctly with flash devices with size more than 128 Mbit(32-bit adressing mode). Fixed.
- Renesas RA device series: ALeRASE ID code authentication failed in Flasher standalone mode. Fixed.
- Renesas RA8x1: Data flash size was incorrect (1920 KB instead of 2016 KB). Fixed.
- Renesas RA8x1: Under special circumstances (DLM == OEM_PL2 or DLM == OEM_PL1), flash programming could fail. Fixed.
- Renesas RZ/V2H: Some peripherals did not work properly due to an improper initialization on connect. Fixed.
- ST STM32F7 device series: Added support for pin configuration "CLK@PB2_nCS@PB6_D0@PC9_D1@PD12_D2@PE2_D3@PA1".
- ST STM32H74xx/STM32H75xx: Added support for pin configuration "CLK@PF10_nCS@PB10_D0@PF8_D1@PF9_D2@PF7_D3@PF6".
DLL
- Xilinx Zynq UltraScale+: Added debug support for Cortex-A53 cores (https://wiki.segger.com/Xilinx_Zynq_UltraScalePlus).
Firmware
- Flasher ARM V5-1: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher ARM V5: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher ARM V6: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher Compact V5: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher Hub-12 V1: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher Hub-12 V1: Lifted number of max. supported modules from 12 to 24.
- Flasher Hub-12 V1: WebIF "Files" tab: Deleting all files and folders on all modules could take some time, depending on the number of connected modules and files stored on them. Fixed.
- Flasher Hub-12 V1: WebIF "Programming" tab: Starting programming on multiple modules could take same time and lead to the web server temporarily being unreachable. Fixed.
- Flasher Hub-12 V1: WebIF "Programming" tab: Starting programming on multiple modules would start programming with a noticable delay from one module to another. Fixed.
- Flasher Hub-12 V1: WebIF: "Programming" tab: Current programming status was displayed in all uppercase. Fixed.
- Flasher Hub-12 V1: WebIF: Updated GUI of navigation bar.
- Flasher Hub-4 V1: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher Hub-4 V1: Lifted number of max. supported modules from 12 to 24.
- Flasher Hub-4 V1: WebIF "Files" tab: Deleting all files and folders on all modules could take some time, depending on the number of connected modules and files stored on them. Fixed.
- Flasher Hub-4 V1: WebIF "Programming" tab: Starting programming on multiple modules could take same time and lead to the web server temporarily being unreachable. Fixed.
- Flasher Hub-4 V1: WebIF "Programming" tab: Starting programming on multiple modules would start programming with a noticable delay from one module to another. Fixed.
- Flasher Hub-4 V1: WebIF: "Programming" tab: Current programming status was displayed in all uppercase. Fixed.
- Flasher Hub-4 V1: WebIF: Updated GUI of navigation bar.
- Flasher Portable PLUS V5: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher PRO V5-1: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher PRO V5: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher PRO V6: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher PRO XL V5-1: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher PRO XL V5: "Reboot" command in J-Link Commander was not supported. Fixed.
- Flasher PRO XL V6: "Reboot" command in J-Link Commander was not supported. Fixed.
- J-Link OB RA4M2-CortexM: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link OB RA4M2-CortexM: VCOM functionality: Increased the maximum supported baudrate from 1 MBaud to 3 MBaud.
- J-Link OB RA4M2-Full: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link OB RA4M2-Full: VCOM functionality: Increased the maximum supported baudrate from 1 MBaud to 3 MBaud.
- J-Link OB RA4M2-Renesas: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link OB RA4M2-Renesas: VCOM functionality: Increased the maximum supported baudrate from 1 MBaud to 3 MBaud.
- J-Link OB RA4M2-RISCV: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link OB RA4M2-RISCV: VCOM functionality: Increased the maximum supported baudrate from 1 MBaud to 3 MBaud.
- J-Link OB-K22-CortexA: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link OB-K22-CortexM: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link OB-K22-Full: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link OB-K22-Qorvo: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link OB-K22-RISCV: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link-OB-K22-NordicSemi: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link-OB-nRF5340-NordicSemi: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link-OB-SAM3U128-V1: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link-OB-SAM3U128-V2-NordicSemi: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link-OB-SAM3U128-V3: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
- J-Link-OB-STM32F072-Qorvo: If drag & drop enabled: The J-Link stuck in a reset loop when connected to a computer with macOS Sonoma 14.4. Fixed.
Version V7.96d (2024-04-10)
Highlights:
Configurator
- Configuration dialog: Added VCOM information table.
Device Support
- Infineon PSoC 4-BLE: Added debug and flash programming support for the CYBLE-224116-01 device.
- Micronas HVC5422D: Added debug & flash programming support.
- NXP iMX8MPlus series: Added debug support for the Cortex-A53 cores (https://wiki.segger.com/NXP_i.MX_8M_Plus).
- NXP iMX8XLite series: Added debug support for the Cortex-A35 cores (https://wiki.segger.com/NXP_i.MX_8XLite).
- Texas Instruments MSPM0Lx22x: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0L).
- Toshiba TMPM4k (group2): Added debug & flash programming support for the most recent devices from this series.
Other changes:
Device Support
- AlifSemi E3/E5/E7 device series: Added OSPI programming support for IS25WX512.
- GigaDevice GD32F130: RAM size was incorrect. Under certain circumstances, this could result in errors during flash programming. Fixed.
- Renesas RZ/N2L: Programming of CFI NOR flash did not work. Fixed.
- ST STM32U5: Flash programming could fail in Flasher standalone mode. Fixed.
DLL
- JLinkDevices.xml: J-Link DLL erroneously only accepted XML files with non-capitalized file extension (JLinkDevices.xml) instead of accepting both capitalized and non-capitalized file extensions (JLinkDevices.xml + JLinkDevices.XML). Fixed.
- Updated image for Flasher Hub-12 in probe selection dialog.
Firmware
- Flasher Hub-12 V1: Added support for connecting modules behind USB hubs when in flex mode.
- Flasher Hub-12 V1: WebIF "Programming" tab: Starting programming could cause Flasher Hub-12 to become unresponsive when module terminal server was not enabled. Introduced with V7.94k. Fixed.
Version V7.96c (2024-04-02)
Highlights:
Device Support
- Fidelix FM25M64C: Added flash programming support for SPIFI flash loaders.
- ST STM32WBA55 series: Added debug & flash programming support (https://wiki.segger.com/ST_STM32WBA).
DLL
- Added native trace buffer support for Xilinx UltraScale+ Cortex-R5 core.
J-Flash SPI
- Fidelix FM25M64C: Added flash programming support.
Other changes:
Device Support
- Added flash programming support for Infineon CYBLE-222014-01.
- Nuvoton KM1M4: Updated list of supported part numbers / device names.
- Nuvoton KM1M7: Updated list of supported part numbers / device names.
- NXP LPC5460 devices series: Devices with 512 KB internal flash did not handle ECRP accordingly to their device names ("LPC54616J512 (allow ECRP)" did not allow ECRP while "LPC54616J512" did). Introduced with V7.70d. Fixed.
- NXP RT1064: Added debug & flash programming support for silicon revision B (MIMXRT1064xxx5B / MIMXRT1064xxx6B).
- Renesas M16C/62, M16C/62L: Added family support via clock synchronized serial I/O mode.
- ST STM32U5 series devices: Flash programming failed when programming data not aligned to 128 bytes. Fixed.
Firmware
- Flasher ARM V5-1: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher ARM V5-1: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher ARM V5: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher ARM V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher ARM V6: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher ARM V6: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher Compact V5: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher Compact V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher Hub-12 V1: Introduced flex mode, allowing the user to freely choose module positions (https://wiki.segger.com/Flasher_Hub-12_-_Module_Configuration#Flex_mode).
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: The module terminal server base port input field was editable before the input fields were unlocked. Fixed.
- Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: The module terminal server base port input field was visible when the web server connection broke down. Fixed.
- Flasher Hub-12 V1: WebIF: Updated image of Flasher Hub-12.
- Flasher Hub-12 V1: When the module terminal server was enabled, a terminal command (e.g. #AUTO) could make Flasher Hub-12 unresponsive until power-cycled. Fixed.
- Flasher Portable PLUS V5: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher Portable PLUS V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher PRO V5-1: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher PRO V5-1: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher PRO V5: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher PRO V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher PRO V6: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher PRO V6: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher PRO XL V5-1: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher PRO XL V5-1: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher PRO XL V5: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher PRO XL V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- Flasher PRO XL V6: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- Flasher PRO XL V6: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
- J-Link EDU Mini V1: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link EDU/BASE/PLUS V12: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link PRO PoE V6: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link PRO V5-1: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link PRO V5: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link PRO V6: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link ULTRA+ V5-1: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link ULTRA+ V5: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link ULTRA+ V6: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link WiFi V1: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link WiFi V2: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link-OB-K22-CortexA: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link-OB-RA4M2-Full: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link-OB-RA4M2-Renesas: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link-OB-S124: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Link-OB-XMC4200 / iMOTION-Link: Cortex-M: Added support for CoreSight SoC-600 debug setups.
- J-Trace PRO V3 Cortex: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
- J-Trace PRO V3: ARMv8-A/R: Firmware module version 11: JTAG: Debugging of core did not work properly if more than 1 device was in the JTAG chain. Fixed.
J-Flash SPI
- Added option for program and erase init commands, making it possible use factory mode programming for some Macronix SPI flashes.
Version V7.96b (2024-03-20)
Highlights:
Device Support
- ArteryTek AT32A40x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32A40x).
- ArteryTek AT32A41x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32A41x).
- ArteryTek AT32A42x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32AT42x).
- ArteryTek AT32F40x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32F40x).
- ArteryTek AT32WB41x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32WB41x).
- Infineon PSoC4000T: Added debug and flash programming support (https://wiki.segger.com/PSoC_4xxx_series).
- Nuvoton KM1M4: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M4).
- Nuvoton KM1M7: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M7).
- Renesas R9A02G021: Added debug and flash programming support (https://wiki.segger.com/Renesas_ASSP_EASY).
Other changes:
Commander
- Improved error output in case of connect failed.
Device Support
- ArteryTek AT32A40x: Add device specific connect and native unlock functionality.
- ArteryTek AT32A41x: Add device specific connect and native unlock functionality.
- ArteryTek AT32A42x: Add device specific connect and native unlock functionality.
- ArteryTek AT32F40x: Add device specific connect and native unlock functionality.
- ArteryTek AT32F43x: Flash bank 2 of the internal flash could not be erased. Fixed.
- ArteryTek AT32WB41x: Add device specific connect and native unlock functionality.
- Cmsemicon BAT32G1xx: Flash breakpoints did not work when using the DMA. Fixed.
- ST STM32H5: Added out of the box SWO support.
DLL
- Renesas RX72N, RX72T, RX66N and RX72M cores: DLL would not provide suggested target interfaces. Fixed.
- TI TMS570 series: Minimum flash programming size was incorrectly set to 16 bytes instead of 8 bytes. Fixed.
- Trace: Trace file has now shared read flag so it can be read while it is being filled.
Firmware
- Flasher ARM V5-1: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher ARM V5-1: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher ARM V5: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher ARM V5: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher ARM V6: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher ARM V6: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher Compact V5: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher Compact V5: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher Hub-12 V1: After disabling multiple Flashers, the list of disabled Flashers could be cut off after a reboot. Fixed.
- Flasher Hub-12 V1: FTP: Listing the contents of the 'All modules' directory (e.g. via MLSD command) failed with error "451 Requested action aborted. Local error in processing". Fixed.
- Flasher Hub-12 V1: FTP: Uploading into the 'All modules' directory could fail when module #12 was connected. Fixed.
- Flasher Hub-12 V1: When connecting an unsupported USB BULK device, the connector's green LED lit up and stayed on, even after disconnect. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher PRO V5: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher PRO V5: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher PRO V6: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher PRO V6: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
- Flasher PRO XL V6: Stand-alone mode: Batch jobs: Under special circumstances, if an individual batch job failed, no error was reported but OK instead. Fixed.
- Flasher PRO XL V6: Stand-alone mode: Cortex-M: Generic reset via AIRCR.SYSRESETREQ did not wait properly for core to halt after reset release but expected core to be halted immediately. Caused problems for example with SiLabs xxx. Fixed.
J-Flash
- Renesas RX72N, RX72T, RX66N and RX72M cores: When selecting devices with one of these cores, J-Flash would crash. Fixed.
J-Scope
- J-Scope crashed when the application was closed while sampling. Fixed.
Version V7.96a (2024-03-14)
Highlights:
Device Support
- Artery Tek AT32F402/AT32F405: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32F40x).
- Artery Tek AT32F423: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32F42x).
- Artery Tek AT32F43x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32F43x).
- NXP MCXA18: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXA18).
Other changes:
Device Provisioner
- Added log output for script file that has been actually opened, so user can see if fallback (looking under Script/) was performed.
- Passing only the script file name to open a script file from Script/ subdirectory under the DevPro executable did not work as expected. Fixed.
Device Support
- Artery Tek AT32F43x: Add device specific connect and native unlock functionality.
- Renesas RZ/V2H: Added warm reset strategy for both Cortex-R8 cores (https://wiki.segger.com/Renesas_RZ/V2H).
- ST STM32H5: Erasing more than 512 KB of internal flash did not work on devices with 1 MB flash size. Introduced in V7.94a. Fixed.
Firmware
- Flasher ARM V5-1: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher ARM V5: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher ARM V6: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher Compact V5: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher Portable PLUS V5: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher PRO V5-1: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher PRO V5: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher PRO V6: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher PRO XL V5-1: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher PRO XL V5: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- Flasher PRO XL V6: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link EDU Mini V1: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link EDU/BASE/PLUS V11: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link EDU/BASE/PLUS V11: Reset pin was not released on disconnect. Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link EDU/BASE/PLUS V12: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link EDU/BASE/PLUS V12: Reset pin was not released on disconnect. Fixed.
- J-Link OB RA4M2-Full: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link PRO PoE V6: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link PRO V5-1: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link PRO V5: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link PRO V6: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link ULTRA+ V5-1: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link ULTRA+ V5: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link ULTRA+ V6: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link WiFi V1: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link WiFi V2: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Link-OB-SAM3U128-V3: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Trace PRO V3 Cortex: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Trace PRO V3 CortexM: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Trace PRO V3 RISC-V: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
- J-Trace PRO V3: ARM7/9: EMU option EMU_OPTION_INVALIDATE_CPU_STATE (used as part of reset / toggle reset pin) could hang / crash FW. Fixed.
J-Flash
- Data window contents could be modified when opened in "Simplified" user interface mode. Fixed.
- Project information: Added element that shows "User interface mode" setting if it is not the default.
- Switching between "Simplified" and "Engineering" user interface modes in the project settings did not update the read-only state of open data windows. Fixed.
Version V7.96 (2024-03-07)
Highlights:
Device Provisioner
- Added script "PCode_DevPro_ST_STM32H5.pex".
J-Link Package
- Added "Device Provisioner" to software package. (See https://wiki.segger.com/Device_Provisioner)
Other changes:
Device Support
- ESWIN EMU32VL170: Added flash programming support for bootloader area.
DLL
- J-Link script files: Added JLINK_FILE_Read() API function call. (See https://wiki.segger.com/J-Link_script_files#JLINK_FILE_Read.28.29)
J-Flash
- Input paramaters for the delrange command were not checked properly, which could have caused a crash. Fixed.
Version V7.94m (2024-03-06)
Highlights:
Device Support
- AlifSemi E3/E5/E7 device series: Added OSPI programming support (https://wiki.segger.com/AlifSemi_CxEx).
- GigaDevice GD32E5xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32E5).
- GigaDevice GD32F1xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32F1).
- GigaDevice GD32F403: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32F4).
- GigaDevice GD32VF103: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32VF1).
- Hilscher NetX90: Added SQI(QSPI) flash programming support for APP Core (https://wiki.segger.com/Hilscher_netX90).
- NXP S32K358: Added debug and flash programming support for Cortex_M7_2 (https://wiki.segger.com/NXP_S32K3xx).
- NXP S32K388: Added debug and flash programming support for Cortex_M7_2 (https://wiki.segger.com/NXP_S32K3xx).
- NXP S32K388: Added debug and flash programming support for Cortex_M7_3 (https://wiki.segger.com/NXP_S32K3xx).
Other changes:
Device Support
- ESWIN EMU32VL170: Flash loader partially did not restore MCU state. Fixed.
- GigaDevice GD32F4xx: Added native unlock functionality.
- GigaDevice GD32H7xx: Added native unlock functionality.
- Nordic Semiconductor nRF9151: Added debug and flash programming support.
- Nuvoton M253, M254, M256 and M258 series: Flash programming did not work. Fixed.
- Nuvoton M254SD2AE: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_M25x).
- Nuvoton M256SD2AE: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_M25x).
- ST STM32U5G7xx/9xx: Added debug and flash programming support (https://wiki.segger.com/ST_STM32U5).
- ST STM32U5G7xx/9xx: Added SPI flash programming support for CLK@PI3_nCS@PH9_D0@PH10_D1@PH11_D2@PH12_D3@PH13_D4@NA_D5@NA_D6@NA_D7@NA pin configuration (Matching STM32U5G9J-DK2).
J-Scope
- When sorting the symbol table by changing values, rows could split. Fixed.
- When the SymbolTable is sorted, the wrong rows got updated. Fixed.
Version V7.94l (2024-02-29)
Highlights:
Device Support
- GigaDevice GD32C1xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32C1).
- GigaDevice GD32E1xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32E1).
- GigaDevice GD32E2xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32E2).
- GigaDevice GD32F2xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32F2).
- GigaDevice GD32F3xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32F3).
- GigaDevice GD32L23x: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32L23).
- Renesas RA0E1: Moved device support from hidden to public (https://wiki.segger.com/Renesas_RA0E1).
- Renesas RA2A2: Added debug & flash programming support (https://wiki.segger.com/Renesas_RA2A2).
- Renesas RZ/V2H: Added debug and flash programming support (https://wiki.segger.com/Renesas_RZ/V2H).
Other changes:
Device Support
- Geehy APM32F003: Programming of option byte memory did not work. Fixed.
- Geehy G32A1: Added a dialog to trigger a mass erase in case a flash sector is write protected.
- Geehy G32A1: Unsecuring a protected device did not work. Fixed.
- Renesas RA6M3/RA6T1/S5D3/S5D5/S5D9: Verification of option-setting memory could fail. Fixed.
- ST SR6xx: Connect to blank devices failed. Fixed.
- ST STM32L5xxx: Renamed QSPI "Default" loader to "CLK@PA3_nCS@PA2_D0@PB1_D1@PB0_D2@PA7_D3@PA6_D4@NA_D5@NA_D6@NA_D7@NA (Matching STM32L562E Discovery Kit).
Firmware
- Flasher ARM V5-1: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher ARM V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher ARM V6: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher Compact V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher PRO V5-1: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher PRO V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher PRO V6: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher PRO XL V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
- Flasher PRO XL V6: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
GUI Applications
- macOS: Sometimes, hovering over the entries of a combo box or context menu did not highlight them and clicking an entry did not select it. Fixed.
- macOS: The entries of a combo box or context menu were cut off in height. Fixed.
J-Link Package
- Windows: Removed obsolete Microsoft DLLs from shipment.
J-Scope
- J-Scope: Reduced the minimum size of J-Scopes main window.
Version V7.94k (2024-02-21)
Highlights:
Device Support
- Artery AT32A403A: Added flash programming support for SPIM (https://wiki.segger.com/Artery_AT32A40x).
- Artery AT32F402: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F40x).
- Artery AT32F403A: Added flash programming support for SPIM (https://wiki.segger.com/Artery_AT32F40x).
- Artery AT32F407: Added flash programming support for SPIM (https://wiki.segger.com/Artery_AT32F40x).
- Artery AT32F413: Added flash programming support for SPIM (https://wiki.segger.com/Artery_AT32F41x).
- GigaDevice GD32A50x: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32A5).
- Infineon CCG7D: Added debug and flash programming support(https://wiki.segger.com/Infineon_CCG7D).
- Infineon CCG7S: Added debug and flash programming support(https://wiki.segger.com/Infineon_CCG7S).
Other changes:
Configurator
- Systemwide option "Reset 'Don't show again'" did not reset registry key DontShowAgainUnlockSTM32. Fixed.
Device Support
- EFx32 Series 2 devices: Connect would fail when RAM was not readable, but device was in unlocked state. Fixed.
- GigaDevice GD32 Cortex-M devices: Description of MCU security added (https://wiki.segger.com/GigaDevice_GD32).
- Nuvoton M4xx: Added device specific connect with unlock (formaly only implemented for M45x devices).
- Renesas RZ/G3S: Added support for some new device names.
- TI CC2340: Improved the device specific handling to ensure that the target application boots without waiting for a specified debug timeout after closing the J-Link <--> target connection (https://wiki.segger.com/TI_CC2340#Device_Specific_Handling).
- TI MSPM0: Improved low power mode debugging capabilities.
DLL
- NXP LPC17xx: RTT: Some devices had dublicated search ranges. Fixed.
- Vorago VAxxx: Flash programming did not work due to overlapping flash banks. Fixed.
Firmware
- Flasher ARM V5-1: Added possibility to enable/disable FTP server of probe via config area.
- Flasher ARM V5-1: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher ARM V5-1: Added possibility to enable/disable web server of probe via config area.
- Flasher ARM V5-1: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher ARM V5: Added possibility to enable/disable FTP server of probe via config area.
- Flasher ARM V5: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher ARM V5: Added possibility to enable/disable web server of probe via config area.
- Flasher ARM V5: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher ARM V6: Added possibility to enable/disable FTP server of probe via config area.
- Flasher ARM V6: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher ARM V6: Added possibility to enable/disable web server of probe via config area.
- Flasher ARM V6: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher Compact V5: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher Hub-12 V1: Implemented module terminal server: https://wiki.segger.com/UM08043_Flasher_Hub-12#Module_terminal_server
- Flasher Hub-12 V1: WebIF: Added "Terminal" tab.
- Flasher Portable PLUS V5: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher PRO V5-1: Added possibility to enable/disable FTP server of probe via config area.
- Flasher PRO V5-1: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher PRO V5-1: Added possibility to enable/disable web server of probe via config area.
- Flasher PRO V5-1: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher PRO V5: Added possibility to enable/disable FTP server of probe via config area.
- Flasher PRO V5: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher PRO V5: Added possibility to enable/disable web server of probe via config area.
- Flasher PRO V5: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher PRO V6: Added possibility to enable/disable FTP server of probe via config area.
- Flasher PRO V6: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher PRO V6: Added possibility to enable/disable web server of probe via config area.
- Flasher PRO V6: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher PRO XL V5-1: Added possibility to enable/disable FTP server of probe via config area.
- Flasher PRO XL V5-1: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher PRO XL V5-1: Added possibility to enable/disable web server of probe via config area.
- Flasher PRO XL V5-1: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher PRO XL V5: Added possibility to enable/disable FTP server of probe via config area.
- Flasher PRO XL V5: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher PRO XL V5: Added possibility to enable/disable web server of probe via config area.
- Flasher PRO XL V5: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- Flasher PRO XL V6: Added possibility to enable/disable FTP server of probe via config area.
- Flasher PRO XL V6: Added possibility to enable/disable TELNET server of probe via config area.
- Flasher PRO XL V6: Added possibility to enable/disable web server of probe via config area.
- Flasher PRO XL V6: If Flasher.ini grew beyond 8 KB in size (e.g. many different configuration pairs placed in it),terminal command #SELECT failed. Fixed.
- J-Link PRO PoE V6: Added possibility to enable/disable TELNET server of probe via config area.
- J-Link PRO PoE V6: Added possibility to enable/disable web server of probe via config area.
- J-Link PRO V5-1: Added possibility to enable/disable TELNET server of probe via config area.
- J-Link PRO V5-1: Added possibility to enable/disable web server of probe via config area.
- J-Link PRO V5: Added possibility to enable/disable TELNET server of probe via config area.
- J-Link PRO V5: Added possibility to enable/disable web server of probe via config area.
- J-Link PRO V6: Added possibility to enable/disable TELNET server of probe via config area.
- J-Link PRO V6: Added possibility to enable/disable web server of probe via config area.
- J-Link WiFi V1: Added possibility to enable/disable TELNET server of probe via config area.
- J-Link WiFi V1: Added possibility to enable/disable web server of probe via config area.
- J-Link WiFi V2: Added possibility to enable/disable TELNET server of probe via config area.
- J-Link WiFi V2: Added possibility to enable/disable web server of probe via config area.
- J-Trace PRO V3 Cortex: Added possibility to enable/disable TELNET server of probe via config area.
- J-Trace PRO V3 Cortex: Added possibility to enable/disable web server of probe via config area.
- J-Trace PRO V3 CortexM: Added possibility to enable/disable TELNET server of probe via config area.
- J-Trace PRO V3 CortexM: Added possibility to enable/disable web server of probe via config area.
- J-Trace PRO V3: Added possibility to enable/disable TELNET server of probe via config area.
- J-Trace PRO V3: Added possibility to enable/disable web server of probe via config area.
J-Mem
- macOS: Moving the scroll bar of the memory view did not work correctly. Fixed.
J-Scope
- Anonymous structs or unions were given the wrong name. Fixed.
- In some cases, classes were falsely named "<inherited>". Fixed.
- When sampling with RTT, the wrong symbol could be updated when adjusting the Y-Offset. Fixed.
Version V7.94j (2024-02-14)
Highlights:
Device Support
- Artery AT32A403A: Added debug and flash programming (internal flash) support (https://wiki.segger.com/Artery_AT32A40x).
- Artery AT32F403A: Added debug and flash programming (internal flash) support (https://wiki.segger.com/Artery_AT32F40x).
- Artery AT32F407: Added debug and flash programming (internal flash) support (https://wiki.segger.com/Artery_AT32F40x).
- NXP MCXN11: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXN11).
DLL
- Trace: Added command string "TRACE_SetBackTraceMaxNumItems". (https://wiki.segger.com/J-Link_Command_Strings#TRACE_SetBackTraceMaxNumItems)
Other changes:
Commander
- Added command "FDiskInfo" for Flashers. Used to show disk/storage usage on Flashers.
Control Panel
- "General" tab: Added Disk info for Flashers (production programmers).
Firmware
- Flasher ARM V5-1: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher ARM V5-1: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher ARM V5: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher ARM V5: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher ARM V6: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher ARM V6: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher Compact V5: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher Portable PLUS V5: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher PRO V5-1: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher PRO V5-1: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher PRO V5: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher PRO V5: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher PRO V6: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher PRO V6: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher PRO XL V5-1: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher PRO XL V5-1: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher PRO XL V5: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher PRO XL V5: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
- Flasher PRO XL V6: Terminal via TELNET (IP): Establishing a new connection now replaces and closes any previously established and active TELNET terminal connection. (New connection was refused until now)
- Flasher PRO XL V6: Terminal: The #RESULT command used the wrong function for sending the response message, causing debug builds to get stuck at a debug assertion. Fixed.
Version V7.94i (2024-02-07)
Highlights:
Device Support
- Artery AT32F405: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F40x).
- Artery AT32F413: Added debug and flash programming (internal flash) support (https://wiki.segger.com/Artery_AT32F41x).
- Artery AT32F423: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F42x).
- Artery AT32WB415: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32WB41x).
- Geehy APM32F035: Added debug and flash programming support (https://wiki.segger.com/Geehy_APM32F0xx).
- Geehy APM32F411: Added debug and flash programming support (https://wiki.segger.com/Geehy_APM32F4xx).
- Geehy G32A1xx: Added debug and flash programming support (https://wiki.segger.com/Geehy_G32A1xx).
- HPMicro HPM68xx: Added debug and flash programming support (https://wiki.segger.com/HPMicro_HPM68).
- NXP S32K388: Added debug and flash programming support for the second Cortex-M7 core (https://wiki.segger.com/NXP_S32K3xx).
Trace
- Published out-of-the-box trace example for NXP iMXRT106x series: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Renesas RZ/A1L: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- Artery AT32F43x QSPI: PLL Clock initialization changed from 288 MHz to 216 MHz in order to match maximum clock speed on AT32F405.
- Geehy APM32F0xx, APM32F1xx: Option-byte programming did not work. Fixed.
- Geehy APM32F4xx: Option-byte programming did not work. Fixed.
- Renesas DA1470x: Not all registers got restored correctly. Fixed.
- Renesas RA6M1: Incorrect flash base address (0x28000000 instead of 0x60000000) used for the external QSPI flash bank. Fixed.
Firmware
- Flasher ARM V5-1: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher ARM V5: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher ARM V6: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher Compact V5: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher Portable PLUS V5: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher PRO V5-1: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher PRO V5: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher PRO V6: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher PRO XL V5-1: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher PRO XL V5: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- Flasher PRO XL V6: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link EDU Mini V1: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link EDU/BASE/PLUS V12: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link PRO PoE V6: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link PRO V5-1: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link PRO V5: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link PRO V6: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link ULTRA+ V5-1: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link ULTRA+ V5: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link ULTRA+ V6: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link WiFi V1: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Link WiFi V2: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Trace PRO V3 Cortex: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Trace PRO V3 CortexM: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
- J-Trace PRO V3: Introduced timeout for HW_Init() call in generic part of FW. If HW_Init() does not return within 5s, probe is reset and stays in BTL.
GDB Server
- When activating thread awareness the debug session could fail to start. Fixed.
J-Scope
- J-Scope now notifies the user if RTT is used without timestamps.
Trace
- Added command string "CORESIGHT_SetSTMBaseAddr" to allow manual override of STM base address. (https://wiki.segger.com/J-Link_Command_Strings#CORESIGHT_SetSTMBaseAddr)
- Added command string "CORESIGHT_SetSTMTraceID" to allow manual override of STM trace ID. (https://wiki.segger.com/J-Link_Command_Strings#CORESIGHT_SetSTMTraceID)
- Added command string "TRACE_SetSTMDataFile" to allow storing STM data into file. (https://wiki.segger.com/J-Link_Command_Strings#TRACE_SetSTMDataFile)
- Added command string "TRACE_SetSTMDataPort" to allow storing STM data to port. (https://wiki.segger.com/J-Link_Command_Strings#TRACE_SetSTMDataPort)
- Added support for script file entry points "StartSTM()" and "StopSTM()" to override default behavior on STM start/stop. (https://wiki.segger.com/J-Link_script_files#StartSTM.28.29)
Version V7.94h (2024-02-01)
Highlights:
Device Support
- Artery AT32F415: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F41x).
- Artery AT32F421: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F42x).
- Artery AT32F425: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F42x).
- ST SR6P3xx: Added debug and flash programming support (https://wiki.segger.com/ST_SR6P3).
- Toshiba TMPM3H Group(2): Added debug and flash programming support for some new part numbers.
Other changes:
Device Support
- Espressif ESP32: Added read support.
- Renesas RZ/G3S: Under certain circumstances erase did not work properly. Fixed.
- ST SR6P6xx/SR6P7xx: The watchdog was not handled properly which could result in expired flag was set. Fixed.
- ST SR6xxxx: The reset did not work properly resulting in an invalid PC after reset. Fixed.
Firmware
- Flasher ARM V5-1: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher ARM V5: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher ARM V6: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher Compact V5: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher Portable PLUS V5: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher PRO V5-1: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher PRO V5: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher PRO V6: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher PRO XL V5-1: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher PRO XL V5: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- Flasher PRO XL V6: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
- J-Link-OB-K22-CortexA: VCOM: Setting force-enable of hardware flow control (J-Link Commander "SetHWFC Force" command) did not work correctly (Enabling this option resulted in hardware flow control to be disabled). Fixed.
- J-Link-OB-K22-CortexM: VCOM: Setting force-enable of hardware flow control (J-Link Commander "SetHWFC Force" command) did not work correctly (Enabling this option resulted in hardware flow control to be disabled). Fixed.
- J-Link-OB-K22-RISCV: VCOM: Setting force-enable of hardware flow control (J-Link Commander "SetHWFC Force" command) did not work correctly (Enabling this option resulted in hardware flow control to be disabled). Fixed.
J-Scope
- Selecting FINE interface could lead to J-Scope trying to connect via BDM3 causing a connection fail. Fixed.
Version V7.94g (2024-01-24)
Highlights:
Device Support
- Artery AT32F43x: Added flash programming support for QSPI 1 flash bank (https://wiki.segger.com/Artery_AT32F43x).
Other changes:
Device Support
- Artery AT32F437VGT7, AT32F437RMT7, AT32F437RGT7, AT32F437RDT7: J-Link used incorrect flash size. Fixed.
- NXP iMXRT1180: XCACHE was not handled properly resulting in verification errors after a successful flash program operation. Fixed.
DLL
- Added support for Cortex-M52 (aka STAR-MC2).
- Added support for the EON SPI flash EN25QH128 to SPIFI-Lib.
- EON SPI flash EN25QH64: Block protection was not set correctly. Fixed.
- RTT: Specifying an RTT search range after/while RTT was running did not work as intended. Fixed.
Firmware
- Flasher ARM V5-1: Added support for Cortex-M52 core.
- Flasher ARM V5-1: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher ARM V5-1: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher ARM V5-1: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher ARM V5: Added support for Cortex-M52 core.
- Flasher ARM V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher ARM V5: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher ARM V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher ARM V6: Added support for Cortex-M52 core.
- Flasher ARM V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher ARM V6: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher ARM V6: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher Compact V5: Added support for Cortex-M52 core.
- Flasher Compact V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher Compact V5: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher Compact V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher Portable PLUS V5: Added support for Cortex-M52 core.
- Flasher Portable PLUS V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher Portable PLUS V5: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher Portable PLUS V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher PRO V5-1: Added support for Cortex-M52 core.
- Flasher PRO V5-1: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher PRO V5-1: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher PRO V5-1: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher PRO V5: Added support for Cortex-M52 core.
- Flasher PRO V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher PRO V5: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher PRO V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher PRO V6: Added support for Cortex-M52 core.
- Flasher PRO V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher PRO V6: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher PRO V6: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher PRO XL V5-1: Added support for Cortex-M52 core.
- Flasher PRO XL V5-1: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher PRO XL V5-1: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher PRO XL V5-1: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher PRO XL V5: Added support for Cortex-M52 core.
- Flasher PRO XL V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher PRO XL V5: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher PRO XL V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- Flasher PRO XL V6: Added support for Cortex-M52 core.
- Flasher PRO XL V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
- Flasher PRO XL V6: After executing a target operation (e.g. #AUTO) and formatting the file system (e.g. #FFORMAT), Flasher would use the deleted project for following operations (e.g. #AUTO). Fixed.
- Flasher PRO XL V6: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
- J-Link EDU Mini V1: Added support for Cortex-M52 core.
- J-Link EDU/BASE/PLUS V12: Added support for Cortex-M52 core.
- J-Link EDU/BASE/PLUS V12: Under very special circumstances, USB driver selection "SEGGER" in Configurator was reset to "WinUSB" after a power-cycle of J-Link. Fixed.
- J-Link PRO PoE V6: Added support for Cortex-M52 core.
- J-Link PRO V5-1: Added support for Cortex-M52 core.
- J-Link PRO V5: Added support for Cortex-M52 core.
- J-Link PRO V6: Added support for Cortex-M52 core.
- J-Link ULTRA+ V5-1: Added support for Cortex-M52 core.
- J-Link ULTRA+ V5: Added support for Cortex-M52 core.
- J-Link ULTRA+ V6: Added support for Cortex-M52 core.
- J-Link WiFi V1: Added support for Cortex-M52 core.
- J-Link WiFi V2: Added support for Cortex-M52 core.
- J-Trace PRO V3 Cortex: Added support for Cortex-M52 core.
- J-Trace PRO V3 CortexM: Added support for Cortex-M52 core.
- J-Trace PRO V3: Added support for Cortex-M52 core.
GDB Server
- Added support for Cortex-M52 (aka STAR-MC2).
J-Flash
- When a J-Flash log file was enabled in the global settings, temporary J-Flash log files passed via command line were overriden. Fixed.
J-Flash SPI
- When a J-Flash log file was enabled in the global settings, temporary J-Flash log files passed via command line were overriden. Fixed.
Version V7.94f (2024-01-17)
Highlights:
Device Support
- Renesas RZ/G3S: Added debug and flash programming support for the Cortex-M33_0 core (https://wiki.segger.com/Renesas_RZ/G3S).
- Renesas RZ/G3S: Added debug and flash programming support for the Cortex-M33_1 (with FPU) core (https://wiki.segger.com/Renesas_RZ/G3S).
Other changes:
Control Panel
- RTT Tab: Added event log.
- RTT Tab: Added search range information.
Device Support
- LPC553x/LPC55S3x: RTT: Added RAMX-RAM4 to auto search ranges.
- Renesas M16C/M62P, M16C/N6A: Added programming support for Renesas M30625FGPGP and M306NAFGGP.
DLL
- Linux: USB: Improved speed of GetList() function for J-Links connected via USB, so startup of debug session has been speed up as well.
Firmware
- Flasher ARM V5-1: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher ARM V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher ARM V5-1: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher ARM V5: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher ARM V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher ARM V5: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher ARM V6: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher ARM V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher ARM V6: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher Compact V5: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher Compact V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher Compact V5: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher Portable PLUS V5: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher Portable PLUS V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher PRO V5-1: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher PRO V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher PRO V5: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher PRO V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher PRO V5: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher PRO V6: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher PRO V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher PRO V6: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher PRO XL V5-1: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher PRO XL V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher PRO XL V5: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher PRO XL V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- Flasher PRO XL V6: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- Flasher PRO XL V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
- Flasher PRO XL V6: Stand-alone mode: Cortex-M: CPU module context was not freed after programming which could lead to "cannot connected to target" errors on following programming rounds. Fixed.
- J-Link EDU Mini V1: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link EDU/BASE/PLUS V12: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link PRO PoE V6: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link PRO V5-1: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link PRO V5: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link PRO V6: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link ULTRA+ V5-1: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link ULTRA+ V5: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link ULTRA+ V6: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link WiFi V1: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link WiFi V2: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link-OB-RA4M2-Full: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link-OB-RA4M2-Renesas: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Link-OB-RA4M2-RISCV: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Trace PRO V3 Cortex: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
- J-Trace PRO V3: RISC-V: Firmware module version 2: DAP-setups only: Debugging 2 or more cores in parallel behind the same DAP but different APs could lead to RISC-V not being accessible anymore via J-Link, after performing any operation on any other core. Fixed.
Version V7.94e (2024-01-15)
CCS Plugin
- Added Cortex-M33 support.
Device Support
- NXP iMXRT1180: Removed some unavailable part numbers.
- ST SR6P6xx: Programming the OTP area (e.g. UTEST) could cause a timeout. Fixed.
DLL
- Linux: DLL API calls would not work as intended. Introduced in V7.94d. Fixed.
Version V7.94d (2024-01-11)
Highlights:
Device Support
- NXP MCXA10: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXA10).
Other changes:
Commander
- Wrong libc version was used by accident. Introduced with V7.94c. Fixed.
Device Support
- Maxim MAX32690: Added flash programming support for internal program / data flash located at address 0x10300000 (256 KB).
- NXP iMXRT1170: Flash programming did not work. Introduced with V7.88l. Fixed.
- NXP iMXRT1180: Some device names used by the RT1180 CMSIS pack were not supported. Fixed.
- Renesas R7S721010 and R7S721010 were incorrectly listed as RZ/A1L. Corrected family to RZ/A1M.
- STM32U5Axxx: Added debug & flash programming support.
- Toshiba TMPM3HQF10BFG: Flash programming via CMSIS-DAP did not work. Fixed.
- Trace: TI Jacinto 7: Corrected ETB base addresses and set fixed ETB size as auto-detection is not working on that device.
DLL
- Added new exec command "CORESIGHT_SetETBBufSize" which can be used to override the ETB buffer size autodetection.
- In rare cases repeated JLINKARM_Open()/JLINKARM_Close() cycles could lead to a stalled DLL. Fixed.
- Wrong libc version was used by accident. Introduced with V7.94c. Fixed.
Firmware
- Flasher ARM V5-1: Renesas RX26T: Added stand-alone mode support.
- Flasher ARM V5: Renesas RX26T: Added stand-alone mode support.
- Flasher Compact V5: Renesas RX26T: Added stand-alone mode support.
- Flasher Portable PLUS V5: Renesas RX26T: Added stand-alone mode support.
- Flasher PRO V5-1: Renesas RX26T: Added stand-alone mode support.
- Flasher PRO V5: Renesas RX26T: Added stand-alone mode support.
- Flasher PRO XL V5-1: Renesas RX26T: Added stand-alone mode support.
- Flasher PRO XL V5: Renesas RX26T: Added stand-alone mode support.
Version V7.94c (2024-01-03)
Device Support
- EFR32xF22xxx, EFR32xF27xxx: Flash programming for UDP region did not work. Introduced in V7.94. Fixed.
- Infineon S25Hxxxx: Under certain circumstances read did not work correctly. Fixed.
- NXP iMXRT1180 (Cortex-M7): "FlexSPI 1 (NS)" flash bank: Flash programming did not work. Fixed.
- NXP iMXRT1180 (Cortex-M7): "FlexSPI 1 (S)" flash bank: Flash programming did not work. Fixed.
- NXP MCXN10: Boot ROM was not executed after reset resulting in unexpected issues after reset. Fixed.
- NXP MCXN10: Reset could fail when using JTAG as target interface. Fixed.
- Renesas RX26T: The J-Link SW did not allow to select JTAG as target interface for RX26T based devices. Fixed.
- Silicon Labs EFR32xG21, EFR32xG22, EFR32xG23, EFR32xG24, EFR32xG25, EFR32xG27, EFR32xG28: Under certain circumstances flash breakpoints did not work. Fixed.
DLL
- Added J-Link script file API function JLINK_RISCV_ReadCSR(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Added J-Link script file API function JLINK_RISCV_WriteCSR(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Trace: Added trace pin support for TI Jacinto 7 series.
- Under certain circumstances SWO init would not be executed. Introduced with V7.88f. Fixed.
J-Flash
- EFM32GG11: Production Programming could lead to all flash banks erased but the BTL flash bank. Fixed.
- Project Settings: Flash: For external flash devices selected manually, the displayed size, number of sectors, sectorization information and sector selection were incorrect. Fixed.
J-Scope
- J-Scope: Added support to scope symbols of base classes.
RTT Logger
- Added J-Link Script file support via command line.
Version V7.94b (2023-12-13)
Device Support
- MindMotion MM32xx: Flash programming did not work with Flasher standalone mode. Fixed.
- NXP iMXRT102x: FlexSPI port B pins were initialized for QSPI flash download, even though they were not being used. Fixed.
- NXP iMXRT1180: Updated device names to match the official device name scheme.
DLL
- Cadence Xtensa: Added command string "XTENSA_SetDEVTYPE" to support systems with modified value of DEVTYPE register. More info: https://wiki.segger.com/J-Link_Xtensa_specifics#Optional_debug_settings
- Cadence Xtensa: For "Xtensa behind CoreSight DAP" setups, an APB-AP was not accepted as a valid debug AP and threw an error. Fixed.
- Under certain circumstances (JLINKARM_Open() call with immediate JLINKARM_Close() call afterwards), J-Link DLL could crash. Fixed.
Firmware
- Flasher ARM V5-1: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- Flasher ARM V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
- Flasher ARM V5: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- Flasher ARM V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
- Flasher Compact V5: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- Flasher Compact V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
- Flasher Portable PLUS V5: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- Flasher Portable PLUS V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
- Flasher PRO V5-1: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- Flasher PRO V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
- Flasher PRO V5: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- Flasher PRO V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
- Flasher PRO XL V5-1: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- Flasher PRO XL V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
- Flasher PRO XL V5: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- Flasher PRO XL V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
- J-Link EDU Mini V1: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link EDU/BASE/PLUS V12: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link PRO PoE V6: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link PRO V5-1: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link PRO V5: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link PRO V6: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link ULTRA+ V5-1: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link ULTRA+ V5: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link ULTRA+ V6: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link WiFi V1: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link WiFi V2: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link-OB-RA4M2-Full: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link-OB-RA4M2-Renesas: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Link-OB-S124: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Trace PRO V3 Cortex: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
- J-Trace PRO V3: ARMv8-A/R: Firmware module version 10: CTIGATE and GTIOUTEN1 of "local" CTI (the one connected to the core that is debugged) was not preserved on Halt/Go. Fixed.
J-Flash SPI
- J-Flash SPI projects would always erase on Flasher even if erase was unchecked in project settings. Fixed.
J-Run
- Some commands of JRun started with "-" instead of "--". fixed.
J-Scope
- J-Scope: Added support for Bitfields.
- J-Scope: Added support for Bitfields.
- J-Scope: The context menu in the symbol table could not be opened. Fixed.
Version V7.94a (2023-12-06)
Highlights:
Device Support
- Macronix MX25UW25345G: Added flash programming support.
- Microchip PIC32CZxxxxCA80, PIC32CZxxxxCA90: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32CZ_CA).
- Renesas RA8D1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8D1).
- Renesas RA8T1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8T1).
J-Flash SPI
- Macronix MX25UW25345G: Added flash programming support.
Other changes:
Commander
- Command "ShowEmus": Extended command so it now also prints the VCOM ports that belong to a specific J-Link.
Device Support
- Infineon Traveo: Erase of the workflash could fail. Fixed.
- LPC11E35/501: Added debug & flash programming support.
- NXP iMXRT1180: The QSPI flash loader skipped the restoration of the original CPU state after programming the flash. Introduced in V7.92m. As this behavior causes problems under certain circumstances, we decided to revert this change. From now, the original state is restored after flash download.
- ST STM32H5: Erasing more than 512 KB of internal flash did not work on devices with 1 MB flash size. Fixed.
DLL
- Connecting via IP: Increased connection timeout from 1.5s to 3s for a better and more reliable connection experience in case of bad WiFi signal strength.
Firmware
- Flasher ARM V5-1: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- Flasher ARM V5: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- Flasher Compact V5: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- Flasher Portable PLUS V1: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- Flasher Portable PLUS V5: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- Flasher PRO V5-1: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- Flasher PRO V5: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- Flasher PRO XL V5-1: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- Flasher PRO XL V5: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link EDU Mini V1: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link EDU/BASE/PLUS V11: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link EDU/BASE/PLUS V12: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link PRO PoE V6: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link PRO V5-1: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link PRO V5: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link PRO V6: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link ULTRA+ V5-1: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link ULTRA+ V5: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link ULTRA+ V6: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link WiFi V1: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link WiFi V2: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link-OB-K22-CortexA: Added support for ARMv8-A/R based cores (e.g. Cortex-R52).
- J-Link-OB-K22-CortexM: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link-OB-RA4M2-CortexM: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link-OB-RA4M2-Full: Added support for ARMv8-A/R based cores (e.g. Cortex-R52).
- J-Link-OB-RA4M2-Full: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link-OB-RA4M2-Renesas: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Link-OB-S124: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Trace PRO V2 Cortex: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Trace PRO V2 CortexM: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Trace PRO V3 Cortex: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- J-Trace PRO V3 CortexM: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- MCU-Link-OB: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
- MCU-Link: Cortex-M7 via SWD and ARMv8-M (e.g. Cortex-M33) via SWD (JTAG was working fine): Firmware module V2: I-cache and D-cache were not handled properly on go / step (could lead to flash programming failures, phatom breakpoints that were already removed, ...). Introduced in V7.86a. Fixed.
GDB Server
- Setting multiple breakpoints on the same address does not produce a message box anymore, but a log entry only.
J-Flash
- New Project Dialog: While the list of devices was loaded, the button for showing the device list dialog could still be clicked, which would cause multiple device selection dialogs to open. Fixed.
- New Project Dialog: While the list of devices was loaded, the New Project dialog could be closed, causing J-Flash to crash. Fixed.
- New Project Dialog: While the list of devices was loaded, the user was given no indication that J-Flash was busy loading the device list. Fixed.
- Project Settings: Init/ Exit steps: The table did not expand in height. Fixed.
- Project Settings: MCU: While the list of devices was loaded, the project settings dialog could be closed, causing J-Flash to crash. Fixed.
J-Scope
- J-Scope crashed in some cases when a symbol was filtered. Fixed.
- J-Scope crashed when the symbol table was sorted and a symbol was removed. Fixed.
Version V7.94 (2023-11-29)
Highlights:
Device Support
- NXP S32M24x: Added debug and flash programming support (https://wiki.segger.com/NXP_S32M24x).
- NXP S32M276: Added debug and flash programming support (https://wiki.segger.com/NXP_S32M27x).
- Texas Instruments MSPM0C: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0C).
J-Link Package
- Windows: Installer: Changed default so "Install a new instance" is checked by default, instead of "Update existing installation".
Other changes:
Device Support
- Silicon Labs EFR32xG24: Under certain circumstances flash breakpoints did not work. Fixed.
- ST STM32G4: Program/Erase did not work for specific device configurations. Fixed.
- ST STM32H7: Device unlock on connect did not work properly. Fixed.
Version V7.92q (2023-11-23)
DLL
- Closing a J-Link connection after a GUI dialog could not be shown (e.g. due to running on a headless system) could lead to unintended behavior (e.g. <stdin> stream being closed). Fixed.
J-Flash
- "Bus error" fix from V7.92p caused a buffer overflow. Fixed.
- J-Flash now attempts to detect file when opening files without extensions.
J-Run
- Reworked J-Runs ELF file parsing.
J-Scope
- "Bus error" fix from V7.92p caused a buffer overflow. Fixed.
Version V7.92p (2023-11-22)
Device Support
- AlifSemi Ensemble E1: Debugging via SWD did not work because of missing dormant mode support. Fixed.
- AlifSemi Ensemble E3: Debugging via SWD did not work because of missing dormant mode support. Fixed.
- AlifSemi Ensemble E5: Debugging via SWD did not work because of missing dormant mode support. Fixed.
- AlifSemi Ensemble E7: Debugging via SWD did not work because of missing dormant mode support. Fixed.
- Renesas RA2L1/RA2E1/RA2E2: Verification of option-setting memory could fail. Fixed.
- Renesas RZ/T2M: Core ID mismatch was reported (warning). Fixed.
- Renesas S1JA/RA2A1: Verification of option-setting memory could fail. Fixed.
- ST STM32L4R9xx: Added QSPI flash programming support for pin configuration CLK@PA3_nCS@PA2_D0@PB1_D1@PB0_D2@PA7_D3@PA6_D4@NA_D5@NA_D6@NA_D7@NA (Matching STM32L4R9I-EVAL).
- ST STM32L4R9xx: Increased max. QSPI flash size to 256MB.
- ST STM32L4R9xx: Renamed QSPI "Default" loader to "CLK@PI6_nCS@PG12_D0@PI11_D1@PI10_D2@PI9_D3@PH8_D4@NA_D5@NA_D6@NA_D7@NA (Matching STM32L4R9 Discovery Kit).
- ST STM32WB55: Improved programming speed for internal flash.
- TDK Micronas HVC5xxx: Under certain circumstances, reset did not work with Flasher standalone mode. Fixed.
DLL
- ARM dormant mode support: JTAG: Added support for connecting via JTAG if device was in SWD or Dormant State (Switching Dormant -> JTAG or SWD -> Dormant -> JTAG).
- ARM dormant mode support: SWD: Added support for connecting via SWD if device was in JTAG State (JTAG -> Dormant -> SWD).
- Flash programming: If garbage CPU speed was measured (!= 0 but < 1 kHz), it was shown as "0 kHz", instead of the "measured" value. Fixed.
- ST STM32H7B0xx: Added QSPI flash programming support.
- Windows: The DLL would not show GUI dialogs (e.g. Flash programming dialog) when the software package was installed by a user "for all users" and second user started an application outside of the software package (e.g. Ozone, Embedded Studio, 3rd party utilities, ...). Fixed.
Firmware
- Flasher ARM V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- Flasher ARM V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- Flasher Compact V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- Flasher Portable PLUS V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- Flasher Portable PLUS V5: Reload FLASHER.INI, if configuration had been invalidated (e.g. on file system change).
- Flasher PRO V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- Flasher PRO V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- Flasher PRO XL V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- Flasher PRO XL V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link EDU Mini V1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link EDU/BASE/PLUS V11: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link EDU/BASE/PLUS V12: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link PRO PoE V6: 5V output on pin 19 was not fed from PoE, if J-Link was powered by power-over-Ethernet instead of USB, which reduced in reduced max. current that could be drawn on pin 19. Fixed.
- J-Link PRO PoE V6: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link PRO V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link PRO V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link PRO V6: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link ULTRA+ V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link ULTRA+ V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link ULTRA+ V6: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Link WiFi V1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Trace PRO V2 Cortex: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Trace PRO V2 CortexM: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Trace PRO V3 Cortex: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Trace PRO V3 CortexM: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
- J-Trace PRO V3 RISC-V: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
J-Flash
- Flash programming: If garbage CPU speed was measured (!= 0 but < 1 kHz), it was shown as "0 kHz", instead of the "measured" value. Fixed.
- Linux arm: J-Flash could crash immediately after launching due to a "Bus error". Fixed.
Version V7.92o (2023-11-08)
Highlights:
Device Support
- AICH 306xH: Added debug and flash programming support (https://wiki.segger.com/AICH_306xH).
- NXP KE1xZ512xxx9: Added debug and flash programming support.
Other changes:
Device Support
- GigaDevice GD32VW553 : Device part numbers completed.
- Infineon S25HS256T, S25HS512T, S25HS01GT, S25HL256T, S25HL512T, S25HL01GT: Sector size was set to 64 KB instead of correct value of 256 KB. Fixed.
Firmware
- Flasher ARM V5-1: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
- Flasher ARM V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
- Flasher Compact V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
- Flasher Hub-12 V1: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
- Flasher Portable PLUS V5: Log output from universal flash loaders (U-Flash) was not forwarded to terminal (VCOM) correctly. Fixed.
- Flasher Portable PLUS V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
- Flasher PRO V5-1: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
- Flasher PRO V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
- Flasher PRO XL V5-1: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
- Flasher PRO XL V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
J-Scope
- Reworked J-Scopes ELF file parsing.
RTT Viewer
- "Clear all terminals" menu action could crash the application fixed.
Version V7.92n (2023-10-31)
Highlights:
Trace
- Added native trace buffer support for Xilinx Zynq device series.
- Published out-of-the-box trace examples for Renesas EK-RA8M1 board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- ST SR6Pxxx: Programming the OTP area (e.g. UTEST) could cause a timeout. Fixed.
DLL
- After the connection to a probe or programmer was closed and re-opened without the J-Link library unloading in between, no GUI dialogs were visible anymore. Introduced in V7.92l. Fixed.
- Linux: Attempting to update the firmware of a probe or programmer via IP could cause the application to crash. Fixed.
- macOS: Attempting to update the firmware of a probe or programmer via IP could cause the application to crash. Fixed.
- Windows: Updating the firmware of a probe or programmer via IP did not work. Introduced in V7.92l. Fixed.
Firmware
- Flasher Hub-12 V1: The #SELMODULE command did not select all of the given modules if there was a gap in the specified list of modules. Fixed.
- J-Link EDU Mini V1: Added support for ARMv8-A/R based cores (e.g. Cortex-A53).
GDB Server
- Monitor command SWO GetMaxSpeed: In some cases, command would return false values. Fixed.
RTT Viewer
- Added "Clear all terminals" menu action.
Version V7.92m (2023-10-26)
Highlights:
Device Support
- Nordic Semiconductor nRF9131: Added debug and flash programming support (https://wiki.segger.com/Nordic_Semiconductor_nRF91xx).
- Nordic Semiconductor nRF9161: Added debug and flash programming support (https://wiki.segger.com/Nordic_Semiconductor_nRF91xx).
- Renesas RA2E3: Added hidden debug and flash programming support.
Other changes:
Device Support
- NXP iMXRT1180: Added debug and QSPI flash programming support for the non-secure flash region @ 0x28000000 (https://wiki.segger.com/NXP_iMXRT1180).
- NXP iMXRT1180: Updated QSPI flash loader to leave the QSPI flash initialized after flash download to ensure that the flash remains memory mapped readable (https://wiki.segger.com/NXP_iMXRT1180).
Firmware
- Flasher Hub-12 V1: Module operations failed for modules running firmware compiled 27th Sep 2023 or later. Fixed.
- Flasher Hub-12 V1: Response strings were sometimes incomplete. Fixed.
- Flasher Hub-12 V1: Under certain circumstances (especially for U-Flash projects with verbose output), the result strings for #AUTO, #ERASE, #PROGRAM and #VERIFY could be incorrect (e.g. "OK:READY:100%" instead of "OK (Total [...]"). Fixed.
- Flasher Hub-12 V1: When transfering multiple files from or to a module via FTP, some files could not be transfered correctly without the client knowing. Fixed.
- Flasher Hub-12 V1: When uploading multiple files to a module via FTP, the module could get stuck with activity "Writing to files". Fixed.
J-Flash
- Downloading files to Flasher Hub-12 modules did not work and J-Flash showed an error stating that 'the connected probe/ programmer is not a gang programmer [...]'. Fixed.
J-Flash SPI
- Downloading files to Flasher Hub-12 modules did not work and J-Flash SPI showed an error stating that 'the connected probe/ programmer [...] does not support the SPI interface'. Fixed.
Version V7.92l (2023-10-25)
Highlights:
Device Support
- GigaDevice GD32H7: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32H7).
- GigaDevice GD32VW553 : Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32VW5).
- Renesas RA8M1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8M1).
Other changes:
Device Support
- CVA BlueWhale CVM014x: After reset, the core did not halt on the first instruction of the target application, but on the second instead. Fixed.
- NXP iMXRT1180: Under certain circumstances, debugging could behave unexpected due to some pending interrupts after boot ROM execution. Fixed.
- NXP K32W14: Programming secure flash bank did not work. Fixed.
- NXP RW61x: Added flash programming support for QSPI secure address.
- NXP RW61x: Connect with JTAG was not working. Fixed.
- Programming errors were not detected correctly on STM32WB55xx-series devices. Fixed.
- ST STM32H7xxxx: Added SPI flash programming support for CLK@PF10_nCS@PG6_D0A@PD11_D1A@PF9_D2A@PF7_D3A@PF6_D0B@PH2_D1B@PH3_D2B@PG9_D3B@PG14 pin configuration (Matching STM32H750B-DK).
- ST STM32H7xxxx: Renamed QSPI loader "CLK@PB2_nCS@PG6_D0A@PH2_D1A@PH3_D2A@PG9_D3A@PG14_D0B@PH2_D1B@PH3_D2B@PG9_D3B@PG14" to "CLK@PB2_nCS@PG6_D0A@PD11_D1A@PF9_D2A@PF7_D3A@PF6_D0B@PH2_D1B@PH3_D2B@PG9_D3B@PG14". Loader name did not describe the correct pin configuration. Fixed.
DLL
- Cortex A/R V8: Under certain circumstances manually defined AP map was not evaluated correctly. Fixed.
- Improved information output if core base address and/or CTI core base address is set e.g. through J-Link Script file.
- JLinkDevices XML device entries with core "JLINK_CORE_RISC_V" were not correctly parsed. Fixed.
- TI CC1314R10: Incorrect core was displayed in the device selection dialog. Fixed.
- TI CC1354P10: Incorrect core was displayed in the device selection dialog. Fixed.
- While the update notification pop-up was visible, other dialogs (e.g. flash programming dialog) would not be shown until the pop-up was closed. Fixed.
Firmware
- Flasher ARM V5-1: Terminal could get unresponsive if sending commands while a background operation was in progress (e.g. host sent #STATUS commands while the background action triggered by a previous #AUTO command was still in progress). Fixed.
- Flasher ARM V5-1: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
- Flasher ARM V5: Terminal could get unresponsive if sending commands while a background operation was in progress (e.g. host sent #STATUS commands while the background action triggered by a previous #AUTO command was still in progress). Fixed.
- Flasher ARM V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
- Flasher Compact V5: Terminal could get unresponsive if sending commands while a background operation was in progress (e.g. host sent #STATUS commands while the background action triggered by a previous #AUTO command was still in progress). Fixed.
- Flasher Compact V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
- Flasher Portable PLUS V1: Undefined behavior of Flasher after programming of certain project files. Fixed.
- Flasher Portable PLUS V5: Terminal could get unresponsive if sending commands while a background operation was in progress (e.g. host sent #STATUS commands while the background action triggered by a previous #AUTO command was still in progress). Fixed.
- Flasher Portable PLUS V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
- Flasher PRO V5-1: Terminal could get unresponsive if sending commands while a background operation was in progress (e.g. host sent #STATUS commands while the background action triggered by a previous #AUTO command was still in progress). Fixed.
- Flasher PRO V5-1: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
- Flasher PRO V5: Terminal could get unresponsive if sending commands while a background operation was in progress (e.g. host sent #STATUS commands while the background action triggered by a previous #AUTO command was still in progress). Fixed.
- Flasher PRO V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
- Flasher PRO XL V5-1: Terminal could get unresponsive if sending commands while a background operation was in progress (e.g. host sent #STATUS commands while the background action triggered by a previous #AUTO command was still in progress). Fixed.
- Flasher PRO XL V5-1: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
- Flasher PRO XL V5: Terminal could get unresponsive if sending commands while a background operation was in progress (e.g. host sent #STATUS commands while the background action triggered by a previous #AUTO command was still in progress). Fixed.
- Flasher PRO XL V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
GDB Server
- Hitting breakpoints compiled into application or set via monitor commands could mess up GDB communication and cause GDB to become unresponsive to user commands, making the debug hang. Fixed.
- Semihosting commands SYS_OPEN and SYS_CLOSE were not working correctly in semihosting IOclient mode == 2 and 3 (when semihosting operation was forwarded to GDB client). Fixed.
J-Flash
- If retrieving information about the default loader of a device failed (because of an internal error), J-Flash worked with invalid settings. Fixed.
J-Flash SPI
- Added support for M95M01 SPI EEPROM.
Manual
- UM08039 Flasher Hub: Moved to SEGGER wiki: https://wiki.segger.com/UM08039_Flasher_Hub
- UM08043 Flasher Hub-12: Created new Flasher Hub-12 manual in the SEGGER wiki: https://wiki.segger.com/UM08043_Flasher_Hub-12
Version V7.92k (2023-10-18)
Device Support
- NXP S32 series: Write protected devices were not properly detected under special circumstances. Fixed.
- Renesas M16C/64A: Added flash programming support for R5F364AKxxx.
DLL
- Added new command string "InhibitConnectRetries" (https://wiki.segger.com/J-Link_Command_Strings#InhibitConnectRetries).
- JLinkScript Files: Added CORTEX_R52 to known predefined __constants.
- Probe selection dialog did not show the correct image for J-Link PRO PoE. Fixed.
- Renesas RZ/N2L: Added background access support (used by e.g. RTT).
- Selecting a J-Link via nickname when a connected J-Link does not have a nickname specified could cause crash. Fixed.
Firmware
- Flasher ARM V5-1: Reading the terminal via USB BULK (e.g. FlasherControl utility) did not work correctly when lots of terminal messages were created (e.g. by a U-Flash project ran with high verbosity). Fixed.
- Flasher ARM V5: Reading the terminal via USB BULK (e.g. FlasherControl utility) did not work correctly when lots of terminal messages were created (e.g. by a U-Flash project ran with high verbosity). Fixed.
- Flasher Compact V5: Reading the terminal via USB BULK (e.g. FlasherControl utility) did not work correctly when lots of terminal messages were created (e.g. by a U-Flash project ran with high verbosity). Fixed.
- Flasher Portable PLUS V5: Reading the terminal via USB BULK (e.g. FlasherControl utility) did not work correctly when lots of terminal messages were created (e.g. by a U-Flash project ran with high verbosity). Fixed.
- Flasher PRO V5-1: Reading the terminal via USB BULK (e.g. FlasherControl utility) did not work correctly when lots of terminal messages were created (e.g. by a U-Flash project ran with high verbosity). Fixed.
- Flasher PRO V5: Reading the terminal via USB BULK (e.g. FlasherControl utility) did not work correctly when lots of terminal messages were created (e.g. by a U-Flash project ran with high verbosity). Fixed.
- Flasher PRO XL V5-1: Reading the terminal via USB BULK (e.g. FlasherControl utility) did not work correctly when lots of terminal messages were created (e.g. by a U-Flash project ran with high verbosity). Fixed.
- Flasher PRO XL V5: Reading the terminal via USB BULK (e.g. FlasherControl utility) did not work correctly when lots of terminal messages were created (e.g. by a U-Flash project ran with high verbosity). Fixed.
- J-Link-OB-nRF5340-NordicSemi: Under special circumstances, VCOM could hang on COM port open. Fixed.
Version V7.92j (2023-10-12)
Highlights:
Device Support
- Silicon Labs EFR32xG27: Added debug and flash programming support (https://wiki.segger.com/Silicon_Labs_EFR32xG27).
Other changes:
Device Support
- AlifSemi Ensemble E1 / E3 / E5 E7 series: Connecting to M55-HE core did not work. Fixed.
- AlifSemi Ensemble E1: Added support for new derivatives: AE101F4071542
- AlifSemi Ensemble E3: Added support for new derivatives: AE302F40C1537, AE302F40C1557, AE302F80F5582, AE302F80F55D5
- AlifSemi Ensemble E5: Added support for new derivatives: AE512F80F5582, AE512F80F55D5
- HPMicro HPM62x4: Programming of SiP flash failed. Fixed.
- Renesas RA4E1, RA4M2, RA4M3, RA6E1, RA6M5, RA6T2: Programming of option-setting memory could fail. Fixed.
Version V7.92i (2023-10-11)
Highlights:
Trace
- Published out-of-the-box trace examples for Renesas EK-RA6M4 and EK-RA6M5 boards: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- EON SPI Flash EN25QH16B and EN25QH32B: Added flash programming support.
- HPMicro HPM62xx: Flash programming could fail if flash size exceeds 16MB. Fixed.
- Infineon S28HL256T, S28HS256T, S28HL512T, S28HS512T, S28HL01GT, S28HS01GT: Added indirect flash programming support.
- MindMotion MM32F5 / MM32G5: Added flash unlock functionality in case active read protection is detected.
- MindMotion MM32F5 / MM32G5: Verification of option bytes could fail after programming. Fixed.
- Renesas RA4E1, RA4M2, RA4M3, RA6E1, RA6M4, RA6M5, RA6T2: Verification of option-setting memory could fail. Fixed.
- SiliconLabs EFx32 Series 2: Added secure boot debug & flash programming support.
- SiliconLabs EFx32 Series 2: Connect would always trigger a reset. Fixed.
- TI DRA821: Added debug support for all Cortex-R5 cores (https://wiki.segger.com/TI_Jacinto_7).
- TI DRA829: Added debug support for all Cortex-R5 cores (https://wiki.segger.com/TI_Jacinto_7).
- TI TDA4VM: Added debug support for all Cortex-R5 cores (https://wiki.segger.com/TI_Jacinto_7).
DLL
- Added several Infineon CYT4BF series secondary JTAG TAP Ids to list of known TAPs.
- Native trace support for Renesas RZ/A1L and RZ/A1LU was not working correctly. Fixed.
Firmware
- Flasher Portable PLUS V5: Terminal could hang if #AUTO command was followed by another command that produced lots of output (e.g. #FLIST). Fixed.
- J-Link-OB-K22-CortexA: Added support for CMSIS-DAP V1 (HID) mode.
- J-Link-OB-K22-CortexM: Added support for CMSIS-DAP V1 (HID) mode.
- J-Link-OB-K22-RISCV: Added support for CMSIS-DAP V1 (HID) mode.
J-Flash
- The stand-alone-mode configuration file was not correct for SEGGER flashloader memory banks. Fixed.
J-Flash SPI
- Infineon S28HL256T, S28HS256T, S28HL512T, S28HS512T, S28HL01GT, S28HS01GT: Added direct flash programming support.
RTT
- SEGGER_RTT_vprintf(): %s handling: In case string is NULL-pointer, function will now write "(NULL)" instead of doing a NULL-pointer access.
Version V7.92h (2023-10-04)
Highlights:
Device Support
- ESWIN EMU32VL170: Added debug and flash programming support(https://wiki.segger.com/ESWIN_EMU32VL170).
Other changes:
Device Support
- CVA BlueWhale CVM014x: Program flash size was reported incorrect. Fixed.
- SiliconLabs EFR32xG22: Under special circumstances, connect could fail with higher interface speeds (e.g. 4 MHz). Fixed.
- ST STM32F303x6/x8: It could happen that the J-Link SW used too much RAM during flash programming (16 KB instead of 12 KB). Fixed.
Firmware
- J-Trace PRO V3 Cortex: Under certain circumstances the first TPIU frame sync packet would not be sampled correctly. Fixed.
- J-Trace PRO V3 CortexM: Under certain circumstances the first TPIU frame sync packet would not be sampled correctly. Fixed.
- J-Trace PRO V3 RISC-V: Under certain circumstances the first TPIU frame sync packet would not be sampled correctly. Fixed.
J-Flash SPI
- J-Flash SPI did not open most recent project or create a new project on startup. Introduced with V7.92a. Fixed.
RTT
- GCC compiler: SEGGER_RTT.c and SEGGER_RTT.h did throw warnings if "-Wcast-align" warning was enabled. Fixed.
Version V7.92g (2023-09-27)
Highlights:
Device Support
- CVA BlueWhale CVM014x: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM014x).
- NXP CTN73x: Added debug and flash programming support (https://wiki.segger.com/NXP_CTN73x).
- NXP iMXRT1180: Added debug and QSPI flash programming support (https://wiki.segger.com/NXP_iMXRT1180).
- PUYA P25Q32SL: Added flash programming support.
- Renesas RA6M5: Added missing device support for R7FA6M5BG (1.5 MB flash).
J-Flash SPI
- PUYA P25Q32SL: Added flash programming support.
Other changes:
Device Support
- MindMotion MM32F5 / MM32G5: Chip erase did not work on option byte. Fixed.
- NXP PN7xxx: EEPROM moved to separate flashbank.
- NXP PN7xxx: Reset could disconnect debug connection. Fixed.
- Renesas DA1470x: Flash programming could fail if target firmware changed clock settings. Fixed.
- Renesas RA4T1 / RA6E2: Verification of option-setting bytes could fail. Fixed.
- Renesas RX26T: The BANKSEL and FAW register (option-setting memory) could not be programmed. Fixed.
- ST STM32G4: Chip erase did not work. Fixed.
Version V7.92f (2023-09-20)
Highlights:
Device Support
- Microchip PIC32CM JH: Added debug and flash programming support(https://wiki.segger.com/Microchip_PIC32CM_JH).
- NXP LPC86x: Added debug and flash programming support (https://wiki.segger.com/NXP_LPC86x).
- NXP S32K388: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
Other changes:
Commander
- Command files could not be executed correctly if they have carriage returns ('\r') as line breaks. Fixed.
Device Support
- Hilscher netX90_COM: Normal reset did not work properly. Fixed.
- HPMicro HPM53xx / HPM63xx / HPM67xx: Verification of flash programming could fail. Fixed.
- HPMicro: Changed naming from HPM53xx to HPM5361xCBx, HPM5361xEGx, HPM5361xCFx, HPM5331xCBx, HPM5331xEGx, HPM5331xCFx, HPM5321xCBx, HPM5321xEGx, HPM5321xCFx, HPM5301xEGx.
- NXP iMX7D device series: QSPI flash bank size was set to 32 MB instead of 256 MB. Fixed.
- NXP LPC55S36: Flash programming for secure bank did not work. Fixed.
DLL
- Toggling the reset pin if no target connection has been established yet could cause the J-Link firmware to hang. Introduced in V7.92d. Fixed.
Firmware
- Flasher Portable PLUS V5: Changed behavior and timing of project selection. Long press of SEL will fast forward after 3s.
Version V7.92e (2023-09-13)
Highlights:
Device Support
- HPMicro HPM53xx: Added debug and flash programming support (https://wiki.segger.com/HPMicro_HPM53).
- MindMotion MM32F5233: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F5).
- MindMotion MM32F5333: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F5).
- MindMotion MM32G0001: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G0).
- MindMotion MM32G5333: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G5).
Other changes:
Control Panel
- Added "MemMap" tab.
Device Support
- Renesas R7G2: Verification of option-setting bytes could fail. Fixed.
DLL
- PIC32MX / MZ: Added command string "PIC32_StayInICSPProgMode". See https://wiki.segger.com/J-Link_Command_Strings#PIC32_StayInICSPProgMode
- SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
Firmware
- Flasher ARM V5-1: SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
- Flasher ARM V5-1: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
- Flasher ARM V5: SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
- Flasher ARM V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
- Flasher Compact V5: SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
- Flasher Compact V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
- Flasher Hub-12 V1: WebIF "Files" tab: When uploading one or more files to a module, the file would be listed before the upload was finished and it could be deleted by the user, causing unexpected behavior to occurr. Fixed.
- Flasher Hub-12 V1: WebIF "Files" tab: While uploading one or more files to a module, other operations (e.g. connecting to FTP server) could fail. Fixed.
- Flasher Portable PLUS V5: SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
- Flasher PRO V5-1: SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
- Flasher PRO V5-1: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
- Flasher PRO V5: SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
- Flasher PRO V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
- Flasher PRO XL V5-1: SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
- Flasher PRO XL V5: SFL: ARM7/9: Depending on the compiler + linker used to generate an SFL, executing the RAMCode failed because J-Link set the PC to an odd value. Fixed.
- Flasher PRO XL V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
- J-Link OB RA4M2-CortexM: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link OB RA4M2-CortexM: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link OB RA4M2-Full: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link OB RA4M2-Full: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link OB RA4M2-Renesas: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link OB RA4M2-Renesas: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link OB RA4M2-RISCV: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link OB RA4M2-RISCV: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link-OB-K22-CortexA: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link-OB-K22-CortexA: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link-OB-K22-CortexM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link-OB-K22-CortexM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link-OB-K22-NordicSemi: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link-OB-K22-NordicSemi: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link-OB-K22-Qorvo: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link-OB-K22-Qorvo: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link-OB-K22-RISCV: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link-OB-K22-RISCV: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link-OB-K22-SiFive: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link-OB-K22-SiFive: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link-OB-SAM3U128-V3: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link-OB-SAM3U128-V3: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
- J-Link-OB-XMC4200 / iMOTION-Link: VCOM: A warning message is now printed in the terminal in case baud rate is set too high or too low.
- J-Link-OB-XMC4200 / iMOTION-Link: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
XVCD Server
- Exiting the application by pressing 'any key' after an error occured did not work. Fixed.
Version V7.92d (2023-09-07)
Highlights:
Device Support
- CVA BlueWhale CVM0114: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM011x).
Other changes:
Commander
- Added USB J-Link selection via nickname to the command line interface (https://wiki.segger.com/J-Link_Commander#USB).
- Command "SetBP": Software instruction breakpoints: RISC-V: Changed breakpoint mode type from "force 32-bit" to "auto".
- The "ShowHWStatus" command could incorrectly report target current measurements of more than 4kA, depending on calibration of connected probe. Fixed.
Device Support
- Added 3rd party debug and flash support for Vorago VA108XX and VA416XX devices.
- Micronas HVC5xxx device series: Reset was not handled correctly. Fixed.
- Renesas R7G2: Verification of option-setting bytes could fail. Fixed.
- ST SR6P6xx: FW cache was not flushed after Reset. Fixed.
- ST STM32F446: QSPI flash bank was not selectable. Fixed.
- Xilinx Zynq 7000 series (e.g. XC7Z020): Added DDR RAM region @ 0x00080000 as "excluded" to "before startup completion" memory map, to avoid debugger accesses to this region before DDR RAM is initialized (can result in the device to hang)
DLL
- CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Extended command string "map add" by optional parameters <RegionName> and <MapType>.
- RISC-V: Software instruction breakpoints: Added support for MODE0 (auto) breakpoint type, where breakpoint instruction to be used is derived from presence of C-extension reported by MISA.
Firmware
- Flasher ARM V5-1: CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Flasher ARM V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- Flasher ARM V5: CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Flasher ARM V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- Flasher Compact V5: CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Flasher Compact V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- Flasher Hub-12 V1: Changed default for handshake mode from "disabled" to "enabled".
- Flasher Hub-12 V1: Flasher Hub log file updates did not work reliably. Fixed.
- Flasher Hub-12 V1: FTP: Opening the "Logs" directory could cause unexpected behavior (e.g. no directory contents were shown, web server failed to send files to client, ...). Fixed.
- Flasher Hub-12 V1: FTP: When uploading empty files to one or more modules, no files were created on the modules at all. Fixed.
- Flasher Hub-12 V1: Implemented firmware update via web interface.
- Flasher Hub-12 V1: Implemented module firmware update via web interface.
- Flasher Hub-12 V1: Inspecting a folder on a module (e.g. via FTP) with more than 16 entries (files or directories) inside would crash Flasher Hub. Fixed.
- Flasher Hub-12 V1: Web interface did not reliably detect server connection breakdown. Fixed.
- Flasher Hub-12 V1: Web server could report "503 Service unavailable" when switching between tabs or opening multiple web sessions in parallel. Fixed.
- Flasher Hub-12 V1: WebIF "Configuration > Flasher Modules" tab: Saving a configuration with one or more modules disabled would always throw an error. Fixed.
- Flasher Hub-12 V1: WebIF "Files" tab: Opening the "Logs" directory could cause unexpected behavior (e.g. no directory contents were shown, web server failed to send files to client, ...). Fixed.
- Flasher Hub-12 V1: WebIF "Files" tab: When uploading empty files to one or more modules, no files were created on the modules at all. Fixed.
- Flasher Hub-12 V1: WebIF "UART" tab: Typo "firwmare" --> "firmware". Fixed.
- Flasher Portable PLUS V5: CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Flasher Portable PLUS V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- Flasher PRO V5-1: CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Flasher PRO V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- Flasher PRO V5: CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Flasher PRO V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- Flasher PRO XL V5-1: CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Flasher PRO XL V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- Flasher PRO XL V5: CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.
- Flasher PRO XL V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- J-Link PRO V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- J-Link PRO V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- J-Link PRO V6: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- J-Link ULTRA+ V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- J-Link ULTRA+ V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
- J-Link ULTRA+ V6: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
GDB Server
- Added USB J-Link selection via nickname to the command line interface (https://wiki.segger.com/J-Link_GDB_Server#-select).
- Added USB J-Link selection via nickname to the graphical user interface.
GDB Server CL
- Added USB J-Link selection via nickname to the command line interface (https://wiki.segger.com/J-Link_GDB_Server#-select).
J-Flash SPI
- Added auto-detect support for SST SST25VF020B SPI flash that does not provide a page buffer but only single-byte programming.
J-Link Package
- Windows: Installer: Changed to NOT install USB driver by default.
XVCD Server
- Added J-Link XVCD Server to software package. More info: https://wiki.segger.com/J-Link_XVCD_Server
Version V7.92c (2023-08-30)
Highlights:
Device Support
- Infineon CYT2CL: Added debug and flash programming support(https://wiki.segger.com/Infineon_CYT2CL).
- NXP RW61x: Added debug and flash programming support(https://wiki.segger.com/NXP_RW61x).
- ST STM32F446: Added flash programming support for external QSPI flash.
Other changes:
Device Support
- Renesas RX24T: Incorrect family name was reported ("RX23T" instead of "RX24T"). Fixed.
- Renesas RX26T: Added debug & flash programming support.
DLL
- Probe selection dialog did not show the correct image for Flasher Hub-12. Fixed.
- Trace: Overflow counter for ETMv4 was not working correctly. Fixed.
DLL Updater
- Added wiki link to DLL updater.
Firmware
- Flasher Portable PLUS V5: Progress bars for Erase and Program were not updated correctly. Fixed.
Version V7.92b (2023-08-23)
Highlights:
Device Support
- NXP S32K358: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
Other changes:
Device Support
- Aurix TC3xx: Device Bulk erase failed on Data Flash DF1. Fixed.
- Infineon TLE988x/TLE989x: Target reset did not work properly. Fixed.
- Qorvo PAC55xx series: Erase did not work for addresses >= 0x10000. Fixed.
- Renesas RX230: Flash programming in big endian mode did not work. Fixed.
- Renesas RX231: Flash programming in big endian mode did not work. Fixed.
- Renesas RX23T: Flash programming in big endian mode did not work. Fixed.
- Renesas RX24T: Flash programming in big endian mode did not work. Fixed.
- ST STM32G4 device series: Loader names contained invalid characters (space). Fixed.
- ST STM32L4 device series: Loader names contained invalid characters (space). Fixed.
DLL
- N-Trace: When recording longer periods of time, instruction counters might be lower than they should. Fixed.
- SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
Firmware
- Flasher ARM V5-1: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
- Flasher ARM V5: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
- Flasher Compact V5: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
- Flasher Portable PLUS V5: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
- Flasher PRO V5-1: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
- Flasher PRO V5: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
- Flasher PRO XL V5-1: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
- Flasher PRO XL V5: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
J-Link Package
- Installer: Option to receive general update notifications will now use the previously selected option as default (if not available: opt-in).
- Installer: Option to receive update notifications for security updates is now opt-out, instead of opt-in.
RTT Viewer
- Configuration dialog: Serialnumbers with >= 9 didgets could not be entered. Fixed.
Version V7.92a (2023-08-16)
Device Support
- Infineon Traveo T2G: Programming the supervisory flash could fail due to a timeout. Fixed.
- ST STM32L476 QSPI support: Added support for pin configuration "CLK@PB10_nCS@PB11_D0@PB1_D1@PB0_D2@PA7_D3@PA6".
- ST STM32L476 QSPI support: Added support for pin configuration "CLK@PE10_nCS@PE11_D0@PE12_D1@PE13_D2@PE14_D3@PE15".
- ST STM32L496 QSPI support: Added support for pin configuration "CLK@PA3_nCS@PB11_D0@PB1_D1@PB0_D2@PA7_D3@PA6".
J-Flash SPI
- When using the '-openprj' option, the last opened project was opened prior to the selected project. Fixed.
Manual
- UM08022 Flasher: Moved to SEGGER wiki: https://wiki.segger.com/UM08022_Flasher
Version V7.92 (2023-08-11)
Highlights:
DnD Conditioner
- Added drag & drop programming file conditioner to J-Link software package. (https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
Other changes:
Firmware
- Flasher ARM V5-1: PCodes in Config files were not loaded correctly. Fixed.
- Flasher ARM V5-1: The JTAG Interface was initialized on startup even when not used. Fixed.
- Flasher ARM V5: PCodes in Config files were not loaded correctly. Fixed.
- Flasher ARM V5: The JTAG Interface was initialized on startup even when not used. Fixed.
- Flasher Compact V5: PCodes in Config files were not loaded correctly. Fixed.
- Flasher Compact V5: The JTAG Interface was initialized on startup even when not used. Fixed.
- Flasher Portable PLUS V5: PCodes in Config files were not loaded correctly. Fixed.
- Flasher Portable PLUS V5: Selection of Images did not work properly under certain circumstances. Fixed.
- Flasher Portable PLUS V5: The JTAG Interface was initialized on startup even when not used. Fixed.
- Flasher PRO V5-1: PCodes in Config files were not loaded correctly. Fixed.
- Flasher PRO V5-1: The JTAG Interface was initialized on startup even when not used. Fixed.
- Flasher PRO V5: PCodes in Config files were not loaded correctly. Fixed.
- Flasher PRO V5: The JTAG Interface was initialized on startup even when not used. Fixed.
- Flasher PRO XL V5-1: PCodes in Config files were not loaded correctly. Fixed.
- Flasher PRO XL V5-1: The JTAG Interface was initialized on startup even when not used. Fixed.
- Flasher PRO XL V5: PCodes in Config files were not loaded correctly. Fixed.
- Flasher PRO XL V5: The JTAG Interface was initialized on startup even when not used. Fixed.
- J-Link OB-K22-Qorvo: Added WinUSB (driverless) mode support.
- J-Link OB-K22-Qorvo: Made sure that firmware boots in driverless mode by default.
Version V7.90a (2023-08-09)
Highlights:
DLL
- ST STM32H562AG, STM32H562IG, STM32H562RG, STM32H562VG, STM32H562ZG: Added debug & flash programming support.
Trace
- Published out-of-the-box trace example for Renesas RZ/A2M series: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Device Support
- ST SR6P6x : ECC RAM was not initialized on connect to cluster 0 core 0, but on reset. Now initialized on connect. Fixed.
- ST SR6Pxxx/ SR6Gxxx : Security watchdog was not disabled when connecting to DME or DSPH core. Fixed.
- TI CC2340: In case of a image with "disable debug interface" configuration was programmed, verify erroneusly failed. Fixed.
Firmware
- Flasher Portable PLUS V5: Save and restore image selection on power cycle.
- Flasher Portable PLUS V5: U-Flash Projects in sub-directories displayed path and not the "display text". Fixed.
- J-Link OB-K22-CortexA: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link OB-K22-CortexA: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link OB-K22-CortexA: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link OB-K22-CortexM: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link OB-K22-CortexM: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link OB-K22-CortexM: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link OB-K22-Full: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link OB-K22-Full: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link OB-K22-Full: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link OB-K22-Qorvo: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link OB-K22-Qorvo: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link OB-K22-Qorvo: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link OB-K22-RISCV: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link OB-K22-RISCV: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link OB-K22-RISCV: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link-OB-K22-NordicSemi: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link-OB-K22-NordicSemi: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link-OB-K22-NordicSemi: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link-OB-nRF5340-NordicSemi: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link-OB-nRF5340-NordicSemi: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link-OB-nRF5340-NordicSemi: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link-OB-SAM3U128-V2-NordicSemi: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link-OB-SAM3U128-V2-NordicSemi: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link-OB-SAM3U128-V2-NordicSemi: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link-OB-SAM3U128-V3: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link-OB-SAM3U128-V3: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link-OB-SAM3U128-V3: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link-OB-STM32F072-128KB-CortexM: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
- J-Link-OB-STM32F072-128KB-CortexM: Drag & Drop programming: If host sent data file contents out of order, flash programming could fail. Fixed. (Files must be conditioned by the J-Link Drag & Drop Conditioner utility: https://wiki.segger.com/J-Link_drag_and_drop_programming#Data_file_conditioner_utility)
- J-Link-OB-STM32F072-128KB-CortexM: Drag & Drop programming: Programmed data could be corrupted if read-modify-write was necessary because read-modify-write did not work properly. Fixed.
- J-Link-OB-XMC4200 / iMOTION-Link: Timing for Infineon SPD protocol was incorrect which could cause debug sessions via SPD to fail on some XMC chips. Introduced in V7.82e. Fixed.
Version V7.90 (2023-08-02)
Highlights:
Device Support
- ISSI IS25LP025E, IS25WP025E and IS25LQ025B: Added flash programming support to all (Q)SPI flash based algorithms.
- ISSI IS25LP10E, IS25WP10E and IS25LQ10B: Added flash programming support to all (Q)SPI flash based algorithms.
- ISSI IS25LP512E, IS25WP512E and IS25LQ512B: Added flash programming support to all (Q)SPI flash based algorithms.
J-Flash SPI
- ISSI IS25LP025E, IS25WP025E and IS25LQ025B: Added direct mode flash programming support
- ISSI IS25LP10E, IS25WP10E and IS25LQ10B: Added direct mode flash programming support
- ISSI IS25LP512E, IS25WP512E and IS25LQ512B: Added direct mode flash programming support
Other changes:
Commander
- J-Link command files: Added support for C-comments (/* ... */) that spread over multiple lines in command file.
- J-Link command files: Lines that only consist of a comment threw "unkown command" errors. Introduced in V7.88l. Fixed.
Device Support
- Infineon: XMC devices via SPD protocol: Connecting failed when using SPD protocol due to "SWD switching sequence" bug which was fixed in this version as well.
- ST SR6P6C4_Cluster_0_R52_0 and SR6P6C8_Cluster_0_R52_0: J-Link init code for disabling the watchdog was incorrect and could lead to watchdog unit to become inaccessible until reset. Fixed.
DLL
- Added new exec command "DisableSoftwareBPs" which can be used to disable the usage of software breakpoints.
- ARMv8-A/R AArch32 (e.g. Cortex-R52): Added support for 64-bit CP15 registers.
- DLL: Under certain circumstances the trace analyzer could crash. Fixed.
- RTT: Search ranges specified before connect were overridden. Fixed.
- SWD: When sending the SWD switching sequence to the target device, the deprecated part of the sequence (needed by some older Cortex-M based devices) was sent incorrectly. Fixed.
Firmware
- Flasher Portable PLUS V5: Changed operating concept: Automatic key repetition for SEL button, decrement on PWR button short press..
- Flasher Portable PLUS V5: Flasher Portable PLUS now supports up to 99 images.
- J-Link EDU Mini V1: Added WinUSB (driverless) mode support.
- J-Link EDU/BASE/PLUS V11: Standby mode: When entering standby mode after 5s of not being in use, J-Link disabled its target interface voltage reference, which could cause problems with some NXP eval boards that have no pull-up populated on the reset line. Fixed.
- J-Link EDU/BASE/PLUS V12: Standby mode: When entering standby mode after 5s of not being in use, J-Link disabled its target interface voltage reference, which could cause problems with some NXP eval boards that have no pull-up populated on the reset line. Fixed.
GDB Server
- ARMv8-A/R AArch32 (e.g. Cortex-R52): Added support for 64-bit CP15 registers.
Version V7.88n (2023-07-26)
Device Support
- CVA BlueWhale CVM011x: Erase chip will not perform an unlock anymore.
- CVA BlueWhale CVM011x: When write protected flash areas are detected on connect, there will be no option for a mass erase unlock anymore.
- ST STM32U5: Connect/unsecure failed in case TZEN == 1 & RDP was set. Fixed.
DLL
- Added command strings "RISCV_SetATBBaseAddr". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetATBBaseAddr)
- Added command strings "RISCV_SetPIBBaseAddr". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetPIBBaseAddr)
- Added command strings "RISCV_SetSRAMBaseAddr". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetSRAMBaseAddr)
- Added command strings "RISCV_SetTFBaseAddr". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetTFBaseAddr)
- Added command strings "RISCV_UseNexusViaATB". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_UseNexusViaATB)
- Extended command string "RISCV_SetTEBaseAddr" to accept optional "APIndex" parameter.. (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetTEBaseAddr)
- Pin trace would not start on Renesas RZ/A2M devices. Introduced with V7.80b. Fixed.
- Trace: RISC-V N-Trace: Under certain circumstances SRAM/buffer tracing could crash the device as the wrong SRAM base address was calculated. Fixed.
- Trace: RISC-V: Added support for N-Trace in combination with Arm CoreSight peripherals like TPIU etc.
Firmware
- Flasher ARM V5-1: An active "Read" task was not clearly signalled by the LED. Fixed.
- Flasher ARM V5: An active "Read" task was not clearly signalled by the LED. Fixed.
- Flasher Compact: An active "Read" task was not clearly signalled by the LED. Fixed.
- Flasher PRO V5 XL: An active "Read" task was not clearly signalled by the LED. Fixed.
- Flasher PRO V5-1 XL: An active "Read" task was not clearly signalled by the LED. Fixed.
- Flasher PRO V5-1: An active "Read" task was not clearly signalled by the LED. Fixed.
- Flasher PRO V5: An active "Read" task was not clearly signalled by the LED. Fixed.
- J-Link OB CALLIOPE MINI V2.1: Added Drag & Drop target application update via Webbrowser (https://www.segger.com/jlink_webusb_update_target_firmware.html).
GDB Server
- ARMv8-A/R AArch32 (e.g. Cortex-R52): Accessing the following PMU CP15 registers did not work properly (wrong encoding used): PMCR, PMCNTENSET, PMCNTENCLR, PMOVSR, PMSWINC, PMSELR, PMCEID0, PMCEID1, PMCCNTR. Fixed.
- ARMv8-A/R AArch32 (e.g. Cortex-R52): Added support for CP15 register "ATS1CPRP".
- ARMv8-A/R AArch32 (e.g. Cortex-R52): Added support for CP15 register "ATS1CPWP".
- FreeRTOS plugin: Armv8-M (e.g. Cortex-M33): Thread/Task-specific register values were shown incorrectly (e.g. PC showed LR value). Fixed.
J-Flash
- 'Start Application' issued a Go-Halt-Go sequence instead of a single Go. Fixed.
Version V7.88m (2023-07-19)
Commander
- Command string "SelectModule" did not work properly in conjunction with "usb" command of J-Link Commander. Fixed.
- Some J-Link command strings (e.g. "EnableEraseAllFlashBanks") were refused as unknown when loaded from a command file. Introduced in V7.88l. Fixed.
Device Support
- DiaSemi DA1469x: Programming could fail if target firmware has changed clock settings. Fixed.
- Micronas HVC5223C: Added debug & flash programming support.
- NXP MCXN10: Reset did not work properly in case of a bootable application got programmed. Fixed.
- Renesas R5F21286JSP and R5F21286KSP (R8C Family): Added flash programming support.
Firmware
- Flasher ARM V5-1: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
- Flasher ARM V5: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
- Flasher Compact: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
- Flasher Portable PLUS V5: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
- Flasher PRO V5-1: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
- Flasher PRO V5: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
- Flasher PRO XL V5-1: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
- Flasher PRO XL V5: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
- J-Link OB CALLIOPE MINI V2.1: Added Drag & Drop target application update via Webbrowser (https://www.segger.com/jlink_webusb_update_target_firmware.html).
- J-Link OB CALLIOPE MINI V2.1: Drag & Drop: Added support for the Universal Hex file format (https://tech.microbit.org/software/spec-universal-hex).
GDB Server
- ARM7/9: "monitor reg" now also accepts USR, FIQ, SVC, ABT, IRQ & UND registers (e.g. "monitor reg r13_svc").
RTT
- SEGGER_RTT_Syscalls_KEIL.c: _sys_tmpnam() was returning a value for __ARMCC_VERSION >= 6190000, even though function would be void in this case. Fixed.
Version V7.88l (2023-07-13)
Highlights:
Device Support
- Artery AT32F435: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F43x).
- Artery AT32F437: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F43x).
- e-peas EDMS105N: Added unprotect mechanism for e-peas EDMS105N.
- ST STM32H5: Added QSPI flash programming support for pin configuration CLK@PF10_nCS@PG6_D0@PF8_D1@PF9_D2@PC2_D3@PF6_D4@NA_D5@NA_D6@NA_D7@NA.
Trace
- Published out-of-the-box trace example for Silicon Labs EFR32ZG23 series: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- If a C/C++ comment was used in a command that accepts parameters, the comment was accidentally interpreted as parameter. Fixed.
Device Support
- e-peas EDMS105N: Device family name was wrong. Fixed.
- Mediatek MT7697: Programming could fail due to wrong restoration of clock settings. Fixed.
- NXP iMXRT117x FlexSPI1 support: Added support for pin configuration "nCS@AD18_CLK@AD19_D0@AD20_D1@AD21_D2@AD22_D3@AD23"
- Reworked Traveo T2G (formerly Traveo II) support.
- SemiDrive D3xxx/E3xxx: Speed up ECC RAM initialization in connection sequence.
- ST STM32H74x/STM32H75x: Added new pin configuration "CLK@PB2_nCS@PB10_D0@PC9_D1@PF9_D2@PF7_D3@PF6" for QSPI flash.
- TI CC2340: Connect to an erased device / device with invalid CCFG block did not work. Introduced in V7.88d. Fixed.
DLL
- Added command string "SetLogVerbose 1/0" to increase verbosity of J-Link log file.
- ARMv7-A/R (e.g. Cortex-R5): Aborts caused by reading non-existent / non-accessible CP15 registers were not cleared correctly so that a following debug operation (read memory, go, step, ...) could fail. Fixed.
- In verbose mode 1 now all data of memory accesses is logged.
Firmware
- Flasher ARM V5-1: Added QUIT command to CLI to close active telnet connections via script.
- Flasher ARM V5: Added QUIT command to CLI to close active telnet connections via script.
- Flasher Portable PLUS V5: Stand-alone mode: Batch programming: U-Flash configurations were not shown correctly on display. Fixed.
- Flasher Pro V5-1: Added QUIT command to CLI to close active telnet connections via script.
- Flasher Pro V5: Added QUIT command to CLI to close active telnet connections via script.
- Flasher Pro XL V5-1: Added QUIT command to CLI to close active telnet connections via script.
- Flasher Pro XL V5: Added QUIT command to CLI to close active telnet connections via script.
GDB Server
- Improved verify download log message.
J-Flash
- When connecting via JTAG failed, J-Flash could report "success" for the connect operation, by accident. Fixed.
Version V7.88k (2023-07-05)
Highlights:
Device Support
- e-peas EDMS105N: Added debug and flash programming support(https://wiki.segger.com/e-peas_EDMS105N).
- Renesas RA4E1: Added RAMLess support for data flash.
- Renesas RA4M2: Added RAMLess support for data flash.
- Renesas RA4M3: Added RAMLess support for data flash.
- Renesas RA6E1: Added RAMLess support for data flash.
- Renesas RA6M4: Added RAMLess support for data flash.
- Renesas RA6M5: Added RAMLess support for data flash.
- Renesas RA6T2: Added RAMLess support for data flash.
- Silicon Labs EFR32xG28x: Added debug and flash programming support (https://wiki.segger.com/Silicon_Labs_EFR32xG28).
- ST SR6Gxxx/SR6Pxxx: Added debug support for DME core.
- ST STM32U575/585: Added SPI flash programming support for CLK@PF10_nCS@PA2_D0@PF8_D1@PF9_D2@PF7_D3@PF6 pin configuration.
- ST STM32U575/585: Added SPI flash programming support for CLK@PF4_nCS@PI5_D0@PF0_D1@PF1_D2@PF2_D3@PF3 pin configuration.
- ST STM32U575/585: Added SPI flash programming support for CLK@PH6_nCS@PI5_D0@PI3_D1@PI2_D2@PI1_D3@PH8 pin configuration.
- ST STM32U595/599: Added SPI flash programming support for CLK@PF10_nCS@PA2_D0@PF8_D1@PF9_D2@PF7_D3@PF6 pin configuration.
- ST STM32U595/599: Added SPI flash programming support for CLK@PF4_nCS@PI5_D0@PF0_D1@PF1_D2@PF2_D3@PF3 pin configuration.
- ST STM32U595/599: Added SPI flash programming support for CLK@PH6_nCS@PI5_D0@PI3_D1@PI2_D2@PI1_D3@PH8 pin configuration.
- ST STM32WBAxx: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WBA).
- TI CC2662R1: Added debug & flash programming support.
DLL
- Added native trace buffer and pin trace support for Renesas RA6M2 series. Example project is available here: https://wiki.segger.com/Renesas_RA6M2
Other changes:
Device Support
- NXP iMXRT117x FlexSPI support: Under certain circumstances writing less than four bytes could fail. Fixed.
- Renesas RZ/N2L: CFI NOR flash programming did not work. Fixed.
- Renesas RZ/T2M: Under certain circumstances QSPI flash programming could fail. Fixed.
- TI MSPM0G: Erasing a single sector would always erase the first sector, regardless which sector was selected.
- TI MSPM0L: Erasing a single sector would always erase the first sector, regardless which sector was selected.
Firmware
- J-Link OB Apollo4 CortexM: VCOM functionality did not work correctly when sending data to target system. Fixed.
Version V7.88j (2023-06-28)
Highlights:
Device Support
- NXP i.MXRT500: Added debug support for Cadence Tensilica Fusion F1 DSP (https://wiki.segger.com/NXP_i.MXRT500).
- ST STM32U5A: Added SPI flash programming support for CLK@PF10_nCS@PA2_D0@PF8_D1@PF9_D2@PF7_D3@PF6 pin configuration.
- ST STM32U5A: Added SPI flash programming support for CLK@PF4_nCS@PI5_D0@PF0_D1@PF1_D2@PF2_D3@PF3 pin configuration.
- ST STM32U5A: Added SPI flash programming support for CLK@PH6_nCS@PI5_D0@PI3_D1@PI2_D2@PI1_D3@PH8 pin configuration.
- ST STM32U535/545xx: Added debug and flash programming support(https://wiki.segger.com/ST_STM32U5).
- Toshiba TMPM3HQF10BFG: Added debug and flash programming support (https://wiki.segger.com/Toshiba_TMPM3H).
Other changes:
Configurator
- Configuration dialog: Added elements for configuring a fixed target reference voltage (VTref).
Device Support
- CVA BlueWhale CVM011x: Programming of data flash failed if EEPROM hardware emulation was enabled. Fixed.
- Renesas RA family: Added support for protection unlock via ALeRASE code.
- Renesas Synergy family: Added support for protection unlock via ALeRASE code.
- ST STM32H5: Added device specific connect.
DLL
- System tray icon: After showing a dialog (e.g. for flash programming), clicking the system tray icon did not open the J-Link Control Panel anymore. Fixed.
DLL Updater
- FORTH, Inc. SwiftX was not found. Fixed.
Firmware
- Flasher ARM V5-1: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- Flasher ARM V5: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- Flasher Compact V5: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- Flasher Portable PLUS V5: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- Flasher PRO V5-1: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- Flasher PRO V5: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- Flasher PRO XL V5-1: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- Flasher PRO XL V5: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
J-Flash
- Under certain circumstances J-Flash could crash on read when using CFI based flash loaders. Fixed.
- Under certain circumstances, using a RAMLess flash loader with J-Flash could fail. Fixed.
J-Flash SPI
- Added support for FRAM Infineon FM25V02A.
Version V7.88i (2023-06-20)
Device Support
- Micron MT25QU256, MT25QU512, MT25QU01, MT25QU02: Under certain circumstances flash programming could fail. Introduced with 7.88f. Fixed.
- ST STM32U575xG: Erasing of internal flash in single-bank flash mode did not work. Fixed.
- TI MSPM0G (PG2): NONMAIN programming did not work. Fixed.
DLL
- J-Link script files: Added predefined constants for MEM-AP access configuration: JLINK_CORESIGHT_AP_CSW_AUTO_INC, JLINK_CORESIGHT_AHB_CSW_DEFAULT, JLINK_CORESIGHT_APB_CSW_DEFAULT, JLINK_CORESIGHT_AXI_CSW_DEFAULT
- J-Link script files: Added predefined constants for MEM-AP access width configuration: JLINK_CORESIGHT_AP_CSW_8_BIT, JLINK_CORESIGHT_AP_CSW_16_BIT, JLINK_CORESIGHT_AP_CSW_32_BIT, JLINK_CORESIGHT_AP_CSW_64_BIT
- Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Under some circumstances, the USB probe selection dialog did not display the probe serial number of nickname. Introduced with V7.88f. Fixed.
Firmware
- Flasher ARM V5-1: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Flasher ARM V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- Flasher ARM V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Flasher ARM V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- Flasher Compact V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Flasher Compact V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- Flasher Portable PLUS V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Flasher Portable PLUS V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- Flasher PRO V5-1: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Flasher PRO V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- Flasher PRO V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Flasher PRO V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- Flasher PRO XL V5-1: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Flasher PRO XL V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- Flasher PRO XL V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
- Flasher PRO XL V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link EDU/BASE/PLUS V11: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link EDU/BASE/PLUS V12: USB Web Server: Added elements for configuring VTref to "Config" tab.
- J-Link EDU/BASE/PLUS V12: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link PRO V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link PRO V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link PRO V6: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link ULTRA+ V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link ULTRA+ V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link ULTRA+ V6: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link WiFi V1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Link-OB-S124: Under special circumstances, USB connection was unstable when using this J-Link OB with the Renesas Flash Programmer (RFP) utility. Introduced in V7.86h. Fixed.
- J-Trace PRO V3 Cortex: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Trace PRO V3 CortexM: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
- J-Trace PRO V3 RISC-V: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
J-Link USB Web Server
- Landing page: Added warning icon when connected J-Link does not support USB Web Server.
- Landing page: Changed background color to gray when no J-Link is connected.
Version V7.88h (2023-06-16)
Highlights:
Device Support
- ST SR6P7Cx: Added debug and flash programming support (https://wiki.segger.com/ST_SR6P7).
Other changes:
DLL
- Linux: The system tray icon was not removed when a J-Link connection was closed. Introduced with V7.88e. Fixed.
- macOS: The system tray icon was not removed when a J-Link connection was closed. Introduced with V7.88e. Fixed.
- SWO: Removed duplicate init steps, making SWO init faster.
RTT
- SEGGER_RTT.h: Contained a relative include path to SEGGER_RTT_Conf.h by accident. Fixed.
Version V7.88g (2023-06-13)
Highlights:
Device Support
- TI CC1311P3: Added debug and flash programming support (https://wiki.segger.com/TI_CC1311P3).
- TI CC1314R10: Added debug and flash programming support(https://wiki.segger.com/TI_CC1314R10).
Other changes:
Control Panel
- Flash tab: Log did not work. Fixed.
- Menu: Changed order of tabs.
Device Support
- HDSC HC32F460: Utilization of WDT or SWDT could cause failing of programming. Fixed.
DLL
- The probe selection dialog showed a generic image for J-Link EDU Minis. Fixed.
- The probe selection dialog showed a generic image for J-Link EDUs. Fixed.
- When connecting to a ST-LINK, a warning message box was shown ("Unknown firmware string: [...]"). Introduced with V7.88f. Fixed.
Firmware
- Flasher ARM V5-1: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher ARM V5-1: SFL: If the default stack size size of 512 bytes or initial data area size did not fit, garbage was calculated. Introduced in V7.88f by the SFL default stack size change. Fixed.
- Flasher ARM V5-1: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher ARM V5: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher ARM V5: SFL: If the default stack size size of 512 bytes or initial data area size did not fit, garbage was calculated. Introduced in V7.88f by the SFL default stack size change. Fixed.
- Flasher ARM V5: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher Compact V5: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher Compact V5: SFL: If the default stack size size of 512 bytes or initial data area size did not fit, garbage was calculated. Introduced in V7.88f by the SFL default stack size change. Fixed.
- Flasher Compact V5: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher Portable PLUS V1: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher Portable PLUS V1: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher Portable PLUS V5: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher Portable PLUS V5: SFL: If the default stack size size of 512 bytes or initial data area size did not fit, garbage was calculated. Introduced in V7.88f by the SFL default stack size change. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher PRO V5-1: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher PRO V5-1: SFL: If the default stack size size of 512 bytes or initial data area size did not fit, garbage was calculated. Introduced in V7.88f by the SFL default stack size change. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher PRO V5: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher PRO V5: SFL: If the default stack size size of 512 bytes or initial data area size did not fit, garbage was calculated. Introduced in V7.88f by the SFL default stack size change. Fixed.
- Flasher PRO V5: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher PRO XL V5-1: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher PRO XL V5-1: SFL: If the default stack size size of 512 bytes or initial data area size did not fit, garbage was calculated. Introduced in V7.88f by the SFL default stack size change. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher PRO XL V5: *.pex files are now stored in the *.CFG file, rather than as separate files. Prevents accidentally mixing a *.pex from config A with CFG file from config B which may be for a completely different device.
- Flasher PRO XL V5: SFL: If the default stack size size of 512 bytes or initial data area size did not fit, garbage was calculated. Introduced in V7.88f by the SFL default stack size change. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Added support for user-specified script files (either specified by XML files in JLinkDevices folder or directly in J-Flash project).
- Flasher: Storing *.pex files in the *.CFG file is no longer compatible with Flasher ARM/PRO V4 and earlier.
Version V7.88f (2023-06-09)
Highlights:
Device Support
- CAST BA53: Added debug support (https://wiki.segger.com/CAST_BA53)
- HPMicro HPM61xx, HPM63xx, HPM64xx, HPM6730 , HPM6750: Added 3rd party flash programming support for XPI1 flash bank.
- Silicon Labs EFR32FG25x: Added debug and flash programming support (https://wiki.segger.com/Silicon_Labs_EFR32xG25).
Other changes:
Configurator
- J-Trace PRO RISC-V was listed as "J-Link (unknown)". Fixed.
Device Support
- SemiDrive E3 multicore devices: Could not connect to CPU 1-4. Fixed.
- ST STM32F7 device series: Added QSPI flash programming support for pin configuration "CLK@PB2_nCS@PB6_D0@PF8_D1@PD12_D2@PF7_D3@PD13".
- ST STM32H7 single core devices: SWO did not work out of the box. Introduced V7.84b. Fixed.
DLL
- Cortex-A/R: Superfluous auto detection of CPU clock frequency could cause fail of programming. Fixed.
- Infineon TLE988x/TLE989x: Added debug & flash programming support.
- J-Link DLL did not deinitialize the SWO config on target side correctly which could lead to issues on consecutive debug session where SWO was used. Fixed.
- macOS: Dialogs (e.g. the USB probe selection dialog) were not the active window when spawned, causing them not to have keyboard focus until clicked manually. Fixed.
- macOS: When showing dialogs, an additional application icon was shown in the Dock as well as in the App Switcher (Cmd + Tab). Fixed.
- Probe selection dialog: Changed wording from "emulator" to "probe".
- Probe selection dialog: Product name, nickname and product image are now displayed for each connected probe.
- Silicon Labs EFR32xG23/G24/G25: Watchdog was not feed during programming. Fixed.
- ST STM32F4: OPTCR WRP value after unlock was not the correct production value for all devices. Fixed.
- ST STM32G47 device series: Added native single bank support via selectable loader.
- ST STM32H5: Flash programming did not work with TrustZone enabled and SECWM regions set to non-secure. Fixed.
- ST STM32H7: Max. QSPI flash size has been raised to 256MB.
- ST STM32H7: Read of last byte in memory region of QSPI flash could fail. Fixed.
Firmware
- Flasher ARM V5-1: Cortex-A/R: Stand-alone mode did not work. Fixed.
- Flasher ARM V5-1: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
- Flasher ARM V5-1: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
- Flasher ARM V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
- Flasher ARM V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
- Flasher ARM V5: Stand-alone mode: Cortex-M: If no script file was given, AHB-AP was assumed to always be AP0 which did not match for some chips like Atmosic ATM3330e. Fixed. (Added AP scan routine)
- Flasher ARM V5: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
- Flasher Compact V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
- Flasher Compact V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
- Flasher Compact V5: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
- Flasher package: Added start menu entry for J-Link commander.
- Flasher Portable PLUS V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
- Flasher Portable PLUS V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
- Flasher Portable PLUS V5: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
- Flasher PRO V5-1: Cortex-A/R: Stand-alone mode did not work. Fixed.
- Flasher PRO V5-1: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
- Flasher PRO V5-1: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
- Flasher PRO V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
- Flasher PRO V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
- Flasher PRO V5: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
- Flasher PRO XL V5-1: Cortex-A/R: Stand-alone mode did not work. Fixed.
- Flasher PRO XL V5-1: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
- Flasher PRO XL V5-1: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
- Flasher PRO XL V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
- Flasher PRO XL V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
- Flasher PRO XL V5: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
J-Scope
- Exporting boolean values to CSV did not work. Fixed.
RTT
- Added support for ARMv8.1-M architecture (e.g. Cortex-M55 / M85) to RTT sources.
- GCC compiler: SEGGER_RTT.c and SEGGER_RTT.h did throw warnings if "-Wcast-align" warning was enabled. Fixed.
Version V7.88e (2023-05-31)
DLL
- Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
- Infineon XMC7000 series: Updated device specific handling and added support for additional flash banks.
- JTAG auto-detection: Some TI devices were erroneously detected as ICEPick. Fixed.
- Linux: Added a system tray icon for quick access to the J-Link Control Panel.
- macOS: Added a system tray icon for quick access to the J-Link Control Panel.
- SemiDrive D32xx: Added debug and flash programming support (https://wiki.segger.com/SemiDrive_D32xx).
- SemiDrive E34xx: Added debug support (https://wiki.segger.com/SemiDrive_E34xx).
- SemiDrive E36xx: Added debug support (https://wiki.segger.com/SemiDrive_E36xx).
- ST STM32H747 device series: Added SPI flash programming support for CLK@PB2_nCS@PG6_D0@PD11_D1@PF9_D2@PF7_D3@PF6 pin configuration.
- ST STM32H747 device series: Added SPI flash programming support for CLK@PB2_nCS@PG6_D0A@PH2_D1A@PH3_D2A@PG9_D3A@PG14_D0B@PH2_D1B@PH3_D2B@PG9_D3B@PG14 pin configuration.
GDB Server
- Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
J-Flash
- Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
J-Flash Lite
- Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
J-Mem
- Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
J-Scope
- Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
RTT Viewer
- Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
SWO Viewer
- Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
Version V7.88d (2023-05-24)
Highlights:
Device Support
- NXP MCXN10: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXN10).
- NXP NCJ29D5: Added debug and flash programming support (https://wiki.segger.com/NXP_NCJ29D5).
- NXP S32K1422W/S32K144W: Added debug and flash programming support (https://wiki.segger.com/S32Kxxx)
- SemiDrive E31xx: Added debug and flash programming support (https://wiki.segger.com/SemiDrive_E31xx).
- SemiDrive E32xx: Added debug and flash programming support (https://wiki.segger.com/SemiDrive_E32xx).
- SemiDrive E33xx: Added debug and flash programming support (https://wiki.segger.com/SemiDrive_E33xx).
- TI CC2340: Added support for "attach to a running system" (https://wiki.segger.com/TI_CC2340).
Other changes:
DLL
- Nations N32G032x8 : Flashbank size wrong. Fixed.
- ST STM32WB: Option byte programming - Flasher stand alone mode: Programming did not work. Fixed.
- TI MSPM0G: Added device specific reset, as original reset would not reset peripherals.
- TI MSPM0L: Added device specific reset, as original reset would not reset peripherals.
Firmware
- Flasher ARM V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- Flasher ARM V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- Flasher Compact V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- Flasher Portable PLUS V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- Flasher PRO V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- Flasher PRO V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- Flasher PRO XL V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- Flasher PRO XL V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link EDU Mini V1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link EDU/BASE/PLUS V11: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link EDU/BASE/PLUS V12: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link PRO V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link PRO V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link PRO V6: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link ULTRA+ V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link ULTRA+ V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Link ULTRA+ V6: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Trace PRO V2 Cortex: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Trace PRO V2 CortexM: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Trace PRO V3 Cortex: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
- J-Trace PRO V3 CortexM: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
Version V7.88c (2023-05-16)
DLL
- CVA BlueWhale CVM011x: Allow programming the option byte area with the default flashloader.
- CVA BlueWhale CVM011x: Programming less data than a sector size could fail. Fixed.
- JLinkDevices.xml: Added core defines for Xtensa (JLINK_CORE_XTENSA_HIFI1, JLINK_CORE_XTENSA_HIFI3, JLINK_CORE_XTENSA_HIFI3Z, JLINK_CORE_XTENSA_HIFI4, JLINK_CORE_XTENSA_HIFI5 and JLINK_CORE_XTENSA_FUSION_F1).
- Nations N32xxx : Some Flashbank sizes had wrong sizes. Fixed.
- SFL / CMSIS flash loader: Sectorization was not determined correctly when absolute addresses were used in SectorInfo. Fixed.
- SFL / CMSIS flash loader: Sectorization was not determined correctly when relative addresses were used in SectorInfo and flash base address was smaller than one of the SectorInfo addresses. Fixed.
- TI CC2340: Added debug and flash programming support (https://wiki.segger.com/TI_CC2340).
Firmware
- Flasher ARM V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
- Flasher ARM V5: Cortex-M: Added support for dormant --> SWD switching sequence.
- Flasher Compact V5: Cortex-M: Added support for dormant --> SWD switching sequence.
- Flasher Portable PLUS V5: Cortex-M: Added support for dormant --> SWD switching sequence.
- Flasher PRO V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
- Flasher PRO V5: Cortex-M: Added support for dormant --> SWD switching sequence.
- Flasher PRO XL V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
- Flasher PRO XL V5: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link EDU Mini V1: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link EDU/BASE/PLUS V11: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Link EDU/BASE/PLUS V11: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link EDU/BASE/PLUS V12: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Link EDU/BASE/PLUS V12: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link PRO V5-1: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Link PRO V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link PRO V5: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Link PRO V5: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link PRO V6: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Link PRO V6: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link ULTRA+ V5-1: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Link ULTRA+ V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link ULTRA+ V5: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Link ULTRA+ V5: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link ULTRA+ V6: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Link ULTRA+ V6: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Link WiFi V1: CMSIS-DAP mode: If last DAP access of a DAP_Transfer and DAP_TransferBlock was a write, there was no final implicit read from RDBUF register triggered to make sure that write was finished. Fixed.
- J-Trace PRO V2 Cortex: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Trace PRO V2 CortexM: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Trace PRO V3 Cortex: Cortex-M: Added support for dormant --> SWD switching sequence.
- J-Trace PRO V3 CortexM: Cortex-M: Added support for dormant --> SWD switching sequence.
Version V7.88b (2023-05-10)
DLL
- Added support for command string "CORTEXM_SetNonCacheAwareDebugAHBAP" to workaround debug-related D-cache issues on some Cortex-M85 implementation.
- ISSI IS25LX512M, IS25WX512M: Under certain circumstances flash read could fail. Fixed.
- Nuvoton M2351: Flash programming could fail because of unpowered RAM used. Fixed.
- Nuvoton M2354: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_M2354).
- Programming of RISC-V devices could fail because auto detection of CPU clock frequency is not supported. Fixed.
- ST SR6G7: Added debug and flash programming support (https://wiki.segger.com/ST_SR6G7)
- ST STM32H5: Flash programming did not work with TrustZone enabled. Fixed.
Firmware
- J-Link OB Apollo4-CortexM: Added auto-enable of WinUSB (driverless) mode support on first boot of OB.
- J-Link OB Apollo4-CortexM: Added WinUSB (driverless) mode support.
- J-Link OB Apollo4-CortexM: Increased drive strength of TIF pins to overcome resistance issues on some eval boards with additional level shifters between OB and target MCU.
- J-Link OB RA4M2-CortexM: Added support for reboot command.
- J-Link OB RA4M2-Full: Added support for reboot command.
- J-Link OB RA4M2-Renesas: Added support for reboot command.
- J-Link OB RA4M2-RISCV: Added support for reboot command.
GDB Server
- Cadence Xtensa: Debugging via Xtensa Xplorer IDE and xt-gdb did not work properly and threw the warning "Target-supplied registers are not supported by the current architecture". Introduced in V7.84e. Fixed.
J-Flash SPI
- ISSI IS25LX512M, IS25WX512M: Under certain circumstances flash read could fail. Fixed.
Version V7.88a (2023-05-03)
DLL
- STM32H5: xSCR_PG bit was set after programming. Fixed.
Firmware
- LPC-Link2 on-board: Added auto-enable of WinUSB (driverless) mode on boot.
- LPC-Link2 on-board: Added support for Cadence / Tensilica Xtensa cores in NXP chips. (e.g. i.MX RT600 series devices)
- LPC-Link2 on-board: Added support for WinUSB (driverless) mode.
- LPC-Link2: Added auto-enable of WinUSB (driverless) mode on boot.
- LPC-Link2: Added support for WinUSB (driverless) mode.
- MCU-Link-OB: Added auto-enable of WinUSB (driverless) mode support on first boot.
- MCU-Link-OB: Added support for CAdence / Tensilica Xtensa cores in NXP chips. (e.g. i.MX RT600 series devices)
- MCU-Link-OB: Added WinUSB (driverless) mode support.
- MCU-Link: Added auto-enable of WinUSB (driverless) mode support on first boot.
- MCU-Link: Added WinUSB (driverless) mode support.
Version V7.88 (2023-04-27)
Highlights:
Trace
- Published out-of-the-box trace example for ST STM32H573I-DK board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Configurator
- Configuration dialog: Removed elements for configuring obsolete feature "Eco logic".
- Replaced "Unhide" dialog with "System settings" dialog.
DLL
- Broadcom BCM89107: Added external QSPI flash programming support (address 0x08200000).
- Broadcom BCM89107: Under special circumstances, flash programming > 16 MB could fail. Fixed.
- CVA BlueWhale CVM011x: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM011x).
- Cypress S6J32x devices series: Under certain circumstances connect did not work. Fixed.
- HPMicro HPM62 family: Added debug and flash programming support (https://wiki.segger.com/HPMicro_HPM62).
- Infineon TLE986x/TLE987x: Flash programming could fail if NMIs were enabled. Fixed.
- J-Link DLL could crash when flash configuration is wrong. Fixed.
- JLinkDevices XML: MaxSize attribute for flash loaders was not correctly handled if MaxSize was smaller than the size specified in the ELF/FLM file. Fixed.
- Microchip SAM4S: Added debug and flash programming support for ATSAM4SD16BB and ATSAM4SD32BB
- MindMotion MM32F5287: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F5).
- Renesas R9A02G020: Added debug and flash programming support.
- Renesas R9A06G150: Added debug and flash programming support.
- ST SR6P6: Core for DSPH was wrong. Fixed.
- ST SR6P6xx: Added flash programming support for CUT 1.0 devices/revisions.
- TI MSPM0G Rev. PG2 devices: Verify after MAIN programming could fail under special circumstances. Fixed.
- TI MSPM0L Rev. PG2 devices: Verify after MAIN programming could fail under special circumstances. Fixed.
Firmware
- Flasher ARM V5-1: Stand-alone mode: Projects that did not specify the (optional) Device.pex file caused programming to be aborted with error. Introduced in V7.86g. Fixed.
- Flasher ARM V5-1: Stand-alone: UFLASH: When using the new terminal command "#READ" (introduced in V7.86g), endless loops could happen, resulting in a lockup of the Flasher that required a power-cycle. Fixed.
- Flasher ARM V5: Stand-alone mode: Projects that did not specify the (optional) Device.pex file caused programming to be aborted with error. Introduced in V7.86g. Fixed.
- Flasher ARM V5: Stand-alone: UFLASH: When using the new terminal command "#READ" (introduced in V7.86g), endless loops could happen, resulting in a lockup of the Flasher that required a power-cycle. Fixed.
- Flasher Compact V5: Stand-alone mode: Projects that did not specify the (optional) Device.pex file caused programming to be aborted with error. Introduced in V7.86g. Fixed.
- Flasher Compact V5: Stand-alone: UFLASH: When using the new terminal command "#READ" (introduced in V7.86g), endless loops could happen, resulting in a lockup of the Flasher that required a power-cycle. Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Projects that did not specify the (optional) Device.pex file caused programming to be aborted with error. Introduced in V7.86g. Fixed.
- Flasher Portable PLUS V1: Stand-alone: UFLASH: When using the new terminal command "#READ" (introduced in V7.86g), endless loops could happen, resulting in a lockup of the Flasher that required a power-cycle. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Projects that did not specify the (optional) Device.pex file caused programming to be aborted with error. Introduced in V7.86g. Fixed.
- Flasher Portable PLUS V5: Stand-alone: UFLASH: When using the new terminal command "#READ" (introduced in V7.86g), endless loops could happen, resulting in a lockup of the Flasher that required a power-cycle. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Projects that did not specify the (optional) Device.pex file caused programming to be aborted with error. Introduced in V7.86g. Fixed.
- Flasher PRO V5-1: Stand-alone: UFLASH: When using the new terminal command "#READ" (introduced in V7.86g), endless loops could happen, resulting in a lockup of the Flasher that required a power-cycle. Fixed.
- Flasher PRO V5: Stand-alone mode: Projects that did not specify the (optional) Device.pex file caused programming to be aborted with error. Introduced in V7.86g. Fixed.
- Flasher PRO V5: Stand-alone: UFLASH: When using the new terminal command "#READ" (introduced in V7.86g), endless loops could happen, resulting in a lockup of the Flasher that required a power-cycle. Fixed.
J-Flash
- In some cases the sectorization in the Flash device info was displayed repetitive. Fixed.
- J-Flash did not keep sector selection when using a different loader than the default loader. Fixed.
J-Scope
- Exporting CSV data for symbols within a struct did not use the extended symbol name. Fixed.
Version V7.86h (2023-04-12)
DLL
- Alif Semiconductor AE3 series: Devices were no longer listed as supported / displayed in the device selection dialog. Introduced in V7.86g. Fixed.
- Alif Semiconductor AE5 series: Devices were no longer listed as supported / displayed in the device selection dialog. Introduced in V7.86g. Fixed.
Firmware
- Flasher Portable PLUS V1: Config of previous programming round was not invalidated properly when changing the image selection via the SEL button. This could lead to next programming cycle returning an error. Fixed.
- Flasher Portable PLUS V5: Config of previous programming round was not invalidated properly when changing the image selection via the SEL button. This could lead to next programming cycle returning an error. Fixed.
J-Flash
- Project settings -> MCU: Added hyperlink to SEGGER Wiki explaining "J-Link Work RAM": https://wiki.segger.com/UM08003_JFlash#J-Link_Work_RAM_settings .
- Project settings -> MCU: Renamed "Target RAM" to "J-Link Work RAM".
J-Scope
- Trigger settings were not properly set when project was loaded. Fixed.
Version V7.86g (2023-04-06)
DLL
- ARMv8-A/R (e.g. Cortex-R52): If 64-bit (or larger) CPU registers were written, under very special circumstances, a stack overflow could happen on the next Go() / core resume. Fixed.
- Cypress CYT4BF: Added flash programming support for supervisory flash.
- J-Link script files: Added support for handling missing return statements at the end of non-void functions as errors. (No firmware change)
- NXP LPC55S36: Extended Device Support for A1 revision.
- NXP MIMXRT1041xxx6B, MIMXRT1042xxx5B: Added debug & QSPI flash programming support.
- Programming could fail when ARMv8-M PSPLIM register was changed by application. Fixed.
- Renesas DA14592: Added QSPI flash programming support.
- RISC-V RV64: If 64-bit (or larger) CPU registers were written, under very special circumstances, a stack overflow could happen on the next Go() / core resume. Fixed.
- ST STM32H72x, STM32H73x: Added support for QSPI pin config CLK@PF10_nCS@PB6_D0@PC9_D1@PC10_D2@PE2_D3@PF6_D4@NA_D5@NA_D6@NA_D7@NA. For more information, see: https://wiki.segger.com/ST_STM32H7#Supported_pin_configurations
- ST STM32H72x, STM32H73x: Added support for QSPI pin config CLK@PF10_nCS@PG6_D0@PD11_D1@PD12_D2@PE2_D3@PD13_D4@NA_D5@NA_D6@NA_D7@NA. For more information, see: https://wiki.segger.com/ST_STM32H7#Supported_pin_configurations
- ST STM32H7Ax, STM32H7Bx: Added support for QSPI pin config CLK@PB2_nCS@PG6_D0@PF8_D1@PF9_D2@PF7_D3@PF6_D4@NA_D5@NA_D6@NA_D7@NA. For more information, see: https://wiki.segger.com/ST_STM32H7#Supported_pin_configurations
- ST STM32H7Ax, STM32H7Bx: Added support for QSPI pin config CLK@PF10_nCS@PB6_D0@PC9_D1@PC10_D2@PE2_D3@PF6_D4@NA_D5@NA_D6@NA_D7@NA. For more information, see: https://wiki.segger.com/ST_STM32H7#Supported_pin_configurations
- ST STM32H7Ax, STM32H7Bx: Set RAM base address used by J-Link to 0x24000000 (AXI SRAM).
- Trace: Added support for command string "TRACE_SetEnableStalling" (https://wiki.segger.com/J-Link_Command_Strings#TRACE_SetEnableStalling)
- Trace: ETMv4: Stalling was enabled by default, by accident, which could result in intrusive trace. Fixed.
- Under special circumstances RAMCode did not respond in time and programming flash failed. Fixed.
Firmware
- Flasher Compact V5: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
- Flasher Compact V5: Stand-alone: UFLASH: Added support for terminal command "#READ".
- Flasher Compact V5: Stand-alone: UFLASH: STM8: Under very special circumstances, some STM8 MCUs sent an ACK packet too early which could be missed by Flasher and result in a programming error being reported. Fixed.
- Flasher Portable PLUS V1: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
- Flasher Portable PLUS V5: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
- Flasher Portable PLUS V5: Stand-alone: UFLASH: Added support for terminal command "#READ".
- Flasher Portable PLUS V5: Stand-alone: UFLASH: STM8: Under very special circumstances, some STM8 MCUs sent an ACK packet too early which could be missed by Flasher and result in a programming error being reported. Fixed.
- Flasher PRO V5-1: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
- Flasher PRO V5-1: Stand-alone: UFLASH: Added support for terminal command "#READ".
- Flasher PRO V5-1: Stand-alone: UFLASH: STM8: Under very special circumstances, some STM8 MCUs sent an ACK packet too early which could be missed by Flasher and result in a programming error being reported. Fixed.
- Flasher PRO V5: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
- Flasher PRO V5: Stand-alone: UFLASH: Added support for terminal command "#READ".
- Flasher PRO V5: Stand-alone: UFLASH: STM8: Under very special circumstances, some STM8 MCUs sent an ACK packet too early which could be missed by Flasher and result in a programming error being reported. Fixed.
- Flasher PRO XL V5-1: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
- Flasher PRO XL V5-1: Stand-alone: UFLASH: Added support for terminal command "#READ".
- Flasher PRO XL V5-1: Stand-alone: UFLASH: STM8: Under very special circumstances, some STM8 MCUs sent an ACK packet too early which could be missed by Flasher and result in a programming error being reported. Fixed.
- Flasher PRO XL V5: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
- Flasher PRO XL V5: Stand-alone: UFLASH: Added support for terminal command "#READ".
- Flasher PRO XL V5: Stand-alone: UFLASH: STM8: Under very special circumstances, some STM8 MCUs sent an ACK packet too early which could be missed by Flasher and result in a programming error being reported. Fixed.
GDB Server
- GDB Server could crash if GDB Server log file was enabled and a packet exceeding max. packet size was received. Fixed.
- Log file: WriteLine() was not thread-safe so that line outputs from different threads in GDB Server could lead to interleaved and messed up log output.
J-Flash SPI
- Enable the temporary VTref before enabling power supply via J-Link as VTref is measured after enabling the power supply.
J-Scope
- ELF file parsing could get stuck with certain ELF files. Fixed.
- Symbols could get matched up incorrectly when loading a project causing duplicate entries. Fixed.
RTT
- SEGGER_RTT_Syscalls_KEIL.c: Updated for usage with ARMCC V6.19.
- Slightly reworked INIT() macro: It is now called as a single statement and does check for "!= 'S'" instead of "== '\0'".
Version V7.86f (2023-03-29)
Commander
- Added support for Greenhills ELF files.
- Reading / writing memory to the topmost address in the 32 bit region (0xFFFFFFFF) resulted in unexpected behavior. Fixed.
DLL
- Added new J-Link Command String "SetVTrefTmp" (https://wiki.segger.com/J-Link_Command_Strings#SetVTrefTmp).
- Added support for the Renesas RX13T core.
- CAST BA51 (RISC-V): Added CAST BA51 as a selectable device.
- CAST BA51 (RISC-V): Added debug support for CAST BA51 core. https://wiki.segger.com/CAST_BA51
- Geehy APM32A091: Added debug and flash programming support for internal flash and option bytes (https://wiki.segger.com/Geehy_APM32A0xx).
- Geehy APM32A103: Added debug and flash programming support for internal flash and option bytes (https://wiki.segger.com/Geehy_APM32A1xx).
- Geehy APM32A407: Added debug and flash programming support.
- Geehy APM32F105 / APM32F107: Added debug and flash programming support for internal flash and option bytes.
- Geehy APM32F415, APM32F417: Added debug and flash programming support.
- Geehy APM32S103: Added debug and flash programming support for internal flash and option bytes.
- Microchip ATSAME5x: Native unsecure on connect did not work correctly (introduced V7.82e). Fixed.
- MindMotion MM32A0144: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32A0).
- MindMotion MM32F0040: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F0).
- MindMotion MM32F0160: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F0).
- MindMotion MM32G0141: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G0).
- MindMotion MM32G0163: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G0).
- MindMotion MM32L0020: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32L0).
- MindMotion MM32L0131: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32L0).
- MindMotion MM32L0136: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32L0).
- MindMotion MM32SPIN0280: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32SPIN).
- NXP i.MXRT1021 device series: Added support for A1 silicon devices.
- Renesas R5F513T3 (RX13T): Added debug & flash programming support.
- Renesas R5F513T5 (RX13T): Added debug & flash programming support.
- Renesas RX: In case of firmware does not support the current core architecture, multiple connects were issued. Fixed.
- Renesas RZ/T2L: Added debug and (QSPI) flash programming support (https://wiki.segger.com/Renesas_RZ/T2L).
- ST STM32WB - FUS (WS upgrade): Reworked concept, to make stack upgrades via J-Flash and Flasher stand-alone programming possible. See: https://wiki.segger.com/ST_STM32WB
- ST STM32WB: Merged "<DeviceName>" and "<DeviceName> (allow opt. bytes)"
Firmware
- Flasher ARM V5-1: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher ARM V5-1: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- Flasher ARM V5: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher ARM V5: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- Flasher Compact V5: Added support for the Renesas RX13T core.
- Flasher Compact V5: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher Compact V5: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- Flasher Portable PLUS V1: Added support for the Renesas RX13T core.
- Flasher Portable PLUS V1: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- Flasher Portable PLUS V5: Added support for the Renesas RX13T core.
- Flasher Portable PLUS V5: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- Flasher PRO V5-1: Added support for the Renesas RX13T core.
- Flasher PRO V5-1: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher PRO V5-1: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- Flasher PRO V5: Added support for the Renesas RX13T core.
- Flasher PRO V5: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher PRO V5: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- Flasher PRO XL V5-1: Added support for the Renesas RX13T core.
- Flasher PRO XL V5-1: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- Flasher PRO XL V5: Added support for the Renesas RX13T core.
- Flasher PRO XL V5: Stand-alone mode: Global variables "IsHalted" was not reset between 2 programming cycles which could lead to issues on some targets if Reset() was not the first operation performed by Flasher (e.g. NXP LPC2378). Fixed.
- Flasher PRO XL V5: Stand-alone mode: Programming of ARM7/9 target devices, that need CPU speed for flash programming, failed. Introduced with V7.84f (when adding RISC-V support for stand-alone mode). Fixed.
- J-Link EDU Mini V1: Added support for the Renesas RX13T core.
- J-Link EDU/BASE/PLUS V11: Added support for the Renesas RX13T core.
- J-Link EDU/BASE/PLUS V12: Added support for the Renesas RX13T core.
- J-Link PRO V5-1: Added support for the Renesas RX13T core.
- J-Link PRO V5: Added support for the Renesas RX13T core.
- J-Link PRO V6: Added support for the Renesas RX13T core.
- J-Link ULTRA+ V5-1: Added support for the Renesas RX13T core.
- J-Link ULTRA+ V5: Added support for the Renesas RX13T core.
- J-Link ULTRA+ V6: Added support for the Renesas RX13T core.
- J-Link WiFi V1: Added support for the Renesas RX13T core.
GDB Server
- RTOSPlugin for FreeRTOS did not report correct task registers. Fixed.
- Semihosting: Some unsupported commands were handled as errors instead of being handled as "unsupported". Fixed.
- Semihosting: SYS_FLEN was not handling stdin handle correctly. Fixed.
- Semihosting: SYS_ISERROR was not marked as unsupported command, even though it is. Fixed.
- Semihosting: SYS_ISTTY did not return 1 for stdin. Fixed.
- Semihosting: SYS_WRITE0 failed when an empty string was passed. Fixed.
J-Flash
- Added support for Greenhills ELF files.
- The "Enable VTref" production project setting could be enabled but was not supported in J-Flash mode (stand-alone mode only). Fixed.
- Under some circumstances, J-Flash would fail to enable the J-Flash log file and would show a message box "Could not open file [...]". Fixed.
J-Flash SPI
- The "Enable VTref" production project setting could be enabled but was not supported in host mode (stand-alone mode only). Fixed.
- Under some circumstances, J-Flash SPI would fail to enable the J-Flash SPI log file and would show a message box "Could not open file [...]". Fixed.
J-Flash SPI CL
- The "Enable VTref" production project setting could be enabled but was not supported in host mode (stand-alone mode only). Fixed.
J-Scope
- Added support for class keyword.
- Arrays of structs did no longer display their names within the table widget. Introduct with V7.86d. Fixed.
- J-Scope will now reparse ELF file on project load.
Version V7.86e (2023-03-22)
Control Panel
- Having the "CPU Regs" tab open during debug could cause instabilities if debugger accessed J-Link in parallel (e.g. doing IsHalted checks or similar). Internal mutex was not locked correctly. Fixed.
DLL
- Added support for Macronix MX25L4006E SPI flash to SPIFI-Lib.
- Infineon XMC7200: Added debug and flash programming support.
- J-Link script files: Added constant "CORESIGHT_AXI_AP". (See https://wiki.segger.com/J-Link_script_files#Constants_for_.22JLINK_CORESIGHT_xxx.22_functions)
- NucleiSys N900 RISC-V TAPs with TAPId == 0x10900A6D were not properly detected as RISC-V TAPs. Fixed.
- Nuvoton M463/M467: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_M46x).
- Nuvoton NUC029 Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
- Nuvoton NUC029FAE: Flash programming could fail because of wrong CPU clock settings. Fixed.
- Nuvoton NUC100/120 Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
- Nuvoton NUC1262 series: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_NUC1262x).
- NXP iMXRT117x: FlexSPI Flash programming did not work. Introduced with V7.86. Fixed.
- Renesas DA1459x device series: Changed eFlash base address from 0x00A00000 to 0x31000000.
- Texas Instruments TMS570LS device series: Added programming support for flash OTP and EEPROM OTP.
Firmware
- J-Link OB RA4M2-CortexM: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link OB RA4M2-CortexM: cJTAG: Under special circumstances, the TMSC line could become floating which could make target device to accidentally detect reset escape sequences. Fixed.
- J-Link OB RA4M2-Full: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link OB RA4M2-Full: cJTAG: Under special circumstances, the TMSC line could become floating which could make target device to accidentally detect reset escape sequences. Fixed.
- J-Link OB RA4M2-RISCV: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link OB RA4M2-RISCV: cJTAG: Under special circumstances, the TMSC line could become floating which could make target device to accidentally detect reset escape sequences. Fixed.
J-Flash
- Menubar selections "Production programming", "Program", "Program & Verify" and "Verify" are no longer greyed out when no data file is opened and instead throw a warning in such a case.
- Project settings dialog, flash page: Removed "Organization" label and drop down menu for non-CFI-NOR flashes.
- Stand-alone-mode programming did not work for the NXP MKL81/MKL82 series devices. Fixed.
J-Flash SPI
- Added support for Macronix SPI flash MX25L4006E.
Version V7.86d (2023-03-15)
DLL
- Added printing of J-Link script file function execution time (e.g. execution time of InitTarget()) to J-Link log output.
- Cortex-A35 based devices were detected as Cortex-A53. Fixed.
- Infineon CY8C6xx, XMC7xxx devices: Chip erase caused J-Link to try to erase SMIF flash bank even if it is not present. Fixed.
- Infineon TLE98xx devices series: Flash programming did not work when NMINVM bit was set. Fixed.
- J-Link script files: Added support for adjacent string literals.
- J-Link script files: If a string literal contained an unescaped newline character (\n), no error was thrown. Fixed.
- Nuvoton M051 Base Series: Data flash programming support added.
- Nuvoton M051 Base Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
- Nuvoton M0518 Series: Data flash programming support added.
- Nuvoton M0518 Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
- Nuvoton M0519 Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
- Nuvoton M0519xDx: Data flash programming support added.
- Renesas RZ/T2L: BSC pins were erroneously initialized on connect. Fixed.
- SiLabs EFM8: Added support for EFM8BB50 series devices: EFM8BB50F4G, EFM8BB50F4I, EFM8BB50F8G, EFM8BB50F8I, EFM8BB50F16G, EFM8BB50F16I.
- ST STM32C0: Add device specific connect and native unlock functionality.
- TI MSPM0G Rev. PG2 devices: NONMAIN programming did not work. Fixed.
- TI MSPM0L Rev. PG2 devices: NONMAIN programming did not work. Fixed.
- User was not informed in case J-Link script file function "ResetTarget()" failed. Fixed.
J-Flash
- Project settings dialog, flash tab: SFL based flash banks with dynamic sector layout were erroneously displayed as having static sector layout. Fixed.
J-Scope
- Cursor time and timestamps were not displayed correctly when graph window size did not align with grid size. Fixed.
- J-Scope RTT projects did not have several actions like "Import raw" or "Start sampling" available on startup. Fixed.
- J-Scope RTT projects did not show previously active symbols on startup. Fixed.
- Member variables of structs or unions now show their parent struct variable name within the symbol table, graph tooltip and symbol trigger selection.
- Trigger symbol selection combobox was too small for many symbol names. Fixed.
- Under certain circumstances, J-Scope could crash. Fixed.
STM32 Utility
- Added ST STM32C0.
Version V7.86c (2023-03-09)
Commander
- Added comand "Uptime" (see: https://wiki.segger.com/J-Link_Commander#Uptime).
- Added optional timeout parameter to "Reboot" command (see: https://wiki.segger.com/J-Link_Commander#Reboot).
Control Panel
- General tab: Added J-Link uptime.
- Settings tab: Combobox entry selection used to flicker when hovering over them. Fixed.
- Settings tab: Ram download => Verify combobox was filling infinitely with the same two entries. Fixed.
DLL
- Added OTP memory bank to STM32F42x series devices.
- ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): Added support for RTT and HSS via MEM-AP (AHB-AP, AXI-AP).
- Atmosic ATM333x devices: Added flash programming support for revision B0 silicon.
- Hilscher NetX90: Added SQI(QSPI) flash programming support.
- JLinkDevicesXML: FlashBankInfo in old format (without LoaderInfo) and with spaces in flash bank name attribute was not handled correctly by J-Link DLL. Fixed.
- Microchip PIC32CM LS/LE devices: Added debug and flash programming support(https://wiki.segger.com/Microchip_PIC32CM_Lx).
- NXP K32W14x devices: Connecting to the devices while no valid target application was on the device would fail. Fixed.
- NXP K32W14x devices: Device reset did not work. Fixed.
- NXP LPC55xx devices: SWO would not work correctly when SWO was initialized from within the target application. Fixed.
- NXP LPC55xx devices: The TPIU was explicitly clocked after Connect/Reset even when SWO/Trace were not being used. This will only happen now if SWO tracing is explicitly active. For ETM tracing the TPIU clock init now must be done by the trace init via J-Link Script. For further information refer to: https://wiki.segger.com/NXP_LPC55xx
- NXP S32K311: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx)
- Realtek RTL872xDx devices: Added debug and flash programming support(https://wiki.segger.com/Realtek_Ameba_D).
- Renesas DA1459x: Added debug and flash programming support for eFlash.
- Renesas RZ/T2M: Added support for RTT and HSS via AXI-AP.
- Setting the memory window to 64-bit item view could cause an error message saying "The connected J-Link does not support the requested memory access". Introduced in V7.86b. Fixed.
- ST STM32H5 device series: Added debug and flash programming support for internal and QSPI flash. For more information: https://wiki.segger.com/ST_STM32H5
Firmware
- ARMv8-A/R firmware module V9 (e.g. Cortex-A53, Cortex-R52): Added support for RTT and HSS via MEM-AP (AHB-AP, AXI-AP) in firmware. (If model supports RTT and HSS in general)
- Flasher ARM V5-1: Implemented ARMv8-A/R firmware module V9.
- Flasher ARM V5: Implemented ARMv8-A/R firmware module V9.
- Flasher Compact V5: Implemented ARMv8-A/R firmware module V9.
- Flasher Portable PLUS V1: Implemented ARMv8-A/R firmware module V9.
- Flasher Portable PLUS V5: Implemented ARMv8-A/R firmware module V9.
- Flasher PRO V5-1: Implemented ARMv8-A/R firmware module V9.
- Flasher PRO V5: Implemented ARMv8-A/R firmware module V9.
- Flasher PRO XL V5-1: Implemented ARMv8-A/R firmware module V9.
- Flasher PRO XL V5: Implemented ARMv8-A/R firmware module V9.
- J-Link EDU Mini V1: Implemented ARMv8-A/R firmware module V9.
- J-Link EDU Mini V1: Implemented Renesas RX firmware module V2.
- J-Link EDU/BASE/PLUS V11: Implemented ARMv8-A/R firmware module V9.
- J-Link EDU/BASE/PLUS V11: Implemented Renesas RX firmware module V2.
- J-Link EDU/BASE/PLUS V12: Implemented ARMv8-A/R firmware module V9.
- J-Link EDU/BASE/PLUS V12: Implemented Renesas RX firmware module V2.
- J-Link Lite-S124: Implemented ARMv8-A/R firmware module V9.
- J-Link OB-S124: Implemented ARMv8-A/R firmware module V9.
- J-Link PRO V5-1: Implemented ARMv8-A/R firmware module V9.
- J-Link PRO V5-1: Implemented Renesas RX firmware module V2.
- J-Link PRO V5: Implemented ARMv8-A/R firmware module V9.
- J-Link PRO V5: Implemented Renesas RX firmware module V2.
- J-Link PRO V6: Implemented ARMv8-A/R firmware module V9.
- J-Link PRO V6: Implemented Renesas RX firmware module V2.
- J-Link ULTRA+ V5-1: Implemented ARMv8-A/R firmware module V9.
- J-Link ULTRA+ V5-1: Implemented Renesas RX firmware module V2.
- J-Link ULTRA+ V5: Implemented ARMv8-A/R firmware module V9.
- J-Link ULTRA+ V5: Implemented Renesas RX firmware module V2.
- J-Link ULTRA+ V6: Implemented ARMv8-A/R firmware module V9.
- J-Link ULTRA+ V6: Implemented Renesas RX firmware module V2.
- J-Link WiFi V1: Implemented ARMv8-A/R firmware module V9.
- J-Trace PRO V2 Cortex: Implemented ARMv8-A/R firmware module V9.
- J-Trace PRO V3 Cortex: Implemented ARMv8-A/R firmware module V9.
- J-Trace PRO V3 Cortex: Implemented Renesas RX firmware module V2.
- Renesas RX firmware module V2: RTT: RTT did stop working after app. 24 days of J-Link uptime. Fixed.
GDB Server
- Added auto-remove of pending breakpoints on GDB connection close, to make sure that there are no BP leftovers from a previous session in case GDB client exited abnormally (e.g. crashed).
- ARMv7-A/R (e.g. Cortex R5, Cortex-A9, ...): R8-R12 of current mode were displayed incorrectly. Introduced in V7.84e. Fixed.
- ARMv8-A/R AArch32 (e.g. Cortex R52): R8-R12 of current mode were displayed incorrectly. Introduced in V7.84e. Fixed.
- FreeRTOS plugin: Threads that are created before the scheduler is running are now marked as "Ready" to prevent confusion.
- Semihosting: Implemented functionality for SEGGER command extension SYS_IS_CONNECTED (0x00).
- Semihosting: SYS_ERRNO often did not return an error code in case an error occurred. Fixed.
- Semihosting: Write operations now also accept handle 2 (stderr), which is routed to the Semihosting TELNET-channel.
Version V7.86b (2023-03-01)
Commander
- Added command "w8" to write 64-bit items. (https://wiki.segger.com/J-Link_Commander#Write8)
DLL
- Added J-Link script file API function JLINK_MEM_FillEx().
- ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): Added support for zoned memory access (CPU, AXI-AP, ...).
- Linux: JLinkDevices folder: By accident, also directories above $HOME/.config/SEGGER/JLinkDevices were searched. Fixed. (https://wiki.segger.com/J-Link_Device_Support_Kit#JLinkDevices_folder)
- NXP S32K3xx: Improved device specific connect to print more detailed information regarding the HSM firmware.
- NXP S32K3xx: Under special circumstances, flash programming (erase / program) did not work. Fixed.
- Qorvo GP570xxx: Increased the delay after releasing the reset pin as part of the device specific connect sequence.
- Qorvo QM3572x device series: Under certain circumstances flash programming could fail. Fixed.
- Qorvo QPG5071G / QPG5072: Increased the delay after releasing the reset pin as part of the device specific connect sequence.
- Qorvo QPG6095x / QPG6100x / QPG6105: Increased the delay after releasing the reset pin as part of the device specific connect sequence.
- Renesas DA1470x: Added debug and QSPI flash programming support.
- ST SR6P6/SR6P7: Flashing of UTEST area failed. Introduced in V7.86a. Fixed.
- ST SR6P6/SR6P7: Updated naming of flash banks.
Firmware
- ARMv8-A/R firmware module V8 (e.g. Cortex-A53, Cortex-R52): Added support for zoned memory access (CPU, AXI-AP, ...).
- Flasher ARM V5-1: Implemented ARMv8-A/R firmware module V8.
- Flasher ARM V5-1: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- Flasher ARM V5: Implemented ARMv8-A/R firmware module V8.
- Flasher ARM V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- Flasher Compact V5: Implemented ARMv8-A/R firmware module V8.
- Flasher Compact V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- Flasher Portable PLUS V1: Implemented ARMv8-A/R firmware module V8.
- Flasher Portable PLUS V1: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- Flasher Portable PLUS V5: Implemented ARMv8-A/R firmware module V8.
- Flasher Portable PLUS V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- Flasher PRO V5-1: Implemented ARMv8-A/R firmware module V8.
- Flasher PRO V5-1: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- Flasher PRO V5: Implemented ARMv8-A/R firmware module V8.
- Flasher PRO V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- Flasher PRO XL V5-1: Implemented ARMv8-A/R firmware module V8.
- Flasher PRO XL V5-1: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- Flasher PRO XL V5: Implemented ARMv8-A/R firmware module V8.
- Flasher PRO XL V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
- J-Link EDU Mini V1: Implemented ARMv8-A/R firmware module V8.
- J-Link EDU/BASE/PLUS V11: Implemented ARMv8-A/R firmware module V8.
- J-Link EDU/BASE/PLUS V12: Implemented ARMv8-A/R firmware module V8.
- J-Link Lite-S124: Implemented ARMv8-A/R firmware module V8.
- J-Link OB-S124: Implemented ARMv8-A/R firmware module V8.
- J-Link PRO V5-1: Implemented ARMv8-A/R firmware module V8.
- J-Link PRO V5: Implemented ARMv8-A/R firmware module V8.
- J-Link PRO V6: Implemented ARMv8-A/R firmware module V8.
- J-Link ULTRA+ V5-1: Implemented ARMv8-A/R firmware module V8.
- J-Link ULTRA+ V5: Implemented ARMv8-A/R firmware module V8.
- J-Link ULTRA+ V6: Implemented ARMv8-A/R firmware module V8.
- J-Link WiFi V1: Implemented ARMv8-A/R firmware module V8.
- J-Trace PRO V2 Cortex: Implemented ARMv8-A/R firmware module V8.
- J-Trace PRO V3 Cortex: Implemented ARMv8-A/R firmware module V8.
GDB Server
- GDB Server was closed with error message if IPv6 was disabled on the host system. Fixed.
J-Flash
- Adapted project settings dialog to be resizeable.
- Added sectorization information to project settings dialog flash page.
- In the command line no space was allowed between options and parameters. Both variants are now possible.
J-Flash SPI
- In the command line no space was allowed between options and parameters. Both variants are now possible.
Version V7.86a (2023-02-22)
Commander
- When listing available memory zones for a connected target, the zone name was not surrounded quotation marks. Fixed.
DLL
- Added "Cortex-A35" as generic device name to the device selection dialog.
- Analog ADuCM342: Added debug & flash programming support.
- Cortex-A35: Auto detection did not work. Fixed.
- Cortex-M ARMv8-M (e.g. Cortex-M33): Cache info was not output even if core implemented CPU cache. Fixed.
- Cortex-M7: D-cache was not properly handled on debugger memory accesses (Could lead to local / global variables to show old values). Fixed.
- Cypress CYT3, CYT4: DCache was not correctly invalidated. Fixed.
- Infineon(Fujitsu) CY9BF121J(MB9BF121J): Internal flashbank size too big. Fixed.
- J-Link script files: Added output of execution time in [ms] on a successful call to a script file function (e.g. InitTarget()).
- NXP Kinetis family: User JTAG chain selection was ignored for some devices. Fixed.
- NXP Kinetis Series, iMXRT Series: DCache was not correctly invalidated. Fixed.
- ST STM32H7 Series, STM32F7 Series: DCache was not correctly invalidated. Fixed.
- ST STM32L4: Added multiple loader support for single bank/dual bank configuration.
- ST STM32L4R: Added multiple loader support for single bank/dual bank configuration.
- TI MSPM0G: Added NONMAIN flash programming support for PG2 revision.
- TI MSPM0L: Added NONMAIN flash programming support for PG2 revision.
Firmware
- Flasher ARM V5-1: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher ARM V5-1: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher ARM V5-1: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
- Flasher ARM V5: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher ARM V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher ARM V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
- Flasher Compact V5: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher Compact V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher Compact V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
- Flasher Portable PLUS V1: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher Portable PLUS V5: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher Portable PLUS V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
- Flasher PRO V5-1: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher PRO V5-1: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher PRO V5-1: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
- Flasher PRO V5: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher PRO V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher PRO V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
- Flasher PRO XL V5-1: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher PRO XL V5-1: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
- Flasher PRO XL V5: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- Flasher PRO XL V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
- Flasher PRO XL V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
- J-Link EDU Mini V1: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link EDU/BASE/PLUS V11: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link EDU/BASE/PLUS V12: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link OB RA4M2-CortexM: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link OB RA4M2-Full: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link OB RA4M2-Renesas: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link OB S124: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link PRO V5-1: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link PRO V5: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link PRO V6: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link ULTRA+ V5-1: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link ULTRA+ V5: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link ULTRA+ V6: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Link WiFi V1: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Trace PRO V2 Cortex: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Trace PRO V2 CortexM: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Trace PRO V3 Cortex: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
- J-Trace PRO V3 CortexM: Cortex-M ARMv8-M (e.g. Cortex-M33, Cortex-M55, Cortex-M85): Firmware module 1: D-cache was not properly handled on debugger AHB-AP memory accesses (Could lead to local / global variables to show old values). Fixed.
GDB Server
- RISC-V: Single precision FPU registers were reported even if double precision FPU was implemented in device. Could cause some GDB clients to refuse the connection if calling convention "ilp32d" was selected during compile time of ELF file. Fixed.
- Semihosting: SYS_WRITE0 call was not working correctly and could potentially cause a GDB Server crash. Introduced in V7.68b. Fixed.
- Semihosting: SYS_WRITE: Always returned error. Introduced in V7.68b. Fixed.
- Semihosting: SYS_WRITEC: Always returned error. Introduced in V7.68b. Fixed.
J-Flash
- Operation "File -> Show files on Flasher" could cause J-Flash to crash if there were more than 16 files on the Flasher. Fixed.
J-Flash SPI
- Added support for SPI EEPROM.
- EEPROM: Added support for Microchip AT25320, AT25640, AT25128, AT25256, AT25512.
Version V7.86 (2023-02-15)
Control Panel
- Improved sectorization output in <Flash> tab.
DLL
- Added support for the following Adesto SPI flashes AT25EU0011A, AT25EU0021A, AT25EU0021A to SPIFI-Lib.
- Added support for the following Micron SPI flashes MT35XL01GCBA, MT35XL02GCBA to SPIFI-Lib.
- Analog Devices ADuCM430 series: Added debug and flash programming support (https://wiki.segger.com/Analog_ADuCM430).
- Nations N32G03x: Added debug and flash programming support (https://wiki.segger.com/Nations_N32G03x).
- Nations N32G4xx: Added debug and flash programming support (https://wiki.segger.com/Nations_N32G4xx).
- Nations N32L4xx: Added debug and flash programming support (https://wiki.segger.com/Nations_N32L4xx).
- Nations N32WB4xx: Added debug and flash programming support (https://wiki.segger.com/Nations_N32WB4xx).
- NXP iMXRT117x: Debug connection would fail when debugging both Cortex-M4 and Cortex-M7 cores and performing a reset via Cortex-M7. Fixed.
- NXP LPC55Sxx: Erase function mistakenly erased one more sector than desired. Fixed.
- NXP LPC55Sxx: Reset did not check secure flash for valid boot image, only non-secure flash. Fixed.
- Renesas RA4E2: Added debug and flash programming support (https://wiki.segger.com/Renesas_RA4E2).
- Renesas RA6E2: Added debug and flash programming support (https://wiki.segger.com/Renesas_RA6E2).
- Renesas RX66N and RX72N: The DLL erroneously detected / reported a core mismatch ("Identified core does not match configuration"). Fixed.
- Renesas RZT2: Added flash Parallel CFI NOR flash support for bank @0x70000000.
- S32K3xx: When HSE is installed and used erasing and programming could fail. Fixed.
- SFL XML: Added support for attribute "Sectorization" in <LoaderInfo> tag.
- SFL: Added possibility to override sectorization information so that info provided by ELF file is ignored. (Allows using the same loader for multiple devices that only differ in flash size / sectorization)
- ST SR6P6: Added debug and flash programming support (https://wiki.segger.com/ST_SR6P6).
- ST SR6P7G7: Erase did not triger writing 0xFFs to flash. Fixed.
- ST SR6P7G7: Wrong CodeID displayed. Fixed.
- ST STM32MP13: Added debug support.
- Syntacore SCR (RISC-V): Added debug support for SCR4 (RV32+RV64), SCR5 (RV32+RV64), SCR6, SCR7.
- Syntacore SCR (RISC-V): Added JTAG TAP IDCODEs for SCR3, SCR4, SCR5, SCR6, SCR7 to the list of known TAP Ids.
- TLE98xx: Ram check failed during erase or program. Fixed.
- Trace: Under certain circumstances conditional jumps with RISC-V Nexus Trace might be counted incorrectly. Fixed.
GDB Server
- Added support for "-version" command line option. https://wiki.segger.com/J-Link_GDB_Server#-version
J-Flash
- New project dialog: Depending on the display scaling, the "Flash banks" table would be smaller than it should. Fixed.
- New project dialog: Dialog can now be resized by the user.
- New project dialog: Moved "Flash banks" table below "Target interface" and "Speed" group boxes.
- Removed the option to program external parallel (CFI compliant) NOR flashes without the usage of RAM (https://wiki.segger.com/CFI_Flash#J-Flash).
- SFL: Added possibility to override sectorization information so that info provided by ELF file is ignored. (Allows using the same loader for multiple devices that only differ in flash size / sectorization)
J-Flash SPI
- Added support for the following Adesto SPI flashes: AT25EU0011A, AT25EU0021A, AT25EU0021A.
- Added support for the following Micron SPI flashes: MT35XL01GCBA, MT35XL02GCBA.
Version V7.84f (2023-02-07)
DLL
- ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- ST SR5E1: Added debug support for second core.
Firmware
- Flasher ARM V5-1: ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- Flasher ARM V5-1: Stand-alone mode: Added support for RISC-V based MCUs.
- Flasher ARM V5-1: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher ARM V5-1: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher ARM V5-1: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
- Flasher ARM V5: ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- Flasher ARM V5: Stand-alone mode: Added support for RISC-V based MCUs.
- Flasher ARM V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher ARM V5: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher ARM V5: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
- Flasher Compact V5: ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- Flasher Compact V5: Stand-alone mode: Added support for RISC-V based MCUs.
- Flasher Compact V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher Compact V5: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher Compact V5: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher Portable PLUS V1: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
- Flasher Portable PLUS V5: ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Added support for RISC-V based MCUs.
- Flasher Portable PLUS V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher Portable PLUS V5: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
- Flasher PRO V5-1: ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Added support for RISC-V based MCUs.
- Flasher PRO V5-1: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher PRO V5-1: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher PRO V5-1: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
- Flasher PRO V5: ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- Flasher PRO V5: Stand-alone mode: Added support for RISC-V based MCUs.
- Flasher PRO V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher PRO V5: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher PRO V5: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
- Flasher PRO XL V5-1: ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Added support for RISC-V based MCUs.
- Flasher PRO XL V5-1: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher PRO XL V5-1: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher PRO XL V5-1: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
- Flasher PRO XL V5: ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Added support for RISC-V based MCUs.
- Flasher PRO XL V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
- Flasher PRO XL V5: Stand-alone mode: If flash algo reported to not support "check blank" operations, this was not honored during "skip sector erase if blank" and "skip programming chunk if blank data" operations, which could lead to problems during flash programming. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Script file functions InitTarget() and ConfigTargetSettings() were executed in wrong order (swapped in comparison to PC driven mode). Fixed.
J-Flash
- ESWIN ECR2560: If performance operations "Skip erase sector if blank" and "Skip blank data on program" were enabled, under very special circumstances, it could happen that verify errors occurred. Fixed.
- J-Flash did not display more than 8 internal flash banks. Fixed.
- Saving flasher cfg file to disk: When the file contained a '.' and a "PEX" file had to be created for the target device, the procedure would fail. Fixed.
Version V7.84e (2023-02-01)
DLL
- Maxim MAX32570: QSPI flash programming did not restore device to the same state as before flash operation. Fixed.
- NordicSemi nRF53: When programming the UICR area, the software reported an verification error. Fixed.
- NXP MWCT2S: Added debug and flash programming support.
- NXP S32K322 / S32K324: Added debug support for the secondary Cortex-M7 core (https://wiki.segger.com/NXP_S32K3xx#Multi-Core_Support).
- NXP S32K3xx: Added RAM initialization for the SRAM0 region (https://wiki.segger.com/NXP_S32K3xx#RAM).
Firmware
- Flasher Compact V5: Stand-alone mode: Some target interface pins were still driven after programming was complete. Fixed.
- Flasher Portable PLUS V5: Some target interface pins were still driven after programming was complete. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: Some flash algos like NordicSemi nRF91, NXP LPC55xx and ST STM32G0 were not available in stand-alone mode. Fixed.
- J-Link EDU Mini V1: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link EDU/BASE/PLUS V10: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link EDU/BASE/PLUS V11: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link EDU/BASE/PLUS V12: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link OB RA4M2-CortexM: VCOM: Added hardware flow control support option.
- J-Link OB RA4M2-Full: VCOM: Added hardware flow control support option.
- J-Link OB RA4M2-RISCV: VCOM: Added hardware flow control support option.
- J-Link PRO V5-1: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link PRO V5: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link PRO V6: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link ULTRA+ V5-1: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link ULTRA+ V5: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link ULTRA+ V6: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Link WiFi V1: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Trace PRO V2 Cortex: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Trace PRO V2 CortexM: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Trace PRO V3 Cortex: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Trace PRO V3 CortexM: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
- J-Trace PRO V3 RISC-V: High speed sampling (HSS): Selecting sampling frequencies of < 10 Hz (down to 1 Hz) resulted in an error being thrown by J-Link. Fixed.
GDB Server
- ARMv8-A/R: AArch32 (e.g. Cortex-R52): Added support for floating point registers fpscr, fpexc, fpsid, mvfr0-2, s0-s31, d0-d31.
- ARMv8-A/R: Added auto-detection of core execution state (AArch64 / AArch32) and register set selection on connect.
- Cortex-M (ARMv8-M e.g. Cortex-M23/M33): Register set passed to GDB always included security extension registers even if the core did not implement them. Caused problems during stack unwinding since GDB13. Fixed.
- GDB Server exited and did not wait for a new connection after connection was closed. Fixed.
- Semihosting: SYS_WRITE/printf: When printing lines it could happen that the last 5 characters were printed twice. Introduced in V7.68a. Fixed.
J-Flash
- New project dialog: Added checkbox to enable/ disable flash banks at project creation.
- New project dialog: After selecting a target device, external flash banks that are not always present (e.g. ST STM32F412CE - QSPI Flash @0x90000000) are now disabled by default.
Version V7.84d (2023-01-25)
DLL
- Microchip ATSAMDxxx, ATSAMExxx: QSPI flash bank was erroneously assumed to be always present. Fixed.
- Renesas RA-series: Low power mode was not restored on disconnect. Fixed.
- Renesas RA-series: Under certain circumstances determining TrustZone configuration on connect did not work. Fixed.
- Renesas RA6M4: QSPI flash programming did not work. Fixed.
- ST STM32H7: For some devices, a slightly wrong factory value was programmed to FLASH_OPTSR, in case device security was set. Fixed.
- ST STM32H7Ax/H7Bx: Under some circumstances, connecting to the device could cause the write protection of the device to be set. Introduced in V7.84b. Fixed.
Firmware
- Flasher Package: Installer: Linux: Debain Package + Archive: GUI folder was missing. Fixed.
- Flasher Package: Installer: Linux: Multiple sample files were missing. Fixed.
J-Link Package
- Installer: Linux: Multiple sample files were missing. Fixed.
- Installer: Windows: When specifiying a directory as installation directory that was shared with other files (e.g. "C:\Program Files\"), the uninstaller would remove all contents of the directory. Fixed.
Version V7.84c (2023-01-20)
Highlights:
Trace
- Published out-of-the-box trace example for Infineon Traveo T2G CYTVII-B-H-8M-320-CPU board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- loadfile: Reading an ELF file with a section that is outside of any specified segments could cause the data of that section to be placed at address 0x0. Fixed.
Configurator
- The probe count displayed in the status bar counted probes/ programmers that were connected via USB as well as TCP/IP twice. Fixed.
Control Panel
- Debug tab: Some values were displayed under the wrong section. Fixed.
DLL
- Firmware update dialog: An exclamation mark icon was displayed instead of the intended question mark icon. Fixed.
- Nuvoton M031xB/M031xC/M031xD/M031xE: Flash programming did not work. Fixed.
- Nuvoton M071x: Added debug & flash programming support (https://wiki.segger.com/Nuvoton_M071x).
- Nuvoton M26x: Added debug & flash programming support (https://wiki.segger.com/Nuvoton_M26x).
- Nuvoton M471x: Added debug & flash programming support (https://wiki.segger.com/Nuvoton_M471x).
- NXP iMXRT117x: Detecting FlexSPI2 boot config and booting from FlexSPI2 did not work. Fixed.
- NXP LPC55S69: Remapping of the device names "LPC55S69_core0" and "LPC55S69_core1" was incorrect resulting in wrong flash bank information were assumed. Fixed.
- Renesas RA series: When connecting to the target device via J-Link Remote Server, it could happen that any high-level operation (reset, halt, go, R/W mem, ...) after the connect failed. Fixed.
- SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Some dialogs informing the user that debugging is not possible with a specific probe due to missing support for the given setup (i.e. J-Link EDU Mini with SWD multi-drop, SoC-600 DAP setups, DAP setups with cascaded APs) showed an "information" icon instead of an exclamation mark icon. Fixed.
- ST BlueNRG-LPS: Added debug and flash programming support.
- ST STM32C0: Added debug & flash programming support (https://wiki.segger.com/ST_STM32C0).
- The J-Link DLL refused to work with some older J-Link BASE V9 units. Fixed.
- Xilinx Zynq-7000: Added optional flash loader with PLL initialization. For more information, see https://wiki.segger.com/Xilinx_Zynq-7000
Firmware
- Flasher ARM V5-1: Added optional output of the DAT file CRC value to the terminal interface after programming.
- Flasher ARM V5-1: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher ARM V5-1: UniversalFlasher: Algorithms that made use of pin override functionality to implement UART / SPI / ... protocols could cause the Flasher firmware to crash because of missing NULL pointer check in the firmware. Fixed.
- Flasher ARM V5: Added optional output of the DAT file CRC value to the terminal interface after programming.
- Flasher ARM V5: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher ARM V5: UniversalFlasher: Algorithms that made use of pin override functionality to implement UART / SPI / ... protocols could cause the Flasher firmware to crash because of missing NULL pointer check in the firmware. Fixed.
- Flasher Compact V5: SFL: Added optional output of the DAT file CRC value to the terminal interface after programming.
- Flasher Compact V5: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher Compact V5: UniversalFlasher: Algorithms that made use of pin override functionality to implement UART / SPI / ... protocols could cause the Flasher firmware to crash because of missing NULL pointer check in the firmware. Fixed.
- Flasher Portable PLUS V1: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher Portable PLUS V1: UniversalFlasher: unierror.log: For parameterized log outputs, the value after the message was missing. Fixed.
- Flasher Portable PLUS V5: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher Portable PLUS V5: UniversalFlasher: Algorithms that made use of pin override functionality to implement UART / SPI / ... protocols could cause the Flasher firmware to crash because of missing NULL pointer check in the firmware. Fixed.
- Flasher Portable PLUS V5: UniversalFlasher: unierror.log: For parameterized log outputs, the value after the message was missing. Fixed.
- Flasher PRO V5-1: Added optional output of the DAT file CRC value to the terminal interface after programming.
- Flasher PRO V5-1: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher PRO V5-1: UniversalFlasher: Algorithms that made use of pin override functionality to implement UART / SPI / ... protocols could cause the Flasher firmware to crash because of missing NULL pointer check in the firmware. Fixed.
- Flasher PRO V5: Added optional output of the DAT file CRC value to the terminal interface after programming.
- Flasher PRO V5: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher PRO V5: UniversalFlasher: Algorithms that made use of pin override functionality to implement UART / SPI / ... protocols could cause the Flasher firmware to crash because of missing NULL pointer check in the firmware. Fixed.
- Flasher PRO XL V5-1: SFL: Added optional output of the DAT file CRC value to the terminal interface after programming.
- Flasher PRO XL V5-1: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher PRO XL V5-1: UniversalFlasher: Algorithms that made use of pin override functionality to implement UART / SPI / ... protocols could cause the Flasher firmware to crash because of missing NULL pointer check in the firmware. Fixed.
- Flasher PRO XL V5: Added optional output of the DAT file CRC value to the terminal interface after programming.
- Flasher PRO XL V5: SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Flasher PRO XL V5: UniversalFlasher: Algorithms that made use of pin override functionality to implement UART / SPI / ... protocols could cause the Flasher firmware to crash because of missing NULL pointer check in the firmware. Fixed.
- J-Link EDU/BASE/PLUS V11: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
- J-Link EDU/BASE/PLUS V11: Standby mode: Further reduced power consumption.
- J-Link EDU/BASE/PLUS V11: Standby mode: Power consumption of J-Link was slightly higher in standby mode, if a debug session was running before. Fixed.
- J-Link EDU/BASE/PLUS V12: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
- J-Link EDU/BASE/PLUS V12: Standby mode: Further reduced power consumption.
- J-Link EDU/BASE/PLUS V12: Standby mode: Power consumption of J-Link was slightly higher in standby mode, if a debug session was running before. Fixed.
- J-Link PRO V5-1: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
- J-Link PRO V5-1: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
- J-Link PRO V5: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
- J-Link PRO V5: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
- J-Link PRO V6: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
- J-Link PRO V6: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
- J-Link ULTRA+ V5-1: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
- J-Link ULTRA+ V5-1: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
- J-Link ULTRA+ V5: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
- J-Link ULTRA+ V5: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
- J-Link ULTRA+ V6: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
- J-Link ULTRA+ V6: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
- J-Link-OB-K22-CortexA: Added support for SWD multi-drop to firmware.
- J-Link-OB-K22-CortexM: Added support for SWD multi-drop to firmware.
- J-Link-OB-K22-RISCV: Added support for SWD multi-drop to firmware.
J-Flash
- Reading an ELF file with a section that is outside of any specified segments could cause the data of that section to be placed at address 0x0. Fixed.
- SFL: Stack alignment of RAMCode was increased from 8-byte to 16-byte for all architectures which broke some very tight customer RAMCodes on targets with 1 KB RAM. Introduced in V7.80c. Fixed.
- Warning and error messages in the log window are now colored.
Version V7.84b (2023-01-11)
Commander
- Calling exec functions with Windows 32-bit version could cause J-Link Commander to crash. Introduced with V7.82c. Fixed.
DLL
- Increased verbosity of error messages if target RAM could not be preserved.
- Maxim MAX32570: Added QSPI flash programming support.
- NXP i.MXRT104x device family: Added debug & flash programming (FlexSPI) support.
- NXP K32W14: Added debug & flash programming support (https://wiki.segger.com/NXP_K32W14).
- NXP KW45: Added debug & flash programming support (https://wiki.segger.com/NXP_KW45).
- Trace: Added warning in case an execution address not covered by the trace cache is accessed/traced (referenced by received trace data).
Firmware
- J-Trace PRO V2 Cortex: LEDs: USB LED did not become orange if target reset pin == active (LOW) was detected (see behavior of J-Link BASE/PLUS center LED). Fixed.
- J-Trace PRO V2 CortexM: LEDs: USB LED did not become orange if target reset pin == active (LOW) was detected (see behavior of J-Link BASE/PLUS center LED). Fixed.
- J-Trace PRO V3 Cortex: LEDs: USB LED did not become orange if target reset pin == active (LOW) was detected (see behavior of J-Link BASE/PLUS center LED). Fixed.
- J-Trace PRO V3 CortexM: LEDs: USB LED did not become orange if target reset pin == active (LOW) was detected (see behavior of J-Link BASE/PLUS center LED). Fixed.
- J-Trace PRO V3 RISC-V: LEDs: USB LED did not become orange if target reset pin == active (LOW) was detected (see behavior of J-Link BASE/PLUS center LED). Fixed.
J-Flash
- On sector layouts with multiple ranges, J-Flash did not display the sector boundaries of the second range correctly. Introduced with V7.82c. Fixed.
J-Scope
- Added -RTTSearchRanges command line option.
- Added checkbox to symbol table for toggling symbol visibility.
- Improved startup-dialog to include a list of recently used projects.
Version V7.84a (2022-12-22)
DLL
- ARMv8-A/R: AArch32: Implementation state for EL2 & EL3 could be reported incorrectly (e.g. EL2 was implemented but J-Link detected not implemented) because EDAA32PFR was not read properly. Fixed.
- Infineon CY8C6xxx, CYB06xxx, CYW20829xx device series: Updated 3rd party support package provided by Infineon.
- Infineon XMC7100 device series: Added 3rd party support package provided by Infineon.
- Renesas RZ/G2UL: Added debug support for R9A07G043U12 and R9A07G043U11.
Firmware
- J-Link PRO V5-1: Eco Plus mode handling temporarily disabled.
- J-Link PRO V5: Eco Plus mode handling temporarily disabled.
- J-Link PRO V6: Eco Plus mode handling temporarily disabled.
- J-Link ULTRA+ V5-1: Eco Plus mode handling temporarily disabled.
- J-Link ULTRA+ V5: Eco Plus mode handling temporarily disabled.
- J-Link ULTRA+ V6: Eco Plus mode handling temporarily disabled.
Version V7.84 (2022-12-14)
DLL
- Added debug & flash programming support for ST STM32F723VC.
- Added support for ARM Cortex-R52+ (Handled as Cortex-R52).
- AUCU AU3x device series: Updated 3rd party support package provided by AUCU.
- NXP KW45: Decreased the initial connect time by improving the device specific connect sequence.
- Option byte support disabled for GigaDevice GD32A50x devices due to customers request.
- Renesas RZ/G2L: Updated list of supported device names.
- Renesas RZ/G2LC: Updated list of supported device names.
- ST STM32F74x/STM32F75x: Wrong loader was selected as default for QSPI flash bank. Fixed.
- ST STM32F7: Added QSPI flash programming support for pin configuration CLK@PF10_nCS@PB10_D0@PF8_D1@PF9_D2@PF7_D3@PF6.
- ST STM32H7 device series: Erasing entire internal flash did not work. Fixed.
- ST STM32H7 device series: For devices with internal flash of 512 KB or less, removing write protection did not work properly. Fixed.
Firmware
- ARMv8-A/R firmware module V7 (e.g. Cortex-R52): AArch32: The following combinations of CoreModeHalted -> CoreModeContinue (CPSR modified via debugger) resulted in an exception: HYP -> non-HYP, non-HYP -> HYP, USR -> non-USR, non-USR -> USR. Fixed.
- Flasher ARM V5-1: Implemented ARMv8-A/R firmware module V7.
- Flasher ARM V5: Implemented ARMv8-A/R firmware module V7.
- Flasher Compact V5: Implemented ARMv8-A/R firmware module V7.
- Flasher Portable PLUS V5: Implemented ARMv8-A/R firmware module V7.
- Flasher PRO V5-1: Implemented ARMv8-A/R firmware module V7.
- Flasher PRO V5: Implemented ARMv8-A/R firmware module V7.
- Flasher PRO XL V5-1: Implemented ARMv8-A/R firmware module V7.
- Flasher PRO XL V5: Implemented ARMv8-A/R firmware module V7.
- J-Link EDU Mini V1: Implemented ARMv8-A/R firmware module V7.
- J-Link EDU/BASE/PLUS V11: Implemented ARMv8-A/R firmware module V7.
- J-Link EDU/BASE/PLUS V11: Implemented LED dimming in Standby mode.
- J-Link EDU/BASE/PLUS V12: Implemented ARMv8-A/R firmware module V7.
- J-Link EDU/BASE/PLUS V12: Implemented LED dimming in Standby mode.
- J-Link Lite-S124: Implemented ARMv8-A/R firmware module V7.
- J-Link OB-S124: Implemented ARMv8-A/R firmware module V7.
- J-Link PRO V5-1: "Eco mode CPU" and "Eco mode Logic" support flags were not returned properly, so J-Link Configurator did not show Eco mode selection options. Fixed.
- J-Link PRO V5-1: Implemented ARMv8-A/R firmware module V7.
- J-Link PRO V5-1: Implemented LED dimming in Standby mode.
- J-Link PRO V5: "Eco mode CPU" and "Eco mode Logic" support flags were not returned properly, so J-Link Configurator did not show Eco mode selection options. Fixed.
- J-Link PRO V5: Implemented ARMv8-A/R firmware module V7.
- J-Link PRO V5: Implemented LED dimming in Standby mode.
- J-Link PRO V6: "Eco mode CPU" and "Eco mode Logic" support flags were not returned properly, so J-Link Configurator did not show Eco mode selection options. Fixed.
- J-Link PRO V6: Implemented ARMv8-A/R firmware module V7.
- J-Link PRO V6: Implemented LED dimming in Standby mode.
- J-Link ULTRA+ V5-1: "Eco mode CPU" and "Eco mode Logic" support flags were not returned properly, so J-Link Configurator did not show Eco mode selection options. Fixed.
- J-Link ULTRA+ V5-1: Implemented ARMv8-A/R firmware module V7.
- J-Link ULTRA+ V5-1: Implemented LED dimming in Standby mode.
- J-Link ULTRA+ V5: "Eco mode CPU" and "Eco mode Logic" support flags were not returned properly, so J-Link Configurator did not show Eco mode selection options. Fixed.
- J-Link ULTRA+ V5: Implemented ARMv8-A/R firmware module V7.
- J-Link ULTRA+ V5: Implemented LED dimming in Standby mode.
- J-Link ULTRA+ V6: "Eco mode CPU" and "Eco mode Logic" support flags were not returned properly, so J-Link Configurator did not show Eco mode selection options. Fixed.
- J-Link ULTRA+ V6: Implemented ARMv8-A/R firmware module V7.
- J-Link ULTRA+ V6: Implemented LED dimming in Standby mode.
- J-Link WiFi V1: Implemented ARMv8-A/R firmware module V7.
J-Flash
- Added debug & flash programming support for ST STM32F723VC.
Version V7.82f (2022-12-08)
Configurator
- Configuration dialog: For J-Links that support J-Link LPM (https://wiki.segger.com/J-Link_LPM), e.g. J-Link EDU/ BASE/ PLUS V11, where LPM has not been configured yet, "Lowest possible power" was shown as configured LPM level, despite "Max. performance" being the default. Fixed.
Version V7.82e (2022-12-07)
Commander
- Commands "Mem", "Mem8", "Mem16", "Mem32": Added support for 64bit addresses.
- Commands "SaveBin", "VerifyBin": Added support for 64bit addresses.
- Commands "Write1", "Write2", "Write4": Added support for 64bit addresses.
Configurator
- Configuration Dialog: Added elements to configure J-Link LPM for models that support the feature (https://wiki.segger.com/J-Link_LPM).
DLL
- Added Debug & Flash support for Mindmotion MM32F0xx Family (https://wiki.segger.com/MindMotion_MM32F0).
- Added Debug & Flash support for Mindmotion MM32F3xx Family (https://wiki.segger.com/MindMotion_MM32F3).
- Added flash programming support for TI MSPM0G (https://wiki.segger.com/TI_MSPM0G#NONMAIN).
- Added flash programming support for TI MSPM0L (https://wiki.segger.com/TI_MSPM0L#NONMAIN).
- Infineon CY8C6xxx: For some devices of the series WFLASH size was mistakenly defined as 2 KB instead of 32 KB. Fixed.
- J-Link script files: If there was a __constant U32 xxx = yyy; expression where yyy was only another __constant, xxx resulted in always being 0. Fixed.
- NXP LPC55S14: Device did no longer support secure flash bank. Introduced with V7.82d. Fixed.
- NXP PN7642: Added debug & flash programming support.
- NXP S32K312: Flash programming didn't work for last 10 sectors if HSE was active. Fixed.
- On slow SPI flashes restoring target state could fail. Fixed.
- Renesas RA device series: Added some additional QSPI flash loader pin configurations for several devices.
- Renesas RA device series: Several devices had a wrong default loader set. Fixed.
- Updated vendor name from "Micronas" to "TDK-Micronas".
Firmware
- J-Link PRO V5-1: VCOM: On Tx, J-Link did 1 STOP bit more than configured by host terminal settings. Fixed. (Did not hurt but limited max. throughput)
- J-Link PRO V5: VCOM: On Tx, J-Link did 1 STOP bit more than configured by host terminal settings. Fixed. (Did not hurt but limited max. throughput)
- J-Link ULTRA+ V5-1: VCOM: On Tx, J-Link did 1 STOP bit more than configured by host terminal settings. Fixed. (Did not hurt but limited max. throughput)
- J-Link ULTRA+ V5: VCOM: On Tx, J-Link did 1 STOP bit more than configured by host terminal settings. Fixed. (Did not hurt but limited max. throughput)
- J-Link-OB-XMC4200: Added support for ARM Cortex-M23, Cortex-M33 cores.
- J-Link-OB-XMC4200: VCOM: Added support generating BREAK condition over terminal application.
- XMC Link: Added support for ARM Cortex-M23, Cortex-M33 cores.
- XMC Link: VCOM: Added support generating BREAK condition over terminal application.
Version V7.82d (2022-11-23)
Commander
- On some Probes, the "Reboot" command failed, even though it was supported by the probe. Fixed.
DLL
- Added J-Link script file API function JLINK_RISCV_DMI_AutodetectDMISettings(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Added J-Link script file API function JLINK_RISCV_DMI_ClearState(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Added J-Link script file API function JLINK_RISCV_DMI_ReadReg(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Added J-Link script file API function JLINK_RISCV_DMI_ReadRegMultiple(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Added J-Link script file API function JLINK_RISCV_DMI_SetDMISettings(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Added J-Link script file API function JLINK_RISCV_DMI_WriteReg(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Added J-Link script file API function JLINK_RISCV_DMI_WriteRegMultiple(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
- Added JTAG TAPId 0x06413B47 (Geehy APM32 Boundary Scan) to the list of known TAPIDs.
- Added JTAG TAPId 0x10900A6D (NucleiSys N900) to the list of known TAPIDs.
- Added JTAG TAPId 0x10999A6D (NucleiSys N900) to the list of known TAPIDs.
- Infineon S6E2C series: Updated RAM addresses and sizes. Fixed.
- NXP i.MXRT117x: Added flash programming support for FlexSPI 2 flash bank.
- NXP LPC55xx/LPC55Sxx: Some non-secure devices mistakenly supported the secure flash bank while their secure counterpart did not. Fixed.
- NXP MIMXRT1061xxx5A, MIMXRT1061xxx5B, MIMXRT1061xxx6A, MIMXRT1061xxx6B, MIMXRT1062xxx5A, MIMXRT1062xxx5B, MIMXRT1062xxx6A, MIMXRT1062xxx6B, MIMXRT106A-ALEXA2: Default loader was mistakenly set to HyperFlash, not QSPI. Introduced with V7.70d. Fixed.
- NXP S32K3xx: Can't flash within last flash block when HSE (Hardware Secure Engine) is activated. Fixed.
- Renesas RA6M3: Created a wiki article (https://wiki.segger.com/Renesas_RA6M3).
- ST STM32 devices: Under rare circumstances, connecting to the devices under reset could fail when the device was running in low power mode. Fixed.
- ST STM32WL5/WLE: Added device specific connect and native unlock functionality.
Firmware
- J-Link PRO V5-1: VCOM: For some terminal applications, if parity / STOP bit settings changed but baudrate did not, it could happen that new settings were not taken into account. Fixed.
- J-Link PRO V5-1: VCOM: STOP bit settings from host terminal were ignored. Fixed.
- J-Link PRO V5-1: VCOM: When sending a bulk of data, there could be a gap of up to 1ms after the initial byte. Fixed.
- J-Link PRO V5: VCOM: For some terminal applications, if parity / STOP bit settings changed but baudrate did not, it could happen that new settings were not taken into account. Fixed.
- J-Link PRO V5: VCOM: STOP bit settings from host terminal were ignored. Fixed.
- J-Link PRO V5: VCOM: When sending a bulk of data, there could be a gap of up to 1ms after the initial byte. Fixed.
- J-Link ULTRA+ V5-1: VCOM: For some terminal applications, if parity / STOP bit settings changed but baudrate did not, it could happen that new settings were not taken into account. Fixed.
- J-Link ULTRA+ V5-1: VCOM: STOP bit settings from host terminal were ignored. Fixed.
- J-Link ULTRA+ V5-1: VCOM: When sending a bulk of data, there could be a gap of up to 1ms after the initial byte. Fixed.
- J-Link ULTRA+ V5: VCOM: For some terminal applications, if parity / STOP bit settings changed but baudrate did not, it could happen that new settings were not taken into account. Fixed.
- J-Link ULTRA+ V5: VCOM: STOP bit settings from host terminal were ignored. Fixed.
- J-Link ULTRA+ V5: VCOM: When sending a bulk of data, there could be a gap of up to 1ms after the initial byte. Fixed.
STM32 Utility
- Added ST STM32WB and STM32WL5/WLE.
Version V7.82c (2022-11-16)
Commander
- Some command strings (e.g. "RTTTelnetAllowNonLocalClient") could not be set prior to opening a connection to J-Link, although the command string required that. Fixed.
DLL
- CMSemicon BAT32G133: Added debug & flash programming support (https://wiki.segger.com/CMSemicon_BAT32G133).
- CMSemicon BAT32G157: Added debug & flash programming support (https://wiki.segger.com/CMSemicon_BAT32G157).
- Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
- Geehy APM32 devices: Size of option bytes flash bank was not correctly displayed in device selection dialog. Fixed.
- NXP LPC55x3x: Added FLEXSPI flash programming support.
- SEGGER Flash Loader (SFL): Under special circumstances, erase timeout was calculated incorrectly in case of multi sector erase was performed. Fixed.
- Some J-Link features were not enabled for the J-Link OB-nRF5340-NordicSemi. Fixed.
- ST STM32WB55: Stand-alone programming of option bytes was not possible due to a padding problem in the Flasher data file. Fixed.
- ST STM32WL55: Stand-alone programming of option bytes was not possible due to a padding problem in the Flasher data file. Fixed.
Firmware
- J-Link-OB-BBC-microbit-V1: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed. https://www.segger.com/downloads/jlink/#BBC_microbit
- J-Link-OB-BBC-microbit-V2: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed. https://www.segger.com/downloads/jlink/#BBC_microbit
- J-Trace PRO V2 Cortex: USB stability issues could be observed when using trace probe with certain USB host controllers (especially ones from Intel). Fixed.
- J-Trace PRO V2 CortexM: USB stability issues could be observed when using trace probe with certain USB host controllers (especially ones from Intel). Fixed.
- J-Trace PRO V3 Cortex: USB stability issues could be observed when using trace probe with certain USB host controllers (especially ones from Intel). Fixed.
- J-Trace PRO V3 CortexM: USB stability issues could be observed when using trace probe with certain USB host controllers (especially ones from Intel). Fixed.
- J-Trace PRO V3 RISC-V: USB stability issues could be observed when using trace probe with certain USB host controllers (especially ones from Intel). Fixed.
GDB Server
- Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
J-Flash
- Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
- J-Flash did not work properly for devices with flash banks that had more than 8192 sectors. Fixed.
- When opening old J-Flash project files (e.g. generated with J-Flash V5.12i), the sector selection was read incorrectly and no sectors were selected in the opened project. Fixed.
J-Flash Lite
- Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
J-Scope
- Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
JTAG Load
- Fixed typo in ExecFREQUENCY() output.
RTT Viewer
- Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
SWO Viewer
- Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
Version V7.82b (2022-11-09)
DLL
- Added debug support for Codasip L11 (RV32) device/core. https://wiki.segger.com/Codasip_L11
- Added debug support for Codasip L31 (RV32) device/core. https://wiki.segger.com/Codasip_L31
- Added debug support for Codasip L31F (RV32) device/core. https://wiki.segger.com/Codasip_L31
- Direct SPI programming: When trying to transfer SPI data at very low speeds (e.g. < 1000 kHz), the J-Link software would sometimes run into timeouts. Fixed.
- GigyDevice GD32A50x: Added debug and flash programming support (internal & option bytes).
- J-Link comand SetInitWorkRAMOnConnect did not work on unkown devices. Fixed.
- MindMotion MM32F5270: Added debug & flash programming support (internal, external QSPI and option bytes).
- Renesas RA4E1, RA4M2, RA4M3, RA6E1, RA6M4, RA6M5, RA6T2: Under certain circumstances connect via JTAG did not work. Fixed.
- Renesas RA4T1 / RA6T3: Added IDCode authentication support.
- Renesas RA4T1 / RA6T3: Removed IDCode authentication support for now because we do not have a valid indicator to determine the current security status.
- Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
Firmware
- Flasher ARM V5: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- Flasher ARM V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
- Flasher ARM V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
- Flasher Compact V5: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- Flasher Compact V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
- Flasher Compact V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
- Flasher Compact V5: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- Flasher Package: DEB package: Trying to install the J-Link software package on WSL2 using dpkg failed. Fixed.
- Flasher Portable PLUS V5: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- Flasher Portable PLUS V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
- Flasher Portable PLUS V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
- Flasher Portable PLUS V5: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- Flasher PRO V5: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- Flasher PRO V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
- Flasher PRO V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
- Flasher PRO V5: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- Flasher PRO XL V5: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- Flasher PRO XL V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
- Flasher PRO XL V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
- Flasher PRO XL V5: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- Flasher: SiliconLabs EFR32xG21: Stand-alone mode did not work. Fixed.
- Flasher: SiliconLabs EFR32xG22: Stand-alone mode did not work. Fixed.
- Flasher: SiliconLabs EFR32xG23: Stand-alone mode did not work. Fixed.
- J-Link EDU Mini V1: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Link EDU Mini V1: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- J-Link EDU/BASE/PLUS V11: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- J-Link OB RA4M2-Full: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- J-Link OB RA4M2-RISCV: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- J-Link OB-K22-RISCV: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- J-Link PRO V5: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Link PRO V5: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- J-Link ULTRA+ V5: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Link ULTRA+ V5: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- J-Link WiFi V1: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Link WiFi V1: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
- J-Link-OB-K22-CortexA: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.
- J-Link-OB-K22-CortexM: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.
- J-Link-OB-K22-NordicSemi: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.
- J-Link-OB-K22-Qorvo: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.
- J-Link-OB-K22-RISCV: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.
- J-Link-OB-K22-SiFive: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.
- J-Link-OB-nRF5340-NordicSemi: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.
- J-Link-OB-SAM3U128-V2-NordicSemi: Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.
- J-Trace PRO V2 Cortex: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Trace PRO V2 CortexM: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Trace PRO V3 Cortex: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Trace PRO V3 CortexM: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Trace PRO V3 RISC-V: cJTAG: When setting/changing the cJTAG speed during the debug session, on a target with buggy/missing KEEPER logic (e.g. ESWIN ECR2560), the debug session could be aborted (WriteMem(), ReadMem() and other operations continuously failed). Fixed.
- J-Trace PRO V3 RISC-V: RISC-V: Firmware module version 1: writing memory via system bus and JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing memory resulted in an error return even if write was successful. Fixed.
GDB Server
- Added support for GDB "detach" command.
- Missing support for GDB "detach" command could cause issues in some environments (e.g. VSCode debugging plugins). Fixed.
- Updated Zephyr RTOS plugin to latest source base.
J-Flash
- Opening ELF files that contained more than 5 data ranges for the application image could cause J-Flash to freeze, crash or similar. Introduced in V7.82. Fixed.
J-Flash SPI
- When trying to do SPI flash operations at very low speed (e.g. < 1000 kHz), the flash operation could fail due to running into timeouts. Fixed.
J-Link Package
- DEB package: Trying to install the J-Link software package on WSL2 using dpkg failed. Fixed.
Version V7.82a (2022-10-30)
Commander
- Command "rcp15ex": Changed output in case of error.
- Command "wcp15ex": Did not indicate errors properly. Fixed.
DLL
- ARMv8-AR: CPU states were not invalidated on reset. Fixed.
- ARMv8-AR: If reading a CP15 register failed, following reads of CP15 registers all returned errors and took >= 100ms each. Fixed.
- J-Link did no longer work with SPI flash ISSI IS25LP512M. Introduced with V7.80b. Fixed.
- NXP i.MXRT1050 devices: RAM size was defined as too large. Introduced in 7.70d. Fixed.
- NXP i.MXRT1060 devices: RAM size was defined as too large. Introduced in 7.70d. Fixed.
- Renesas RA4T1, RA6T3: Split off PCode for ID code authentication.
- ST SR6P7x: Connect after executing a reset failed. Fixed.
- Western Digital SweRV_EH1 device selection: Core type was set to RV64 while RV32 is correct. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V11: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
- J-Link PRO V5.1: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
- J-Link PRO V5: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
- J-Link ULTRA+ V5.1: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
- J-Link ULTRA+ V5: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
- J-Link WiFi V1: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
GDB Server
- ARMv8-AR: Corrected CP15 register name "ATS1HRc" -> "ATS1HR"
- ARMv8-AR: Corrected CP15 register name "ATS1HWc" -> "ATS1HW"
- ARMv8-AR: Corrected CP15 register name "CP15DMBi" -> "CP15DMB"
- ARMv8-AR: Corrected CP15 register name "CP15DSBi" -> "CP15DSB"
- ARMv8-AR: Corrected CP15 register name "PMCCFILTRk" -> "PMCCFILTR"
- ARMv8-AR: Corrected CP15 register name "SCRd" -> "SCR"
- ARMv8-AR: Corrected CP15 register name "TLBIALLHc" -> "TLBIALLH"
- ARMv8-AR: Corrected CP15 register name "TLBIALLHISc" -> "TLBIALLHIS"
- ARMv8-AR: Corrected CP15 register name "TLBIALLNSNHc" -> "TLBIALLNSNH"
- ARMv8-AR: Corrected CP15 register name "TLBIALLNSNHISc" -> "TLBIALLNSNHIS"
- ARMv8-AR: Corrected CP15 register name "TLBIMVAHc" -> "TLBIMVAH"
- ARMv8-AR: Corrected CP15 register name "TLBIMVAHISc" -> "TLBIMVAHIS"
- ARMv8-AR: Corrected CP15 register name 64-bit instance of "PAR" -> "PAR_64"
- ARMv8-AR: If reading a CP15 register failed (e.g. register not implemented), no error was reported to GDB. Fixed.
- ARMv8-AR: If reading a CP15 register failed, following reads of CP15 registers all returned errors and took >= 100ms each. Fixed.
- Configuration dialog: On some setups (e.g 13-inch M1 MacBook), the dialog was larger than the screen and some elements were inaccessible. Fixed.
- Updated Zephyr RTOS plugin to latest source base.
- When connecting to GDB Server via "localhost", some GDB clients try to connect to IPv6 first before trying to connect via IPv4. This caused a delay (a few seconds) in connection buildup because GDB Server did not support IPv6 connections. Fixed.
J-Flash
- When trying to open project files generated by old J-Flash versions (e.g. V4.99c from 2015), J-Flash could crash. Fixed.
J-Flash SPI
- When loading projects that specified SPI speeds lower than 1000 kHz, J-Flash SPI changed the speed to 1000 kHz. Fixed.
Manual
- UM08022: Updated how to enter the file access mode.
RTT Viewer
- Opening the channel info dialog (F8) could cause the application to freeze or crash. Fixed.
- When the input line was empty but end of line character(s) were selected, no data was sent when pressing the "Send" button or when pressing Return/Enter. Fixed.
SWO Viewer
- Added command line option to directly specify a J-Link script file. See: https://wiki.segger.com/J-Link_SWO_Viewer#-jlinkscriptfile
Version V7.82 (2022-10-13)
Commander
- loadbin: The error message when trying to load files of an unknown / unsupported format contained a typo. Fixed.
- loadfile: Added support for ELF file formats (.elf, .out, .axf).
- loadfile: The error message when trying to load files of an unknown / unsupported format contained a typo. Fixed.
DLL
- Added debug & flash programming support for Cypress CY8C4746xxx-Sxxx and CY8C4747xxx-Sxxx series.
- Added support for J-Link-Lite-S124.
- Cadence Xtensa: Added some Xtensa LX TAPId's to the supported list (e.g. "0x120034E5")
- Flash programming: Blank check did not work properly for non-turbo mode (All Cortex-A/R based devices or Cortex-M based ones with less than 2 KB work RAM) and if blank/erased value of flash is not 0xFF. Fixed.
- Improved connect time for Cortex-M targets when using SWD.
- In some cases, J-Link DLL did not work with Keil-based flash loaders. Introduced in V7.80. Fixed.
- Infineon TLE986x: Under special circumstances, verify via CRC could cause issues. Fixed.
- Infineon TLE987x: Under special circumstances, verify via CRC could cause issues. Fixed.
- SEGGER flash loaders (ex open flash loader) with more than 8 elements for FlashDevice.aSectorInfo[] were rejected with an error message. Fixed.
Firmware
- Flasher ARM V5: Flash programming: Blank check did not work properly for non-turbo mode (All Cortex-A/R based devices or Cortex-M based ones with less than 2 KB work RAM) and if blank/erased value of flash is not 0xFF. Fixed.
- Flasher ARM V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
- Flasher Compact V5: Flash programming: Blank check did not work properly for non-turbo mode (All Cortex-A/R based devices or Cortex-M based ones with less than 2 KB work RAM) and if blank/erased value of flash is not 0xFF. Fixed.
- Flasher Compact V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
- Flasher Portable PLUS V5: Flash programming: Blank check did not work properly for non-turbo mode (All Cortex-A/R based devices or Cortex-M based ones with less than 2 KB work RAM) and if blank/erased value of flash is not 0xFF. Fixed.
- Flasher Portable PLUS V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
- Flasher PRO V5: Flash programming: Blank check did not work properly for non-turbo mode (All Cortex-A/R based devices or Cortex-M based ones with less than 2 KB work RAM) and if blank/erased value of flash is not 0xFF. Fixed.
- Flasher PRO V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
- Flasher PRO XL V5: Flash programming: Blank check did not work properly for non-turbo mode (All Cortex-A/R based devices or Cortex-M based ones with less than 2 KB work RAM) and if blank/erased value of flash is not 0xFF. Fixed.
- Flasher PRO XL V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
- J-Link OB Apollo4 CortexM: SWO did not work (no data received via SWOViewer). Fixed.
GDB Server
- ARMv7-R (e.g. Cortex-R4F): Some GDBs complained about a too long reply to the remote 'g' packet. Fixed.
- ARMv8-A/R AArch32 (e.g. Cortex-R52): Added CP15 registers to GDB Server register table.
- Breakpoints did not work properly for unaligned (not word aligned) thumb-2 (32 bit code) instructions. Fixed.
J-Flash
- Added more wiki links and manuals to the help menu.
- Flash operations on devices with multiple flash banks and different loader names selected could fail due to a false-positive when checking for overlapping flash bank memory ranges. Fixed.
- SEGGER flash loaders (ex open flash loader) with more than 8 elements for FlashDevice.aSectorInfo[] were rejected with an error message. Fixed.
- When connecting to a J-Link it was still possible to access the project options, causing undesired effects like freezing or crashing the application. Fixed.
- When connecting to a probe/ programmer, J-Flash now prints the serial number to the log.
J-Flash SPI
- Added more wiki links and manuals to the help menu.
- After closing a project file, multiple message boxes stating "No project file opened." could appear. Fixed.
- Menu bar: When no project file was opened, some entries were enabled although the action was not available without an opened project (e.g. "Download config & data file to Flasher"). Fixed.
- Trying to create a new project when no project file was currently opened would cause multiple message boxes stating "No project file opened." to appear. Fixed.
- When a data file was opened while no project was opened, a message box stating "No project file opened." appeared each time the data file gained focus. Fixed.
- When connecting to a J-Link it was still possible to access the project options, causing undesired effects like freezing or crashing the application. Fixed.
J-Scope
- Repeated ELF file parsing could fail. Fixed.
Version V7.80d (2022-10-04)
Control Panel
- Settings tab: Added field for configuring the threshold for enabling Read-Modify-Write behavior (https://wiki.segger.com/Read-Modify-Write_Flash).
- Settings tab: The tab did not update periodically after it was opened. Introduced with V7.22. Fixed.
DLL
- Added SPI Flash programming support for onsemi LE25U20AQG.
- AUCU AU3x: Updated device specific reset strategy.
- Cadence Xtensa: Added "Xtensa LX6" as supported + selectable device name. (For custom Xtensa LX6 based cores)
- EFR32 Series 1 devices: Connect would fail for some devices. Introduced V7.80c. Fixed.
- Infineon CYT3DL: Updated supported device list to accept the new part numbers from the latest datasheet.
- JLinkDevices.xml: Device entry with missing flashloader could cause DLL to crash. Fixed.
- JLinkDevices.xml: Increased verbosity of error message for broken device entries.
- Qorvo PAC55xx series: Added debug & flash programming support.
- SWO: Added native SWO support for ST STM32U5 series devices.
- The Read-Modify-Write threshold (https://wiki.segger.com/Read-Modify-Write_Flash) is now stored across sessions via the J-Link settings file, if one is present.
- Updated MCU-Link Pro and MCU-Link terms of use dialog to name the covered cores instead of the covered families.
J-Flash
- When downloading multiple files to a Flasher, multiple progress dialogs were opened and closed swiftly, making it look like a dialog was flashing. Fixed.
J-Flash SPI
- Added SPI Flash programming support for onsemi LE25U20AQG.
- Project settings: Flash: On small screens (22" and smaller), it could happen that the dialog was too tall to reach the "OK" and "Cancel" buttons and the dialog could not be resized. Fixed.
- Project settings: Flash: There was whitespace below the "Use Quad Mode" checkbox even when it was not checked. Fixed.
- When downloading multiple files to a Flasher, multiple progress dialogs were opened and closed swiftly, making it look like a dialog was flashing. Fixed.
Version V7.80c (2022-09-27)
DLL
- Geehy APM32E1xx, APM32F1xx, APM32F4xx: Connect via JTAG did not work. Fixed.
- Infineon PSoC6 devices: SMIF flash bank was mistakenly treated as always present, causing chip erase to fail. Introduced with 7.70d. Fixed.
- ONSemi RSL15: Reset was not working correctly, which could cause erase operations (and similar) to fail. Fixed.
- Silicon Labs EFR32 family: User JTAG chain selection was ignored. Fixed.
- ST STM32WBxx - FUS: The wireless stack state is now being restored in case the user only connects to the device but does not trigger any upgrade process.
Firmware
- Flasher Compact V5: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- Flasher Portable PLUS V5: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- Flasher PRO V5: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- Flasher PRO XL V5: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link EDU Mini V1: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link EDU/BASE/PLUS V10: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link EDU/BASE/PLUS V11: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link OB RA4M2-Full: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link OB RA4M2-RISCV: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link OB SAM3U128 V2 NordicSemi: SWD speed: J-Link OB used half the speed the user selected (e.g. user selected 1 MHz, OB did 500 kHz). Introduced in V7.58e. Fixed.
- J-Link OB-K22-RISCV: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link PRO V4: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link PRO V5: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link ULTRA+ V4: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link ULTRA+ V5: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
- J-Link WiFi V1: RISC-V via JTAG + DMI + writing memory via program buffer: If JTAG was faster than CPU speed it could happen that writing bulk memory (more than 16 bytes) resulted in an error return even if write was successful. Fixed. (Writing single items in memory was not affected by this)
GDB Server
- When used in "No-Localhost-Only-mode" ("Localhost only" was not selected), the RTT TELNET port was still only available for localhost. Fixed.
GDB Server CL
- When "-noLocalhostOnly" was selected ("Localhost only" was not selected), the RTT TELNET port was still only available for localhost. Fixed.
J-Flash
- For flash banks with gaps (e.g. ST STM32F071CB (allow opt. bytes) "Internal flash") the size of the bank was determined incorrectly, causing read, program and erase operations to not affect any range after the gap (e.g. any data after 0x8000000 was not taken into account for ST STM32F071CB (allow opt. bytes) "Internal flash"). Introduced with V7.80. Fixed.
- For some devices (e.g. Infineon CY8C6XXA_CM0P), J-Flash did not determine the correct number of sectors for a flash bank and defaulted to a single sector layout. Fixed.
RTT Viewer
- Command line: Connect to existing session: Added option to connect to a specific process via TELNET port.
- Config dialog: Connect to existing session: Added option to connect to a specific process via TELNET port. See: https://wiki.segger.com/J-Link_RTT_Viewer
Version V7.80b (2022-09-20)
Highlights:
Trace
- Published out-of-the-box trace example for NXP S32K3X4EVB-Q257 and NXP S32K3X4EVB_T172 boards: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
DLL
- Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
- Cortex-M23: ROMTable scan: TPIU and ETM were detected as "Cortex-M23" by mistake. Fixed.
- Renesas RZ/T2M: Added flash programming support for external flashes connected to xSPI0.
Firmware
- J-Link EDU/BASE/PLUS V11: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
- J-Link PRO V5.1: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
- J-Link PRO V5: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
- J-Link ULTRA+ V5.1: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
- J-Link ULTRA+ V5: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
- J-Link WiFi V1: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
GDB Server
- NXP i.MXRT685: Starting a debug session in Cadence Xtensa Xplorer IDE could fail (Xplorer suddenly closed the connection to GDB Server). Fixed.
J-Flash SPI
- Added SPI Flash programming support for ISSI IS25LX512M, IS25WX512M.
Version V7.80a (2022-09-14)
DLL
- Geehy APM32E103xx, APM32F030xx, APM32F003xx, APM32F051xx, APM32F072xx, APM32F091xx, APM32F4xx device families: Added option byte programming support.
- Geehy APM32E103xx, APM32F030xx, APM32F003xx, APM32F051xx, APM32F072xx, APM32F091xx, APM32F4xx device families: Added read- and write-protection detection and unlock.
- RISC-V: Detection if CSR access via abstract commands is supported did not work correctly if core also had NumProgramBuffers != 0. Fixed.
Firmware
- Flasher ARM V5: Under very special circumstances, some subroutines that encountered an error did not pass the error to the caller which could result in an error state being swallowed and a final "OK" result being transmitted instead of "error". Fixed.
- Flasher Compact V5: Under very special circumstances, some subroutines that encountered an error did not pass the error to the caller which could result in an error state being swallowed and a final "OK" result being transmitted instead of "error". Fixed.
- Flasher Portable PLUS V5: Under very special circumstances, some subroutines that encountered an error did not pass the error to the caller which could result in an error state being swallowed and a final "OK" result being transmitted instead of "error". Fixed.
- Flasher PRO V5: Under very special circumstances, some subroutines that encountered an error did not pass the error to the caller which could result in an error state being swallowed and a final "OK" result being transmitted instead of "error". Fixed.
- Flasher PRO XL V5: Under very special circumstances, some subroutines that encountered an error did not pass the error to the caller which could result in an error state being swallowed and a final "OK" result being transmitted instead of "error". Fixed.
J-Flash
- After creating a new project, no sectors of any flash bank were selected initially. Introduced with V7.70. Fixed.
- When creating a new project without a project already open, multiple "No project file opened." error dialogs were shown. Introduced with V7.70. Fixed.
Version V7.80 (2022-09-08)
Control Panel
- RTT Tab: Added TELNET port of DLL instance field.
- Under rare circumstances, "Data rate", "Total received" and "Buffered" were showing wrong values. Fixed.
DLL
- GigaDevice GD32F3 device family: Sector erase was not working correctly on bank 1. Fixed.
- NXP NHS52S04: Added debug and flash programming support.
- Renesas RZ/N2L: Added flash programming support for external (CFI compliant) parallel NOR flashes.
- SiliconLabs: EFR32 Series 2: Added native unlock functionality.
Firmware
- Flasher: ST STM32F7: Option byte programming did not work in stand-alone mode. Fixed.
- J-Link-OB-S124: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Link-OB-S124: Renesas RZ/N2L: Flash programming did not work. Fixed.
J-Flash
- For target devices with multiple flash loaders for a flash bank where the loaders support different flash sizes, J-Flash always used the flash size of the default loader. Fixed.
- Project information: For flash banks without a name (e.g. bank 0 in the default project), the project information widget would show a tree item without text. Fixed.
- Project settings: Flash: The "loader" selection was visible for external banks. Fixed.
- ST STM32F7: J-Flash rejected to download the data & config file in case of option bytes have been selected.
- When opening a project, J-Flash would try and check external flash banks for loaders, despite no loaders being available for external banks. Fixed.
J-Scope
- Tooltip symbol information did not match actual data at cursor position. Fixed.
RTT Logger
- "Bytes written" > 1 MB was partially displayed incorrectly. Fixed.
RTT Viewer
- Under rare circumstances, it could happen that the main window was not showing on startup. Fixed.
Version V7.70e (2022-08-31)
DLL
- Infineon CYxxxx devices: Connect did not work due to missing algo info error. Fixed.
Version V7.70d (2022-08-30)
Commander
- Added "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
DLL
- Added "SuppressGUI" command string. For more information, refer to https://wiki.segger.com/J-Link_Command_Strings#SuppressGUI .
- Added debug and flash programming support for ncoder N4.
- Added debug support for SiFive E20 device/core. (https://wiki.segger.com/SiFive_E20)
- Added debug support for SiFive E61, E61-MC device/core. (https://wiki.segger.com/SiFive_E61)
- Added debug support for SiFive E76-MC device/core.
- Added debug support for SiFive P270 device/core. (https://wiki.segger.com/SiFive_P270)
- Added debug support for SiFive P550 device/core. (https://wiki.segger.com/SiFive_P550)
- Added debug support for SiFive S61, S61-MC device/core. (https://wiki.segger.com/SiFive_S61)
- Added debug support for SiFive S76-MC device/core.
- Added debug support for SiFive U54, U54-MC device/core. (https://wiki.segger.com/SiFive_U54)
- Added debug support for SiFive U64, U64-MC device/core. (https://wiki.segger.com/SiFive_U64)
- Added debug support for SiFive U74, U74-MC device/core. (https://wiki.segger.com/SiFive_U74)
- Added debug support for SiFive X280, X280-MC device/core. (https://wiki.segger.com/SiFive_X280)
- Added PCode functions "JLINK_SetBP()" and "JLINK_ClrBP()".
- AmbiqMicro Apollo4: Added debug and flash programming support for AMAP42KP-KBR, AMA4B2KP-KXR, AMA4B2KP-KBR.
- ARMv8-AR (e.g. Cortex-R52): Software breakpoints did not work correctly. Fixed.
- ARMv8-AR: In case of the sticky error bit was set, the DAP could not be powered when using JTAG. Fixed.
- Geehy APM32: Updated list of supported device names.
- GigaDevice GD32E113 device family: Added debug & flash programming support.
- Infineon CYT2B6, CYT2B7, CYT2B9, CYT2BL device series: Under certain circumstances JTAG connect to M4 core did not work. Fixed.
- Infineon CYT3BB device series: Under certain circumstances JTAG connect to M7 core did not work. Fixed.
- Infineon CYT4BB, CYT4BF device series: Under certain circumstances JTAG connect to M7 cores did not work. Fixed.
- Renesas RZ/T2M: By default, the xSPI0 and xSPI1 module were disabled after reset. Fixed.
Firmware
- Flasher ARM V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- Flasher Compact V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- Flasher Portable PLUS V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- Flasher PRO V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- Flasher PRO XL V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- J-Link EDU Mini V1: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- J-Link EDU Mini V1: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- J-Link EDU/BASE/PLUS V11: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- J-Link PRO V5: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- J-Link PRO V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- J-Link ULTRA+ V5: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- J-Link ULTRA+ V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- J-Link WiFi V1: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- J-Link WiFi V1: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- J-Link-OB-STM32F103: Green LED did not indicate heartbeat & debug interface activity correctly. Fixed.
- J-Trace PRO V2 Cortex: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- J-Trace PRO V2 Cortex: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- J-Trace PRO V2 CortexM: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- J-Trace PRO V3 Cortex: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- J-Trace PRO V3 Cortex: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
- J-Trace PRO V3 CortexM: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
- mIDAS-Link: The J-Link DLL rejected to work with Analog ADRF88xx / ADRF89xx device series. Fixed.
GDB Server
- GUI: Config dialog: Added fields for specifying GDB port, SWO port and telnet port.
J-Scope
- Added "Import Raw" functionality.
- Added command line option -openprj.
- J-Scope now remembers the directory of the last project/ELF/data file opened/saved.
- Under certain circumstances cursor tooltip did not work correctly. Fixed.
Version V7.70c (2022-08-18)
J-Flash
- Some verbose output log messages were printed by default by mistake. Fixed.
Version V7.70b (2022-08-18)
Commander
- ARMv8-AR AArch32: Added the CPSR register to the list of supported register for the wreg command.
- List of supported registers for the wreg command were incorrectly formatted. Fixed.
DLL
- Added JTAG TAPId 0x10307A6D (RISC-V RV32 TAP) to the list of known TAPIds.
- Added JTAG TAPId 0x790007A3 (Boundary Scan TAP) to the list of known TAPIds.
- J-Link script files: If a J-Link script file has setup a JTAG chain manually but the TAPId of the CPU-TAP was unknown to J-Link, the connection to the CPU core was still rejected. Fixed.
- NXP i.MX RT1010 (i.MX RT1011): Device specific reset did not work correctly. Fixed.
- Open flash loader: Under special circumstances, if an entry point was by the linker in the final OFL creation step, J-Link detected a garbage offset for that entry point, instead of reporting that it is not present. Fixed.
Firmware
- Flasher ARM V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
- Flasher ARM V5: Terminal ASCII interface: Under special circumstances a #erase, #auto, ... operation could result in multiple #ERR responses being sent by Flasher. Fixed.
- Flasher Compact V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
- Flasher Compact V5: Terminal ASCII interface: Under special circumstances a #erase, #auto, ... operation could result in multiple #ERR responses being sent by Flasher. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
- Flasher Portable PLUS V5: Terminal ASCII interface: Under special circumstances a #erase, #auto, ... operation could result in multiple #ERR responses being sent by Flasher. Fixed.
- Flasher PRO V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
- Flasher PRO V5: Terminal ASCII interface: Under special circumstances a #erase, #auto, ... operation could result in multiple #ERR responses being sent by Flasher. Fixed.
- Flasher PRO XL V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
- Flasher PRO XL V5: Terminal ASCII interface: Under special circumstances a #erase, #auto, ... operation could result in multiple #ERR responses being sent by Flasher. Fixed.
J-Flash
- Open flash loader: Under special circumstances, if an entry point was by the linker in the final OFL creation step, J-Link detected a garbage offset for that entry point, instead of reporting that it is not present. Fixed.
J-Scope
- Performance broke down when viewing the oldest data with full sample ring buffer. Fixed.
Version V7.70a (2022-08-10)
Highlights:
Trace
- Published out-of-the-box trace example for Toshiba AdBun-M3HQA board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Toshiba AdBun-M4GR board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Toshiba AdBun-M4KN board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
- Published out-of-the-box trace example for Toshiba AdBun-M4NR board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- For some J-Trace models an incorrect MAC address was displayed (e.g. J-Trace PRO V2 Cortex) or the MAC address could not be determined at all (e.g. J-Trace PRO V3 Cortex). Fixed.
DLL
- Cleaned up some ALGO info structs. No functional change.
- Cypress CYT3, CYT4: DCache was not correctly invalidated. Fixed.
- Geehy APM32E103xx, APM32F030xx, APM32F003xx, APM32F051xx, APM32F072xx, APM32F091xx, APM32F4xx device families: Added debug & flash programming support.
- GigaDevice GD32C1 device family: Added debug & flash programming support.
- JLinkDevices.xml files: Aliases were not handled correctly if the aliased device name already existed. Fixed.
- NXP Kinetis Series, iMXRT Series: DCache was not correctly invalidated. Fixed.
- NXP MIMX8DL1, MIMX8SL1: Device specific handling was not executed. Fixed.
- Renesas R5F5140x (RX140): Added debug & flash programming support ("User Area" and "Data Area").
- Renesas R5F5660x (RX660): Added debug & flash programming support ("data flash", "program flash" and "option setting memory").
- Renesas RZ/A3UL: Added debug & flash programming support (https://wiki.segger.com/Renesas_RZ/A3UL).
- Renesas RZ/N2L: Added debug & flash programming support (https://wiki.segger.com/Renesas_RZ/N2L).
- ST STM32H7 Series, STM32F7 Series: DCache was not correctly invalidated. Fixed.
DLL Updater
- Under rare circumstances the DLL path was cut off in the middle of the window. Fixed.
Firmware
- Flasher ARM V5.1: HW version was reported as V5.00 instead of V5.10 in utilities like J-Link/Flasher Commander. Fixed.
- Flasher PRO V5.1: HW version was reported as V5.00 instead of V5.10 in utilities like J-Link/Flasher Commander. Fixed.
- Flasher PRO XL V5.1: HW version was reported as V5.00 instead of V5.10 in utilities like J-Link/Flasher Commander. Fixed.
GDB Server
- Added flash loader selection for target devices with flash banks that support more than one flash loader (e.g. Flash bank "External QSPI Flash" for ST STM32H743XI).
J-Flash
- J-Flash could crash for some some specific devices (like the Microchip ATSAMV70N20B) that provide multiple flash banks and were using an outdated internal device entry format. Fixed.
- Project information: Improved flash bank information display.
- Removed deprecated / unused function unsecure chip.
Version V7.70 (2022-08-03)
Highlights:
DLL
- Added support for Cadence Xtensa LX6/LX7 architecture.
- Cadence Xtensa: Added debug support for HiFi 1, HiFi 3, HiFi 3z, HiFi 4, Fusion F1 cores.
GDB Server
- Added native debug support for Cadence Xtensa LX architecture via Cadence xt-gdb client (Xtensa Xplorer IDE).
Other changes:
CCS Plugin
- Added support for ARM7/9.
Commander
- Added support for Cadence Xtensa LX6/LX7 architecture.
- Command 'erase': Added <noreset> option, to inhibit implicit reset before command operation.
- Command 'erase': Now performs implicit reset before erase.
- Command 'loadbin': Added <noreset> option, to inhibit implicit reset before command operation.
- Command 'loadbin': Now performs implicit reset before download.
- Command 'loadfile': Added <noreset> option, to inhibit implicit reset before command operation.
- Command 'loadfile': Now performs implicit reset before download.
DLL
- Alif Semiconductor AC302, AC512, AC722 device series: Added flash programming support for Cortex-A32 cores.
- AndesTech A45MP: Added debugging support.
- AndesTech AX45MP: Added debugging support.
- Microchip PIC32CX1025SGxx: Changed device names to "full" device names (e.g. PIC32CX1025SG41 => PIC32CX1025SG41100 & PIC32CX1025SG41128).
- NXP i.MXRT685: Added device selection "MIMXRT685S_HiFi4" for debugging support of HiFi 4 core via J-Link Commander, GDB Server, ...
- Renesas R-IN32M4-CL3: Added debug & flash programming support.
- ST STM32: Some device specific debug bits were not reset on disconnect. Fixed.
- ST STM32WB: Add device specific connect and native unlock functionality.
Firmware
- Flasher Compact V5: O2Micro OZ93506: Flash programming did not work in stand-alone mode. Introduced in V6.68. Fixed.
- Flasher Package: Installer: Start Menu entry for "Flasher Registration".
GDB Server
- Cortex-R52: Added target.xml with CPU mode registers (r8_fiq, r13_irq, ...), so these registers are directly accessible through GDB without the need to change the CPSR all the time.
J-Flash
- Added flash loader selection for target devices with flash banks that support more than one flash loader (e.g. Flash bank "External QSPI Flash" for ST STM32H743XI).
J-Scope
- J-Scope did not parse the addresses of structs nested within structs correctly. Fixed.
Manual
- UM08003: Chapter "Command Line interface" * Section "Programming multiple targets in parallel": Updated batch file example. Added Python script example.
SWO Viewer
- Windows: GUI: The SWO Viewer application mistakenly had the icon for "J-Mem". Fixed.
Version V7.68c (2022-07-28)
CCS Plugin
- Changed TIF selected by default to SWD from JTAG.
DLL
- Renesas RA4M2 device series: Added SPI flash programming support for CLK@P500_nCS@P501_D0@P502_D1@P503 pin configuration.
- Renesas RA6M3 device series: Added SPI flash programming support for CLK@P500_nCS@P501_D0@P502_D1@P503 pin configuration.
- ST SR5E1E3 and SR5E1E7 were not selectable in device selection dialog. Fixed.
- ST STM32F413/STM32F423: Write protection of the last 4 sectors was not unlocked by unlock procedure. Fixed.
J-Flash
- ST SR5E1E3 and SR5E1E7 were not selectable in device selection dialog. Fixed.
Version V7.68b (2022-07-22)
CCS Plugin
- Added Cortex-M0 support.
- Added SEC AP support.
- In case the connect was unsuccessful, misleading error messages were printed. Fixed.
DLL
- Added debug support for ST SR5E1 series devices SR5E1E3, SR5E1E7. https://wiki.segger.com/J-Link_ST_SR5E1
- RaspberryPi RP2040: Reset did not work for B0 and B2 silicon. Fixed.
- ST SR5E1 series: Added flash programming support for "code flash 1" flash bank.
- ST SR5E1 series: Added flash programming support for "code flash 2" flash bank.
- ST SR5E1 series: Added flash programming support for "data flash" flash bank.
- ST SR5E1 series: Added flash programming support for "HSM code flash" flash bank.
- ST SR5E1 series: Added flash programming support for "HSM data flash" flash bank.
- ST STM32F7, STM32G0, STM32G4, STM32H7, STM32L0, STM32L1, STM32L4, STM32L5: Flash programming failed if any flash error bits were set before flash operation. Fixed.
Firmware
- Flasher Compact V5: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- Flasher Portable PLUS V5: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- Flasher PRO V5.1: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- Flasher PRO V5: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- Flasher PRO XL V5.1: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- Flasher PRO XL V5: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link EDU Mini V1: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link EDU/BASE/PLUS V10: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link EDU/BASE/PLUS V11: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link OB RA4M2-Full: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link OB RA4M2-RISCV: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link OB-K22-RISCV: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link PRO V5.1: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link PRO V5: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link ULTRA+ V5.1: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link ULTRA+ V5: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
- J-Link WiFi V1: RISC-V via JTAG + DMI: If JTAG was faster than CPU speed it could happen that writing a single item in RAM resulted in an error return even if write was successful. Fixed. (Writing blocks of memory was not affected by this)
GDB Server
- GUI: Added field for specifying a J-Link script file.
- If specified, the path to the J-Link script file is now saved in the J-Link GDB Server settings file and loaded automatically on future sessions.
J-Flash
- When downloading configuration to Flasher for stand-alone mode preparation, for some MCUs the error "Flash bank @ xxx is not supported in stand-alone mode" came up even if the flash bank was supported. Introduced in V7.68. Fixed.
J-Flash Lite
- After selecting a data file, the contained data memory ranges are now printed to the log.
- The "Prog. addr." field is no longer updated when selecting a file format that specifies the data start address.
- The "Prog. addr." field is now only shown when a .bin file is selected.
Version V7.68a (2022-07-19)
DLL
- AUCU AU3x: Changed device names of former AG32 device family.
- GigaDevice GD32F4: Some devices were listed twice. Fixed.
- JLinkDevices XML <FlashBankInfo> tag entries were not parsed correctly. Introduced in V7.68. Fixed.
- ST STM32WB15xx: Wireless stack and FUS upgrade did not work. Fixed.
Firmware
- J-Link EDU Mini V1: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
- J-Link PRO V5: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
- J-Link ULTRA+ V5: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
- J-Link WiFi V1: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
- J-Trace PRO V2 Cortex: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
- J-Trace PRO V2 CortexM: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
- J-Trace PRO V3 Cortex: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
- J-Trace PRO V3 CortexM: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
J-Flash
- Global settings: The dialog was not modal (i.e. after the dialog was opened, the main window could still be interacted with). Fixed.
Version V7.68 (2022-07-14)
Highlights:
Trace
- Published out-of-the-box trace example for ST STM32U575I-EVAL board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
Other changes:
Commander
- Added support for showing J-Link uptime (since boot).
- Updated parameter overview for "wreg" and "rreg" commands.
DLL
- Added debug & flash programming support for some new Toshiba TMPM3H devices (e.g. TMPM3HQFDAFG).
- Added debug & flash programming support for some new Toshiba TMPM4G devices (e.g. TMPM4GRF20FG).
- Added debug & flash programming support for Toshiba TMPM4N devices (e.g. TMPM4NRF20FG).
- Added debug and (QSPI) flash programming support for HPMicro HPM63 (https://wiki.segger.com/HPMicro_HPM63).
- Added debug and flash programming support for missing GD32F4xx devices.
- Added debug and flash programming support for PIC32CX1025SGxx devices.
- Added debug and flash programming support for TI MSPM0G (https://wiki.segger.com/TI_MSPM0G).
- Added debug and flash programming support for TI MSPM0L (https://wiki.segger.com/TI_MSPM0L).
- Added JTAG TAPId pattern 0xXBBXXX2F as known TI ICEPick JTAG device.
- AUCU AG32: Added debug and flash programming support (e.g. for AG32R2080LF).
- Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- ESWIN ECR2560: Added debug and flash programming support.
- Extended command string "CORESIGHT_AddAP" to accept parameter <Parent> to specify parent AP for cascaded AP setups: https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- GigaDevice GD32F470: Added debug & flash programming support.
- GigaDevice GD32L233 devices series: Added debug and flash programming support for internal flash.
- HPMicro HP67xxxANx, HP67xxxVMx : Added support for second core.
- Infineon CY8C6 family: Updated Infineon 3rd party Device Support.
- Infineon CYT2B9, CYT4BB: More detailed structure of the supervisory flash.
- Maxim (Analog Devices) MAX32690: Added debug and flash programming support.
- NXP MKL81 device series: Added debug and flash programming support.
- O2Micro OZ935xx device series: Added flash programming support for EEPROM.
- Renesas R7FA6M5BF: Added debug & flash programming support.
- Renesas RA4T1: Added debug & flash programming support.
- Renesas RA6T3: Added debug & flash programming support.
- Renesas RZ/T2M: Added authentication support (https://wiki.segger.com/Renesas_RZ/T2M#JTAG_Authentication).
- Renesas RZ/T2M: Added debug and (QSPI) flash programming support (https://wiki.segger.com/Renesas_RZ/T2M).
- SiliconLabs BGM220, BGM240, MGM220, MGM240, FGM230, ZGM130, ZGM230 devices series: Added debug and flash programming support for various members of those device families.
- ST STM32G050/STM32G051 device series: Added support for missing devices of device family.
- ST STM32L5: Add device specific connect and native unlock functionality.
- ST STM32U5: Add device specific connect and native unlock functionality.
- Updated debug and (QSPI) flash programming support for HPMicro HPM61 (https://wiki.segger.com/HPMicro_HPM61).
- Updated debug and (QSPI) flash programming support for HPMicro HPM64 (https://wiki.segger.com/HPMicro_HPM64).
- Updated debug and (QSPI) flash programming support for HPMicro HPM67 (https://wiki.segger.com/HPMicro_HPM67).
- Updated debug and (QSPI) flash programming support for HPMicro HPM6x.
Firmware
- J-Link EDU/BASE/PLUS V11: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- J-Link PRO V5.1: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- J-Link PRO V5: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- J-Link ULTRA+ V5.1: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- J-Link ULTRA+ V5: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- J-Link WiFi V1: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- J-Trace PRO V3 Cortex: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
- J-Trace PRO V3 CortexM: Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs
GDB Server
- GUI: Configuration dialog: Renamed "Misc. settings" to "Server settings" and moved them out of the "Target interface" group.
J-Flash
- Added JTAG TAPId pattern 0xXBBXXX2F as known TI ICEPick JTAG device.
- Added support for ARMv8-AR based devices (AArch32 and AArch64).
J-Mem
- Data window: Added support to save memory data to file in different formats (.mot, .srec, .s19, .s28, .s, .hex, .bin, .raw, .c).
- Menu bar: Added "Save memory to data file" action.
J-Run
- Added command line options "--usb" and "--ip" for selecting a J-Link to connect to without user interaction (e.g. selecting in GUI dialog).
- Added log message indicating which J-Link J-Run is connected to.
RTT
- Added special handling for IAR compiler to RTT sources if SEGGER_RTT_CPU_CACHE_LINE_SIZE is defined != 0.
RTT Viewer
- Added a command line option to extend the window title, so that it is easier to distinguish between mutliple RTT Viewer instances.
STM32 Utility
- Added ST STM32L5.
- Added ST STM32U5.
Version V7.66g (2022-07-07)
DLL
- Added workaround for misconfigured J-Link-OB-K22-CortexM on some Ambiq Micro eval boards. See https://wiki.segger.com/J-Link-OB-K22-CortexM#SN_900031732_to_900032331
- ST STM32F1: Watchdogs were not frozen in debug mode. Fixed.
- ST STM32G0: Watchdogs were not frozen in debug mode. Fixed.
Version V7.66f (2022-07-05)
DLL
- Microchip SAMD20/SAMD21: Flash size was incorrect for 128 KB flash devices (64 KB instead of 128 KB). Fixed.
GDB Server
- Cortex-A57: Connection attempts were rejected with "Device family is not supported by GDB Server" error message. Fixed.
J-Flash
- Device selection dialog: In the "Flash Size" column, multiple flash banks were shown "merged" to one when they were adjacent. Fixed.
Version V7.66e (2022-06-28)
Firmware
- Flasher ARM V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
- Flasher Compact V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
- Flasher Portable PLUS V1: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
- Flasher Portable PLUS V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
- Flasher PRO V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
- Flasher PRO XL V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
- J-Link EDU Mini V1: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Link OB K22 Cortex-A: cJTAG: Added support for targets with buggy/missing KEEPER logic. https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link OB K22 Cortex-M: cJTAG: Added support for targets with buggy/missing KEEPER logic. https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link OB K22 RISCV: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link PRO V5: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Link ULTRA+ V5: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Link WiFi V1: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Link-OB-S124: OBs on Renesas eval boards: All OBs reported S/N 831004110. Fixed. (See https://wiki.segger.com/J-Link-OB-S124-Renesas#Serial_number)
- J-Trace PRO V2 Cortex: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Trace PRO V2 CortexM: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Trace PRO V3 Cortex: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
- J-Trace PRO V3 CortexM: ARMv8-A/R: Under special circumstances, the CPU did not continue to execute the target application after halt request. Instead, the CPU jumped to the exception handler. Fixed.
Version V7.66d (2022-06-21)
Commander
- "rreg" command was unable to show 64-bit values for architectures other than ARM AArch64. Fixed.
Firmware
- Flasher ARM V5: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- Flasher Compact V5: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- Flasher Portable PLUS V5: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- Flasher PRO V5: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- Flasher PRO XL V5: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link EDU Mini V1: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link EDU/BASE/PLUS V11: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link PRO V5: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link ULTRA+ V5: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Link WiFi V1: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Trace PRO V2 Cortex: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Trace PRO V2 CortexM: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Trace PRO V3 Cortex: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
- J-Trace PRO V3 CortexM: cJTAG: Added support for targets with buggy/missing KEEPER logic (e.g. ESWIN ECR2560 series devices). https://wiki.segger.com/J-Link_cJTAG_specifics
J-Flash SPI
- When programming a data image which contained only the first byte for a whole flash sector (i.e. NumBytes = (SectorSize * n) + 1) ), J-Flash SPI would ignore that single byte during production programming, neither programming nor verifying it. Fixed.
Version V7.66c (2022-06-15)
DLL
- After a connection to J-Link could not be established (e.g. invalid IP host name entered), any following connection attempt that failed would show the same error message "Failed to open DLL" Fixed.
- ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): AArch32: Accessing FPU registers Q0-Q15 always resulted in Q0 being accessed. Fixed.
- Infineon MB9BF121J: Flash programming did not work due to incorrect sectorization and incorrect flash algorithm. Fixed.
- ISSI IS25LP512M, IS25WP512M: SPIFI-Lib did not support EXTADD mode. Fixed.
- Maxim (Analog Devices) MAX32650: In case of the watchdog was enabled / used, flash programming could fail. Fixed.
- NXP LPC55S66: Internal flash memory size was incorrectly set to 320KB instead of 256KB. Fixed.
- Open flashloader: SEGGER_OPEN_Read function parameter "NumBytes" was always zero in turbo mode. Fixed.
- SWO: JLINK_SWO_EnableTarget() (affects e.g. SEGGER Ozone and SEGGER Embedded Studio): On SWO start, timestamps were not enabled properly if requested by caller. Fixed.
Firmware
- ARMv8-A/R firmware module V2 (e.g. Cortex-A53, Cortex-R52): AArch32: CPU register ELR_HYP could not be read/written. Fixed.
- ARMv8-A/R firmware module V2 (e.g. Cortex-A53, Cortex-R52): AArch32: FPU Q0-Q15 could not be read/written (incorrect instruction used for register access). Fixed.
- ARMv8-A/R firmware module V2 (e.g. Cortex-A53, Cortex-R52): AArch32: FPU registers FPEXC, FPSID, MVFR0, MVFR1, MVFR2 could not be read/written. Fixed.
- ARMv8-A/R firmware module V2 (e.g. Cortex-A53, Cortex-R52): AArch64: FPU registers FPEXC32_EL2, MVFR0_EL1, MVFR1_EL1, MVFR2_EL1 could not be read/written. Fixed.
- ARMv8-A/R firmware module V2 (e.g. Cortex-A53, Cortex-R52): If instruction execution via ITR failed in debug mode (e.g. when trying to read an FPU register while the FPU was disabled), control of core could be lost. Fixed.
- ARMv8-A/R firmware module V2 (e.g. Cortex-A53, Cortex-R52): Reading AArch32 32-bit registers via 64-bit ReadRegs API could return garbage for bits 63:32. Fixed.
- Flasher ARM V4: Flash algorithms (e.g. STM32L562) that required the total flash size to be passed by Flasher did not work properly in stand-alone mode. Fixed.
- Flasher PRO V4: Flash algorithms (e.g. STM32L562) that required the total flash size to be passed by Flasher did not work properly in stand-alone mode. Fixed.
- Flasher V5: GigaDevice GD32F1, GD32F2, GD32F3, GD32F4: Stand-alone-mode did not work. Fixed.
- J-Link EDU Mini V1: Update to ARMv8-A/R firmware module V2. Fixed.
- J-Link EDU/BASE/PLUS V11: Update to ARMv8-A/R firmware module V2. Fixed.
- J-Link OB RA4M2: Update to ARMv8-A/R firmware module V2. Fixed.
- J-Link PRO V5: Update to ARMv8-A/R firmware module V2. Fixed.
- J-Link ULTRA+ V5: Update to ARMv8-A/R firmware module V2. Fixed.
- J-Link WiFi V1: Update to ARMv8-A/R firmware module V2. Fixed.
- J-Link-OB-S124: Update to ARMv8-A/R firmware module V2. Fixed.
- J-Trace PRO V2 Cortex: Update to ARMv8-A/R firmware module V2. Fixed.
- J-Trace PRO V3 Cortex: Update to ARMv8-A/R firmware module V2. Fixed.
J-Flash
- For some ELF files (e.g. generated by GNU C99 7.2.1 toolchain) it could happen that after opening the file in J-Flash, some static data (i.e. '.data') was placed at its virtual address in RAM instead of its physical address in flash. This also caused programming operations to fail. Fixed.
J-Scope
- Under certain circumstances J-Scope could crash when drawing the graph. Fixed.
Version V7.66b (2022-05-30)
DLL
- Cortex-M ARMv8-M: Support for new CPU registers PAC_KEY_P_0-3, PAC_KEY_U_0-3, VPR did break flash programming for some ARMv8-M based MCUs (e.g. some Renesas RA series derivatives). Introduced in V7.66a. Fixed.
Version V7.66a (2022-05-19)
Configurator
- Emulator config dialog: If a product name did not fit into its field, the end of the string is now cut off instead of the start.
- Emulator config dialog: Increased width of the "product name" field so it can show most product names without them being cut off. Fixed.
DLL
- Cortex-M ARMv8-M: Added support for CPU registers PAC_KEY_P_0-3, PAC_KEY_U_0-3 (including secure / non-secure variants).
- Cortex-M85: Added support for CPU register VPR.
- Device selection dialog: On displays with high scaling or high pixel density, the initial size for this dialog was too small. Fixed.
- SiliconLabs EFR32xG21, EFR32xG22 device series: Flash operation on internal flash did not work after user data page had been programmed. Fixed.
GDB Server
- Config dialog: On displays with high scaling or high pixel density, the "command line option" field was too small. Fixed.
- Config dialog: On displays with high scaling or high pixel density, the fields for specifying USB serial number and IP hostname were too small. Fixed.
J-Flash
- New Project dialog: For some devices, some supported target interfaces were missing in the "Target interface" dropdown (i.e. SWD was missing for RISC-V devices). Fixed.
Version V7.66 (2022-05-18)
DLL
- Added J-Link OB CALLIOPE MINI V2.1 firmware.
- Added log information when a Reset via Reset pin is executed by the DLL during the generic connect sequence.
- Added support for new Cortex-M85 (ARMv8-M) core.
- Atmosic ATM333x device series: Added debug and flash programming support for ATM3330 and ATM3330e.
- GigaDevice GD32F303xB: Added debug and flash programming support (e.g. for "GD32F303CB").
- Infineon PSoC4: Updated device database to support most recent part numbers.
- Microchip ATSAMD21: Added RWW section (EEPROM) flash programming support.
- NXP LPC5514/16: Added new part numbers to the list of supported devices.
- NXP LPC55S14/S16: Added new part numbers to the list of supported devices.
- NXP PN76 device series: Added hidden debug & flash programming support for NXP PN7640.
- NXP RT1061x/RT1062x: Added debug & (QSPI) flash programming support for MIMXRT1061xxx5B, MIMXRT1062xxx5B and MIMXRT1062xxx6B.
- Silicon Labs BGM220S devices series: Added debug and flash programming support.
- Silicon Labs EFM32TG11B devices: Bootloader flash bank size was defined with 32KB, should be 18KB. Fixed.
- Silicon Labs EFR32xG14 devices: Bootloader flash bank size was defined with 16KB, should be 18KB. Fixed.
- TDK Micronas HVC5xxx device series: Added debug and flash programming support for HVC5221D, HVC5222C.
- TDK Micronas HVC5xxx device series: Halt after reset did not work properly. Fixed.
DLL Updater
- Added IAR EWRX as updatable IDE.
GDB Server
- Cortex-A32 (ARMv8-A): Added support for "monitor regs" command.
- Updated Zephyr RTOS plugin to latest source base.
J-Flash
- On displays with high scaling or high pixel density, icons of docked windows were displayed too small. Fixed.
- On displays with high scaling or high pixel density, the initial window size of J-Flash was too small. Fixed.
- When a data file that was open in J-Flash was modified outside of J-Flash (i.e. by another application), J-Flash did not prompt the user to reload the data. Fixed.
J-Flash SPI
- On displays with high scaling or high pixel density, icons of docked windows were displayed too small. Fixed.
- On displays with high scaling or high pixel density, the initial window size of J-Flash was too small. Fixed.
- When a data file that was open in J-Flash SPI was modified outside of J-Flash SPI (i.e. by another application), J-Flash SPI did not prompt the user to reload the data. Fixed.
J-Link Package
- Linux: The "Installed-Size" field for the .deb package was a floating point number, should be an integer to comply with debian docs. Fixed.
J-Scope
- Improved error message when data sampling could not be started.
- macOS: J-Scope would crash on project creation. Fixed.
- Options dialog would always show JTAG selected even if previously another interface was selected. Fixed.
Registration
- Added context menu for copying registration link to clipboard, as fallback if the "Register" button does not automatically open the browser.
Version V7.64e (2022-05-10)
DLL
- Infineon CYT4BFxxxB: Under certain circumstances, flash programming did not work. Fixed.
- NXP i.MXRT600 device series: With certain hardware configurations reset did not work properly. Fixed.
- NXP i.MXRTR101x device series: QSPI flash size was limited to 64 MB instead of 512 MB. Fixed.
- NXP i.MXRTR102x device series: QSPI flash size was limited to 64 MB instead of 512 MB. Fixed.
- NXP i.MXRTR105x device series: QSPI flash size was limited to 64 MB instead of 512 MB. Fixed.
- NXP i.MXRTR1064 device: QSPI flash size was limited to 64 MB instead of 256 MB. Fixed.
- NXP i.MXRTR106x device series: QSPI flash size was limited to 64 MB instead of 512 MB. Fixed.
- RAM was not preserved if RAM was changed between reset and the first flash download. Fixed.
- SiLabs EFR32xG24: Device specific reset did not work correctly. Fixed.
- ST STM32WB5x: Device was unnecessarily halted after connect. Fixed.
Firmware
- Flasher ARM V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
- Flasher Compact V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
- Flasher Portable PLUS V1: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
- Flasher Portable PLUS V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
- Flasher PRO V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
- Flasher PRO XL V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
J-Flash
- Qorvo QPGxxx: J-Flash rejected to download the config & data file. Fixed.
J-Scope
- Parsing volatile symbols could cause those symbols to be interpreted as a different type. Fixed.
Manual
- UM08001: Chapter "Target interfaces and adapters", Section "20-pin J-Link connector": Added sub-section "Pinout for QSPI"
Version V7.64d (2022-05-03)
DLL
- Microchip ATSAMC20 / ATSAMC21: Under special circumstances, flash programming could fail depending on the watchdog settings. Fixed.
- RaspberryPi RP2040: Updating the 2nd stage BTL located in the first flash sector could lead to unexpected issues (device does no longer boot due to invalid CRC) if the data file contained gaps. Fixed.
- RaspberryPi RP2040: When setting a breakpoint before calling the reset function (e.g. using IDEs), the reset did not work as expected. Fixed.
Firmware
- Flasher ARM V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- Flasher Compact V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- Flasher Portable PLUS V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- Flasher Portable PLUS V5: Some target interfaces used by universal flash loaders (e.g. STM8 SWIM, AVR PDI, ...) were reported as "not supported" by the firmware, by accident. Fixed.
- Flasher PRO V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- Flasher PRO XL V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link EDU Mini V1: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link EDU/BASE/PLUS V11: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link OB RA4M2-CortexM: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link OB RA4M2-Full: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link OB RA4M2-Renesas: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link OB RA4M2-RISCV: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link OB-K22-CortexA: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link OB-K22-CortexM: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link OB-K22-RISCV: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link PRO V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link ULTRA+ V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link WiFi V1: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Link-OB-S124: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Trace PRO V2 Cortex: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Trace PRO V2 CortexM: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Trace PRO V3 Cortex: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
- J-Trace PRO V3 CortexM: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
GDB Server
- Semi-hosting did not work for ARMv8-AR targets (e.g. Cortex-A32). Fixed.
J-Scope
- Options dialog: The project settings were not updated after pressing "OK". Introduced with V7.64c. Fixed.
Version V7.64c (2022-04-20)
DLL
- ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): Added CP15 register support via J-Link API.
- RTT: The control block was not identified as valid in case a buffer was configured in a different mode than SEGGER_RTT_MODE_NO_BLOCK_SKIP. Fixed.
J-Flash
- The merge command did not actually merge the datafiles (introduced V7.60). Fixed.
J-Scope
- After creating a new project (with 'HSS' for 'Sampling Source'), opening the ELF file for showing the symbol selection would sometimes fail. Fixed.
- After creating a new project and J-Scope failed to load the ELF file, J-Scope could hang indefinitely. Fixed.
- If one instance of J-Scope was running, opening a new instance in parallel would cause that instance to freeze. Fixed.
- Immediately after starting J-Scope, a rather large window could be seen flashing for a brief moment before disappearing. Fixed.
- Symbol selection: Members of a union could not be selected. Fixed.
- Symbol selection: The "Name" column for an anonymous (unnamed) struct or union was empty. Fixed.
Version V7.64b (2022-04-08)
Firmware
- Flasher ARM V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
- Flasher ARM V5: ASCII command interface: Commands with parameters (e.g,. "#FOPEN <File>") did not work properly. Introduced in V7.64 with fix for "SECUREAREA" command. Fixed.
- Flasher Compact V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
- Flasher Compact V5: ASCII command interface: Commands with parameters (e.g,. "#FOPEN <File>") did not work properly. Introduced in V7.64 with fix for "SECUREAREA" command. Fixed.
- Flasher Portable PLUS V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
- Flasher Portable PLUS V5: ASCII command interface: Commands with parameters (e.g,. "#FOPEN <File>") did not work properly. Introduced in V7.64 with fix for "SECUREAREA" command. Fixed.
- Flasher PRO V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
- Flasher PRO V5: ASCII command interface: Commands with parameters (e.g,. "#FOPEN <File>") did not work properly. Introduced in V7.64 with fix for "SECUREAREA" command. Fixed.
- Flasher PRO XL V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
- Flasher PRO XL V5: ASCII command interface: Commands with parameters (e.g,. "#FOPEN <File>") did not work properly. Introduced in V7.64 with fix for "SECUREAREA" command. Fixed.
Version V7.64a (2022-04-07)
DLL
- Microchip PIC32MZ: Under special circumstances, flash programming could fail (error while preparing target). Fixed.
- NXP iMX8ML: Under special circumstances, reset did not work as expected. Fixed.
- NXP iMX8MN: Under special circumstances, reset did not work as expected. Fixed.
- NXP iMXRT600 device series: QSPI-Flashloader did not work with correctly with SPI flashes that are only 3-byte addressable. Fixed.
- Setting/deactivating permanent powersupply did not work (introduced in V7.62). Fixed.
- SWO: Disconnecting the USB cable from the J-Link while SWO was running could cause a crash. Fixed.
Firmware
- Flasher ARM V4: Stand-alone mode: Flash programming of Cortex-M based MCUs that require CPU speed measurement feature (e.g. TI TM4C129 and ST STM32H7 series) failed on erase/program. Introduced in V7.22b. Fixed.
- Flasher PRO V4: Stand-alone mode: Flash programming of Cortex-M based MCUs that require CPU speed measurement feature (e.g. TI TM4C129 and ST STM32H7 series) failed on erase/program. Introduced in V7.22b. Fixed.
J-Run
- When using RTT, linebreaks were ignored. Fixed.
J-Scope
- Enumerated types were not handled correctly. Fixed.
- Nested structs were not selectable. Fixed.
Version V7.64 (2022-04-01)
Commander
- SWOStart ignored device specific SWO init. Fixed.
DLL
- Added "InheritFrom" attribute for "Device" tag in JLinkDevices.xml files. For more information: https://wiki.segger.com/Open_Flashloader#JLinkDevices.xml_Tags_and_Attributes
- Added debug support for Cortex-R7 core.
- Added Digi NS9210 and NS9215B series devices debug support.
- Added early warning watchdog check during internal flash programming for Microchip ATSAMD20 and ATSAMD21 series devices.
- Added more verbosity to logging for devices created/modified through *.xml files.
- Added SPI Flash programming support for Macronix MX66U1G45G within SPIFI-Lib.
- Added SPI Flash programming support for Macronix MX66U2G45G within SPIFI-Lib.
- Analog Devices ADuCM410, ADuCM412, ADuCM420: Added debug and flash programming support.
- Improved ECC RAM initialization speed for ST SR6P7G7x series device.
- Increased logging-verbosity for parsing of JLinkDevices.xml files.
- Modified conditions for early warning watchdog check during internal flash programming for Microchip ATSAMD20 and ATSAMD21 series devices.
- Nuvoton M0A21, M0A23: Added debug and flash programming support.
- ON Semiconductor: Added debug support for Ezario 3800 (https://wiki.segger.com/ONSemi_Ezairo_8300).
- Raspberry RP2040: Reset did not work properly. Fixed.
- RTT: Flags[31:24] of RTT buffer description are now reserved and must be zero for validity check.
- ST SR6P7G7x series devicers, RAM intialization speed improved during connect.
- ST STM32H723/33: SWO did not work out of the box. Fixed.
- ST STM32WB5x: When a Wireless Stack was already running on the device, another connect or power-cycle was required. Fixed.
Firmware
- Flasher ARM V5: ASCII command interface: #SECUREAREA command resulted in #SECURE command to be executed instead. Fixed.
- Flasher ARM V5: ASCII command interface: Added support for backspace character to delete / correct a pending command when typing (e.g. terminal application via RS232)
- Flasher ARM V5: Stand-alone mode: ONSemi RSL10 series: Programming did not work correctly because reset was not working properly (PC-based programming worked). Fixed.
- Flasher ARM V5: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- Flasher Compact V5: ASCII command interface: #SECUREAREA command resulted in #SECURE command to be executed instead. Fixed.
- Flasher Compact V5: ASCII command interface: Added support for backspace character to delete / correct a pending command when typing (e.g. terminal application via RS232)
- Flasher Compact V5: Stand-alone mode: ONSemi RSL10 series: Programming did not work correctly because reset was not working properly (PC-based programming worked). Fixed.
- Flasher Compact V5: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- Flasher Portable PLUS V5: Battery: Under special circumstances, the battery state was incorrect and always showed 100%. Fixed.
- Flasher Portable PLUS V5: Stand-alone mode: ONSemi RSL10 series: Programming did not work correctly because reset was not working properly (PC-based programming worked). Fixed.
- Flasher Portable PLUS V5: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- Flasher PRO V5: ASCII command interface: #SECUREAREA command resulted in #SECURE command to be executed instead. Fixed.
- Flasher PRO V5: ASCII command interface: Added support for backspace character to delete / correct a pending command when typing (e.g. terminal application via RS232)
- Flasher PRO V5: Stand-alone mode: ONSemi RSL10 series: Programming did not work correctly because reset was not working properly (PC-based programming worked). Fixed.
- Flasher PRO V5: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- Flasher PRO XL V5: ASCII command interface: #SECUREAREA command resulted in #SECURE command to be executed instead. Fixed.
- Flasher PRO XL V5: ASCII command interface: Added support for backspace character to delete / correct a pending command when typing (e.g. terminal application via RS232)
- Flasher PRO XL V5: Stand-alone mode: ONSemi RSL10 series: Programming did not work correctly because reset was not working properly (PC-based programming worked). Fixed.
- Flasher PRO XL V5: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- J-Link PRO V5: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- J-Link ULTRA+ V5: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- J-Trace PRO V2 Cortex: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- J-Trace PRO V2 CortexM: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- J-Trace PRO V3 Cortex: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
- J-Trace PRO V3 CortexM: TIF UART: Using TDO as Rx pin (e.g. as it is the case for SCI boot mode on Renesas RA series devices) accidentally modified the state of the TCK on the probe side. Fixed.
GDB Server
- GUI: Passing an invalid command line could cause J-Link GDB Server to crash. Fixed.
- Updated Zephyr RTOS plugin to latest source base.
- Windows: Added error code and message to log when loading a RTOS plugin failed.
J-Flash
- Added Flasher file dialog (File -> "Show files on Flasher...").
J-Flash SPI
- GUI: Added Flasher file dialog (File -> "Show files on Flasher...").
RTT Viewer
- Added "Find Bar" for finding occurrences of string inside a terminal. Find Bar can be opened via <Ctrl> + F (<Cmd> + F on macOS).
- Added an option to start the devices core, if it was halted after connect.
Version V7.62c (2022-03-22)
Configurator
- Log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
DLL
- Added new exec command "RISCV_SetHartSel=<HartIndex>" which can be used to set the "Hart" (core) to be used in multi-core
- Firmware update dialog log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
- HPMicro HPM67: Added support for the second core. For details, please refer to https://wiki.segger.com/HPMicro_HPM67#Dual_Core_Debugging.
- NXP MIMXRT106x: Under rare circumstances, a reset could cause the DLL to crash. Fixed.
- ONSemi RSL10 series devices sector erase of NVR flash banks can result in accidental loss of calibration data, instead use read modify write for NVR flash banks. Fixed.
- SiliconLabs EFR32xG21, EFR32xG23, EFR32xG24: Flash programming did not work properly. Fixed.
- ST STM32WB5x: FUS upgrade did not work for devices < 1MB. Fixed.
Firmware
- Flasher Compact V5: Universal flash loader: ST STM8 programming: If target MCU was running slow, flash programming did fail. Fixed.
- Flasher Compact V5: Universal flash loader: ST STM8 programming: SWIM target interface communication could lock up (power cycle of Flasher required) in case the target MCU did not respond with an ACK / NACK. Fixed.
- Flasher Portable PLUS V1: Introduction of countdown for the last 10 seconds before "auto power off on idle" caused progress bar for erase / program / verify to be cut off at the bottom. Introduced in V7.62b. Fixed.
- Flasher PRO V5: Universal flash loader: ST STM8 programming: If target MCU was running slow, flash programming did fail. Fixed.
- Flasher PRO V5: Universal flash loader: ST STM8 programming: SWIM target interface communication could lock up (power cycle of Flasher required) in case the target MCU did not respond with an ACK / NACK. Fixed.
- Flasher PRO XL V5: Universal flash loader: ST STM8 programming: If target MCU was running slow, flash programming did fail. Fixed.
- Flasher PRO XL V5: Universal flash loader: ST STM8 programming: SWIM target interface communication could lock up (power cycle of Flasher required) in case the target MCU did not respond with an ACK / NACK. Fixed.
- J-Trace PRO V2 Cortex: HSS: When using HSS at max. speed (sampling period == 0us) via IP, lots of gaps were seen in the timestamps because IP transmissions kept J-Trace busy too much. Fixed.
- J-Trace PRO V2 CortexM: HSS: When using HSS at max. speed (sampling period == 0us) via IP, lots of gaps were seen in the timestamps because IP transmissions kept J-Trace busy too much. Fixed.
- J-Trace PRO V3 Cortex: HSS: When using HSS at max. speed (sampling period == 0us) via IP, lots of gaps were seen in the timestamps because IP transmissions kept J-Trace busy too much. Fixed.
- J-Trace PRO V3 CortexM: HSS: When using HSS at max. speed (sampling period == 0us) via IP, lots of gaps were seen in the timestamps because IP transmissions kept J-Trace busy too much. Fixed.
- MCU-Link: Firmware did not set PIO0_14 (used as DBGIF_ISP0_CTRL on many eval boards) into GPIO mode correctly but left it in I2C mode (default after reset). This could interfere with pull-up / pull-down settings configured for that pin. Fixed.
GDB Server
- GUI Log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
J-Flash
- Data windows: Some icons were much smaller than the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
- Log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
- Project settings: When clicking "..." to select a target device, it could happen that the button was clicked multiple times while the selection dialog was loading. This caused mutliple device selection dialogs to open at once. Fixed.
J-Flash Lite
- Log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
J-Flash SPI
- Data windows: Some icons were much smaller than the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
- Log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
J-Mem
- Some icons were much smaller than the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
J-Scope
- Selecting target interface FINE lead to an error message stating BDM3 was selected. Fixed.
Registration
- Log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
Remote Server
- GUI Log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
RTT Viewer
- Terminals: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
SWO Viewer
- GUI Log: On some systems, the log font was much smaller than that of the rest of the GUI, depending on the configuration of the operating system's scaling and resolution. Fixed.
Version V7.62b (2022-03-08)
DLL
- Added debug and (QSPI) flash programming support for HPMicro HPM61 (https://wiki.segger.com/HPMicro_HPM61).
- Added debug and (QSPI) flash programming support for HPMicro HPM64 (https://wiki.segger.com/HPMicro_HPM64).
- Added debug and (QSPI) flash programming support for HPMicro HPM67 (https://wiki.segger.com/HPMicro_HPM67).
- NXP LPC55xx / LPC55sxx: In case of no valid application was located in flash, the CPU did not halt after reset. Fixed.
DLL Updater
- MPLAB X: The location of the DLL was not found for MPLAB X v6.00 and later. Fixed.
- Windows arm64: Embedded Studio was not detected by DLL Updater. Fixed.
Firmware
- Flasher ARM V5.1: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
- Flasher ARM V5: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
- Flasher Compact V5: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
- Flasher Portable PLUS V1: Battery mode: Countdown for the last 10 seconds before "auto power off on idle" is now shown on display.
- Flasher Portable PLUS V1: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
- Flasher Portable PLUS V1: Universal flash loader: Programming Renesas RX MCUs via UART protocol did not work properly (wrong number of STOP bits sent by Flasher). Fixed.
- Flasher PRO V5.1: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
- Flasher PRO V5: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
- J-Link EDU Mini V1: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Link EDU/BASE/PLUS V11: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Link OB-K22-CortexM: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Link OB-K22-CortexM: VCOM hardware flow control (HWFC): J-Link asserted RTS signal too late which could result in discard of data on J-Link side (at baudrates > 500 kHz). Fixed.
- J-Link PRO V5: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Link PRO V5: Webserver: Uptime on emulator status page was showing garbage. Fixed.
- J-Link ULTRA+ V5: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Link WiFi V1: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Link WiFi V1: The probe name was shown as "J-Link" and not as "J-Link WiFi" when connected via TCP/IP. Fixed.
- J-Trace PRO V2 Cortex: Connecting by nickname failed (Nickname feature was not supported by accident). Fixed.
- J-Trace PRO V2 Cortex: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Trace PRO V2 Cortex: Some probes had sporadic USB connection issues (especially at higher temperatures). Fixed.
- J-Trace PRO V2 Cortex: Webserver: Uptime on emulator status page was showing garbage. Fixed.
- J-Trace PRO V2 CortexM: Connecting by nickname failed (Nickname feature was not supported by accident). Fixed.
- J-Trace PRO V2 CortexM: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Trace PRO V2 CortexM: Some probes had sporadic USB connection issues (especially at higher temperatures). Fixed.
- J-Trace PRO V2 CortexM: Webserver: Uptime on emulator status page was showing garbage. Fixed.
- J-Trace PRO V3 Cortex: Connecting by nickname failed (Nickname feature was not supported by accident). Fixed.
- J-Trace PRO V3 Cortex: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Trace PRO V3 Cortex: Some probes had sporadic USB connection issues (especially at higher temperatures). Fixed.
- J-Trace PRO V3 Cortex: Webserver: Uptime on emulator status page was showing garbage. Fixed.
- J-Trace PRO V3 CortexM: Connecting by nickname failed (Nickname feature was not supported by accident). Fixed.
- J-Trace PRO V3 CortexM: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
- J-Trace PRO V3 CortexM: Some probes had sporadic USB connection issues (especially at higher temperatures). Fixed.
- J-Trace PRO V3 CortexM: Webserver: Uptime on emulator status page was showing garbage. Fixed.
J-Link Package
- Installer: The uninstaller (Uninstall.exe) was not signed, which could cause issues with anti-virus applications. Fixed.
Version V7.62a (2022-02-23)
DLL
- Infineon CY8C6xx, CYB06xx: Device name for Cortex-M0 core forwarded by Keil uVision was always mapped to Cortex-M4 core. Fixed.
- MacOS: If JLinkDevices folder did not exist, DLL printed "No such file or directory". Fixed.
- NXP MKE13Z, MKE14Z, MKE15Z, internal and EEPROM programming support. Fixed.
- NXP S32K344: Under special circumstances, the reset did not work as expected. Fixed.
- RTT: Possible crash when RTT buffers were not initialized correctly. Fixed.
Version V7.62 (2022-02-16)
Configurator
- Improved product names displayed in "Product" column.
- Some product names contained a redundant "SEGGER" at the start (e.g. "SEGGER J-Link ARM"). Fixed.
- Some product names contained multiple occurrences of firmware version (e.g. "J-Link V11 compiled <...> V11.00"). Fixed.
DLL
- Added debug support for Xilinx XA7Z010, XA7Z020, XQ7Z020 devices.
- Added native debug support for the Cortex-M4 core of the i.MX8M Mini.
- Added native debug support for the Cortex-M4 core of the i.MX8M.
- Added new ID for Adesto ATXP064B SPI Flash.
- Added SPI flash programming support for ST STM32U5 series devices.
- Added support for Macronix SPI flash MX25UW6345G.
- Analog Devices ADRF88xx: Added debug and flash programming support for Analog Devices ADRF88xx series devices.
- Analog Devices ADuCM43x: Core did not halt after reset. Fixed.
- Analog Devices ADuCM43x: Flashloader cache handling was not Inited/Uninited correctly. Fixed.
- ARMv8-AR: Added generic CFI complaint parallel NOR flash support.
- Cypress CYT2B and Cypress CYT4B: Added flash programming support for supervisory flash.
- HDSC HC32F460: Added debug & flash programming support for Huada Semiconductor HC32F460 series.
- HDSC HC32F460: Improved flash programming and erase speed.
- Improved error logging for instruction trace if issues with the host interface arise.
- Infineon Traveo II (CYT2B6): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
- Infineon Traveo II (CYT2B7): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
- Infineon Traveo II (CYT2B9): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
- Infineon Traveo II (CYT3BB): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
- Infineon Traveo II (CYT4BB): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
- Infineon Traveo II (CYT4BF): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
- J-Link DLL now looks for *.xml files in /AppData/Roaming/SEGGER/JLinkDevices/ and evaluates them as JLinkDevices.xml files. For more information: https://wiki.segger.com/Open_Flashloader#JLinkDevices_folder.
- NXP iMX8, iMX8M, iMX8M Mini: RAM location and size for M4 core was incorrect. Fixed.
- NXP LPC553x/LPC55S3x: On connect: CPU would always be reset, even when not required (attach). Fixed.
- NXP S32K3x2: Added debug & flash programming support for NXP S32K312, S32K322, S32K342 devices.
- Silicon Labs EFR32BG24: Added debug and flash programming support.
- Silicon Labs EFR32MG24: Added debug and flash programming support.
- SiliconLabs ExR32xG2x devices series: Added basic TrustZone support.
- ST STM32G0x0 and STM32G0x1: Size of option bytes flash bank and flash algorithm was incorrect. Fixed.
- ST STM32G0x0: Size of option bytes flash bank was incorrect. Fixed.
- ST STM32L5: Added flash programming support for secure flash bank.
- ST STM32WB15CC: Added debug and flash programming support.
- ST STM32WB30CE: Added debug and flash programming support.
- ST STM32WB50CG: Added debug and flash programming support.
- ST STM32WB5MMG: Added debug and flash programming support.
- XHSC HC32F460xC: Added debug & flash programming support for XHSC HC32F460xC devices.
Firmware
- Flasher ARM V5: Stand-alone mode: Batch programming: Parsing of config file (.CFG) aborted with error. Fixed.
- Flasher Compact V5: Stand-alone mode: Batch programming: Parsing of config file (.CFG) aborted with error. Fixed.
- Flasher package: Added J-Link commander to package.
- Flasher package: Added J-Link registration utility to package.
- Flasher package: Added JTAGLoad utility to package.
- Flasher PRO V5: Stand-alone mode: Batch programming: Parsing of config file (.CFG) aborted with error. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Batch programming: Parsing of config file (.CFG) aborted with error. Fixed.
GDB Server
- Added support for Cortex-A55.
J-Flash
- The blank check function checked up to 128 KB, only. For devices with more flash, blank check could return erroneously that the device is blank although data after the first 128 KB block were not blank. Fixed.
J-Flash SPI
- Added new ID for Adesto ATXP064B SPI Flash.
- Added support for Macronix SPI flash MX25UW6345G.
J-Scope
- In some cases(e.g. when using stdint.h types), J-Scope interpreted signed elements of an array as unsigned. Fixed.
- When opening a project with a changed ELF file, the GUI was not updated after reparsing. Fixed.
Manual
- UM08001: Chapter "Open Flashloader", Section "General procedure": Updated information regarding usage of JLinkDevices folder.
- UM08001: Chapter "Open Flashloader", Section "Information for Silicon Vendors": Updated information regarding usage of JLinkDevices folder.
Version V7.60h (2022-02-09)
DLL
- PTM Trace: Under certain circumstances exceptions could cause a wrong program flow analysis. Fixed.
- PTM Trace: Under certain circumstances indirect branches could cause a wrong program flow analysis. Fixed.
Firmware
- Flasher ARM V5: Stand-alone mode: Batch programming: AUTO command did not work properly. Fixed.
- Flasher ARM V5: Stand-alone mode: Batch programming: Batch configurations were not parsed correctly. Fixed.
- Flasher Compact V5: Stand-alone mode: Batch programming: AUTO command did not work properly. Fixed.
- Flasher Compact V5: Stand-alone mode: Batch programming: Batch configurations were not parsed correctly. Fixed.
- Flasher Compact V5: Universal flash loader: Improved performance for sparse data files (data files with many gaps in them).
- Flasher Compact V5: Universal flash loader: TIF_UART (e.g. ESP32): Improved performance (reduced gaps and length of gaps) of UART transmission.
- Flasher PRO V5: Stand-alone mode: Batch programming: AUTO command did not work properly. Fixed.
- Flasher PRO V5: Stand-alone mode: Batch programming: Batch configurations were not parsed correctly. Fixed.
- Flasher PRO V5: Universal flash loader: Improved performance for sparse data files (data files with many gaps in them).
- Flasher PRO V5: Universal flash loader: TIF_UART (e.g. ESP32): Improved performance (reduced gaps and length of gaps) of UART transmission.
- Flasher PRO XL V5: Stand-alone mode: Batch programming: AUTO command did not work properly. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Batch programming: Batch configurations were not parsed correctly. Fixed.
- Flasher PRO XL V5: Universal flash loader: Improved performance for sparse data files (data files with many gaps in them).
- Flasher PRO XL V5: Universal flash loader: TIF_UART (e.g. ESP32): Improved performance (reduced gaps and length of gaps) of UART transmission.
RTT Viewer
- Bright Theme: The "All Terminals" tab and the "Log" output did not adjust colors to fit the theme. Fixed.
Version V7.60g (2022-02-01)
Commander
- Command FWRITE: <Offset> parameter was applied to <EmuFile> only but not to <HostFile>. Fixed.
DLL
- J-Trace PRO V3 Cortex: If a USB write of multiple of 512 bytes (USB2) or multiple of 1024 (USB3) was issued by the J-Link software, the communication hung for 5 seconds and then a USB timeout was thrown. Fixed.
- J-Trace PRO V3 CortexM: If a USB write of multiple of 512 bytes (USB2) or multiple of 1024 (USB3) was issued by the J-Link software, the communication hung for 5 seconds and then a USB timeout was thrown. Fixed.
- Missing register mapping for IAPSR, EAPSR and IEPSR for ARMv8-M devices. Fixed.
- NXP iMX8: Under special circumstances, reset did not work (e.g. when using FreeRTOS based applications). Fixed.
- NXP iMXRT106x: Device was always halted after connect. Fixed.
- NXP Kinetis S32: user JTAG configuration was ignored. Fixed.
- SiliconLabs BGM210: Some device names were not recognized by the J-Link software. Fixed.
- SiliconLabs BGM210PB22: Added debug and flash programming support.
- SiliconLabs BGM210PB32: Added debug and flash programming support.
- SiliconLabs EFM32PG22C: Some device names were not recognized by the J-Link software. Fixed.
- SiliconLabs EFR32BG1: Some device names were not recognized by the J-Link software. Fixed.
- SiliconLabs EFR32FG1: Some device names were not recognized by the J-Link software. Fixed.
- SiliconLabs EFR32MG1: Some device names were not recognized by the J-Link software. Fixed.
- SiliconLabs EFR32MG2: Some device names were not recognized by the J-Link software. Fixed.
- SiliconLabs EZR32HG22: Some device names were not recognized by the J-Link software. Fixed.
- SiliconLabs EZR32HG32: Some device names were not recognized by the J-Link software. Fixed.
- Under special circumstances, incorrect behavior was executed on dialogs when pressing the escape button. Fixed.
J-Flash
- Fill Memory Area feature did not work correctly. Fixed.
Registration
- Allowed re-registration for already registered devices.
Version V7.60f (2022-01-25)
DLL
- NXP Kinetis K80: Under certain circumstances, QSPI flash programming did not work. Fixed.
- NXP S32K148: FlexNVM programming did not work due to incorrect sector size. Fixed.
- RISC-V: If the IDE / debugger created the disassembly window contents, warnings regarding "mis-aligned memory read accesses" could happen if compressed instructions were present in the code. Fixed.
Firmware
- Flasher ARM V5: Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
- Flasher Compact V5: Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
- Flasher Portable PLUS V1: Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
- Flasher PRO V5: Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
- J-Link OB SAM3U128 V2 NordicSemi: VCOM: Tx (OB -> target) output was delayed by 1 character. 1st character that was sent to target MCU after COM port open was garbage. Introduced in V7.58e. Fixed.
Version V7.60e (2022-01-20)
DLL
- ARMv8-A/R (e.g. Cortex-R52): AArch32: R14 / LR in Hypervisor mode was not read / written correctly and showed 0xAAAAAAAA all the time. Fixed.
- ST STM32G0B0xx series devices internal flash programming for second flash bank (starting @0x8040000) did not work. Fixed.
- ST STM32L5: Flash programming with TZEN = 1, RDP = 0 was not possible. Fixed.
Firmware
- Flasher Compact V5: Universal flash loader (e.g. Renesas RL78, TI MSP430, Espressif ESP32): Under special circumstances, UART failed because Flasher sent the same data twice. Fixed.
- Flasher PRO V5: Universal flash loader (e.g. Renesas RL78, TI MSP430, Espressif ESP32): Under special circumstances, UART failed because Flasher sent the same data twice. Fixed.
- Flasher PRO XL V5: Universal flash loader (e.g. Renesas RL78, TI MSP430, Espressif ESP32): Under special circumstances, UART failed because Flasher sent the same data twice. Fixed.
Version V7.60d (2022-01-17)
DLL
- Maxim MAX32660 series device, size of used SRAM for flash programming algo. Fixed.
- Microchip PIC32CX series devices, reset behavior for both cores was not correct. Fixed.
- Microchip PIC32CX: Connect to the second core did not work. Fixed.
- ST STM32F2xxx series devices second internal flash bank was not correctly named as option memory. Fixed.
- ST STM32G0: Improved unlock handling.
Firmware
- Flasher ARM V4: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
- Flasher ARM V5: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
- Flasher Compact V5: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
- Flasher PRO V4: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
- Flasher PRO V5: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
- J-Link-OB-S124: If bigger chunks of memory were read / written (>= 8 KB) the USB communication could break down and the OB has reset itself. Fixed.
J-Flash SPI
- After executing "Production programming" with F-RAM, any following operation (e.g. Production Programming, Erase, Program, Verify, ...) could crash J-Flash SPI. Fixed.
- When trying to program an SPI Flash with a Flash ID that is not part of J-Flash SPI's database (e.g. 0x00 0x00 0x00), J-Flash SPI could crash. Fixed.
J-Link Package
- Installer: Windows ARM64: Code signatures for installed .exe and .dll files were missing. Fixed.
- Installer: Windows ARM64: On some systems, after successfully installing the package, J-Link GUI applications crashed immediately after executing due to missing Visual C/C++ runtime DLLs. Fixed.
- Installer: Windows ARM64: The default destination directory was "Program Files (Arm)" instead of "Program Files". Fixed.
J-Scope
- J-Scope did not display boolean variables by their truth value. Fixed.
- J-Scope did not handle bool type symbols correctly. Fixed.
- Last column of symbol table was too wide. Fixed.
- The horizontal zoom levels for 20s/div and 50s/div were missing. Fixed.
- When assigning default colors to symbols, the seventh symbol would get an invalid color assigned. Fixed.
- With full sample buffer, J-Scope did wrongfully draw a line from the last sample to the first. Fixed.
Version V7.60c (2022-01-07)
DLL
- MediaTek MT7697 series devices QSPI flash programming support wrong flash base address. Fixed.
- NXP iMXRT101x: Under special circumstances, the device specific reset did not work properly. Fixed.
- NXP iMXRT102x: Under special circumstances, the device specific reset did not work properly. Fixed.
- NXP iMXRT106x: Under special circumstances, flash programming failed. Fixed.
- NXP iMXRT106x: Under special circumstances, the device specific reset did not work properly. Fixed.
- PIC32CX series devices second core RSTC_MR register was not correctly restored after core reset. Fixed.
- Under special circumstances, flash programming of external parallel CFI compliant NOR flashes could fail. Fixed.
- Verify command reported wrong mismatch address for CMSIS flash loaders. Fixed.
Version V7.60b (2021-12-22)
DLL
- Added option byte flash programming support for HSXP HK32F030Mxx series devices.
- GigaDevice GD32F4xx series devices, RAM size used by flashloader, fixed.
- Microchip PIC32CX series devices reset for second Cortex-M4, fixed.
- NXP iMXRT106x: The power down counter was not handled which could cause issues after ~16s during flash programming. Fixed.
- STM32F family: User JTAG chain selection was ignored. Fixed.
- STM32WB55 - FUS: Improved stability and terminal output.
Firmware
- Flasher ARM V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
- Flasher Compact V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
- Flasher Compact V5: Universal flash loader: Renesas RL78: Programming via half-duplex UART did not work properly. Fixed.
- Flasher Portable PLUS V1: PDI interface (AVR XMEGA) did not work. Fixed.
- Flasher PRO V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
- Flasher PRO V5: Universal flash loader: Renesas RL78: Programming via half-duplex UART did not work properly. Fixed.
- Flasher PRO XL V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
- Flasher PRO XL V5: Universal flash loader: Renesas RL78: Programming via half-duplex UART did not work properly. Fixed.
- J-Link PRO V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
- J-Link ULTRA+ V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
Release Notes
- Renamed "Flasher PRO-2GB V5" entries to "Flasher PRO XL V5" to match the official product name.
Version V7.60a (2021-12-16)
DLL
- Added debug and internal flash programming support for HSXP HK32F030Mxx series devices.
- Connect to some devices (e.g. CY8C6xx4_CM4) failed with error 'Algo error: Cannot find struct "FlashDevice"'. Introduced with V7.60. Fixed.
Firmware
- J-Link OB S124: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
Version V7.60 (2021-12-14)
Commander
- Added info about USB speed mode (full speed, high speed, ...) when connected via USB.
- In script mode, currently executed command was not output via stdout. Fixed.
Configurator
- Added setting to switch between WinUSB and SEGGER USB driver, if supported.
Control Panel
- Merged STRACE and LIVETRACE tabs.
- RTT Tab: Users can now switch between ASCII and hex view for all channels.
DLL
- Added debug & flash programming support for Qorvo QPG6105.
- Added debug and internal flash programming support for Microchip PIC32CX series devices.
- Added debug and internal flash programming support for Renesas RA6T2 series devices.
- Added debug and internal flash programming support for ST STM32WB10CC series devices.
- Added debug support for Microchip ATSAMA5D29 series devices.
- Added debug support for ST Stellar SR6P7G7x device DSPH and DME Cortex-M4 cores.
- Added debug support for ST Stellar SR6P7G7x device R52 cores.
- Added internal flash programming support for ST Stellar SR6P7G7x device cluster 0 R52_0 code flash.
- Added internal flash programming support for ST Stellar SR6P7G7x device EEPROM, UTEST flash and BCS flash.
- Added PID for Cortex-A72 devices.
- Added support for second Cortex-M4 core of Microchip PIC32CX series devices.
- ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Improved generic reset handling for devices where the generic reset does not reset the core only but also the debug logic.
- Hilscher NetX90 Com core added support for Reset via reset pin and reset via SYSRESETREQ.
- Hilscher NetX90 Com Core RAM base address for RAMCode was wrong. Fixed.
- Hilscher NetX90 Com core reset and halt after bootloader handling, fixed.
- Hilscher NetX90 Com core used software reset instead of reset pin toggling within reset routine. Fixed.
- Nordic Semiconductor nRF5340 (NET core): No reset was performed for the net core. Fixed.
- ONSemi RSL15 series devices sector erase of NVR flash banks can result in accidential loss of calibration data, instead use read modify write for NVR flash banks.
- Open flash loader: When using latest Embedded Studio (V5.68) to generate the flash loader, some flash loader entry points (Init(), UnInit(), ...) were not found. Fixed.
- Renesas RA: Added debug and flash programming support for RA2E2 family of devices.
- Trace on Cortex-M: Ozone: Sometimes, the sequence "Reset Download Reset StartTrace Go Halt" caused timestamps not to be output by target chip because ITM sync packets were not configured correctly. Fixed.
- Trace on Cortex-M: Ozone: Timeline was broken after first "halt + resume/go" request as J-Trace has reset the timestamp reference to 0. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V11: Windows: Added support for switching to WinUSB enumeration / driver mode. (BTL does not support WinUSB)
- J-Link PRO V5: Windows: Added support for switching to WinUSB enumeration / driver mode. (BTL does not support WinUSB)
- J-Link ULTRA+ V5: Windows: Added support for switching to WinUSB enumeration / driver mode. (BTL does not support WinUSB)
- J-Link WiFi V1: Windows: Added support for switching to WinUSB enumeration / driver mode. (BTL does not support WinUSB)
GDB Server
- Added AzureRTOS plugin.
- Log: Warnings and errors are now printed in color.
J-Flash
- Added shortcut "Alt+F10" for reading back selected sectors.
J-Link Package
- Installer: macOS: Added macOS universal installer.
- Installer: Windows: Added Windows ARM64 installer.
- Linux: Added multiple libraries as dependencies to the debian package that were missing before.
J-Run
- J-Run would crash when passing an ELF file generated by GCC 11.2. Fixed.
J-Scope
- J-Scope now checks if the ELF file has changed in the background and if that is the case, offers to reparse the ELF file.
Version V7.58e (2021-12-07)
Commander
- "loadbin" command: Downloads to RAM and unknown memory was not verified which could lead to undetected download errors. Fixed.
DLL
- Added support for command string "SetVerifyRAMDownload".
- Instruction trace default timestamp unexpectedly was changed to 64 cycles instead of 1024 as before when Ozone was used. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
- J-Link OB K22 NordicSemi: VCOM hardware flow control (HWFC): J-Link asserted RTS signal too late which could result in discard of data on J-Link side (at baud rates > 500 kHz). Fixed.
- J-Link OB SAM3U128 V2 NordicSemi: VCOM hardware flow control (HWFC): J-Link asserted RTS signal too late which could result in discard of data on J-Link side (at baud rates > 500 kHz). Fixed.
- J-Link PRO V5: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
- J-Link ULTRA+ V5: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
- J-Link WiFi V1: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
- J-Trace PRO Cortex V2: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
- J-Trace PRO Cortex V3: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
J-Scope
- J-Scope could freeze when adjusting Y-Resolution. Fixed.
Version V7.58d (2021-12-02)
DLL
- JTAG: If a malfunctioning JTAG device caused J-Link to detect 0 devices on the JTAG chain but a valid TotalIRLen, it could happen that an internal error was thrown: "JTAG: Buffer is full ... Problem in upper layer". Fixed.
- Renesas R7FS3A17C three internal flash banks (program flash, option-setting memory, data flash) were incorrectly displayed as one flash bank. Fixed.
Firmware
- Flasher Compact V5: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
- Flasher Compact V5: Universal flash loader: ST STM8: Programming via SWIM interface (ACK / NACK handling) did not work properly. Fixed.
- Flasher Portable PLUS V1: STM8 SWIM interface: Pull-up on STM8 SWIM adapter was not enabled correctly (via Pin17 of Flasher Portable PLUS) which could lead to communication errors. Fixed.
- Flasher Portable PLUS V1: Universal flash loader: STM8: Under very rare circumstances, connect/program/verify could fail because line state was sampled by Flasher too early. Fixed.
- Flasher Portable PLUS V1: Universal flash loader: When selecting an algorithm that uses HW UART as target interface, the Flasher firmware could hang. Fixed.
- Flasher PRO V5: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
- Flasher PRO V5: Universal flash loader: ST STM8: Programming via SWIM interface (ACK / NACK handling) did not work properly. Fixed.
- Flasher PRO XL V5: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
- Flasher PRO XL V5: Universal flash loader: ST STM8: Programming via SWIM interface (ACK / NACK handling) did not work properly. Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R (e.g. Cortex-A53), ARMv7-A/R (e.g. Cortex-A9), ARMv7-M (Cortex-M7): D-cache was not cleaned on Step/Go. Fixed.
- J-Link EDU/BASE/PLUS V11: VCOM: After closing a debug session, VCOM port became non-functional. Fixed.
- J-Link OB-S124: ARMv8-A/R (e.g. Cortex-A53), ARMv7-A/R (e.g. Cortex-A9), ARMv7-M (Cortex-M7): D-cache was not cleaned on Step/Go. Fixed.
- J-Link PRO V5: ARMv8-A/R (e.g. Cortex-A53), ARMv7-A/R (e.g. Cortex-A9), ARMv7-M (Cortex-M7): D-cache was not cleaned on Step/Go. Fixed.
- J-Link PRO V5: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
- J-Link ULTRA+ V5: ARMv8-A/R (e.g. Cortex-A53), ARMv7-A/R (e.g. Cortex-A9), ARMv7-M (Cortex-M7): D-cache was not cleaned on Step/Go. Fixed.
- J-Link ULTRA+ V5: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
- J-Link WiFi V1: ARMv8-A/R (e.g. Cortex-A53), ARMv7-A/R (e.g. Cortex-A9), ARMv7-M (Cortex-M7): D-cache was not cleaned on Step/Go. Fixed.
- J-Link WiFi V1: VCOM: After closing a debug session, VCOM port became non-functional. Fixed.
- J-Trace PRO Cortex V2: ARMv8-A/R (e.g. Cortex-A53), ARMv7-A/R (e.g. Cortex-A9), ARMv7-M (Cortex-M7): D-cache was not cleaned on Step/Go. Fixed.
- J-Trace PRO Cortex V3: ARMv8-A/R (e.g. Cortex-A53), ARMv7-A/R (e.g. Cortex-A9), ARMv7-M (Cortex-M7): D-cache was not cleaned on Step/Go. Fixed.
- J-Trace PRO V2 Cortex: HSS: Sampling speeds < 1kHz (period > 1ms) did not work properly. Fixed.
- J-Trace PRO V2 Cortex: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
- J-Trace PRO V2 CortexM: HSS: Sampling speeds < 1kHz (period > 1ms) did not work properly. Fixed.
- J-Trace PRO V2 CortexM: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
- J-Trace PRO V3 Cortex: HSS: Sampling speeds < 1kHz (period > 1ms) did not work properly. Fixed.
- J-Trace PRO V3 Cortex: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
- J-Trace PRO V3 CortexM: HSS: Sampling speeds < 1kHz (period > 1ms) did not work properly. Fixed.
- J-Trace PRO V3 CortexM: Under very rare circumstances, USB communication and firmware could lock up until power cycle due to an FPGA-internal synchronization problem. Fixed.
GDB Server
- FreeRTOS plugin: Stepping over a CreateTask() call before scheduler of FreeRTOS was started, could result in CPU not halting after step over operation. Fixed.
- FreeRTOS plugin: Task creation before scheduler start was not detected / handled properly. Fixed.
J-Scope
- Under certain circumstances, sample rate label in new project dialog was showing broken letter. Fixed.
Version V7.58c (2021-11-24)
Commander
- If ExitOnError was specified and the initial connection to the J-Link failed, the Commander did not close. Fixed.
- MacOS: Under some circumstances, the commander would close if an empty line was passed. Fixed.
DLL
- ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): ROM table scan: If ROM table entry had some bits in [11:2] set (which is allowed by spec.) component address was calculated incorrectly. Fixed.
- ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): ROM table scan: Some CoreSight SoC-600 components were not identified properly (TMC-ETS, ATBR, CATU, CSTF, HSSTP). Fixed.
- ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): ROM table scan: Some CoreSight SoC-600 components were not identified properly, textoutput. Fixed.
- Internal flash programming support for Microchip PIC32CX series devices. Fixed.
- NXP iMX8M: Under special circumstances, a debug session did not work as expected. Added a device specific reset. Fixed.
- Renesas R7FS3A7: Under special circumstances (no pullup on QSPI_IO2/ QSPIIO3), programming an external QSPI flash could fail. Fixed.
- Renesas R7FS7G2: Under special circumstances (no pullup on QSPI_IO2/ QSPIIO3), programming an external QSPI flash could fail. Fixed.
Firmware
- J-Link OB-K22-CortexA: Improved drag & drop flash programming support for target devices with erased value != 0xFF.
- J-Link OB-K22-CortexM: Improved drag & drop flash programming support for target devices with erased value != 0xFF.
- J-Link OB-K22-Qorvo: Improved drag & drop flash programming support for target devices with erased value != 0xFF.
GDB Server
- GUI: The configuration dialog had no option to enable "Generate logfile" before starting a GDB session. Fixed.
- GUI: The location of the generated logfile was not visible. Fixed.
- GUI: When starting a session with "Generate logfile" enabled, no logfile was generated. The logfile was only generated after toggling the checkbox. Fixed.
J-Scope
- Under certain circumstances opening the symbol selection dialog could cause a crash. Fixed.
Manual
- UM08022: Replaced occurrences of "J-Link mode" with "PC-based mode"
- UM08022: Replaced occurrences of "MSD mode" with "file access mode"
Version V7.58b (2021-11-16)
Configurator
- Show VCOM port drop down menu only in case J-Link has more than one VCOM available. Fixed.
DLL
- ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
- When a settings file (.jlink, used by IDEs) was accidentally edited by the user in such a way that it contained line endings other than \r\n (CR + LF), the file contents could get corrupted after ending a debug session. Fixed.
Firmware
- Flasher Compact V5: Renesas RX: Connecting to the MCU via JTAG could lead to a USB communication timeout on J-Link side. Introduced with V7.58. Fixed.
- Flasher PRO V5: Renesas RX: Connecting to the MCU via JTAG could lead to a USB communication timeout on J-Link side. Introduced with V7.58. Fixed.
- Flasher PRO XL V5: Renesas RX: Connecting to the MCU via JTAG could lead to a USB communication timeout on J-Link side. Introduced with V7.58. Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
- J-Link PRO V5: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
- J-Link PRO V5: Renesas RX: Connecting to the MCU via JTAG could lead to a USB communication timeout on J-Link side. Introduced with V7.58. Fixed.
- J-Link ULTRA+ V5: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
- J-Link ULTRA+ V5: Renesas RX: Connecting to the MCU via JTAG could lead to a USB communication timeout on J-Link side. Introduced with V7.58. Fixed.
- J-Link WiFi V1: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
- J-Trace PRO Cortex V2: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
- J-Trace PRO Cortex V3: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
J-Scope
- macOS: J-Scope would not properly launch. Fixed.
Version V7.58a (2021-11-11)
DLL
- J-Link Commander rreg and wreg command for 64bit CPUs. Fixed.
- ST STM32U5 device series: Extended support to include secure flash address.
Firmware
- Flasher ARM V5: RTT: Firmware reported built-in RTT support but did not support it in reality, so legacy host emulation mode did not work in RTTViewer etc. making RTT not usable at all. Fixed.
- Flasher PRO V5: RTT: Firmware reported built-in RTT support but did not support it in reality, so legacy host emulation mode did not work in RTTViewer etc. making RTT not usable at all. Fixed.
- Flasher PRO XL V5: RTT: Firmware reported built-in RTT support but did not support it in reality, so legacy host emulation mode did not work in RTTViewer etc. making RTT not usable at all. Fixed.
- J-Trace PRO V2 Cortex: Enable 5V target power did not work properly. Introduced in V7.58. Fixed.
- J-Trace PRO V2 Cortex: VTref was measured incorrectly so J-Trace generated HIGH levels on interface signals that were too high. Introduced in V7.58. Fixed.
- J-Trace PRO V2 CortexM: Enable 5V target power did not work properly. Introduced in V7.58. Fixed.
- J-Trace PRO V2 CortexM: VTref was measured incorrectly so J-Trace generated HIGH levels on interface signals that were too high. Introduced in V7.58. Fixed.
J-Scope
- Under certain circumstances, changing the options could cause crash. Fixed.
- When using RTT, trigger settings would not be used. Fixed.
Version V7.58 (2021-11-04)
Control Panel
- Breakpoints tab: Added commonly used default values.
DLL
- Added debug and flash programming support for NXP LPC802UK.
- Added debug and flash programming support for NXP LPC804UK.
- Added debug and flash programming support for NXP MK22FN128xxx12 series devices.
- Added debug and internal flash programming support for Microchip PIC32CMxxxx series devices.
- Added debug support for Microchip SAM7X7x series.
- Added debug support for NucleiSys N203 (RV32) device/core.
- Added debug support for NucleiSys N203E (RV32) device/core.
- Added debug support for NucleiSys N900 / N900MP (RV32) device/core.
- Added debug support for NucleiSys NX605 / NX607 / NX608 (RV64) device/core.
- Added debug support for NucleiSys NX900 / NX900MP (RV64) device/core.
- Added debug support for NucleiSys UX605 / UX607 / UX608 (RV64) device/core.
- Added debug support for NucleiSys UX900 / UX900MP (RV64) device/core.
- Added debug support for Renesas RZ/V2L series devices (e.g. "R9A07G054L_M33").
- Added flash programming support for RWW section of Microchip ATSAMHA0 and ATSAMHA1 series devices.
- Added flash programming support for RWW section of Microchip ATSAML22 series devices.
- Added flash programming support for RWW section of Microchip ATSAMR30 series devices.
- Added functionality for J-Link command string "SetSkipRestoreRAMCode".
- Added missing alias for SiLabs EFM32PG22CxxxF512 series device.
- Added OctoSPI flash programming support for STM32H7A3xx and STM32H7B3xx series devices.
- Added special A-Sync handling when tracing a Cypress/Infineon PSoC6 device, as some devices from these series could create an unknown package error. Fixed.
- Added support for the following Macronix SPI flashes MX25UW51245 to SPIFI-Lib.
- NXP MIMXRT11xx_M4: Added FlexSPI (Alias) region.
- Rasberry Pi RP2040: Added RTT search ranges.
- Renesas RA: Added debug and flash programming support for RA4E1 family of devices.
- Renesas RA: Added debug and flash programming support for RA6E1 family of devices.
- Silicon Labs EFM32PG23xxx: Added debug and flash programming support for EFM32PG23xxx family of devices.
- Silicon Labs EFR32FG23xxx: Added debug and flash programming support for EFR32FG23xxx family of devices.
- Silicon Labs EFR32ZG23xxx: Added debug and flash programming support for EFR32ZG23xxx family of devices.
- ST STM32G0 series: Improved remapping detection provided by boot configuration.
- When exec command DisableLTRACEAnalysis is used set, backtrace data can now be displayed by debug tools e.g. Ozone.
Firmware
- Flasher Compact V5: ESP32: Flash programming via UART could fail due to Tx data failure inside Flasher firmware. Fixed.
- Flasher PRO V5: ESP32: Flash programming via UART could fail due to Tx data failure inside Flasher firmware. Fixed.
- Flasher PRO XL V5: ESP32: Flash programming via UART could fail due to Tx data failure inside Flasher firmware. Fixed.
J-Flash SPI
- Added support for the following Macronix SPI flashes MX25UW25345G and MX25UW51245.
J-Link Package
- Linux: The .deb package did not name libsm6 as dependency. Fixed.
J-Scope
- Changed graph Y-Offset to be measured in divs, where one div equals 100px.
- Improved UI handling for graphs with a base line that is out of the visible area.
Manual
- UM08022: Added Logfile section and improved some chapters according to the feedback from the "Flasher Reader Test"
Version V7.56d (2021-10-29)
Commander
- Linux: Due to a bug introduced in 7.56c, the last character of console user input was cut off for some applications. Fixed.
DLL
- ARMv8-A/R (e.g. Cortex-A53): R31 which made it into API by accident, could return undefined values on read. Fixed. (Returns 0x0 now)
Firmware
- J-Trace PRO V2 Cortex: Fixed VTref feature did not work properly. Fixed.
- J-Trace PRO V2 CortexM: Fixed VTref feature did not work properly. Fixed.
Version V7.56c (2021-10-28)
Commander
- All Platforms: CTRL + C was not handled correctly. Fixed.
- Users were not notified that a power-cycle is required after changing VTref from fixed to not fixed. Fixed.
Control Panel
- Commander tab: Browser autofill feature could interfere with Arrowkey functionality. Fixed.
DLL
- Debugging via cJTAG did not work on NucleiSys RV32 cores (N1xx, N2xx, N3xx, N6xx, ...). Fixed.
- Debugging via cJTAG did not work on NucleiSys RV64 cores (NX6xx, UX6xx, ...). Fixed.
- Debugging via cJTAG did not work on SiFive E3, E7 series cores. Fixed.
- Debugging via cJTAG did not work on SiFive S2, S3, S5, S7 series cores. Fixed.
- NXP S32K344: Connection via JTAG as target interface did not work. Fixed.
- NXP S32K344: Erasing the data flash did not work on recent silicon revisions. Fixed.
- PLL init for STM32H7A3xx and STM32H7B3xx for internal flash programming. Fixed.
- SiliconLabs EFM32GG12 series devices size of bootloader flash memory. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V11: Cortex-M: Improved memory read speed for SWD interface by up to 20%. (20% for SWD frequencies > 10 MHz).
- J-Link PRO V5: Cortex-M: Improved memory read speed for SWD interface by up to 20%. (20% for SWD frequencies > 10 MHz).
- J-Link ULTRA+ V5: Cortex-M: Improved memory read speed for SWD interface by up to 20%. (20% for SWD frequencies > 10 MHz).
- J-Link WiFi V1: Cortex-M: Improved memory read speed for SWD interface by up to 20%. (20% for SWD frequencies > 10 MHz).
J-Scope
- "Decrease Y-Resolution" action did not always decrease with the correct step size. Fixed.
- Added option to directly edit Y-Offset of symbols by double clicking the corresponding Y-Offset cell.
- Added progress bar for elf parsing process.
- Adding new symbols after completely emptying the list of active symbols did not work. Fixed.
- Changing the ELF file or HSS/RTT mode through the options did not work. Fixed.
- Graph tooltip was shown even when J-Scope was not the active window. Fixed.
- Improved speed of symbol selection dialog initialization.
- In RTT mode it was possible to remove active symbols from the symbol table. Fixed.
- In some cases, restarting read could lead to crash. Fixed.
- It was possible to loose the visibility of the graph when zooming into an area without data. Fixed.
- The main window was placed wrong when using multi-monitor setups. Fixed.
- Under certain circumstances opening a project could cause a crash. Fixed.
- Under certain circumstances parsing of an elf file could fail. Fixed.
- Zooming in did not cause autoscroll to turn off when it should. Fixed.
- Zooming in when in Autoscroll mode caused the first graph to be misaligned. Fixed.
Version V7.56b (2021-10-18)
Commander
- TestRSpeed: When the target was halted, the measured read speeds were wrong. Fixed.
Configurator
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
DLL
- Firmware update dialog: It could happen that the very last line of text inside the log was cut off vertically. Fixed.
- J-Link Commander erase + address range command flash bank size calculation. Fixed.
- Renesas RA6M4: QSPI flash banks were configured as "always present" which could cause issues during erase for hardware without QSPI flash. Fixed.
- Renesas RA6M5: QSPI flash banks were configured as "always present" which could cause issues during erase for hardware without QSPI flash. Fixed.
- Silabs EFM32GG11 series and EFM32TG11 series devices internal flash programming, check for page-aligned programming. Fixed.
DLL Updater
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
Firmware
- J-Link OB-K22-CortexA: Added pin override function for TCK, TMS, TDI, TDO, NRESET, TRST, Pin17 and RTCK.
- J-Link OB-K22-CortexA: Increased the max. supported baud-rate of VCOM0 and VCOM1 from 1 Mbps to 2 Mbps.
- J-Link OB-K22-CortexM: Added pin override function for TCK, TMS, TDI, TDO, NRESET, TRST, Pin17 and RTCK.
- J-Link OB-K22-CortexM: Increased the max. supported baud-rate of VCOM0 and VCOM1 from 1 Mbps to 2 Mbps.
- J-Link OB-K22-RISCV: Added pin override function for TCK, TMS, TDI, TDO, NRESET, TRST, Pin17 and RTCK.
- J-Link OB-K22-RISCV: Increased the max. supported baud-rate of VCOM0 and VCOM1 from 1 Mbps to 2 Mbps.
- J-Link PRO V5: Under special circumstances, a USB communication timeout could occur during a debug session. Fixed.
- J-Link ULTRA+ V5: Under special circumstances, a USB communication timeout could occur during a debug session. Fixed.
GDB Server
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
J-Flash Lite
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
J-Flash SPI
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
J-Mem
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
J-Scope
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
- Loading ELF-file could cause crash. Fixed.
License Manager
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
Registration
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
Remote Server
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
RTT
- The SEGGER RTT Control block was not zero initialized separately, which could cause issues when not linked to a zero initialized RAM section. Fixed.
RTT Viewer
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
SWO Viewer
- It could happen that the very last line of text inside the log was cut off vertically. Fixed.
Version V7.56a (2021-10-11)
DLL Updater
- A misleading error message was shown in case a mandatory file used to update an application was missing. Fixed.
J-Scope
- Parsing ELF files with arrays of size zero would cause crash. Fixed.
- Symbol view table was not always correctly updated when adding active symbols. Fixed.
Remote Server
- JLINK_PIN_Override API calls did not work correctly (communication errors were thrown). Fixed.
- JLINK_TIF_UART API calls did not work correctly (communication errors were thrown). Fixed.
Version V7.56 (2021-10-07)
CCS Plugin
- Added Cortex-A9 support.
Commander
- If a J-Link Script file was specified, it would be ignored before connecting to J-Link, so functions like InitEMU() were not called. Fixed.
Configurator
- Removed an obsolete trailing space in the hyperlink inside the "Check segger.com" text for the host firmware column for a Flasher ATE.
Control Panel
- Added Watchpoint functionality (Set/Remove) to the "Breakpoints" tab.
- Changed appearance of the active menu tab to white font on black background.
- Settings: Added link to SEGGER Wiki for explanation of L1 Verify and L2 Verify.
- Settings: Added section "Application download"
- Settings: Moved settings for "L1 Verify" and "L2 Verify" from "Flash download" to "Application download"
DLL
- Added additoinal aliases for Atmel ATSAMA5 series devices.
- Added debug & flash programming support for Qorvo QPG5072 series.
- Added debug and flash programming support for Infineon CYPM1311 series devices.
- Added debug and flash programming support for TI CC2652RB series device.
- Added debug and internal flash programming support for Maxim MAX32675 series device.
- Added support for the following Macronix SPI flashes MX25LW51245, MX25UW12345G, MX25UW25345G to SPIFI-Lib.
- Added support for the following Windbond SPI flashes W25Q32JW, W25Q64JW, W25Q128JW, W25Q256JW, W25Q512NW, W25Q01NW, W25Q01JV to SPIFI-Lib.
- Changed default for verify of application downloads to RAM to "disabled" because most IDEs do it on their own automatically, so a double verify only costs time.
- Disabling L1 Verify now also prevents readback when downloading into RAM.
- Improved erase and programming speed of Nuvoton M031/M032 series devices.
- NXP iMXRT106x: For some devices (e.g. "MIMXRT106A-ALEXA", "MIMXRT106SDVL6A", ...), QSPI flash programming did not work as "fall back" (HyperFlashloader disabled). Fixed. (https://wiki.segger.com/i.MXRT1060)
- NXP S32K144: Improved the device specific connect to output a proper error message in case of a protected device has been detected with "mass erase disabled".
- Renesas RA4M2: Added a new device alias per device with a "_RAMLess" prefix (e.g. "R7FA4M2AF_RAMLess") which uses a "RAMLess" method to program the flash by default. This is required for scenarios where the flash cannot be programmed via RAMCode (e.g. DLM state == NSECSD)
- Renesas RA4M2: Enabled RAMCode based algorithm by default.
- Renesas RA4M2: Option byte programming did not work under certain circumstances. Fixed.
- Renesas RA6M4: Added a new device alias per device with a "_RAMLess" prefix (e.g. "R7FA4M2AF_RAMLess") which uses a "RAMLess" method to program the flash by default. This is required for scenarios where the flash cannot be programmed via RAMCode (e.g. DLM state == NSECSD)
- Renesas RA6M4: Enabled RAMCode based algorithm by default.
- Renesas RA6M5: Added a new device alias per device with a "_RAMLess" prefix (e.g. "R7FA4M2AF_RAMLess") which uses a "RAMLess" method to program the flash by default. This is required for scenarios where the flash cannot be programmed via RAMCode (e.g. DLM state == NSECSD)
- Renesas RA6M5: Enabled RAMCode based algorithm by default.
- ST STM32G0x1 series devices base address for second internal flash bank. Fixed.
Firmware
- Flasher Compact V5: ASCII command interface could hang on certain commands like "#BAUDRATE" and "#FLIST". Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-AR (e.g. Cortex-A53): Improved download speed into target memory by up to factor 4 (e.g. @ 25 MHz SWD 310 KB/s -> 1140 KB/s).
- J-Link OB-K22-Qorvo: Added support for new J-Link OB.
- J-Link PRO V5: ARMv8-AR (e.g. Cortex-A53): Improved download speed into target memory by up to factor 4 (e.g. @ 25 MHz SWD 310 KB/s -> 1140 KB/s).
- J-Link PRO V5: cJTAG: Increased max. communication speed: 16 MHz -> 33 MHz.
- J-Link PRO V5: Download speed: Regression was introduced in V7.54c which slowed down download speeds when using higher JTAG/SWD speeds. Fixed.
- J-Link PRO V5: ICSP PIC32: Increased max. communication speed: 16 MHz -> 33 MHz.
- J-Link PRO V5: VCOM: Added support for odd/even parity.
- J-Link ULTRA+ V5: ARMv8-AR (e.g. Cortex-A53): Improved download speed into target memory by up to factor 4 (e.g. @ 25 MHz SWD 310 KB/s -> 1140 KB/s).
- J-Link ULTRA+ V5: cJTAG: Increased max. communication speed: 16 MHz -> 33 MHz.
- J-Link ULTRA+ V5: Download speed: Regression was introduced in V7.54c which slowed down download speeds when using higher JTAG/SWD speeds. Fixed.
- J-Link ULTRA+ V5: ICSP PIC32: Increased max. communication speed: 16 MHz -> 33 MHz.
- J-Link ULTRA+ V5: VCOM: Added support for odd/even parity.
- J-Link WiFi V1: ARMv8-AR (e.g. Cortex-A53): Improved download speed into target memory by up to factor 4 (e.g. @ 25 MHz SWD 310 KB/s -> 1140 KB/s).
- J-Trace PRO Cortex V2: ARMv8-AR (e.g. Cortex-A53): Improved download speed into target memory by up to factor 4 (e.g. @ 25 MHz SWD 310 KB/s -> 1140 KB/s).
- MCU-Link: Changed the state of some unused pins (pull to no pull resistor etc) as requested by NXP.
- MCU-Link: VCOM: 1st character received by MCU-Link and forwarded to terminal application could get lost. Fixed.
GDB Server
- Mac M1: Connecting to some devices did not work. Fixed.
J-Flash SPI
- Added StatusRegFormat parameter to Flash settings.
- Added support for the following Macronix SPI flashes MX25LW51245 and MX25UW12345G.
- Added support for the following Windbond SPI flashes W25Q32JW, W25Q64JW, W25Q128JW, W25Q256JW, W25Q512NW, W25Q01NW and W25Q01JV.
- Possible crash when erasing sectors but the connect failed. Fixed.
- Windows: 64-bit build did crash under certain circumstances when saving configs to Flasher. Fixed.
J-Scope
- Searching symbols in symbol selection dialog caused crash. Fixed.
- Under certain circumstances, parsing ELF file could cause a crash. Fixed.
RTT Logger
- All Platforms: CTRL + C was not handled correctly. Fixed.
Version V7.54d (2021-09-28)
DLL
- Microchip ATSAMA5D2x Family: Some device names were not detected by the J-Link software (e.g. "ATSAMA5D27CLD2G"). Fixed.
- STM32U585QE and STM32U585ZE device descriptions passed to DLL by KEIL uVision were recognized as "unknown" device. Fixed.
DLL Updater
- 64-bit version: Updating the J-Link DLL for Microchip MPLAB X failed. Fixed.
Firmware
- Flasher Portable PLUS V1: Stand-alone mode: Direct SPI flash programming: Erase/Program/Verify progress bar was not updated properly. Fixed.
- J-Link EDU Mini V1: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
- J-Link PRO V4: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
- J-Link PRO V5: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
- J-Link ULTRA+ V4: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
- J-Link ULTRA+ V5: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
- J-Link WiFi V1: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
- J-Link-OB-K22-RISCV: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
J-Flash SPI
- Errors due to missing licenses are now always printed to log regardless of the configured log level.
J-Flash SPI CL
- All log messages (stdout output) were missing, regardless of the configured log level. Introduced with V7.22a. Fixed.
- Errors due to missing licenses are now always printed to log (and stdout) regardless of the configured log level.
Version V7.54c (2021-09-20)
DLL
- Cortex-M (ARMv6-M / 7-M / 8-M: When single stepping, the instruction BLX LR was not simulated correctly (jumped to wrong destination address). Fixed.
- STM32L5 series devices: Sector erase was not working correctly. Fixed.
Firmware
- J-Link PRO V5: cJTAG: Selecting a cJTAG speed resulted in a lower speed being used (e.g. 12 MHz selected -> 9 MHz used). Fixed.
- J-Link ULTRA+ V5: cJTAG: Selecting a cJTAG speed resulted in a lower speed being used (e.g. 12 MHz selected -> 9 MHz used). Fixed.
J-Scope
- Added J-Scope user guide to "Help" menu.
- Added option to select symbol from struct arrays.
- Improved performance of graph drawing.
- Zoom buttons were not set to active when opening a project. Fixed.
Version V7.54b (2021-09-14)
Commander
- Calling "erase" command with wrong parameter resulted in chip erase was triggered. Fixed.
DLL
- NXP iMXRT101x devices: Added device specific reset behavior.
- NXP K32L2 series: Implemented RAM-ranges were not correct. Fixed.
- NXP LPC55S0x/LPC550x series: Flash sizes were not correct for the variants with < 256KB internal flash. Fixed.
- NXP LPC55xx family: Incorrect flash size was used for some 64 KB and 128 KB flash devices. Fixed.
- NXP LPC55xx family: Some non existing device names were displayed. Corrected.
- NXP LPC55xx family: The secure flash region was enabled for some devices without TrustZone feature. Fixed.
- NXP LPC55xx family: The secure flash region was not enabled for the LPC55S36. Fixed.
Firmware
- Flasher ARM V5: O2Micro OZ935xx: Flash programming did not work in stand-alone mode. Fixed.
- Flasher Portable PLUS V1: O2Micro OZ935xx: Flash programming did not work in stand-alone mode. Fixed.
- Flasher PRO V5: O2Micro OZ935xx: Flash programming did not work in stand-alone mode. Fixed.
J-Scope
- Array base type and base type size were not correctly read from .elf file. Fixed.
- It was not possible to read float/double symbols. Fixed.
- J-Scope did not save project files correctly. Fixed.
- Trigger selection and symbol view table were not always correctly updated when removing/adding active symbols. Fixed.
Version V7.54a (2021-09-07)
Configurator
- If a Flasher ATE Mainboard was listed in a table and was moved to a different row, the host firmware text "Check segger.com" stayed in the old row, causing text overlaps. Fixed.
- IP settings of a probe could not be changed via IP, only when connecting the probe via USB. Fixed.
- The "Check segger.com" text in the host firmware column for a Flasher ATE was not aligned with the text for other rows. Fixed.
- When a configuration could not be applied (e.g. because the desired probe/ programmer was not connected), no message box was shown. Fixed.
DLL
- ARMv8-AR (e.g. Cortex-A53): When listing processor features, EL2 support was listed twice instead of EL2 and EL3 support. Fixed.
- CoreSight SoC-600: Having a Cortex-M3/M4 with ETB, the ETB was not correctly detected in the ROM table. Fixed.
- Multiple Nuvoton device descriptions passed to DLL by IAR EWARM were recognized as "unknown" device. Fixed.
- Multiple Nuvoton device descriptions passed to DLL by KEIL uVision were recognized as "unknown" device. Fixed.
Firmware
- Flasher ARM V5: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- Flasher PRO V5: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- Flasher PRO XL V5: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- J-Link EDU/BASE/PLUS V11: Under very special circumstances, debug connection could be unstable and throw timeout errors etc. Introduced in V7.52b. Fixed.
- J-Link PRO V4: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- J-Link PRO V5: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- J-Link WiFi V1: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- J-Trace PRO V2 Cortex: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- J-Trace PRO V2 CortexM: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- J-Trace PRO V3 Cortex: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
- J-Trace PRO V3 CortexM: Changing IP settings while connected to J-Link via IP lead to connection loss. Fixed. (Settings are now updated as soon as J-Link becomes idle and there are no more connections to it.)
Version V7.54 (2021-09-01)
Commander
- "?" Command: Long and short names are now all printed in CamelCase.
- A visual bug could occur when using the "?" command. Fixed.
- Added "ClearWP" as long command for "ClrWP".
- Added function WJTAGIR and WJTAGDR which extend & replace functions WJC and WJR.
- Added long names for some commands that only had short names.
- ARMv8-M (Cortex-M23, Cortex-M33, ...): Added MSPLIM and PSPLIM to the registers that are shown on halt().
- Expended functionality of the command "?". "? [<Command>]" now shows additional information about <Command> if passed.
- Improved description of "?" command.
- Improved documentation of available commands shown with "?".
- Obsolete/deprecated commands are not shown "?" anymore.
- Rearranged display of commands when "?" command is called to be in a more logical order.
DLL
- 64Bit DLL Updater did not find MPLAB-X. Fixed.
- Added debug & flash programming support for TI CC1312R7 and CC1352P7 series.
- Added debug & flash programming support for TI CC2652R7 and CC2652P7 series.
- Added debug and flash programming support for Infineon CYPM1011 series devices.
- Added debug and flash programming support for not yet listed ST STM32G061 devices.
- Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- Added exec command DisableLTRACEAnalysis.
- Added flash programming and debug support for NXP LPC553x/LPC55S3x devices.
- Added native trace buffer support for single core ST STM32H7 series.
- Added part numbers as additoinal aliases for Infineon PMG1 series devices.
- Added SPI Flash support in SPIFI-Lib for Adesto AT25FF081A, AT25FF161A and AT25XE161D series devices.
- Added SPI Flash support in SPIFI-Lib for GigaDevice GD25Q257D series devices.
- Cypress CYT2Bxxxx and CYT4BFxxx series devices Reset for Coretx-M4 and Cortex-M7. Fixed.
- Generic SWO init uses devices ROM Table TPIU address now where available.
- GigaDevice GD25B512ME serial flash added programming support within SPIFI-Lib.
- GigaDevice GD25LQ256D serial flash enter exit 4 byte address mode, fixed.
- iMXRT10xx devices: Improved reset behavior.
- Infineon CYPM1011 series devices init sequence after restoring VTref configuration. Fixed.
- Multi-byte units will be displayed without "i" again. (KiB, MiB, GiB,... => KB, MB, GB,...).
- Multiple Nuvoton device descriptions passed to DLL by IAR EWARM were recognized as "unknown" device. Fixed.
- Multiple Nuvoton device descriptions passed to DLL by KEIL uVision were recognized as "unknown" device. Fixed.
- NXP iMXRT117x devices: Flashloader did not save and restore all used registers. Fixed.
- NXP LPC5411x series devices internal flash programming. Fixed.
- Replaced occurrences of multi-byte unit "KiB" with "KB" according to SEGGER's new naming convention: https://wiki.segger.com/SEGGER_standard_for_units_of_Memory_size
- ST STM32G0: When the devices was read and write protected, the unlock dialog was shown twice. Fixed.
- ST STM32H7Axx / STM32H7Bxx series devices issues with voltage scaling (VOS) and flash latency settings for flash programming. Fixed.
- Suppress continues verbose output when calling J-Link ScriptFile function "HandleBeforeMemAccessWrite".
- Tested and verified flash programming support of Winbond W25Q128JV with QSPI based flash algorithms.
Firmware
- Flasher ARM V5: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
- Flasher ARM V5: Stand-alone mode: Added support for Cortex-A/R (ARMv7) based devices. (E.g. Xilinx Zynq-7000 series)
- Flasher Compact V5: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
- Flasher Compact V5: Universal flash loader: Under special circumstances, Erase() could hang if flash bank started at addr 0x0. Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
- Flasher Portable PLUS V1: Stand-alone mode: Added support for Cortex-A/R (ARMv7) based devices. (E.g. Xilinx Zynq-7000 series)
- Flasher Portable PLUS V1: Universal flash loader: Under special circumstances, Erase() could hang if flash bank started at addr 0x0. Fixed.
- Flasher PRO V5: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
- Flasher PRO V5: Stand-alone mode: Added support for Cortex-A/R (ARMv7) based devices. (E.g. Xilinx Zynq-7000 series)
- Flasher PRO V5: Universal flash loader: Under special circumstances, Erase() could hang if flash bank started at addr 0x0. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
- Flasher PRO XL V5: Stand-alone mode: Added support for Cortex-A/R (ARMv7) based devices. (E.g. Xilinx Zynq-7000 series)
- Flasher PRO XL V5: Universal flash loader: Under special circumstances, Erase() could hang if flash bank started at addr 0x0. Fixed.
- J-Link OB-K22-CortexA: Added support for cJTAG target interface.
- J-Link OB-K22-CortexM: Added support for cJTAG target interface.
- J-Link OB-K22-RISCV: Added support for cJTAG target interface.
J-Flash
- Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
- When trying to program a device added via Open Flash Loader, J-Flash could crash if a mandatory algo function (e.g. UnInit) was not implemented. Fixed.
J-Flash SPI
- Added SPI Flash support for Adesto AT25FF081A, AT25FF161A and AT25XE161D series devices.
- Added SPI Flash support for GigaDevice GD25Q257D series devices.
- GigaDevice GD25B512ME serial flash added programming support.
- GigaDevice GD25LQ256D serial flash enter exit 4 byte address mode, fixed.
J-Link Package
- Multi-byte units will be displayed without "i" again. (KiB, MiB, GiB,... => KB, MB, GB,...).
- Replaced occurrences of multi-byte unit "KiB" with "KB" according to SEGGER's new naming convention: https://wiki.segger.com/SEGGER_standard_for_units_of_Memory_size
J-Scope
- Added arrow key left/right as shortcuts to move the graph to the left/right.
- Added key "End" as shortcut to move the graph to the end.
- Added key "Home" as shortcut to move the graph to the start.
- Crash when using RTT mode. Fixed.
- Improved usability on displays with scaling factor differing from 100%.
- It was possible to use invalid characters for the symbol selection of arrays. Fixed.
- Using the arrow up/down shortcuts to change the zoom level was no longer possible after the symbol table was focused. Fixed.
- When drawing points, the color of the points did not match the selected color. Fixed.
RTT Logger
- The names and indexes of all available buffers are now also printed on connect.
Version V7.52d (2021-08-17)
Commander
- "loadfile" command: When loading Intel HEX files that contain both "extended segment address record" and "extended linear address record" types (very very rare), it could happen that wrong addresses where computed. Fixed.
- Linux: Interactive command prompt (via shared libedit) did not work under some Debian-based distributions. Fixed.
DLL
- ARMv8-M baseline (e.g. Cortex-M23): MSPLIM and PSPLIM were always read as 0 / writes were ignored. Fixed.
- ARMv8-M mainline (e.g. Cortex-M33) without security extensions (e.g. ST STM32L5 series): MSPLIM and PSPLIM were always read as 0 / writes were ignored. Fixed.
- Flash programming SPIFI algorithm for Telink TLSR9518xxx series devices, fixed.
- GigaDevice GD32F1xx series devices internal flash programming sector size. Fixed.
- NXP iMXRT102x: RAM debugging did not work when no valid image was present in the external memory. Fixed.
- ST STM32H7Axx and STM32H7Bxx series devices changed RAM address to DTCM RAM for flashalgos. Fixed.
- Under certain circumstances when tracing multiple stacked exception calls, trace analysis might be incorrect. Fixed for both live and buffered trace.
Firmware
- Flasher Portable PLUS V1: Firmware crashed when using cJTAG as target interface. Fixed.
J-Flash
- License dialog did not display certain licenses correctly. Fixed.
- License dialog: Deleting certain licenses did not work. Fixed.
- NXP iMXRT102x: Flash programming did not work when no valid image was already present in it. Fixed.
- When loading Intel HEX files that contain both "extended segment address record" and "extended linear address record" types (very very rare), it could happen that wrong addresses where computed. Fixed.
J-Flash SPI
- License dialog did not display certain licenses correctly. Fixed.
- License dialog: Deleting certain licenses did not work. Fixed.
J-Scope
- Additional variables could be added while active data sampling, which could cause a crash. Fixed.
- Crash when using RTT mode due to missing GUI element. Fixed.
- HSS: Using HSS caused a minor memory leak. Fixed.
- HSS: Using more variables then supported by the J-Link probe caused a crash. Fixed.
- If at project creation no symbols were selected, it was not possible to add symbols since the relevant button was missing. Fixed.
- Improved reading performance.
- Save dialog did not open when exiting the app and the user was prompted with the option to save. Fixed.
- Using shortcuts "+" and "-" to adjust the Y-Resolution caused crash when no symbol was selected. Fixed.
- When canceling the color selection dialog, the color of the symbol was set to black. Fixed.
- When reading data tooltip always showed the symbol data at cursor position, blocking all other tooltips (e.g. button tooltips). Fixed.
- When starting data sampling failed for some reason, the user was not informed. Fixed.
Version V7.52c (2021-08-10)
Commander
- ARMv8-A/R (e.g. Cortex-A53): ELR_EL1/2/3 were not shown on "regs" command. Fixed.
- ARMv8-A/R (e.g. Cortex-A53): SP_EL1/2/3 were not shown on "regs" command. Fixed.
DLL
- ARMv8-A/R (e.g. Cortex-A53): Added more information about supported exception levels, FPU implemented, ... to the connect sequence.
- Big endian Cortex-A and Cortex-R devices flash programming, fixed.
- Cortex-M ARMv8-M targets: Watchpoint (WP) handling (for Cortex-M23, Cortex-M33) did not work for an address + data matching WP. Fixed.
- GUI Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.
- NXP LPC54xx: Under special circumstances, flash programming could fail. Fixed.
- Restore of SPIFI flash programming algorithm for Xilinx Zynq7000 series devices. Fixed.
Firmware
- Flasher ARM V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- Flasher ARM V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- Flasher ARM V5: Raspberry Pi RP2040: Flash programming in stand-alone mode did not work properly. Fixed.
- Flasher Compact V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- Flasher Compact V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- Flasher Compact V5: Raspberry Pi RP2040: Flash programming in stand-alone mode did not work properly. Fixed.
- Flasher PRO V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- Flasher PRO V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- Flasher PRO V5: Raspberry Pi RP2040: Flash programming in stand-alone mode did not work properly. Fixed.
- Flasher PRO XL V5: Raspberry Pi RP2040: Flash programming in stand-alone mode did not work properly. Fixed.
- J-Link EDU Mini V1: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
- J-Link EDU/BASE/PLUS V10: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Link EDU/BASE/PLUS V11: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- J-Link EDU/BASE/PLUS V11: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
- J-Link PRO V4: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Link PRO V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- J-Link PRO V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Link PRO V5: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
- J-Link ULTRA+ V4: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Link ULTRA+ V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- J-Link ULTRA+ V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Link ULTRA+ V5: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
- J-Link WiFi V1: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- J-Link WiFi V1: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Link WiFi V1: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
- J-Link-OB-K22-RISCV: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
- J-Trace PRO V2 Cortex: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- J-Trace PRO V2 Cortex: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Trace PRO V2 Cortex: Static IP configuration did not work properly in setups with switches that do MAC authentication (expect J-Link to send the first packet on its own even if a static IP is used). Fixed.
- J-Trace PRO V2 CortexM: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
- J-Trace PRO V2 CortexM: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
- J-Trace PRO V2 CortexM: Static IP configuration did not work properly in setups with switches that do MAC authentication (expect J-Link to send the first packet on its own even if a static IP is used). Fixed.
- LPC-Link2 on-board: Updated Terms of Use. See http://www.segger.com/lpcxpresso-v2.html
- LPC-Link2: Updated Terms of Use. See http://www.segger.com/lpc-link-2.html
- MCU-Link: Updated Terms of Use. See http://www.segger.com/mcu-link.html
GDB Server
- Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.
J-Flash
- Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.
- NXP LPC54xx: Flash programming did not work because unavailable RAM (SRAM1) was used. Fixed.
J-Flash Lite
- Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.
J-Flash SPI
- Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.
J-Scope
- "Add Symbol" button was visible in RTT mode. Fixed.
- .out files were not selectable. Fixed.
- Default window size was not FullHD compatible. Fixed.
- J-Scope did not properly find RTT variables. Fixed.
- JLinkScript files with a different ending than ".JLinkScript" could not be selected. Fixed.
Remote Server
- Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.
SWO Viewer
- Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.
Version V7.52b (2021-08-03)
DLL
- ARMv8-A: J-Link script files: Specifying an AP map via JLINK_ExecCommand("CORESIGHT_AddAP ..."); did not work properly. Fixed.
- ARMv8-R: J-Link script files: Specifying an AP map via JLINK_ExecCommand("CORESIGHT_AddAP ..."); did not work properly. Fixed.
- Microchip SAMA7G54: Updated device name from "ATSAMA7G54" to "SAMA7G54". Fixed.
- NXP iMXRT11xx devices: SPI flash: Flash download did not work with flashes > 64MB. Fixed.
- Reset strategy "Reset + Halt after bootloader using watchpoint" did not work for ARMv8M based devices. Fixed.
- STM32U5: Flash programming/Erase failed when TrustZone is enabled and CPU is in non-secure state. Fixed.
Firmware
- J-Trace PRO V2 Cortex: Debugging via Infineon SPD target interface did not work properly. Fixed.
- J-Trace PRO V2 CortexM: Debugging via Infineon SPD target interface did not work properly. Fixed.
J-Flash
- Welcome Dialog: The "Do not show this message again" checkbox did not have any effect. Introduced with V6.70. Fixed.
J-Link Package
- Installer: Windows: Renamed Flasher i386 installer from "Flasher_Windows_Vxxxx.exe" to "Flasher_Windows_Vxxxx_i386.exe"
- Installer: Windows: Renamed Flasher x86_64 installer from "Flasher_Windows_x86_64_Vxxxx.exe" to "Flasher_Windows_Vxxxx_x86_64.exe"
- Installer: Windows: Renamed J-Link i386 installer from "JLink_Windows_Vxxxx.exe" to "JLink_Windows_Vxxxx_i386.exe"
- Installer: Windows: Renamed J-Link x86_64 installer from "JLink_Windows_x86_64_Vxxxx.exe" to "JLink_Windows_Vxxxx_x86_64.exe"
Registration
- Registering a probe/ programmer did not change its "Registered" status inside the utility. Fixed.
Version V7.52a (2021-07-28)
Firmware
- J-Link PRO V4: Some older units (4.3, 4.2) were stuck in BTL after firmware update. Introduced with V7.52. Fixed.
- J-Link ULTRA+ V4: Some older units (4.3, 4.2) were stuck in BTL after firmware update. Introduced with V7.52. Fixed.
Version V7.52 (2021-07-27)
DLL
- Added debug and flash programming support for NXP MKE12Z series.
- Added debug and internal flash programming support for Maxim MAX32655 series device.
- Added debug support for Microchip SAMA7G54.
- Added debug support for SiLabs BGM220P device series.
- Added debug support for Syntacore SCR3 (RV32) device/core.
- Added flash programming support for SiLabs BGM220P device series.
- Added native background memory access for Renesas RZ/A2M series so things like SEGGER RTT work without stop mode.
- Added new J-Link Command String which can be uesed to specify the watchpoint address when using Reset + Halt after bootloader reset strategy.
- Added new reset strategy: Reset + Halt after bootloader using watchpoint. (https://wiki.segger.com/Reset_and_Halt_After_Bootloader)
- Cortex-A/R: During flash programming, CPSR.F was forcefully set to 0 which could lead to problems on devices with support for non-maskable FIQs (NMFI) like bthe Xilinx Zynq 7000 series devices. Fixed.
- GigaDevice GD32F450xx series devices working RAM size, fixed.
- GigaDevice GD32F450xx series devices: Due to wrong RAM size in MCU database, flash programming could fail. Fixed.
- Microchip ATSAML10 and ATSAML11 series devices added internal data flash programming support.
- Microchip SAM9X60 series devices were handled as ARM920T based while they are ARM926EJ-S based. Fixed.
- NXP i.MXRT116x Cortex-M4 debug: Software breakpoints did not work correctly in case the LMem caches were enabled. Fixed.
- NXP i.MXRT116x series: Connect sequence to the Cortex-M4 failed under certain circumstances. Fixed.
- NXP i.MXRT116x series: Some devices passed by ARM KEIL MDK were not detected correctly. Fixed.
- NXP iMXRT11xx devices: The available QSPI memory range for FLEXSPI1 was falsly set to 64 MB instead of 256 MB. Fixed.
- Raspberry RP2040 improved SPI flash programmng speed.
- Some device aliases were missing for the NXP MKE13Z series. Fixed.
- ST STM32H7Axx series devices flash signal delay during flash programming. Fixed.
- STM32L5: Flash programming did not work properly when Trustzone was enabled and some sectors were set to non-secure while others were secure. Fixed.
- STM32U5 devices: Flash programming did not work properly when Trustzone was enabled and some sectors were set to non-secure while others were secure. Fixed.
- Windows: When selecting a J-Link before opening a connection to it (e.g. in the "emulator selection" dialog), the control panel tray icon was already visible and redirected to an incorrect address. Fixed.
Firmware
- J-Link EDU Mini V1: RISC-V: RTT stop mode did not work. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: RTT stop mode did not work. Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V: RTT stop mode did not work. Fixed.
- J-Link PRO V4: RISC-V: RTT stop mode did not work. Fixed.
- J-Link PRO V5: RISC-V: RTT stop mode did not work. Fixed.
- J-Link ULTRA+ V4: RISC-V: RTT stop mode did not work. Fixed.
- J-Link ULTRA+ V5: RISC-V: RTT stop mode did not work. Fixed.
- J-Link WiFi V1: RISC-V: RTT stop mode did not work. Fixed.
- J-Link-OB-K22-RISCV: RISC-V: RTT stop mode did not work. Fixed.
- J-Link-OB-K22-SiFive: RISC-V: RTT stop mode did not work. Fixed.
- J-Trace PRO Cortex-M V1: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
J-Flash
- GigaDevice GD32F450xx series devices: Due to wrong RAM size in MCU database, flash programming and reading of more than 128 KB of flash at once, could fail. Fixed.
- If a data file path in a J-Flash project file was a relative path, J-Flash would change the project settings to contain the absolute path and notify this as a project change to the user. Fixed.
OFL
- Cortex-A/R: During flash programming, CPSR.F was forcefully set to 0 which could lead to problems on devices with support for non-maskable FIQs (NMFI) like bthe Xilinx Zynq 7000 series devices. Fixed.
Registration
- Added "nickname" column to J-Link table.
- Added button to refresh list.
- Depending on the desktop resolution, some text was cut off. Fixed.
- Registering products did not work, log always reported "Multiple selections detected". Fixed.
- The window title did not contain the correct product name (missing spaces) and was missing the version number as well as the company name. Fixed.
- The window was not resizable. Fixed.
- Updated GUI.
- Updated J-Link picture so it also contains J-Trace and Flasher.
- Updated J-Link picture.
- Updated references to "J-Link" or similar to say "probes and programmers" instead.
RTT Viewer
- If there are < 2 recent devices, the device selection combobox will not show a selection button anymore.
Version V7.50a (2021-07-08)
DLL
- J-Link EDU / ST-LINK, ... terms of use dialog was shown on connect to probe even if probe was not used to debug a target MCU. Fixed.
- License dialog: On high-resolution displays, only a few lines of license text were visible without scrolling. Fixed.
- License dialog: The dialog was not resizable. Fixed.
- License dialog: When closing a license dialog (e.g. when using J-Link EDU or CMSIS-DAP) using the <Escape> key, the DLL would hang. Fixed.
- Linux: NXP LPC-Link 2 CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
- Linux: NXP MCU-Link CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
- macOS: Connecting to CMSIS-DAP could fail because device path exceeded internal buffer sizes. Fixed.
- macOS: NXP LPC-Link 2 CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
- macOS: NXP MCU-Link CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
- O2Micro OZ935xx series devices internal flash programming chip erase functionality. Fixed.
- ST STM32H7Axx series devices internal flash programming algo, flash delay calculation. Fixed.
- STM32L5: TrustZone flash programming did not work correctly, when only a part of the flash was secure. Fixed.
- STM32U5: Flash programming failed when TrustZone was enabled. Fixed.
- The following core identifiers were not accepted in JLinkDevices.xml: JLINK_CORE_CORTEX_M55, JLINK_CORE_CORTEX_A35, JLINK_CORE_CORTEX_R52, JLINK_CORE_RV32, JLINK_CORE_RV64. Fixed.
- When using unknown command string with JLINKARM_ExecCommand() / JLINK_ExecCommand(), these calls were not shown in the J-Link log file. Fixed.
- Windows: NXP LPC-Link 2 CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
- Windows: NXP MCU-Link CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
DLL Updater
- Some applications (e.g. Ozone) were listed twice per installation (introduced in V7.50). Fixed.
GDB Server
- The J-Link GDB Server rejected to work with Cortex-A53 based MCUs. Fixed.
J-Flash
- Downloading files to modules of Flasher ATE or Flasher Hub did not work correctly. Fixed.
- Extended Flasher module selection so up to 24 modules can be specified.
- Improved speed when downloading multiple files to programmer.
J-Flash SPI
- Files can now be downloaded to modules of Flasher ATE or Flasher Hub.
- Improved speed when downloading multiple files.
Version V7.50 (2021-07-01)
Commander
- Added a message when the connect failed because the measured target voltage was too low.
DLL
- Added alias for ONSemi RSL15-512 series device.
- Added Cortex-M0 debug support for STM32WL55xx and STM32WL54xx series devices.
- Added debug and flash programming support for Infineon CYPM1111 and CYPM1211 series devices.
- Added debug and flash programming support for Maxim MAX32672 series devices.
- Added debug support for CloudBEAR BM-310 (RV32) device/core.
- Added debug support for CloudBEAR BM-610 (RV64) device/core.
- Added debug support for Codasip H50X (RV64) device/core.
- Added debug support for Codasip H50XF (RV64) device/core.
- Added debug support for Codasip L10 (RV32) device/core.
- Added debug support for Codasip L30 (RV32) device/core.
- Added debug support for Codasip L30F (RV32) device/core.
- Added debug support for Codasip L50 (RV32) device/core.
- Added debug support for Codasip L50F (RV32) device/core.
- Added debug support for Infineon IMD700A series devices (IMD700A_128, IMD701A_128).
- Added debug support for Microchip SAM9X60D5M, SAM9X60D1G, SAM9X60D6K.
- Added debug support for Renesas RA6T1 family.
- Added flash programming support for Infineon IMD700A series devices (IMD700A_128, IMD701A_128).
- Added flash programming support for internal flash and internal QSPI flash of NXP K32W041AM device (Details: https://wiki.segger.com/NXP_K32W0_Series).
- Added flash programming support for Renesas RA6T1 family.
- Added support for Macronix MX66UM1G45G to all (Q)SPI based flash algorithms.
- Added trace related ROM table base addresses natively for STM32H7 series devices.
- ARM MPS3 related devices: Changed naming scheme so that it is unambiguous, as it now contains the FPGA image name.
- Cortex-M: Command string "CORESIGHT_SetCoreBaseAddr" did not disable ROMBASE check and ROM table scan. Fixed.
- Holtek HT32: Added debug support for multiple devices of the HT32-Series.
- Holtek HT32: Added flash programming support for missing HT32F52-family devices.
- Microchip ATSAML11 series device, added Reset after Enable RAM execution.
- Multiple ST STM32 device descriptions passed to DLL by KEIL uVision were recognized as "unknown" device. Fixed.
- NXP i.MXRT117x series: Connect sequence to the Cortex-M4 failed under certain circumstances. Fixed.
- NXP i.MXRT117x series: Some devices passed by ARM KEIL MDK were not detected correctly. Fixed.
- NXP iMXRT102x devices: Reset did not work correctly. Fixed.
- NXP iMXRT102x devices: Under some circumstances, flash programming did not works after reset. Fixed.
- NXP iMXRT106x devices: Under rare circumstances, the reset could cause to a HardFault. Fixed.
- NXP iMXRT10xx devices: When a breakpoint was active, the reset would sometimes fail. Fixed.
- NXP S32K148 code flash size (1.5MB), fixed.
- OnSemi RSL15, added default reset.
- Raspberry Pi RP2040: Power-cycle or reset pin toggle was needed after 1st debug session to allow a new debug session. Fixed.
- Raspberry Pi RP2040: QSPI flash-programming did not work in case the device was still in bootrom under certain circumstances. Fixed.
- ST STM32 devices: For some devices the watchdog timers were not frozen correctly. Fixed.
- ST STM32: Added debug and flash programming support for multiple missing devices.
- ST STM32F750x8 series devices, internal flash size, fixed.
- ST STM32G4 family: During unsecure: If the DEV_ID was unknown the connect was aborted instead of skipping the unsecure. Fixed.
- ST STM32L071, STM32L072, STM32L073, STM32L083 devices with 64 KiB internal flash had their EEPROM misplaced. Fixed
DLL Updater
- The 64-bit versions of the more recent IAR Embedded Workbench for ARM were not found shown for update. Fixed.
- The version number of the IAR Embedded Workbench for ARM > V6.50.1 was not displayed correctly. Fixed.
Firmware
- Flasher ARM V4: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- Flasher ARM V5: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- Flasher Compact V5: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- Flasher Portable PLUS V1: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- Flasher PPC V4: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- Flasher PRO V4: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- Flasher PRO V5: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- Flasher RX V4: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Link EDU Mini V1: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link EDU Mini V1: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link EDU Mini V1: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Link EDU/BASE/PLUS V10: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Link EDU/BASE/PLUS V10: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link EDU/BASE/PLUS V10: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Link EDU/BASE/PLUS V11: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Link EDU/BASE/PLUS V11: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link EDU/BASE/PLUS V11: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Link OB-K22-RISCV: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link OB-K22-RISCV: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link OB-K22-RISCV: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Link PRO V4: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link PRO V4: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Link PRO V4: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link PRO V4: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Link PRO V5: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link PRO V5: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Link PRO V5: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link PRO V5: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Link ULTRA+ V4: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link ULTRA+ V4: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Link ULTRA+ V4: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link ULTRA+ V4: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Link ULTRA+ V5: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link ULTRA+ V5: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Link ULTRA+ V5: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link ULTRA+ V5: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Link WiFi V1: RISC-V (RV64): R/W memory via abstract commands and ProgBuf was executed with <aarsize> == 2 (32-bit GPR accesses). Fixed.
- J-Link WiFi V1: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Link WiFi V1: RISC-V: Added support for background memory accesses (RTT, HSS) via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- J-Link WiFi V1: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
- J-Trace PRO V2 Cortex: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
- J-Trace PRO V2 CortexM: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
GDB Server
- Incorrect reply has been replied on target quit / exit signal. Fixed.
- Some commands were not printed to the log immediately (e.g. "monitor reset"). Fixed.
J-Flash
- Certain custom init steps did not work as expected as cache handling changed the behavior on the HW. J-Flash now disables internal J-Link DLL caching (MemCache, FlashCache) during the custom init steps. Fixed.
- Improved performance of the "Eliminate blank areas..." option.
- Memory window: The address inside the view is now displayed with an underscore ('_') between upper and lower 16bit to improve readability, e.g. "0123ABCD" turns into "0123_ABCD".
- Memory window: When trying to select an item (e.g. before writing a new value to it), the selection was off by one character. Introduced with V7.23b. Fixed.
- Renesas RA6M4 series: Programming of code & data flash did not work properly. Fixed.
- When passing the "-exit" parameter, the "no license found" dialog will not be shown anymore.
J-Flash SPI
- Memory window: The address inside the view is now displayed with an underscore ('_') between upper and lower 16bit to improve readability, e.g. "0123ABCD" turns into "0123_ABCD".
- Memory window: When trying to select an item (e.g. before writing a new value to it), the selection was off by one character. Introduced with V7.23b. Fixed.
- When passing the "-exit" parameter, the "no license found" dialog will not be shown anymore.
J-Mem
- Memory window: The address inside the view is now displayed with an underscore ('_') between upper and lower 16bit to improve readability, e.g. "0123ABCD" turns into "0123_ABCD".
- Memory window: When trying to select an item (e.g. before writing a new value to it), the selection was off by one character. Introduced with V7.23b. Fixed.
J-Run
- Added new command-line option for setting the J-Link script file to use: --jlinkscriptfile <str>
Remote Server
- Added command line option "-log".
RTT
- 32-bit Cortex-A/R: RTT control block and buffers may now also be in normal uncached memory rather than strongly-ordered memory. Results in better RTT performance.
- _DoInit() could cause an unaligned access which caused a DataAbort when accessing strongly-ordered memory. Fixed.
- Added identification of Cortex-R for automatic locking.
- DMB was not defined for 32-bit Cortex-A/R (ARMv7-A, ARMv7-R). Fixed.
- RISC-V: Added support for RTT via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
- ST STM32F405 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
- ST STM32F407 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
- ST STM32F415 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
- ST STM32F417 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
- ST STM32F423 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
- ST STM32F427 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
- ST STM32F429 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
- ST STM32F437 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
- ST STM32F439 series devices: Added CCM RAM @ 0x1000_0000 to RTT auto-search ranges to make RTT working out-of-the-box if RTT control block is placed in CCM.
SWO Viewer
- Command line option "-itmport" did not set <ITMMask> properly. Fixed.
Trace
- LTRACE: ETMv4 (Cortex-M7, Cortex-M33) packet analyzer could crash under special circumstances. Introduced in Feb 2021 in V6.96. Fixed.
Version V7.22b (2021-06-17)
DLL
- Added four new J-Link script file functions which are executed right after and before memory access : HandleBeforeMemAccessWrite/Read() and HandleAfterMemAccessWrite/Read().
- Multiple Cypress device descriptions passed to DLL by IAR EWARM of the CY8C, CYB0, CYS0 and CYT2 families were recognized as "unknown" device. Fixed.
- Multiple Cypress device descriptions passed to DLL by KEIL uVision of the CY8C, CYB0, CYS0 and CYT2 families were recognized as "unknown" device. Fixed.
- Multiple Holtek device descriptions passed to DLL by KEIL uVision of the HT32 family were recognized as "unknown" device. Fixed.
- Multiple Infineon device descriptions passed to DLL by IAR EWARM of the TLE and XMC families were recognized as "unknown" device. Fixed.
- Multiple Infineon device descriptions passed to DLL by KEIL uVision of the TLE and XMC families were recognized as "unknown" device. Fixed.
- NXP i.MXRT101x: Reset did not work correctly in case the MCU was configured for QSPI boot. Fixed.
- NXP i.MXRT117x Cortex-M4 debug: Software breakpoints did not work correctly in case the LMem caches were enabled. Fixed.
- NXP NHS31xx Sector preparation did not work correctly for multiple sectors. Fixed.
- O2Micro OZ935xx FlashA timeout flag reset, fixed.
- Silicon Labs EFM32GG11: Under special circumstances, flash programming did not work. Introduced in V7.22. Fixed.
- TI MSP432P41: In case of the flash controller was configured to erase the information memory, erase of the internal flash failed. Fixed.
Firmware
- Flasher ARM V4: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- Flasher ARM V5: Stand-alone mode: Programming via debug interface: Added automatic CPU speed detection for algorithms that need the CPU speed.
- Flasher ARM V5: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- Flasher Compact V5: Stand-alone mode: Programming via debug interface: Added automatic CPU speed detection for algorithms that need the CPU speed.
- Flasher Compact V5: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Programming via debug interface: Added automatic CPU speed detection for algorithms that need the CPU speed.
- Flasher Portable PLUS V1: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- Flasher PPC V4: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- Flasher PRO V4: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- Flasher PRO V5: Stand-alone mode: Programming via debug interface: Added automatic CPU speed detection for algorithms that need the CPU speed.
- Flasher PRO V5: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Programming via debug interface: Added automatic CPU speed detection for algorithms that need the CPU speed.
- Flasher PRO XL V5: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- Flasher RX V4: Stand-alone mode: When programming a data file with large 0xFF areas in it, under very rare circumstances it could happen that after several programming cycles, the Flasher firmware reported a corrupted data file and rejected further programming until the data file was downloaded to the Flasher again. Fixed.
- J-Link EDU Mini V1: Regression: Writing memory via system bus was slow. Introduced with V6.94c. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link PRO V4: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link PRO V5: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link ULTRA+ V4: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link ULTRA+ V5: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link WiFi V1: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link-OB-K22-RISCV: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
J-Flash
- Project Settings: Target interface: When trying to remove the text inside a "kHz" combobox, a "1" would always stay, even when trying to remove it via backspace or delete. Fixed.
J-Flash SPI
- Project Settings: Setup: When trying to remove the text inside the "kHz" combobox, a "1" would always stay, even when trying to remove it via backspace or delete. Fixed.
Manual
- UM08001: Chapter "J-Link Script Files" updated. Section "Global DLL variables": Updated MAIN_ResetType (obsolete) to JLINK_ResetType. Also updated the flags from RO to RW.
Remote Server
- Executing file operations (e.g. via "flist" command by J-Link Commander) failed when connected via J-Link Remote Server instance. Fixed.
Version V7.22a (2021-06-09)
DLL
- J-Link Script Files: In the past, the "JLINK_ResetType" variable was read only. Updated the variable to read / write (RW).
- Renesas R7FS3A7 (e.g. R7FS3A77C): By default, the QSPI flash bank was enabled which could cause issues in setups where the external flash is not used. Fixed.
Firmware
- Flasher Compact V5: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- Flasher Compact V5: SPI direct programming / universal flash loader: Programming DAT files with lots of gaps (> 100) resulted in excessive heap usage and potential allocation failures. Fixed.
- Flasher Compact V5: SPI direct programming: Programming of DAT files with a lot of small ranges (1 flash page max.) could result in verify step to hang. Fixed.
- Flasher Portable PLUS V1: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- Flasher Portable PLUS V1: SPI direct programming / universal flash loader: Programming DAT files with lots of gaps (> 100) resulted in excessive heap usage and potential allocation failures. Fixed.
- Flasher Portable PLUS V1: SPI direct programming: Programming of DAT files with a lot of small ranges (1 flash page max.) could result in verify step to hang. Fixed.
- Flasher PRO V5: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- Flasher PRO V5: SPI direct programming / universal flash loader: Programming DAT files with lots of gaps (> 100) resulted in excessive heap usage and potential allocation failures. Fixed.
- Flasher PRO V5: SPI direct programming: Programming of DAT files with a lot of small ranges (1 flash page max.) could result in verify step to hang. Fixed.
- Flasher PRO XL V5: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- Flasher PRO XL V5: SPI direct programming / universal flash loader: Programming DAT files with lots of gaps (> 100) resulted in excessive heap usage and potential allocation failures. Fixed.
- Flasher PRO XL V5: SPI direct programming: Programming of DAT files with a lot of small ranges (1 flash page max.) could result in verify step to hang. Fixed.
- J-Link EDU Mini V1: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- J-Link OB-K22-RISCV: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- J-Link PRO V4: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- J-Link PRO V5: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- J-Link ULTRA+ V4: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- J-Link ULTRA+ V5: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
- J-Link WiFi V1: RISC-V in CoreSight SoC-600: Some debug operations like IsHalted() did not work properly. Fixed.
J-Flash
- When opening large data files (e.g. > 20MB) it could happen that 0s were displayed in gaps instead of "--". Fixed.
J-Flash SPI
- When opening large data files (e.g. > 20MB) it could happen that 0s were displayed in gaps instead of "--". Fixed.
J-Flash SPI CL
- The process return code was 0 when an error occurred (e.g. Verify failed). Fixed.
- When specifying a J-Flash log file via command line ("-jflashlog") no log file was created. Fixed.
Version V7.22 (2021-06-01)
Commander
- Cortex-M: Symbolic name for active exception indicated by IPSR was not correct for IPS values > 3. Fixed.
- RISC-V RV64: Added suggested TIFs JTAG, SWD, cJTAG for default TIF selection.
Control Panel
- Added auto-reconnect mechanism in case control panel lost connection due to restarted debug session.
- Added button to remove breakpoints.
- Added heading when control panel lost connection to current debug session.
DLL
- Added and corrected RTT ranges of all supported LPC55xx devices.
- Added debug & flash programming support for Microchip's ATSAMRH707F18A series.
- Added debug & flash programming support for NXP KE1xZ128/KE1xZ256 device family.
- Added debug and flash programming support for GigaDevice GD32E232xx family.
- Added debug and flash programming support for GigaDevice GD32E501xx family.
- Added debug and flash programming support for NXP NxH2004.
- Added debug and flash programming support for NXP NxH3675.
- Added debug support for SiFive E21, E21ARTY device/core.
- Added debug support for SiFive E24, E24ARTY device/core.
- Added debug support for SiFive E34, E34ARTY device/core.
- Added debug support for SiFive E76, E76ARTY device/core.
- Added debug support for SiFive S21, S21ARTY device/core.
- Added debug support for SiFive S51, S51ARTY device/core.
- Added debug support for SiFive S76, S76ARTY device/core.
- Added debug support for the Cortex-M33 of the Renesas RZ/G2L series.
- Added debug support for the Cortex-M33 of the Renesas RZ/G2LC series.
- Added flash programming support for NXP K32W041A device.
- Added flash programming support for ST STM32G031xx, STM32G041xx, STM32G050xx, STM32G051xx, STM32G061xx, STM32G071xx, STM32G0B0xx and STM32G0B1xx series of devices.
- Added flash support for STM32L5 while trust zone is enabled (TZEN == 1).
- Added generic debug support for Cortex-A32 (ARMv8-A).
- Added generic debug support for Cortex-A55 (ARMv8-A).
- Added internal FlashB programming support for O2Micro OZ93506 series devices.
- Added missing aliases for TLE987x series devices.
- Added SiFive S54, S54ARTY.
- Added support for Macronix MX66UM1G45G to all (Q)SPI based flash algorithms.
- Improved displayed multi-byte units to be less ambiguous (KB, MB, GB,... => KiB, MiB, GiB,...).
- Improved programming speed for STM32L5 series devices internal flash.
- iMXRT105x: Under some circumstances, the reset did not work. Fixed.
- Multiple GigaDevice device descriptions passed to DLL by IAR EWARM of the GD32E family were recognized as "unknown" device. Fixed.
- Multiple GigaDevice device descriptions passed to DLL by IAR EWARM of the GD32F family were recognized as "unknown" device. Fixed.
- NXP iMX8: Added 3rd party Device Support for iMX8 family.
- NXP iMXRT1064 series devices reconfigured external flash at address 0x6000 0000 as optional.
- O2Micro OZ93506 series devices Flash A size, fixed.
- O2Micro OZ935xx series devices Flash A erase value and Flash A lifecycle flag handling, fixed.
- Renesas R7FA2L1A9 and R7FA2L1AB size of data flash, fixed.
- RISC-V behind SoC-600 DAP: If J-Link script file specified AP map + <APAddr> for all APs but used <CORESIGHT_SetIndexAPBAPToUse> instead of <CORESIGHT_SetDebugAPToUse> to assign the AP in use, J-Link complained that AP could not be used. Fixed.
- SiLabs EFM32TG11: When programming the internal flash, the lock bits were not cleared. Fixed.
- SPIFI-Lib QSPI flash programming for NXP iMXRT106x series devices, fixed.
- STM32G4: Added native SWO support.
Firmware
- Flasher Compact V5: SPI direct programming / universal flash loader: In case of a very fragmented data file (several hundreds to thousands of gaps), it could happen that a memory allocation failure of Flasher was output as error via ASCII interface of Flasher but final result indicated OK. Fixed.
- Flasher Package: macOS: Installer: arm64: Did require Rosetta to run. Fixed.
- Flasher Portable PLUS V1: SPI direct programming / universal flash loader: In case of a very fragmented data file (several hundreds to thousands of gaps), it could happen that a memory allocation failure of Flasher was output as error via ASCII interface of Flasher but final result indicated OK. Fixed.
- Flasher PRO V5: SPI direct programming / universal flash loader: In case of a very fragmented data file (several hundreds to thousands of gaps), it could happen that a memory allocation failure of Flasher was output as error via ASCII interface of Flasher but final result indicated OK. Fixed.
- Flasher PRO XL V5: SPI direct programming / universal flash loader: In case of a very fragmented data file (several hundreds to thousands of gaps), it could happen that a memory allocation failure of Flasher was output as error via ASCII interface of Flasher but final result indicated OK. Fixed.
- J-Link PRO V5: Max. number of connections was set to 5 instead of 10 (like for the V4) by accident. Fixed.
- J-Link ULTRA+ V5: Max. number of connections was set to 5 instead of 10 (like for the V4) by accident. Fixed.
GDB Server
- Cortex-A32: Connect did not work. "Device family is not supported by GDB Server." message reported. Fixed.
- Linux: Under very special circumstances a "buffer overflow detected" GLibc error was triggered when a close request was issued to GDB Server. (Mainly happened under Ubuntu 20.04) Fixed.
- Updated Zephyr RTOS plugin to latest source base.
HSS
- RISC-V with system bus access: HSS did not work / was reported to be not supported for this combination. Fixed.
J-Flash SPI
- Added support for Microchip SST26VF016B and SST26VF032B.
- The display name of ZB25VQ64 and ZB25VQ128 was ZB25VQ32. Fixed.
J-Link Package
- Improved displayed multi-byte units to be less ambiguous (KB, MB, GB,... => KiB, MiB, GiB,...).
- macOS: Installer: arm64: Did require Rosetta to run. Fixed.
J-Link Script Files
- Non-bracketed arithmetic expressions with operands of the same precedence (+, -, ...) resulted in incorrect evaluation of right-to-left instead of left-to-right. Fixed.
SWO Viewer
- Added command line option "-swoattach <OnOff>" that disables all J-Link side initialization of SWO and relies on the target application to perform SWO init.
Version V7.20b (2021-05-21)
DLL
- ARMv8-AR: No reset was performed. Fixed.
- macOS: Connected probes in CMSIS-DAP mode were not detected correctly in case SIP (System Integrity Protection) was enabled. Fixed.
- RISC-V Nexus Trace: Under certain circumstances stepping out of functions could lead to a crash of the trace analyzer. Fixed.
- STM32H7: H7 specific watchdog handling was not used for STM32H723/33. Fixed.
- STM32H7: Under some circumstances, the LS watchdog was not frozen while debugging. Fixed.
- The serial numbers of the following devices were not resolved to their correct names: J-Link-OB-K22-RISCV, Flasher PRO XL, Flasher Compact, Flasher Hub, SEGGER LicStick (USB Dongle), J-Link OB-nRF5340-NordicSemi, J-Link MCU-Link, J-Link-OB-STM32F4405-Arduino, J-Link-OB-RA4M2. Fixed.
- Under certain circumstances the calculated SWO Speed may exceed the CPU clock speed causing issues on some target devices. Fixed.
- Under certain circumstances when doing buffer trace with ETMv4 on a target fault exception backtrace may be analyzed further then necessary. Fixed.
J-Flash
- Project information: When "TCP/IP" was selected for connection type in the project settings, the string displayed for "host connection" in the project information window was incorrect. Fixed.
- Project settings -> Performance, shortcut description for Verify, fixed.
J-Flash SPI
- Project information: When "TCP/IP" was selected for connection type in the project settings, the string displayed for "host connection" in the project information window was incorrect. Fixed.
J-Link Package
- Linux ARM: J-Links in CMSIS-DAP mode could not be accessed without root privileges. (So they could not be configured back without starting J-Link Configurator as root). Fixed.
- Linux: J-Links in CMSIS-DAP mode could not be accessed without root privileges. (So they could not be configured back without starting J-Link Configurator as root). Fixed.
Version V7.20a (2021-05-07)
Control Panel
- The rows inside the "Data breakpoints" table could contain garbage data. Fixed.
DLL
- ARM SSE-200 devices: Connecting to Core 1 resulted in connecting to Core 0. Fixed.
- NXP S32K14x series devices flash programming with 8byte min alignment, fixed.
- Qorvo GP570xxxx, UE878xxxx and QPG6095: Reset did not work properly. Fixed.
- Qorvo GP570xxxx, UE878xxxx and QPG6095: Under special circumstances, flash programming could fail. Fixed.
- Qorvo QPG5071 and QPG6100: Reset did not work properly. Fixed.
- Qorvo QPG5071 and QPG6100: Under special circumstances, flash programming could fail. Fixed.
- RAM was not preserved if RAM was changed between reset and the first flash download. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V9: When using SPI, the CS# signal was sometimes set HIGH prematurely, causing SPI operations (e.g., ReadID, Erase, Program, Verify, ...) to fail. Fixed.
- J-Link-OB-K22-NordicSemi: VCOM HWFC support: Configuring the J-Link OB for forced HWFC was effectively ignored. Fixed.
- J-Link-OB-K22-NordicSemi: VCOM HWFC support: The RTS line was not cleared under certain circumstances, even when the J-Link OB was ready to receive data. Fixed.
Registration
- Linux: When starting from the terminal, some warning messages were shown in the console. Fixed.
- macOS: When starting from the terminal, some warning messages were shown in the console. Fixed.
Version V7.20 (2021-04-28)
Commander
- Application version was not shown correctly, when the minor was a single digit value. Fixed.
- ARMv8-A/R: Current PC was not displayed e.g. when single stepping or halting the CPU. Fixed.
- ARMv8-A/R: Some CPU register could not be written using the "wreg" command. Fixed.
Configurator
- Updated references to "emulator" to say "probe/ programmer" instead.
DLL
- Added debug & flash programming support for Cypress CY8C4149xxx-Sxxx series.
- Added debug and flash programming support for Renesas R7FA4M2AC and R7FA4M2AB series devices.
- Added debug and internal flash programming support for O2Micro OZ935xx series devices.
- Added flash programming support for Cypress CYT2B6 series devices.
- Added flash programming support for Silicon Labs EFM32PG22C200F32, EFM32PG22C200F64, EFM32PG22C200F128, EFM32PG22C200F256, EFM32PG22C200F512.
- Added internal SPI flash programming support for O2Micro OZ93510 series devices.
- Added native SWO init for Microchip/Atmel SAME5x target device series.
- Added support for Cortex-R52 (ARMv8-R).
- ARMv8-AR: Implement caches were not displayed correctly. Fixed.
- ARMv8-AR: Under special circumstances, connect did not work to devices in AArch32 mode. Fixed.
- Cypress CY8C4149xxx-Sxxx: Flash size was incorrect (256 KB instead of 384 KB). Fixed.
- GigaDevice GD32F350CB and GD32F350RB internal flash programming size, fixed.
- Microchip SAMC family: Improved error handling in case of boot protection is enabled.
- Microchip SAMD family: Improved error handling in case of boot protection is enabled.
- NordicSemi nRF5340 NET core flash sector size was incorrectly set to 4 KB (0x1000) while it really is 2 KB (0x800). Fixed.
- NXP LPC55S69: Improved error handling in case of no valid boot image was detected / the device was in a confused state.
- RaspberryPi RP2040 port pin config for QSPI Flash support, fixed.
- TI CC2538 devices: Reconnection to the device failed after unlocking without power-cylcing the device afterwards. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V10: ARMv8-AR: 16 bit read / write accesses did not work. Fixed.
- J-Link EDU/BASE/PLUS V11: ARMv8-AR: 16 bit read / write accesses did not work. Fixed.
- J-Link OB K22 NordicSemi: Drag & drop programming of APP core did not work on nRF53-DK and nRF53-PDK. Fixed.
- J-Link PRO V4: ARMv8-AR: 16 bit read / write accesses did not work. Fixed.
- J-Link PRO V5: ARMv8-AR: 16 bit read / write accesses did not work. Fixed.
- J-Link ULTRA+ V4: ARMv8-AR: 16 bit read / write accesses did not work. Fixed.
- J-Link ULTRA+ V5: ARMv8-AR: 16 bit read / write accesses did not work. Fixed.
- J-Link WiFi V1: ARMv8-AR: 16 bit read / write accesses did not work. Fixed.
GDB Server
- Added NuttX RTOS plugin to shipment.
- Added support for Cortex-R52 (ARMv8-R).
- Added Zephyr RTOS plugin to shipment.
J-Flash
- Added shortcut (F10) for menu option: Target -> Manual Programming -> Read back -> Entire chip
J-Flash SPI
- Added shortcut (F10) for menu option: Target -> Read back -> Entire chip
J-Link Package
- Linux: RPM package: Installation of jlink package failed under certain circumstances due to a build-id conflict. Fixed.
Manual
- UM08001: Chapter "Target interfaces and adapters", *Section "20-pin J-Link connector", *Section "Pinout for SWD", *Section "Target power supply": The word "perm" was part of the wrong column. Fixed.
- UM08001: Chapter "Target interfaces and adapters", *Section "Reference voltage (VTref)": Added link to wiki article for setting a fixed VTref via J-Link Commander.
- UM08001: Chapter "Target interfaces and adapters", *Section "Reference voltage (VTref)": Typo: "on" instead of "one. Fixed.
RTT Viewer
- Added command line option "-ti" / "--terminalindex" (see: https://wiki.segger.com/J-Link_RTT_Viewer#--terminalindex ).
- The currently opened terminal tab is now remembered after closing the application and will be opened automatically on the next application start.
Version V7.00a (2021-04-16)
DLL
- Connect sequence for MediaTek MT7686 series device, fixed.
- Data flash start address for Analog Devices ADuCM330 and ADuCM332, fixed.
- Expanded QSPI flash programming support for Renesas RZ/A2M series devices for QSPI flashes with up to 256 MB flash size.
- Firmware update dialog: Closing the dialog (via <Escape> or [ X ]) would cause the firmware update to be executed. Fixed.
- Monitor mode license dialog: The "Yes" button was in focus instead of the "No" button. Fixed.
- NXP iMXRT1064: Under special circumstances, the reset did not work properly. Introduced in V7.00. Fixed.
- Second debugger connection dialog: The "Yes" button was in focus instead of the "No" button. Fixed.
- ST STM32F4xxx: When an unknown DEV_ID was read during protection check, the connection sequence was aborted instead of only skipping the protection check. Fixed.
- ST STM32F7xxx: When an unknown DEV_ID was read during protection check, the connection sequence was aborted instead of only skipping the protection check. Fixed.
- When an error message box was created during disconnect from J-Link, it could happen that the message box did not have keyboard focus. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V10: J-Link VCOM stopped working when setting too high VCOM baud rates, fixed.
- J-Link EDU/BASE/PLUS V11: J-Link VCOM stopped working when setting too high VCOM baud rates, fixed.
- J-Link PRO V4: J-Link VCOM stopped working when setting too high VCOM baud rates, fixed.
- J-Link ULTRA+ V4: J-Link VCOM stopped working when setting too high VCOM baud rates, fixed.
- J-Link WiFi V1: J-Link VCOM stopped working when setting too high VCOM baud rates, fixed.
J-Flash SPI
- Clear block protection bits function, fixed.
- Number of block protection bits for several ISSI SPI Flashes, adapted.
J-Link Package
- Updated license text.
STM32 Utility
- STM32G4: CAT4 devices were not handled. Fixed.
Version V7.00 (2021-04-08)
Commander
- Added new commands "tdi0" and "tdi1" which can be used to set TDI == HIGH or TDI == LOW.
- Added new commands "tms0" and "tms1" which can be used to set TMS == HIGH or TMS == LOW.
Configurator
- Added support for changing J-Link boot mode to CMSIS-DAP (USB HID).
- When resizing a column in a table to be narrower than the contents of a cell in that column, the font of the cell would change. Fixed.
DLL
- Added debug & flash programming support for Cypress CY8C4149xxx-Sxxx series.
- Added debug and flash programming support for Renesas R7F0E01BD series devices.
- Added debug and internal flash programming support for STM32WB55xx and STM32WB35xx series devices.
- Added debug and QSPI flash programming for Telink TLSR9518xxx series devices.
- Added debug and QSPI flash programming support for NXP i.MXRT116x series devices.
- Added flash programming support for Cypress CYT2BL series devices.
- Added flash programming support for ST STM32U575AI, STM32U575CI, STM32U575OI, STM32U575QI, STM32U575RI, STM32U575VI, STM32U575ZI.
- Added flash programming support for ST STM32U585AI, STM32U585CI, STM32U585OI, STM32U585QI, STM32U585RI, STM32U585VI, STM32U585ZI.
- Added flash programming support for ST STM32U595ZJ, STM32U599BJ, STM32U599NJ devices.
- Added QSPI flash programming for STM32L4Pxxx, STM32L4Qxxx, STM32L4Sxxx and STM32L4Rxxx series devices.
- Added quad memory mapped read for NXP iMXRT117x series devices with SPIFI-Lib support.
- Changed SPI flash programming support for NXP LPC408x series devices to optional.
- Cortex-M55: J-Link did not detect "AMBA AHB5 + enhanced HPROT" APs as AHB AP. Fixed.
- Emulator selection dialog: When resizing a column in a table to be narrower than the contents of a cell in that column, the font of the cell would change. Fixed.
- Further device names for Telink TLSR9518 series devices added.
- NXP iMXRT105x: Added device specific reset.
- NXP iMXRT106x: Reset: In some cases, the Reset did not work correctly. Fixed.
- NXP MIMXRT106x: Added device specific reset.
- Renesas RA: Added debug and flash programming support for RA6M5 family of devices.
- RTT: LPC175x/6x: Added AHB SRAM to auto detection ranges.
- Silicon Labs EFM32TG: Some device names (e.g. EFM32TG11B120F128GM32) were not recognized by Keil MDK. Fixed.
- SPIFI-Lib protection byte check, fixed.
- TI TMS570 / RM44L: Improved OTP flash algorithm to return a more accurate error in case of a invalid AJSM key was programmed.
DLL Updater
- When resizing a column in a table to be narrower than the contents of a cell in that column, the font of the cell would change. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V11: Added support for USB HID CMSIS-DAP / DAPLink mode.
- J-Link PRO V5: Added support for USB HID CMSIS-DAP / DAPLink mode.
- J-Link ULTRA+ V5: Added support for USB HID CMSIS-DAP / DAPLink mode.
- J-Link WiFi V1: Added support for USB HID CMSIS-DAP / DAPLink mode.
J-Flash
- Changed log window background color from gray to white.
- Project settings: Raised limit for init./ exit step comments from 79 characters to 255 characters.
- Project settings: The start address of internal flash banks could be edited. Fixed.
- Project settings: When resizing a column in a table to be narrower than the contents of a cell in that column, the font of the cell would change. Fixed.
J-Flash Lite
- Changed log window background color from gray to white.
J-Flash SPI
- Changed log window background color from gray to white.
- Project settings: Raised limit for init./ exit step comments from 79 characters to 255 characters.
License Manager
- When resizing a column in a table to be narrower than the contents of a cell in that column, the font of the cell would change. Fixed.
Manual
- UM08022: Added Flasher Compact model to manual.
Registration
- When resizing a column in a table to be narrower than the contents of a cell in that column, the font of the cell would change. Fixed.
SWO Viewer
- When all required parameters (Device, CPUFreq, SWOFreq) are passed via commandline, the configuration dialog will now be skipped.
Version V6.98e (2021-03-29)
Commander
- The commands testnrspeed/ testnwspeed would report incorrect (way too high) speeds when the test failed. Fixed.
DLL
- Linux: Applications involving GUI elements (e.g. device selection dialog, flash progress bar, ...) caused a segmentation fault. Introduced in V6.98d. Fixed.
- Mac: Applications involving GUI elements (e.g. device selection dialog, flash progress bar, ...) caused a segmentation fault. Introduced in V6.98d. Fixed.
Version V6.98d (2021-03-26)
DLL
- For Renesas RZ/A1 Dual SPI, NXP Kinetis K80, and ST STA8088 series devices exec to disable compare and L2-Verify mode, fixed.
- Microchip ATSAMHA1E1xAB: Improved flash programming speed.
- NXP RT105x QSPI: Flash-breakpoints did not work under certain circumstances. Fixed.
J-Flash
- Microchip ATSAMHA1E1xAB: J-Flash rejected to download config & data files for stand-alone mode operation. Fixed.
J-Flash SPI
- macOS: Trying to program + verify an SPI flash could crash J-Flash SPI. Fixed.
J-Run
- Added command line option --dryrun.
- Download could program out-of-range data. Fixed.
Version V6.98c (2021-03-16)
DLL
- NXP iMXRT117x: Reading PC & SP after reset could return incorrect values. Fixed.
Firmware
- Flasher ARM V5: Some target interfaces ran at wrong speed (e.g. cJTAG, C2, FINE, UART for universal flash loader, I2C). Introduced with V6.94c. Fixed.
- Flasher Compact V5: Some target interfaces ran at wrong speed (e.g. cJTAG, C2, FINE, UART for universal flash loader, I2C). Introduced with V6.94c. Fixed.
- Flasher PRO V5: Some target interfaces ran at wrong speed (e.g. cJTAG, C2, FINE, UART for universal flash loader, I2C). Introduced with V6.94c. Fixed.
- Flasher PRO XL V5: Some target interfaces ran at wrong speed (e.g. cJTAG, C2, FINE, UART for universal flash loader, I2C). Introduced with V6.94c. Fixed.
Version V6.98b (2021-03-12)
Control Panel
- RTT tab: Improved visualization of information.
DLL
- Atmel (Microchip) ATSAMRH71F20x: ATSAMRH71F20A, ATSAMRH71F20B and ATSAMRH71F20C could not be selected. Fixed.
- Device selection dialog: Some core names were displayed as "???". Fixed.
- Device selection dialog: Some core names were displayed as "???". Fixed.
- NXP i.MXRT101x QSPI: Flash-breakpoints did not work in case the Data-Cache was enabled. Fixed.
- Renesas RA4M2: Under special circumstances, option bytes could not be programmed / verified. Fixed.
- Renesas RX64M (2 MB, 2.5 MB and 3 MB devices): Programming the code flash did not work. Fixed.
- Renesas RX71M (2 MB, 2.5 MB and 3 MB devices): Programming the code flash did not work. Fixed.
- SPI Flash for several Renesas series devices not always present, fixed.
- TI AM335x series: Added reference to wiki page (https://wiki.segger.com/TI_AM335x) to device list (https://www.segger.com/downloads/supported-devices.php).
- TI AM335x series: RTT did not work out-of-the-box because AHB-AP was not marked as usable for RTT. Fixed.
Firmware
- Flasher ARM V5: Stand-alone mode: Programming of Renesas RX72M series devices via JTAG did not work properly. Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Programming of Renesas RX72M series devices via JTAG did not work properly. Fixed.
- Flasher PRO V5: Stand-alone mode: Programming of Renesas RX72M series devices via JTAG did not work properly. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Programming of Renesas RX72M series devices via JTAG did not work properly. Fixed.
- J-Link PRO V5: Direct SPI programming: Improved erase + program + verify speed when used inside J-Flash SPI by using FlashDL logic inside firmware.
- J-Link ULTRA+ V5: Direct SPI programming: Improved erase + program + verify speed when used inside J-Flash SPI by using FlashDL logic inside firmware.
- J-Link-OB-K22-Cortex-A: JTAG did not work for older 1st gen. OBs. Introduced with V6.98a. Fixed.
- J-Link-OB-K22-Cortex-M: JTAG did not work for older 1st gen. OBs. Introduced with V6.98a. Fixed.
GDB Server
- Device selection dialog: Some core names were displayed as "???". Fixed.
J-Flash
- "Create New Project" dialog: After selecting a RX72M device (e.g. Renesas R5F572MN), the "Target interface" drop-down list did not contain any entries. Fixed.
- Device selection dialog: Some core names were displayed as "???". Fixed.
J-Flash Lite
- Device selection dialog: Some core names were displayed as "???". Fixed.
J-Mem
- Device selection dialog: Some core names were displayed as "???". Fixed.
RTT Viewer
- Device selection dialog: Some core names were displayed as "???". Fixed.
SWO Viewer
- Device selection dialog: Some core names were displayed as "???". Fixed.
Version V6.98a (2021-03-05)
Configurator
- Windows: Removed unnecessary help button from certain GUI dialogs.
DLL
- When trying to connect to an unsupported core, the user was correctly informed that the core was not supported, but the connect was attempted anyway. This could cause the probe to crash. Fixed.
- Windows: Connecting to multiple J-Links failed for some J-Links that are composite devices (e.g. J-Link + VCOM) and which used WinUSB as the USB driver (like the J-Link OB K22 SiFive does). Fixed.
DLL Updater
- Windows: Removed unnecessary help button from certain GUI dialogs.
Firmware
- Flasher ARM V4: NXP iMXRT1064: Flash programming in stand-alone mode did not work. Fixed.
- Flasher ARM V4: Under special circumstances, the reset did not work in stand-alone mode. Fixed.
- Flasher ARM V5: NXP iMXRT1064: Flash programming in stand-alone mode did not work. Fixed.
- Flasher ARM V5: Stand-alone mode: When using direct SPI programming, J-Flash SPI option "erase if required" was ignored and sectors were always erased. Fixed.
- Flasher ARM V5: Under special circumstances, the reset did not work in stand-alone mode. Fixed.
- Flasher Portable PLUS V1: NXP iMXRT1064: Flash programming in stand-alone mode did not work. Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: When using direct SPI programming, J-Flash SPI option "erase if required" was ignored and sectors were always erased. Fixed.
- Flasher Portable PLUS V1: Under special circumstances, the reset did not work in stand-alone mode. Fixed.
- Flasher PRO V4: NXP iMXRT1064: Flash programming in stand-alone mode did not work. Fixed.
- Flasher PRO V4: Under special circumstances, the reset did not work in stand-alone mode. Fixed.
- Flasher PRO V5: NXP iMXRT1064: Flash programming in stand-alone mode did not work. Fixed.
- Flasher PRO V5: Stand-alone mode: When using direct SPI programming, J-Flash SPI option "erase if required" was ignored and sectors were always erased. Fixed.
- Flasher PRO V5: Under special circumstances, the reset did not work in stand-alone mode. Fixed.
- Flasher PRO XL V5: Stand-alone mode: When using direct SPI programming, J-Flash SPI option "erase if required" was ignored and sectors were always erased. Fixed.
- J-Link-OB-K22-Cortex-A: Improved max. JTAG speed (and therefore also download speed) by 10% (3 MHz -> 3.33 MHz)
- J-Link-OB-K22-Cortex-M: Improved max. JTAG speed (and therefore also download speed) by 10% (3 MHz -> 3.33 MHz)
- J-Link-OB-K22-RISCV: Improved max. JTAG speed (and therefore also download speed) by 10% (3 MHz -> 3.33 MHz)
- J-Link-OB-K22-SiFive: Improved max. JTAG speed (and therefore also download speed) by 10% (3 MHz -> 3.33 MHz)
GDB Server
- Linux: RTOS plug-ins failed to load. Fixed.
- Windows: Removed unnecessary help button from certain GUI dialogs.
J-Flash
- Windows: Removed unnecessary help button from certain GUI dialogs.
J-Flash Lite
- Windows: Removed unnecessary help button from certain GUI dialogs.
J-Flash SPI
- For certain J-Link models there was a speed regression during programming an SPI flash directly. Introduced with V6.94b. Fixed.
- Windows: Removed unnecessary help button from certain GUI dialogs.
J-Mem
- Windows: Removed unnecessary help button from certain GUI dialogs.
Remote Server
- Windows: Removed unnecessary help button from certain GUI dialogs.
RTT Viewer
- Data logging: Starting data logging before connecting to a device did not work correctly. Fixed.
- Data logging: The data log paths are now saved over sessions.
- Data logging: When stopping data logging, a false error was shown. Fixed.
- Windows: Removed unnecessary help button from certain GUI dialogs.
SWO Viewer
- Windows: Removed unnecessary help button from certain GUI dialogs.
Version V6.98 (2021-03-02)
Configurator
- The "product name" column contained a wrong name for the Flasher Compact. Fixed.
DLL
- Added debug and (HyperFlash) flash programming support for NXP MIMXRT106SDVL6A .
- Added debug and (QSPI) flash programming support for NXP MIMXRT1177xxxA_M4 and MIMXRT1177xxxA_M7.
- Added QSPI flash programming support for Raspberry PI RP2040 series device.
- Maxim MAX3267x series device, Reset handling, fixed.
- NXP LPC1766: Verify after program could fail because the controller returned cached values. Fixed.
- NXP LPC1812 for devices with internal flash, SPI Flash as always present assumed, fixed.
- Renesas R7FA4W1: Erase failed due to flash bank info incorrectly containing a Q-SPI flash bank. Fixed.
- Silicon Labs RS9116 series: Device names did not match the devices actually supported for debugging. Corrected.
- STM32H7: IWDG was not frozen during debug, so it would reset the device while debugging when enabled. Fixed.
DLL Updater
- Clicking on "Retry" after a failed update always resulted in another failed update, even when the blocking process was closed. Fixed.
J-Flash
- Added new command line option "-updateprj" which can be used to force J-Flash to automatically update the project in case of device information specified in the project do not match with the device information from the used J-Flash version.
J-Link Package
- Linux: DEB and RPM package: J-Links already connected via USB before the initial installation of the J-Link Software were not accessible by non-root users. Fixed.
Remote Server
- Debug registers were not deinitialized on disconnect resulting in slighly higher power consumption. Fixed.
Version V6.96 (2021-02-18)
Configurator
- Added dialog allowing to unhide all dialogs where 'do not show again' was checked.
DLL
- Added debug and flash programming support for GigaDevice GD32E230Fx and GD32E230Gx.
- Added debug and flash programming support for Toshibas TMPM4KHFWAUG series.
- Added debug and flash programming support for Toshibas TMPM4KHFYAUG series.
- Added debug and internal flash programming support for AmbiqMicro Apollo4 series devices.
- Added debug and internal flash programming support for ST BLUENRG_LP series devices.
- Added debug support for Nuvoton M25x series devices.
- Added debug support for Raspberry RP2040 series device.
- Added internal flash and option byte programming support for ST STM32WLE4xx series devices.
- Added internal flash programming support for Maxim MAX32570 series device.
- Added internal flash programming support for Maxim MAX78000 series device.
- Added internal flash programming support for Nuvoton M031xx6x, M031xx8x, M031xxAx series devices.
- Added internal flash programming support for Nuvoton M032xx1x, M032xx2x, M032xx6x, M032xx8x, M032xxAx series devices.
- Added internal flash programming support for Nuvoton M25x series devices.
- Added internal flash programming support for ST STM32WL55xx, STM32WL54xx and STM32WLE5xx series devices.
- Added option byte programming support for ST STM32WL55xx, STM32WL54xx and STM32WLE5xx series devices.
- Added programming support for internal flash of GigaDevice GD32F350xx series devices.
- Added SPI flash programming support for ISSI IS25LP032 and IS25LP032A within SPIFI-Lib.
- Added support for some new Infineon (Cypress) PSoC 4100S Max series devices.
- Added support for some new PSoC64 secure MCUs.
- Flash programming mode: If implicit Prepare() of RAMCode changed CPU clock speed, DLL did not recognize this. Fixed.
- Improved flash programming speed for Nuvoton devices M03xxx, M05xxx, MINIxxx, NUCxxx and NANOxxx.
- Improved native pin trace initialization for NXP Kinetis K6x devices now do read modify writes instead of direct writes.
- Improved programming speed for internal flash of NXP S32K14x series devices.
- Infineon TLE986x/TLE987x series: Added Re-Try bit support for flash-programming (Disturb handling and program retry).
- MTB Trace, improved log message formatting.
- Removed leftover third party support from JLinkDevices.xml package (NXP i.MXRT500, Renesas RZN1 - both are already officially supported).
- Renesas RA: Added debug and flash programming support for RA2E1 family of devices.
- Renesas RA: Added debug and flash programming support for RA4M2 family of devices.
- Silicon Labs RS9116 series: Added debug- and flash-programming (internal) support.
- STM32G4: CAT2 devices were always detected as protected, even when they were not actually protected. Fixed.
Firmware
- Flasher ARM V5: Direct SPI programming: Added firmware logic to speed up PC-driven programming via J-Flash SPI.
- Flasher ARM V5: Direct SPI programming: Flashes with 512-byte pages were not handled correctly and threw and error on programming. Fixed.
- Flasher ARM V5: Direct SPI programming: Programming speed in PC-driven mode now up to par with stand-alone mode.
- Flasher ARM V5: Static IP configuration did not work properly in setups with switches that do MAC authentication (expect J-Link to send the first packet on its own even if a static IP is used). Fixed.
- Flasher PRO V5: Direct SPI programming: Added firmware logic to speed up PC-driven programming via J-Flash SPI.
- Flasher PRO V5: Direct SPI programming: Flashes with 512-byte pages were not handled correctly and threw and error on programming. Fixed.
- Flasher PRO V5: Direct SPI programming: Programming speed in PC-driven mode now up to par with stand-alone mode.
- Flasher PRO V5: Static IP configuration did not work properly in setups with switches that do MAC authentication (expect J-Link to send the first packet on its own even if a static IP is used). Fixed.
- Flasher PRO XL V5: Direct SPI programming: Added firmware logic to speed up PC-driven programming via J-Flash SPI.
- Flasher PRO XL V5: Direct SPI programming: Flashes with 512-byte pages were not handled correctly and threw and error on programming. Fixed.
- Flasher PRO XL V5: Direct SPI programming: Programming speed in PC-driven mode now up to par with stand-alone mode.
- Flasher PRO XL V5: Static IP configuration did not work properly in setups with switches that do MAC authentication (expect J-Link to send the first packet on its own even if a static IP is used). Fixed.
- J-Link EDU Mini V1: SWD multi-drop was not supported by accident. This caused some devices to be not supported (e.g. the Raspberry RP2040 series devices). Fixed.
- J-Link PRO V4: IP: Static IP configuration did not work properly in setups with switches that do MAC authentication (expect J-Link to send the first packet on its own even if a static IP is used). Fixed.
- J-Link PRO V5: IP: Static IP configuration did not work properly in setups with switches that do MAC authentication (expect J-Link to send the first packet on its own even if a static IP is used). Fixed.
- J-Link PRO V5: VCOM start bit detection, fixed.
- J-Link ULTRA+ V5: VCOM start bit detection, fixed.
GDB Server
- Added nickname to -listprobes USB command in JLinkGDB ServerCL
J-Flash
- TI RM42L432: Blank check always returned an error for the OTP flash sector. Changed to report a warning that check blank is skipped for this sector instead.
- When trying to close an open data window after connecting to a target device with a Renesas RX core, J-Flash would crash. Fixed.
J-Flash SPI
- Added SPI flash programming support for ISSI IS25LP032 and IS25LP032A.
- Added support for different transfer mode configurations when using quad mode.
- Changed default speed for new projects from 12000 to 50000 kHz.
- Changed default to "compare = disabled" for new projects.
- Cypress S25FL512S: Improved erase + programming speed.
- Cypress S25FL512S: When using auto detection, sector size and page size was incorrectly detected. Fixed.
- Implemented quad config auto-detection for GigaDevice GD25Q128E.
J-Flash SPI CL
- Changed default speed for new projects from 12000 to 50000 kHz.
J-Link Package
- Linux: Some distributions (like Mint 20 for example) did not detect executables (J-Link Commander, J-Flash, ...) as executables in the GUI so they could not be started by double-clicking them. Introduced with V6.92. Fixed.
Version V6.94d (2021-02-12)
DLL
- If J-Link was connected for the first time, default enumeration type was not changed from USB0 to RealSN. Introduced in V6.88. Fixed.
- NXP iMXRT1024: Improved the reset strategy to perform a halt after bootloader.
- ST STM32G47xx and STM32G4xx restoration of clock settings for flash programming algorithm, fixed.
- ST STM32MP15xx: Connect via JTAG did not work. Fixed.
J-Flash
- Project information: "Clock speed" value was displayed in Hz with kHz as unit. Fixed.
J-Run
- Host-formatted semihosting did not output all data before exit wildcard. Fixed.
SWO Viewer
- When connecting to a device without specifying the SWO frequency, 1 kHz was used instead of auto-detection. Introduced in V6.88. Fixed.
Version V6.94c (2021-02-05)
DLL
- Flash bank entries for Renesas RZ/A2M series devices, fixed.
- Flash banks that reached to the end of address space (0xFFFFFFFF) (e.g. on Renesas RX65N) could not be erased via erase range because of a detection issue. Fixed.
- JTAG chain detection for NXP iMXRT117x series devices, fixed.
- NXP iMXRT600: The default reset sequence performed for RT600 series devices did not consider the resettype overwrite (core / reset pin). Fixed.
- Open Flashloader: Special return value to skip verify after program was not considered but evaluated as error. Fixed.
Firmware
- Flasher ARM V4: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- Flasher ARM V5: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- Flasher Portable PLUS V1: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- Flasher PRO V4: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- Flasher PRO V5: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link EDU Mini V1: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link EDU Mini V1: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link EDU/BASE/PLUS V10: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link EDU/BASE/PLUS V11: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link EDU/BASE/PLUS V11: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link EDU/BASE/PLUS V9: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link Lite Cortex-M V9: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link Lite V9: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB K22 Cortex-A: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB K22 Cortex-M: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB K22 NordicSemi: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB K22 SiFive: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB S124: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB SAM3U128 V2 NordicSemi: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB SAM3U128 V2: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB SAM3U128 V3: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB SAM3U128: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB STM32F072 128KB Cortex-M: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link OB STM32F103: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link PRO V4: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link PRO V4: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link PRO V5: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link PRO V5: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link ULTRA+ V4: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link ULTRA+ V4: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link ULTRA+ V5: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link ULTRA+ V5: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link WiFi V1: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Link WiFi V1: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Link-OB-K22-RISCV: RISC-V: IBEX core: Reading / writing memory did not work properly because J-Link did not handle 32-bit only system bus implementation properly. Fixed.
- J-Trace PRO V1 Cortex-M: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Trace PRO V2 Cortex: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
- J-Trace PRO V2 CortexM: Some devices were not handled correctly when connecting over the J-Link Remote Server. Fixed.
J-Flash
- Removed GLIBC 2.29 dependency (made executable not usable under Ubuntu 18.04)
J-Flash SPI
- Removed GLIBC 2.29 dependency (made executable not usable under Ubuntu 18.04)
J-Mem
- Removed GLIBC 2.29 dependency (made executable not usable under Ubuntu 18.04)
J-Run
- Added fallback: Determining RTT control block via symbol table of ELF file if no debug information is available.
- Formatting of floats might have been wrong. Fixed.
- Matching output with exit wildcard string did not work with smeihosting. Fixed.
RTT
- LPC540 and LPC54S0: Autodetection did not work correctly. Fixed.
- The RTT modules produced compilation warnings under GCC with optimization -O2 and -O3. Fixed.
RTT Viewer
- "All Terminals" tab: When a line was bigger than the viewable area it could happen that the last characters were not shown correctly. Fixed.
Version V6.94b (2021-01-26)
Configurator
- Log: Double clicking the mouse wheel selected a word. Fixed.
- Log: Holding down the mouse wheel selected text. Fixed.
- Log: Linux: Some characters were merged into ligatures (e.g. "ff", "fl", "fi", ... turned into a single character). This could cause alignment issues. Fixed.
- Log: Linux: Switched default fixed-width font to "DejaVu Sans Mono".
- Log: Linux: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: macOS: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: Trying to select a word (double click) in the log after it has been cleared caused a seemingly random sequence of characters to be selected. Fixed.
- Log: When selecting many characters (> 512) in a single line, the application could crash. Fixed.
- Log: When selecting text (over and over), the process would take up more and more RAM. Fixed.
DLL
- Cypress PSoC6: Applied some minor bug fixes.
- QSPI Flash programming memory-mapped read mode for SiFive FE310 series device, fixed.
- Renesas RA6M4: QSPI flash programming did not work. Introduced in V6.92. Fixed.
- TI RM42L432: Size of OTP flash sector was incorrect (2 KB instead of 1 KB). Fixed.
Firmware
- Flasher ARM V5: Stand-alone programming of SPI flashes did not abort when verifying the SPI Flash ID failed. Fixed.
- Flasher PRO V4: Universal Flashloader: Programming of Microchip PIC18 series devices could fail since last update. Fixed.
- Flasher PRO V5: Added support for different transfer mode configurations when using quad mode.
- Flasher PRO V5: Stand-alone programming of SPI flashes did not abort when verifying the SPI Flash ID failed. Fixed.
- Flasher PRO V5: UART programming (e.g. RL78 targets) did not work correctly. Fixed.
- Flasher PRO XL V5: Added support for different transfer mode configurations when using quad mode.
- J-Link-OB-K22-SiFive: Controlling RTS / CTS lines of virtual COM port did not work properly which could cause ESP32 firmware updates to fail. Fixed.
GDB Server
- Log: Double clicking the mouse wheel selected a word. Fixed.
- Log: Holding down the mouse wheel selected text. Fixed.
- Log: Linux: Some characters were merged into ligatures (e.g. "ff", "fl", "fi", ... turned into a single character). This could cause alignment issues. Fixed.
- Log: Linux: Switched default fixed-width font to "DejaVu Sans Mono".
- Log: Linux: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: macOS: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: Trying to select a word (double click) in the log after it has been cleared caused a seemingly random sequence of characters to be selected. Fixed.
- Log: When selecting many characters (> 512) in a single line, the application could crash. Fixed.
- Log: When selecting text (over and over), the process would take up more and more RAM. Fixed.
J-Flash
- Improved error message if data did not fit into selected sectors.
- Log: Double clicking the mouse wheel selected a word. Fixed.
- Log: Holding down the mouse wheel selected text. Fixed.
- Log: Linux: Some characters were merged into ligatures (e.g. "ff", "fl", "fi", ... turned into a single character). This could cause alignment issues. Fixed.
- Log: Linux: Switched default fixed-width font to "DejaVu Sans Mono".
- Log: Linux: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: macOS: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: Trying to select a word (double click) in the log after it has been cleared caused a seemingly random sequence of characters to be selected. Fixed.
- Log: When selecting many characters (> 512) in a single line, the application could crash. Fixed.
- Log: When selecting text (over and over), the process would take up more and more RAM. Fixed.
- macOS: On systems running macOS Big Sur, variable-width fonts were used instead of fixed-width fonts, causing data windows to look broken. Fixed.
- When trying to download config + data file to a Flasher ATE with a project which does not specify the desired modules, a message box appeared with the same message three times. Fixed.
J-Flash Lite
- Log: Double clicking the mouse wheel selected a word. Fixed.
- Log: Holding down the mouse wheel selected text. Fixed.
- Log: Linux: Some characters were merged into ligatures (e.g. "ff", "fl", "fi", ... turned into a single character). This could cause alignment issues. Fixed.
- Log: Linux: Switched default fixed-width font to "DejaVu Sans Mono".
- Log: Linux: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: macOS: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: Trying to select a word (double click) in the log after it has been cleared caused a seemingly random sequence of characters to be selected. Fixed.
- Log: When selecting many characters (> 512) in a single line, the application could crash. Fixed.
- Log: When selecting text (over and over), the process would take up more and more RAM. Fixed.
- Some log messages were printed without line breaks inbetween. Fixed.
J-Flash SPI
- Log: Double clicking the mouse wheel selected a word. Fixed.
- Log: Holding down the mouse wheel selected text. Fixed.
- Log: Linux: Some characters were merged into ligatures (e.g. "ff", "fl", "fi", ... turned into a single character). This could cause alignment issues. Fixed.
- Log: Linux: Switched default fixed-width font to "DejaVu Sans Mono".
- Log: Linux: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: macOS: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: Trying to select a word (double click) in the log after it has been cleared caused a seemingly random sequence of characters to be selected. Fixed.
- Log: When selecting many characters (> 512) in a single line, the application could crash. Fixed.
- Log: When selecting text (over and over), the process would take up more and more RAM. Fixed.
- macOS: On systems running macOS Big Sur, variable-width fonts were used instead of fixed-width fonts, causing data windows to look broken. Fixed.
- macOS: Trying to execute "Erase Chip" could fail when "Auto detect flash" was selected in the project settings. Fixed.
- macOS: Trying to program an SPI flash could crash J-Flash SPI. Fixed.
- When using different Flash settings than determined by J-Flash SPI's auto-detection, the settings were replaced with those determined by J-Flash SPI. Fixed.
J-Mem
- macOS: On systems running macOS Big Sur, variable-width fonts were used instead of fixed-width fonts, causing the data window to look broken. Fixed.
Remote Server
- Log: Double clicking the mouse wheel selected a word. Fixed.
- Log: Holding down the mouse wheel selected text. Fixed.
- Log: Linux: Some characters were merged into ligatures (e.g. "ff", "fl", "fi", ... turned into a single character). This could cause alignment issues. Fixed.
- Log: Linux: Switched default fixed-width font to "DejaVu Sans Mono".
- Log: Linux: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: macOS: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: Trying to select a word (double click) in the log after it has been cleared caused a seemingly random sequence of characters to be selected. Fixed.
- Log: When selecting many characters (> 512) in a single line, the application could crash. Fixed.
- Log: When selecting text (over and over), the process would take up more and more RAM. Fixed.
RTT Viewer
- Double clicking the mouse wheel selected a word. Fixed.
- Holding down the mouse wheel selected text. Fixed.
- Linux: Some characters were merged into ligatures (e.g. "ff", "fl", "fi", ... turned into a single character). This could cause alignment issues. Fixed.
- Linux: Switched default fixed-width font to "DejaVu Sans Mono".
- Linux: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- macOS: On systems running macOS Big Sur, variable-width fonts were used instead of fixed-width fonts. Fixed.
- macOS: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Trying to select a word (double click) in a terminal after it has been cleared caused a seemingly random sequence of characters to be selected. Fixed.
- When selecting many characters (> 512) in a single line, the application could crash. Fixed.
- When selecting text (over and over), the process would take up more and more RAM. Fixed.
SWO Viewer
- Log: Double clicking the mouse wheel selected a word. Fixed.
- Log: Holding down the mouse wheel selected text. Fixed.
- Log: Linux: Some characters were merged into ligatures (e.g. "ff", "fl", "fi", ... turned into a single character). This could cause alignment issues. Fixed.
- Log: Linux: Switched default fixed-width font to "DejaVu Sans Mono".
- Log: Linux: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: macOS: When selecting text, the selection would sometimes appear at the wrong position. Fixed.
- Log: Trying to select a word (double click) in the log after it has been cleared caused a seemingly random sequence of characters to be selected. Fixed.
- Log: When selecting many characters (> 512) in a single line, the application could crash. Fixed.
- Log: When selecting text (over and over), the process would take up more and more RAM. Fixed.
Version V6.94a (2021-01-14)
Commander
- 'setbp' displayed handle always 0. Fixed.
- Added alias 'clearbp' for 'clrbp'
- Added alias 'quit' for 'q'
- Added alias 'write1' for 'w1'
- Added alias 'write2' for 'w2'
- Added alias 'write4' for 'w4'
Configurator
- Removed "Reset config" option from context menu.
DLL
- macOS Apple M1: Some calculations of time were incorrect (e.g. Flash programming speed calculation). Fixed.
- macOS: Some dialogs changed their font after being clicked. Fixed.
- Renesas R7S721000 could not be selected. Fixed.
- RISC-V: Debugging cores that are based on the V0.11 debug spec. failed with error "The connected J-Link does not support selecting another hart/core than 0 for RISC-V" even if hart 0 was debugged. Fixed.
RTT
- Sometimes, when doing a source-level step over a printf(), SEGGER_RTT_Write(), ... in the debugger, the RTT was not available in the RTT window after the step but only at the next continue/step/.... Fixed.
Version V6.94 (2021-01-08)
DLL
- Added aliases for NXP MKM14Z64xxx5, MKM14Z128xxx5, MKM33Z64xxx5, MKM33Z128xxx5, MKM34Z128xxx5 and MKM34Z256xxx5 series devices.
- Added debug support for Toshiba TMPM4M series (e.g. TMPM4MLFWAFG).
- Added debug support for ABOV A34M41x series devices.
- Added debug support for some new Toshiba TMPM4K devices (e.g. TMPM4KLFWAFG).
- Added flash programming support for ABOV A34M41x series devices.
- Added flash programming support for some Microchip PIC32MZ DAK/DAL/DAR/DAS devices.
- Added flash programming support for some new Toshiba TMPM4K devices (e.g. TMPM4KLFWAFG).
- Added flash programming support for Toshiba TMPM4M series (e.g. TMPM4MLFWAFG).
- Added J-Link support (debug + flash programming) for ST STM32G0B1xC/xE devices.
- Added J-Link support (debug + flash programming) for ST STM32G0C1xC/xE devices.
- Added support for some new ST STM32H750 devices (STM32H753AI and STM32H750ZB).
- Holtek HT32F125x: Flash-programming did not work correctly under some circumstances. Fixed.
- MindMotion MM32xx series: Flash-programming did not work correctly under some circumstances. Fixed.
- NXP i.MXRT101x QSPI: Flash-breakpoints did not work correctly under certain conditions. Fixed.
- NXP i.MXRT102x QSPI: Flash-breakpoints did not work correctly under certain conditions. Fixed.
- Renesas RA6M4 devices: Added native ETB support.
- SiFive Nexus trace: Jumplocation of direct conditional branches was calculated incorrectly under certain circumstances. Fixed.
- Silicon Labs EFM32GG (series 0): User Data Page and Lockbits Page size was incorrect (4 KB while it's actually 2 KB). Fixed.
- Xilinx UltraScale+ series (XCZUxxx devices): Connecting to Cortex-R5 core could fail on first try. Fixed.
DLL Updater
- Added support for IAR EW 64bit version.
Firmware
- Flasher ARM V4: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- Flasher ARM V5: Direct SPI flash programming (config downloaded via J-Flash SPI) did not work in stand-alone mode. Fixed.
- Flasher ARM V5: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- Flasher PRO V4: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- Flasher PRO V5: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- Flasher PRO XL V5: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- J-Link EDU Mini V1: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- J-Link EDU/BASE/PLUS V10: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- J-Link EDU/BASE/PLUS V11: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- J-Link PRO V4: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- J-Link ULTRA+ V4: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- J-Link WiFi V1: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- J-Trace PRO V2 Cortex: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
- J-Trace PRO V2 CortexM: J-Flash SPI: Under very special circumstances, USB communication on Program operation could hang. Fixed.
J-Flash
- Improved log messages in case downloading files failed.
- Improved speed calculation for "Target -> Test -> Test speed...".
- Linux: PCode files failed to download when trying to download .cfg and .dat file to Flasher. Fixed.
- macOS: PCode files failed to download when trying to download .cfg and .dat file to Flasher. Fixed.
J-Flash SPI
- When downloading a configuration to a Flasher that does not support stand-alone SPI programming, there was no error message. Fixed.
Version V6.92 (2020-12-18)
Commander
- ARMv8M (Cortex-M23 and Cortex-M33): Security extension registers were displayed incorrectly. Fixed.
Control Panel
- CPU register tab: 64-bit registers (e.g. ARM NEON D16-D31) were not handled correctly (only 32-bit were shown, valid state was not updated correctly). Fixed.
- Flash download during debug: Added possibility to select chip erase instead of sector erase, to speed up erase process for some devices.
DLL
- Added QSPI flash programming support for STM32H74x and STM32H75x series devices.
- Device selection dialog could cause crash when hitting 'x' instead of cancel button. Fixed.
- Improved QSPI programming speed for iMXRT5xx series device.
- Renesas RA6M4: Added link to reference wiki article to supported devices table on website. https://wiki.segger.com/J-Link_Renesas_RA6M4
- RISC-V: Andestech N22 (RV32 core) was missing in the list of supported devices/cores. Fixed.
DLL Updater
- MPLAB X: MPLAB X V4.45 onwards could not be detected anymore, because the registry path was changed by Microchip. Fixed.
Firmware
- J-Trace PRO V2 Cortex: HSS: Added support for higher sampling frequencies (same frequencies as J-Link PRO V5 supports)
- J-Trace PRO V2 Cortex: If no target was connected, J-Trace reported 0.0xxV for VTref instead of 0V. Fixed.
- J-Trace PRO V2 CortexM: HSS: Added support for higher sampling frequencies (same frequencies as J-Link PRO V5 supports)
- J-Trace PRO V2 CortexM: If no target was connected, J-Trace reported 0.0xxV for VTref instead of 0V. Fixed.
GDB Server
- ARMv8M (Cortex-M23 and Cortex-M33): Security extension registers were displayed incorrectly. Fixed.
- Cortex-M: PRIMASK and FAULTMASK register returned incorrect values. Fixed.
- Cortex-M: Writing PRIMASK and FAULTMASK did not work properly. Fixed.
- Extended monitor regs command to also display the security extension register for ARMv8M based MCUs.
J-Link Package
- Linux ARM 32-bit: Removed GLibc 2.28 dependency from SEGGER executables and libraries as these potentially cause problems on older Raspberry Pis.
- Linux ARM: Added GUI applications (J-Flash, J-Flash Lite, ...)
Version V6.90a (2020-12-14)
DLL
- AutoChips AC7801x: Added flash-programming support for the option byte area.
- AutoChips AC7801x: Part number AC78016MDQI was missing. Corrected.
- AutoChips AC7801x: System clock was not configured correctly during a flash-programming operation. AC78016x series was not affected. Fixed.
- SoC-600: Under special circumstances, the specified AP to use and AP base address was ignored. In such cases, connect could fail. Fixed.
Firmware
- Flasher ARM V5: Universal Flashloader: Renesas RH850: Flash programming via UART could fail for certain baud rates. Introduced with V6.90. Fixed.
- Flasher ARM V5: Universal Flashloader: Renesas RL78: Flash programming via UART could fail for certain baud rates. Introduced with V6.90. Fixed.
- Flasher PRO V5: Universal Flashloader: Renesas RH850: Flash programming via UART could fail for certain baud rates. Introduced with V6.90. Fixed.
- Flasher PRO V5: Universal Flashloader: Renesas RL78: Flash programming via UART could fail for certain baud rates. Introduced with V6.90. Fixed.
- Flasher PRO XL V5: Universal Flashloader: Renesas RH850: Flash programming via UART could fail for certain baud rates. Introduced with V6.90. Fixed.
- Flasher PRO XL V5: Universal Flashloader: Renesas RL78: Flash programming via UART could fail for certain baud rates. Introduced with V6.90. Fixed.
Version V6.90 (2020-12-11)
Control Panel
- Commander: Added "ih" Command.
DLL
- Added debug support for Altera Arria 10 Cortex-A9 series device.
- Added debug support for Analog's ADSP-SC589 series.
- Added debug support for the AutoChips AC7801x series of devices.
- Added flash programming support for some new ST STM32H742xI/G (e.g. "STM32H742VI").
- Added flash programming support for some new ST STM32H743xI/G (e.g. "STM32H743VG").
- Added flash-programming support (internal flash) for the AutoChips AC7801x series of devices.
- Added internal data flash programming support for NXP MKE14F256xxx16, MKE14F512xxx16, MKE16F256xxx16, MKE16F512xxx16, MKE18F256xxx16, MKE18F512xxx16.
- Added internal flash programming support for On Semiconductor AXM0F243-64 series device.
- Cortex-AR (JTAG): Connect could fail in case of a APB-AP to use was specified by the user (AP map auto detection skipped) but no AP map was specified. Fixed.
- Cypress CYT3DL9BHA and CYT3DLABHA series device internal flash programming support for Cortex-M0 and Cortex-M7 added.
- Device names for ST STM32H723xx, STM32H725xx, STM32H730xx, STM32H733xx, and STM32H735xx series devices, fixed.
- Gigadevice GD32VF103 series (RV32 based): Added support for flash programming (in debug sessions) via flash alias at address 0x0.
- Increased internal flash programming support for NXP LPC5569 series device from 608kB to 630.5kB internal flash.
- ON Semiconductor RSL10: Improved flash programming speed by factor 3.6 (up to 380 KB/s).
- Renesas RZ A1L: Connect failed. Introduced in V6.88. Fixed.
- RISC-V: Added support for Andestech RV32 cores: A25MP, A27, A27L2, D25F, D45, N25, N25F, N45
- RISC-V: Added support for Andestech RV64 cores: A45, AX25, AX25MP, AX45, AX27, AX27L2, NX25F, NX27V, NX45
- RISC-V: Implemented detection of "enter debug mode reason/cause" (MOE).
- Unlocking did not work correctly for NXP KE02 and KE06 series devices. Fixed.
Firmware
- Flasher PRO V5: PDI and SWIM target interface did not work correctly in Universal Flashloader. Fixed.
J-Flash
- When running multiple J-Flash instances in parallel, it could sometimes happen that a J-Flash instance failed when trying to open or save the global settings file. Fixed.
J-Flash SPI
- Added support for QSPI programming.
- When running multiple J-Flash SPI instances in parallel, it could sometimes happen that a J-Flash SPI instance failed when trying to open or save the global settings file. Fixed.
J-Flash SPI CL
- Added support for QSPI programming.
Remote Server
- For some devices (e.g. SiLabs EFM32GG series) the error "Unknown EMU command #12 received" was thrown. Fixed.
RTT Logger
- Added connection over IP via command line.
STM32 Utility
- Added handling for all STM32L4xxxx devices.
Version V6.88c (2020-12-04)
Commander
- Under special circumstances available target interfaces were not shown correctly. Fixed.
DLL
- Cypress CYT3BBxx, CYT4BBxx and CYT4BFxx series devices internal flash programming via Cortex-M7, fixed.
- Cypress CYT3DLBBHA series device code and work flash size, fixed.
- NXP MKE04Z8 series: Flash-programming did not work (too less RAM reported by the DLL). Fixed.
- NXP MKE04Z8 series: Improved flash-programming speed by about a factor of four.
- Renesas RX66N: Core ID mismatch was reported (warning). Fixed
- RISC-V: Connecting to RV64 based cores from Andestech did not work properly. Fixed.
- SiFive Nexus trace: Under certain circumstances to many instructions were analyzed on step over. Fixed.
GDB Server
- Incorrect watchpoint address reported in case of a watch point event occurred. Fixed.
Version V6.88b (2020-11-27)
CCS Plugin
- TI TMS570LS: Debug session did not start properly. Fixed.
Control Panel
- RTT tab: When sending data via the RTT tab an error message was shown. Fixed.
DLL
- Adapted unlock for both cores (APP and NET core) of Nordic nRF5340_xxAA series device for new hardware revision.
- Added debug support for Renesas RA2L1 series.
- Added debug support for Renesas RA4M3 series.
- Added flash programming support for Renesas RA2L1 series.
- Added flash programming support for Renesas RA4M3 series.
- Cortex-M: In case J-Link was low on memory (especially J-Link OBs) sometimes the false positive error message "the connected J-Link does not support CoreSight SoC-600 DAP setups" was shown. Fixed.
- Cortex-M: In case J-Link was low on memory (especially J-Link OBs) sometimes the false positive error message "the connected J-Link does not support SWD multi-drop" was shown. Fixed.
- Cortex-M: In case J-Link was low on memory (especially J-Link OBs) sometimes the false positive error message "the connected J-Link does not support the ARMv8-M architecture" was shown. Fixed.
- Cortex-M: In case J-Link was low on memory (especially J-Link OBs) sometimes the false positive error message "the connected J-Link does not support the connected core ..." was shown. Fixed.
- Improved removal of of zombie connections in J-Link if a previous debug session was not shutdown properly.
- Improved STM32H7 connect sequence for cases where sleep modes or watch dogs may be active.
- NXP iMX7D: When programming QSPI flash, the original QSPI clock configuration was not restored correctly after programming. Fixed.
- NXP LPC55S69: Connect to devices without a valid application could fail. Fixed.
- Renesas RX64M: Flash programming did not work for big endianness. Introduced with V6.88. Fixed.
- Renesas RX71M: Flash programming did not work for big endianness. Introduced with V6.88. Fixed.
- ST STM32Gxx series devices restoriation of flash lock bits after erasing/programming internal flash, fixed.
Firmware
- Flasher Portable PLUS V1: The progress bar did not work correctly for large images. Fixed.
RTT Logger
- Application did not terminate when a non-decimal value was passed for the command line "-SelectEmuBySN". Fixed.
Version V6.88a (2020-11-18)
Control Panel
- RAWTrace tab: Improved error handling.
DLL
- DAPLink / CMSIS-DAP support: Debug session could crash because of NULL pointer dereference on memory reads. Introduced in V6.84. Fixed.
- Improved trace cache handling for downloads smaller than 4 bytes. Fixed.
- NXP iMX7D: QSPI flash programming did not work under very specific conditions. Fixed.
- Renesas RX64M: Under special circumstances, flash programming failed. Fixed.
- Renesas RX71M: Under special circumstances, flash programming failed. Fixed.
- STM32 devices: Unlock dialog: Information text was not matching the check box description. Fixed.
- STRACE: Under special circumstances, ring buffer for backtrace data did not work properly so too much memory was allocated (reaching the 1.8 GB limit on 32-bit systems) which could make the calling process crash. Fixed.
- Updated Nuvoton device data base ("Nuvoton_ARM9_Series").
Manual
- UM08001: SEGGER_RTT_ConfigDownBuffer and SEGGER_RTT_ConfigUpBuffer: In the "Example" section both functions were falsely named. Fixed.
Version V6.88 (2020-11-12)
Commander
- Changed representation of available memory zones.
- mem16/mem32 commands did not work properly for zoned memory accesses on big endian target devices (e.g. AHB-AP access on a TI TMS570 series device). Fixed.
- w2/w4 commands did not work properly for zoned memory accesses on big endian target devices (e.g. AHB-AP access on a TI TMS570 series device). Fixed.
Control Panel
- "Log" tab: "Time spent in DLL" value did not work correctly. Fixed.
- Commander tab: "exec" commands could return an error even if there was none (uninitialized return value in subroutine). Fixed.
DLL
- Added 4byte address mode QSPI flash programming support NXP iMXRT1015 series devices.
- Added 4byte address mode QSPI flash programming support NXP iMXRT101x series devices.
- Added 4byte address mode QSPI flash programming support NXP iMXRT102x series devices.
- Added 4byte address mode QSPI flash programming support NXP iMXRT105x series devices.
- Added 4byte address mode QSPI flash programming support NXP iMXRT106x series devices.
- Added 4byte address mode QSPI flash programming support NXP iMXRT117x series devices.
- Added CoreSight SoC-600 support for ARMv7-A based cores (e.g. Cortex-A8, Cortex-A9, ...)
- Added CoreSight SoC-600 support for ARMv7-R based cores (e.g. Cortex-R4, Cortex-R5, ...)
- Added debug support for GigaDevice GD32E1 series devices (https://wiki.segger.com/GigaDevice_GD32E1).
- Added debug support for GigaDevice GD32E2 series devices (https://wiki.segger.com/GigaDevice_GD32E2).
- Added debug support for GigaDevice GD32E5 series devices (https://wiki.segger.com/GigaDevice_GD32E5).
- Added debug support for Microchip's PIC32MZ DA series.
- Added debug support for NXP MIMXRT633SFAWBR and MIMXRT685SFAWBR.
- Added debug support for some new ST STM32G4 series devices (e.g. STM32G491CC).
- Added flash programming support for GigaDevice GD32E1 series devices (https://wiki.segger.com/GigaDevice_GD32E1).
- Added flash programming support for GigaDevice GD32E2 series devices (https://wiki.segger.com/GigaDevice_GD32E2).
- Added flash programming support for GigaDevice GD32E5 series devices (https://wiki.segger.com/GigaDevice_GD32E5).
- Added flash programming support for Microchip's PIC32MZ DA series.
- Added flash programming support for Silicon Labs EFM8BB51 and EFM8BB52.
- Added flash programming support for some new ST STM32G4 series devices (e.g. STM32G491CC).
- Added internal flash programming support for ST STM32H723xx devices.
- Added internal flash programming support for ST STM32H725xx devices.
- Added internal flash programming support for ST STM32H730xx devices.
- Added internal flash programming support for ST STM32H733xx devices.
- Added internal flash programming support for ST STM32H735xx devices.
- Added new J-Link Command String: SetCSCompAccessType
- Added new J-Link Command String: SetETBRAMAccessType
- Added QSPI flash programming support for NXP MIMXRT633SFAWBR and MIMXRT685SFAWBR (QSPI connected to FlexSPI A).
- Added QSPI flash programming support for ST STM32H723xx series devices.
- Added QSPI flash programming support for ST STM32H725xx series devices.
- Added QSPI flash programming support for ST STM32H730xx series devices.
- Added QSPI flash programming support for ST STM32H733xx series devices.
- Added QSPI flash programming support for ST STM32H735xx series devices.
- Added SPI Flash programming for ISSI IS25LP01G SPI Flash device in SPIFI-Lib.
- Added SPI Flash programming for Macronix MX25UW51345G, MX25UW12845G, MX66LM1G45G, MX66UM2G45G, MX25UW6445G, MX25UM25645G SPI Flash devices in SPIFI-Lib.
- Added support for command string "TraceFile" to allow streaming of raw trace data into file.
- ARMv8-A/R based targets (Cortex-A53, Cortex-A57, ...): In case of heavily nested ROM tables (>= 8 nesting levels) a non-allocated buffer was accidentally freed. Fixed.
- Closing a debug session in a multi-core setup could result in a crash of the other sessions. Fixed.
- Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
- Cortex-A/R: Under special circumstances, the debug init was not aborted immediately on error but only after several follow-up errors occurred. Fixed.
- Device selection dialog: Removed "RAM Size" column.
- For ST STM32G491xx series devices internal flash programming and optionbyte programming, fixed.
- If command string "CORESIGHT_Configure" was passed, this was not always caught as an error. Fixed.
- J-Link Script Files: Added new function: JLINK_CPU_Go()
- J-Link Script Files: Added new function: JLINK_CPU_Halt()
- J-Link Script Files: Added new function: JLINK_CPU_IsHalted()
- J-Link Script Files: Added new function: JLINK_CPU_ReadReg()
- J-Link Script Files: Added new function: JLINK_CPU_WriteReg()
- NXP Kinetis series: J-Link inhibits debugger access to uninitialized FlexBus area to avoid system bus hangig (see Kinetis TRM for more info). This check sometimes let accesses through even if the FlexBus area was uninitialized. Fixed.
- NXP LPC55S0x/LPC550x series: Added debug and flash-programming support.
- NXP LPC55S6x: Added debug support for the second Cortex-M33 core.
- Renesas RX66N / RX66T: Programming of option-setting memory did not work in big endian mode. Fixed.
- Renesas RX66N: Wrong flash algo was associated with data flash bank. Fixed.
- Renesas RX66N: Wrong flash algo was associated with program flash bank. Fixed.
- Renesas RX72M / RX72T: Programming of option-setting memory did not work in big endian mode. Fixed.
- RISC-V: On a RISC-V with no trigger units usable as hardware breakpoints, garbage was detected during connect. Fixed.
- Script files: On 64-bit systems, CPU_GetUnlockKey() could crash because incorrect pointer arithmetic. Fixed.
- Script files: When calling JLINK_MEM_Fill() function with another fill value than 0x00, the fill value was ignored. Fixed.
- Script files: When calling JLINK_MEM_Preserve() function with > 1 MB ranges, a crash could happen. Fixed.
- SiLabs EFM8 series: Instruction set simulation did not detect failed memory accesses for PUSH and POP correctly. Fixed.
- ST STM32WB55xx series: Renamed devices: Wildcard device names were misleading. Corrected.
- STM32G4 series device: Added unlock/unsecure behavior if Write/Read protection is set.
- STM32H7A series device: Added native SWO support.
- SWO: Setting an SWO speed that caused > 3% deviation between target sending speed and J-Link sampling speed was not always caught as an error. Fixed.
- Trace flow analysis for ETMv3.3 or older could fail under certain circumstances. Fixed.
- Trace on Armv7AR: Improved analysis of BX/BXL (register) instructions.
- Updated documentation for APEXMIC APM32F103xx series device family(https://wiki.segger.com/APM32F103xx)
- Updated supported device list for all Qorvo based devices.
DLL Updater
- Added a warning message box when any DLL could not be updated.
Firmware
- Flasher ARM V4: Stack of RAMCode was not write-initialized by Flasher which could cause problems on devices with ECC RAM (e.g. NXP S32K116). Fixed.
- Flasher ARM V5: ARM7/9 based devices: Adaptive clocking did not work properly. Fixed.
- Flasher ARM V5: Stack of RAMCode was not write-initialized by Flasher which could cause problems on devices with ECC RAM (e.g. NXP S32K116). Fixed.
- Flasher ARM V5: Universal Flashloader: When programming a device containing multiple flash banks and there were two or more banks with no address gap in between, flashing could fail. Fixed.
- Flasher Portable PLUS V1: Flash programming did not work in stand-alone mode for PPC devices. Fixed.
- Flasher Portable PLUS V1: Stack of RAMCode was not write-initialized by Flasher which could cause problems on devices with ECC RAM (e.g. NXP S32K116). Fixed.
- Flasher Portable PLUS V1: Universal Flashloader: When programming a device containing multiple flash banks and there were two or more banks with no address gap in between, flashing could fail. Fixed.
- Flasher PRO V4: Stack of RAMCode was not write-initialized by Flasher which could cause problems on devices with ECC RAM (e.g. NXP S32K116). Fixed.
- Flasher PRO V5: ARM7/9 based devices: Adaptive clocking did not work properly. Fixed.
- Flasher PRO V5: Flash programming did not work in stand-alone mode for PPC devices. Fixed.
- Flasher PRO V5: Stack of RAMCode was not write-initialized by Flasher which could cause problems on devices with ECC RAM (e.g. NXP S32K116). Fixed.
- Flasher PRO V5: Universal Flashloader: Programming of Microchip PIC18xxx devices did not work properly. Fixed.
- Flasher PRO V5: Universal Flashloader: When programming a device containing multiple flash banks and there were two or more banks with no address gap in between, flashing could fail. Fixed.
- Flasher PRO XL V5: ARM7/9 based devices: Adaptive clocking did not work properly. Fixed.
- Flasher PRO XL V5: Stack of RAMCode was not write-initialized by Flasher which could cause problems on devices with ECC RAM (e.g. NXP S32K116). Fixed.
- Flasher PRO XL V5: Universal Flashloader: Programming of Microchip PIC18xxx devices did not work properly. Fixed.
- J-Link EDU Mini V1: Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
- J-Link EDU/BASE/PLUS V10: Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
- J-Link EDU/BASE/PLUS V11: Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
- J-Link PRO V4: Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
- J-Link PRO V5: ARM7/9 based devices: Adaptive clocking did not work properly. Fixed.
- J-Link ULTRA+ V4: Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
- J-Link ULTRA+ V5: ARM7/9 based devices: Adaptive clocking did not work properly. Fixed.
- J-Link WiFi V1: Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
- J-Trace PRO V2 Cortex: Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
- J-Trace PRO V2 CortexM: Cortex-A/R ARMv7: Added support for big endian APs (e.g. AHB-AP on TMS570 series devices)
GDB Server
- Added security extension register support for Cortex-M23 and Cortex-M33.
- Device selection dialog: Removed "RAM Size" column.
- FreeRTOS plugin: Added support for Cortex-M23.
J-Flash
- Closing the last opened data window caused J-Flash to not respond anymore. Introduced with V6.86e. Fixed.
- Device selection dialog: Removed "RAM Size" column.
- Project settings dialog: Flash tab: When displaying more than 200 sectors, the sector table was lagging behind while scrolling or (de-)selecting multiple rows. Fixed.
- Project settings dialog: Flash tab: When selecting multiple rows in the sector table and pressing <space> to disable/ enable them, the selection was cleared afterwards. Fixed.
- Stack of RAMCode was not write-initialized which could cause problems on devices with ECC RAM (e.g. NXP S32K116). Fixed.
J-Flash Lite
- Device selection dialog: Removed "RAM Size" column.
J-Flash SPI
- Added SPI Flash programming for ISSI IS25LP01G SPI Flash device.
- Added SPI Flash programming for Macronix MX25UW51345G, MX25UW12845G, MX66LM1G45G, MX66UM2G45G, MX25UW6445G, MX25UM25645G SPI Flash devices.
- Closing the last opened data window caused J-Flash SPI to not respond anymore. Introduced with V6.86e. Fixed.
- Device selection dialog: Removed "RAM Size" column.
J-Link Package
- Linux ARM: Command line applications did not run on older platforms (e.g. Raspberry Pis) because of certain dependencies. Fixed.
J-Mem
- Device selection dialog: Removed "RAM Size" column.
JTAG Load
- User input on stdin was broken under Windows. Introduced in V6.86e. Fixed.
RTT
- TI RM48 series: Enabled out-of-the-box RTT support on PC side. For target side, see: https://wiki.segger.com/RTT#RTT_on_Cortex-R_targets
- TI RM57 series: Enabled out-of-the-box RTT support on PC side. For target side, see: https://wiki.segger.com/RTT#RTT_on_Cortex-R_targets
RTT Logger
- User input on stdin was broken under Windows. Introduced in V6.86e. Fixed.
RTT Viewer
- Device selection dialog: Removed "RAM Size" column.
- Hotbar menu "Help": RTT Webpage: Opened a non existing webpage. Fixed, and changed to open RTT wiki page instead.
STM32 Utility
- Added support for STM32G0.
- Added support for STM32G4.
- User input on stdin was broken under Windows. Introduced in V6.86e. Fixed.
- Windows: Deleted notification message box, that device will be mass erased if security is active, since this information was also given via console.
STR91x Utility
- User input on stdin was broken under Windows. Introduced in V6.86e. Fixed.
SWO Viewer
- Configuration Dialog: Updated combobox so a user-defined SWO speed can be set, too.
- Device selection dialog: Removed "RAM Size" column.
Version V6.86g (2020-11-06)
Commander
- Trying to read/write memory via mem/w1/w2/w4 commands in an unknown memory zone did not throw an appropriate error message. Fixed.
- w1/w2/w4 commands did not throw an error in case writing memory returned an error. Fixed.
DLL
- Cypress PSoC4: If the J-Link did not support certain capabilities, the connect was aborted without performing a fallback. Fixed.
- Cypress PSoC4: In some rare cases, the connect could fail because of a too tightly set timeout. Fixed.
- Instruction trace on ARMv7 Cortex-A/R based targets did PC relative branches from Thumb -> ARM incorrectly if current PC was not 4-byte aligned. Fixed.
- PTM Trace: On a potential mode switch branch, instruction analysis always assumed that CPU mode changed, even if branch did not change modes. Fixed.
- PTM Trace: Thumb mode: If waypoint was emitted by PTM in the middle of a 32-bit Thumb instruction, analysis got out of sync. Fixed.
- RAWTRACE tab: Fixed and improved formatting. Fixed.
- ST STM32F769I-DISCOVERY: Programming the external QSPI flash did not work. Fixed.
- ST STM32F7: Under special circumstances, programming the external QSPI flash did not work. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: LDM instruction: Mode switches to Thumb mode were not detected correctly. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: LDR (immediate)instruction: Destination == PC (branch) were not detected properly. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: LDR (literal) instruction: Mode switches to Thumb mode were not detected correctly. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: LDR (register) instruction: Destination == PC (branch) were not detected properly. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: LDRB (literal) instruction: Mode switches to Thumb mode were not detected correctly. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: Mode switches via SUBS PC, LR were not detected correctly. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: POP instruction: Destination == PC (branch) were not detected properly. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: RFE instruction: Mode switches to Thumb mode were not detected correctly. Fixed.
- Trace on ARMv7 Cortex-A/R: ARM mode: Some instructions were incorrectly decoded as SUBS PC, LR. Fixed.
- Trace on ARMv7 Cortex-A/R: Thumb mode: BXJ instruction: Mode switches to ARM mode were not detected correctly. Fixed.
- Trace on ARMv7 Cortex-A/R: Thumb mode: LDM/LDMIA instruction: Mode switches to ARM mode were not detected correctly. Fixed.
- Trace on ARMv7 Cortex-A/R: Thumb mode: LDR (literal) instruction: Mode switches to ARM mode were not detected correctly. Fixed.
- Trace on ARMv7 Cortex-A/R: Thumb mode: POP instruction T2 & T3: Destination == PC (branch) were not detected properly. Fixed.
- Trace on ARMv7 Cortex-A/R: Thumb mode: POP instruction: Mode switches to ARM mode were not detected correctly. Fixed.
- Trace: Instruction trace on big endian BE32 Cortex-A/R based targets (e.g. TI TMS570 series) did not work properly. Fixed.
- XMC-Link / iMOTION Link: The firmware could hang / crash when trying to establish a connection to a unresponsive target. Fixed.
Firmware
- Flasher ARM V5: Flash programming did not work in stand-alone mode for some devices. Fixed.
- Flasher Portable PLUS V1: Flash programming did not work in stand-alone mode for some devices. Fixed.
- Flasher PRO V5: Flash programming did not work in stand-alone mode for some devices. Fixed.
- J-Link EDU Mini V1: Big endian targets (e.g. TI TMS570 series): Writing a big chunk of target memory that does not start 4-byte aligned could result in data being written incorrectly. Fixed.
- J-Link EDU/BASE/PLUS V10: Big endian targets (e.g. TI TMS570 series): Writing a big chunk of target memory that does not start 4-byte aligned could result in data being written incorrectly. Fixed.
- J-Link EDU/BASE/PLUS V11: Big endian targets (e.g. TI TMS570 series): Writing a big chunk of target memory that does not start 4-byte aligned could result in data being written incorrectly. Fixed.
- J-Link PRO V4: Big endian targets (e.g. TI TMS570 series): Writing a big chunk of target memory that does not start 4-byte aligned could result in data being written incorrectly. Fixed.
- J-Link ULTRA+ V4: Big endian targets (e.g. TI TMS570 series): Writing a big chunk of target memory that does not start 4-byte aligned could result in data being written incorrectly. Fixed.
- J-Link WiFi V1: Big endian targets (e.g. TI TMS570 series): Writing a big chunk of target memory that does not start 4-byte aligned could result in data being written incorrectly. Fixed.
- J-Trace PRO V2 Cortex: Big endian targets (e.g. TI TMS570 series): Writing a big chunk of target memory that does not start 4-byte aligned could result in data being written incorrectly. Fixed.
- J-Trace PRO V2 CortexM: Big endian targets (e.g. TI TMS570 series): Writing a big chunk of target memory that does not start 4-byte aligned could result in data being written incorrectly. Fixed.
J-Flash
- Data windows: When trying to jump to an address close to the end of the data window, the cursor was not set at the specified address. Fixed.
J-Flash SPI
- Data windows: When trying to jump to an address close to the end of the data window, the cursor was not set at the specified address. Fixed.
J-Link Package
- Linux: The .deb package Installed-Size value was not set correctly. Fixed.
RTT Viewer
- "Auto Scroll" was disabled by default, even though it should be enabled by default when using a Version with this feature for the first time. Fixed.
- Font size was reset when closing RTT Viewer. Fixed.
- When disconnecting while an input was the last line of the "All Terminals" terminal, "(Connection lost)" was printed in the same line as the input. Fixed.
Version V6.86f (2020-10-23)
Commander
- "Stepover" command did not catch it correctly if command is not supported for connected CPU. Fixed.
- "STraceRead" command did not catch errors correctly. Fixed.
- "STraceReadEx" command did not catch errors correctly. Fixed.
DLL
- AmbiqMicro Apollo3 Blue Plus: The flash beyond 1 MB was not erased in case of chip erase was used. Fixed.
- Connecting to Cortex-M based MCUs which expect CSW[30:30] == 0, did not work out-of-the-box. Fixed.
- Device protect check for nRF5340_xxAA_NET core of nRF5340 series device according to new hardware revision (v0.9.0 or newer), adapted. SECUREAPPROTECT bit only for nRF5340_xxAA_APP core implemented.
- RTT: STM32H7A/H7B: Updated auto search range to include all of the AXI SRAM.
Firmware
- Flasher ARM V5: Debugging / flashing via target interface cJTAG did not work correctly on TI devices. Fixed.
- Flasher ARM V5: The DHCP hostname was not set correctly. Fixed.
- Flasher Portable PLUS V1: In Universal Flashloader mode, messages were not reported correctly. Fixed.
- Flasher PRO V5: Debugging / flashing via target interface cJTAG did not work correctly on TI devices. Fixed.
- Flasher PRO V5: In Universal Flashloader mode, messages were not reported correctly. Fixed.
- Flasher PRO V5: The DHCP hostname was not set correctly. Fixed.
- Flasher PRO XL V5: Debugging / flashing via target interface cJTAG did not work correctly on TI devices. Fixed.
- J-Link PRO V5: Debugging / flashing via target interface cJTAG did not work correctly on TI devices. Fixed.
- J-Link ULTRA+ V5: Debugging / flashing via target interface cJTAG did not work correctly on TI devices. Fixed.
J-Flash
- External CFI NOR flashes: Use *no* target RAM option did not work. Fixed.
- Linux: When saving the project config (.cfg) file, .pex files were generated with a broken name at the wrong location and a directory with a broken name was created. Fixed.
- macOS: When saving the project config (.cfg) file, .pex files were generated with a broken name at the wrong location and a directory with a broken name was created. Fixed.
- When using a serial number list file (..._SNList.txt), J-Flash failed to prepare S/N data when accessing lines that started after the 64th character in the serial number list file. Introduced with V6.70.
J-Flash SPI
- When using a serial number list file (..._SNList.txt), J-Flash SPI failed to prepare S/N data when accessing lines that started after the 64th character in the serial number list file.
J-Link Package
- Installer: Update existing installation: If a J-Link application was still opened while updating it, this application was deleted after reboot. Fixed.
Version V6.86e (2020-10-16)
Control Panel
- CPU regs tab: Updated display format for floating-point numbers.
- Debug regs tab: Updated display format for floating-point numbers.
DLL
- Added SPI-Flash programming support for ST STM32L552xx and STM32L562xx series devices.
- Analog ADuCM355: Under special circumstances, flash programming did not work. Fixed.
- Cypress PSoC6 series: Under special circumstances, connect failed. Fixed.
- Cypress Traveo II: Using Flash BPs could cause errors in DLL. Fixed.
- External CFI flash based setups: Under special circumstances, flash programming failed. Fixed.
- Increased supported size of QSPI flashes to 64MB for external SPI Flash of iMXRT102x series devices.
- OTP flash banks for TI TMS570LS11xx and TMS570LS12xx series were accidentally flagged as erasable. Fixed.
- Sometimes when closing the application (e.g. J-Link Commander) when the "No emulator via USB found..." dialog was shown, any following GUI dialogs would not be displayed. Fixed.
- TI MSP432E series: When connecting for the first time we iterated over the complete possible AP map (index 0 - 255). Fixed.
DLL Updater
- Atollic TrueSTUDIO: Under some circumstances, it could happen, that the 64-bit version of the DLL was not updated correctly. Fixed.
J-Flash
- Linux: After opening a data file, a .conf file was created at /home/<user>/.config/Unknown Organization/ . Fixed.
J-Flash SPI
- Linux: After opening a data file, a .conf file was created at /home/<user>/.config/Unknown Organization/ . Fixed.
JTAG Load
- Added command line commands for emulator select via usb, ip and serialnumber "-USB", "IP" and "-SelectEmuBySN".
Manual
- UM08001: Chapter "Working with J-Link and J-Trace" Section "J-Link Command Strings" Added missing parameters of command "SetCFIFlash".
RTT Viewer
- Added "enable/disable auto-scroll" option for terminals.
- Tabbing out of either a Terminal or the log caused the scrollbar to scroll to bottom. Fixed.
Version V6.86d (2020-10-09)
Control Panel
- Breakpoints tab: If watchpoints were managed by debugger, not J-Link, garbage was shown. Fixed.
DLL
- Cypress CYT2B7, CYT2B9, CYT3BB, CYT4BB, CYT4BF series devices flash programming for Cortex-M4 and Cortex-M7, fixed.
- Renesas RZ/A2M series: A permanently locked device was not detected properly and J-Link tried to unsecure it anyway. Fixed.
- STM32F46G-DISCO QSPI support, fixed.
J-Flash
- In case of J-Flash opened a project with an old silicon vendor name, the project was updated but not marked as changed. Fixed.
- Opening a project with invalid device name could lead to unexpected behavior. Fixed..
- When executing operations passed via the command line interface, some MessageBoxes were still shown. Fixed.
J-Flash SPI
- When executing operations passed via the command line interface, some MessageBoxes were still shown. Fixed.
Version V6.86c (2020-10-06)
DLL
- J-Link Script File: Under special circumstances, J-Link script files were not loaded correctly. Fixed.
- On headless systems (no GUI available) and Linux ARM systems (e.g. Raspberry Pi), no firmware updates were applied to J-Links. Fixed.
Firmware
- Flasher ARM V5: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
- Flasher ARM V5: Introduced in V6.86b: If no FLASHER.INI was present on the Flasher but only FLASHER.CFG and FLASHER.DAT (default), Flasher incorrectly used universal flash loader mode. Fixed.
- Flasher Portable PLUS V1: Introduced in V6.86b: If no FLASHER.INI was present on the Flasher but only FLASHER.CFG and FLASHER.DAT (default), Flasher incorrectly used universal flash loader mode. Fixed.
- Flasher Portable PLUS V1: Stand-alone mode: Direct SPI Flash programming did not clear RESET line. It was possible that a connected CPU could have interfered with SPI communication done by Flasher. Fixed.
- Flasher PRO V5: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
- Flasher PRO V5: Introduced in V6.86b: If no FLASHER.INI was present on the Flasher but only FLASHER.CFG and FLASHER.DAT (default), Flasher incorrectly used universal flash loader mode. Fixed.
- Flasher PRO V5: Stand-alone mode: Direct SPI Flash programming did not clear RESET line. It was possible that a connected CPU could have interfered with SPI communication done by Flasher. Fixed.
- Flasher PRO XL V5: Introduced in V6.86b: If no FLASHER.INI was present on the Flasher but only FLASHER.CFG and FLASHER.DAT (default), Flasher incorrectly used universal flash loader mode. Fixed.
- Flasher PRO XL V5: Stand-alone mode: Direct SPI Flash programming did not clear RESET line. It was possible that a connected CPU could have interfered with SPI communication done by Flasher. Fixed.
- J-Link EDU Mini: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
- J-Link EDU/BASE/PLUS V10: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
- J-Link EDU/BASE/PLUS V10: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- J-Link EDU/BASE/PLUS V11: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
- J-Link EDU/BASE/PLUS V11: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- J-Link PRO V4: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
- J-Link PRO V4: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- J-Link ULTRA+ V4: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
- J-Link ULTRA+ V4: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- J-Link WiFi V1: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
- J-Link WiFi V1: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- J-Trace PRO V2 Cortex: Added CoreSight SoC-600 support for ARMv7-A/R based cores (e.g. Cortex-A8, Cortex-A9, Cortex-R4, Cortex-R5, ...)
J-Flash SPI
- Adjusted connection sequence so that init steps are now executed before any other SPI Flash communication (e.g. Verify ID) happens.
- RESET line was not cleared early enough. It was possible that a connected CPU could have interfered with SPI communication done by J-Flash SPI. Fixed.
Version V6.86b (2020-10-02)
DLL
- Some J-Link OBs were unable to connect to ON Semiconductor devices due to the vendor limit. Fixed.
- STM32F2 series device: Unlock did not work correctly. Fixed.
- The DLL could crash when trying to connect to a device with an Open Flash Loader .elf file which contained a sector size of 0 bytes. Fixed.
Firmware
- Flasher ARM V5: The #SELECT command did not work correctly under special circumstances. Fixed.
- Flasher Portable PLUS V1: The #SELECT command did not work correctly under special circumstances. Fixed.
- Flasher PRO V5: The #SELECT command did not work correctly under special circumstances. Fixed.
- Flasher PRO XL V5: The #SELECT command did not work correctly under special circumstances. Fixed.
J-Flash
- Canceling the exit dialog for the second time did crash J-Flash. Fixed.
- Command line interface: On some systems (e.g. Windows XP), it could happen that flash operations sometimes failed with the message "canceled by user". Fixed.
- When trying to merge two data files and an error occured, J-Flash could crash. Fixed.
J-Flash SPI
- When trying to merge two data files and an error occured, J-Flash could crash. Fixed.
RTT
- SEGGER_RTT_LOCK() and _UNLOCK() macros in SEGGER_RTT_Conf.h were not set to proper defaults for Cortex-A/R based systems and IAR compiler. Fixed.
RTT Viewer
- In some cases, line breaks were not shown correctly. Fixed.
Version V6.86a (2020-09-28)
Firmware
- Flasher ARM V5: When making use of an INI file (Flasher.ini) to have multiple target images selectable, stand-alone direct SPI programming only worked once. Fixed.
- Flasher Portable PLUS V1: Timeout overrides were used even when specified otherwise in the config file. Fixed.
- Flasher Portable PLUS V1: When making use of an INI file (Flasher.ini) to have multiple target images selectable, stand-alone direct SPI programming only worked once. Fixed.
- Flasher Portable PLUS V1: When using Universal Flashloader and not having any INI file specified, the default configuration (FLASHER.uni) was not loaded and an error was returned. Fixed.
- Flasher Portable PLUS V1: When using Universal Flashloader in stand-alone mode, Flasher firmware could crash. Introduced with V6.86. Fixed.
- Flasher PRO V5: Timeout overrides were used even when specified otherwise in the config file. Fixed.
- Flasher PRO V5: When making use of an INI file (Flasher.ini) to have multiple target images selectable, stand-alone direct SPI programming only worked once. Fixed.
- Flasher PRO XL V5: Timeout overrides were used even when specified otherwise in the config file. Fixed.
- Flasher PRO XL V5: When making use of an INI file (Flasher.ini) to have multiple target images selectable, stand-alone direct SPI programming only worked once. Fixed.
J-Flash SPI
- Updated default "override timeout" values for new projects.
Version V6.86 (2020-09-24)
Commander
- fdelete now deletes directories with contents up to 4 levels deep.
DLL
- Added (Q)SPI flash programming support for Zbit Semiconductor ZB25VQ32, ZB25VQ64 and ZB25VQ128.
- Added debug support for Marvell 88MW320 / 88MW322 series devices.
- Added flash programming support for Cypress PSoC6A-256K (CY8C6xx4) series.
- Added flash programming support for Cypress PSoC6A-2M (CY8C6xx8) series.
- Added flash programming support for HVC4263R.
- Added flash programming support for Marvell 88MW320 / 88MW322 series devices.
- Added SPI Flash programming for Adesto AT25QF641B, AT25SF041B, AT25SF161B, AT25SF081B, AT25XE081D, AT25XE041D, AT25FF041A SPI Flash devices.
- Allow STRACE data to be read after trace is stopped but the target is still running to also cover corner cases where the target may not be reachable anymore.
- CoreSight SoC-600: If DPIDR1.ASIZE indicated 32-bit size for SELECT register, "0 KB" was shown as address range. Fixed.
- CoreSight SoC-600: If SW-DP DPIDR reported != 0x-B------ as pattern, the SW-DP was not correctly detected. Fixed.
- CoreSight SoC-600: MEM-APv1 (APv1 adapter) were not detected properly. Fixed.
- Extended command string "CORESIGHT_AddAP" to allow setting an <APAddr> (required for CoreSight SoC-600 support).
- NXP i.MX RT105x series: QSPI flash-programming: Under specific circumstances the flash was not memory-mapped after the initialization procedure. Fixed.
- NXP i.MX6Solo (i.MX6S, MCIMX6Sx) series: Enabled out-of-the-box RTT support on PC side. For target side, see: https://wiki.segger.com/RTT#RTT_on_Cortex-A_targets
- NXP RT117x: Reset did not work for rev B0 silicon. Fixed.
- Whitespace characters after command string "CORESIGHT_AddAP" were not handled correctly. Fixed.
Firmware
- Flasher ARM V5: Stand-alone direct SPI programming could fail for data files which are not multiple of 4 KB. Fixed. (Bug was only present in beta versions since V6.85b)
- Flasher Portable PLUS V1: Added support for stand-alone direct programming of SPI flashes (configuration downloadable via J-Flash SPI).
- Flasher PRO V5: Added support for stand-alone direct programming of SPI flashes (configuration downloadable via J-Flash SPI).
- Flasher PRO V5: Stand-alone direct SPI programming could fail for data files which are not multiple of 4 KB. Fixed. (Bug was only present in beta versions since V6.85b)
- Flasher PRO XL V5: Added support for stand-alone direct programming of SPI flashes (configuration downloadable via J-Flash SPI).
- Flasher PRO XL V5: Stand-alone direct SPI programming could fail for data files which are not multiple of 4 KB. Fixed. (Bug was only present in beta versions since V6.85b)
J-Flash
- ELF files built without debug information could not be opened. Fixed.
- Linux: When programming serial numbers, the ..._Serial.txt file was not created correctly. Fixed.
- Linux: When programming serial numbers, the ..._SNList.txt file was not detected correctly. Fixed.
- macOS: When programming serial numbers, the ..._Serial.txt file was not created correctly. Fixed.
- macOS: When programming serial numbers, the ..._SNList.txt file was not detected correctly. Fixed.
- The generated ..._Serial.txt contained a redundant NULL character. Fixed.
- When programming serial numbers using a ..._SNList.txt, a ..._Serial.txt exceeding the number of lines in the list file was not handled correctly. Fixed.
J-Flash SPI
- Added (Q)SPI flash programming support for Zbit Semiconductor ZB25VQ32, ZB25VQ64 and ZB25VQ128.
- Added SPI Flash programming for Adesto AT25QF641B, AT25SF041B, AT25SF161B, AT25SF081B, AT25XE081D, AT25XE041D, AT25FF041A SPI Flash devices.
- Added support for stand-alone direct programming of SPI flashes (configuration downloadable via J-Flash SPI).
- ELF files built without debug information could not be opened. Fixed.
- Implemented programming serial numbers in PC-based mode to J-Flash SPI.
RTT
- SEGGER_RTT_Conf.h: Renesas RX: <machine.h> was not included so using intrinsics like get_psw() threw errors. Fixed.
- Updated RTT target sources to support Cortex-A based targets with cache.
- Xilinx Zynq7000 series: Enabled out-of-the-box RTT support on PC side. For target side, see: https://wiki.segger.com/RTT#RTT_on_Cortex-A_targets
Version V6.84b (2020-09-21)
Commander
- fread command: Trying to read files larger than 1MB failed with error message "ERROR: Could not write to destination file". Fixed.
DLL
- Nuclei N2xx, N3xx, N6xx series: Maximum QSPI flash size was set to a too low value. Fixed.
- ST STM32WB55xx-series: Flash-programming could have failed under specific conditions. Fixed.
Firmware
- Flasher ARM V4: Fixed patch file support.
- Flasher ARM V5: Fixed patch file support.
- Flasher ARM V5: Unsupported/ unknown parameters inside config files were ignored. Fixed.
- Flasher ARM V5: When having a Patches.txt file with invalid contents (i.e. incorrect syntax), trying to start programming for the second time would cause the Flasher to hang. Fixed.. Fixed.
- Flasher Portable PLUS V1: Fixed patch file support.
- Flasher Portable PLUS V1: For backwards-compatibility, the FW now accepts both ':' and ',' as delimiter between <NumBytes> and <Data> inside Patches.txt
- Flasher Portable PLUS V1: Universal Flashloader configurations were not shown in default configuration. Fixed.
- Flasher PRO V4: Fixed patch file support.
- Flasher PRO V5: Fixed patch file support.
- Flasher PRO V5: Unsupported/ unknown parameters inside config files were ignored. Fixed.
- Flasher PRO V5: When having a Patches.txt file with invalid contents (i.e. incorrect syntax), trying to start programming for the second time would cause the Flasher to hang. Fixed.
- Flasher PRO XL V5: Fixed patch file support.
- Flasher PRO XL V5: Unsupported/ unknown parameters inside config files were ignored. Fixed.
- Flasher PRO XL V5: When having a Patches.txt file with invalid contents (i.e. incorrect syntax), trying to start programming for the second time would cause the Flasher to hang. Fixed.
- J-Link PRO V5: VCOM was not supported by accident. Fixed.
- J-Link ULTRA+ V5: VCOM was not supported by accident. Fixed.
J-Flash
- Adjusted phrasing of log message for downloading PCodes.
- macOS: When programming serial numbers with an SN list file, J-Flash would look for a _SNList..txt instead of _SNList.txt . Fixed.
- When having multiple data windows open, the title bar of each window would overlap with the data window above it. Fixed
- When programming serial numbers without an SN list file, J-Flash would show a warning message box. Fixed.
- Windows: Menu Bar: When having "Ukrainian" or "Russian" as system locale, the list of most recently used files and projects did not display Cyrillic characters correctly. Fixed.
- Windows: Welcome Dialog: When having "Ukrainian" or "Russian" as system locale, the list of most recently used projects did not display Cyrillic characters correctly. Fixed.
- Windows: When having "Ukrainian" or "Russian" as system locale, the dialog to open a data or project file did not start with the most recently opened directory if its path contained Cyrillic characters. Fixed.
J-Flash SPI
- When having multiple data windows open, the title bar of each window would overlap with the data window above it. Fixed
- Windows: Menu Bar: When having "Ukrainian" or "Russian" as system locale, the list of most recently used files and projects did not display Cyrillic characters correctly. Fixed.
- Windows: When having "Ukrainian" or "Russian" as system locale, the dialog to open a data or project file did not start with the most recently opened directory if its path contained Cyrillic characters. Fixed.
RTT
- ARMv8-M (Cortex-M23, M33): Support for assembler variant was enabled for Cortex-M23 by accident but did not compile. Fixed.
- Assembler version was disabled for ARM compiler V6 or later even if it was usable. Fixed.
- SEGGER_RTT_LOCK() for ARMv6-A/R was not specifying that condition codes have been changed by inline assembly which could cause problems with certain compiler optimization levels. Fixed.
- SEGGER_RTT_LOCK() for ARMv6-M was not specifying that condition codes have been changed by inline assembly which could cause problems with certain compiler optimization levels. Fixed.
- SEGGER_RTT_LOCK() for ARMv6-M was using non-standard inline-assembly syntax '$' instead of '#' (Caused problems with Clang 11). Fixed.
- SEGGER_RTT_LOCK() for ARMv7-M was not specifying that condition codes have been changed by inline assembly which could cause problems with certain compiler optimization levels. Fixed.
- SEGGER_RTT_Syscalls_GCC.c: function prototypes for _write() and _write_t() caused problems with current GCCs. Fixed.
- volatile qualifier was missing before inline assembly. Fixed.
Version V6.84a (2020-09-07)
Configurator
- Configurator crashed when selecting "update/replace firmware". Introduced in V6.84. Fixed.
Version V6.84 (2020-09-04)
Commander
- Added "default" as device name for command line option "-device". It selects the default / last used device name as device.
- fwrite command: When writing to an existing file without specifying <Offset> and <NumBytes>, the existing file was not replaced. Fixed.
Control Panel
- Added "Help" tab.
- Added Web Commander.
- RISC-V only: J-Link software could crash when opening the RAWTRACE tab and having SiFive Insight trace active. Fixed.
DLL
- Added debug and internal flash and option byte programming support for APEXMIC APMF103xx series devices.
- Added debug and internal flash programming support for ST STM32H7A3LI series device.
- Added debug and internal flash programming support for ST STM32H7A3xG family series devices.
- Added debug and internal flash programming support for ST STM32H7B0xB family series devices.
- Added debug and internal flash programming support for ST STM32H7B3LI series device.
- Added debug support for Western Digigtal SweRV_EH1 series device.
- Added debugging and internal flash programming support for ST STM32L4P5xx series devices.
- Added debugging and internal flash programming support for ST STM32L4Q5xx series devices.
- Added HyperFlash programming support for "MIMXRT106A-ALEXA".
- Added internal QSPI Flash programming support for NXP iMXRT1024 series devices.
- Added native SWO support for NXP i.MXRT6xx family
- Added QSPI flash programming support for "MIMXRT106A-ALEXA2".
- Added stalling mode support for ETMv3.
- Added stalling mode support for ETMv4.
- Cypress TVII: Added some missing aliases for backward compatibility reasons.
GDB Server
- Action Help -> J-Link User Guide now opens the User Guide Wiki page instead of the PDF manual.
- Added monitor commands "ReadCSR" and "WriteCSR"
J-Flash
- "New Project" dialog: Changed element to enter interface speed to combobox (extended drop-down menu).
- Actions Help -> J-Link User Guide / J-Flash User Guide now opens the User Guide Wiki page instead of the PDF manual.
- Added log messages when reading ELF files.
- On some systems (e.g. Linux Mint 19.3 Cinnamon 64-bit), message box icons were displayed too large. Fixed.
- Project Settings --> Target Interface: Changed element to enter interface speed to combobox (extended drop-down menu).
- Under certain circumstances, the "IRPre" selection was ignored when changed manually in "Simple configuration".
J-Flash SPI
- Added log messages when reading ELF files.
- Added option to show license dialog to menu bar, similar to J-Flash.
- Project Settings --> Setup: Changed element to enter interface speed to combobox (extended drop-down menu).
- When opening a project with an interface speed of more than 25MHz, J-Flash SPI used 25MHz. Fixed.
Manual
- UM08022: Added new examples with pictures on how to patch data using the Flasher.
RTT Viewer
- Action Help -> J-Link User Guide now opens the User Guide Wiki page instead of the PDF manual.
- Configuration dialog: When a Serial number was specified and the host interface was changed from USB and then back to USB, the SN was set to 0. Fixed.
- Configuration dialog: When a Serial number was specified that was unequal to 0, the Serial No. check box could not be unchecked. Fixed.
- J-Link Serial No. is now saved for the next session.
- JTAG scanchain can now be configured in the Configuration dialog.
SWO Viewer
- Action Help -> J-Link User Guide now opens the User Guide Wiki page instead of the PDF manual.
Version V6.82g (2020-08-28)
DLL
- Cypress TVII: Under special circumstances, flash programming could fail. Introduced in V6.82b. Fixed.
- Erase failed for devices with non-1kB-aligned RAM. Fixed.
- LPC5460x-family devices: Erasing failed when no QSPI was connected to the chip. Fixed.
GDB Server
- Even with "-nohalt" specified, devices could be in halted state after connect, when the halt was implicitly issued by the generic connect sequence for the device. Fixed.
J-Flash
- Project settings: Production: Changes to timeouts for <Erase>, <Program> and <Verify> were not recognized/ applied correctly. Fixed.
- When reading ELF files containing C++ code (i.e. exception handling, [pre-]initialization functions, termination functions), those sections were not read as part of the application image. Fixed.
J-Flash SPI
- When reading ELF files containing C++ code (i.e. exception handling, [pre-]initialization functions, termination functions), those sections were not read as part of the application image. Fixed.
Version V6.82f (2020-08-24)
Firmware
- Flasher ARM V5: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- Flasher PRO V5: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- Flasher PRO XL V5: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- J-Link PRO V5: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
- J-Link ULTRA+ V5: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.
Version V6.82e (2020-08-21)
Control Panel
- Tracepoints were not listed correctly. Fixed.
DLL
- Cortex A/R SWD: Cache sizes were not detected correctly. Fixed.
- NXP S32K148: J-Link could not access the flash >= 1.5 MB (0x180000). Fixed.
- ONSemiconductor Nebo40-256 and AXM0F343-256 series devices page size, fixed.
- Under certain circumstances deleting all Tracepoints might have failed. Fixed
Firmware
- Flasher ARM V4: When trying to read a a non-existent large file (>= 512 KB) from the Flasher via J-Link Commander etc., the firmware could crash and reset itself. Fixed.
- Flasher Portable PLUS V1: When trying to read a a non-existent large file (>= 512 KB) from the Flasher via J-Link Commander etc., the firmware could crash and reset itself. Fixed.
- Flasher PRO V4: When trying to read a a non-existent large file (>= 512 KB) from the Flasher via J-Link Commander etc., the firmware could crash and reset itself. Fixed.
J-Flash
- Command line: The command line options "-savedat" and "-savecfg" were parsed incorrectly and the corresponding files were not created. Introduced with V6.82. Fixed.
- J-Flash would crash when trying to read large ELF files with >= 256 abreviation table entries for a compilation unit. Fixed.
- Trying to open an ELf file with >= 5 data ranges to download could fail or create a corrupted data range. Fixed.
SWO Viewer
- Under some circumstances, SWO viewer failed to connect to target. Fixed.
Version V6.82d (2020-08-13)
CCS Plugin
- Plug-in file extensions for Linux and Mac were still ".tar.gz" instead of ".zip". Fixed.
DLL
- DLL could crash if JLINKARM_Open() was called again without a previous call to JLINKARM_Close(). Fixed.
- Error when reading/writing serial number and serial number list file located in same folder as called batch file, fixed.
- For SPI Flash Adesto AT25SF128A/AT25QF128A flash programming in SPIFI-Lib, fixed.
- Nuclei System N101: Flash programming did not work due to a different system memory map. Fixed.
- NXP i.MX7D Cortex-M4: QSPI flash programming could have interfered with an application running on the main Cortex-A7. Fixed.
- Under certain circumstances clearing individual trace points failed. Fixed.
J-Flash
- Command line interface: Under some circumstances, it could happen that flash operations failed with the message "canceled by user". Fixed.
- J-Flash refused to open certain ELF files with zero data sections. Fixed.
- Project Settings: Flash: When selecting multiple sectors and inverting their selection state (i.e. by pressing <Space>), the GUI would freeze for some time. Fixed.
J-Flash SPI
- Fixed manual settings to read ID Code of SPI Flash.
- GigaDevice 256 MBit flashes: Programming beyond 16 MB did not work in auto-detection mode. Fixed.
Version V6.82c (2020-07-31)
Commander
- In case the selected speed was set to auto, the Commander skipped to reconnect to target when executing the "connect" command. Fixed.
Control Panel
- Wrong port used (19081 instead of 19080). Introduced in V6.82. Fixed.
DLL
- Cypress Traveo II: Under special circumstances, flash programming did not work. Affected areas: Work flash. Fixed.
- Cypress Traveo II: Updated device name database to support all available devices.
- RTT: Under some circumstances, sending data to the Target returned a false error. Fixed.
- ST STM32 series unsecure: After an successful unsecure no reset was performed. Fixed.
- ST STM32F4 series: Unsecure could have failed under very specific conditions. Fixed.
- ST STM32F4 series: Unsecure did fail under specific circumstances. Fixed.
- STM32F1 device family: Connect when using JTAG with a locked device failed. Fixed.
- STM32F72/STM32F73 Family: Devices protected via PCROP were not detected as protected. Fixed.
Firmware
- J-Link PRO V5: JTAG/SWD/SPI: Under special circumstances when selecting a specific TIF speed that could not match exactly, a higher speed was selected by accident instead of the next slower one. Fixed.
- J-Link ULTRA+ V5: JTAG/SWD/SPI: Under special circumstances when selecting a specific TIF speed that could not match exactly, a higher speed was selected by accident instead of the next slower one. Fixed.
J-Flash
- Cypress Traveo II: Under special circumstances, flash programming did not work. Affected areas: Work flash. Fixed.
- J-Flash log file: The log message for programming flash ranges was cut off in the J-Flash log file ("- ogramming performed"). Fixed.
- Manual Programming -> Read Back -> Range... could fail due to an internal error. Fixed.
J-Flash SPI
- Project Settings: Flash: After detecting the connected SPI Flash via "Detect flash", the menu bar was not updated correctly. Fixed.
- Project Settings: Flash: After detecting the connected SPI Flash via "Detect flash", the project was falsely shown as modified. Fixed.
Version V6.82b (2020-07-23)
DLL
- NXP iMX7D: QSPI flash programming did not work on the Cortex-M4 core. Fixed.
- NXP RT500: Under special circumstances, flash programming failed if no reset was executed. Fixed.
- ST STM32H7 M4: CPU speed calculation did not work. Fixed.
- STM32F1: The Unlock did not work correctly. This could cause Problems when used in combination with J-Flash. Fixed.
- Under special circumstances, flash programming could fail on ARMv8M based devices. Fixed.
Firmware
- Flasher ARM V4: Chip select signal was accidentally cleared during SPI communication. Fixed.
- Flasher ARM V4: Under special circumstances, flash programming could fail on ARMv8M based devices. Fixed.
- Flasher Portable PLUS V1: Chip select signal was accidentally cleared during SPI communication. Fixed.
- Flasher Portable PLUS V1: Under special circumstances, flash programming could fail on ARMv8M based devices. Fixed.
- Flasher PRO V4: Chip select signal was accidentally cleared during SPI communication. Fixed.
- Flasher PRO V4: Under special circumstances, flash programming could fail on ARMv8M based devices. Fixed.
- Flasher V4: For some targets the Flasher could no longer program in stand-alone after some programming cycles. Fixed.
J-Flash
- When opening a data file with an offset (e.g. Intel HEX format) which is the same as defined inside the project file, the project was shown as "modified" immediately after opening it. Fixed.
- Windows: When saving a data file via "Save data file as..." the resulting path used forward slashes ('/') instead of backward slashes ('\'). Fixed.
J-Flash SPI
- Sector size for Cypress S25HL256T, S25HL512T, S25HL01GT, S25HS256T, S25HS512T, S25HS01GT SPI Flashes, fixed.
- When opening a data file with an offset (e.g. Intel HEX format) which is the same as defined inside the project file, the project was shown as "modified" immediately after opening it. Fixed.
- Windows: After opening a data file with path separators different from the OS native separators, the project file was not auto-saved with the correct path. Fixed.
- Windows: When saving a data file via "Save data file as..." the resulting path used forward slashes ('/') instead of backward slashes ('\'). Fixed.
Version V6.82a (2020-07-21)
DLL
- Added missing device name SiliconLabs EFR32FG12P231F1024GM48 to supported devices.
- NXP iMX7D: Flash programming did not work. Fixed.
Firmware
- J-Trace PRO V2 Cortex: Firmware from V6.82 could make J-Trace getting stuck in bootloader mode. Fixed. (Affected J-Traces can be fixed by performing a firmware update with this software version)
- J-Trace PRO V2 CortexM: Firmware from V6.82 could make J-Trace getting stuck in bootloader mode. Fixed. (Affected J-Traces can be fixed by performing a firmware update with this software version)
Version V6.82 (2020-07-20)
Commander
- "VCOM" was missing in the command info text of the Commander. Fixed.
- Reworked -NoGui command.
- Windows: When closing by clicking the "x" of the Shell window, the Tray icon to the Control Panel did not disappear. Fixed.
Control Panel
- Long tables are now scrollable.
DLL
- "Secure chip" in J-Flash for Silicon Labs EFM32GG11 series devices, fixed.
- Added (QSPI) flash programming support for NXP iMXRT500 family (https://wiki.segger.com/NXP_i.MXRT500)
- Added 4byte address mode for QSPI-Flash programming with iMXRT105x series devices.
- Added debug and flash programming support for Renesas RX66N series devices.
- Added debug and flash programming support for Renesas RX72N series devices.
- Added debug and internal and external (QSPI) flash programming support for Maxim MAX32561 series device.
- Added debug and internal flash programming support for Maxim MAX32670 and MAX32671 series devices.
- Added debug support for RelChip RC10001 series device.
- Added programming support in SPIFI-Lib for GigaDevice: GD25Q16E, GD25LE32E, GD25D80C, GD25WQ16E, GD25WQ32E, GD25WQ64E, GD25WQ128E
- Added programming support in SPIFI-Lib for GigaDevice: GD25Q32ESIG, GD25WQ80ESIG, GD25LQ32ESIG, GD25LQ32DSIG, GD25WD80CSIG, GD25WD05CTIG, GD25LE80CSIG, GD25LQ64ESIG, GD25LD80CSIG, GD25Q64ESIG
- Added programming support in SPIFI-Lib for Macronix: MX25UW51345G octa SPI Flash.
- Added support for command string "CORESIGHT_AddAP"
- Added support for Cortex-A/R NEON registers D16-D31.
- Eta-Compute ECM3531, ECM3532: Improved the reset to always perform a reset via debug register + reset pin.
- Instruction set simulation: ARMv8-M: MRS and MSR instruction were not simulated correctly. Fixed.
- NXP i.MX8: Added support for new devices of the MIMX8QX, MIMX8DX and MIMX8UX series.
- Renesas RE01: Added J-Link support for new RE01 256KB devices: R7F0E0108 and R7F0E0118
- Reset for Maxim MAX3267x series devices, fixed.
- STM32G0: Under some circumstances when the device was locked, it was not correctly detected as locked. Fixed.
- TI TMS570LCxx series: Added support for RTT
- TI TMS570LS31xx series: Added support for RTT
- Under special circumstances, a connect via USB was performed by accident if connect via IP was selected. Fixed.
- When connecting to J-Link via IP and programming large parts of flash, the internal error "NET_IP_WriteRead(): Max. Size exceeded" could occur. Fixed.
- When using SWO, the user's time stamp configuration was reset. Fixed.
Firmware
- Flasher ARM V4: When selecting SPI as target interface, the reset pin of the target interface was released by accident (even if explicitly asserted before). Fixed.
- Flasher Portable PLUS V1: When selecting SPI as target interface, the reset pin of the target interface was released by accident (even if explicitly asserted before). Fixed.
- Flasher PRO V4: When selecting SPI as target interface, the reset pin of the target interface was released by accident (even if explicitly asserted before). Fixed.
- J-Link EDU Mini: Added support for Cortex-A/R NEON registers D16-D31.
- J-Link EDU Mini: Improved SWD download speed by up to 13%.
- J-Link EDU/BASE/PLUS V10: Added support for Cortex-A/R NEON registers D16-D31.
- J-Link EDU/BASE/PLUS V10: Improved SWD download speed by up to 13%.
- J-Link EDU/BASE/PLUS V11: Added support for Cortex-A/R NEON registers D16-D31.
- J-Link EDU/BASE/PLUS V11: Improved SWD download speed by up to 13%.
- J-Link PRO V4: Added support for Cortex-A/R NEON registers D16-D31.
- J-Link PRO V4: Improved performance of SWD non-fast download mode: @25 MHz: 1100 KB/s -> 1300 KB/s.
- J-Link PRO V4: Improved SWD download speed by up to 13% (1172 KB/s -> 1330 KB/s @ 25 MHz SWD speed)
- J-Link PRO V4: Improved SWD download speed by up to 13%.
- J-Link ULTRA+ V4: Added support for Cortex-A/R NEON registers D16-D31.
- J-Link ULTRA+ V4: Improved performance of SWD non-fast download mode: @25 MHz: 1100 KB/s -> 1300 KB/s.
- J-Link ULTRA+ V4: Improved SWD download speed by up to 13% (1172 KB/s -> 1330 KB/s @ 25 MHz SWD speed)
- J-Link ULTRA+ V4: Improved SWD download speed by up to 13%.
- J-Link V10: Firmware: Over time current measurement (10ms and 100ms) was unsupported. Fixed.
- J-Link V11: Firmware: Over time current measurement (10ms and 100ms) was unsupported. Fixed.
- J-Link WiFi V1: Added support for Cortex-A/R NEON registers D16-D31.
- J-Link WiFi V1: Improved SWD download speed by up to 13%.
- J-Trace PRO V2 Cortex: Added support for Cortex-A/R NEON registers D16-D31.
- J-Trace PRO V2 Cortex: Improved SWD download speed by up to 13%.
- J-Trace PRO V2 CortexM: Improved SWD download speed by up to 13%.
GDB Server
- Added "monitor rtosconf [...]" command to allow configuration of RTOS Plugins.
J-Flash
- In some message boxes (e.g. "Do you want to save any unsaved changes [...]"), switching between the buttons with the arrow keys did not work correctly. Fixed.
- The "save project" menu action was sometimes not enabled/ disabled correctly. Fixed.
- When a data window was open, copying from the log window via "Ctrl + C" did not work. Fixed.
- When connecting to J-Link via IP and programming large parts of flash, the internal error "NET_IP_WriteRead(): Max. Size exceeded" could occur. Fixed.
- Windows: Separators in paths could sometimes be mixed ('/' and '\'). Fixed.
- Windows: When having "Ukrainian" or "Russian" as system locale, opening projects located at paths which contain Cyrillic characters did not work. Introduced with V6.70. Fixed.
- Windows: When opening a project with a data file located on a network drive (path starts with "\\"), the data file could not be opened. Fixed.
J-Flash SPI
- Added programming support for GigaDevice: GD25Q16E, GD25LE32E, GD25D80C, GD25WQ16E, GD25WQ32E, GD25WQ64E, GD25WQ128E
- Added programming support for GigaDevice: GD25Q32ESIG, GD25WQ80ESIG, GD25LQ32ESIG, GD25LQ32DSIG, GD25WD80CSIG, GD25WD05CTIG, GD25LE80CSIG, GD25LQ64ESIG, GD25LD80CSIG, GD25Q64ESIG
- In some message boxes (e.g. "Do you want to save any unsaved changes [...]"), switching between the buttons with the arrow keys did not work correctly. Fixed.
- The "save project" menu action was sometimes not enabled/ disabled correctly. Fixed.
- When a data window was open, copying from the log window via "Ctrl + C" did not work. Fixed.
- Windows: Separators in paths could sometimes be mixed ('/' and '\'). Fixed.
- Windows: When having "Ukrainian" or "Russian" as system locale, opening projects located at paths which contain Cyrillic characters did not work. Introduced with V6.70. Fixed.
- Windows: When opening a project with a data file located on a network drive (path starts with "\\"), the data file could not be opened. Fixed.
Remote Server
- Connecting to the J-Link Remote Server with a target interface other than JTAG would make a message box appear which told the user that a second debugger connection was detected. Fixed.
STM32 Utility
- Support for ST STM32H745_47_55_57 option bytes added.
Version V6.80e (2020-07-13)
Control Panel
- Target Power tab could have crashed under certain circumstances. Fixed.
DLL
- Added support for ARMCC compiler V6 in RTT Syscalls files.
- Empty lines in Intel HEX files could cause parse errors and aborting of parsing the hex file. Fixed.
- Fixed size of Bootloaderflash for SiliconLabs EFR32BG12PxxxF1024, EFR32FG12PxxxF1024 and EFR32MG12PxxxF1024 series devices.
- Flash programming for Qorvo devices did not work properly. Fixed. Affected device series: QPG5071F, QPG5071G, QPG6100, QPG6100M, QPG6100S
- When connecting to J-Link via IP a handle leak occurred which could crash the debug session after 64 consecutive connection open + close attempts without unloading the DLL in between. Fixed.
J-Flash
- Empty lines in Intel HEX files could cause parse errors and aborting of parsing the hex file. Fixed.
- Erase chip failed for STM32F7-series devices. Fixed.
- Flash programming for Qorvo devices did not work properly. Fixed. Affected device series: QPG5071F, QPG5071G, QPG6100, QPG6100M, QPG6100S
- Improved version compatibility check.
- Sample projects: nRF51822_xxAA_Unlock.jflash contained an init. step with a comment which exceeds J-Flash limit for custom step comments. Fixed.
- When opening a project file with a string that is longer than expected, a cryptic error message box could appear. Fixed.
J-Flash SPI
- When opening a project file with a string that is longer than expected, a cryptic error message box could appear. Fixed.
Version V6.80d (2020-06-26)
DLL
- NXP LPC55S69 core 0: Reset did not work when core was running in non-secure mode. Fixed.
- NXP RT106x: Flash programming >= 8 MB failed. Fixed.
- NXP RT500: Improved the reset to always perform a reset via debug register + reset pin.
- NXP RT600: Improved the reset to always perform a reset via debug register + reset pin.
- Qorvo UE878, GP570 and QPG6095: For some chip revisions, erase could fail. Fixed.
- Renesas RE01 (1500 KB flash): Updated supported device names.
- SAM-ICE could not be used with Microchip (Atmel) ATSAMA5D27. Fixed.
- ST STM32: Unsecure did fail under specific conditions, when there was an application running that secures the MCU again. Fixed.
- STM32L0: Under some circumstances the first 32 bits of the option bytes area were not reset correctly when unlocking the device. Fixed.
J-Flash
- After opening multiple data windows (4 or more), closing them afterwards could cause J-Flash to crash or hang. Fixed.
- macOS: Data files can now be opened via drag and drop.
- Read back: For some devices, trying to read a range from a flash bank with gaps could fail. Fixed.
- STM32L0: Under some circumstances the first 32 bits of the option bytes area were not reset correctly when unlocking the device. Fixed.
- Windows: Opening a data file could have failed when starting multiple instances of J-Flash in parallel. Fixed.
J-Flash SPI
- After opening multiple data windows (4 or more), closing them afterwards could cause J-Flash to crash or hang. Fixed.
- macOS: Data files can now be opened via drag and drop.
Monitor Mode
- Monitor mode sources and samples may calculate incorrect SP when FP application was used. Fixed.
Version V6.80c (2020-06-19)
Commander
- Cortex-A/R: On reading the CPU registers, depending on the CPU mode on halt, the error "failed to read register 81" could pop up. Fixed.
DLL
- Cypress PSoC 4100S Plus: Flash programming did not work beyond 128 KB. Fixed.
- Cypress PSoC 4500: Flash programming did not work beyond 128 KB. Fixed.
- Linux: On some distrubutions (i.e. Debian 10) GUI dialogs were not displayed. Fixed.
- NXP RT106x: QSPI programming failed under specific circumstances. Fixed.
- NXP RT500: Attach to a running application did not work. Fixed.
- NXP RT500: The J-Link software did not support reset type 2 (reset via reset pin). Fixed.
- NXP RT500: The wrong reset type was executed by default. Fixed.
- NXP RT600: Attach to a running application did not work. Fixed.
- On some Nuvoton NUC4xx series devices Flash download might fail. Fixed.
- Some ST STM32G0 family based device names where listed twice in the J-Link device selection dialog. Fixed.
Firmware
- Flasher Portable PLUS: Flasher PRO unlocking of Renesas Synergy S124/S128 enabled.
- Flasher PRO V4: Flasher PRO unlocking of Renesas Synergy S124/S128 enabled.
J-Flash
- After manually changing data inside a data window, the change was only applied after 500ms. Adjusted so the changes take effect immediately.
- macOS: J-Flash could crash after opening a data file (and beginning to scroll inside the data window). Fixed.
- Project files which contained a chip name with the vendor "Atmel" defaulted to "ARM7" for the device. Introduced with V6.80a. Fixed.
- When dropping a data window onto another data window and "tabbing" them, selecting one of the now tabbed data windows did not automatically set it as the active data window. Fixed.
- When trying to program data which did not fit into the selected sectors, the user was asked if the data should be relocated accordingly. Even after clicking "Yes", J-Flash threw an error. Fixed.
J-Flash SPI
- After manually changing data inside a data window, the change was only applied after 500ms. Adjusted so the changes take effect immediately.
- More than 8192 sectors were unsupported for erasing, could led to a crash. Fixed.
- When dropping a data window onto another data window and "tabbing" them, selecting one of the now tabbed data windows did not automatically set it as the active data window. Fixed.
Version V6.80b (2020-06-05)
DLL
- NXP RT117x QSPI flash programming: Some necessary pins were not correctly configured to connect to the FLEXSPI controller. Fixed.
J-Flash
- After relocating data inside a data file, the menu action "Save data file" was still disabled. Fixed.
- In some occasions (e.g. saving data to a file), the scrollbar of the affected data window would jump to the top. Fixed.
- Project Settings: Flash: When opening a project file with a disabled flash bank (with a dynamic sector layout), the flash bank was shown as enabled. Fixed.
J-Flash SPI
- In some occasions (e.g. saving data to a file), the scrollbar of the affected data window would jump to the top. Fixed.
RTT Client
- Linux/Mac: User input was double echoed. Fixed.
Version V6.80a (2020-05-29)
Configurator
- Copying info from table to clipboard via context menu action did not work correctly. Fixed.
- Log contained system time instead of local time. Fixed.
- Updated displayed image to contain various SEGGER probes and programmers.
- Updated log element to behave like other J-Link GUI software log elements.
- Updated references to "emulator" to say "probe/ programmer" instead.
Control Panel
- Context trace packets were not identified. Fixed.
DLL
- Cypress Traveo II (e.g. CYT4BB8CES): Repeated flash downloads failed (e.g. using J-Link Commander). Fixed.
- In some cases, the PC sampling rate for SWO was overridden on initialization. Fixed.
- ST STM32L4xx series devices internal flash programming speed, optimized.
Firmware
- Flasher ARM V4: Flasher would reconnect after trying to unsecure a device, even when it was not secured. Fixed.
- Flasher ATE: Flasher would reconnect after trying to unsecure a device, even when it was not secured. Fixed.
- Flasher Portable PLUS: Flasher would reconnect after trying to unsecure a device, even when it was not secured. Fixed.
- Flasher PRO V4: Flasher would reconnect after trying to unsecure a device, even when it was not secured. Fixed.
- J-Link EDU Mini: Cortex-A/R via JTAG was not supported while via SWD was supported. Fixed.
- J-Trace PRO V1 Cortex-M: Under special circumstances, SWO speeds above 1.3 MHz could lead to firmware-internal buffer overflows and therefore data loss. Fixed.
- J-Trace PRO V2 Cortex-M: Under special circumstances, SWO speeds above 1.3 MHz could lead to firmware-internal buffer overflows and therefore data loss. Fixed.
- J-Trace PRO V2 Cortex: Under special circumstances, SWO speeds above 1.3 MHz could lead to firmware-internal buffer overflows and therefore data loss. Fixed.
J-Flash
- File download to Flasher ATE Modules did not work correctly when SWD was selected as target interface for the project. Fixed.
- Menu elements for "Target" are now disabled when "Flasher ATE Module selection" is checked for the project.
- Project info window: Added info display for Flasher ATE module selection.
- Project settings: General: Improved phrasing of info text.
- Project settings: General: Updated displayed image to contain a J-Link as well as a Flasher.
- Updated references to "emulator" or "J-Link" to say "probe/ programmer" instead.
- When a project file contained info for more internal banks than reported by the DLL (e.g. when flash bank info was removed from the JLinkDevices.xml), J-Flash could crash. Fixed.
J-Flash SPI
- Project settings: General: Updated displayed image to contain a J-Link as well as a Flasher.
- Updated references to "emulator" or "J-Link" to say "probe/ programmer" instead.
Version V6.80 (2020-05-25)
Commander
- Added "-NoGui"-command line. For more information please refer to https://wiki.segger.com/J-Link_Commander#-NoGui
DLL
- Added "MIMRT685S_M33" as backward compatible alias.
- Added clickable links to flash programming dialog
- Added command string "SetSkipL1Verify" to disable implicit L1Verify after programming a data chunk.
- Added debug support for Microchip MEC170x devices.
- Added debug support for NXP JN5188 and JN5189 series (https://wiki.segger.com/NXP_JN5188/89).
- Added debug support for NXP K32W061 and K32W041 series (https://wiki.segger.com/NXP_K32W061/41).
- Added debug support for NXP QN9030 and QN9090 series (https://wiki.segger.com/NXP_QN9090/30).
- Added debug support for Renesas RA4W1 family (R7FA4W1AD and R7FA4W1AD2CNG).
- Added DTCM RAM area of STM32H7 series Cortex-M7 devices to auto search range for RTT.
- Added flash programming support for NXP JN5188 and JN5189 series (https://wiki.segger.com/NXP_JN5188/89).
- Added flash programming support for NXP K32W061 and K32W041 series (https://wiki.segger.com/NXP_K32W061/41).
- Added flash programming support for NXP QN9030 and QN9090 series (https://wiki.segger.com/NXP_QN9090/30).
- Added flash programming support for Renesas RA4W1 family (R7FA4W1AD and R7FA4W1AD2CNG).
- Added programming support in SPIFI-Lib for Adesto: AT25XE321D, AT25FF321A, AT25QF641 SPI Flash.
- Added programming support in SPIFI-Lib for GigaDevice: GD25Q256C, GD25S512MDFIG, GD25LQ05C, GD25LD05C, GD25LQ10C, GD25LD10C, GD25LQ20C, GD25LD20C, GD25LQ20C, GD25LD20C, GD25LQ40C, GD25LD40C, GD25LQ80C, GD25LD80C, GD25LQ16C, GD25LQ32C, GD25LQ64C, GD25LE128D, GD25WD20C, GD25WD40C SPI Flash.
- Added programming support in SPIFI-Lib for Macronix: MX25L6445E, MX25U1635E SPI Flash.
- Added programming support in SPIFI-Lib for Micron: MT25QU256ABA, MT25QU128ABA SPI Flash.
- Added programming support in SPIFI-Lib for Winbond: W25Q40CL, W25Q20EW, W25Q128JV SPI Flash.
- Added QSPI Flash programming support for Altera Cyclone V series device.
- Added QSPI flash programming support for Microchip MEC170x devices.
- Improved flash programming speed for SEGGER SPIFI algos (ext. QSPI NOR flash)
- Links inside of message boxes or similar dialogs are now clickable.
- MKE15Z device family: When connecting with J-Link, the Watchdog was disabled without configuring it configurable for some devices. Fixed.
- NXP iMXRT600 series devices QSPI Flash programming optimized.
- NXP K80 series devices QSPI Flash programming support, speed optimization.
- NXP MK80FN256 series devices QSPI Flash programming optimized.
- NXP MK80FN256 series devices QSPI Prallel Flash programming, fixed.
- Ozone: When using POWERTRACE, on each step/go the buffer size was recalculated and reallocated even if no settings changed. Fixed.
- Restoration of QE-Bit for Altera Cyclone V QSPI Flash programming support, fixed.
- Selecting a J-Link via nickname when connecting via IP did not work properly. Fixed.
- ST STM32F76xxx and STM32F77xxx: Some RAM ranges were missing. Fixed.
- STM32F76x and STM32F77x: Added support for option byte programming.
- Under certain circumstances the Target Power tab in the J-Link Control panel may display incorrect information for the Power On Perm setting. Fixed.
- Updated device selection dialog.
- Updated flash programming dialog so that progress bars for steps which have been disabled by the user are no longer shown.
GUI Applications
- Links inside of message boxes or similar dialogs are now clickable.
- Updated device selection dialog.
J-Flash
- Added Flasher ATE module selection for file downloads at Project Settings -> General
- Added option "Disconnect afterwards" at Project Settings -> Production -> Actions performed by 'Production Programming'
- The table for sector selection at Project Settings -> Flash can now select multiple sectors at once for easier sector selection.
J-Flash SPI
- Added programming support for Adesto: AT25XE321D, AT25FF321A, AT25QF641 SPI Flash.
- Added programming support for GigaDevice: GD25LE128E, GD25LB128D, GD25LQ128E SPI Flash.
- Added programming support for GigaDevice: GD25Q256C, GD25S512MDFIG, GD25LQ05C, GD25LD05C, GD25LQ10C, GD25LD10C, GD25LQ20C, GD25LD20C, GD25LQ20C, GD25LD20C, GD25LQ40C, GD25LD40C, GD25LQ80C, GD25LD80C, GD25LQ16C, GD25LQ32C, GD25LQ64C, GD25LE128D, GD25WD20C, GD25WD40C SPI Flash.
- Added programming support for Macronix: MX25L6445E, MX25U1635E SPI Flash.
- Added programming support for Micron: MT25QU256ABA, MT25QU128ABA SPI Flash.
- Added programming support for Winbond: W25Q40CL, W25Q20EW, W25Q128JV SPI Flash.
- Added SPI Flash programming support for Cypress S25HS256T / S25HS512T / S25HS01GT / S25HL256T / S25HL512T / S25HL01GT devices.
Remote Server
- GUI: Updated SEGGER tunnel server list to contain the following entries: jlink-europe.segger.com, jlink-america.segger.com and jlink-asia.segger.com .
RTT
- Added support for ARM cores that need a DMB (Cortex-M7/M23/33/...) to RTT sources.
- Updated README.txt to add specifics for using RTT in MDK-ARM.
RTT Logger
- Added "-RTTSearchRanges"-command line.
- Extended delay before shutting down to 3 sec., so that the user has more time to read an error messages.
Version V6.72e (2020-05-20)
DLL
- Added programming support in SPIFI-Lib for GigaDevice: GD25LE128E, GD25LB128D, GD25LQ128E SPI Flash.
- Flash programming (internal) support for NXP MKE04Z8xxx4 series devices, fixed.
- NXP RT600: The J-Link software did not support reset type 2 (reset via reset pin). Fixed.
Firmware
- Flasher ARM V4: NAND Flash initialization could fail on Flasher hardware version 4.0 and 4.1. Fixed.
- Flasher PPC V4: NAND Flash initialization could fail on Flasher hardware version 4.0 and 4.1. Fixed.
- Flasher PRO V4: NAND Flash initialization could fail on Flasher hardware version 4.0 and 4.1. Fixed.
- Flasher RX V4: NAND Flash initialization could fail on Flasher hardware version 4.0 and 4.1. Fixed.
J-Flash
- Eliminating blank areas from the command line when no data file was opened could crash J-Flash. Fixed.
- When no data file was specified via command line interface, J-Flash would open the project file's data file only AFTER executing any passed command line parameters. Introduced with V6.70. Fixed.
Version V6.72d (2020-05-15)
Control Panel
- RAWTRACE tab: For some browsers, printing of analyzed data stopped after "->". Fixed.
- Target power tab: "Target consumption" field showed the oldest available value instead of the latest available one. Fixed.
DLL
- Renesas RE01 QSPI: Power-saving state of MCU was not correctly restored after programming. Fixed.
- SAM-ICE could not be used with Microchip (Atmel) SAM9X60. Fixed.
- STM32H7-dual core devices: ETB was not detected correctly. Fixed.
GUI Applications
- A file dialog different from the operating system's "native" dialog was used. Introduced with V6.72a. Fixed.
J-Flash
- Linux: Opening the device selection dialog could crash J-Flash when a J-Link Devices XML was found. Fixed.
J-Flash SPI CL
- Erase chip could fail due to a too short timeout. Fixed.
RTT Logger
- The default output file path string was not created correctly. Fixed.
RTT Viewer
- Under some circumstances, the RTT Viewer font size was not initialized correctly. Fixed.
Version V6.72c (2020-05-08)
DLL
- Information in RAWTRACE tab in J-Link Control Panel was missing on first run. Fixed.
- NXP LPC55xx: Memory accesses to memory regions which are available in non-secure and secure address space could fail (e.g. wrong values read / written). Fixed.
- NXP MKE14Z32VFP4 and MKE15Z32VFP4 aliases were missing. Fixed.
J-Flash
- For flash banks added using Open Flash Loader, the ranges displayed at Project Settings -> Flash were incorrect. Fixed.
- Linux / macOS: Licenses added through the J-Link License Manager were not correctly detected. Fixed.
- Setting a J-Link Devices XML file via CL parameter could cause J-Flash to crash. Fixed.
SWO Viewer CL
- A target device could no longer be selected without passing it as command line parameter. Fixed.
Version V6.72b (2020-05-04)
Firmware
- Flasher: Firmware showed wrong serial number. Fixed.
SWO Viewer
- Displayed SWO frequency was not updated correctly when no frequency was selected in configuration dialog by user.
- Improved logging performance when using GUI.
- Pause/ Resume button did not work correctly. Fixed.
Version V6.72a (2020-04-30)
Commander
- Added support for Cortex-M55 core
DLL
- Added support for Cortex-M55 core
- Compare progress bar overflow, fixed.
- IAR EWARM: When using POWERTRACE, IAR could hang when halting the target CPU. Fixed.
- If debugger requested a CPU register index that was out of bounds, application could crash. Fixed.
- NXP LPC80x device series: Flash programming did fail for the last sector. Fixed.
- Overflow of percentage progress value for J-Link Commander. Fixed.
- STM32H7-dual core devices: Trace peripherals were not detected correctly. Fixed.
GDB Server
- Added support for Cortex-M55 core
- VisualGDB: Live update of variables (while CPU is running) was slow (reading 1 variable could take up to 20ms). Fixed.
J-Flash
- Added check for overlapping flash banks to programming/erasing/reading/... procedures.
- Added support for Cortex-M55 core
- Improved check for overlapping flash banks.
- Linux: Creating a new project could crash J-Flash sometimes. Introduced with V6.72. Fixed.
- Passed command line parameters will now be added to the J-Flash log file.
- Saving files (e.g. data files) did not work correctly when the file extension was not explicitly set inside the file dialog input field. Fixed.
J-Flash Lite
- The clipboard was cleared when closing the application. Fixed.
J-Flash SPI
- Passed command line parameters will now be added to the J-Flash SPI log file.
- Saving files (e.g. data files) did not work correctly when the file extension was not explicitly set inside the file dialog input field. Fixed.
- The log mentioned "J-Flash" instead of "J-Flash SPI" at the beginning. Fixed.
- When adding a custom init. or exit step, a message box could appear saying "Failed to parse bytestream", even for action types which do not require a bytestream to be entered. Introduced with V6.70. Fixed.
RTT Viewer
- Under special circumstances it could happen that text output was no longer updated even if new data was received from the target device. Fixed.
SWO Viewer
- Adjusted Pause/ Resume button appearance.
- Under special circumstances it could happen that text output was no longer updated even if new data was received from the target device. Fixed.
Version V6.72 (2020-04-28)
Configurator
- For Flasher ATE, the string for "host firmware" in the emulator table has been replaced by a link to segger.com.
- macOS: Binary for GUI application was included twice in the software package - once in the .app bundle and once again "stand-alone". Removed the "stand-alone" binary.
DLL
- Added (QSPI) flash programming support for the Cortex-M4 core of NXP iMXRT117x series devices.
- Added debug support for Cypress CY8C4148xxx-Sxxx series (PSoC4100S Plus family).
- Added debug support for Cypress CY8C4148xxx-Sxxx series (PSoC4100S Plus family).
- Added debug support for Cypress CY8C4546xxx-Sxxx series (PSoC4500 family).
- Added debug support for Cypress CY8C4547xxx-Sxxx series (PSoC4500 family).
- Added debug support for Cypress CY8C4548xxx-Sxxx series (PSoC4500 family).
- Added debug support for GigaDevice GD32F33x family (e.g. GD32F330G4).
- Added debug support for the Cortex-M4 core of NXP iMXRT117x series devices.
- Added flash programming support for Cypress CY8C4148xxx-Sxxx series (PSoC4100S Plus family).
- Added flash programming support for Cypress CY8C4148xxx-Sxxx series (PSoC4100S Plus family).
- Added flash programming support for Cypress CY8C4546xxx-Sxxx series (PSoC4500 family).
- Added flash programming support for Cypress CY8C4547xxx-Sxxx series (PSoC4500 family).
- Added flash programming support for Cypress CY8C4548xxx-Sxxx series (PSoC4500 family).
- Added flash programming support for GigaDevice GD32F33x family (e.g. GD32F330G4).
- Added secure flash bank for NXP LPC55xx series devices.
- Flash programming dialog did not show total elapsed time (stayed at 0.000 sec). Fixed.
- LPC8xx family: Reset: Added backwards compatibility for J-Links V8 and older.
Firmware
- Flasher PRO/ARM/Portable PLUS: BlueNRG2 was not unsecured in stand-alone mode. Fixed.
- J-Link EDU Mini: ST STM32H7 series: When using ETB trace, SFRs in the DBGMCU domain were not longer accessible by the target application and returned 0x0 on read. Fixed.
- J-Link EDU/BASE/PLUS V10: ST STM32H7 series: When using ETB trace, SFRs in the DBGMCU domain were not longer accessible by the target application and returned 0x0 on read. Fixed.
- J-Link EDU/BASE/PLUS V11: ST STM32H7 series: When using ETB trace, SFRs in the DBGMCU domain were not longer accessible by the target application and returned 0x0 on read. Fixed.
- J-Link PRO V4: ST STM32H7 series: When using ETB trace, SFRs in the DBGMCU domain were not longer accessible by the target application and returned 0x0 on read. Fixed.
- J-Link ULTRA+ V4: ST STM32H7 series: When using ETB trace, SFRs in the DBGMCU domain were not longer accessible by the target application and returned 0x0 on read. Fixed.
- J-Link WiFi V1: ST STM32H7 series: When using ETB trace, SFRs in the DBGMCU domain were not longer accessible by the target application and returned 0x0 on read. Fixed.
- J-Trace PRO V2 Cortex-M: ST STM32H7 series: When using ETB trace, SFRs in the DBGMCU domain were not longer accessible by the target application and returned 0x0 on read. Fixed.
- J-Trace PRO V2 Cortex: ST STM32H7 series: When using ETB trace, SFRs in the DBGMCU domain were not longer accessible by the target application and returned 0x0 on read. Fixed.
J-Flash
- Added version check when opening project files.
- J-Flash can now automatically update project files upon opening, if necessary. Example case: Internal flash bank information inside the J-Link DLL was changed from one version to another.
- Menu bar actions under "Edit" were not enabled when a data window was open but no project was open. Fixed.
- Project settings --> Flash: The "Select flash device" button was missing. Fixed.
J-Mem
- macOS: Binary for GUI application was included twice in the software package - once in the .app bundle and once again "stand-alone". Removed the "stand-alone" binary.
RTT Viewer
- Added a "Stay on top" action to the menu bar.
- macOS: Binary for GUI application was included twice in the software package - once in the .app bundle and once again "stand-alone". Removed the "stand-alone" binary.
- Tabs can now be closed by clicking on them with the middle mouse button (except for "All Terminals" tab).
SWO Viewer
- macOS: Binary for GUI application was included twice in the software package - once in the .app bundle and once again "stand-alone". Removed the "stand-alone" binary.
Version V6.70g (2020-04-23)
J-Flash
- When programming serial numbers with auto increment, the serial number was sometimes not incremented correctly. Fixed.
- When programming serial numbers without a S/N list file, a warning message box would pop up. Fixed.
J-Link Package
- Installer: Windows: If installer was renamed by user before execution, installation failed. Fixed.
Version V6.70f (2020-04-22)
DLL
- Open Flashloader: The "Aliases" tag could not be used to extend an existing device. Fixed.
- Ozone: When using live trace, instruction counters in sections smaller than 16 bytes were not incremented correctly. Fixed.
- Renesas RX: Software breakpoints in flash did not work. Fixed.
- ST STM32F0xx family: Unlock did not work correctly. Fixed.
- When selecting a target device using the device selection dialog, the DLL did not detect the dialog closing correctly and would wait endlessly. Fixed.
J-Flash
- In 2-byte and 4-byte mode, data windows were displaying incorrect values for items which contained one or more invalid bytes (e.g. after the last valid memory address). Fixed.
J-Flash SPI
- In 2-byte and 4-byte mode, data windows were displaying incorrect values for items which contained one or more invalid bytes (e.g. after the last valid memory address). Fixed.
Version V6.70e (2020-04-17)
Commander
- Log output for "calibrate" command did not print any values. Fixed.
DLL
- ARM China STAR core was shown as "???" for core in the device selection dialog. Fixed.
- Flasher: Stand-alone mode programming did not work for certain Synergy S7 devices. Fixed.
- Handling of flash protection registers for ONSemiconductor Nebo40 family devices, fixed.
- Some message boxes contained the J-Link DLL version twice. Fixed.
- User data and lock bit page size for Giant Gecko device family fixed.
- When selecting the first device inside the device selection dialog, the line above it (with filter fields) was highlighted as well. Fixed.
DLL Updater
- Installed SEGGER Embedded Studio instances V4.51 and later were not found. Fixed.
Firmware
- Flasher: Stand-alone mode programming did not work for certain Synergy S7 devices. Fixed.
GDB Server
- Unified ini/settings file name under all OS platforms. (JLinkGDB ServerSettings.ini)
GUI Applications
- On Windows 10, some dialog text was too small with text scaling at 100% on a 4K Display. Fixed.
- The point size of a log element's default font was not correct. Fixed.
- Updated the colors used for selected text to fit better into operating system style.
J-Flash
- A data file could only be opened with an open project. Fixed.
- Project settings dialog: Flash tab: When clicking a checkbox inside the 'sector selection' table, the scroll bar jumped to the top. Fixed.
- Removed redundant margins inside the "project information" window.
- Some project files caused a message box saying "Expected ',', got ''" due to incorrect parsing. Fixed.
- Unified ini/settings file name under all OS platforms. (JFlashSettings.ini)
- Updated interface for data windows so it fits better into the overall style of the GUI.
- When changing the selected target device in the 'Project Settings' dialog, it could happen that the data inside the 'Flash' tab was not updated correctly. Fixed.
- When creating a new project, Cortex-M0 was selected as default target core. Changed so user has to select target device manually.
- When selecting a target device, the target device selection dialog did not start with focus inside the edit field to look for a target device. Fixed.
- When selecting the first device inside the device selection dialog, the line above it (with filter fields) was highlighted as well. Fixed.
- When using the -unsecurechip option in the command line, a dialog for invalid license popped up, even when a valid license was present. Fixed.
J-Flash SPI
- Removed redundant margins inside the "project information" window.
- Some project files caused a message box saying "Expected ',', got ''" due to incorrect parsing. Fixed.
- Unified ini/settings file name under all OS platforms. (JFlashSPISettings.ini)
- Updated interface for data windows so it fits better into the overall style of the GUI.
J-Mem
- Linux/macOS: Settings file contained backslashes. Fixed.
- Unified ini/settings file name under all OS platforms. (JMemSettings.ini)
- When closing J-Mem, the clipboard was cleared. Fixed.
Manual
- UM08003: All chapters: Updated for new version of J-Flash.
- UM08003: Chapter "Target systems" * Section "Which devices can be programmed by J-Flash?": Added reference to SEGGER Wiki article about 'Open Flash Loader'.
RTT Logger
- Linux/macOS: Default log file contained backslashes. Fixed.
RTT Viewer
- Added an "Edit font size" action to the menu bar.
- Linux/macOS: Settings file contained backslashes. Fixed.
- Unified ini/settings file name under all OS platforms. (JLinkRTTViewerSettings.ini)
SWO Viewer
- Linux/macOS: Settings file contained backslashes. Fixed.
- Unified ini/settings file name under all OS platforms. (JLinkSWOViewerSettings.ini)
Version V6.70d (2020-04-16)
Firmware
- J-Link EDU Mini: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
- J-Link EDU/BASE/PLUS V10: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
- J-Link EDU/BASE/PLUS V11: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
- J-Link PRO V4: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
- J-Link ULTRA+ V4: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
- J-Link WiFi V1: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
- J-Link-OB-SAM3U128 V3: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
- J-Link-OB-STM32F103: cJTAG: TCK was not toggled correctly at certain steps during the cJTAG init sequence which could cause problems with some target devices. Fixed.
- J-Trace Cortex-M PRO V1 : SPI interface was reported as not supported. Fixed.
- J-Trace PRO V2 Cortex-M: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
- J-Trace PRO V2 Cortex: Self-recovery of config area (added in V6.70) could interfere with Embedded Studio licenses stored in J-Link (if used as dongle). Fixed.
Version V6.70c (2020-04-07)
Commander
- Printing registers could had lead to a segmentation fault. Fixed.
DLL
- NOP instructions were not handled correctly in Cortex-A PTM trace. Fixed.
- RISC-V: CPU registers were not restored correctly after flash programming. This could make CPU crash when using flash breakpoints feature. Fixed.
- Under certain circumstances skip count of branch coverage for Cortex-A trace was incorrect. Fixed.
Firmware
- J-Link-OB-SAM3U128 V3: Drag and drop device did not show up in file explorer. Introduced in V6.62. Fixed.
J-Flash
- J-Flash would sometimes crash when creating more than 4 data windows. Fixed.
Version V6.70b (2020-04-03)
DLL
- Qorvo QPG5071: Flash programming did not work for the alternate flash section at address 0x4200000. Fixed.
- Qorvo QPG6100: Flash programming did not work for the alternate flash section at address 0x4200000. Fixed.
Firmware
- Flasher: The power down of the debug interface after programming in stand-alone mode did not work for all devices. Fixed.
J-Flash
- Flasher config files were generated with an incorrect size. Fixed.
- The command line option "-min" did not affect progress dialogs. Fixed.
- When relocating memory via "Edit -> Relocate", it was not possible to enter a '-' for a negative offset. Fixed.
- When save-on-close was enabled and the project was modified, the user could not save it manually. Fixed.
- When trying to open a .bin file without any project opened, a warning message box appeared. Fixed.
J-Flash SPI
- The command line option "-jflashlog" did not work correctly. Fixed.
- The command line option "-min" did not affect progress dialogs. Fixed.
- When relocating memory via "Edit -> Relocate", it was not possible to enter a '-' for a negative offset. Fixed.
- When save-on-close was enabled and the project was modified, the user could not save it manually. Fixed.
Version V6.70a (2020-03-30)
DLL
- Linux: When a new firmware was available for a connected J-Link, the user was not asked if the update should be performed. Fixed.
- macOS: When a new firmware was available for a connected J-Link, the user was not asked if the update should be performed. Fixed.
- RISC-V: C.LUI Rd, Imm6 instruction was simulated incorrectly (e.g. during single stepping). Fixed.
- SiLabs EFx32 family: Under special circumstances, connect did not work. Fixed.
J-Link Package
- Linux: The J-Link software was linked against too new versions of some libraries. Introduced in V6.70. Fixed.
Remote Server
- Linux: When a ppp interface was present, the application could crash. Fixed.
Version V6.70 (2020-03-27)
Commander
- RISC-V: "step" command now shows changed register contents with each step.
- RISC-V: Changed register names shown on "regs" command to symbolic assembler names (a0, a1, sp, ...)
- RISC-V: Improved display of registers shown on "regs" command.
- When using "disassemble" on a RISC-V target, the numeric register names were used. Switched to ABI register names.
DLL
- Added command string "RISCV_SetTEBaseAddr" to support on-chip trace for SiFive target devices.
- Added debug support for Eta Compute ECM3532 series devices.
- Added debug support for Qorvo QPG5071 series devices.
- Added debug support for Qorvo QPG6100 series devices.
- Added debugging and (internal) flash programming support for Microchip ATSMAE51Gxx and ATSAME51Pxx series devices.
- Added flash programming support for Eta Compute ECM3532 series devices.
- Added flash programming support for Qorvo QPG5071 series devices.
- Added flash programming support for Qorvo QPG6100 series devices.
- Added support for ARM China STAR core.
- Added support for SiFive RISC-V on-chip trace (Insight trace).
- Apollo3 (plus): Added native SWO support.
- Connect to Cortex-M4 of STM32H7x5/x7 series devices, when M7 boot is deactivated, fixed.
- For Cortex-M, the DLL did not support >= 16 hardware breakpoints. Fixed.
- NordicSemi nRF5340: Added unsecure support concerning debug protection for the network core.
- NXP RT106x: QSPI programming did not work for some already supported flashes. Fixed.
- SiLabs EFx32 family: Under special circumstances, connect took up to 60 seconds. Fixed.
- ST STM32H745/STM32H750 series devices dual SPI flash programming fixed.
- The "unknown device selected" dialog title contained "J-Link V<Version>" twice. Fixed.
- When a J-Link script file function could not be executed in the J-Link FW a message box popped up with an incorrect title. Fixed.
- When closing a firmware update messagebox by pressing [ Esc ], the firmware update was still executed. Fixed.
- When having multiple J-Link Remote Server instances running on the same machine, it could happen that when disconnecting one client from one server, the other server also lost its connection. Fixed.
Firmware
- J-Link EDU Mini: Added self-recovery of config area in case it contained garbage data
- J-Link EDU/BASE/PLUS V10: Added self-recovery of config area in case it contained garbage data
- J-Link EDU/BASE/PLUS V11: Added self-recovery of config area in case it contained garbage data
- J-Link PRO V4: Added self-recovery of config area in case it contained garbage data
- J-Link ULTRA+ V4: Added self-recovery of config area in case it contained garbage data
- J-Link WiFi V1: Added self-recovery of config area in case it contained garbage data
- J-Trace PRO V2 Cortex-M: Added self-recovery of config area in case it contained garbage data
- J-Trace PRO V2 Cortex: Added self-recovery of config area in case it contained garbage data
J-Flash
- Added a new exit-step for reporting an error.
- Added support for .elf files.
- Data files for stand-alone mode could be incorrect under special circumstances. Fixed.
- Drag and drop of data files did not work correctly when moving the cursor over an already open data window. Fixed.
- Improved performance.
- Linux: Added J-Flash for Linux.
- macOS: Added J-Flash for macOS.
- Project settings dialog: "OK" button did not save settings. Fixed.
- Project settings dialog: Init/ Exit steps: "Edit" dialog: The input fields for values of a custom CPU action were not displayed correctly. Fixed.
- Project settings dialog: Init/ Exit steps: Double-clicking a row or pressing the "Return" button when a row was selected did not open an "Edit" dialog. Fixed.
- Project settings dialog: Init/ Exit steps: The "Edit" dialog was not blocking. Fixed.
- Project settings dialog: Removed redundant "Apply" button.
- Removed nested elements inside "Project information".
- Some menubar actions for programming the target were enabled even without any data to program selected. Fixed.
- When a read operation failed a data window without any contents was created. Fixed.
- When a target connection was established, the target voltage was not checked anymore. Fixed.
- When an open data file is modified by another application, J-Flash informs the user.
- When creating a data-window (e.g. via Target --> Test --> Generate test data), trying to save it via "Save data file" did not work correctly. Fixed.
- When having no project open and creating a new project, some menu bar actions were still disabled. Fixed.
- When saving a data-file but cancelling the file dialog, a "data was changed in background" message appeared. Fixed.
- When scrolling inside a data window, the displayed memory was shown as "invalid" until the user stopped scrolling. Fixed.
- When selecting a device, the device selection dialog did not highlight the previously selected device. Fixed.
- Windows: Updated GUI.
J-Flash SPI
- Added SPI Flash programming support for Macronix MX66U1G45G.
- Added SPI Flash programming support for Macronix MX66U2G45G.
- Added support for .elf files.
- Drag and drop of data files did not work correctly when moving the cursor over an already open data window. Fixed.
- Improved performance.
- Linux: Added J-Flash SPI GUI for Linux.
- macOS: Added J-Flash SPI GUI for macOS.
- Project settings dialog: Init/ Exit steps: "Edit" dialog: The input fields for values of a custom CPU action were not displayed correctly. Fixed.
- Project settings dialog: Init/ Exit steps: Double-clicking a row or pressing the "Return" button when a row was selected did not open an "Edit" dialog. Fixed.
- Project settings dialog: Init/ Exit steps: The "Edit" dialog was not blocking. Fixed.
- When an open data file is modified by another application, J-Flash SPI informs the user.
- When scrolling inside a data window, the displayed memory was shown as "invalid" until the user stopped scrolling. Fixed.
- Windows: Updated GUI.
Manual
- UM08001: Chapter "J-Flash SPI" updated for recently added cross-platform availability of J-Flash SPI.
- UM08001: Chapter "J-Link Commander (Command line tool)" *Section "Command line options": Moved to SEGGER wiki.
- UM08001: Chapter "J-Link Commander (Command line tool)" *Section "Using J-Link Command Files": Moved to SEGGER wiki.
- UM08001: Chapter "J-Link GDB Server" *Section "Command line options": Replaced occurrences of "OS X" with "macOS".
- UM08003: All chapters updated for recently added cross-platform availability of J-Flash.
Remote Server
- Added option to display the password in the connection string as plaintext.
- When using the GUI and closing the application, the application could crash. Fixed.
RTT Logger
- Added a warning message in case the RTT log file could not be created or written.
- Changed default RTT log file path to a location that should always be writable.
RTT Viewer
- MacOS: RTT Viewer did not start. Fixed.
- Moved the Log window below the terminals, so that it is always visible.
- Under some circumstances, action bar action "Open terminal on output" did not work correctly. Fixed.
Version V6.64a (2020-03-18)
DLL
- ARMv8M: Under special circumstances, reset did not work. Fixed.
- Having two instances of the device selection dialog open and closing one could cause a crash. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V10: Firmware could crash if IP-over-USB feature was enabled. Fixed.
- J-Link EDU/BASE/PLUS V11: Firmware could crash if IP-over-USB feature was enabled. Fixed.
- J-Link-OB-SAM3U128-NordicSemi: Drag and drop device did not show up in file explorer. Introduced in V6.62. Fixed.
J-Mem
- The icons for selecting a display width were blurry. Fixed.
RTT Viewer
- Terminal logging did not work correctly when the RTT Viewer received data that did not end in a linebreak. Fixed.
- When starting terminal logging, the file selection dialog appeared twice. Fixed.
Version V6.64 (2020-03-13)
Commander
- Linux: w1/w2/w4 commands could crash with segmentation fault when passing more than 32 items per call. Fixed.
DLL
- Added (QSPI) flash programming support for NXP iMXRT117x series devices.
- Added (QSPI) flash programming support for Realtek RTL872xCS series devices.
- Added debug support for Cypress CYBLE-214015-01 series devices.
- Added debug support for Micronas HVC4420F series devices.
- Added debug support for Nordic Semi nRF52820_xxAA devices.
- Added debug support for TI AM572x series devices, Cortex-A15 and Cortex-M4.
- Added debugging support for Dialog Semiconductor DA14585 series devices.
- Added debugging support for Dialog Semiconductor DA14586 series devices.
- Added flash programming support for Cypress CYBLE-214015-01 series devices.
- Added flash programming support for Cypress CYPD319xx devices.
- Added flash programming support for Micronas HVC4420F series devices.
- Added flash programming support for Nordic Semi nRF52820_xxAA devices.
- Added flash programming support for NXP KM35 family.
- Added Flash programming support for ST STM32G473xx series devices.
- Added internal flash programming support for Hilscher NetX990 Application Core.
- Added internal flash programming support for ONSemiconductor Nebo40 family devices.
- Added internal flash programming support for ST STM32G484xE series devices.
- Added internal flash programming support in SPIFI-Lib for Winbond W25Q512JV SPI flash.
- Added lock detection and and unlock sequence for ONSemiconductor Nebo40 series devices.
- Added support for the Macronix MX25UM51345G octaflash to our (Q)SPI based flash algorithms.
- Added Winbond W25Q512JV to openflashloader for STM32F746 Discovery QSPI.
- Added Winbond W25Q512JV to openflashloader for STM32F769I EVAL QSPI.
- Analog Devices CM40z: Unified device names shown in the J-Link software.
- Cypress CYPD312xx (CCG3): Some devices names were not recognized by the DLL. Fixed.
- Cypress CYPD317xx (CCG3PA): Wrong flash size was displayed. Fixed.
- EFM32TG11B: Added native MTB support.
- Infineon TLE9850QX and TLE9852XQ: Under special circumstances, connect did not work. Fixed.
- J-Trace PRO V2 Cortex-M: USB only: If a command was exactly 512/1024 bytes in size, J-Link software hung. Fixed.
- J-Trace PRO V2 Cortex: USB only: If a command was exactly 512/1024 bytes in size, J-Link software hung. Fixed.
- Lifted the max. RAM size of Open Flashloader based algorithms from 32 KB to 512 KB.
- Nordic nRF59160: The device name "nRF9160_xxAA" was not recognized by the J-Link DLL. Fixed.
- NordicSemi nRF5340: Added unsecure support concerning debug protection for the application core.
- NXP K32L2A / K32L2B: The J-Link DLL reported "unknown device selected" for some K32L2A / K32LB based devices (e.g. K32L2B31XXX0A). Fixed.
- NXP LPC54018: Added native support for SWO.
- NXP LPC55S69: Added native support for SWO.
- NXP LPC55xx: Reset did not work correctly, when an invalid application was present. Fixed.
- NXP MKW37Z512xxx4 could not be selected in the device selection dialog. Fixed.
- Renesas RA6M3: QSPI flash programming did not work. Fixed.
- Renesas S124: Read back of data flash did not work. Fixed.
- Renesas S128: Read back of data flash did not work. Fixed.
- Renesas S3A3: Read back of data flash did not work. Fixed.
- RTT TELNET connection: Added config string "SetRTTAddr" (manually sets the addr. of the RTT control block and disables auto-detect).
- RTT TELNET connection: Added config string "SetRTTSearchRanges" (defines additional search ranges that will be searched during auto-detect of RTT control block).
- ST STM32WB55xx - FUS: After programming a new wireless stack, it was not started correctly. Fixed.
Firmware
- J-Link OpenSDA: Added new firmware port for TWR-KM35Z75M.
- J-Link-OB-K22-CortexA: VCOM: When using multi-VCOM, VCOM2 did not work properly. Fixed.
- J-Link-OB-K22-CortexM: VCOM: When using multi-VCOM, VCOM2 did not work properly. Fixed.
- J-Link-OB-K22-SiFive: Activated WinUSB/WebUSB by default, allowing to use WebUSB with this OB: https://wiki.segger.com/J-Link:WebUSB
- J-Link-OB-K22-SiFive: Changed WebUSB selection name to "HiFive"
- J-Link-OB-STM32F103: Added support for cJTAG target interface
J-Flash
- Lifted the max. RAM size of Open Flashloader based algorithms from 32 KB to 512 KB.
- The J-Link DLL version used by J-Flash was displayed incorrectly. Fixed.
J-Flash SPI
- Added Flash programming support for Winbond W25Q512JV SPI flash.
- Added FRAM memory support (Fujitsu MB85RS256TY).
J-Flash SPI CL
- Added FRAM memory support (Fujitsu MB85RS256TY).
RTT Viewer
- Attach mode: Added support for additional search ranges.
- Attach mode: Added support for manually specifying the address of the RTT control block.
Version V6.62d (2020-03-02)
DLL
- Added (secure) flash programming support for NXP iMXRT600 (Details: https://wiki.segger.com/i.MXRT600).
- Cortex-M connect fallback: An internal error flag was not correctly cleared when the DLL recovered from a connect error. Fixed.
- Cortex-M, Cortex-AR, RISC-V: Specifying more than 10 APs in a J-Link script file did not work. Fixed.
- NordicSemi nRF5340: Added unsecure support concerning debug protection for the application core.
- NXP iMXRT600: Flash programming did not work for address offset >= 16 MB. Fixed.
- NXP LPC55S69: SWO base clock was not calculated correctly. Fixed.
- ST STM32F1xxx: Under some circumstances, the unsecure/unlock mechanism did not work correctly. Fixed.
- The DLL checked the passed device name case-sensitive resulting in some devices were no longer recognised (e.g. "nRF51" when passing "nrf51" or "NRF51"). Fixed.
- TI MSP432P411Y: Under special circumstances, flash programming did not work. Fixed.
- Verification of option memory programming for Renesas S5D9 series devices could fail, fixed.
J-Flash SPI
- Files with .mcs suffix were not opened/saved correctly, fixed.
J-Link Package
- Linux: The .deb package Installed-Size value was wrongly set as a GB value instead of MB. Fixed.
License Manager
- (Linux) Adding licenses did not work correctly. Fixed.
- (macOS) Adding licenses did not work correctly. Fixed.
Manual
- UM08001: J-Link script files chapter: Added function parameter limitation.
Version V6.62c (2020-02-21)
DLL
- (Linux) Flash programming dialog: The color of the text inside the progress bar changed from black to white. Fixed.
- (macOS) Firmware update dialog: Updated style of progress bar for better visibility.
- (Windows) Flash programming dialog: The color of the text inside the progress bar changed from black to white. Fixed.
- Added debug and (QSPI) flash programming support for Renesas RZ/T1M series devices.
- Added flash programming support for NXP iMXRT600 (Details: https://wiki.segger.com/i.MXRT600).
- NXP RT600: Removed old device names.
- OpenFlashLoader: When writing flash breakpoints, the Init() function was not called correctly. Fixed.
Version V6.62b (2020-02-17)
Configurator
- Added "Copy emulator info" feature to context menu of emulator tables.
DLL
- (Linux) The flash programming dialog could flicker on systems using IceWM. Fixed.
- (Linux) The flash programming dialog progress bars were rendered incorrectly on systems using IceWM. Fixed.
- (macOS) Updated style for the flash programming dialog progress bars.
- (QSPI)Flash programming support for iMXRT102x series devices, fixed.
- Command string "CORESIGHT_SetIndexAPBAPToUse" did not work correctly. Fixed.
- Corrected company name "Eta Compute" (new) / "Eta-Computing" (old).
- NXP iMXRT106x: (Q)SPI flash programming did not work when using Adesto ATXP064 as external flash. Fixed.
- Programming speed for (QSPI) flash programming with Realtek RTL872xCS series devices, improved.
- RAM size of Analog Devices CM40z_128_256, CM40z_128_512 and CM40z_128_1024 devices was wrong. Fixed.
Firmware
- Flasher ARM/PRO/Portable PLUS: EFR32/EFM32 programming did not work in stand-alone mode. Fixed.
GUI Applications
- (Windows) Some GUI applications cleared the clipboard on close. Fixed.
J-Flash SPI
- Displayed name of Macronix MX25R6435F SPI Flash, fixed.
- When reading back very large chunks at once (> 64 KB, e.g. when reading back complete chip), USB communication could lock-up. Fixed.
Version V6.62a (2020-01-31)
Commander
- With ASCII view enabled for mem commands, the console output was incorrect when one of the ASCII symbols was a percentage sign ("%"). Fixed.
DLL
- (Linux) In some occasions, selecting an emulator from the USB selection dialog did not work correctly. Fixed.
- (Linux) The firmware update dialog could flicker on systems using IceWM. Fixed.
- Analog Devices CM40x family: Updated device name scheme.
- NXP iMXRT500: Under special circumstances (no bootable application), reset did not work. Fixed.
- Under special circumstances, blank check did not work. Introduced in V6.52. Fixed.
Firmware
- Flasher ARM/PRO/Portable PLUS: The JTAG target interface did not work correctly, if the SPI target interface was used before. Fixed.
- Flasher ARM/PRO: Added verbosity level for terminal messages.
GUI Applications
- (Linux) On some distributions (e.g. Ubuntu 18.04) it could happen that the last word inside a log element would not be painted correctly. Fixed.
- Selecting a row inside a table also selected the table header. Fixed.
J-Flash
- Under special circumstances, blank check did not work. Introduced in V6.52. Fixed.
Remote Server
- Updated GUI.
Version V6.62 (2020-01-24)
Commander
- (macOS/Linux): Entering '?' as device name did not show device selection dialog. Fixed.
- Extended the output message of the IsHalted command to also show the current PC in case CPU is halted.
Configurator
- J-Trace PRO probes were displayed as "J-Link (unknown)". Fixed.
DLL
- "Out of breakpoints" dialog on windows had broken title and cut off text for a checkbox. Fixed.
- (macOS/ Linux) "Out of breakpoints" dialog was not displayed. Fixed.
- (Windows): After a dialog from the DLL was closed, the original window did not regain keyboard focus. Fixed.
- A deadlock could happen when a dialog created from the DLL was closed. Fixed.
- Added debug support for CKS CS32F103 (CS32F103C8 and CS32F103CB).
- Added debug support for Microchip "SAM9X60" series devices.
- Added debug support for Microchip DEC15xx family.
- Added debug support for Microchip MEC15xx family.
- Added debug support for Microchip PIC32CX0525SG12 family.
- Added debug support for NXP K32L2A (e.g. K32L2A31xxxxA and K32L2A41xxxxA).
- Added debug support for NXP K32L2B (e.g. K32L2B31xxxxA, K32L2B21xxxxA and K32L2B11xxxxA).
- Added debug support for NXP LPC55S16 (Niobe4 Mini).
- Added debugging support for TI AM437x series devices.
- Added flash programming support for AmbiqMicro Apoolo3 Blue Plus family (AMA3B2KK-KBR, AMA3B2KK-KCR).
- Added flash programming support for CKS CS32F103 (CS32F103C8 and CS32F103CB).
- Added flash programming support for Cypress CYT4BB and CYT3BB series devices.
- Added Flash programming support for Eta-Compute ECM3531 series device.
- Added flash programming support for NXP K32L2A (e.g. K32L2A31xxxxA and K32L2A41xxxxA).
- Added flash programming support for NXP K32L2B (e.g. K32L2B31xxxxA, K32L2B21xxxxA and K32L2B11xxxxA).
- Added flash programming support for NXP LPC55S16 (Niobe4 Mini).
- Added flash programming support for ST's STM32H7Axx / STM32H7Bxx family.
- Added flash programming support for Toshiba TMPM3HLFDUG, TMPM3HLFYUG, TMPM3HLFZUG.
- Added following device names for iMXRT1011 series devices, "MIMXRT1011XXX5A", "MIMXRT1011XXX5A".
- Added internal flash programming support for Nuvoton M031xx and M032xx series devices.
- Added missing entry for J-Link EDU Mini, as probe was identified as unknown probe, in J-Link Registration application.
- Added native SWO support for STM32WP55xx-series devices.
- Added new command string "CORESIGHT_SetDebugAPToUse" for allow specifying the APBaseAddr for CoreSight SoC-600 setups.
- Added programming support for WWR section within Microchip ATSAMR34/35 series devices.
- Added QSPI flash programming support for Nuclei N1xx, N2xx, N3xx, N6xx series cores bistreams on ARTY boards.
- Added QSPI flash programming support for Renesas RZ devices.
- Added SPI flash programming support for Microchip MEC15xx family.
- Added SPI flash programming support for Microchip PIC32CX0525SG12 family.
- Added support for Adesto ATXP064B series flash devices.
- Added support for GigaDevice GD25LQ128D and GD25LD128D for all QSPI based flash banks.
- Added support for Microchip SST25PF040C series flash devices for any (Q)SPI based flash bank.
- ARMv8-M: Under special circumstances, when running code in non secure mode, system reset did not work. Fixed.
- Cortex-M: Added support for CoreSight SoC-600 setups.
- Cypress PSc4A S0 - S3: Connect and reset did not work under special circumstances. Fixed.
- Firmware update: When suppressing the firmware update dialog, the DLL crashed. Introduced in V6.60. Fixed.
- Flash programming algo for STM32G43xx series devices, fixed.
- Flash programming dialog could crash. Introduced in V6.60. Fixed.
- Flash programming dialog could show "0.000s" for some steps even though they took time. Introduced in V6.60. Fixed.
- Flasher ARM: Open flash loader: When programming very large chunks at once in RAMCode (> 32 KB), USB communication could lock-up. Fixed.
- Flasher Portable PLUS: Open flash loader: When programming very large chunks at once in RAMCode (> 32 KB), USB communication could lock-up. Fixed.
- Flasher PRO: Open flash loader: When programming very large chunks at once in RAMCode (> 32 KB), USB communication could lock-up. Fixed.
- Improved/Reduced DLL startup time.
- In some occasions, restoring keyboard focus after displaying a dialog could lead to a deadlock. Fixed.
- Linux: If a file was specified to be opened exclusively (e.g. SEGGER registry), this did not work correctly, so a 2nd process could modify the file at the same time. Fixed.
- Naming for Toshiba TMPM4G9F15FG, fixed.
- Nordic Semi nRF5340 Application core: When the application core is protected and we wanted to connect to it, we accidentally would have connected to the network core. Fixed.
- NXP iMXRT500: Under special circumstances, reset did not work. Fixed.
- NXP LPC55Sxx: Attach to a running target did not work. Fixed.
- Option Byte data preparation for STM32G0x0 series devices, fixed.
- RAM size for CYT2B7 series devices, updated.
- RAM size for CYT2B9 and CYT4BF series devices, updated.
- Reduced number of alloc calls when evaluating JLinkDevices.xml by factor 14,000 which results in a speed improvement of 10-20% during XML parse.
- Reduced time for Cortex-M connect up to 64ms (depending on host system).
- RISC-V: Added support for CoreSight SoC-600 setups.
- RISC-V: JALR rd, rs1, SImm instruction was simulated incorrectly if rd == rs1. Fixed.
- Silicon Labs EFR32xG22: Under special circumstances, reset did not work properly. Fixed.
- Some device names passed to the DLL by IAR EWARM were not recognized correctly (e.g. MCIMXRT1064). Fixed.
- Some messagebox titles were displayed incorrectly. Fixed.
- Some Renesas R7F0E01 series devices could not be selected in the DLL. Fixed.
- SPIFI-Lib added SPI Flash programming support for GigaDevice GD25LF255E.
- SPIFI-Lib added SPI Flash programming support for Winbond W25Q256PW
- STM32F030F4: In Keil uVision, STM32F030F4Px was not correctly detected as an STM32F030F4 device. Fixed.
- STM32L0: Under some circumstances, wrong reset values were written to the option bytes section when unlocking the device. Fixed.
- Target RAM address was not correct for the MKL27Z32xxx4 devices. Fixed.
- The RWW section of ATSAMC2x/ATSAMD2x devices was not erased before programming. Fixed.
- Under certain circumstances Keil uVision crashed when using RTT Viewer in attach mode. Fixed.
- Unified display of flash bank sizes for device selection dialogs across all J-Link utilities.
- Windows 10: Flash programming progress dialog could flicker. Fixed.
Firmware
- Flasher: Erase was not handled correctly for flash banks supporting automatic erase. Fixed.
- J-Link EDU Mini: Cortex-M: Added support for CoreSight SoC-600 setups.
- J-Link EDU Mini: RISC-V: Added support for CoreSight SoC-600 setups.
- J-Link EDU/BASE/PLUS V10: Cortex-M: Added support for CoreSight SoC-600 setups.
- J-Link EDU/BASE/PLUS V10: RISC-V: Added support for CoreSight SoC-600 setups.
- J-Link EDU/BASE/PLUS V11: Cortex-M: Added support for CoreSight SoC-600 setups.
- J-Link EDU/BASE/PLUS V11: RISC-V: Added support for CoreSight SoC-600 setups.
- J-Link PRO V4: Cortex-M: Added support for CoreSight SoC-600 setups.
- J-Link PRO V4: RISC-V: Added support for CoreSight SoC-600 setups.
- J-Link ULTRA+ V4: Cortex-M: Added support for CoreSight SoC-600 setups.
- J-Link ULTRA+ V4: RISC-V: Added support for CoreSight SoC-600 setups.
- J-Link WiFi V1: Cortex-M: Added support for CoreSight SoC-600 setups.
- J-Link WiFi V1: RISC-V: Added support for CoreSight SoC-600 setups.
- J-Link-OB-K22-CortexA: VCOM: After 24 days of firmware up time, VCOM functionality became unresponsive. Fixed.
- J-Link-OB-K22-CortexM: VCOM: After 24 days of firmware up time, VCOM functionality became unresponsive. Fixed.
- J-Link-OB-K22-NordicSemi: VCOM: After 24 days of firmware up time, VCOM functionality became unresponsive. Fixed.
- J-Link-OB-K22-SiFive: VCOM: After 24 days of firmware up time, VCOM functionality became unresponsive. Fixed.
- J-Link-OB-SAM3U128 V1: VCOM: After 24 days of firmware up time, VCOM functionality became unresponsive. Fixed.
- J-Link-OB-SAM3U128 V3: VCOM: After 24 days of firmware up time, VCOM functionality became unresponsive. Fixed.
- J-Link-OB-SAM3U128-NordicSemi: VCOM: After 24 days of firmware up time, VCOM functionality became unresponsive. Fixed.
- J-Link-OB-STM32F072-128KB-CortexM: VCOM: After 24 days of firmware up time, VCOM functionality became unresponsive. Fixed.
- J-Trace PRO V2 Cortex-M: Added support for CoreSight SoC-600 setups.
- J-Trace PRO V2 Cortex: Added support for CoreSight SoC-600 setups.
- J-Trace PRO V2 RISC-V: Added support for CoreSight SoC-600 setups.
GDB Server
- (macOS): Restarting the GDB Server shortly after a previous instance of the GDB Server was closed could lead to the new instance to not start. Fixed.
- Added "ICSP" as valid argument for the command line option "-if".
GDB Server CL
- Added "ICSP" as valid argument for the command line option "-if".
J-Flash
- Added QSPI flash programming support for Renesas RZ devices.
- When passing the -exit parameter, a success messagebox could appear and keep J-Flash from self-exiting. Introduced with V6.60. Fixed.
J-Flash Lite
- The log was missing linebreaks in some cases. Fixed.
- The QSPI flash programming for NXPs iMXRT1010 family (e.g. MIMXRT1011CAE4A) was not erased by default. Fixed.
J-Flash SPI
- Added Eon EN25HQ16
- Added programming support for GigaDevice SPI Flashes, GD25Q05B, GD25Q10B, GD25Q20C, GD25Q40C, GD25Q80C, GD25Q16C.
- Added SPI Flash programming support for GigaDevice GD25LF255E.
- Added SPI Flash programming support for Winbond W25Q256PW.
- Added support for Adesto ATXP064B series flash devices.
- Added support for GigaDevice GD25LQ128D and GD25LD128D SPI flashes.
- Added support for ISSI IS25LP256E and IS25LP512M flashes.
- Added support for Microchip SST25PF040C series flash devices.
- IS25DLP flashes where successfully auto-detected although they are not supported due to a special required SPI command set. Corrected.
- Passing 'connect' via the command line without any J-Links connected, could lead to J-Flash SPI opening two modal dialogs at once. Fixed.
- Under special circumstances (compare enabled and data in flash == data to be programmed), flash programming failed. Fixed.
J-Flash SPI CL
- Additional licenses added to a J-Link were not recognized. Fixed.
- Under some circumstances, downloading a file led to an endless loop. Fixed.
Manual
- UM08001: Chapter "J-Link Commander (Command line tool)" *Section "Commands": Moved to SEGGER wiki.
Remote Server
- (Windows): Starting a second instance of the J-Link Remote Server did not work correctly. Introduced with V6.60. Fixed.
- Added field to change listening port for LAN mode.
- Connecting remotely to XMC1402-0200 devices did not work under some circumstances. Fixed.
- Removed excessive spacing between GUI elements.
RTT
- SEGGER_RTT_Conf.h: Updated LOCK/UNLOCK macros for ARMv8-M support.
- SEGGER_RTT_Conf.h: Updated LOCK/UNLOCK macros for RISC-V support.
- Updated KEIL syscalls file so it is compatible to uVision V5.
- Updated license
RTT Client
- Linux: While not being able to attach to a running debug session, RTT Client could eat up to 100% CPU time of a single core of the host system. Fixed.
- macOS: While not being able to attach to a running debug session, RTT Client could eat up to 100% CPU time of a single core of the host system. Fixed.
RTT Viewer
- Under some circumstances auto reconnect did not work. Fixed.
Version V6.60f (2020-01-20)
DLL
- QSPI Flash programming for NXP iMXRT1064 internal QSPI Flash (at address 0x7000 0000), fixed.
- Reset did not work properly for Gigadevice GD32V (RISC-V based) series devices. Peripherals were not reset correctly. Fixed.
GUI Server
- Linux: Restarting the GDB Server shortly after a previous instance of the GDB Server was closed could lead to the new instance to not start. Fixed.
Version V6.60e (2020-01-17)
Configurator
- J-Trace PRO probes were displayed as "J-Link (unknown)". Fixed.
DLL
- A deadlock could happen when a dialog created from the DLL was closed. Fixed.
- Cypress PSc4A S0 - S3: Connect and reset did not work under special circumstances. Fixed.
- In some occasions, restoring keyboard focus after displaying a dialog could lead to a deadlock. Fixed.
- Nordic Semi nRF5340 Application core: When the application core is protected and we wanted to connect to it, we accidentally would have connected to the network core. Fixed.
- NXP iMXRT500: Under special circumstances, reset did not work. Fixed.
- Option Byte data preparation for STM32G0x0 series devices, fixed.
- Silicon Labs EFR32xG22: Under special circumstances, reset did not work properly. Fixed.
- Some device names passed to the DLL by IAR EWARM were not recognized correctly (e.g. MCIMXRT1064). Fixed.
- Under certain circumstances Keil uVision crashed when using RTT Viewer in attach mode. Fixed.
- Windows 10: Flash programming progress dialog could flicker. Fixed.
GDB Server
- (macOS): Restarting the GDB Server shortly after a previous instance of the GDB Server was closed could lead to the new instance to not start. Fixed.
J-Flash SPI
- Passing 'connect' via the command line without any J-Links connected, could lead to J-Flash SPI opening two modal dialogs at once. Fixed.
J-Flash SPI CL
- Additional licenses added to a J-Link were not recognized. Fixed.
Version V6.60d (2020-01-09)
DLL
- (Windows): After a dialog from the DLL was closed, the original window did not regain keyboard focus. Fixed.
- Added flash programming support for Toshiba TMPM3HLFDUG, TMPM3HLFYUG, TMPM3HLFZUG.
- Linux: If a file was specified to be opened exclusively (e.g. SEGGER registry), this did not work correctly, so a 2nd process could modify the file at the same time. Fixed.
- Naming for Toshiba TMPM4G9F15FG, fixed.
- Reduced number of alloc calls when evaluating JLinkDevices.xml by factor 14,000 which results in a speed improvement of 10-20% during XML parse.
- RISC-V: JALR rd, rs1, SImm instruction was simulated incorrectly if rd == rs1. Fixed.
- Target RAM address was not correct for the MKL27Z32xxx4 devices. Fixed.
- The RWW section of ATSAMC2x/ATSAMD2x devices was not erased before programming. Fixed.
Firmware
- Flasher: Erase was not handled correctly for flash banks supporting automatic erase. Fixed.
J-Flash
- When passing the -exit parameter, a success messagebox could appear and keep J-Flash from self-exiting. Introduced with V6.60. Fixed.
J-Flash Lite
- The log was missing linebreaks in some cases. Fixed.
J-Flash SPI
- Under special circumstances (compare enabled and data in flash == data to be programmed), flash programming failed. Fixed.
J-Flash SPI CL
- Under some circumstances, downloading a file led to an endless loop. Fixed.
Remote Server
- (Windows): Starting a second instance of the J-Link Remote Server did not work correctly. Introduced with V6.60. Fixed.
Version V6.60c (2019-12-23)
DLL
- Linux: "DoNotShowAgain" did not work for J-Link dialog boxes. Fixed.
- macOS: "DoNotShowAgain" did not work for J-Link dialog boxes. Fixed.
RTT Viewer
- Under some circumstances auto reconnect did not work. Fixed.
Version V6.60b (2019-12-20)
Commander
- (macOS/Linux): Entering '?' as device name did not show device selection dialog. Fixed.
DLL
- Some messagebox titles were displayed incorrectly. Fixed.
- Some Renesas R7F0E01 series devices could not be selected in the DLL. Fixed.
- STM32F030F4: In Keil uVision, STM32F030F4Px was not correctly detected as an STM32F030F4 device. Fixed.
- STM32L0: Under some circumstances, wrong reset values were written to the option bytes section when unlocking the device. Fixed.
- Unified display of flash bank sizes for device selection dialogs across all J-Link utilities.
J-Flash Lite
- The QSPI flash programming for NXPs iMXRT1010 family (e.g. MIMXRT1011CAE4A) was not erased by default. Fixed.
RTT Client
- Linux: While not being able to attach to a running debug session, RTT Client could eat up to 100% CPU time of a single core of the host system. Fixed.
- macOS: While not being able to attach to a running debug session, RTT Client could eat up to 100% CPU time of a single core of the host system. Fixed.
Version V6.60a (2019-12-17)
DLL
- Flash programming dialog could crash. Introduced in V6.60. Fixed.
- Flash programming dialog could show "0.000s" for some steps even though they took time. Introduced in V6.60. Fixed.
J-Flash SPI
- IS25DLP flashes where successfully auto-detected although they are not supported due to a special required SPI command set. Corrected.
Version V6.60 (2019-12-16)
Commander
- "mem" command: Added additional space character after first 4 bytes in a row that are shown. Used as separator.
- Added "ASCIIView = <1/0>" command to be able to disable ASCII view column for "mem" command.
- Added ASCII view column for "mem" command.
- Cortex-A/R: When showing CPU registers (e.g. on "h" command) R11-R14 "current" could show incorrect values. Fixed.
DLL
- Added debug support for Dialog Semiconductor DA14531 series.
- Added debug support for Microchip MEC1501.
- Added debug support for Nulcei System based devices via cJTAG
- Added debug support for Nulcei System N1xx series (RV32 based)
- Added debug support for Nulcei System N2xx series (RV32 based)
- Added debug support for Nulcei System N3xx series (RV32 based)
- Added debug support for Nulcei System N6xx series (RV32 based)
- Added debug support for NXPx iMXRT1010 family (e.g. MIMXRT1011CAE4A).
- Added flash programming support for MIMXRT106A, MIMXRT106C, MIMXRT106F and MIMXRT106L devices.
- Added flash programming support for NXP MIMXRT1062DVJ6A (QSPI flash).
- Added Flash programming support for Renesas S1JA series devices option bytes.
- Added Flash programming support for ST STM32L4RxxG series devices.
- Added QSPI flash programming support for NXPs iMXRT1010 family (e.g. MIMXRT1011CAE4A).
- Added QSPI flash programming support via SPI interface for Microchip MEC1501.
- Added QSPI-Flash programing support for Microchip MEC1501
- ATSAM4SD: Under special circumstances (lock bits set) flash programming did not work. Fixed.
- Device selection dialog summed up sizes of all flash banks for devices which could lead to odd KB sizes being shown. Fixed.
- STM32G0x0/STM32G0x1: Some devices from these families were wrongly registered as locked. Fixed.
Firmware
- J-Link EDU Mini: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Link EDU/BASE/PLUS V10: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Link EDU/BASE/PLUS V11: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Link EDU/BASE/PLUS V9: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Link PRO V4: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Link ULTRA+ V4: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Link WiFi V1: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Link-OB-K22-SiFive: Drag and drop: Depending on hex file layout (if big gaps were in there), certain sectors were not erased prior to programming which resulted in verify errors. Fixed.
- J-Link-OB-K22-SiFive: Drag and drop: Depending on hex file layout, program errors were not reported properly to FAIL.txt. Fixed.
- J-Link-OB-K22-SiFive: Drag and drop: Depending on target state, "error while connecting to CPU" was thrown. Fixed.
- J-Trace PRO V1 Cortex-M: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Trace PRO V2 Cortex-M: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- J-Trace PRO V2 Cortex: RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
- RTT on big endian devices did not work properly (e.g. Renesas RX). Fixed.
GDB Server
- (Windows): Changed default font for Log to "Consolas".
- Changed icon for "Error" message boxes to error symbol.
- Main window is now visible in background during configuration of J-Link connection.
J-Link Package
- Windows: Removed "J-Link Remote Server (Tunneling Mode)" start menu entry as there is a GUI for it now.
Remote Server
- Added connection information.
- LAN mode: Command line version did not listen on port 19020 by default. Fixed.
- LAN mode: Socket were not closed correctly when a remote connection was closed. Fixed.
Remote Server CL
- Linux: Segfault could occur when checking for key input on STDIN. Fixed.
- Linux: When starting J-Link Remote Server as system service, main thread looped forever and used 100% CPU time of a core on the host. Fixed.
RTT Viewer
- (Windows): Changed default font from "Courier" to "Consolas".
SWO Viewer
- Drastically improved performance.
- Reduced CPU load.
- Settings were not saved/ loaded correctly. Fixed.
Trace
- Expanded exec commands for setting coresight base addresses, so unlock can be forced and AP index can be set.
Version V6.56d (2019-12-12)
Firmware
- J-Trace PRO V1 Cortex-M: Firmware from V6.56c could make J-Trace unresponsive. Fixed.
Version V6.56c (2019-12-11)
DLL
- Added support for new 256 KB Renesas R7F0E0 series devices.
- Device names for Toshiba TMPM4K series were incorrect. Fixed.
- Hilscher NetX90 Flash bank 2, programming and erase, fixed.
Firmware
- J-Link EDU Mini: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Link EDU/BASE/PLUS V10: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Link EDU/BASE/PLUS V11: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Link EDU/BASE/PLUS V9: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Link PRO V4: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Link ULTRA+ V4: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Link WiFi: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Link-OB-K22-CortexA: drag n drop: If mot/hex file contained Linux line endings (\n only), programming of target firmware could fail and J-Link OB could crash. Fixed.
- J-Link-OB-K22-CortexM: drag n drop: If mot/hex file contained Linux line endings (\n only), programming of target firmware could fail and J-Link OB could crash. Fixed.
- J-Link-OB-K22-NordicSemi: drag n drop: If mot/hex file contained Linux line endings (\n only), programming of target firmware could fail and J-Link OB could crash. Fixed.
- J-Link-OB-K22-SiFive: drag n drop: If mot/hex file contained Linux line endings (\n only), programming of target firmware could fail and J-Link OB could crash. Fixed.
- J-Link-OB-SAM3U128 V3: If mot/hex file contained Linux line endings (\n only), programming of target firmware could fail and J-Link OB could crash. Fixed.
- J-Link-OB-STM32F072-CortexM-128KB: If mot/hex file contained Linux line endings (\n only), programming of target firmware could fail and J-Link OB could crash. Fixed.
- J-Trace PRO V1 Cortex-M: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Trace PRO V2 Cortex-M: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
- J-Trace PRO V2 Cortex: Firmware could crash when programing flash on an ARM7/9 based device. Fixed.
Version V6.56b (2019-12-06)
DLL
- Atmel (Microchip) ATSAMRH71F20x: Under special circumstances, flash programming failed. Fixed.
- Flash and RAM size for Cypress CY8C5287xxxLP were incorrect. Corrected.
- Microchip DEC1702: Under special circumstances, flash programming could fail. Fixed.
- Renesas RZ-A2M series devices SPIBSC_OctaFlash variant, fixed.
- Return value of the CMSIS and OpenFlashLoader erase-sectors function was not correctly evaluated when using non-turbo mode. Fixed.
- RISC-V: Hardware breakpoints did not work properly on AndesTech cores (e.g. A25). Fixed.
- When using SystemView etc. in parallel to an IDE with an active debug session, the IDE could crash (because the J-Link SW crashed) on debug session end if SystemView was not stopped before. Fixed.
Version V6.56a (2019-11-25)
DLL
- Sessions with multiple processes connecting to the same J-Link (e.g. EmbeddedStudio + SystemView) could fail. Introduced with V6.56. Fixed.
- Some Renesas R7S9 devices (e.g. R7S910125_M3) where listed with an co-processor unit although they are actually single core devices. Fixed.
Version V6.56 (2019-11-22)
Configurator
- Added option to change number of enabled VCOM ports.
- Changing WiFi settings for J-Link WiFi did not work. Fixed.
- Replaced "Refresh rate" selection with checkbox.
DLL
- (macOS): Registry was written even if no settings etc. were changed. Fixed.
- (macOS): Segfault could occur if the J-Link lib was used by 2 processes at the same time and opened / closed very fast. Fixed.
- Added flash programming support for Nordic Semi nRF5340.
- Added flash programming support for ST STM32H742xx devices.
- Added flash programming support for ST STM32H742ZG and STM32H742ZI.
- Added flash programming support for ST STM32L4R5VG.
- Added QSPI Flash programming support for STM32MP15x series devices for both Cortex A7 CPUs
- Atmel (Microchip) ATSAMV7x: Under special circumstances, QSPI flash programming failed (timeout while programming). Fixed.
- Embedded Studio: Updated flash programming dialog for DAPLink / CMSIS-DAP.
- Flash programming for device CY8C4147xxx-Sxxx did not work correctly. Fixed.
- NXP MKE04Z64xxx4: Under special circumstances, flash programming failed (verification error). Fixed.
- Renesas RZ/A2M QSPI Flash programming unprotect routine, fixed.
- Under special circumstances, connecting to a specific device in a JTAG chain did not work (e.g. Renesas R7FS5D57C). Fixed.
- Under special circumstances, the flash programming progress dialog was not shown during flash programming. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V10: When using the pin override functionality for Pin17, the override was reverted by accident on the next JTAG transaction. Fixed.
- J-Link EDU/BASE/PLUS V11: When using the pin override functionality for Pin17, the override was reverted by accident on the next JTAG transaction. Fixed.
- J-Link WiFi V1: When using the pin override functionality for Pin17, the override was reverted by accident on the next JTAG transaction. Fixed.
- J-Link-OB-K22-SiFive: When used under Linux, depending on the distribution, it could happen that sometimes the baud rate of a VCOM port was not set correctly. Fixed.
- J-Link-OB-K22-SiFive: When used under Linux, depending on the distribution, it could happen that sometimes the J-Link OB did not enumerate. Fixed.
J-Flash
- In stand-alone-mode the blank check before erase did not work. Fixed.
- NetX90 programming could fail under special circumstances. Fixed.
J-Flash SPI
- Added Flash programming support for Gigadevice GD25Q256D and GD25LQ256D
J-Link Package
- Installer: Uninstalling via Control Panel did not work correctly. Fixed.
License Manager
- Added "Exit" option to menu bar.
- Moved "About" button into menu bar.
Manual
- UM08001: Chapter "J-Link GDB Server" Section "Command line options" Added information for command line option "-rtos" where to request the SDK for creating plug-ins.
- UM08001: Chapter "J-Link software and documentation package" Section "J-Link Commander (Command line tool)" Added note for command "VTREF".
- UM08003: Chapter "Settings": Section "Init steps": Added additional info about Verify/Write&Verify.
RTT
- Added API function SEGGER_RTT_GetAvailWriteSpace().
Version V6.54c (2019-11-07)
DLL
- Software breakpoints in flash did not work properly. Fixed.
- Some JLinkScript file functions were not handling return values correctly. Fixed.
Firmware
- J-Link-OB-K22-NordicSemi: If VCOM was enabled and used and then the config area of J-Link was changed (e.g. when issuing a MSDDiable command in J-Link Commander), FW could crash. Fixed.
RTT
- ASM version was disabled by default for IAR compiler. Fixed.
- Default config threw compiler errors when using IAR compiler. Fixed.
Version V6.54b (2019-11-05)
DLL
- Embedded Studio: When using DAPLink / CMSIS-DAP support, some Gigadevice GD-Links on new boards were not found. Fixed.
Version V6.54a (2019-10-31)
Control Panel
- Log tab could cause severe CPU and RAM load if a bigger log was shown (~200 lines). Fixed.
DLL
- Added option memory programming support Renesas SOTB ASSP devices (R7F0E010D2CFP, R7F0E011D2CFP, R7F0E014D2CFB, R7F0E015D2CFB, R7F0E016D2DBN, R7F0E017D2DBN).
- Embedded Studio: When using DAPLink / CMSIS-DAP support, flash download could fail on Cortex-M based targets where a watchdog was running after reset (e.g. Toshiba TMPM3HQFDFG series). Fixed.
- J-Link WiFi could report communication breakdowns even if the communication itself was fine. Fixed.
- Log tab could cause severe CPU and RAM load if a bigger log was shown (~200 lines). Fixed.
DLL Updater
- Added "Ctrl+A" as shortcut to select all DLLs.
- Clicking checkboxes did not change the selected row. Fixed.
Firmware
- Flasher PRO/ARM/PORTABLE PLUS: SPIFI-Algorithm did not work under specific circumstances. Fixed.
- J-Link WiFi V1: J-Link could hang when using WiFi and RTT. Fixed.
- J-Trace PRO V2 Cortex-M: SPI interface was reported as not supported. Fixed.
- J-Trace PRO V2 Cortex: SPI interface was reported as not supported. Fixed.
J-Link Package
- Installer: Start menu entries and desktop shortcuts were not deleted correctly on "update existing" installation. Fixed.
Version V6.54 (2019-10-28)
Configurator
- "Close" button did not work. Fixed.
- Added support for J-Link WiFi
- If USB J-Link was disconnected during list update, emulator selection dialog could pop up by accident. Fixed.
Control Panel
- Added functionality for "SetCodeBP" to breakpoints tab
- Added functionality for writing CPU registers to CPU register tab.
- Sometimes, live updates did not work after reloading page in browser (F5). Fixed.
DLL
- Added Cortex-M4 debug and flash programming support for STM32H745xx, STM32H747xx, STM32H755xx and STM32H757xx series devices.
- Added debug and flash programming support for Renesas R7FA4xx and R7FA6xx series devices.
- Added debug support for both Cortex-A7 CPUs on STM32MP157 series devices.
- Added flash programming support for Cypress PSoC6A-512K series devices.
- Added flash programming support for Nordic Semi nRF52833.
- Added flash programming support for Toshiba TMPM4K (group2) devices.
- Added flash programming support for Toshiba TMPM4KL devices.
- Added missing device names for Renesas RZ/T1 series devices.
- Added QSPI Flash programming support for Microchip ATSAMD5x and ATSAME5x series devices.
- added support for SPI Flash Gigadevice GD25LQ256D to SPIFI-Lib for indirect flash programming.
- added support for SPI Flash Winbond W25Q256JV to SPIFI-Lib for indirect flash programming.
- Changed log file timestamps to [us] accuracy
- Control Panel <RTT> tab did not work correctly. Fixed.
- Control Panel <Settings> tab checkbox for "Allow caching of flash contents" did not work correctly. Fixed.
- Dialog Semiconductor DA1469x family: Under special circumstances, single stepping in QSPI based applications did not work. Fixed.
- For STM32F413 and STM32F423 devices, unlock was not working correctly. Fixed.
- If trace was running only for a very short amount of time (e.g. single stepping), it could happen that "no trace data received" was reported, even though trace data was received correctly. Fixed.
- NXP iMXRT500: Reset and connect did not work under special circumstances. Fixed.
- Under special circumstances, flash programming did not work for Toshiba TMPM4G devices. Fixed.
- Under special circumstances, flash programming did not work for Toshiba TMPM4K (group1) devices. Fixed.
Firmware
- J-Link EDU Mini: cJTAG: Improved protocol stability for buggy target devices that do not keep the line state after rising edge of TCKC
- J-Link EDU/BASE/PLUS V10: cJTAG: Improved protocol stability for buggy target devices that do not keep the line state after rising edge of TCKC
- J-Link EDU/BASE/PLUS V10: When using cJTAG, J-Link FW sometimes crashed. Fixed.
- J-Link PRO V4: Added support for up to 50 MHz for SPI target interface (12 MHz before)
- J-Link PRO V4: cJTAG: Improved protocol stability for buggy target devices that do not keep the line state after rising edge of TCKC
- J-Link ULTRA+ V4: Added support for up to 50 MHz for SPI target interface (12 MHz before)
- J-Link ULTRA+ V4: cJTAG: Improved protocol stability for buggy target devices that do not keep the line state after rising edge of TCKC
GDB Server
- Made target device name field read-only.
J-Flash SPI
- Added Flash programming support for Gigadevice GD25Q256D and GD25LQ256D
- Added Flash programming support for Winbond W25Q256JV.
- Added option to enable programming of blank data.
- Added SPI Flash programming support for GigaDevice GD25Q128ESIG SPI Flash.
- If "compare" was disabled in the production settings, "Erase sectors if not blank" did not work properly. Fixed.
- If "erase chip" was configured, time was wasted because certain blank checks were done before. Fixed.
- Improved speed if "erase sectors if not blank" was selected (default).
Manual
- UM08001: Added J-Link WiFi setup
- UM08001: Chapter "RTT" *Section "Example code" updated.
- UM08001: Chapter "Semihosting", section "Debugger Support": Took off Keil MDK-ARM of the list of supported IDEs as MDK does not support semihosting.
Remote Server
- Added option for 'encrypted data transfer'.
- Only 1st encrypted session did work without restarting the Remote Server. Fixed.
RTT Viewer
- "Select All" on an empty log did not work as expected. Fixed.
- Displaying TABs (\t) did not work. Fixed.
- Long lines could lead to a crash. Fixed.
Version V6.52e (2019-10-16)
Firmware
- Flasher ARM/PPC/RX/Portable PLUS: Flasher reported errors in a correct data files during stand-alone programming. Introduced in V6.52c. Fixed.
Manual
- UM08001: Chapter "J-Link software and documentation package" - *Section "J-Link Remote Server": Added command "-TunnelEncrypt"; Added subsection "Encrypted connection".
Version V6.52d (2019-10-15)
DLL
- Detection of memory mapping at address 0x0 for STM32F0xx series devices, fixed.
- SiLabs EFR32xG21 series: Erasing the UDP-flash did not work correctly. Fixed.
Firmware
- Flasher: Connect under reset did not work for STM32L0 series devices. Fixed.
- J-Link-OB-S124: Enabled LVD1 in firmware to detect CPU voltage drops properly and avoid undefined behavior on power loss.
Version V6.52c (2019-10-11)
DLL
- If operations on XML files failed, memory leaks could occur. Fixed.
- Linux: Internal memory leak when using simulated windows registry to remember settings etc. cross-session. Fixed.
- Linux: Some resources were not freed when unloading the shared library via dlclose(). Fixed.
- macOS: Internal memory leak when using simulated windows registry to remember settings etc. cross-session. Fixed.
- macOS: Some resources were not freed when unloading the shared library via dlclose(). Fixed.
- Named mutex for IPC locking was not closed/freed correctly on DLL close. Caused a handle leak. Fixed.
- Renesas RX via JTAG: Setting a reset pulse length via command string "SetResetPulseLen = xxx" was not taken into consideration for reset pulses during connect phase. Fixed.
- SiFive E31ARTY QSPI flash on ARTY-100T board could not be programmed. Fixed. (Only the flash on the 35T worked)
Firmware
- Flasher: ST STM32G0xx series devices did not work in stand-alone mode. Fixed.
- J-Link EDU Mini: RISC-V: Fixed fast mode for system bus access (not waiting for ready bit). Taken out in V6.52b
- J-Link EDU Mini: RISC-V: For RV64 based devices, for system bus accesses <ADDR0> was written before <ADDR1> causing a read from an incorrect address for the first item. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: Fixed fast mode for system bus access (not waiting for ready bit). Taken out in V6.52b
- J-Link EDU/BASE/PLUS V10: RISC-V: For RV64 based devices, for system bus accesses <ADDR0> was written before <ADDR1> causing a read from an incorrect address for the first item. Fixed.
- J-Link PRO V4: RISC-V: Fixed fast mode for system bus access (not waiting for ready bit). Taken out in V6.52b
- J-Link PRO V4: RISC-V: For RV64 based devices, for system bus accesses <ADDR0> was written before <ADDR1> causing a read from an incorrect address for the first item. Fixed.
- J-Link ULTRA+ V4: RISC-V: Fixed fast mode for system bus access (not waiting for ready bit). Taken out in V6.52b
- J-Link ULTRA+ V4: RISC-V: For RV64 based devices, for system bus accesses <ADDR0> was written before <ADDR1> causing a read from an incorrect address for the first item. Fixed.
J-Flash
- In some occasions, the file dialog did not appear upon trying to open or save a file. Fixed.
J-Link Package
- Installer: Under special circumstances, the J-Link installer would not run successfully when executed from desktop. Fixed.
- Installer: When updating the J-Link Software and Documentation pack, uninstall.exe was deleted after reboot. Fixed.
RTT
- SEGGER_RTT_Syscalls_IAR.c threw a warning for IAR EWARM V8.x and IAR EWRX. Fixed.
Version V6.52b (2019-10-08)
DLL
- Added flash programming support for Renesas R7FA2A1.
- Added flash programming support for Renesas R7FA4M1.
- Added flash programming support for Renesas R7FA6M1.
- Added flash programming support for Renesas R7FA6M2.
- Added flash programming support for Renesas R7FA6M3.
- Added QSPI flash programming support for STM32H745I Discovery board.
- Added unlocking support concerning read and write protection for STM32G0xx series devices.
- JLinkScript file for i.MX8M Nano, fixed.
- Open Flashloader: Verify failed in case of the flashloader provided a native Verify() function. Fixed.
Firmware
- J-Link EDU Mini: RISC-V: Removed fast mode for system bus access (not waiting for ready bit) for now, as it created problems on some RV32 targets returning invalid data but no error (e.g. when using RTT)
- J-Link EDU/BASE/PLUS V10: RISC-V: Removed fast mode for system bus access (not waiting for ready bit) for now, as it created problems on some RV32 targets returning invalid data but no error (e.g. when using RTT)
- J-Link PRO V4: RISC-V: Removed fast mode for system bus access (not waiting for ready bit) for now, as it created problems on some RV32 targets returning invalid data but no error (e.g. when using RTT)
- J-Link ULTRA+ V4: RISC-V: Removed fast mode for system bus access (not waiting for ready bit) for now, as it created problems on some RV32 targets returning invalid data but no error (e.g. when using RTT)
J-Link Package
- Installer: (macOS): J-Link software package installer is now shipped notarized.
- Installer: Windows: Checkbox "create desktop shortcuts" was checked by default (not backward compatible to older installers). Fixed.
- Installer: Windows: When updating the installation for the active user only (C:\Users\...), installer accessed C:\Program Files (x86)\ for certain steps by accident. Fixed.
RTT Viewer
- Added <Select All> and <Copy> context menu options and shortcuts to terminal.
- Log lines were slightly cut off sometimes. Fixed.
- Reduced max. CPU workload during terminal logging.
- Reduced max. CPU workload.
- Selecting and copying text did not work correctly. Fixed.
- Terminals would flicker when text was appended. Fixed.
Version V6.52a (2002-10-19)
DLL
- Added flash programming support for STM32G030xx series devices.
- If connection to J-Link failed, the error message "Failed to open DLL" was output instead of "failed to connect to J-Link". Introduced in V6.52. Fixed.
- NXP LPC55Sxx: Connect did not work. Introduced in V6.52. Fixed.
- NXP LPC55Sxx: Flash programming did not work on some early silicon revisions. Fixed.
GDB Server
- For big endian targets, reading all registers resulted in registers being shown in wrong byte order in debugger. Fixed.
Version V6.52 (2019-09-27)
Configurator
- For emulators that support IP but were connected via USB, IP configuration was not shown. Introduced in V6.50. Fixed.
Control Panel
- Some settings were not correctly saved in SettingsFile. Fixed.
DLL
- (Improved): RISC-V: Moved DSCR into register group 0 so it is read by default. Saves a USB transactions for every RAMCode start during flash programming.
- (Improved): RISC-V: Moved DSCR into register group 0 so it is read by default. Saves a USB transactions for every RAMCode start during flash programming.
- Added flash programming support for Goodix GMF03 series devices.
- Added flash programming support for Goodix GMF03 series devices.
- Added flash programming support for Infineons TLE9850 and TLE9852 device family.
- Added Flash programming support for Maxim MAX32520 series device.
- Added Flash programming support for Maxim MAX32520 series device.
- Added flash programming support for second QSPI flash bank of NXP K80/K82 series devices.
- Added flash programming support for second QSPI flash bank of NXP K80/K82 series devices.
- Added flash programming support for Silicon Labs EFR32BG22CxxxF352 and EFR32BG22CxxxF512 devices.
- Added flash programming support for Silicon Labs EFR32BG22CxxxF352 and EFR32BG22CxxxF512 devices.
- Added flash programming support for Silicon Labs EFR32FG22CxxxF256 and EFR32FG22CxxxF512 devices.
- Added flash programming support for Silicon Labs EFR32FG22CxxxF256 and EFR32FG22CxxxF512 devices.
- Added flash programming support for Silicon Labs EFR32MG22CxxxF352 and EFR32MG22CxxxF512 devices.
- Added flash programming support for Silicon Labs EFR32MG22CxxxF352 and EFR32MG22CxxxF512 devices.
- Added flash programming support for ST STM32L081CB.
- Added flash programming support for ST STM32L081CB.
- Added flash programming support of RWW-Flash for Atmel (Microchip) SAML21xxx family.
- Added NXP "LPC55S28" as device name.
- Added NXP "LPC55S28" as device name.
- Added QSPI Flash programming support for ST STM32H743xx series devices.
- Added QSPI Flash programming support for ST STM32H750xx series devices.
- Added QSPI Flash programming support for ST STM32H753xx series devices.
- Added SPI Flash programming support for AndesTech A25 core (RV32, RISC-V based).
- Added SPI Flash programming support for AndesTech A25 core (RV32, RISC-V based).
- Added SPIFI Flash programming support for ST STM32MP15x Bank 1, 2 and Dual-flash mode.
- Added SPIFI Flash programming support for ST STM32MP15x Bank 1, 2 and Dual-flash mode.
- Added support for complete NXP LPC55Sxx device series.
- Added support for complete NXP LPC55Sxx device series.
- added support for SPI Flash Spansion(Macronix) MX25U6435F to SPIFI-Lib for indirect flash programming.
- added support for SPI Flash Spansion(Macronix) MX25U6435F to SPIFI-Lib for indirect flash programming.
- Added support for turbo mode to open flash loaders for Cortex-M targets.
- Added support for turbo mode to open flash loaders for Cortex-M targets.
- Added tunnel server address to log message in case of failed connection.
- Added tunnel server address to log message in case of failed connection.
- Corrected Arm Coresight Addresses for Nordic nRF91 device series to enable tracing when initialized from application.
- Corrected Arm Coresight Addresses for Nordic nRF91 device series to enable tracing when initialized from application.
- Flash programming algorithm for Gigadevice GD32F403 series devices, fixed.
- Improved Flash programming speed for Gigadevice GD32VF103 series devices.
- Incorrect flash size reported for MK10DN512xxx10. Fixed.
- Incorrect flash size reported for MK10DN512xxx10. Fixed.
- NXP LPC55S6x/LPC55S2x/LPC552x: Under special circumstances, flash programming did not work. Fixed.
- NXP LPC55S6x/LPC55S2x/LPC552x: Under special circumstances, flash programming did not work. Fixed.
- On Windows XP, connecting to a J-Link via USB failed. Introduced in V6.50. Fixed.
- On Windows XP, connecting to a J-Link via USB failed. Introduced in V6.50. Fixed.
- Renesas RX65N: Specified option byte size was too small (112 bytes instead of 128 bytes). Fixed.
- Watchpoint support for ARMv8-M Architecture devices(Cortex-M23 and Cortex-M33).
- Windows: Improved performance for internal thread locking
Firmware
- Flasher ARM/PRO/RX: added remove read only flag for file in the _SECURE folder before overwriting file content.
- Flasher Portable PLUS: "displayname" was overwritten by datafile name if the name was longer than the first line. Fixed.
- Flasher Portable PLUS: Progress bar did not behave correctly in Universal Flashloader mode. Fixed.
- Flasher PRO/ARM: added new ASCII commands "HasSecureArea" and "SecureArea Create/Remove".
- J-Link EDU Mini: RISC-V: Improved download speed for Gigadevice GD32VF103 series devices (RV32 based)
- J-Link EDU Mini: RISC-V: Improved download speed for Gigadevice GD32VF103 series devices (RV32 based)
- J-Link EDU/BASE/PLUS V10: RISC-V: Improved download speed for Gigadevice GD32VF103 series devices (RV32 based)
- J-Link EDU/BASE/PLUS V10: RISC-V: Improved download speed for Gigadevice GD32VF103 series devices (RV32 based)
- J-Link PRO V4: RISC-V: Improved download speed for Gigadevice GD32VF103 series devices (RV32 based)
- J-Link PRO V4: RISC-V: Improved download speed for Gigadevice GD32VF103 series devices (RV32 based)
- J-Link ULTRA+ V4: RISC-V: Improved download speed for Gigadevice GD32VF103 series devices (RV32 based)
- J-Link ULTRA+ V4: RISC-V: Improved download speed for Gigadevice GD32VF103 series devices (RV32 based)
- J-Link-OB-K22-SiFive: Windows: Under very special circumstances, when using the VCOM functionality with the python serial lib (pyserial) it could happen that Rx data was lost and not transmitted to the PC. Fixed.
GDB Server
- When using semihosting mode 2 (system calls forwarded to be handled GDB, not GDB Server) it could happen that a SYS_WRITE placed an error response to R0 of the target application, even if everything worked fine. Fixed.
- When using semihosting mode 2 (system calls forwarded to be handled GDB, not GDB Server) it could happen that a SYS_WRITE placed an error response to R0 of the target application, even if everything worked fine. Fixed.
J-Flash
- Added flash programming support for Infineons TLE9850 and TLE9852 device family.
- Added support for the file extension *.mcs (Intel MCS-86 hex).
- Added support for the file extension *.mcs (Intel MCS-86 hex).
- Added support for turbo mode to open flash loaders for Cortex-M targets.
- Added support for turbo mode to open flash loaders for Cortex-M targets.
- Improved flash programming speed for open flash loaders by using more work RAM.
- Improved flash programming speed for open flash loaders by using more work RAM.
- When opening the project settings of a new project, a error related to the serial number file was showen. Fixed.
J-Flash SPI
- Added flash programming support for Adesto AT25PE16 SPI Flash.
- Added flash programming support for Adesto AT25PE20 SPI Flash.
- Added flash programming support for Adesto AT25PE32 SPI Flash.
- Added flash programming support for Adesto AT25PE40 SPI Flash.
- Added flash programming support for Adesto AT25PE80 SPI Flash.
- Added flash programming support for Adesto AT25QF128A SPI Flash.
- Added flash programming support for Adesto AT25QL128A SPI Flash.
- Added flash programming support for Adesto AT25QL641 SPI Flash.
- Added flash programming support for Adesto AT45DB021E SPI Flash.
- Added flash programming support for Adesto AT45DB041E SPI Flash.
- Added flash programming support for Adesto AT45DB081E SPI Flash.
- Added flash programming support for Adesto AT45DB161E SPI Flash.
- Added flash programming support for Adesto AT45DB321E SPI Flash.
- Added flash programming support for Adesto AT45DB641E SPI Flash.
- Added flash programming support for Adesto AT45DQ321 SPI Flash.
- Added flash programming support for ISSI IS25WP256D SPI Flash.
- Added flash programming support for ISSI IS25WP512M SPI Flash.
- Added flash programming support for Macronix MX25R1635F SPI Flash.
- Added flash programming support for Micron MT25QU512ABB SPI Flash.
- Added flash programming support for Winbond W25M512JVFIQ SPI Flash.
- Added flash programming support for Winbond W25Q16JV SPI Flash.
- Added flash programming support for Winbond W25Q16WS SPI Flash.
- Added support for the file extension *.mcs (Intel MCS-86 hex).
- Added support for the file extension *.mcs (Intel MCS-86 hex).
- corrected number of protection bits for Spansion S25FL064K / Winbond W25Q064F
- corrected number of protection bits for Spansion S25FL064K / Winbond W25Q064F
- Fixed flash size of Micron M25PE40 SPI Flash.
- SPI devices: added MX25U6435F device, corrected MX25L6439E
- SPI devices: added MX25U6435F device, corrected MX25L6439E
J-Link Package
- Installer: If the installer is started as administrator, it does not ask second time for elevation anymore.
- Installer: Pages were shown wrong under Windows text scalings different to 100%. Fixed.
- Installer: Pages were shown wrong under Windows text scalings different to 100%. Fixed.
J-Mem
- Crashed when writing data to the device via hex window. Fixed.
JTAG Load
- Added support for command line "-LogFile <Path>"
- Added support for command line "-LogFile <Path>"
- If SVF file did end with a comment but not a final newline following that comment, JTAGLoad could crash. Fixed.
- If SVF file did end with a comment but not a final newline following that comment, JTAGLoad could crash. Fixed.
Manual
- UM08001: Chapter "J-Link software and documentation package" Section "J-Link Remote Server" Created examples for the syntax of the connect-string
- UM08001: Chapter "J-Link software and documentation package" Section "J-Link Remote Server" Updated screenshots
Remote Server
- On some devices (e.g. ARM7) reading memory did not work when using the J-Link Remote Server. Fixed.
- On some devices (e.g. ARM7) reading memory did not work when using the J-Link Remote Server. Fixed.
RTT Viewer
- Copying text from a terminal lead to unwanted characters in the clipboard in place of line breaks. Fixed.
- RTT channel description showed incorrect names for unconfigured buffers. Fixed.
- RTT channel description showed incorrect names for unconfigured buffers. Fixed.
Version V6.50b (2019-09-06)
Configurator
- For emulators that support IP but were connected via USB, IP configuration was not shown. Introduced in V6.50. Fixed.
Control Panel
- Some settings were not correctly saved in SettingsFile. Fixed.
DLL
- Flash programming algorithm for Gigadevice GD32F403 series devices, fixed.
- Renesas RX65N: Specified option byte size was too small (112 bytes instead of 128 bytes). Fixed.
J-Mem
- Crashed when writing data to the device via hex window. Fixed.
RTT Viewer
- Copying text from a terminal lead to unwanted characters in the clipboard in place of line breaks. Fixed.
Version V6.50a (2019-08-26)
DLL
- Improved Flash programming speed for Gigadevice GD32VF103 series devices.
Firmware
- J-Link-OB-K22-SiFive: Windows: Under very special circumstances, when using the VCOM functionality with the python serial lib (pyserial) it could happen that Rx data was lost and not transmitted to the PC. Fixed.
J-Link Package
- Installer: If the installer is started as administrator, it does not ask second time for elevation anymore.
Version V6.50 (2019-08-16)
Commander
- Added command "SetTimeoutCmd"
- Added command "stepover"
- Commands "ReadCSR" and "WriteCSR" did not output an error when trying to access the CSRs while the core is running. Fixed.
- JTAG: Under special circumstances a TAP could be reported as "unknown device" even though the TAPId was known and found in the internal table. Fixed.
Configurator
- MacOS/ Linux: Added J-Link Configurator for MacOS and Linux.#
- Windows: Updated J-Link Configurator GUI.
Control Panel
- Adjusted edit fields as some were too small / big
- Opening the CPU register tab when having a RISC-V based MCU connected could crash the web browser. Fixed.
- Settings and log tab did not remember settings properly. Fixed.
- The CPU register tab now shows if a target connection needs to established or if the target core needs to be halted.
DLL
- Added flash programming support for Atmel ATSAMRH71F20x series devices.
- Added Flash programming support for Gigadevice GD32VF103 series devices.
- Added flash programming support for NXP K32L3A series devices.
- Added some EFM32GG device name aliases for IAR.
- Added support for AndesTech A25 core (RV32, RISC-V based)
- Command string "JLinkDevicesXMLPath=<Path>" did not work properly when passing a path without a terminating '\' character. Fixed.
- Fixed remapping of RAM or Flash at Address 0x0000 0000 for ST STM32F042xx series devices.
- Gigadevice GD32VF103 (RISC-V based) series devices were not detected properly. Fixed.
- J-Link nicknames are now shown in selection dialog that pops up if multiple J-Links are connected
- JTAG: Added Gigadevice RISC-V TAP ID to the list of known TAP IDs.
- Mac: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the JLinkDevices.xml file was not found. Fixed.
- Microchip SST39VF1601C: CFI flash programming did not work due to an invalid CFI information table reported by the device. Fixed.
- RISC-V: Added auto-recovery with connect under reset in case target device is unresponsive to debug commands. (Saves closing and restarting a debug session in certain cases)
- RISC-V: Connecting to Gigadevice GD32VF103 (RISC-V) series devices could throw a JTAG error. Fixed.
- RISC-V: Flash programming could throw errors that certain optional CSRs could not be saved/restored if they were not implemented on the connected core. Fixed.
- RISC-V: Improved output for system bus support. Now also outputting information about what access sizes are supported by system bus.
- STM32WB55 reset did not work properly. Fixed.
- When using command string "JLinkDevicesXMLPath=<Path>", <Path>\JLinkDevices.xml was sometimes not found properly. Fixed.
- XML tag "-" was not supported correctly. Fixed.
Firmware
- J-Link EDU Mini: RISC-V: JTAG: When selecting another scan chain between J-Link commands (e.g. via "i" command in J-Link Commander), following J-Link operations returned with an error. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: JTAG: When selecting another scan chain between J-Link commands (e.g. via "i" command in J-Link Commander), following J-Link operations returned with an error. Fixed.
- J-Link PRO V4: RISC-V: JTAG: When selecting another scan chain between J-Link commands (e.g. via "i" command in J-Link Commander), following J-Link operations returned with an error. Fixed.
- J-Link ULTRA+ V4: RISC-V: JTAG: When selecting another scan chain between J-Link commands (e.g. via "i" command in J-Link Commander), following J-Link operations returned with an error. Fixed.
GDB Server
- Added RTOSPlugin for ChibiOS.
- Beginning of text was cut off in GUI when it did not fit into line. Fixed.
- Command line parameter "-JLinkDevicesXMLPath <Path>" did not work properly. Fixed.
- RISC-V: Added CSR registers for RV32 based RISC-V designs.
- Windows: GUI element borders were not shown in the Windows Classic Theme. Fixed.
J-Flash
- Added command line option "jlinkdevicesxmlpath".
J-Link Package
- Added new template J-Link script file: Template_ExcludeIllegalRegions.JLinkScript. More info: https://wiki.segger.com/J-Link_script_files#J-Link_script_file_samples
- Installer: Added command line options to installer (https://wiki.segger.com/J-Link_Installer#Command_line_parameters)
- Installer: Added option to installer to install for current user only (no admin rights required)
Manual
- UM08001: Chapter "J-Link software and documentation package" Section "J-Link Commander (Command line tool) Added command "readcsr"
- UM08001: Chapter "J-Link software and documentation package" Section "J-Link Commander (Command line tool) Added command "SetTimeoutCmd"
- UM08001: Chapter "J-Link software and documentation package" Section "J-Link Commander (Command line tool) Added command "stepover"
- UM08001: Chapter "J-Link software and documentation package" Section "J-Link Commander (Command line tool) Added command "writecsr"
- UM08001: GDB Server command line parameter "-JLinkDevicesXMLPath <Path>" was not described properly. Fixed.
- UM08003: Chapter "Command Line Interface" Section "Programming multiple targets in parallel": Updated batch scripts.
Remote Server
- Field to enter password was not displayed correctly. Fixed.
Version V6.48b (2019-08-02)
Commander
- Added commands "ReadCSR" and "WriteCSR"
- Command "setWP": Added "ANY" to the allowed specifiers for <accesstype> and <size>
DLL
- Cortex-A/R: When an SVC vector catch triggered, it could happen that PC got stuck at SWI vector when hitting F5 (Go). Fixed.
- Linux: At least under Debian, J-Link VCOM devices (/dev/ttyACMxxx) were enumerated to be accessed by root only. Normal user accounts could not open them for R/W Fixed.
- No target connection could be established in case of an invalid J-Link script file has been specified in the J-Link settings file. Fixed.
- Renesas RX130 / RX111: OFS1 could not be modified. Fixed.
- RISC-V: Added support for data breakpoints (watchpoints). For specifics and potential limitations, see: https://wiki.segger.com/J-Link:RISC-V
- Script File: ReconnectTarget() was not executed, even if specified in the J-Link Script file. Fixed.
- Some Infineon XMC1404 device names where not accepted by the J-Link DLL. Fixed.
- Unlock did not work for PSoC4100/PSoC4200. Fixed.
Version V6.48a (2019-07-29)
Commander
- Added commands "WebUSBDisable" and "WebUSBEnable".
DLL
- No target connection could be established in case of an invalid J-Link script file has been specified in the J-Link settings file. Fixed.
- Under special circumstances, flash programming of dual SPI QSPI flash configurations did not work (e.g. Renesas RZA1H). Fixed.
Firmware
- J-Link-OB-K22-SiFive: Added support for WebUSB. More info: https://wiki.segger.com/J-Link-OB-K22-SiFive#WebUSB_support
- J-Link-OB-K22-SiFive: MSD drag & drop programming did not issue a TAP reset to the device first (to be on the safe side). Fixed.
- J-Link-OB-K22-SiFive: Under special circumstances, MSD drag & drop programming could fail with FAIL.TXT: "Connect error" even though the connection was fine. Fixed.
- J-Link-OB-K22-SiFive: When a DMI access timed out and was aborted by J-Link, following DMI accesses could fail as well because DMI scan chain was not re-selected properly. Fixed.
J-Mem
- MacOS/ Linux: Added J-Mem for MacOS and Linux.
Version V6.48 (2019-07-26)
CCS Plugin
- Added a new option which allows configuring a J-Link script file (project dependent).
Commander
- "erase" did not use the EraseChip command to erase the entire flash but the EraseSector command. Changed.
- "erase" did not use the EraseChip command to erase the entire flash but the EraseSector command. Changed.
- RISC-V: Added <SWD> to the list of suggested/available interfaces
DLL
- STM32WB55 added support for Co-Processor Wireless stack upgrade.
- Added flash programming support for AmbiqMicro's AMA2B1KK (Apollo2 Blue; AMA2BEVB).
- Added flash programming support for AmbiqMicro's AMA2B1KK (Apollo2 Blue; AMA2BEVB).
- Added Flash programming support for Cypress Traveo2 CYT2B and CYT4B series devices.
- Added Flash programming support for Cypress Traveo2 CYT2B and CYT4B series devices.
- Added Flash programming support for CYT2B9 series devices.
- Added Flash programming support for CYT2B9 series devices.
- Added flash programming support for Panasonic MN1M7BFxx and MN1M7AFxx series devices.
- Added flash programming support for Panasonic MN1M7BFxx and MN1M7AFxx series devices.
- Added flash programming support for ST STM32G47xx series devices.
- Added flash programming support for ST STM32G4xx series devices.
- Added flash programming support for ST STM32G4xx series devices.
- Added flash programming support for STM32H745, STM32H755, STM32H747 and STM32H757 series devices.
- Added flash programming support for STM32H745, STM32H755, STM32H747 and STM32H757 series devices.
- Added flash programming support for WIZnet W7500 series device.
- Added flash programming support for WIZnet W7500 series device.
- Added native trace buffer support for Renesas RZ/A2M series.
- Added OTP flash programming support for TI's RM42L device family.
- Added OTP flash programming support for TI's RM44L device family.
- Added OTP flash programming support for TI's RM46L device family.
- Added OTP flash programming support for TI's RM48L device family.
- Added support for command string "CORESIGHT_SetCoreBaseAddr"
- Added support for Cypress CYT2B series devices Cortex-M4.
- Added support for Cypress CYT4B series devices Cortex-M7_0 and Cortex-M7_1.
- Added support for Cypress MB9DF / MB9EF series (FCR4) devices.
- Added support for RISC-V behind a DAP as setup.
- Added support for RISC-V via SWD for RISC-V behind a DAP setups.
- Added support for SPI FLash Adesto ATXP128/ATXP128R to SPIFI-Lib for indirect flash programming.
- Added support for SPI FLash Adesto ATXP128/ATXP128R to SPIFI-Lib for indirect flash programming.
- Added unlocking support for Microchip SAML10 series devices.
- Added unlocking support for Microchip SAML10 series devices.
- Analog Devices ADUCM355: Reset could not be overwritten using a J-Link script file. Fixed.
- Changed an ambiguous J-Link report output.
- Cypress PSoC4 family: Under special circumstances, unlock did not work. Fixed.
- Cypress PSoC4 family: Under special circumstances, unlock did not work. Fixed.
- Flash programming sector sizes corrected for Traveo2 CYT4B series devices.
- Flash programming sector sizes corrected for Traveo2 CYT4B series devices.
- For the MPC560xx devices, the ECC SRAM was not initialized after connect. Fixed.
- Hilscher NetX90 flash bank size, fixed.
- Infineon TLE98xx: Some J-Link LITEs could not connect establish a successful target connection due to missing firmware functionality. Fixed.
- JTAG: When only having 1 TAP in the JTAG chain and its <IRLen> matches the one for the configured CPU core but the TAP-ID was unknown, connect did not work. Fixed.
- Linux: Delayed / slowed execution of certain API functions when using J-Link via USB (e.g. on Close()). Introduced in V6.46. Fixed.
- Linux: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the JLinkDevices.xml file was not found. Fixed.
- Linux: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the libjlink* shared library was not found. Fixed.
- macOS: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the libjlink* shared library was not found. Fixed.
- Microchip J-32 OEM probes could not support legacy Atmel devices. Fixed.
- Minor bug in flash programming algorithm for STM32G0xx series devices, fixed.
- NXP KW34: Added flash programming support for the program and data flash area.
- NXP KW34: Added flash programming support for the program and data flash area.
- NXP KW35 / KW36 / KW38 / KW39: Added flash programming support for the data flash area.
- NXP KW35 / KW36 / KW38 / KW39: Added flash programming support for the data flash area.
- NXP KW38: Corrected device names showen in the device selection dialog.
- NXP KW38: Corrected device names showen in the device selection dialog.
- NXP KW3x family: Improved flash programming speed significantly.
- NXP KW3x family: Improved flash programming speed significantly.
- NXP LPC18xx / LPC43xx: After QSPI flash programming, the QSPI flash memory was no longer memory mapped accessible. Introduced in V6.41. Fixed.
- Open flash loaders for RISC-V did not work properly anymore (introduced with V6.46). Fixed.
- Programming issue while another application is already running on Hilscher NetX90, fixed.
- Qorvo GP570 / UE878 / QPG6 family: Flash programming did not work in recent silicon revisions. Fixed.
- Qorvo GPxxx: Under special circumstances, flash programming did not work. Fixed.
- QSPI flash programming: When the QE bit was set before flash programming, it has been cleared but not restored by the DLL. Introduced in V6.46h. Fixed.
- RAM size of ST STM32F412 series devices, fixed.
- Re-attaching to existing debug session after connecting and disconnecting once via TELNET (e.g. used by RTT Client and RTT Viewer) did not work properly. Fixed.
- Renesas R5F51306 (RX130) devices were not detected by the J-Link DLL. Fixed.
- Renesas RX231: OFS1 could not be modified. Fixed.
- Renesas RX: Added support for RX66N series devices
- Renesas RX: Added support for RX72M series devices
- Renesas RX: Added support for RX72M series devices
- Renesas RX: Added support for RX72N series devices
- Renesas RX: Added support for RX72T series devices
- Renesas RX: Added support for RX72T series devices
- Renesas RX: RX66T: Programming of option-setting memory (OSIS) did not work properly. Fixed.
- Renesas RX: When connecting to locked RX devices via JTAG (does not affect FINE!), 16-byte IDCODE (OSIS) could be rejected even though the correct code was given. Fixed.
- Renesas S7G2: QSPI flash programming did not work for QSPI flashes >= 16MB. Fixed.
- Resets during halt of TI RM57L843ZWT device, due to running watchdog, fixed. Enabled cross trigger interfaces to forward debug acknowledge signal to Watchdog.
- Resolved an issue where some Cypress PSoC4 devices would not unlock automatically when connecting to them. Fixed.
- RISC-V behind a DAP: Setting system variables <JLINK_CORESIGHT_CoreBaseAddr>, <JLINK_CORESIGHT_IndexAHBAPToUse>, <JLINK_CORESIGHT_IndexAPBAPToUse> from J-Link script files did not have any effect for RISC-V behind a DAP. Fixed.
- RISC-V behind a DAP: Setting system variables <JLINK_CORESIGHT_CoreBaseAddr>, <JLINK_CORESIGHT_IndexAHBAPToUse>, <JLINK_CORESIGHT_IndexAPBAPToUse> from J-Link script files did not have any effect for RISC-V behind a DAP. Fixed.
- RISC-V: Added reset type "Reset Pin" to explicitly allow resetting the target via the reset pin, instead of the <ndmreset> bit
- RISC-V: Changed default reset type from reset pin to <ndmreset> to support reset on almost all systems, also ones that do not populate a reset pin
- RISC-V: Interrupts were not disabled correctly during flash programming for built-in flash algos (works well for open flash loaders). Fixed.
- RISC-V: Reset could fail with "core did not halt after reset" even if the core halted correctly. Fixed.
- SPI-Flash programming for Spansion S25FL256L, fixed.
- STM32L031K6 secure chip did not work. Fixed.
- STM32WB55 added support for Co-Processor Wireless stack upgrade.
- TI RM42L420 added EEPROM support.
- TI RM44L520/RM44L920 added flash and EEPROM support
- TI RM57L843ZWT added EEPROM support.
- TI RM57L843ZWT added EEPROM support.
- Under some circumstances Flash Cache was not cleaned after erase operations.
- Unsecure read protection for STM32L151xx series devices, fixed.
- Unsecure write protection for STM32L151xxx series devices, fixed.
- When using J-Trace PRO with IAR EWARM a "failed to allocate x bytes of memory" error could occur. Fixed.
- Windows: Renesas RX: When using FINE interface and disabling ongoining debug mode on debug session close, it could happen that a thread was not exited gracefully, causing handle leaks. Fixed.
Firmware
- Flasher ARM / PRO / Portable PLUS: Chip erase could fail in stand-alone mode. Fixed.
- Flasher ARM / PRO / Portable PLUS: Init/Exit step BNE and BEQ could jump to #step + 1. Fixed.
- Flasher ARM / PRO / Portable PLUS: Open Flashloader RAMCodes in stand-alone-mode can be >12kB now.
- Flasher ARM / PRO / Portable PLUS: Parallel CFI NOR Flash memory programming could fail under special circumstances. Fixed.
- Flasher ARM / PRO / Portable PLUS: Stand-alone mode did not work for some ARM devices. Introduced in V6.47b. Fixed.
- Flasher ARM / PRO / Portable PLUS: Stand-alone mode did not work for some devices from Analog Devices (e.g. ADuCM7023). Fixed.
- Flasher ARM / PRO: FWrite command was unable to receive 512 bytes via UART at once. Fixed.
- Flasher ARM / PRO: Reading or writing memory in J-Link mode via JTAG caused the firmware to hang and report a USB timeout. Fixed.
- Flasher ARM V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- Flasher ARM/PPC/RX/PRO: Target power supply monitoring could erroneously detect an over-current. Fixed.
- Flasher Portable PLUS did not show the correct status under special circumstances. Fixed.
- Flasher Portable PLUS did not work in J-Link Mode while showing "OK" message. Fixed.
- Flasher Portable PLUS: Universal Flash Loader mode detection in batch mode did not work. Fixed.
- Flasher Portable PLUS: Number of bytes to program was not calculate correctly, progress bar showed wrong percentage. Fixed.
- Flasher Portable PLUS: Open flash loaders for RISC-V did not work properly anymore (introduced with V6.46). Fixed.
- Flasher Portable PLUS: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- Flasher PRO: Open flash loaders for RISC-V did not work properly anymore (introduced with V6.46). Fixed.
- Flasher PRO: Universal Flash Loader mode detection in batch mode did not work. Fixed.
- Flasher PRO: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- Flasher: Added stand-alone mode support for Traveo2 CYT2B and CYT4B devices.
- Flasher: Added stand-alone mode support for Traveo2 CYT2B and CYT4B devices.
- J-Link BASE/EDU/PLUS: SPI flash programming with J-Flash SPI was very slow. Fixed.
- J-Link EDU Mini: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be accessed correctly, resulting in non-functional debug sessions. Fixed.
- J-Link EDU Mini: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link EDU/BASE/PLUS V10: Added support for RISC-V behind a DAP as setup.
- J-Link EDU/BASE/PLUS V10: Increased heap size of firmware (Added support for heap over multiple memory ranges with gaps between them)
- J-Link EDU/BASE/PLUS V10: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be accessed correctly, resulting in non-functional debug sessions. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link EDU/BASE/PLUS V10: SWO: Under very special circumstances it could happen that the 1st byte received on SWO was swallowed. Only happened, if SWO pin was used for something else between SWO_Stop() and SWO_Start(). Fixed.
- J-Link EDU/BASE/PLUS V10: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- J-Link OB-K22-SiFive: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link PRO V4: Added support for RISC-V behind a DAP as setup.
- J-Link PRO V4: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be accessed correctly, resulting in non-functional debug sessions. Fixed.
- J-Link PRO V4: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link PRO V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- J-Link PRO V4: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
- J-Link ULTRA+ V4: Added support for RISC-V behind a DAP as setup.
- J-Link ULTRA+ V4: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be accessed correctly, resulting in non-functional debug sessions. Fixed.
- J-Link ULTRA+ V4: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link ULTRA+ V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- J-Link ULTRA+ V4: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
- J-Link-OB-K22-SiFive: Linux: When using both VCOM ports extensively under special circumstances it could happen that the USB communication locked up. Fixed.
- J-Trace PRO V1 Cortex-M: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
- J-Trace PRO V2 Cortex-M: Corrected typo on th webserver trace configuration page.
- J-Trace PRO V2 Cortex-M: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
- J-Trace PRO V2 Cortex: Corrected typo on th webserver trace configuration page.
- J-Trace PRO V2 Cortex: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
GDB Server
- Under special circumstances, a remote "g" packet error popped up when using the GDB Server with Cortex-AR or MIPS. Fixed.
GUI Applications
- Linux: The directory the application was executed from affected the behavior of the application. Fixed.
J-Flash
- Added command line parameter "?" (Same functionality as "-?").
- Added command line parameter "?" (Same functionality as "-?").
- Generated data files could be unnecessarily big. Fixed.
- Generated data files could be unnecessarily big. Fixed.
- Improved error messages during the check, if the data fits into the flash memory.
- Improved error messages during the check, if the data fits into the flash memory.
- Licenses that have been burned into J-Link via J-Link Commander "license add" command were not detected properly. Fixed.
J-Flash Lite
- Updated to select the flash base address of the selected device by default as "Prog. Addr." instead of always 0x00000000.
- Updated to select the flash base address of the selected device by default as "Prog. Addr." instead of always 0x00000000.
J-Flash SPI
- Added flash programming support for ISSI IS25LP016D SPI Flash.
- Added flash programming support for ISSI IS25LP016D SPI Flash.
- Added flash programming support for ISSI IS25LP080D SPI Flash.
- Added flash programming support for ISSI IS25LP080D SPI Flash.
- Added flash programming support for ISSI IS25WP016D SPI Flash.
- Added flash programming support for ISSI IS25WP016D SPI Flash.
- Added flash programming support for ISSI IS25WP080D SPI Flash.
- Added flash programming support for ISSI IS25WP080D SPI Flash.
- Added flash programming support for ISSI IS25WP128D SPI Flash.
- Added flash programming support for ISSI IS25WP128D SPI Flash.
- Added SPI flash programming support for ISSI IS25LP016D SPI flash.
- Added SPI flash programming support for ISSI IS25LP016D SPI flash.
- Licenses that have been burned into J-Link via J-Link Commander "license add" command were not detected properly. Fixed.
J-Flash SPI CL
- Added command line parameter "?" (Same functionality as "-?").
- Added command line parameter "?" (Same functionality as "-?").
J-Link Package
- USB driver for VCOM: Under very special circumstances bluescreens could occur when using VCOM. Fixed. (Driver update only applies to Windows Vista and later. Windows XP still uses the old driver as the new one is not compatible to Windows XP anymore)
JTAG Load
- Added command line parameters "?" and "-?" (Same functionality as "/?").
- Added command line parameters "?" and "-?" (Same functionality as "/?").
Remote Server
- Command line options '-select USB=<SN>' and '-SelectEmuBySN <SN>' did not work correctly. Fixed.
RTT Client
- Added command line parameter "?" (Same functionality as "-?").
- Added command line parameter "?" (Same functionality as "-?").
- Connecting to existing session did not work correctly on MacOS. Fixed.
- Linux: Ubuntu: Attaching to existing debug session did not work properly. Fixed.
RTT Logger
- Added command line parameter "?" (Same functionality as "-?").
- Added command line parameter "?" (Same functionality as "-?").
- Linux: Using logrotate lead to null characters being printed before RTT data. Fixed.,
RTT Viewer
- Added 'All terminals' message in case of connection loss.
- Added information display on how to correctly enter RTT control block search range.
- Echo to Terminal 0 / 'All terminals' was not working correctly. Fixed.
- Fixed 'Attach to existing session' mode for Windows, MacOS and Linux.
- Fixed typo.
- Improved handling for data logging.
- Improved handling for terminal logging.
- Improved J-Link connect/ disconnect sequence.
- Improved log messages when connecting to J-Link.
- Improved log output.
- Improved reconnecting for attach mode.
- Improved the handling in case reading of RTT data failed.
- In some occasions, the CL option '--autoconnect' did not work. Fixed.
- In some rare occasions, clearing a terminal could crash the application. Fixed.
- Linux: Ubuntu: Option "Attaching to existing debug session" did not work properly. Fixed.
- Some ANSI CSI sequences caused the application to crash. Fixed.
- The '--autoconnect' CL option caused the application to crash. Fixed.
STR91x Utility
- Added command line parameter "?" (Same functionality as "-?") and implemented "help" functionality which returns the available command line parameters.
- Added command line parameter "?" (Same functionality as "-?") and implemented "help" functionality which returns the available command line parameters.
Trace
- Under certain circumstances backtrace was not showing for targets with PTM. Fixed.
Version V6.46k (2019-07-19)
CCS Plugin
- Added a new option which allows configuring a J-Link script file (project dependent).
Commander
- RISC-V: Added <SWD> to the list of suggested/available interfaces
DLL
- JTAG: When only having 1 TAP in the JTAG chain and its <IRLen> matches the one for the configured CPU core but the TAP-ID was unknown, connect did not work. Fixed.
- Linux: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the libjlink* shared library was not found. Fixed.
- macOS: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the libjlink* shared library was not found. Fixed.
- Microchip J-32 OEM probes could not support legacy Atmel devices. Fixed.
- Re-attaching to existing debug session after connecting and disconnecting once via TELNET (e.g. used by RTT Client and RTT Viewer) did not work properly. Fixed.
- Windows: Renesas RX: When using FINE interface and disabling ongoining debug mode on debug session close, it could happen that a thread was not exited gracefully, causing handle leaks. Fixed.
Firmware
- Flasher ARM/PPC/RX/PRO: Target power supply monitoring could erroneously detect an over-current. Fixed.
- Flasher Portable PLUS did not show the correct status under special circumstances. Fixed.
- J-Link EDU/BASE/PLUS V10: Increased heap size of firmware (Added support for heap over multiple memory ranges with gaps between them)
- J-Link EDU/BASE/PLUS V10: SWO: Under very special circumstances it could happen that the 1st byte received on SWO was swallowed. Only happened, if SWO pin was used for something else between SWO_Stop() and SWO_Start(). Fixed.
J-Flash
- Licenses that have been burned into J-Link via J-Link Commander "license add" command were not detected properly. Fixed.
J-Flash SPI
- Licenses that have been burned into J-Link via J-Link Commander "license add" command were not detected properly. Fixed.
RTT Client
- Linux: Ubuntu: Attaching to existing debug session did not work properly. Fixed.
RTT Viewer
- Fixed typo.
- Improved the handling in case reading of RTT data failed.
- Linux: Ubuntu: Option "Attaching to existing debug session" did not work properly. Fixed.
- Some ANSI CSI sequences caused the application to crash. Fixed.
Version V6.46j (2019-07-12)
DLL
- Linux: Delayed / slowed execution of certain API functions when using J-Link via USB (e.g. on Close()). Introduced in V6.46. Fixed.
- NXP LPC18xx / LPC43xx: After QSPI flash programming, the QSPI flash memory was no longer memory mapped accessible. Introduced in V6.41. Fixed.
- QSPI flash programming: When the QE bit was set before flash programming, it has been cleared but not restored by the DLL. Introduced in V6.46h. Fixed.
- RISC-V: Added reset type "Reset Pin" to explicitly allow resetting the target via the reset pin, instead of the <ndmreset> bit
- RISC-V: Changed default reset type from reset pin to <ndmreset> to support reset on almost all systems, also ones that do not populate a reset pin
- RISC-V: Reset could fail with "core did not halt after reset" even if the core halted correctly. Fixed.
Firmware
- J-Link EDU Mini: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be accessed correctly, resulting in non-functional debug sessions. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be accessed correctly, resulting in non-functional debug sessions. Fixed.
- J-Link PRO V4: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be accessed correctly, resulting in non-functional debug sessions. Fixed.
- J-Link ULTRA+ V4: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be accessed correctly, resulting in non-functional debug sessions. Fixed.
Version V6.46i (2019-07-05)
DLL
- Added support for command string "CORESIGHT_SetCoreBaseAddr"
- Added support for Cypress MB9DF / MB9EF series (FCR4) devices.
- For the MPC560xx devices, the ECC SRAM was not initialized after connect. Fixed.
- Hilscher NetX90 flash bank size, fixed.
- Qorvo GP570 / UE878 / QPG6 family: Flash programming did not work in recent silicon revisions. Fixed.
- Qorvo GPxxx: Under special circumstances, flash programming did not work. Fixed.
- Renesas RX231: OFS1 could not be modified. Fixed.
- Renesas RX: RX66T: Programming of option-setting memory (OSIS) did not work properly. Fixed.
- Renesas RX: When connecting to locked RX devices via JTAG (does not affect FINE!), 16-byte IDCODE (OSIS) could be rejected even though the correct code was given. Fixed.
- Resets during halt of TI RM57L843ZWT device, due to running watchdog, fixed. Enabled cross trigger interfaces to forward debug acknowledge signal to Watchdog.
- STM32L031K6 secure chip did not work. Fixed.
- When using J-Trace PRO with IAR EWARM a "failed to allocate x bytes of memory" error could occur. Fixed.
Firmware
- Flasher ARM / PRO / Portable PLUS: Chip erase could fail in stand-alone mode. Fixed.
GUI Applications
- Linux: The directory the application was executed from affected the behavior of the application. Fixed.
Version V6.46h (2019-06-28)
DLL
- Added support for RISC-V behind a DAP as setup.
- Added support for RISC-V via SWD for RISC-V behind a DAP setups.
- RAM size of ST STM32F412 series devices, fixed.
- SPI-Flash programming for Spansion S25FL256L did not work under spepcial circumstances. Fixed.
- Under some circumstances Flash Cache was not cleaned after erase operations. Fixed.
Firmware
- Flasher ARM / PRO / Portable PLUS: Init/Exit step BNE and BEQ could jump to #step + 1. Fixed.
- Flasher ARM / PRO / Portable PLUS: Open Flashloader RAMCodes in stand-alone-mode can be >12kB now.
- Flasher ARM / PRO: FWrite command was unable to receive 512 bytes via UART at once. Fixed.
- Flasher ARM V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- Flasher Portable PLUS did not work in J-Link Mode while showing "OK" message. Fixed.
- Flasher Portable PLUS: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- Flasher PRO: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- J-Link EDU/BASE/PLUS V10: Added support for RISC-V behind a DAP as setup.
- J-Link EDU/BASE/PLUS V10: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- J-Link PRO V4: Added support for RISC-V behind a DAP as setup.
- J-Link PRO V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- J-Link PRO V4: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
- J-Link ULTRA+ V4: Added support for RISC-V behind a DAP as setup.
- J-Link ULTRA+ V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fixed.
- J-Link ULTRA+ V4: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
- J-Trace PRO V1 Cortex-M: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
- J-Trace PRO V2 Cortex-M: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
- J-Trace PRO V2 Cortex: When connecting via IP and using RTT it could happen that J-Link FW crashed and rebooted if the PC did not exit the controlling process in a clean way. Fixed.
RTT Logger
- Linux: Using logrotate lead to null characters being printed before RTT data. Fixed.
RTT Viewer
- In some occasions, the CL option '--autoconnect' did not work. Fixed.
Version V6.46g (2019-06-14)
Firmware
- Flasher ARM / PRO / Portable PLUS: Stand-alone mode did not work for some ARM devices. Introduced in V6.47b. Fixed.
- Flasher ARM / PRO: Reading or writing memory in J-Link mode via JTAG caused the firmware to hang and report a USB timeout. Fixed.
J-Flash SPI
- J-Link BASE/EDU/PLUS: SPI flash programming with J-Flash SPI was very slow. Fixed.
Version V6.46f (2019-06-13)
Version V6.46e (2019-06-13)
DLL
- Added native trace buffer support for Renesas RZ/A2M series.
- Changed an ambiguous J-Link report output.
- Resolved an issue where some Cypress PSoC4 devices would not unlock automatically when connecting to them. Fixed.
GDB Server
- Under special circumstances, a remote "g" packet error popped up when using the GDB Server with Cortex-AR or MIPS. Fixed.
Remote Server
- Command line options '-select USB=<SN>' and '-SelectEmuBySN <SN>' did not work correctly. Fixed.
RTT Client
- Connecting to existing session did not work correctly on MacOS. Fixed.
RTT Viewer
- The '--autoconnect' CL option caused the application to crash. Fixed.
Version V6.46d (2019-06-07)
Firmware
- Flasher ARM / PRO / Portable PLUS: Parallel CFI NOR Flash memory programming could fail under special circumstances. Fixed.
- Flasher ARM / PRO / Portable PLUS: Stand-alone mode did not work for some devices from Analog Devices (e.g. ADuCM7023). Fixed.
- Flasher Portable PLUS: Universal Flash Loader mode detection in batch mode did not work. Fixed.
- Flasher Portable PLUS: Number of bytes to program was not calculate correctly, progress bar showed wrong percentage. Fixed.
- Flasher Portable PLUS: Open flash loaders for RISC-V did not work properly anymore (introduced with V6.46). Fixed.
- Flasher PRO: Open flash loaders for RISC-V did not work properly anymore (introduced with V6.46). Fixed.
- Flasher PRO: Universal Flash Loader mode detection in batch mode did not work. Fixed.
RTT Viewer
- Added 'All terminals' message in case of connection loss.
- Echo to Terminal 0 / 'All terminals' was not working correctly. Fixed.
- Fixed 'Attach to existing session' mode for Windows, MacOS and Linux.
- Improved handling for data logging.
- Improved handling for terminal logging.
- Improved J-Link connect/ disconnect sequence.
- Improved log messages when connecting to J-Link.
- Improved log output.
- Improved reconnecting for attach mode.
- In some rare occasions, clearing a terminal could crash the application. Fixed.
Version V6.46c (2019-06-03)
DLL
- Open flash loaders for RISC-V did not work properly anymore (introduced with V6.46). Fixed.
- Renesas R5F51306 (RX130) devices were not detected by the J-Link DLL. Fixed.
J-Link Package
- USB driver for VCOM: Under very special circumstances bluescreens could occur when using VCOM. Fixed. (Driver update only applies to Windows Vista and later. Windows XP still uses the old driver as the new one is not compatible to Windows XP anymore)
Version V6.46b (2019-05-31)
DLL
- Analog Devices ADUCM355: Reset could not be overwritten using a J-Link script file. Fixed.
- Minor bug in flash programming algorithm for STM32G0xx series devices, fixed.
- Renesas S7G2: QSPI flash programming did not work for QSPI flashes >= 16MB. Fixed.
- TI RM42L420 added EEPROM support.
- TI RM44L520/RM44L920 added flash and EEPROM support.
RTT Viewer
- Added information display on how to correctly enter RTT control block search range.
Version V6.46a (2019-05-27)
DLL
- RISC-V: Interrupts were not disabled correctly during flash programming for built-in flash algos (works well for open flash loaders). Fixed.
Firmware
- J-Link EDU Mini: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link OB-K22-SiFive: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link PRO V4: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
- J-Link ULTRA+ V4: RISC-V: Reset on SiFive FE310 device (mounted on HiFive1 boards) could fail with timeout error. Fixed.
Version V6.46 (2019-05-23)
Control Panel
- Clicking the tray icon now opens the web version of the panel.
DLL
- Added chip secure and unsecure procedure for Autochips AC781x series devices.
- Added debug and QSPI programming support for Xilinx Zynq 7015 device.
- Added debug support for ST STR710RZ device.
- Added debug support for Xilinx Zynq UltraScale+ Cortex-R5_0 core.
- Added debugging and Flash programming support for MicroSemi M2S090 and M2S150 series devices.
- Added device names for Xilinx Zynq UltraScale+ CG series: XCZU2CG_R5_0, XCZU3CG_R5_0, XCZU4CG_R5_0, XCZU5CG_R5_0, XCZU6CG_R5_0, XCZU7CG_R5_0, XCZU9CG_R5_0
- Added device names for Xilinx Zynq UltraScale+ DR series: XCZU21DR_R5_0, XCZU25DR_R5_0, XCZU27DR_R5_0, XCZU28DR_R5_0, XCZU29DR_R5_0, XCZU39DR_R5_0, XCZU46DR_R5_0, XCZU47DR_R5_0, XCZU48DR_R5_0, XCZU49DR_R5_0
- Added device names for Xilinx Zynq UltraScale+ EG series: XCZU2EG_R5_0, XCZU3EG_R5_0, XCZU4EG_R5_0, XCZU5EG_R5_0, XCZU6EG_R5_0, XCZU7EG_R5_0, XCZU9EG_R5_0, XCZU11EG_R5_0 XCZU15EG_R5_0, XCZU17EG_R5_0, XCZU19EG_R5_0
- Added device names for Xilinx Zynq UltraScale+ EV series: XCZU4EV_R5_0, XCZU5EV_R5_0, XCZU7EV_R5_0
- Added Flash and option bytes support for ST STM32WB55
- Added Flash and User Data Page programming support for Silicon Labs EFR32xG21 and EFR32xG22 series.
- Added flash programming support for AmbiqMicro AMA2B1KK-KLR family devices (AMA2BEVB).
- Added flash programming support for Analog Devices ADuCM410 device.
- Added flash programming support for Cypress CYBLE-012011-00 series devices.
- Added flash programming support for EFR32FG14PxxxF128.
- Added Flash programming support for Hilscher NetX90 series device.
- Added Flash programming support for NXP MK02FNxxx series devices.
- Added Flash programming support for NXP MKW39/38/37
- Added flash programming support for Renesas R5F51306 and R5F51307 devices.
- Added flash programming support for Renesas R7FS12877 and R7FS1JA78.
- Added flash programming support for Renesas R7FS5D37A.
- Added flash programming support for Silicon Labs EFR32ZG14PxxxF256.
- Added flash programming support for Silicon Labs for BGM13xxxxxxx and MGM13xxxxxxx series devices.
- Added flash programming support for Silicon Labs ZGM130S.
- Added Flash programming support for STM32L41x and STM32L42x series devices.
- Added mass erase for Silicon Labs EFR32 series devices.
- Added new device names for RZA2 series devices.
- Added OTP support for Nordic Semi nRF9160 device.
- Added QSPI Flash programming support for Dialog Semiconductor DA14196 and fixed bug for DA14495.
- Added Regular-UICR support for Nordic Semi nRF9160 device.
- Added support debug and programming support for: Analog ADuCM4150, Atmel ATSAM9CN11, ATSAM9CN12 and ATSAM9N12 series devices.
- Added support for open flash loader for ARM7/9 based devices.
- Implemented heap visualization for DLL in debug tab of control panel
- Infineon TLE9862: Added flash programming support.
- Infineon TLE9872: Added flash programming support.
- Internal Flash programming of Autochips AC781x series devices, fixed.
- macOS: Under special circumstances, USB re-enumeration during FW update was not recognized properly. Fixed.
- NXP iMX8 (Cortex-M4). Added debug support.
- NXP iMXRT500: Added flash programming support.
- NXP iMXRT600: Added flash programming support.
- NXP LPC55xx / LPC55Sxx: Added the SRAM @ address 0x2000000 as RTT search range to support auto-detection of the RTT block.
- Open Flashloader: Added new functions SEGGER_OPEN_Erase() and SEGGER_OPEN_Program() which can be used to erase multiple sectors or to program multiple pages.
- Open Flashloader: The flash size can now be limited by the <FlashSize> tag in the JLinkDevices.xml entry.
- Silicon Labs EFM32GG12 family: Added flash programming support (Main, User Data, Lock Bits and Bootloader flash).
- Silicon Labs EFR32xG1: Added flash programming support for the bootloader section.
- Silicon Labs: Added debug support for EFR32xG22 family devices.
- SiliconLabs EFM32GG12 and EFM32GG11 series devices bootloader flash size, corrected.
- TI TMS570LC4357 added R/W EEPROM support
- When trying to perform a firmware update from one process while another one is already connected to the same J-Link, the process performing the FW update could crash with an access violation. Fixed.
- Windows: DLL and some executables were bigger than necessary (incorrect project settings). Fixed.
Firmware
- Flasher ARM / PRO / Portable PLUS: Fixed data file read in for last page if flash is located a end of 4G mem area.
- J-Link EDU Mini: RISC-V: Added support for RV64 (RISC-V 64-bit)
- J-Link EDU/BASE/PLUS V10: RISC-V: Added support for RV64 (RISC-V 64-bit)
- J-Link PRO V4: RISC-V: Added support for RV64 (RISC-V 64-bit)
- J-Link ULTRA+ V4: RISC-V: Added support for RV64 (RISC-V 64-bit)
J-Flash SPI
- Added Flash programming support for Adesto AT25SF128A SPI FLASH.
J-Link Package
- Installer: Added option (new default) to update a J-Link installation (removes the previously installed instance)
- Installer: Windows: Added new option (default from now on) that installs and updates a J-Link installation into a generic directory
- Installer: Windows: Added start menu shortcut to open web browser based control panel
- Installer: Windows: Updated product images
Manual
- UM08001: Added description of J-Mem to manual
RTT
- Fixed warnings.
Trace
- Added JLinkScript for LPC845 MTB trace init.
Version V6.44i (2019-05-17)
DLL
- Analog Devices CM40x: Under special circumstances, single stepping did not work. Fixed.
- Flash programming of SPIFI (QSPI) based algorithms with DUALSPI configuration did not work. Fixed.
- Microchip (Atmel) SAMC20/21 and SAMD20/21 family: Under special circumstances, the auxiliary space could not be programmed. Fixed.
- Microchip (Atmel) SAMHA0A / SAMHA1A: Under special circumstances, the auxiliary space could not be programmed. Fixed.
- MTB backtrace: Conditional branches which were not taken (condition not fulfilled) were not handled correctly, resulting in incorrect backtrace information. Fixed.
- MTB: Single stepping could lead to missing backtrace data. Fixed.
- MTB: With some MTB implementations, more instructions were reported as executed as really were executed. Fixed.
- The RAM size used during flash programming was incorrect for some RX130 devices. Fixed.
- Under special circumstances, flash programming of Renesas RZA1 devices with dual SPI flash configuration did not work. Fixed.
- When using flash breakpoints while having MTB enabled, flash breakpoints could not be set. Fixed.
Firmware
- Flasher PRO: Universal flash loader: UART interface in full duplex mode did not work. Fixed.
- J-Link BASE V10: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link BASE V9: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link EDU Mini: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link EDU V10: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link EDU V9: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link Lite Cortex-M V9: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link Lite V9: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link PLUS V10: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link PLUS V9: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link PRO V4: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Link ULTRA+ V4: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Trace PRO V1 Cortex-M: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Trace PRO V2 Cortex-M: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
- J-Trace PRO V2 Cortex: Under very special circumstances it could happen that when writing a bulk of words into memory on Cortex-M, a HardFault was triggered inside the J-Link FW. Fixed.
Version V6.44h (2019-05-03)
DLL
- Autochips AC781x series devices, clock settings for flash module, fixed.
- Command string "CORESIGHT_SetMTBBufUsageSize" did not work correctly. (Only half of configured MTB buffer size was used) Fixed.
- Command string "CORESIGHT_SetMTBBufUseAddr" did not work correctly. Fixed.
- Improved sanity checks for MTB buffer configuration.
- Microchip (Atmel) ATSAM5x family: Under special circumstances, erase of the auxiliary space did not work. Fixed.
- Under certain circumstances connecting to a NXP Kinetis L Series device could fail. Introduced with V6.40. Fixed.
- Under special circumstances, the used timeout for Open Flashloader based algorithms was chosen too low resulting in timeout errors. Fixed.
- Under special circumstances, watchpoints got corrupted after single stepping. Fixed.
GDB Server
- Improved RTOS plugin for embOS to be more descriptive (info will be added to RTOS plugin SDK documentation as well)
- Improved RTOS plugin handling, especially when having FPU support
Manual
- UM08001: Added missing - and updated existing command lines for all tools
Version V6.44g (2019-04-18)
DLL
- Extending existing devices through the JLinkDevices.xml from the hidden device database did not work. Fixed.
- ST STM32F412VG: Under special circumstances, flash programming did not work. Fixed.
Firmware
- Flasher: Programming could fail, if the Flasher was not connected to a network or an USB host. Fixed.
- Flasher: Under special circumstances, flash programming of Open Flashloader based algorithms in stand-alone mode failed. Introduced in V6.44e. Fixed.
Version V6.44f (2019-04-12)
Control Panel
- Linux: Log tab did not work properly. Fixed.
- macOS: Log tab did not work properly. Fixed.
DLL
- ST STM32H7 series: Improved flash programming speed.
- When downloading to flash, empty sectors were erased again unnecessarily. (e.g. ST STM32H7 series) Fixed.
Firmware
- Flasher: Flasher Portable PLUS did not power off automatically after being charged. Fixed.
- Flasher: Flasher Portable PLUS did not use the DisplayName tags. Fixed.
- J-Link-OB-K22-CortexM: Drag and drop programming could fail with "failed to allocate memory for buffer" FAIL.TXT. Fixed.
J-Link Package
- Installer: macOS: License text was outdated. Fixed.
Version V6.44e (2019-04-05)
Commander
- "term" expected a capital letter as protocol selection for no reason. Fixed.
DLL
- Analog Devices ADuCM320: Under special circumstances, block verification errors could occur while an additional readback afterwards succeeded (data cache of flash controller was not invalidated correctly). Fixed.
- Renesas S5D9 series: programming of option-setting memory did not work properly. Fixed.
- Reset did not work properly for LPC12xx series devices. Fixed.
- RISC-V: Latest Syntacore SCR1 bitstreams were no longer correctly detected as RISC-V cores. Fixed.
- Some devices names passed by TI's Code Composer Studio (CCS) were not accepted by the J-Link DLL (e.g. TMS570LS20216SZWT). Fixed.
- Updated NXP's K32W device family support.
Firmware
- Flasher ARM/PRO fixed missing CR LF after change baud rate command
- Flasher: exit steps will only be executed after successful flashing
J-Link Package
- Linux: DEB/RPM package versioning was incorrect in case no patch level was applied (patch level == 0), so that for example V6.45 was considered older than V6.44a. Fixed.
Version V6.44d (2019-03-27)
Commander
- Command "vtref" did not work correctly. Introduced in V6.42. Fixed.
DLL
- Added "RV64" as selection to list of supported devices
- ST STM32F4xx (Access line devices): Improved flash programming speed.
- ST STM32L0 family: Attach did not work. Fixed.
- Under special circumstances, target connection via JTAG did not work (e.g. for TI CC1310F128). Introduced in V6.44c. Fixed.
GDB Server
- Added support for RV64 (RISC-V 64-bit)
- Some cores were shown as ???. Fixed.
J-Flash Lite
- Some cores were shown as ???. Fixed.
Version V6.44c (2019-03-22)
Commander
- RISC-V: Disassembly of LI instruction was disassembled incorrectly. Fixed.
DLL
- Added support for RV64 (RISC-V 64-bit)
- Flash programming support for Dialog Semiconductor DA14x95 series device, fixed.
- Microchip IS208x: Flash programming could fail if WDT on target device was already enabled. Fixed.
- Microchip IS208x: Halting core before first instruction of user code was executed at 0x20_0000 did not work properly. Fixed.
- SPIFI-Lib, restore of QE (Quad Enable) bit, fixed.
- ST STM32F4 Access Line (e.g. STM32F412VG): Flash programming did not work under special circumstances. Fixed.
- The unlocking algorithm for STM32F0 series devices did not work correctly. Fixed.
- TI TMS570LS10 / TMS570LS10: Flash programming did not work. Fixed.
Firmware
- J-Link EDU/BASE/PLUS V10: Microchip IS208x 2-wire JTAG: Under very special circumstances, a response from the device was not evaluated correctly, leading to verify errors, even if everything was O.K. Fixed.
- J-Link PRO V4: Microchip IS208x 2-wire JTAG: Under very special circumstances, a response from the device was not evaluated correctly, leading to verify errors, even if everything was O.K. Fixed.
- J-Link ULTRA+ V4: Microchip IS208x 2-wire JTAG: Under very special circumstances, a response from the device was not evaluated correctly, leading to verify errors, even if everything was O.K. Fixed.
J-Flash
- The unlocking algorithm for STM32F0 series devices did not work correctly. Fixed.
J-Link Package
- Windows: The uninstaller ignored the /S parameter. Fixed.
RTT Viewer
- Fixed RTT Control block addresses were not displayed inside the configuration dialog. Fixed.
- Improved output speed of RTT data.
- Improved RTT data parsing speed.
- Terminals shared the same font color/ background color. Fixed.
Version V6.44b (2019-03-15)
DLL
- Added command string "SetSkipDebugDeInit" to allow skipping of debug de-init at the end of a debug session. This may be used on Cortex-M for example to make sure that DEMCR.TRCENA stays enabled and so does the DWT unit and CYCCNT.
- Added device names for NXP iMXRT101x series devices, MIMXRT1015xxx4A, MIMXRT1015xxx5A.
- Added missing Cortex-A72 to device selection list.
- Linux: DEB package tried to incorrectly remove symlink that pointed to the previously installed version. Fixed.
- Microchip IS2083B: Changed halt address after reset to 0x27_0000
- NXP i.MXRT1064: Flash programming support for the internal (QSPI) flash was not available for all iMXRT1064 devices. Fixed.
- NXP i.MXRT1064: Some devices names (e.g. MIMXRT1064xxx5A) were not recognized by the J-Link DLL. Fixed.
- NXP LPC51U68: "LPC51U68JBD48" and "LPC51U68JBD64" could not be selected as target device name. Fixed.
- NXP LPC8N804: Under special circumstances, reset did not work and returned an error. Fixed.
- NXP LPC8xx family: Some device names where not recognized by the J-Link DLL. Fixed.
- Option bytes programming could fail in stand-alone mode for Renesas S5D9 series devices. Fixed.
Firmware
- Flasher: FTP server did not report errors for invalid paths. Fixed.
- Flasher: Option bytes programming could fail in stand-alone mode for Renesas S5D9 series devices. Fixed.
J-Flash
- J-Flash did not handle the alignment information for Open Flash Loader correctly. Fixed.
Version V6.44a (2019-03-08)
DLL
- Microchip IS208x series: Improved flash programming speed
- Microchip IS208x series: When debugging in Keil uVision, the error message "Cannot read register ACON while core is running" could occur. Fixed.
- Microchip PIC32MX family: For some devices (e.g. PIC32MX270F256D) unlock did not work. Fixed.
- NXP LPC55xx / LPC55SXX: Under special circumstances (flash erased), flash programming failed. Fixed.
- QSPI flash programming support for Freescale K80/K82 series devices, fixed.
- Updated unsecure dialog for Microchip PIC32xx series devices.
Firmware
- (Flasher Portable PLUS): Added support for upt to 16 images
- (Flasher Portable PLUS): DisplayName corrected for Batch mode
- J-Link EDU Mini: RISC-V: When writing memory via 32-bit system bus accesses, it could happen that garbage was written for the first 32-bit in case a 8-/16-bit access preceded the write. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: When writing memory via 32-bit system bus accesses, it could happen that garbage was written for the first 32-bit in case a 8-/16-bit access preceded the write. Fixed.
- J-Link PRO V4: RISC-V: When writing memory via 32-bit system bus accesses, it could happen that garbage was written for the first 32-bit in case a 8-/16-bit access preceded the write. Fixed.
- J-Link ULTRA+ V4: RISC-V: When writing memory via 32-bit system bus accesses, it could happen that garbage was written for the first 32-bit in case a 8-/16-bit access preceded the write. Fixed.
J-Flash SPI
- Cypress S25FS512S: This flash was not detected by the auto-detect feature of J-Flash SPI. Fixed.
Version V6.44 (2019-03-01)
DLL
- Added debug support for Syntacore SCR1 (RISC-V based). Fixed.
- Added Flash programming support for Autochip AC781x series devices.
- Added flash programming support for Dialog Semiconductor DA1469x device family.
- Added Flash programming support for iMXRT101x series devices.
- Added Flash programming support for Maxim MAX32625 and MAX32626 series devices.
- Added flash programming support for NXP IMXRT1064 series devices.
- Added flash programming support for NXP LPC54018JxM/LPC54S018JxM series devices.
- Added flash programming support for ST STM32L552xx and STM32L562xx series devices.
- Added Flash programming support for STM32G070xx series devices.
- Added Flash programming support for Toshiba TMPM4G series devices.
- Added Flash programming support for Toshiba TMPM4K series devices.
- Added Info Flash Bank programming support for TI MSP432P401M and MSP432P401R devices.
- Added QSPI Flash programming support for Mediatek MT7686 series devices.
- Added Trusted Secure IP Authentication for Renesas RZ-A2M series devices.
- Analog Devices nRF52811_xxAA: Added flash programming support.
- Dialog Semiconductor DA1469x: Under special circumstances, flash programming did not work. Fixed.
- Improved connect for MediaTek MT7686 series device.
- J-Link script files: When using the same label name in multiple functions, it could happen that a "goto" jumped to the wrong label. Fixed.
- Microchip IS208x: If user application enabled the WDT of the device, debugging did not work correctly (WDT kept running while core was halted). Fixed.
- NXP MK22FN512xxx12: Flash size assumed by the DLL was incorrect (256 KB instead of 512 KB). Fixed.
- NXP S32K14x (e.g. S32K144): Erasing more then one sector of the EEPROM did not work. Fixed.
- RISC-V: Enabled support for RTT and memory accesses while the CPU is running (requires RISC-V implementation with system bus access support)
- ST STM32F730xx / STM32F750xx: Added flash programming support (internal flash).
- ST STM32F730xx / STM32F750xx: Added flash programming support (QSPI flash).
- ST STM32H750xx: Added flash programming support (internal flash).
- ST STM32L010: Added flash programming support.
- Syntacore SCR1 (RISC-V based) device was not detected properly. Fixed.
- When connecting to a J-Link via TCP/IP and making use of auto-detect (not specifying an IP or S/N), the connection failed. Introduced with V6.42. Fixed.
DLL Updater
- Under some locale distributions of Windows, Keil uVision could not be updated. Fixed.
Firmware
- Flasher Portable PLUS: Update Batch file processing, now 16 setups supported
- Flasher: Added debug interface power down after stand-alone programming.
- Flasher: Added support for Cortex-M23/M33.
- Flasher: SPI interface supports up to 21MHz now. Idle state of SCK will no longer be forced to high-level.
- J-Link EDU Mini: Enabled RTT support for RISC-V in firmware (requires RISC-V implementation with system bus access support)
- J-Link EDU Mini: RISC-V: 8 and 16 bit write accesses to non-4-byte aligned addresses did not work correctly. Fixed.
- J-Link EDU Mini: Syntacore SCR1 (RISC-V): Single stepping did not work reliably. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: 8 and 16 bit write accesses to non-4-byte aligned addresses did not work correctly. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: Enabled RTT support for RISC-V in firmware (requires RISC-V implementation with system bus access support)
- J-Link EDU/BASE/PLUS V10: Syntacore SCR1 (RISC-V): Single stepping did not work reliably. Fixed.
- J-Link OB-K22-SiFive: RISC-V: 8 and 16 bit write accesses to non-4-byte aligned addresses did not work correctly. Fixed.
- J-Link PRO V4: Enabled RTT support for RISC-V in firmware (requires RISC-V implementation with system bus access support)
- J-Link PRO V4: RISC-V: 8 and 16 bit write accesses to non-4-byte aligned addresses did not work correctly. Fixed.
- J-Link PRO V4: Syntacore SCR1 (RISC-V): Single stepping did not work reliably. Fixed.
- J-Link ULTRA+ V4: Enabled RTT support for RISC-V in firmware (requires RISC-V implementation with system bus access support)
- J-Link ULTRA+ V4: RISC-V: 8 and 16 bit write accesses to non-4-byte aligned addresses did not work correctly. Fixed.
- J-Link ULTRA+ V4: Syntacore SCR1 (RISC-V): Single stepping did not work reliably. Fixed.
- J-Link-OB-XMC4200: Using the <getmi> command in J-Link Commander before connecting to the target device could cause the J-Link firmware to hang and report a USB timeout. Fixed.
Remote Server
- Added J-Link selection options.
- Under special circumstances it could happen that in tunneled mode a connection to the tunnel server was closed immediately, even if the connection itself was fine. Fixed.
STM32 Utility
- Added support to reset option bytes for STM32H7xxxx.
Trace
- Added StartETB and StopETB JLinkScript file functions which can be used to replace the generic ETB init.
Version V6.42f (2019-02-26)
DLL
- Cypress PSoC4 family: Under special circumstnaces, connect did not work (e.g. on some CY8C4125xxx-Sxxx based device). Fixed.
- EFM32HG (4 KB variants; e.g. EFM32HG210F32): Flash programming did not work. Fixed.
- NXP LPC55xx / LPC55SXX: Under special circumstances, flash programming failed (verification error). Fixed.
- Renesas RX: Setting the authentication key via J-Link Command String (exec SetRXIDCode <Code>) did not work. Fixed.
- Under special circumstances, when a breakpoint was set on the upper and lower halfword of the same word, one of the two breakpoints could be ignored. Fixed.
Version V6.42e (2019-02-21)
Commander
- Commands "testnrspeed" and "testnwspeed" did not produce correct KB/s output. Fixed.
DLL
- A reset did not halt an Infineon XMC MCUs under special circumstances. Fixed.
- Microchip (Atmel) SAM5x auxiliary space: Under special circumstances, flash programming failed. Fixed.
- NXP S32k116: When programming the data flash @ 0x10000000, verification errors could occur. Fixed.
- RAM reinitialization during connect for NXP S32K1xx series devices, fixed.
- Read speeds for RTT buffer sizes >2KB improved by 10-15%.
- RISC-V: Improved log output for detected features of core.
- RISC-V: In case a RISC-V implementation only supported memory accesses via system bus but J-Link did not, no appropriate error message was output. Fixed.
- RISC-V: Under special circumstances, SiFive E31ARTY core (bitstream for ARTY board) was not recognized as a known core by J-Link. Fixed.
- ST STM32F7 QSPI: Increased the supported flash size up to 64 MB.
Firmware
- Flasher: The PCode functions for "reset"/"after reset" were not always used. Fixed.
- J-Link EDU Mini: RISC-V: Added support for memory accesses via system bus
- J-Link EDU/BASE/PLUS V10: RISC-V: Added support for memory accesses via system bus
- J-Link PRO V4: RISC-V: Added support for memory accesses via system bus
- J-Link ULTRA+ V4: RISC-V: Added support for memory accesses via system bus
J-Flash Lite
- Support for debug interfaces other than JTAG broke. (Introduced in V6.42c) Fixed.
RTT
- Read speeds for RTT buffer sizes >2KB improved by 10-15%.
Version V6.42d (2019-02-15)
DLL
- Improved ROM table scan for ARMv8-A based cores (e.g. Cortex-A53/72)
- Microchip IS208x: If control over target was lost, it could happen that the J-Link SW hung because of entering an endless loop. Fixed.
- Microchip IS208x: If FLASH_HDR_B1 was completely 0xFF (empty), it could happen that J-Link detected the wrong flash bank to be active. Fixed.
- Programming of Renesas RX230 / RX231 based devices could fail with programming errors when reprogramming flash at higher flash clocks (>= 36 MHz). Fixed.
- When connecting to an Renesas RX231 based device a warning did occur that an RX230 based device was configured. Fixed.
- When selecting generic Cortex-A53/72, the error message "Failed to power up DAP" could occur even if the DAP init was fine. Fixed.
Firmware
- J-Link-OB-K22-NordicSemi: VCOM: If Hardware flow control was used and the target interrupted the transmission by setting RTS == HIGH, it could happen that J-Link did not continue the transmission once RTS became LOW again. Fixed.
J-Flash
- Programming of Renesas RX230 / RX231 based devices could fail with programming errors when reprogramming flash at higher flash clocks (>= 36 MHz). Fixed.
Version V6.42c (2019-02-11)
Commander
- When having a comment '//' after the value/NumBytes on a w1/w2/w4 or mem command, it was accidentally interpreted as a memory zone. Fixed.
DLL
- Flash programming support for Dialog Semiconductor DA14195 series device, PLL settings were wrong. Fixed.
- When using streaming trace with timestamps, under very special circumstances a buffer overflow could happen. Fixed.
GDB Server
- cJTAG could not be selected in the TIF selection dialog. Fixed.
J-Flash Lite
- cJTAG could not be selected in the TIF selection dialog. Fixed.
Version V6.42b (2019-02-05)
DLL
- Connecting to J-Links via LAN-IP using identify by S/N did not work. Introduced in V6.42. Fixed.
- Connecting to SiFive RISC-V targets via cJTAG could fail if the device did not report a JTAG TAP Id. Fixed.
- J-Link script files: Big static arrays (>= 1 KB) could make script execution causing access violations. Fixed.
- Microchips SAMD51x: Flash programming performance improved.
- Microchips SAMD51x: Under special circumstances, user row programming did not work. Fixed.
- When selecting "E31ARTY" as device name, connecting via cJTAG failed. Fixed.
Firmware
- J-Link PRO V4: Added support for TIF Microchip 2-wire JTAG via TDI
- J-Link ULTRA+ V4: Added support for TIF Microchip 2-wire JTAG via TDI
GDB Server
- Cortex-M: Reading/Writing of single precision FPU registers s23-s31 did not work. Fixed.
- Cortex-M: Writing of double precision FPU registers d0-d15 did not work. Fixed.
- When register index list contained gaps, it was possible that writing a single register after the first gap resulted in an incorrect register being written. Fixed.
Version V6.42a (2019-02-01)
DLL
- improved connect sequence for TI AM335x series devices.
- Sector size of NXP MKV42Fxxx, MKV44Fxxx and MKV46Fxxx devices was incorrect. Fixed.
- SPIFI flash programming speed improved by 10 to 15% for certain devices. Affected device series: Microchip SAMV7, Broadcom BCM89107, Marvell MW30x, Maxim MAX3265, NXP LPC18xx, NXP LPC43xx, NXP LPC408x, NXP LPC54xx, Renesas RZ/A1L, Renesas RZ/A1H, Renesas RZ/T1, Renesas Synergy, Xilinx Zynq7000.
J-Flash
- Added support to write to the DEV_RAM on the TI PGA900, if memory remapping is set.
Version V6.42 (2019-01-30)
Commander
- Command "VTref" did not always throw errors when invalid configuration was passed. Fixed.
DLL
- Adapted SPIFI FLASH programming algorithms according to improved SPIFI lib.
- Added bootloader FLASH section for EFR32 series devices.
- Added command string "ResetJLink" to reset a J-Link (Currently only available for JLink-OB-SAM3U128-NordicSemi)
- Added command string "SetcJTAGInitMode"
- Added debug support for Renesas RZ/T1 M3 subcore.
- Added debug support for TI AM437X series devices.
- Added ETB trace support for Renesas RZ/T1 M3 subcore.
- Added Flash programming support for LPC55xx series devices.
- Added Flash programming support for Analog ADuCM355 series devices.
- Added Flash programming support for Cypress CY8C6xxA series devices.
- Added Flash programming support for Maxim MAX32665, MAX32666, MAX32667 and MAX32668 series devices.
- Added Flash programming support for Microchip ATSAMR34 and ATSAMR35 series devices.
- Added Flash programming support for Nuvoton NuMicro M2351xxxx series devices.
- Added Flash programming support for ST STM32G0 series devices.
- Added HYPERFLASH programming support for Renesas RZ/A2M series devices.
- Added HYPERFLASH programming support via QSPI for Renesas RZ/A2M series devices.
- Added OCTA FLASH programming support for Renesas RZ/A2M series devices.
- Added option byte programming for MindMotion MM32xxx series devices.
- Added QSPI Flash programming support for Dialog Semiconductor DA14x95 series devices.
- Added QSPI FLASH programming support for Renesas RZ/A2M series devices.
- Added QSPI-Flash programming support for CYW43907 series devices.
- Added read protection and unprotect mechanism for MindMotion MM32xxx series devices.
- Added support for command string "InvalidateCPUState"
- Added support for command string "RestoreDownloadAfterReset"
- Added support for SiFive RISC-V based targets via cJTAG
- Added support for some new Cypress PSoC4 devices.
- Added support for TI PGA900
- Extended support for PW-protected tunnel connections as well as connections to custom tunnel servers
- Fixed connect sequence for Cypress PSoc4 devices.
- Implemented QSPI flash programming support for SiFive FE310
- Implemented support for tunnel connections via custom tunnel server and port
- Implemented support for tunnel connections via nickname
- improved connect sequence for TI AM335x series devices.
- J-Link script files: Added constant JLINK_TIF_MC2WJTAG_TDI
- J-Link script files: Added pseudo variable JLINK_FLASH_DownloadAddr
- J-Link script files: Added pseudo variable JLINK_FLASH_NumBytesDownloaded
- J-Link script files: Added support for API calls SPI2FE_ReadBits() and SPI2FE_WriteBits()
- J-Link script files: Added support for BeforeResetTarget() function
- J-Link script files: Added support for sizeof() operator
- J-Link script files: Comparisons with more than 2 operands did not work properly. Example: if (Addr || Addr1 || Addr2) { ... }. Fixed.
- Memory overlap issue for NXP MKxx series devices, fixed.
- New ST STM32L4xx devices show different IDCODE needed for Flash protection handling. Added IDCODE for L45x and L46x series.
- On some cores which require certain registers to be restored in HW by J-Link on each Go() / Step(), it could happen that some of these registers were not restored correctly. Fixed.
- Renesas RX66T group devices: Added data flash programming support
- Renesas RX66T group devices: Added debugging support for: R5F566TA, R5F566TE, R5F566TF, R5F566TK
- Renesas RX66T group devices: Added program flash programming support
- Sector size of NXP MKV42Fxxx, MKV44Fxxx and MKV46Fxxx devices was incorrect. Fixed.
- SiFive FE310: Reduced time needed for reset from app. 3 seconds to slightly above 1 second (cannot be reduced further because core does not become responsive before that)
- Size of RAM for NXP MK22FX512xxx series devices to 128kB, corrected.
- Some NXP LPC802 / LPC804 passed by IAR EWARM where not accepted by the J-Link DLL. Fixed.
- SPIFI flash programming speed improved by 10 to 15% for certain devices. Affected device series: Microchip SAMV7, Broadcom BCM89107, Marvell MW30x, Maxim MAX3265, NXP LPC18xx, NXP LPC43xx, NXP LPC408x, NXP LPC54xx, Renesas RZ/A1L, Renesas RZ/A1H, Renesas RZ/T1, Renesas Synergy, Xilinx Zynq7000.
- The RAM size of NXP LPC804 devices was incorrect (2 KB instead of 4 KB). Fixed.
- Updated flash programming support for Cypress CY8C6xx6 and CY8C6xx7 series devices.
- Warning "Mis-aligned memory write: ..." printed garbage for <Address> and <NumBytes>. Fixed.
Firmware
- Flasher PORTABLE PLUS: Added stand-alone programming for RX63 MCUs.
- Flasher PORTABLE PLUS: Added universal flash loader support for PIC16 derivatives
- Flasher PRO V4: Added stand-alone programming for RX63 MCUs.
- Flasher PRO V4: Added universal flash loader support for PIC16 derivatives
- J-Link EDU Mini: RISC-V: Added support for cJTAG
- J-Link EDU Mini: RISC-V: Improved timeout handling in case BUSY responses were sent by the debug module interface.
- J-Link EDU/BASE/PLUS V10: Added support for target interface "Microchip 2-wire JTAG via TDI"
- J-Link EDU/BASE/PLUS V10: RISC-V: Added support for cJTAG
- J-Link EDU/BASE/PLUS V10: RISC-V: Improved timeout handling in case BUSY responses were sent by the debug module interface.
- J-Link OB-K22-SiFive: Drag & Drop: Improved error message of FAIL.txt in case a datafile contained addresses that are not in the target's flash range.
- J-Link OB-K22-SiFive: If drag & drop programming failed, the OB always tried an emergency erase of the first sector. This emergency erase has been removed.
- J-Link OB-K22-SiFive: Under special circumstances, drag & drop programming could fail. Fixed.
- J-Link PRO V4: RISC-V: Added support for cJTAG
- J-Link PRO V4: RISC-V: Improved timeout handling in case BUSY responses were sent by the debug module interface.
- J-Link ULTRA+ V4: RISC-V: Added support for cJTAG
- J-Link ULTRA+ V4: RISC-V: Improved timeout handling in case BUSY responses were sent by the debug module interface.
- J-Link-OB-K22-NordicSemi: Under very special circumstances, it could happen that when changing the non-volatile config area of J-Link (e.g. via J-Link Configurator), it could happen that the FW hang. Fixed.
- J-Link-OB-K22-SiFive: Improved MSD drag and drop programming speed
- J-Link-OB-K22-SiFive: Under very special circumstances, it could happen that when changing the non-volatile config area of J-Link (e.g. via J-Link Configurator), it could happen that the FW hang. Fixed.
- PCode support for Firmware_JLink_Lite_XMC4200, added.
GDB Server
- Added double precision floating point registers (to be shown in Eclipse based IDEs like NXP MCUXpresso) for Cortex-M based devices.
J-Flash
- Added support to write to the DEV_RAM on the TI PGA900, if memory remapping is set.
- Corrected some misleading error messages (e.g. "no license" error in case of programming failed).
- Creating data files did not work for specific CFI flash configurations. Fixed.
- Eliminating blank areas failed for bigger images with many blank areas. Fixed.
- Projects using CFI NOR flash crashed on creating Flasher config files. Fixed.
- QN908x was reported as not supported in stand-alone mode. Fixed.
J-Flash SPI
- Added Flash programming support for Adesto ATXP128/ATXP128R SPI FLASH.
- Added Flash programming support for GD25Q32 SPI-FLASH
- Added Flash programming support for GD25Q64 SPI-FLASH
- Added flash programming support for Spansion S25FL128L SPI-FLASH.
- Eliminating blank areas failed for bigger images with many blank areas. Fixed.
Manual
- UM08001: Added information about how to use comand line option "-usb" with SWOViewer_CL.
- UM08001: Added information about how to use SWD multi-drop.
Remote Server
- Added options to connect to a custom tunnel server listening on a custom port
- Added options to identify by name instead of S/N, for tunnel connections
- Added options to protect a tunnel connections with a password
- Updated images for connection status.
RTT
- Added ASM variant for RTT on ARMv7-M (Cortex-M3/M4/M7)
- Added defines for gcc and clang in RTT assembly file for non Embedded Studio setups. Otherwise build errors would pop up.
RTT Client
- Added command line option to enable/ disable local echo: "-LocalEcho <On/Off>".
RTT Viewer
- "unspecified" script file would show a warning. Fixed.
- Fixed parsing of RTT Control block address.
- Set 'All terminals' tab to be selected by default.
SWO Analyzer
- Added auto exit command line option ("-s").
Version V6.40b (2019-01-22)
DLL
- "App nap" feature of macOS caused J-Link communication to break down when having applications with an active J-Link connection napping (e.g. napping was activated by system if application was not in the foreground). Fixed.
- 'Terms of use' dialogs (e.g. for J-Link EDU) could be cut off with bigger text scaling on Windows 10. Fixed.
- Allow security algorithm for NXP S32K1xx series devices, fixed.
- Bug within JLinkScript for ONSemiconductor RSL10 series device, fixed.
- Fixed clock restore settings within programming algorithms for iMXRT105x and iMXRT106x QSPI-FLASH and HyperFLASH series devices.
- Linux: When connecting to a J-Link via its network name and the name resolution failed, a segfault could occur. Fixed.
- macOS: When connecting to a J-Link via its network name and the name resolution failed, a segfault could occur. Fixed.
- Nuvoton series devices Flash programming in case of programming less than 4KB, fixed.
- Size of RAM for NXP MK22FX512xxx series devices to 128kB, corrected.
- Some log outputs for warnings on mis-aligned memory accesses could lead to access violations. Fixed.
- When sampling SWO data between 2 BPs and only a very small amount of SWO data was sent by the target, it could happen that the complete chunk was swallowed. Fixed.
- When stopping SWO (e.g. on a BP hit etc.) on the J-Link side, it could happen that the last SWO data received by J-Link was lost. Fixed.
- When writing zoned memory via J-Link (mainly on 8051 targets), writing of 8-bit or 16-bit items did not work correctly. Fixed.
Firmware
- J-Link EDU Mini: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link EDU/BASE/PLUS V10: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link Lite Cortex-M V9: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link Lite V9: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link PRO V4: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link ULTRA+ V4: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link WiFi V1: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-K22-CortexA: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-K22-CortexM: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-K22-NordicSemi: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-K22-SiFive: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-SAM3U128 V1: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-SAM3U128 V3: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-SAM3U128-NordicSemi: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-STM32F072-128KB-CortexM: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-STM32F072-CortexAR: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-STM32F072-CortexM: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-STM32F103: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
- J-Link-OB-XMC4200: VCOM: Under special circumstances, J-Link used an incorrect baud rate. Fixed. (Mainly happened under macOS and Linux when the host PC set the baud rate twice: Once the default one, then the user configured one, on COM port open)
RTT
- Assembler variant for Cortex-M did not behave correctly when writing into the ring buffer, around the corner. Fixed.
RTT Viewer
- 'Attach'-mode reconnecting did not work. Fixed.
- Fixed message box and dialog positioning.
- Multiple spaces could be summarized to a single space. Fixed.
- Removed redundant line breaks.
Version V6.40a (2018-12-11)
DLL
- Made support for Nordic Semi nRF91 series devices public
- Made support for NXP LPC55 series devices public
- Made support for ST STM32G0 series devices public
Version V6.40 (2018-10-26)
DLL
- Added command string "JLinkMemAccMapXMLPath" to specify a memory access map file that specifies how to access memory while the CPU is running / halted, to override the default behavior also in IDEs that do not know about different access types.
- Added debugging support for Mediatek MT2523D, MT2523G, MT2523S series devices
- Added error message in case command string "JLinkDevicesXMLPath" selected a non-existent J-Link device XML file.
- Added error message in case command string "ScriptFile" selected a non-existent J-Link script file.
- Added FLASH programming support for Maxim MAX32660 series devices.
- Added Flash programming support for MindMotion MM32F103xx and MM32F031xxx series devices.
- Added Flash programming support for MindMotion MM32L05xxx, MM32L06xxx and MM32L07xxx series devices.
- Added in-package QSPI programming support for Mediatek MT2523D, MT2523G, MT2523S series devices
- Added missing device alias "XMC1402-T038x0200"
- Added QSPI Flash programming support for MediaTek MT7697 series devices.
- Added QSPI Flash programming support for STM32F413xx series devices.
- Added QSPI Flash programming support for STM32L476xx series devices.
- Added QSPI Flash programming support for STM32L496xx series devices.
- Added QSPI Flash programming support for STM32L4R9xx series devices.
- Added QSPI-Flash programming support for NXP i.MX RT1064 series devices.
- Added support for FPGA timestamps.
- Added support for Renesas RAA305350GBM (Cortex-M0+, 48 KB flash)
- Added support for SiFive FE310 QSPI programming
- Allow J-Link script file to overwrite selective functions of internal script.
- For Microchip ATSAML21 secured device has been detected erroneously during connect, fixed.
- Infineon TLE98xx series devices: Improved connect sequence so that wild running devices that reject a debug connection due to bad code, can get under control again.
- J-Link script files: Added support for structures
- J-Link script files: By accident a variable could be defined multiple times with different declarations. Fixed.
- OpenSDA on Mediatek LinkIt 2523 board could not be used. Fixed.
- Renesas Synergy S7 series: When trying to issue a blank check on data flash, an error was thrown. Fixed.
- RISC-V: Reset failed on SiFive FE310 target device (Could also cause debug session to fail after reset). Fixed.
- RISC-V: Under special circumstances it could happen that J-Link reported incorrect CPU register values after issuing a reset. Fixed.
- RISC-V: When halting the target core and then physically disconnecting J-Link, a reset button push etc. did not restart the target application. Fixed.
- SPIFI flash programming: Added support for Microchip SST26VF016B, SST26VF032B, SST26VF064B
- Trace init for NXP Kinetis devices possibly disabled other peripherals. Fixed.
- Trace: When using streaming trace and having J-Trace connected via IP, the J-Link software did not use the dedicated streaming channel by default but the main IP connection instead (way less throughput). This could cause trace buffer overflows. Fixed.
- XML parser for JLinkDeviceList.xml etc. threw an error if empty tags have been used (e.g. <Test></Test>). Fixed.
Firmware
- Added official support for J-Link-OB-K22-NordicSemi
- Flasher Portable PLUS: When running on battery, auto power off time can be configured.
- J-Link EDU Mini: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- J-Link EDU Mini: RISC-V: If core did not respond to halt request immediately (but needed a few ms), it could happen that J-Link reported an error while halting the core. Fixed.
- J-Link EDU Mini: RISC-V: Under very special circumstances, sometimes a "power up request" to the debug unit of the core was "swallowed", resulting in a connection failure. Fixed.
- J-Link EDU Mini: RISC-V: When working on a slow running core, J-Link did not catch timeout errors when reading/writing DMI registers properly. Fixed.
- J-Link EDU Mini: RISC-V: When working on a slow running core, J-Link did not repeat DMI accesses correctly if busy state was received. Fixed.
- J-Link EDU/BASE/PLUS V10: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: If core did not respond to halt request immediately (but needed a few ms), it could happen that J-Link reported an error while halting the core. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: Under very special circumstances, sometimes a "power up request" to the debug unit of the core was "swallowed", resulting in a connection failure. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: When working on a slow running core, J-Link did not catch timeout errors when reading/writing DMI registers properly. Fixed.
- J-Link EDU/BASE/PLUS V10: RISC-V: When working on a slow running core, J-Link did not repeat DMI accesses correctly if busy state was received. Fixed.
- J-Link EDU/BASE/PLUS V9: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- J-Link PRO V4: Added support for SEGGER FIND extension with optional MAC filter
- J-Link PRO V4: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- J-Link PRO V4: RISC-V: If core did not respond to halt request immediately (but needed a few ms), it could happen that J-Link reported an error while halting the core. Fixed.
- J-Link PRO V4: RISC-V: Under very special circumstances, sometimes a "power up request" to the debug unit of the core was "swallowed", resulting in a connection failure. Fixed.
- J-Link PRO V4: RISC-V: When working on a slow running core, J-Link did not catch timeout errors when reading/writing DMI registers properly. Fixed.
- J-Link PRO V4: RISC-V: When working on a slow running core, J-Link did not repeat DMI accesses correctly if busy state was received. Fixed.
- J-Link ULTRA+ V4: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- J-Link ULTRA+ V4: RISC-V: If core did not respond to halt request immediately (but needed a few ms), it could happen that J-Link reported an error while halting the core. Fixed.
- J-Link ULTRA+ V4: RISC-V: Under very special circumstances, sometimes a "power up request" to the debug unit of the core was "swallowed", resulting in a connection failure. Fixed.
- J-Link ULTRA+ V4: RISC-V: When working on a slow running core, J-Link did not catch timeout errors when reading/writing DMI registers properly. Fixed.
- J-Link ULTRA+ V4: RISC-V: When working on a slow running core, J-Link did not repeat DMI accesses correctly if busy state was received. Fixed.
- J-Link-OB-K22-CortexM: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- J-Link-OB-K22-SiFive: Drag and drop programming did not correctly reset + start the CPU core after programming. Fixed.
- J-Link-OB-K22-SiFive: Drag and drop programming did not work properly for files > 256 bytes. Fixed.
- J-Trace PRO V1 Cortex-M: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- J-Trace PRO V2 Cortex-M: Added support for SEGGER FIND extension with optional MAC filter
- J-Trace PRO V2 Cortex-M: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- J-Trace PRO V2 Cortex: Added support for SEGGER FIND extension with optional MAC filter
- J-Trace PRO V2 Cortex: Background operations like RTT were not temporarily stopped correctly if a 2nd instance issued a connect. This for example could cause problems when running SystemView in parallel to Embedded Studio. Fixed.
- OpenSDA: Uploaded fixed firmware images More info: https://www.segger.com/products/debug-probes/j-link/models/other-j-links/opensda-sda-v2/#firmware-version-history-and-limitations
GDB Server
- Added monitor command "flash erase"
J-Flash
- Added option to disable skipping of blank data on programming.
- Added support for SiFive FE310 QSPI programming
- Flashers could not be configured for SAMD5x devices in stand-alone-mode. Fixed.
- Focusing on the first element in the general options dialog did not work. Fixed.
- J-Link firmware version now showed in log output
- Reduced startup time from ~650ms to < 15ms to speed up mass production where J-Flash is started via batch processing for each device.
- Renesas Synergy S7 series: When trying to issue a blank check on data flash, an error was thrown. Fixed.
J-Flash SPI
- Added interface speed options 100kHz, 200kHz, 500kHz and 750kHz for selection.
- Added programming support for SPI Flash Microchip SST26VF064B.
- Added support for -min command line option (to start application minimized)
J-Link Package
- Linux: Updated rules file to support J-Links that enumerate as multi VCOM devices
J-Link Script Files
- Initialization of static variables was not possible with the complete variable size (e.g. initializing an U8 variable with values > 127 failed). Fixed.
- Under special circumstances, expressions like a = Test | (Test + b); could lead to faulty behavior. Fixed.
Manual
- UM08001: Chapter "Target interfaces and adapters": Section "19-pin JTAG/SWD and Trace connector": Added information about pitch of connector.
SWO Viewer
- When SWOViewer was launched with CL options and another connection to the target device was already active e.g. debug session in IDE, SWOViewer would crash. Fixed.
SWO Viewer CL
- When SWOViewer was launched with CL options and another connection to the target device was already active e.g. debug session in IDE, SWOViewer would crash. Fixed.
Trace
- Added StartETM/StopETM JLinkScript file functions to be able to replace internal generic trace related ETM initialization.
- Added StartPTM/StopPTM JLinkScript file functions to be able to replace internal generic trace related PTM initialization.
- Added StartTF/StopTF JLinkScript file functions to be able to replace internal generic trace related TF initialization.
- Added StartTMC/StopTMC JLinkScript file functions to be able to replace internal generic trace related TMC initialization.
- Added StartTPIU/StopTPIU JLinkScript file functions to be able to replace internal generic trace related TPIU initialization.
Version V6.34h (2018-10-09)
DLL
- QSPI flash programming support for Cypress S25FL256L fixed.
- Reset for Analog Devices ADUCM32x series devices did not work properly. Fixed.
- Selecting "auto" for JTAG speed could fail for new Cortex-M33 based devices. Fixed.
- ST STM32F2xxx and F4xxx series devices: If SYSCFG unit mapped external memory to addr. 0x0, it could happen that J-Link accessed internal flash by accident. Fixed.
- Windows: When flash programming dialog was shown from EmbeddedStudio, characters could be cut off. Fixed.
J-Flash
- Analog Devices ADUCM32x series: Default projects issuing a reset at the beginning failed and caused RAMCode timeout messages. Fixed.
RTT Viewer
- 'All terminals' displayed redundant line breaks. Fixed.
- Sending data to target could lead to crash. Fixed.
Version V6.34g (2018-09-26)
DLL
- Internal MRU handling of J-Link software could lead to a buffer overflow if MRU contained entries of 253 - 256 bytes in size. Fixed.
- Livetrace did not work properly under special circumstances. Fixed.
- Microchip ATSAME51J20 was not selectable by accident. Fixed.
- Page "RawTrace" in control panel did not work when using livetrace. Fixed.
- When trying to programming a Microchip ATSAM4S device that has a wrongly configured flash controller/clock and did not respond correctly, it could happen that the J-Link software ended up in an endless loop. Fixed.
RTT Viewer
- 'Attach' mode did not work correctly. Fixed.
- Newlines were not handled correctly. Fixed.
- Sending RTT data to target did not work correctly. Fixed.
Version V6.34f (2018-09-05)
Control Panel
- Did only show VUSB and VTref if 5V target power supply output of J-Link was enabled. Fixed.
DLL
- ITM timestamps for ETMv3 / ETMv4 trace did not work properly. Fixed.
- Some Cypress aliases where not accepted as valid device names. Fixed. Aliases added: CY8C4125LQA-S423, CY8C4146LQA-S423, CY8C4124LQS-S423, CY8C4125LQS-S423, CY8C4146LQS-S423, CY8C4124LQE-S423, CY8C4125LQE-S423, CY8C4146LQE-S423, CY8C4146AZI-S443, CY8C4146AZI-S453, CY8C4146AZI-S463, CY8C4127AZI-S443, CY8C4127AZI-S453, CY8C4147AZI-S443, CY8C4147AZI-S453, CY8C4147AZI-S463, CY8C4146AZQ-S445, CY8C4146AZQ-S455, CY8C4127AZQ-S445, CY8C4147AZQ-S445, CY8C4127AZQ-S455, CY8C4147AZQ-S455, CY8C4147AZQ-S465, CY8C4147AZQ-S475
- Trace on Cortex-M3/M4 did not work with IAR EWARM. Fixed.
Firmware
- J-Link V10: Firmware did not transfer VUSB and VTref values for control panel to J-Link PC software. Fixed.
- J-Trace PRO V2 Cortex-M: Firmware did not transfer VUSB and VTref values for control panel to J-Link PC software. Fixed.
- J-Trace PRO V2 Cortex: Firmware did not transfer VUSB and VTref values for control panel to J-Link PC software. Fixed.
Remote Server
- Unknown command errors were thrown when trying to debug a RISC-V based target. Fixed.
Version V6.34e (2018-08-30)
DLL
- Error check for devices XML file could trigger false alarms. Introduced in V6.34d. Fixed.
Version V6.34d (2018-08-30)
DLL
- Added error output in case a specified J-Link devices XML file could not be found
- Added error output in case a specified J-Link script file could not be found
- Broken command string support made flash programming on i.MX7ULP devices not working in IAR EWARM V8.30. Fixed.
- Some command strings did not work correctly with paths that contain spaces but no quotation marks (worked in earlier versions). Introduced in V6.34. Fixed. Affected command strings: "JLinkDevicesXMLPath", "ProjectFile", "ScriptFile", "HSSLogFile", "JLinkLogFile"
DLL Updater
- S32 Design Studio for ARM by NXP was not found by updater. Fixed.
Firmware
- Overcurrent detection did not work properly (Introduced in V6.34). Fixed. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4
RTT
- Made SEGGER_RTT_vprintf() public in SEGGER_RTT.h
Version V6.34c (2018-08-23)
Commander
- Commands "testwspeed" and "testrspeed" did not show speed correctly (Introduced in V6.34). Fixed.
DLL
- Added command string "SetInitWorkRAMOnConnect"
- NXP S32K116 series: Flash programming did not work correctly if internal ECC RAM was not initialized. Fixed.
Firmware
- When using J-Flash SPI in a VM or on slow host PCs, it could happen that verify failed even though the data in the SPI flash was correct. Fixed. Affected firmwares: J-Link BASE/PLUS/EDU V9, J-Link BASE/PLUS/EDU V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Link EDU Mini, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, Flasher ARM/PRO V4
GDB Server
- Under special circumstances it could happen that GDB Server crashed when reading FPU registers of ARM9 targets (Introduced with V6.34). Fixed.
J-Flash
- Log output from J-Link and script files was swallowed and not shown in log window. Fixed.
JTAG Load
- For SDR/SIR commands with less than 8 bits it could happen that the error message ""TDO data is larger than specified number of bits in SDR command" was thrown. Fixed.
- If the first transmission statement was "STATE RESET;" it could happen that J-Link output too many bits. Fixed.
- Under special circumstances, the statement "FREQUENCY" did not result in a change of the frequency. Fixed.
Version V6.34b (2018-08-13)
Commander
- Selecting a target interface by number did not work. Fixed.
DLL
- Change regarding "default AHB-AP configuration" from V6.34 caused problems on some Cortex-M23 / M33 devices (e.g. Microchip SAML11). Fixed.
- TI CC26xx series: Flash programming was very slow. Fixed.
RTT
- SEGGER_RTT_Syscalls_IAR.c could throw a warning under IAR EWARM V8 and later. Fixed.
Version V6.34a (2018-08-08)
DLL
- J-Link script files: When using pseudo variables in a leaf function, it could happen that stack got corrupted. Fixed.
- Some Infineon XMC1302 device aliases used by Infineon DAVE IDE were not recognized correctly. Fixed.
GDB Server
- Atollic/ST TrueSTUDIO: Under special circumstances starting a debug session could fail because GDB Server has sent an incorrectly formatted GDB packet. Introduced with V6.34. Fixed.
- Command line parameter "-log" did not work correctly. Introduced with V6.34. Fixed.
- Command line parameters passed after "-LocalHostOnly" could lead to a command line parse error. Fixed.
- GUI version showed incorrect command line for "-select USB" and "-select IP". Fixed.
- Last device in device list was not shown. Fixed.
J-Flash Lite
- Last device in device list was not shown. Fixed.
RTT Viewer
- Last device in device list was not shown. Fixed.
Version V6.34 (2018-08-07)
CCS Plugin
- TI MSP432P401R: Under special circumstances, a debug session could not be started. Fixed.
Commander
- When selecting a hidden device, the erase command caused a crash. Fixed.
DLL
- Added alias for Flash at address 0x00000000 and fixed unsecure for Zilog Z32F0xx3 devices.
- Added command strings "CORESIGHT_SetMTBUseAddr" and "CORESIGHT_SetMTBBufUsageSize" to allow more customization of MTB buffer usage. See https://wiki.segger.com/MTB_specifics
- Added Flash programming support for Nuvoton Mini57 series devices.
- Added Flash programming support for Nuvoton Nano103xx, NUC121xx, NUC125xx, NUC126xx, M0564xx series devices.
- Added Flash programming support for Nuvoton NuMicro M0518xx series devices.
- Added Flash programming support for Nuvoton NuMicro M48x series devices.
- Added Flash programming support to Holtek HT32F52xxx series devices, including option bytes.
- Added FlexNVM flash programming support for NXP KE14Z and KE15Z devices.
- Added ITM timestamp support for ETMv3 trace (Cortex-M3, M4).
- Added ITM timestamp support for ETMv4 trace (Cortex-M7).
- Added native unlock support for STM32H7xx series devices.
- Added optional D-Flash programming support for NXP S32K1xx devices.
- Added QSPI Flash support for Adesto ATXP032/ATXP032R flash on NXP iMXRT1052
- Added QSPI-Flash programming support for NXP i.MX RT106x series devices.
- Added QSPI-Flash support for STM32F412xx series devices
- Added QSPI-Flash support for STM32F723xx series devices
- Added RWW section (EEPROM) flash programming support for Atmel (Microchip) SAMC20 and SAMC21 devices.
- Added support for new Cypress devices: CY8C4547xxx series, CY8C4724xxx-Sxxx series, CY8C4725xxx-Sxxx series, CY8C4744xxx-Sxxx series, CY8C4745xxx-Sxxx series
- Changed default AHB-AP configuration (CSW [30] was cleared so far, now set) used by J-Link for Cortex-M devices because it could be problematic with some very special devices.
- In case Embedded Studio performed downloads to non-supported flash banks, it could happen that no error was returned by J-Link. Fixed.
- Optimization of Flash programming for Nuvoton NuMicro M0564xx, M48x and NUC126xx series devices
- Optimized programming page size for STM32F412G Disco QSPI
- QSPI Flash support for SPI flashes with different supply voltages (1.8V - 3.3V) added to Xilinx Zynq 70xx series devices.
- RAM size for Zilog Z32F0642 device, fixed.
- Renesas S5D3: Erase using J-Link Commander did not work. Fixed.
- Renesas S5D5 family: Added option-setting memory programming support
- Some Cypress PSoC4 and PSoC5 devices were not detected by the J-Link software. Fixed.
- Some Infineon XMC1302 device names were not recognized by the J-Link software. Fixed.
- ST STM32L4 family: For some devices, incorrect RAM sizes were used by the J-Link DLL resulted in errors during flash programming. Fixed.
- Trace: Added support for ITM timestamps on Cortex-M3/M4 targets
- Trace: Added support for ITM timestamps on Cortex-M7 targets
- Under special circumstances, flash programming failed in QSPI setups with IS25LP512M as SPI flash (e.g. Renesas R7S721000 + IS25LP512M). Fixed.
- Unlock of read protection for Zilog Z32F0323 and Z32F0643 series devices. Fixed.
- Unprotect of Flash blocks for Adesto ATXP032/ATXP032R Flash added.
- Updated USB modules to support J-Links that enumerate as multi VCOM devices
Firmware
- Improved POWERTRACE sampling used by "Power Graph" in SEGGER Ozone. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4
GDB Server
- When passing a command line with a specific J-Link S/N and in the next session passing a command line without a J-Link S/N specification, the S/N from the old session was used by J-Link GDB Server. Fixed.
J-Flash
- Added support for new Cypress devices: CY8C4547xxx series, CY8C4724xxx-Sxxx series, CY8C4725xxx-Sxxx series, CY8C4744xxx-Sxxx series, CY8C4745xxx-Sxxx series
J-Flash SPI
- Added FLASH programming support for Adesto ATXP032/ATXP032R, also added automatic unprotect of flash blocks in case of FLASH erase or FLASH write.
- Added FLASH programming support for Cypress S25FL256L
- Added new SPI flashes (MX66UM1G45G, MX66UM1G45G, MX25UM51245G, MX25L3225D, MX25R3235F, W25Q64FW, W25Q64JV)
- Wrong flash size reported for Spansion S25FL128SAGN, S25FL256SAIF. Fixed.
J-Flash SPI CL
- Linux/macOS: Renamed executable to match standard naming scheme. Symlinks for backward compatibility have been added
J-Link Package
- Windows: Updated USB driver installer to support J-Links that enumerate as multi VCOM devices
RTT Client
- Linux/macOS: Renamed executable to match standard naming scheme. Symlinks for backward compatibility have been added
RTT Logger
- Linux/macOS: Renamed executable to match standard naming scheme. Symlinks for backward compatibility have been added
STM32 Utility
- Linux/macOS: Renamed executable to match standard naming scheme. Symlinks for backward compatibility have been added
SWO Viewer
- Under certain circumstances when pressing Measure the measured value was not updated in the GUI. Fixed.
SWO Viewer CL
- Improved handling of -device and -cpufreq CL parameters and edited console output accordingly.
- Linux/macOS: Renamed executable to match standard naming scheme. Symlinks for backward compatibility have been added
Version V6.32i (2018-07-24)
DLL
- J-Link-OB-BBC-micro:bit: Error message "The connected J-Link is low on memory" could occur, even if the current connection to J-Link was the only one. Fixed.
- J-Link-OB-XMC4200: When connecting to an Infineon XMC1xxx series device, the error message "Firmware of connected J-Link [...] is too old" could appear. Fixed.
- Linux: On Linux distributions where the ModemManager daemon is enabled by default, it could happen that as soon as a J-Link VCOM device has enumerated, the host started sending data to the target device which could confuse the target application. Fixed.
- RAM size for Xilinx Zynq 70xx series devices, fixed.
- Tracing via MTB: If the target application called subroutines via BL <Imm> instructions, it could happen that the subroutine call was shown twice in a row in the instruction trace. Fixed.
- When using "tracing via buffer" in Ozone and the target populated MTB instead of an ETB, the error message "ETB selected as trace source, but current device does not have an ETB." could occur. Fixed.
- When using an open flashloader from Keil for the STM32F7xxx ITCM flash address space, a J-Link API error ("MEM_MAP_AddRegion(): Function called with start address greater than end address") could occur. Fixed.
Firmware
- On Renesas RX651 / RX65N based devices it could happen that error message "CPU register 0 is already marked as valid" appeared. Fixed. Affected firmwares: Flasher PRO V4, Flasher Portable PLUS, Flasher RX V4
- Under very special circumstances it could happen that VCOM Tx (PC -> Target) did not work correctly and J-Link did not send the data to the target. Fixed. Affected firmwares: JLink-OB-SAM3U128 V1, JLink-OB-SAM3U128 V3, JLink-OB-SAM3U128-NordicSemi
J-Flash
- Downloading large data files to a Flasher via USB could cause a communication timeout. Fixed.
- When using an open flashloader from Keil for the STM32F7xxx ITCM flash address space, a J-Link API error ("MEM_MAP_AddRegion(): Function called with start address greater than end address") could occur. Fixed.
J-Flash SPI CL
- Device was not programmed correctly in auto mode, if pages in an affected sector remained unchanged.
Version V6.32h (2018-07-05)
Commander
- Improved output of memory zones
- Selecting the core index through the device selection dialog did not work. Fixed.
DLL
- Cortex-M23/M33: Detection of CoreSight components did not work properly (e.g. different components were identified as identical ones by mistake). Fixed.
- For current J-Trace PRO revisions which support streaming trace via USB3, it could happen that the warning "For max. trace throughput, please connect J-Trace via IP" appeared. Fixed.
- Improved script language. Now also supported: __constant U32 xxx = <__constantU32> + <Imm>;, __constant U32 xxx = <__constantU32> + <__constantU32>;, static U32 xxx = <Imm>;, static U32 xxx = <__constantU32>;, static const char* xxx = <sLit>;
- J-Link Lite FSL: When having multiple of these J-Links connected, connection dialogs have shown the same S/N (2147483647) for all of them. Fixed.
- Loading JLinkDevices.xml from DLL directory failed if DLL was located on a network drive. Fixed.
- OpenSDA running J-Link firmware could not be used with NXP devices like i.MXRT1052 (J-Link software complained about silicon vendor limit of OpenSDA). Fixed.
- Renesas S5D9 series: Erasing option-setting memory did not work properly. Fixed.
- Script files When using static const U8/U16 *, only 8/16-bit were allocated for variable, not 32-bit. Fixed.
- Script files When using static variables, it was not made sure that variables were positioned aligned in memory. Fixed.
- Under certain circumstances MTB addresses set by user were reset for Cortex-M33 target devices. Fixed.
- Under special circumstances, memory zones for Cortex-A/R devices were not shown correctly in Ozone. Fixed.
- Unknown ELF file types (other than executable files, object files, ...) could cause a crash in the ELF analyzer logic. Fixed.
- Unsecuring a TI CC25xx or CC26xx device could fail. Fixed.
Firmware
- VCOM: It could happen that on a COM port open the J-Link internal "hardware flow control in use" detection was not reset properly. Fixed. Affected firmwares: JLink-OB-SAM3U128-NordicSemi
- When selecting specific interface speeds and the initial connect via SWD interface failed, it could happen that the J-Link firmware hang and USB timeouts occurred when the DLL tried the fallback connect method. Fixed. Affected firmwares: JLink-OB-SAM3U128 V1, JLink-OB-SAM3U128 V3, JLink-OB-SAM3U128-NordicSemi
J-Flash
- Connecting to Infineon XMC1xxx series devices with SWD interface could fail with error "invalid core ID read", even though the connection was fine. Fixed. Affected firmwares: J-Link BASE/PLUS/EDU V10
- J-Flash did not return in error in case of flash information could not be determined. Fixed.
- Renesas S5D9 series: Erasing option-setting memory did not work properly. Fixed.
- Unknown ELF file types (other than executable files, object files, ...) could cause a crash in the ELF analyzer logic. Fixed.
Manual
- UM08001: Added description of J-Flash Lite to manual
RTT Viewer
- If sending input fails, application could get stuck in a loop. Fixed.
Version V6.32g (2018-06-15)
DLL
- Under certain circumstances flashing to address 0x0 on ST STM32L476 device series failed. Fixed.
DLL Updater
- Atollic TrueSTUDIO versions 9.0.0 and later were not found by updater. Fixed.
Firmware
- Flasher stand-alone support for PPC: Under very special circumstances, Flasher tried to halt the core when already halted, which caused the core logic to hang. Fixed. Affected firmwares: Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4
Version V6.32f (2018-06-12)
DLL
- Access violation could happen if DLL was opened / closed multiple times without unloading it from memory in between (Introduced in V6.32e, V6.33d (beta)). Fixed.
- Renesas S124: Under special circumstances (Flash Access Window configured), erase did not work. Fixed.
- When initializing Trace pins for ST STM32F1 series devices registers could be written that are not available. Fixed.
Version V6.32e (2018-06-08)
DLL
- Atmel SAMV7: Under special circumstances, the programmed application did not boot after flash programming. Fixed.
- For pin reset, the delay after reset setting was not taken into account for Cortex-M SWD / JTAG devices. Fixed.
- For pin reset, the delay after reset setting was not taken into account for Cortex-M SWD / JTAG devices. Fixed.
- Improved startup time (DLL open -> selecting device -> selecting TIF -> selecting TIF speed) reduced by 174ms (76%, in VMs the absolute time may be even more than 174ms)
Firmware
- JTAG: Under special circumstances, glitches on TDI and TMS lines could happen at the start of a sequence, before the first falling edge on TCK was output. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
- JTAG: Under special circumstances, the last clock (TCK) of a JTAG sequence could look like a glitch because it did not have a 50% duty cycle. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
GDB Server
- Memory leak occurred when streaming trace feature (qSeggerSTRACE:GetInstStats: command) was used, e.g. in VisualGDB. Fixed.
SWO Viewer
- When using JLinkSWOViewer with another software e.g. an IDE the JLinkSWOViewer would crash under certain circumstances. Fixed.
Version V6.32d (2018-05-25)
Commander
- Under certain circumstances command "power on" did not show any warning if command is not supported by debug probe. Fixed.
DLL
- NXP iMXRT1021: "MIMXRT1021xxx4A" and "MIMXRT1021xxx5A" were not accepted by the J-Link DLL but passed by some IDEs. Fixed.
- Renesas RX devices: If RX based devices were running very slow, it could happen that debug operations timed out when using JTAG interface (does not happen with FINE) with speeds of 1 MHz, 2 MHz or 4 MHz. Fixed. Affected RX cores: RX630/631/63N, RX64M, RX65N
- Streaming trace: When having a flash based project that also contained some __ramfunc functions, trace statistics for __ramfunc functions were incorrect. Fixed.
- SWO: Under certain circumstances SWO support for NXP LPC5460x device series did not work. Fixed.
- TI CC3220: We did not perform a reset for this family. Fixed.
- Under certain circumstances J-Link Scriptfiles could timeout after 2 seconds. Introduced with V6.32b. Fixed.
- When using the auto-detection feature of the RTT control block and having a slow running device (e.g. Renesas RX64M @ 120 kHz after reset), searching the RTT block could significantly slow down the debug session. Fixed.
DLL Updater
- If more than 128 applications to update were installed, not all instances were found. Fixed.
- Under certain circumstances, the DLL Updated did not update the J-Link DLL's altough it was told to update them. Fixed.
Firmware
- Added support for RX65N (JTAG) in stand-alone mode. Affected firmwares: Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher RX V4
- Improved error handling in case a device is not supported in stand-alone mode but J-Flash only. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
- Renesas RX devices: If RX based devices were running very slow, it could happen that debug operations timed out when using JTAG interface (does not happen with FINE) with speeds of 1 MHz, 2 MHz or 4 MHz. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher RX V4
J-Flash
- Erroneously, Cortex-A53 and Cortex-A57 could be selected as core in J-Flash. Fixed.
- Improved error handling if a Flasher CFG file should be generated for a configuration that is not supported in stand-alone mode.
- When using very long path names for files (> 256 characters), the error "CMDLINE_GetString: String to long" could be triggered. Fixed.
Remote Server
- Error "Unknown EMU command #28 received" could occur. Fixed.
RTT
- When using the auto-detection feature of the RTT control block and having a slow running device (e.g. Renesas RX64M @ 120 kHz after reset), searching the RTT block could significantly slow down the debug session. Fixed.
SWO Viewer
- Under certain circumstances command line options were not applied correctly. Fixed.
- Under certain circumstances selected SWO clock was shown as 0 Hz. Fixed.
Version V6.32c (2018-05-11)
DLL
- Stand-alone-mode programming of LPC546xx series devices failed. Fixed.
Version V6.32b (2018-05-08)
DLL
- Added CORESIGHT_SetTPIUBaseAddr exec command.
- Infineon TLE986x/TLE987x: Added support for data flash and fixed two bugs in the algorithm.
- NXP iMXRT105x (HyperFlash): Under special circumstances, a debug session could not be started successfully. Fixed.
- NXP LPC54018: The J-Link flashloader did not restore some clock register. Fixed.
- NXP LPC802 / LPC804 / LPC845: Under special circumstances (empty was empty before programming), debug session could not be started properly. Fixed.
- NXP LPC804: Erase of the last sector did not work. Fixed.
- NXP LPC845: Reset did not work properly. Fixed.
- Under special circumstances, it could happen that a SYS_Sleep() in a J-Link script file could lead to an endless loop. Fixed.
- Under special circumstances, Keil MDKs could crash when using TCP/IP as host interface. Fixed.
GDB Server
- GUI version was not correctly updated on target state change (halted -> executing). Fixed.
- Improved stability of the RTOS plug-ins.
J-Flash
- NXP iMX7D: J-Flash did not support the entire 256 MB QSPI flash section but 64 MB, only. Fixed.
RTT
- Wrong pointer type in function SEGGER_RTT_HasDataUp. Fixed.
Version V6.32a (2018-04-30)
DLL
- Erase/Write of option bytes for Renesas S3A7 boards fixed.
- SPIFI / QSPI algorithms: Flash programming did not work when the Complement Protect bit (CMP) was set. Fixed.
- When using an old J-Link with Keil MDK-ARM and Cortex-R4 based devices, the error message "The connected J-Link does not support the requested memory access (Flags = 02000000)". Fixed.
Firmware
- The GUI did not work properly when using batch mode programming. Fixed. Affected firmwares: Flasher Portable PLUS
GDB Server
- Command line option -log did not work properly for GUI version of GDB Server (Introduced in V6.30). Fixed.
- Debug session could fail with error message "Remote failure reply: ..." if R0 of the target CPU contained "Ex" in the lowest byte of the register value. Introduced in V6.30k. Fixed.
J-Flash
- Improved error handling when an invalid J-Flash project configuration was downloaded to the Flasher.
- On devices with small sectors (e.g. 128 byte sectors), it could happen that *.DAT files generated for Flasher stand-alone operation had significant overhead in size. Fixed.
Registration
- Some GUI updates for checkbox states could trigger some unwanted events that could interfere with specified command line options. Fixed.
Remote Server
- Some GUI updates for checkbox states could trigger some unwanted events that could interfere with specified command line options. Fixed.
Version V6.32 (2018-04-20)
Commander
- Added new command "IsHalted" which can be used to receive the current CPU state.
- NXP LPC540xx: QSPI could not be erased because banks was not marked as "always present". Fixed. As these devices do not provide internal flash, but QSPI only, we can mark this bank as always present.
- VTref is now shown with additional information if "fixed VTref" is active.
Configurator
- A crash could happen when hitting "Update firmware of selected emulators" but not having any emulators selected. Fixed.
DLL
- Added API functions: JLINK_ReadMemZonedU32(), JLINK_ReadMemZonedU16(), JLINK_WriteZonedU32(), JLINK_WriteZonedU16()
- Added command string "MemPreserveOnReset" to specify memory areas that need to be preserved + restored across resets
- Added flash programming support for Cypress CY8C4125xxx-PSxxx and CY8C4145xxx-PSxxx series devices.
- Added flash programming support for Cypress CYBLE-014008-00, CYBLE-022001-00 and CYBLE-214009-00 series devices.
- Added flash programming support for Maxim MAX32552 series devices.
- Added flash programming support for Microchip ATSAMHA0E / ATSAMHA0G series devices.
- Added flash programming support for Microchip PIC32MX170F512H series devices.
- Added flash programming support for NXP Kinetis K27FA (MK27FN2M0Axxx15) and K28FA (MK28FN2M0Axxx15).
- Added flash programming support for NXP LPC804 series devices.
- Added flash programming support for Silicon Labs EFM32TG11BxxxF64 and EFM32TG11BxxxF128 series devices.
- Added flash programming support for Silicon Labs EFR32MG14PxxxF256, EFR32BG14PxxxF256 and EFR32FG14PxxxF256 series devices.
- Added flash programming support for ST "STM32L442KC" series devices.
- Added flash programming support for TI CC3220xx devices
- Added PCode/script file functions JLINK_MEM_Preserve(), JLINK_MEM_Restore(), JLINK_MEM_Fill()
- Added programming support for internal flash of GigaDevice GD32F1xx, GD32F2xx, GD32F3xx and GD32F4xx series.
- Added programming support for ST STM32F2xxx Option Bytes.
- Added Scriptfile function SWO_EnableTarget() for non generic SWO configurations.
- Added SPI / SPIFI (QSPI) support for Eon EN25QH64 SPI flash.
- Added SPI / SPIFI (QSPI) support for Macronix MX25R3235F, MX25L6433F and MX25R4035F SPI flashes.
- Added support for accessing memory via different zones/methods (e.g. AHB-AP, APB-AP, ... on Cortex-A/R, to allow live updates). Will be used in future SEGGER Ozone versions.
- Added support for RISC-V with V0.11 (legacy) debug interface.
- Calls to JLINK_STRACE_GetInstStats() were not thread safe (other API functions could be called in parallel, messing up DLL internal status data). Fixed.
- Debugging on NXP LPC54S0xx devices did not work. Fixed.
- Improved debugging on NXP LPC540xx devices.
- NXP iMX7D: Added QSPI flash programming support.
- NXP iMXRT1051 / iMXRT1052: Added HyperFlash flash programming support.
- NXP iMXRT1051 / iMXRT1052: Added QSPI flash programming support.
- NXP iMXRT1051 / iMXRT1052: Changed device names to more generic ones (MIMXRT1051xxxxA, MIMXRT1052xxxxA, MIMXRT1051xxxxB and MIMXRT1052xxxxB.
- Open flash loader did not work correctly (DLL could complain about not finding some symbols in the ELF file). Introduced with V6.30i (release) and V6.31f (beta). Fixed.
- Renamed Scriptfile function GetSWOBaseClock() to SWO_GetSWOBaseClock().
- Silicon Labs EFM32GG11Bxx devices and bootloader flash added, also for EFM32TG11BxxxF64 and EFM32TG11BxxxF128
- Writing to memory via zones could write wrong data. Fixed.
Firmware
- Configuring fixed VTref of <= 1.2V was not catched and ignored properly. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex
- Flasher: Downloading the config & data file to the Flasher did not work when the project contained a CFI auto-detect flash bank. Fixed.
- Flasher: Silicon Labs EFM32 / EFR32 devices: Flasher did not support programming of secured devices in stand-alone mode. Fixed.
- If J-Trace PRO was configured in J-Link Configurator, from there on, incorrect SWO speed capabilities were reported, even if max. SWO speed was not changed. Fixed. Affected firmwares: J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex
GDB Server
- Added support for SEGGER specific GDB protocol extension for streaming trace (qSeggerSTRACE:caps, qSeggerSTRACE:GetInstStats)
- Improved parsing speed of GDB protocol packets
J-Flash
- Added flash programming support for Silicon Labs EFR32MG14PxxxF256, EFR32BG14PxxxF256 and EFR32FG14PxxxF256 series devices.
- Added flash programming support for Cypress CY8C4125xxx-PSxxx and CY8C4145xxx-PSxxx series devices.
- Added flash programming support for Cypress CYBLE-014008-00, CYBLE-022001-00 and CYBLE-214009-00 series devices.
- Added flash programming support for NXP LPC804 series devices.
- Added flash programming support for Silicon Labs EFM32TG11BxxxF64 and EFM32TG11BxxxF128 series devices.
- Added flash programming support for ST "STM32L442KC" series devices.
- Added new command line option "-hide" which can be used to run J-Flash in hidden mode (no windows are showen).
- Improved log output during Erase/Program/Read back.
- In case of command line execution, J-Flash closed in case of error even if no -exit command was passed. Fixed.
- NXP iMXRT102x: Added QSPI-Flash programming support.
- NXP iMXRT1051 / iMXRT1052: Added HyperFlash flash programming support.
- NXP iMXRT1051 / iMXRT1052: Added QSPI flash programming support.
- Preparing the Flasher for stand-alone mode with a J-Flash project which uses the auto-detect flash bank feature did not work. Introduced in V6.30h. Fixed.
- The extension of the *.PEX file was corrupted when saving a config & pex file to the pc using (File -> Save Flasher config file...). Introduced in V6.30i. Fixed.
- Under special circumstances, executing J-Flash from the command line interface failed. J-Flash closed immediately in this case. Fixed.
- Under special circumstances, J-Flash did not recognize that the opened data file does not fit into selected sectors. Fixed.
- Under special circumstances, reading back flash contents could be slowed down by accident (e.g. when reading large parts of the flash with lots of non-programmed areas in the requested area). Fixed.
- When generating a DAT file with big gaps for Flasher stand-alone operation, for parallel CFI NOR flash, it could happen that Flasher failed to flash the file while J-Flash worked fine. Fixed.
- When importing a binary data file, the start address of the the first flash memory bank is set as default start address.
- When reading back large flash areas where there were huge non-programmed parts between programmed data areas, J-Flash could enter an endless loop. Fixed.
J-Flash Lite
- File dialog did not allow selecting network resources. Fixed.
- NXP LPC540xx: QSPI could not be erased because banks was not marked as "always present". Fixed. As these devices do not provide internal flash, but QSPI only, we can mark this bank as always present.
J-Flash SPI
- Added SPI / SPIFI (QSPI) support for Eon EN25F40, EN25F80, EN25Q80A, EN25F32, EN25P32, EN25F16 and EN25QH64 SPI flashes.
- Added SPI / SPIFI (QSPI) support for Macronix MX25R3235F, MX25L6433F and MX25R4035F SPI flashes.
- Added support for Macronix MX25R8035F serial flashes.
- Some SPI flashes listed as supported were not detected properly. Fixed. Affected flashes: ISSI IS25LQ080B, ISSI IS25LQ016B, ISSI IS25LQ032B
J-Flash SPI CL
- Added CL option -jflashlog and -jlinklog.
- Streamlined CL options to follow descriptions in user manual.
J-Link Package
- Linux: 3rd party plugins may failed to detect certain executables like J-Link GDB Server names. Fixed. (Added symlinks because executable names were changed from V6.22 to V6.30)
- macOS: 3rd party plugins may failed to detect certain executables like J-Link GDB Server names. Fixed. (Added symlinks because executable names were changed from V6.22 to V6.30)
- Windows: In Windows 10 and later, when having multiple versions of the J-Link software installed, they were presented in a messy way in the start menu. Fixed.
Manual
- UM08001: Added SEGGER specific GDB protocol extension for streaming trace
- UM08001: Moved J-Link GDB Server to separate chapter
Version V6.30k (2018-04-09)
Commander
- Commander could crash on command file execution if a line in the command file contained more than 511 characters. Fixed.
Configurator
- A crash could happen when hitting "Update firmware of selected emulators" but not having any emulators selected. Fixed.
DLL
- If both, a JLinkDevices.xml and JLinkDevices.ref was present in the DLL dir, the XML always had priority which made it impossible to update SEGGER Embedded Studio installations via new J-Link software packages. Fixed.
- Open flash loader did not work correctly (DLL could complain about not finding some symbols in the ELF file). Introduced with V6.30i (release) and V6.31f (beta). Fixed.
- Some old SiLabs J-Link OBs are running a buggy firmware that did not work well with current J-Link software versions. Fixed.
J-Flash
- *.s37 could not be selected in the data file dialog. Fixed.
- When creating a new project for a Renesas RX device and then open a data file, followed by a "Save Flasher data file" select, it could happen that the Flasher data file was empty (header data only, no payload data). Fixed.
J-Flash SPI CL
- Possible vulnerability in -open command line option when passing formatter strings like xxx%p%p%p. Fixed.
Version V6.30j (2018-03-29)
Commander
- Exec command verifybin did not handle correctly on failed verify. Fixed.
DLL
- Flashing of NXP LPC8N04 could fail under certain circumstances as 32 kB was configured instead of actual 30 kB. Fixed.
- Nordic Semi NRF52: SWO did not work properly. Fixed.
- NXP iMX7ULP: Under special circumstances, flash programming could fail. Fixed.
- Renesas R5F51116 series devices where not recognized by J-Link properly, so ongoing debug mode etc. were not correctly configured on connect, making debugging impossible. Fixed.
- Silicon Labs EFM32JG: Incorrect core was displayed in the device selection dialog. Fixed.
- ST BLUENRG1: Reset did not work properly (this could cause flash programming to fail) and output a lot of garbage log outputs. Fixed.
Firmware
- J-Link drove pins by accident, even if there was no connection to J-Link etc. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
- When selecting an interface != JTAG, it could happen that a glitch was output on the TCK and/or TMS pin of J-Link (this caused problems when performing the ASC -> SWD BMI switching sequence for Infineon XMC1xxx series devices). Fixed. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4
J-Flash
- When using third party remote applications (e.g. TeamViewer) in parallel to J-Flash, the "-exit" command may not worked in J-Flash. Fixed.
Version V6.30i (2018-03-23)
DLL
- NXP Kinetis family: J-Link was not able to perform a proper reset on devices with an invalid application (e.g. flash addr 0x4 == 0x00000000). Improved.
- TI CC3200 / CC3220SF: Connect via JTAG interface did not work. Fixed.
- TI TMS570LSxxxx family: Erase returned an error because the erasure of the OTP area returned an error. Fixed.
Firmware
- Flasher: The flasher did not accept a new command in case of an "#auto patch" command failed due to invalid parameters. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
- Flasher: The flasher did not power down the target, if the VTRef monitor reported an error. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher PPC V4, Flasher RX V4
J-Flash
- Atmel SAMD5x family: Under special circumstances, flash programming could fail. Fixed.
- Microsemi A2F500M3G: Flash programming did not work for the second flash bank (Addr >= 0x60040000). Fixed.
- The checkbox state of "Fixed VTref" was not taken into account. Fixed.
- The power options were not handled correctly. Fixed.
- Under special circumstances, when changing the MCU device in the project settings, it could happen that an additional "Auto detection" flash bank has been added. Fixed.
- When connecting to the J-Link for downloading config files, the connect was rejected, if a fixed VTref setting was applied. Fixed.
Version V6.30h (2018-03-16)
Control Panel
- "Log" tab refurbished.
- Under special circumstances "Log" tab did not work correctly. Fixed.
DLL
- Added command string "SetAllowStopMode"
- Analog Devices CM41x_M0 devices did not work. Fixed.
- When using an old J-Link with Keil MDK-ARM and Cortex-R4 based devices, the error message "The connected J-Link does not support the requested memory access (Flags = 02000000)". Fixed.
Firmware
- Flasher: #select was no longer usable after programming failed due to an invalid config file. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher PPC V4, Flasher RX V4
J-Flash
- J-Flash did not behave correctly under special circumstances when importing old project files. Fixed.
- Multiple chips for CFI flash programming were not handled correctly. Fixed.
- Saving a project/data file under the root dir on a volume (D:\, E:\, ...) failed. Fixed.
Manual
- UM08001: Added command string "SetAllowStopMode"
Version V6.30g (2018-03-12)
DLL
- Connecting to fab. new Analog Devices CM40x revision 2 or later series devices could fail. Fixed.
- J-Link OB on Holt IC boards with S/N 302113761 - 302113860 incorrectly reported "Renesas" as silicon vendor limit. Fixed.
- JLINK_FUNC_CAN_ACC_MEM_WHILE_RUNNING did not distinguish between 1 and 2 which allows detection of background access support and stop mode access support. Fixed.
- Linux/macOS: If JLINKARM_Open() failed and no JLINKARM_Close() was called afterwards (which is allowed due to the API spec.) it could happen that the process crashed on unload of J-Link DLL (Mainly happened in SEGGER Embedded Studio). Fixed.
- Reverted change (V6.30f) in Flash loader for STM32F401CC devices. More information how to program STEVAL-FCU001V1 can be found in SEGGER Wiki.
- SiLabs EFM32/EFR32/EZR32: Support for voltage scaling mode broke support for some EFM32 series devices (e.g. EFM32WG series). Introduced in V6.30e. Fixed.
- TI RM47L series devices could halt on SVC exceptions even if user did not set vector catch in IDE. Fixed.
- TI RM4xL series devices could halt on SVC exceptions even if user did not set vector catch in IDE. Fixed.
- TI TMS570 series devices could halt on SVC exceptions even if user did not set vector catch in IDE. Fixed.
- Under special circumstances, flash programming on Cypress S6J32x /S6J33x (Traveo) series devices could fail. Fixed.
Firmware
- Flasher: A communication timeout could occur while creating the secure area or deleting files. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
J-Link Package
- Windows: Added version number to shortcuts in start menu to be able to distinguish between multiple versions in Windows 10 start menu and Windows 7 start menu search
Version V6.30f (2018-03-02)
Commander
- When using speed selection "auto" a double connect was performed. Fixed.
- When using speed selection "auto" it could happen that a connect output garbage data. Fixed.
Control Panel
- Bugfixes for various browsers.
- Log tab was updated even if data did not change (prevented being able to copy window contents). Fixed.
- RTT was updated even if data did not change (prevented being able to copy window contents). Fixed.
DLL
- NXP LPC12xx Under special circumstances, the device specific reset could fail. Fixed.
- Renesas Synergy: Under special circumstances (if QSPI controller was in XIP mode), QSPI flash programming did not work. Fixed.
- STM32F401CC flash loader for STEVAL-FCU001V1 board could fail under certain circumstances. Fixed.
Firmware
- When using high target interface speeds (> 20 MHz) it could happen that debug operations on Cortex-A/R targets timed out and threw errors even if signal quality etc. were all good. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
- When using RTT/memory stop mode with high target interface speeds (> 20 MHz), it could happen that firmware hang. Introduced in V6.30. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
GDB Server
- Disabling option "Localhost only" did not work in GUI version (ports were still opened listening localhost only). Introduced in V6.30. Fixed.
Version V6.30e (2018-02-23)
DLL
- Improved error handling if J-Link runs out of memory because of too many parallel connections.
- Silicon Labs EFM32 / EF32: When using the MCUs voltage scaling feature, flash programming could fail. Fixed.
- When connecting to a Cortex-M7 device and using RTT, it could happen that the error message "the connected J-Link does not support Cortex-M7" was shown, even if J-Link supported Cortex-M7. Fixed.
- When using low power mode debugging (https://wiki.segger.com/Generic_IDE#Low_power_debugging) it could happen that manually halting the CPU after a low power -> normal mode transition failed, even if the debug interface was available again. Fixed.
Firmware
- Flasher Portable PLUS: Added support for custom configuration labels
- Infineon XMC1000 series devices: Automatic switching from ASC mode did not work. Fixed. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4
- Reading the serial number from the file could result in a wrong serial number. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
- When connecting to Infineon XMC1000 series devices automatic switching from ASC mode succeeded but following SWD communication could fail as SWDIO was no longer driven by J-Link. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4
J-Flash
- Some windows (e.g. "Enter start address") were displayed on the wrong monitor when using multiple monitors. Fixed.
- The flash size was displayed incorrectly in the device selection dialog. Introduced in V6.30d. Fixed.
J-Flash Lite
- Not all devices with flash were shown (e.g. Renesas Synergy S128 series was missing). Fixed.
- Window was positioned off screen in multi-monitor setup. Fixed.
Trace
- Cortex-M3/M4: If an LDR/STR instruction was aborted due to an exception, it could happen that the aborted instruction was shown twice in backtrace (did not happen for live trace fetch/executed counters). Fixed.
Version V6.30d (2018-02-16)
Commander
- A communication timeout could occur while creating the secure area. Fixed.
DLL
- Added debug support for Cypress S6J324CKSM series devices.
- Connect sequence was not correctly aborted if initial flash programming for debug enable failed. Fixed.
- Cortex-A/R: When reading/writing memory while the CPU was running (J-Link performed an implicit halt and go where necessary), an internal error for R0 could happen. Introduced with V6.30. Fixed.
- Cortex-M7 r0p0: Stepping over a POP {..., PC} instruction failed. Fixed.
- Disassemble functionality of DLL did not detect POP {..., PC} as branch. Fixed.
- update of Flasher via IP could throw communication time outs. Fixed.
Firmware
- Authorized Flashing: Flasher did not copy the _SECURE area folder to the secure partition. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
- Authorized Flashing: Flasher reported failure when initiating a flash operation from the secure partition. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
- Flasher: Some status messages did not fit on display. Fixed. Affected firmwares: Flasher Portable PLUS
- Renesas RX via FINE (especially RX2xx, RX1xx): Sometimes, the CPU did not start correctly on Go() requests. Mainly happened when starting the CPU for flash programming. Could result in all kinds of error messages for flash programming. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4
J-Flash
- If the address space of the opened data file does not match the selected sectors, a message box pops up which allows to relocate the application to fit the selected address space.
- Under special circumstances, erase could fail when using Open Flashloader based RAMCodes without native SEGGER_OPEN_Read but without BlankCheck() function. Fixed.
J-Flash Lite
- Improved log output
- Programming of empty NXP LPC1857 devices failed. (Introduced with V6.30b) Fixed.
Remote Server
- Added GUI version for Linux and macOS
Version V6.30c (2018-02-09)
CCS Plugin
- Some TI CC32xx series devices were not detected correctly. Fixed.
DLL
- Some J-Link models with USB full speed (J-Link BASE/PLUS V9, J-Link OB ST-Link, ...) did not work properly with Windows 7 running in VirtualBox + VirtualBox running on current (2016 or later) MacBook revisions. Fixed.
DLL Updater
- Installations of SEGGER Embedded Studio for ARM V3.34 and later were not found. Fixed.
Firmware
- Flasher failed to program Renesas RX65N series via FINE if 2 MHz was selected, while J-Link BASE/PLUS worked. Fixed. Affected firmwares: Flasher PRO V4, Flasher RX V4, Flasher Portable V1, Flasher Portable PLUS V1
- The Flasher Secure Area feature did not work in recent versions of the Flasher firmware (Secure Area detection failed). Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
GDB Server
- Device selection dialog in GUI version did not show PIC32 devices. Fixed.
- GUI thread did not lock correctly (log output could be lost). Fixed.
J-Flash
- The verify type could not be changed in the project settings GUI window. Fixed.
J-Flash Lite
- GUI thread did not lock correctly (log output could be lost). Fixed.
J-Link Package
- Windows: Shortcut in start menu to J-Link Registration utility did not work. Fixed.
Version V6.30b (2018-02-02)
DLL
- Erase of 512 KB based ST STM32L451, STM32L452 and STM32L462 series devices did not work. Fixed.
- Open Flashloader: Under special circumstances, the ELF file parser was not able to locate the function entry of a function (e.g. Init()). Fixed.
Firmware
- VCOM Tx did not work correctly (Introduced with V6.22c). Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
J-Flash Lite
- Now available for Linux and macOS too.
RTT Viewer
- Increased limit of max. lines to be buffered/shown to 10k
Version V6.30a (2018-01-31)
DLL
- Auto-detection of latest installed J-Link DLL version did not work properly for 64-bit applications. (Introduced with V6.30). Fixed.
- Some Atmel (Microchip) devices were not recognized by the J-Link DLL (ATSAMHA1G14A, ATSAMHA1G15A and ATSAMHA1G16A). Fixed.
- Under certain circumstances connect to Altera Cyclone V was not possible. Fixed.
GDB Server
- About dialog could stay open if GDB Server exited itself while about dialog was open. Fixed.
- Multiple instances of about dialog could be opened. Fixed.
- Sometimes GUI version did not start under macOS. (Introduced with V6.30). Fixed.
License Manager
- Sometimes GUI version did not start under macOS. (Introduced with V6.30). Fixed.
Registration
- Sometimes GUI version did not start under macOS. (Introduced with V6.30). Fixed.
Version V6.30 (2018-01-30)
DLL
- Added flash programming support for NXP LPC51U68 series devices.
- Cypress PSoC6: Erasing flash banks that are always present (like internal flash) did not work out-of-the-box. Fixed.
- Extended max. path length (to 512 characters) when manually specifying a path to a JLinkDevices.xml file
- Implemented RTT stop mode support for Cortex-A/R based devices
- Implemented RTT stop mode support for RISC-V based devices
- Implemented RTT stop mode support to allow RTT also on targets that do not support background access.
- Microchip ATSAMHA1ExxAB and ATSAMHA1GxxAB: Added flash programming support.
- Open flashloader did not program flash correctly. Introduced with V6.22g. Fixed.
- Open flashloader: The parser did not work with special formatted elf files. Fixed.
- SiLabs EFM32 series: When using Keil/IAR flashloader for flash download and making use of J-Link FlashBP feature and having 2 or more FlashBP set in different flash sectors, it could happen that one of the sectors was not programmed correctly. Fixed.
- Under special circumstances, Cypress S6J33xx series devices did not work. Fixed.
- Under special circumstances, erase chip failed for the LPC540xx series devices (e.g. in J-Flash Lite). Fixed.
- Under special circumstances, flash download through the Keil flashloader failed on LPC540xx devices. Fixed.
Firmware
- Connect to Qorvo GP570 series devices failed because J-Link reported pin override as not supported. Fixed. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4
- Flasher Universal flashloader did not disable target IF at the end. Fixed. Affected firmwares: Flasher PRO V4
- Flasher: Reset did not work in stand-alone mode for analog devices Analog Devices ADuCM3x and ADuCRF series devices. Fixed.
- Flashing of internal and external flash in one step in Flasher stand-alone mode, fixed.
GDB Server
- Introduced GUI version for Linux and macOS
GDB Server CL
- Command line output was broken in case open flashloader was used and flash contents already matched the data to be programmed. Fixed.
J-Flash
- Added flash programming support for NXP LPC51U68 series devices.
- Added option for setting a fixed VTref.
- Added options for Flasher ATE power supply.
- Centralized the main GUI window on startup.
- Cypress PSoC6: Erasing flash banks that are always present (like internal flash) did not work out-of-the-box. Fixed.
- Microchip ATSAMHA1ExxAB and ATSAMHA1GxxAB: Added flash programming support.
- Under special circumstances, preparing the Flasher for stand-alone mode did not work (data file corrupted). Fixed.
J-Flash SPI
- Opening an J-Flash project with NumAddrBytes != 3 or 4 (e.g. NumAddrBytes == 2) did not work. Fixed.
J-Flash SPI CL
- Flash programming did not work for Micron SPI flashes >= 16 MB. Fixed.
J-Link Package
- SDK: We did not ship the JLinkDevices.XML (+ required device specific files) with the J-Link SDK. Fixed.
RTT Viewer
- Added option to configure terminal buffer size. Changed default buffer size to 500 lines.
SWO Viewer
- Added default message when no SWO clock speed is selected.
Version V6.22g (2018-01-17)
DLL
- Added support for Samsung ARTIK05X series devices.
- J-Link OB SAM7 (Holt IC) did not allow debugging of Atmel / Microchip devices (e.g. ATSAM3U4). Fixed.
J-Flash
- Check for missing custom RAMCode file, fixed.
- Download of flash data for Flasher stand-alone mode for devices with internal flash and no additional external flash, fixed.
Version V6.22f (2018-01-12)
Commander
- Within the Linux variant command line entries could get twisted. Fixed.
DLL
- Added official support for Renesas synergy S3A1 series devices
- The RAM size of MB9BF121J series devices was incorrect resulted in flash programming failed. Fixed.
Firmware
- Read in from SWO of external devices with J-Link OB on Nordic Semiconductor nrF52-DK, fixed.
GDB Server
- Implemented WriteDP/WriteAP/ReadDP/ReadAP monitor commands
Version V6.22e (2018-01-08)
DLL
- Connecting to NXP i.MX6UL and i.MX6ULL series devices failed. Introduced with V6.22. Fixed.
- Internal flash programming support for NXP LPC8N04 device added.
- Message box "Found active soft BPs when downloading to flash" could appear. Fixed.
- NXP S32K142: The device was configured as Cortex-M0 but it is a Cortex-M4. Fixed.
Firmware
- Flasher: Under special circumstances e.g. in case of the device is in some kind of low power mode, flash programming in stand-alone mode failed (e.g. EM357 devices). Fixed.
J-Flash
- If a flash algorithm specified page sizes > 2KB, generation of FLASHER.DAT, for stand-alone mode operation, failed. Fixed.
J-Flash SPI
- Erase timed out for SPI flashes with a busy bit (e.g. Adesto AT25SF64). Fixed.
Version V6.22d (2017-12-14)
DLL
- Fixed programming speed regression for CFI based flash algorithms (AMD). Introduced in V6.xx. Fixed.
- Flash programming of the Flex NVM area of NXP MWCT101xS series devices did not work. Fixed.
- The sector size of NXP S32K142 series devices was incorrect (4KB instead of 2KB). This could cause issues during flash programming. Fixed.
- There has been a regression regarding the flash programming speed of Marvell 88MW300 series devices. Introduced in V6.16i. Fixed.
- TI CC2538: Unlocking of secured devices did not work. Fixed.
- Updated the flashloader for Analog Devices ADUCM4x50 (erase timing updated).
Firmware
- Flasher: Stand-alone mode: There has been a regression regarding the flash programming speed of Marvell 88MW300 series devices. Introduced in V6.16i. Fixed.
J-Flash
- Added a new tab (Performance), which can be used to configure certain optimizations which are valid for all actions in J-Flash (Production Programming & Manual Programming).
- J-Flash does no longer perform a erase prior "Manual Programming" -> "Program" or "Manual Programming" -> "Program & Verify".
Version V6.22c (2017-12-08)
Commander
- MacAddr command: Wrong MACAddr was shown for unknown J-Link models. Fixed.
DLL
- Added flash programming support for Maxim MAX32558 series devices.
- Flasher Portable PLUS: Firmware update failed. Introduced in V6.22. Fixed.
- NXP LPC540xx: Under special circumstances, flash programming (QSPI) did not work. Fixed.
- Under certain circumstances ETM Trace with 3rd party debug software was not working correctly, introduced with V6.20g. Fixed.
- When having multiple connections to a J-Link open, no error was indicated if J-Link firmware could not allocate connection context. Fixed.
- Windows: If FlashBPs needed to be removed on DLL close, GUI thread was not exited properly which could cause J-Link tray icon to stay in task bar until the whole process was exited. Fixed.
Firmware
- J-Link OB-MB9AF312K-Spansion did not allow debugging of Cypress devices that were originally Spansion devices. Fixed.
- RTT did not work correctly on big endian targets. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
- Under special circumstances, connecting to XMC1000 series devices did not work. Fixed.
- When having multiple connections to a J-Link open, J-Link firmware could crash if it not allocate connection context. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
J-Flash SPI CL
- Under special circumstances, the command line version did not return an value != 0 in case of error. Fixed.
Version V6.22b (2017-12-06)
DLL
- Opening multiple connections to a J-Link could fail on some current models. Introduced with V6.22a Windows Hibernate workaround. Fixed.
Version V6.22a (2017-11-28)
Commander
- Added command "VTREF" to set a fixed VTref for J-Links that support it
DLL
- Added CORESIGHT_SetCSTFBaseAddr exec command to be able to set trace funnel base address over scriptfile should automatic detection through ROM table not be available.
- Added NVM user row programming support for SAM4L series devices.
- Atmel SAMD20: Under special circumstances, the user row could not be programmed. Fixed.
- Connect sequence of Infineon XMC4000 series devices could not be overwritten via J-Link script files. Fixed.
- For some devices (e.g. Synergy S7G2) Coresight addresses were set incorrectly. Introduced with V6.20g. Fixed.
- If one instance had a connection to a new USB 3.0 based J-Trace model open, this J-Trace was not listed in Configurator anymore. Fixed. Affected J-Trace models: J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex
- NXP LPC1850: QSPI flash programming did not work when using a S25FL129P as target SPI flash. Fixed.
- Reset sequence of Infineon XMC4000 series devices could not be overwritten via J-Link script files. Fixed.
- S32K144: Unlocking procedure was not reliable. Fixed.
- Some batches of J-Link EDU Mini did not report to have a valid FlashBP license. Fixed.
- Some Infineon XMC100 device names (e.g. xmc1100) were not accepted by the J-Link DLL. Fixed.
- Some J-Link OBs on eval boards from Engenuics (e.g. Razor Board 2) could only be used with the NordicSemi nRF device on the board but not with the Microchip SAM3U. Introduced in V6.22. Fixed.
- When exiting Hibernate mode under Windows 7 / Windows 10 it could happen that J-Link became unresponsive to certain commands. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
Firmware
- Added support for setting fixed VTref. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex
SWO Viewer
- Added SWOClock Combobox and renamed TRACECLK Combobox to CPUClock. Now the user has the option to select the SWOClock speed manually. Default is maximum supported SWOSpeed by target device.
Version V6.22 (2017-11-24)
Commander
- Added new command "ExpDevListXML" which can be used to export the entire device list + aliases in a xml formatted file.
Control Panel
- RTT tab in web based control panel did not lock correctly when adding RTT printf data. Fixed.
DLL
- Added command string SetDisableSkipBlankDataOnProg. Forces J-Link/Flasher to also program all areas in the data file that are filled with the erased value (usually 0xFF)
- Added flash programming support for Cypress PSoC 4100 Plus series devices.
- Added flash programming support for Cypress PSoC 4100S series devices.
- Added flash programming support for Cypress S6J3300 series devices.
- Added flash programming support for Maxim MAX32510 series devices.
- Added flash programming support for Maxim MAX32510 series devices.
- Added flash programming support for Maxim MAX32600 series devices.
- Added flash programming support for Maxim MAX32650.
- Added flash programming support for Maxim MAX32650.
- Added flash programming support for NXP LPC802 series devices.
- Added flash programming support for NXP S32K116 and S32K118 series devices.
- Added flash programming support for NXP S32K116 and S32K118 series devices.
- Added flash programming support for Qorvo UE878 series devices.
- Added flash programming support for ST BlueNRG2 series devices.
- Added flash programming support for ST STM32L4R and STM32L4S series devices.
- Added flash programming support for TI MSP432E series devices.
- Added native pin trace support for STM32L4R/S device family based on STM32L4R9I - EVAL board.
- Added QSPI flash programming support for NXP LPC540xx series devices.
- Added user row programming support for Atmel (Microchip) SAMC20, SAMC21, SAMDA and SAML22 series devices.
- Added write protected device detection for Nuvoton NUC1xx, NUC4xx and M45x series devices.
- Added write protected device detection for Nuvoton NUC1xx, NUC4xx and M45x series devices.
- For some very old J-Link OBs mounted on IAR MB9BG618T-SK boards, the error message that the OB has been designed to work with devices from "Renesas only" popped up. Fixed.
- For some very old J-Link OBs mounted on IAR TMPM369-SK boards, the error message that the OB has been designed to work with devices from "Renesas only" popped up. Fixed.
- Implemented graphs for target power consumption, target voltage, ... in web based control panel.
- Implemented support for script file function to retrieve SWO base clock for devices where SWO base clock is not CPU clock (e.g. SiLabs EFM32 and NordicSemi nRF52)
- Implemented support for script file function to retrieve SWO base clock for devices where SWO base clock is not CPU clock (e.g. SiLabs EFM32 and NordicSemi nRF52)
- J-Link Lite-ADI (Analog Devices) probes could not be used with ADuCM450. Fixed.
- Linux: Under very special circumstances a deadlock could occur due to incorrect handling of WaitForMutexTimed()
- New USB 3.0 based J-Trace models were not detected properly by the J-Link SW when J-Trace was connected to a USB 3.1 controller (only happened on some PCs). Fixed. Affected J-Trace models: J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex
- NXP K32W_M4: Changed reset behavior of the M4 to perform a ordinary reset (reset via system reset request).
- NXP S32K148: The flash size specified in the J-Link software was incorrect (2 MB instead of 1.5MB). Fixed.
- Open Flashloader: The Open Flashloader now allows to specify less than 512 elements in the SECTOR_INFO struct which is part of the "FlashDevice".
- QSPI flash programming did not work for empty NXP LPC540xx and LPC54S0xx series devices. Fixed.
- Renesas Synergy S5D9: Added flash programming support for the configuration flash area.
- Renesas Synergy S5D9: Added flash programming support for the configuration flash area.
- RISC-V: Flash breakpoints did work properly if interrupts were active/enabled
- Some J-Link OBs on eval boards from Engenuics (e.g. Razor Board 2) threw the error message "This J-Link has been designed to work with devices made by Atmel only", while there is a Nordic Semi device on the board. Fixed.
- ST STM32F7: Added support to program the internal flash trough the ITCM memory space.
- When debugging on RISC-V based devices, a reset sometimes did not halt the MCU before it executed some user code. Fixed.
DLL Updater
- SEGGER Embedded Studio RISC-V was not offered for DLL updates. Fixed.
Firmware
- Under very special circumstances, download into RAM on Renesas RZ/A1H devices was factor 3 slower when running a firmware from the V6.20 J-Linmk software series. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace PRO V2 Cortex-M, J-Trace PRO V2 Cortex, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
J-Flash
- Added new command line argument "-setcpuidcode<IDCodeString>".
J-Flash SPI
- "-speed" command line option was not evaluated. Fixed.
- Added new example project which performs a protection unlock on connect for Adesto AT25DF081 SPI flashes.
Manual
- UM08001: Updated.
Trace
- Updated script file for Atmel SAMA5D2x devices to support ETB trace.
Version V6.20i (2017-11-17)
Commander
- FPU registers were not shown for Cortex-M23 / M33 based devices. Fixed.
- J-Trace Pro MACAddress was not printed in Commander correctly when requested. Fixed.
DLL
- Added SiFive E31ARTY as supported device name.
- Analog Devices ADuCM405x: Updated the flash algorithm with a new version which sets the ECC bits.
- Atmel SAMV7: From now, we support flash programming through the mirror address at 0x00000000.
- Flash programming of Cypress PSoC6 series did not work. Fixed.
- JTAG Id of NXP iMX8 DAP was not recognized. Fixed. (A53 / A72 cores are not supported yet!)
- NXP: Updated the alias device table as some devices were not recognized.
- Silicon Labs EFM32JG12BxxxF1024 was not recognized by the J-Link DLL. Fixed.
- Some Realtek devices were identified incorrectly, causing memory accesses that crossed a 1 KB boundary, to not work correctly. Fixed.
OFL
- Default programing timeout changed to 1 second. Should a flashloader be used with a lower value it will be overwritten to 1 second.
- SPI Flashloader on NXP iMX7ULP series devices could timeout under certain circumstances. Fixed.
Version V6.20h (2017-10-27)
DLL
- Cypress CY8C4126xxx-Sxxx_ID25x / CY8C4146xxx-Sxxx_ID25x: Page size of the internal flash, used during programming procedure, was incorrect. Fixed.
- Flasher V3 was not able to detect a STM32L4 series device. Fixed.
- When using an old Flasher V3 with a target device which requires special handling on connect, a communication time out occurred. Fixed.
J-Flash SPI
- J-Flash SPI did not evaluate the "Disconnect after each operation" setting. Fixed.
Version V6.20g (2017-10-20)
CCS Plugin
- From now, a J-Link script file can be specified in the target configuration dialog.
Commander
- No target interface was suggested for devices with Cortex-M3 r2p1 core. Fixed.
- No target interface was suggested for devices with RX65N/RX24T/RX130 core. Fixed.
DLL
- Added command string "CORESIGHT_SetETBBaseAddr"
- Added command string "CORESIGHT_SetMTBBufBaseAddr"
- Added command string "CORESIGHT_SetTFEnableMask"
- Added ETM backtrace support via J-Trace for Cortex-A9 + PTM (e.g. Renesas RZ/A1H)
- Added flash programming support for TI MSP432E series devices.
- Added Trace Pin initialization for Renesas RZ/A1H to generic part.
- Cortex-M23/M33: ROM table detection did not detect ITM component properly. Fixed.
- Cortex-M23: ROM table detection did not detect MTB-M23 component properly. Fixed.
- Improved single stepping speed in case trace is active
- Infineon TLE985x: Verify of the NACNAD area failed erroneously. Fixed.
- NXP Kinetis KL46 series: MTB tracing did not work properly. Fixed.
- Open Flashloader: Download failed on Cortex-A/R device. Introduced with 6.20b. Fixed.
- Windows 64-bit: Message box "The connected J-Link has been designed to work with devices made by xxx..." could crash debug session. Fixed.
J-Flash
- No target interface was suggested for devices with Cortex-M3 r2p1 core. Fixed.
- No target interface was suggested for devices with RX65N/RX24T/RX130 core. Fixed.
- Secure Target could fail if exit steps were specified. Fixed.
RTT Viewer
- [RTT Viewer] now uses the standard device selection dialog.
Version V6.20f (2017-10-13)
Control Panel
- Added support for multiple instances (e.g. in multiple Embedded Studio sessions etc.)
DLL
- Added flash programming support for NXP LPC802 series devices.
- Added new command string (SetHostIF <Interface>) which allows to configure the host interface (e.g. IP=192.168.0.12).
- Flash programming for TI TMS570 did not work correctly. Introduced in V6.20b. Fixed.
- Infineon TLE985x: Connect did not work and under special circumstances, flash programming failed. Fixed.
- Linux: When using streaming trace, the error "unknown trace packet found" could occur, even if everything was fine. Fixed.
- ON Semiconductor RSL10: RTT did not work due to incorrect work RAM was used. Fixed.
- ON Semiconductor RSL10: System clock was restored incorrectly. Fixed.
- Open Flashloader: When issuing two erase operations in a row, the Init() and UnInit() functions have been called in an incorrect order. Fixed.
- ST STM32F0: Attach did not work. Fixed.
- UNC network shares were accidentally handled as relative paths. Fixed.
GDB Server
- A buffer overflow could occur, if a symbol name in the RTOS plugin was longer than 31 characters. Fixed.
J-Flash
- J-Flash ignored invalid command line options. From now, J-Flash handles invalid / unknown command line options as error.
- UNC network shares were accidentally handled as relative paths. Fixed.
Version V6.20e (2017-10-06)
DLL
- Flash programming of Infineon TLE98xx series devices did not work. Fixed.
- Silicon Labs EFM32TG: Connecting to a secured device failed. Fixed.
- Under certain circumstances, connecting to NXP Kinetis V5x devices did not work. Fixed.
Firmware
- Flasher: Stand-alone mode programming failed when using SPC560D30/SPC560D40 target devices. Fixed.
- J-Link PRO: Webserver: Target power consumption is displayed in uA, but unit was displayed as "mA". Fixed.
J-Flash SPI
- Flash programming did not work for Micron SPI flashes >= 16 MB. Fixed.
Version V6.20d (2017-09-29)
CCS Plugin
- Under certain conditions, e.g. using an AM335x device, starting a debug session did not work. Fixed.
Commander
- J-Link Commander did not quit if exitonerror was active and the "connect" command failed. Fixed.
DLL
- Added new aliases for the NXP Kinetis / LPC device series as NXP is going to change the official naming.
- Data flash could not be programmed on SPC560D30/SPC560D40 devices. Fixed.
- Improved Atmel SAMD20 flash download speed.
- Open Flashloader: The incorrect sector information (the one from the JLinkDevices.XLM) have been showed in the device selection dialog. Fixed.
Firmware
- Flasher: Flash programming of Atmel SAMD20 series devices did not work in stand-alone mode. Fixed.
- Flasher: Under special circumstances (device empty), flash programming of NXP SKEAZNxx and KE0x series devices failed. Fixed.
J-Flash
- Added example project for SiliconLabs EF32G1 series, which enables the security as part of the exit steps. (EFR32BG1BxxxF256_EnableSecurity.jflash)
- Data flash could not be programmed on SPC560D30/SPC560D40 devices. Fixed.
- In command line mode, saving a flasher data file did not work. Fixed.
- In command line mode, some error messages were not logged. Fixed.
- Under special circumstances (device empty), flash programming of NXP SKEAZNxx and KE0x series devices failed. Fixed.
RTT Viewer
- Terminals were cleared on disconnect for no reason. Fixed.
Version V6.20c (2017-09-26)
Firmware
- RISC-V: Under special circumstances, flash programming could fail when checking IsHalted() state of CPU, before starting flash programming. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Link EDU Mini
Version V6.20b (2017-09-22)
Commander
- Command "setpc" did not work properly for RISC-V based targets. Fixed.
DLL
- "LowPowerHandlingMode" can now be enabled and disabled via command string.
- Added flash programming support for TI TMS570LS0714 and TMS570LS0914 series devices.
- Added OTP flash programming support for TI TMS570LS11xx and TMS570LS12xx series devices.
- Added QSPI flash programming for SiFive FE310 device on ARTY board.
- Added QSPI flash programming support for NXP iMX6SX series devices.
- The RAM size of Renesas R7FS5D57A series devices was incorrect. Fixed.
- Under special circumstances, flash programming failed on Renesas RX100 series target devices. Fixed.
Firmware
- J-Link OB-SAM3U128 V3: Added support for Cortex-M23 and Cortex-M33.
- RISC-V: X8 could be corrupted on single step. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
GDB Server
- The breakpoint packet did not return an error in case of breakpoint could not be set. Fixed.
J-Flash
- Under special circumstances, flash programming failed on Renesas RX100 series target devices. Fixed.
Remote Server
- If remote server was connected to a J-Link in the local network via Ethernet, tunnelled communication through J-Link Remote Server did not work. Fixed.
- Under special circumstances error "Unknown EMU command #26 received" was thrown. Fixed.
Version V6.20a (2017-09-15)
DLL
- Added flash programming support for Renesas R7FS5D57C and R7FS5D57A series devices.
- CMSIS / Open Flashloader: From now, we use the "TimeoutErase" for chip erase instead of the fixed timeout of 20 seconds.
- ST STM32F4: Sector erased failed on dual bank flash devices (2 MB). Fixed.
- TI "TMS570LS023X" and "TMS570LS033X" passed by TI Code Composer Studio were not recognized by the J-Link software. Fixed.
- When erasing sector 0 of Cypress S6E1C series devices, the trimming data were erased, too. Fixed.
Firmware
- Memory read/write speed on Cortex-A/R devices was very slow. Introduced in V6.18d. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
J-Flash
- "-save" required a start and end address when using to save *.bin files. From now, we simply save the entire file.
- When specifying a data file relative to the project file, the data file could not be opened. Fixed.
Version V6.20 (2017-09-08)
Control Panel
- Title contained garbage text. Fixed.
DLL
- Added "Data Flash" (4KB) programming support for Infineon TLE984x series devices.
- Added flash programming support for Cypress PSoC6 series devices.
- Added flash programming support for GigaDevice GD32F101xx, GD32F103xx, GD32F105xx, GD32F107xx, GD32F130xx and GD32F150xx series devices.
- Added flash programming support for Qorvo GP570, GP870 and QPG6095 series devices.
- Added flash programming support for ST STM32L011F4 series devices.
- Added flash programming support for the FlexNVM area of NXP MWCT101x series devices.
- Added flash programming support for TLE985x series devices.
- Added flash programming support for Toshiba TMPM3H0, TMPM3H1, TMPM3H2, TMPM3H3, TMPM3H4, TMPM3H5, TMPM3H6, TMPM3HM, TMPM3HN, TMPM3HP and TMPM3HQ series devices.
- Added flash programming support for Zilog Z32F0642 series devices.
- Added new command strings for setting Coresight ETM, PTM and TMC base addresses if they cannot be determined via the ROM table of the device
- Added QSPI flash programming support for ST STM32F469xx series devices.
- Added QSPI flash programming support for ST STM32F746NG.
- Added support for NXP MWCT101x series devices.
- NXP K32W Series: Added flash programming + full debug support for the Cortex-M0 core.
- Sector information of Infineon TLE98xx series devices were incorrect. Fixed.
- ST STM32F4: Sector erase failed when erasing sectors beyond the 1 MB flash size boundary (e.g. on STM32F413CH). Fixed.
- Updated flash programming support for the Infineon TLE984x, TLE986x and TLE987x series.
Firmware
- Flasher: Flash programming did not work for Infineon TLE98xx series devices in stand-alone mode. Fixed.
- HSS might output corrupted timestamps. Fixed.
- TIF_UART did not handle free space in the ring buffer correctly. Fixed.
Version V6.18d (2017-09-01)
DLL
- Added flash programming support for Analog Devices ADSP-CM41x and ADuCM4050 series devices.
- J-Link script files: Added new predefined objects "CORTEX_M23" and "CORTEX_M33".
- Open Flashloader: The J-Link DLL could crash when using flash loaders which were > 64KB in size. Fixed.
- Under rare circumstances, the device detection stalled when using the JTAG interface. Introduced with 6.15f / 6.16. Fixed.
- Webserver control panel did not load fonts properly, if not already available in browser. Fixed.
- When selecting a Zilog Z32Fxxx1 series device, the J-Link DLL displayed the "unknown device selected" dialog. Fixed.
Firmware
- Under special circumstances the HSS buffer size was not a multiple of one sample block, leading to a FW crash. Fixed. Affected firmwares: J-Link V9, J-Link V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, (Any OB with HSS support)
- Using HSS on Renesas RX based targets could crash the firmware. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
- When having multiple processes accessing the same device and core at the same time (e.g. when using J-Scope in parallel to a debugger), it could happen that incorrect data was read from the target. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
J-Flash
- When having gaps in the data file at certain address ranges (e.g. addr 0xFFFFFF8B of RX111 targets), J-Flash reported an error during verify. Fixed.
Version V6.18c (2017-08-21)
DLL
- Cleaned up / improved web based control panel for small window sizes.
- The script file, specified for the ONSemi RSL10 series devices was not executed. Fixed.
J-Link Package
- Uninstaller showed a message box if the silent option was specified (/S). Fixed.
Version V6.18b (2017-08-18)
Commander
- "exitonerror" did not work correctly in script mode on Linux ARM hosts. Fixed.
- No Error Message was shown if command file could not be opened. Fixed.
DLL
- Added flash programming support for ONSemi RSL10 series devices.
- NXP K32W Series: Added flash programming + full debug support for the Cortex-M0 core.
- RTT did not work correctly on Cortex-A and Cortex-R based devices. Introduced in V6.16. Fixed.
- TI MSP432P401V / MSP432P411V: Internal flash size was incorrect. Fixed.
GDB Server
- RTOS plugins handled some error conditions incorrectly. Fixed.
Version V6.18a (2017-08-11)
Commander
- "expdevlist" command could not be used without having a J-Link connected. Fixed.
DLL
- Added flash programming support for Microsemi M2S060 series devices.
- Added flash programming support for Nordic Semiconductor nRF52810_xxAA series devices.
- Added support for Renesas RX65N series.
- CMSIS / Open Flashloader: The DLL crashed when using large flash algorithms ( > 64 KB ). Fixed.
- CMSIS / Open Flashloader: The J-Link DLL was not able to handle algorithms with a RAM usage (RAMCode size + Page Size == data block size) > 32 KB. Fixed.
- Cortex-M23 / M33 core was no longer found on some buggy FPGA setups which provide incorrect ROM table information. Introduced with V6.18. Fixed.
- Renesas RX65N: Flash programming when using the Renesas FINE interface did not work properly. Fixed.
J-Flash
- When generating Flasher DAT files for Renesas RX based targets, for some specific hex/mot/bin files, the error "Error occurred while parsing the flash blocks" was thrown. Fixed.
STM32 Utility
- Factory default value for FLASH_OPTCR1 of STM32F7xx series devices was incorrect. Fixed.
Version V6.18 (2017-08-03)
DLL
- Added debug and flash programming support for Silicon Labs EFM32GG11B820F2048 device.
- Added QSPI flash programming support for CEC1702 series devices with SST26VF016B flash(e.g. mikro BUS Clicker board).
- Added QSPI flash programming support for CEC1702 series devices with SST26VF016B flash(e.g. mikro BUS Clicker board).
- Added support for TI DM3730
- Flash programming could fail on Cortex-M systems with MPU enabled and RAM being configured as "execute never". Fixed.
- For some devices, certain IDEs specified an MTB address, even if the device does not implement one. This could cause problems during flash programming (e.g. on NXP LPC54608). Fixed.
- Improved auto-detection of CPU core in a multi-AP Coresight setup (especially Cortex-M23 / M33)
DLL Updater
- In case multiple installations of Keil MDK-ARM (uVision) were present, only the last installed one was found. Fixed.
Firmware
- Current Flasher firmwares were unable to handle configurations that have been generated with old versions of J-Flash (V5.01e or earlier). Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
- Flasher Portable PLUS sometimes did not show all configurations. Introduced in V6.16j. Fixed. Affected firmwares: Flasher PRO V4, Flasher Portable PLUS
GDB Server
- Error message could be thrown if large memory write packets were received from GDB. Fixed.
J-Flash
- Added QSPI flash programming support for CEC1702 series devices with SST26VF016B flash(e.g. mikro BUS Clicker board)..
- Added QSPI flash programming support for CEC1702 series devices with SST26VF016B flash(e.g. mikro BUS Clicker board)..
- Added read back function for CMSIS based flash algorithms.
- From now, we output the CRC of the data file on open in the log window of J-Flash.
- From now, we output the CRC of the data file on open in the log window of J-Flash.
J-Flash SPI
- Added flash programming support for ISSI IS25LP032D and IS25WP032D SPI flashes.
- Added flash programming support for ISSI IS25LP032D and IS25WP032D SPI flashes.
- Added flash programming support for Micron M25PX80 SPI flashes.
- Added flash programming support for Micron M25PX80 SPI flashes.
Remote Server
- Error "unknown EMU command #24 received" occurred for some J-Link models. Fixed.
SWO Viewer
- SWO enable could fail on Cortex-M systems with MPU enabled and RAM being configured as "execute never". Fixed.
Version V6.16j (2017-07-24)
Commander
- Added names for some CoreSight components that were not detected properly, to ROM table detection.
- Some command strings (exec CmdStr) need to be called before a connection to J-Link has been opened. This did not work correctly. Fixed.
DLL
- Automatic unsecure of secured Nordic Semi nRF52 series devices did not work correctly. (Worked by chance in versions prior to V6.16b). Fixed.
- Cortex-M disassembly of 32-bit LRD/STR contained spaces before condition, making formatting in Ozone look odd. Fixed.
- Unsecure of Silicon Labs EFx32 series did not work properly. Fixed.
- When tracing via USB, one CPU core on the host PC was kept busy 100% even while the target CPU was halted and the DLL idle. Fixed.
Firmware
- It could happen that Flasher hang + restarted when changing the IP address. Introduced in V6.16i. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
Version V6.16i (2017-07-21)
DLL
- Added support for GigaDevice (Q)SPI NOR flashes: GD25Q05B, GD25Q10B, GD25Q20C, GD25Q40C, GD25Q80C, GD25Q16C, GD25Q32C, GD25Q64C, GD25Q127C, GD25Q128C, GD25Q256C, GD25Q512M
- CMSIS / Open Flashloader: Added "AlwaysPresent" as new attribute to the <FlashBankInfo> tag which allows to specify that a flash bank is always present (e.g. internal flash).
- CMSIS / Open Flashloader: From now, we use the timeouts specified in the "FlashDevice" structure for program ("TimeoutProg") and erase sector ("TimeoutErase").
- Connecting to legacy ST STR912 devices could fail. Fixed.
- Infineon TLE98xx series devices: We did not distinguish between TLE9842 and TLE9842-2 series devices. Fixed.
- Marvell 88MW300: Improved verification speed for QSPI programming (Example: 1 MB took ~8 seconds, now: ~3 seconds)
- QSPI flash programming did not work with Cypress S25FL064L SPI flashes (e.g. on the LPC4330). Fixed.
- Under special circumstances, connect to secured NXP (Freescale) Kinetis devices could fail. Fixed.
Firmware
- Added built-in HSS support to allow sampling frequencies of 1 kHz instead of 50 Hz. Affected firmwares: JLink-OB-SAM3U128, JLink-OB-SAM3U128 V3
- Connecting to Infineon XMC4400 series via SWD failed. Introduced in V6.16g. Fixed. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4
GDB Server
- Command line version now outputs full, passed command line via stdout.
- Server could hang and did not respond to any pause/exit etc. requests anymore if target application used semihosting with a getchar() putchar() echo implementation. Fixed.
J-Flash
- Buttons in general options dialog overlapped with controls. Fixed.
- CMSIS / Open Flashloader: Added support for check blank via read back.
- CMSIS / Open Flashloader: If programming failed in J-Flash, an incorrect address has been reported in the error message. Fixed.
- Connecting to legacy ST STR912 devices failed. Fixed.
- Under special circumstances, connect to secured NXP (Freescale) Kinetis devices could fail. Fixed.
J-Flash SPI
- Added example project for Cypress FM25CL64B SPI / F-RAM flash (Cypress_FM25CL64B.jflash).
- Added support for Cypress S25FL064L SPI flash.
Version V6.16h (2017-07-14)
DLL
- Erase did not work for Atmel ATSAM4C dual flash bank devices. Fixed.
- On some J-Trace PRO V1 units, the firmware update could fail. Fixed. (Note that on such units 3 FW updates may been seen, happing in a row, with this version. This is O.K. and expected)
- Open Flashloader: Under special circumstances, it could happen that compare compared too much data. Fixed.
- Under special circumstances, flash programming of Microchip's CEC1702 series devices did not work. Fixed.
Firmware
- Under special circumstances (programming failed for some reason), the firmware did not free allocated memory regions which could result in Flasher hang. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
J-Flash Lite
- Devices which have been added using the Open Flashloader were not displayed in the device selection dialog. Fixed.
Version V6.16g (2017-07-10)
DLL
- Added debug support for Renesas RZ/N1 series. R9A06G032 (RZ/N1D), R9A06G033 (RZ/N1S), R9A06G034 (RZ/N1L)
- Added support for Microchip: PIC32MX570F512H, PIC32MX570F512L
- Added support for Renesas R5F51308
- Command string "HideDeviceSelection = 1" was not evaluated correctly. Fixed.
- Data breakpoints (also called data events or watchpoints) could not be set while the CPU was running, even if the architecture allowed it (e.g. Cortex-M). Fixed.
- Device selection dialog was not created as topmost window and therefore could be covered by the application's window if opened from within an IDE etc. Fixed.
- Having multiple WriteMem accesses to flash with ReadMem accesses to RAM etc. between them could cause following WriteMem accesses to not trigger further flash downloads. Fixed.
- NXP Kinetis K32W: Device names were incorrect. Fixed.
- ST STM32F3 series: We do no longer perform the RAM initialization as according to the manual, the STM32F3 series does not come with ECC RAM.
- TI MSP432P401M / MSP432P401R: It seems like executing the flash algorithm (RAMCode) at 0x20000000 does not work. From now, we use the SRAM at 0x01000000. Fixed.
- When using command string "SetRestartOnClose = 0", some DLL internal caches were not invalidated and freed correctly, on close. Which could cause problems the next time, the DLL was opened. Fixed.
DLL Updater
- Added SEGGER Embedded Studio.
Firmware
- J-Link did not work properly if USB isolator was connected in between. Fixed. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4
- J-Trace PRO: Added support for ARMv8-M architecture.
GDB Server
- Corrected spelling mistakes in log output.
J-Flash
- "-open<DataFilePath>" command line option did not work when the specified path contained spaces. Fixed.
J-Flash SPI
- The application returned O.K. (0) instead of error (!= 0) in case of an incorrect data / project file has been passed via command line option. Fixed.
Version V6.16f (2017-07-03)
Commander
- Output of ExecCommand was accidentally parsed by printf formatter. Fixed.
Configurator
- Changing the maximum SWO speed of J-Link ULTRA+ / PRO v4 did not work correctly. Fixed.
DLL
- [J-Link Package] could no longer be used under Windows XP. Introduced in V6.16. Fixed.
- Added flash programming support for NXP Kinetis K32W series devices.
- Added QSPI flash programming support for iMX7ULP series devices (MCIMX7U3, MCIMX7U5).
- Added support for Cypress CCG3 series devices
- CLOUDERSEMI CR600: Updated flash algorithm which is shipped with the software package.
- Default reset strategy for Cortex-M did not try again via reset pin if initial attempt via AIRCR.SYSRESETREQ bit failed. Introduced in V6.16. Fixed.
- DLL could crash if starting + terminating a debug session multiple times without unloading the DLL between the sessions (some statics were not reset correctly on close). Fixed
- NXP KW01Z, KW2xZ, KW3xZ and KW4xZ: Connect and flash programming did not work under special circumstances. Fixed.
- Unsecure for S32K144 did not work reliably. Fixed.
J-Flash
- Added QSPI flash programming support for iMX7ULP series devices (MCIMX7U3, MCIMX7U5).
- When using CMSIS based flash loaders, the second programming cyclus failed. Introduced in V6.16e. Fixed.
Version V6.16e (2017-06-27)
DLL
- Added flash programming support for some new STM32F723xx and STM32F733 series devices.
- Added support for LPC54628 device series.
- Flash download did fail if 2 continuous flash banks were written in one big memory access. Fixed.
- Renesas RX simulation did not handle Carry flag correctly for some variants of the ADD instruction
GDB Server
- -timeout command line option was removed by accident. Fixed.
Version V6.16d (2017-06-21)
CCS Plugin
- In older versions, J-Link always performed a Halt() when connecting to the target. From now, we evaluate the "Target Halt On Connect" project option property.
DLL
- Added flash programming support for NXP KS22FN128, KS22FN256, KS20FN128 and KS20FN256 series devices.
- Exception could be caused in Ozone when disassembling instructions with specific conditions. Fixed.
- SEGGER Embedded Studio could crash if J-Link software was trying to show some message boxes. Fixed.
- Trace pin init for Atmel ATSAMV7 series could not be overwritten via J-Link script file function OnTraceStart(). Fixed.
J-Flash
- Improved the prepare speed for CMSIS based / Open Flashloader based flash algorithms.
- We do no longer show the "J-Flash project has been modified, would you like to save..." dialog if the command line is active.
- We do no longer show the emulator selection dialog if the command line is active.
J-Link Package
- Installer: In older versions, J-Link always performed a Halt() when connecting to the target. From now, we evaluate the "Target Halt On Connect" project option property.
RTT Viewer
- Output could stop when reconnecting to the target. Fixed.
Version V6.16c (2017-06-16)
DLL
- Linux: On Fedora 25 systems and some other distributions, a segmentation fault could occur, if there were multiple processes connecting to the same J-Link in parallel and the initial process exited. Fixed.
- Some TI devices, that incorporate an ICEPick, did not work correctly with Rowley Crossworks. Introduced with V6.16b. Fixed.
- ST BlueNRG1: Added AfterReset() functionality which makes sure that the bootloader is executed after reset.
- ST STM32F070x6 devices: Erase sector did not work correctly resulting in errors during flash programming. Fixed.
- Using ETB trace on Cortex-A9 with J-Link LITE ARM could cause the error message "The connected J-Link does not support the requested memory access". Fixed.
Firmware
- If VCOM functionality with hardware flow control was used and target continued sending data after terminal session on PC side has been closed, it could happen that J-Link did not continue to receive VCOM data on a new COM port open. Fixed. Affected firmwares: JLink-OB-SAM3U128, JLink-OB-SAM3U128 V3
- Improved USB read performance. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4
- Incorrect capabilities for reading/writing memory were reported. This could cause ETB trace on Cortex-A/R to not work correctly. Introduced with V6.16. Fixed. Affected firmwares: - J-Link BASE V10, - J-Link PLUS V10, - J-Link EDU V10, - J-Link BASE V9, - J-Link PLUS V9, - J-Link EDU V9, - J-Link ULTRA+ V4, - J-Link PRO V4, - J-Trace PRO V1 Cortex-M, - J-Link Lite ARM V9, - J-Link Lite Cortex-M V9, - J-Link EDU Mini
GDB Server
- (Linux/Mac): Application did not perform a clean close/shutdown in case it was started with the "timeout" command as it did not handle SIGTERM correctly. Fixed.
J-Flash
- J-Flash did not close in command line execution mode if any error occurred although the "-exit" option was set. Fixed.
J-Flash SPI
- Added timeout handling for erase sector and erase chip.
- Programming of SPI flashes with an BUSY status flag did not work. Fixed.
J-Link Package
- Installer: Linux: rules file had incorrect syntax for some specific product ids. On some systems (e.g. Fedora 25) this could cause being unable to use J-Link with normal user rights (root rights needed). Fixed.
RTT Logger
- (Linux/Mac): Application did not perform a clean close/shutdown in case it was started with the "timeout" command as it did not handle SIGTERM correctly. Fixed.
SWO Viewer
- (Linux/Mac): Application did not perform a clean close/shutdown in case it was started with the "timeout" command as it did not handle SIGTERM correctly. Fixed.
Version V6.16b (2017-06-09)
DLL
- CMSIS flash algorithm didn't erase flash if verify failed. Fixed.
- NXP Kinetis devices: Under special circumstances, connect / flash programming did not work. Fixed.
Firmware
- Added support for low-level Coresight DAP accesses in firmware, to speed up debugging during startup etc. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Link Lite ARM V9, J-Link Lite Cortex-M V9, J-Link EDU Mini
- If VCOM functionality with hardware flow control was used and target continued sending data after terminal session on PC side has been closed, it could happen that J-Link did not continue to receive VCOM data on a new COM port open. Fixed. Affected firmwares: JLink-OB-SAM3U128-mbedBTL-NordicSemi
GDB Server
- The qCRC command was accepted although it is not supported. Fixed.
- Writing registers resulted in wrong terminal output. Fixed.
SWO Viewer
- Error message "Cannot not connect to J-Link" popped up and SWOViewer exited, even in case connection was successful. Fixed.
Version V6.16a (2017-06-06)
DLL
- Under special circumstances, compare did not work during flash programming. Introduced in V6.16. Fixed.
J-Flash
- "Test speed" did not show values in result dialog. Fixed.
Version V6.16 (2017-06-02)
DLL
- Added an unlock dialog which allows to confirm or decline the unlock process for Silicon Labs EFM32, EFR32 and EZR32 series devices.
- Added checksum generation to algo for QN908x.
- Added debug support for Cypress CYW43907 series devices.
- Added debug support for Cypress S6J328CK, S6J328CL series devices.
- Added debug support for NXP iMX7D (MCIMX7D3, MCIMX7D5, MCIMX7D7) series devices.
- Added debug support for NXP iMX7ULP series devices (MCIMX7U3 and MCIMX7U5).
- Added flash programming support for Atmel (Microchip) SAMD51, SAME51, SAME53 and SAME54 series devices.
- Added flash programming support for Cypress PSoC 4xxDS family devices.
- Added flash programming support for Infineon IMCxxxx_0128 / IMMxxxx_0128 series devices.
- Added flash programming support for NXP K32W series.
- Added flash programming support for NXP KW35/36 series.
- Added flash programming support for NXP KW35/36 series.
- Added flash programming support for NXP LPC54101 and LPC54102 series devices.
- Added flash programming support for NXP LPC844 and LPC845 series devices.
- Added flash programming support for NXP QN908x series devices.
- Added flash programming support for ST STM32F72xxx and STM32F73xxx series devices.
- Added flash programming support for ST STM32L45x and STM32L46x series devices.
- Added flash programming support for ST STM32L49x and STM32L4Ax series devices.
- Added flash programming support for TI CC2640R2F.
- Added flash programming support for TI MSP432P401x and MSP432P411x series devices.
- Added new J-Link script file function AterResetTarget() which can be used to perform actions after reset.
- Added QSPI flash programming support for Maxim MAX32560 series devices.
- Added QSPI flash programming support for Maxim MAX32565, MAX32566 and MAX32635 series devices.
- Added some missing NXP K32W device names.
- Added support for the Cortex-R8 core.
- Added support for the Verify() function of Open Flashloader (CMSIS) based flash algorithms.
- Analog Devices ADuCM3xx: Under special circumstances, flash programming could fail. Fixed.
- Connecting to Cortex-M devices which had another implementer than ARM in the CPUID register, failed. Fixed.
- Connecting to the Cortex-M4 of the iMX7ULP device did not work. Introduced in V6.15b. Fixed.
- Cortex-M: If user specified command string "SetRestartOnClose = 0", it could happen that CPU was restarted on debug session close. Fixed.
- Depending on the format of the elf file, passed for a Open Flashloader, the J-Link DLL read incorrect device description information. Fixed.
- Improved JTAG chain auto-detection for unknown JTAG TAPs.
- Instruction set simulation could lead to internal error "Register x already marked as valid" on ARM v8M based devices. Fixed.
- J-Link-OB-S124: Free flash breakpoints for Renesas Synergy series did not work properly. Fixed.
- NXP Kinetis series: Attach to a running CPU did not work. Introduced in V6.15d. Fixed.
- NXP LPC18xx / LPC43xx: Under special circumstances, unlimited number of breakpoints in QSPI flash did not work. Fixed.
- Open Flashloader: If the specified loader file was invalid, the J-Link DLL crashed. Fixed.
- Open Flashloader: The DLL did not handle flashloader files with more than 8 flash sector blocks correctly. Fixed.
- Open Flashloader: The J-Link DLL was not able to load flashloader elf files with incorrect ELF information (2 different variables stored at the same address). "Fixed".
- Open Flashloader: When specifying more than 7 flash blocks, flash programming failed. Fixed.
- Optimized JTAG chain detection sequence (shortened number of bits being shifted)
- Precompiled PCodes can now be passed as J-Link script files. (Allows to pass non-human-readable script files)
- Renesas RZ/T1: If the device was protected and an incorrect IDCODE was entered by the user, it could happen that the J-Link software did try to unlock the debug interface multiple times. As the authentication interface of the RZ/T1 only allows to try to unlock the debug interface 3 times after a power-cycle, this could lead to unwanted behavior. Fixed.
- Some "Cypress" devices were still listed as "Fujitsu". Fixed.
- Some "Cypress" devices were still listed as "Spansion". Fixed.
- Some "Microsemi" devices were still listed as "Actel". Fixed.
- Some "NXP" devices were still listed as "Freescale". Fixed.
- Some "Silicon Labs" devices were still listed as "Energy Micro". Fixed.
- Some "TI" devices were still listed as "Luminary". Fixed.
- Target current was not shown in the control panel for some J-Link/Flasher models. Fixed.
- The QN9080x are no longer allowed to program security configuration, now there are special devices allowing this.
- The QN9080x did not always have the flash memory remapped to 0x00000000 after a reset. Fixed.
- Under special circumstances, the J-Link DLL reported an error if CPU clock could not be measured even if the CPU clock was not required. Fixed.
- Under special circumstances, the total flash size displayed in the J-Link DLL device selection dialog for multi-bank devices was not shown correctly. Fixed.
- VCOM was interrupted by a connect to a target until a new baud rate was set. Fixed.
- When using normal reset with ARM Cortex-M prototyping system and Cortex-M23 / M33, many warnings were issued. Fixed.
Firmware
- Added FTP server to Flasher models with ETH. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher PPC V4, Flasher RX V4
- Added support for the Verify() function of Open Flashloader (CMSIS) based flash algorithms. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- Flasher Portable: Auto power off did not work when in finished state. Fixed.
- Flasher: Improved stand-alone mode programming for NXP Kinetis-E, Kinetis-K, Kinetis-L and Kinetis-M series devices to be able to handle devices with enabled write protection.
- Idle state of the SWCLK signal was erroneously set to HIGH while it should be LOW. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10
- Measuring load on pin 19 (5V supply) could return incorrect values if no load was present. Fixed. Affected firmwares: J-Link Lite V9, J-Link Lite Cortex-M V9
- Nordic Semiconductor NRF52 series devices: Under special timing circumstances, flash programming of secured devices could fail. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher Portable PLUS, Flasher PPC V4, Flasher RX V4
- Renesas Synergy devices: Flash programming did not work in stand-alone mode. Fixed. Affected firmware: Flasher Portable PLUS
- Some J-Links did not support __probe attribute for J-Link script files. Fixed. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10, J-Link BASE V9, J-Link PLUS V9, J-Link EDU V9, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Trace for Cortex-M, J-Link Lite V9, J-Link Lite Cortex-M V9
- Under special circumstances, #verify command did not work in stand-alone mode. Introduced in V6.15c. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- Under special circumstances, VCOM direction J-Link -> Target did not work properly (characters could have been swallowed). Fixed. Affected firmwares: J-Link-OB-STM32F072-CortexM, J-Link-OB-STM32F072-128KB-CortexM, J-Link-OB-STM32F072-CortexAR
- Under special circumstances, verify could fail in stand-alone mode. Introduced in V6.14g. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- Under special circumstances, verify via CRC did not work for Open Flashloader (CMSIS) based flash algorithms. Introduced in V6.15a. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- VTref was always measured as 0V, even if voltage was present. Fixed. Affected firmwares: J-Link EDU Mini
GDB Server
- IP addresses were not shown correctly. Fixed.
- Multiple instances of the GDB Server were possible on windows. Fixed.
J-Flash
- "Disable flash bank" option in the project settings was not considered in stand-alone mode. Fixed.
- Action on J-Flash start can now be configured in the J-Flash Global settings dialog.
- Drag & drop a J-Flash project on the executable did not work. Introduced in V6.15. Fixed.
- Open Flashloader: Improved error handling if the flashloader file specified in the JLinkDevices.xml is invalid.
- Projects with older vendor names e.g. "Freescale" could not be opened. Introduced in V6.15d. Fixed.
- Projects with R7FS7G2 and R7FS3A7 were not opened correctly. Fixed.
- Since V6.15, J-Flash closed on errors during command line options. Reverted behavior back so J-Flash stays open. Introduced in V6.15. Fixed.
- Under certain conditions, if 2KB or less RAM was available on a target MCU, J-Flash created a .CFG file for stand-alone mode which did not work. Fixed.
- Under special circumstances, command line mode did not work when having third party remote access applications running in parallel. Fixed.
- Under special circumstances, stand-alone mode did not work if the data of a Flashbank other than the last one was not 2KB aligned. Fixed.
J-Flash SPI
- Added support for dedicated 4 byte address mode.
- Added support for different status register layouts.
- Updated the project settings GUI dialog.
J-Link Package
- Moved JLink_x64.dll from sub directory "bin_x64" to the top level of the installation directory.
Remote Server
- IP addresses were not shown correctly. Fixed.
STM32 Utility
- Added support for ST STM32F72xxx and STM32F73xxx series devices.
- Added support for STM32L0xxxx devices.
Version V6.14h (2017-05-10)
J-Flash
- Stalled during creation of stand-alone mode data files when the flash features different sector sizes in one continuous range and certain conditions were met. Introduced with 6.14c / 6.15a. Fixed.
RTT Viewer
- [RTT Viewer] closed itself, if an error message was received from the DLL. Fixed.
- [RTT Viewer] tried to read RTT data while handling error messages from the DLL. Fixed.
Version V6.14g (2017-05-09)
Commander
- Commands "testnrspeed" and "testnwspeed" could end up in an endless loop with some combinations of <NumBytes> and <NumReps>. Fixed.
DLL
- Analog Devices ADuCM331: Improved the flash algorithm so it is able to handle the temporary write protection (through the FEEPROP register).
- Analog Devices ADuCM331: Under special circumstances, flash algorithm did not return an error if erase failed due to active write protection. Fixed.
- Improved behavior for legacy ARM7 devices that need an initial reset pin toggle before debug interface gets responsive.
- J-Trace PRO for Cortex-M: Having multiple sessions with J-Trace PRO running in parallel and streaming via IP, did not work properly (local port allocation issue on PC side). Fixed.
- J-Trace PRO for Cortex-M: Streaming trace via IP did not work properly from inside VM via network adapters configured as NAT. Fixed.
- Linux: When running a Linux VM on a Mac host, connecting to J-Link could take considerably longer (about half a second) than in V6.12 series versions. Fixed.
- Mac: When running a Mac VM on a Mac host, connecting to J-Link could take considerably longer (about half a second) than in V6.12 series versions. Fixed.
- Some ADSP-CM41... target names did not work. Fixed.
GDB Server
- "JTAGConf" command line option did not support negative values which are required to configure auto-detect. Fixed.
- Added new command line option "jlinkscriptfile" which behaves similar to "scriptfile" (deprecated).
J-Link Package
- Linux: Fixed 99-jlink.rules line-endings.
Version V6.14f (2017-05-04)
DLL
- Added flash programming support for Microchip (Atmel) SAMC20J15A and SAMC21J15A series devices.
- Added flash programming support for NXP QN908x series devices.
- J-Link Script File function JLINK_ReadDAP() returned an incorrect value. Fixed.
- Linux: When running a Linux VM on a Mac host, USB performance was poor (Other setups were not affected!). Introduced with V6.14 when improving streaming trace via USB for J-Trace PRO. Fixed.
GDB Server
- When using GDB Server with GDB V7.12 and later versions, unintentional resets were issued (problem caused by change inside GDB, not GDB Server). Fixed.
Version V6.14e (2017-04-27)
Commander
- Added a new command "JTAGConfig" which allows to specify the jtag config during execution (e.g. from within a J-Link command file).
DLL
- Added debug support for Cypress CYW43907 series devices.
- Streaming trace: When streaming via Ethernet, on some Windows systems with Windows firewall enabled, trace packets were not received when firewall was enabled, even if it was configured correctly. Fixed.
- Streaming trace: When streaming via Ethernet, under special circumstances error message "Unknown trace data packet detected" could occur when starting + stopping the CPU multiple times. Fixed.
- VCOM was interrupted by a connect to a target until a new baud rate was set. Fixed.
Firmware
- Flash programming of secured STM32F2 series devices did not work. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- Streaming trace: Under special circumstances error message "Unknown trace data packet detected" could occur when starting + stopping the CPU multiple times. Fixed. Affected firmwares: J-Trace PRO V1 Cortex-M
- Under special circumstances, verify via CRC did not work for Open Flashloader (CMSIS) based flash algorithms. Introduced in V6.15a. Fixed.
Version V6.14d (2017-04-19)
DLL
- Added debug support for ON SEMI "RSL10" series devices.
- Added some device aliases for Renesas Synergy devices.
- Added support for Renesas Synergy R7FS12878.
- Added support for Renesas Synergy R7FS3A37A.
- Added support for Renesas Synergy R7FS3A678.
- Setting breakpoints while CPU is running did not work for Cortex-AR cores. Fixed.
- The QSPI / SPIFI flash algorithms did not handle the extended 4 byte address mode (EXTADD) correctly. Fixed.
- Under special circumstances, CFI compliant flash device detection did not work. Fixed.
- Updated AmbiqMicro Apollo device names in the J-Link software.
- Updated NXP KV10 / KV11 device names in the J-Link software.
Firmware
- Flasher: For NXP KE0x series devices, Flasher performed a mass erase via MDM-AP always. Improved so the mass erase is performed if required (device is secured), only.
- Flasher: Under special circumstances, Flasher filled unselected sectors with erased value in stand-alone mode. Fixed.
- Under special circumstances, stand-alone mode did not work when using the Open Flashloader (CMSIS). Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
GDB Server
- Logging of TCP traffic was accidentally removed. Fixed.
J-Flash
- Added new init / exit steps which allow to change the opened data file (WriteFile8, WriteFile16 and WriteFile32).
Version V6.14c (2017-03-31)
Commander
- During TDO output, the command "wjraw" truncated leading zeros in a byte. Fixed.
DLL
- "LPC4367" (device description passed to DLL by MCUXPresso) was recognized as "unknown" device. Fixed.
- Added debug support for the Cortex-M0 core of the NXP LPC541xx series devices.
- Added flash programming support for Microchip (Atmel) SAMC20N / SAMC21N series devices.
- Added support for ARM SWD v2 multi-drop.
- Added support for Nordic Semi nRF51801_xxAB series devices.
- Added support for Nordic Semi nRF52832_xxAB series devices.
- Devices that boot in dormant mode did not work properly when selecting SWD as debug interface (mainly affects some preliminary Cortex-M33 FPGA designs at this point). Fixed.
- Exec "DisableFlashDL" did not work correctly. Fixed.
- Implemented info message box for Flasher Portable units that run a faulty firmware that does not allow automatic firmware updates.
- JLinkDevices.xml was not shipped with .deb and .rpm packages. Fixed.
- NXP MK81FN256xxx15: Added flash programming support.
- Renesas S124: Automatic CPU clock speed detection did not work correctly (calculated speed was double the real one). Fixed.
- Silicon Labs EFx32G12: Added flash programming support for the bootloader section 0x0FE10000 - 0xFE19800 (38 kB).
- Silicon Labs EFx32G13: Added flash programming support for the bootloader section 0x0FE10000 - 0xFE14000 (16 kB).
- Some older Linux kernels did not work correctly with current J-Link models any longer. Introduced with V6.14 when optimizing performance for streaming trace. Fixed.
- Under special circumstances it could happen that J-Link drove SWDIO pin LOW while target drove it HIGH, during the connect sequence. This did not cause any problems for any target so far. Fixed.
- Under special circumstances, flash programming could fail for Renesas RX231 target devices. Fixed.
- Under special circumstances, the total flash size displayed in the J-Link DLL device selection dialog for multi-bank devices was not shown correctly. Fixed.
- Under very special circumstances, J-Link Commander could crash. Fixed.
Firmware
- Added Open Flashloader (CMSIS) flash programming support for Flasher stand-alone mode. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- Added support debugging multiple devices in an ARM SWD multi-drop system simultaneously. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- Added support debugging multiple devices in an ARM SWD multi-drop system simultaneously. Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M
- Added support for VCOM Affected firmwares: J-Link-OB-BBC-micro:bit
- Extended VCOM hook function functionality. Affected firmwares: J-Link-OB-XMC4200
- Flasher Portable: Auto power off did not work when in finished state. Fixed.
- Flasher: Flash programming in stand-alone mode did not work for Renesas Synergy S7G2 series devices. Fixed
- Flasher: The bootloader always exposes the whole flash memory as MSD device, including any secure area. Fixed. Affected firmwares (bootloader): Flasher ARM V4, Flasher PRO V4, Flasher PPC V4, Flasher RX V4
GDB Server
- Under Linux / macOS, after repeatedly opening and closing a connection to the GDB Server, GDB Server stopped accepting new connections. Fixed.
J-Flash
- Under certain conditions, if 2KB or less RAM was available on a target MCU, J-Flash created a .CFG file for stand-alone mode which did not work. Fixed.
- Under special circumstances, command line mode did not work when having third party remote access applications running in parallel. Fixed.
- Under special circumstances, stand-alone mode did not work if the data of a Flashbank other than the last one was not 2KB aligned. Fixed.
J-Flash SPI
- Under special circumstances (when using large data files), J-Flash SPI could crash. Fixed.
- Under special circumstances memory was not freed. Fixed.
- Under special circumstances, save as did not work for *.bin files. Fixed.
J-Flash SPI CL
- Under special circumstances, an error occurred while establishing a connection to the SPI flash. Fixed.
Version V6.14b (2017-03-08)
DLL
- J-link OB SAM3U on Quintic/NXP MiniDK: Error message "The connected J-Link has been designed to work with devices made by Quintic only" appeared when trying to debug the QN9020 device on the board. Introduced with V6.14. Fixed.
- Renesas Synergy S124: Erasing of option setting memory did not work properly if an IDCODE etc. was already programmed. Fixed.
- Renesas Synergy S5 series: Added support for internal data flash.
- Renesas Synergy S5: Flash cache was not invalidated correctly after flash programming, which could cause issues when using unlimited flash breakpoints feature of J-Link. Fixed.
- Software could crash if garbage was found in the feature area of J-Links (only happened on open platforms like OpenSDA). Fixed.
- Under special circumstances, flash programming could fail for Renesas RX231 target devices. Fixed.
- Under special circumstances, reset of Silicon Labs EFM / EFR devices could fail. Fixed.
Firmware
- could hang if multiple of 2 KB memory have been read. Fixed. Affected firmwares: J-Link-OB-RX621-ARM-SWD
- Under special circumstances, the feature area of the J-Link contained garbage which could result in incorrect behavior of the firmware. Fixed. Affected firmwares: J-Link OpenSDA. Firmware 17-02-28: https://www.segger.com/downloads/jlink#JLinkOpenSDABoardSpecificFirmwares
GDB Server
- Changed RTOS plugins to dynamic libs for Mac. Improved loading algorithm for RTOS libs.
- GDB Server did not behave correctly, if RTOS_GetNumThreads() returns 0. Fixed.
- RTOS plugins did not load under linux/mac, if given with an absolute path. Fixed.
Version V6.14a (2017-02-27)
DLL
- CMSIS algorithms compiled as position independent code threw an error when us ed. Introduced with V6.12j. Fixed.
Version V6.14 (2017-02-23)
Commander
- Added new command "WaitHalted" which stops command file execution until the CPU is halted or a given timeout exceeds.
DLL
- Added debug support for Broadcom BCM43907 device series.
- Added Dialog Semiconductor DA14680, DA14681 series devices to the list of known device names.
- Added flash programming support for Analog Devices ADuCM3027/ADuCM3029 device series.
- Added flash programming support for Nuvoton MINI58xxx series devices.
- Added flash programming support for Nuvoton NUC230 and NUC240 device series.
- Added flash programming support for SiLabs EFR32xG12xxx, EFR32xG13xxx, EFR32xG12xxx and EFR32xG13xxx series devices.
- Added flash programming support for some missing ST STM32L0xxx series devices.
- Added flash programming support for Toshiba TMPM47x device series (Cortex-M4).
- Added new exec command "SetRAMUsageLimit" which allows to override to limit the max. RAM usage during flash programming.
- Added new exec command which allows specifying the core index to be used. Syntax: "SetCoreIndex <CoreIndex>".
- Added possibility to call command strings from J-Link script files
- Added possibility to override trace port width to be used, via J-Link script files
- Added QSPI flash algo for Atmel SAMA5D2 (works on SAMA5D2XPLAINED evaluation board).
- Added QSPI flash programming support for iMX6UL series devices (MCIMX6G0, MCIMX6G1, MCIMX6G2 and MCIMX6G3).
- Added QSPI flash programming support for NXP iMX6ULL series devices.
- Added QSPI flash programming support for NXP LPC5460 series devices.
- Added QSPI flash programming support for NXP MCIMX6Y7 (iMX6ULL) series devices.
- Added secured device detection for Nordic Semi nRF51 series devices.
- Added SPIFI flash programming support for Adesto AT25SL128, AT25SL641, AT25SF641 and AT25SL321SPI flashes.
- Added support for Ambiq Apollo 2 series devices.
- Added support for NXP LPC54604, LPC54616, LPC54618, LPC54S606, LPC54S608, LPC54S616, LPC54S618 device series.
- Added support for ST BLUENRG1 series devices.
- Function pointer was not checked for NULL before call. Fixed.
- Implemented command string "SetRTTStreamingMode" to allow to block certain RTT read accesses from certain callers (e.g. to block read accesses via DLL API and only allow TELNET read accesses)
- Improved error detection for streaming trace in case invalid A-sync packets are received.
- Introduced new exec "SetMSGBoxTimeout" which can be used to configure the timeout for all information-level message boxes. It supersedes the existing exec "SetBatchMode", which will still be available for legacy applications and scripts. "Exec SetBatchMode 1" internally is the same as "exec SetMSGBoxTimeout 5000"
- Introduction of support for unary NOT (~) caused problems with some binary operators as other unsupported unary operators were parsed, by accident. Introduced in V6.12i. Fixed.
- Linux: Updated USB implementation of J-Link / J-Trace which improves performance especially for streaming trace via USB
- macOS: Updated USB implementation of J-Link / J-Trace which improves performance especially for streaming trace via USB
- NXP iMX6UL / iMX6ULL: Under special circumstances, QSPI flash programming did not work. Fixed.
- Optimized CMSIS flash algorithm handling. 25% performance increase.
- Programming failed for Maxim MAX3263x devices under special circumstance. Fixed.
- RTT Telnet connection was slow on sending data. Fixed.
- Some features like ETB trace did not work properly when using J-Link in the IAR Eclipse plugin. Fixed.
- Some new NXP (Freescale) KEA128, KEA64 and KEA8 devices were unknown to the J-Link DLL ("S9KEA" instead of "SKEA" prefix). Added.
- SPIFI flash programming: Added support for GigaDevice GD25Q05B, GD25Q10B, GD25Q20C, GD25Q40C, GD25Q80C, GD25Q16C, GD25Q32C, GD25Q64C, GD25Q127C, GD25Q128C, GD25Q256C, GD25Q512M
- TI MSP432: For some BSL versions, connect could fail. Fixed.
- Timestamps for flash programming were incorrect. Fixed.
- Unsecure dialog assumed "Yes" instead of "No", if closed via escape button. Fixed.
- User could specify enormous timeouts for JLINKARM_ReadDCC() and JLINKARM_WriteDCC() that even exceeded J-Link communication protocol timeouts. Added automatic timeout limit.
- Users can know select "Do not unsecure and do not ask me again" in unsecure device dialogs.
Firmware
- Debugging RX devices via JTAG could fail (e.g. device was detected as big endian while it really was little endian etc.). Introduced in V6.12c. Fixed. Affected firmwares: J-Link PRO V4, J-Link ULTRA+ V4
- Delaying trace signals did not work correctly. Fixed. Affected firmwares: J-Trace PRO V1 Cortex-M
- Flasher: Added stand-alone mode support for secured TI CC13xx processors.
- Tracing via pins did not work properly on Infineon XMC4xxx series devices and older NXP Kinetis K60 derivatives. Fixed. Affected firmwares: J-Trace PRO V1 Cortex-M
- When doing streaming trace via USB on slow hosts (e.g. inside virtual machines), under very rare circumstances, it could happen that garbage was transmitted as trace data. Fixed. Affected firmwares: J-Trace PRO V1 Cortex-M
GDB Server
- Under Linux / macOS, after repeatedly opening and closing a connection to the GDB Server, GDB Server stopped accepting new connections. Fixed.
J-Flash
- Added *.s28 (mot) file format support.
- Added flash programming support for Analog Devices ADuCM3027/ADuCM3029 device series.
- Added flash programming support for Nuvoton MINI58xxx series devices.
- Added flash programming support for Nuvoton NUC230 and NUC240 device series.
- Added flash programming support for SiLabs EFR32xG12xxx, EFR32xG13xxx, EFR32xG12xxx and EFR32xG13xxx series devices.
- Added flash programming support for Toshiba TMPM47x device series (Cortex-M4).
- Added QSPI flash programming support for iMX6UL series devices (MCIMX6G0, MCIMX6G1, MCIMX6G2 and MCIMX6G3).
- Added QSPI flash programming support for NXP iMX6ULL series devices.
- Added support for Ambiq Apollo 2 series devices.
- Added support for ST BLUENRG1 series devices.
- Init / Exit step type "Comment", adds the comment to the LOG window of J-Flash.
- Optimized CMSIS flash algorithm handling. 25% performance increase.
- Programming failed for Maxim MAX3263x devices under special circumstance. Fixed.
- ST SPC560B (PPC): Under special circumstances (devices with empty flash), flash programming did not work. Fixed.
- Timestamps for flash programming were incorrect. Fixed.
J-Flash Lite
- From now, the last used device is preselected in the startup dialog.
J-Flash SPI
- Added SPI flash programming support for Adesto AT25SL128, AT25SL641, AT25SF641 and AT25SL321SPI flashes.
- IDCheck did not work properly. Fixed.
J-Flash SPI CL
- In Batch mode, J-Flash SPI CL aborted if a User defined SPI ID was not found in the list of supported SPI flashes. Fixed.
J-Link Package
- Windows: Updated USB driver of J-Link / J-Trace which improves performance especially for streaming trace via USB by app. 100% (from 20 MB/s to 38 MB/s)
OFL
- Init and prepare functions were not called before reading flash memory. Fixed.
Remote Server
- Dialog window sometimes was not correctly updated. Fixed.
- TCP connection was not closed properly under Linux/Mac. Fixed.
RTT Logger
- Added command line options.
RTT Viewer
- Added "bright theme" command line option.
- Added option to specify a J-Link script file.
Version V6.12j (2017-02-15)
Commander
- SETB instruction was disassembled incorrectly. Fixed.
DLL
- Added command string "TraceSampleAdjust"
- Added new exec command which allows specifying the core index to be used. Syntax: "SetCoreIndex <CoreIndex>".
- Added possibility to call command strings from J-Link script files
- Command string "TraceSampleAdjust" reported an error if there was one or more whitespace characters between the pin identifier and the '=' character. Fixed.
- Flash size of devices added via JLinkDevices.xml was not shown correctly in the device selection dialog. Fixed.
- Function pointer was not checked for NULL before call. Fixed.
- Streaming trace via IP did not work properly if special constellations of network adapters (VM, real ones, bluetooth, ...) were present on the PC. Fixed.
- TI MSP432: For some BSL versions, connect could fail. Fixed.
- Under special circumstances, tracing on Cortex-M7 devices could lead to "unknown trace packet" errors even if trace data was correct. Fixed.
Firmware
- Flasher: Under special circumstances, SPIFI flash programming did not work in stand-alone mode. Fixed.
- Flasher: Under special circumstances, SPIFI flash programming did not work in stand-alone mode. Fixed.
- Tracing via pins did not work properly on Infineon XMC4xxx series devices and older NXP Kinetis K60 derivatives. Fixed. Affected firmwares: J-Trace PRO V1 Cortex-M
J-Flash SPI
- IDCheck did not work properly. Fixed.
J-Scope
- Some ELF files with DWARF 3/4 debug informations could not be analyzed correctly. Fixed.
Remote Server
- Dialog window sometimes was not correctly updated. Fixed.
- TCP connection was not closed properly under Linux/Mac. Fixed.
Version V6.12i (2017-02-03)
DLL
- Added flash programming support for ST STM32F413 and STM32F423 device series.
- Added new script file function (OnTraceStart()) which allows to override the device specific trace setup function (e.g. to initialize the trace pins).
- Added support for unary NOT operator (~) to J-Link script file language.
- exec "SetRAWTRACEPinDelay" did not return an error if the connected J-Trace did not support the feature. Fixed.
- exec "SetRAWTRACEPinDelay" extended to support setting delay for multiple data pins at once via TD<Start>..<End>=<Delay>
- Internal flash erase failed for some memory ranges on STM32L4 dual bank devices. Fixed.
- J-Link script files can now passed to / specified in the J-Link software before a connection to a J-Link is established. (Makes it easier to use J-Link script files in some IDEs).
- NXP LPC43xx: Under special circumstances, QSPI flash programming did not work for certain SPI flashes (e.g. N25Q128A). Fixed.
- SiLabs EFM23 / EFR32 series: When programming the user page, the lock page has been erased. Fixed.
- SiLabs EFM32 / EFR32: Added unlocking in case of a locked device has been detected.
- Some NXP KEAZNxx device names were not recognized correctly. Fixed.
- The trace pin setup did not work for STM32L series devices. Fixed.
Firmware
- Configuring trace pin delays did not work properly. Fixed. Affected firmwares: J-Trace PRO V1 Cortex-M
- internal pull-up on nRESET line was not enabled, by accident. Introduced in V6.12g. Fixed. Affected firmwares: J-Link OB SAM3U
J-Flash
- Added flash programming support for ST STM32F413 and STM32F423 device series.
- SiLabs EFM32 / EFR32: Under special circumstances, unlocking of locked devices did not work / unlocking of not locked devices resulted in an error. Fixed.
- The core ID check was not performed when SWD was selected. Fixed.
Version V6.12h (2017-02-01)
DLL
- SiLabs EFM23 / EFR32 series: When programming the user page, the lock page has been erased. Fixed.
Version V6.12g (2017-01-27)
Commander
- Under special circumstances, "ShowEmu" command did not show all connected J-Links. Fixed.
Configurator
- Under special circumstances, not all J-Links connected via USB were listed. Fixed.
DLL
- Added missing device names for NXP iMX6ULL series devices (MCIMX6Y0, MCIMX6Y1, MCIMX6Y2).
- RTT block auto-detection did not work properly for NXP Kinetis MKL27Z32xxx4, MKL27Z64xxx4 series. Fixed.
Firmware
- Added firmware image for OpenSDA on FRDM-KW24D512. More info: https://www.segger.com/downloads/jlink#JLinkOpenSDABoardSpecificFirmwares
- Flasher: The telnet RX buffer was not sufficient for long commands (#AUTO PATCH). Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- SPI target interface did not work properly at max. speed. Fixed. Affected firmwares: J-Link ULTRA+ V4, J-Link PRO V4, Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- Under special circumstances, it could happen that target interface pins were driven from startup, even if no debugger was connected to the OB. Fixed. Affected firmwares: J-Link OB SAM3U
J-Link Package
- Installer: Windows: Start menu entries were not created when starting the installer in silent mode (/S command line option). Fixed.
- Installer: Windows: USB drivers were not installed when starting the installer in silent mode (/S command line option). Fixed.
Version V6.12f (2017-01-13)
DLL
- Added debug support for TI RM44 device series.
- Added flash programming support for the Customer Information Block (CIB) of Silicon Labs EM358x and EM359x series devices.
- For Silicon Labs EM351 / EM357 series devices, Customer Information Block (CIB) programming did not work due to an incorrect CIB base address. Fixed.
- On some Windows based PCs, under very rare circumstances, it took Windows app. 6 seconds to recognize a detach of J-Link during a firmware update which could cause the firmware update to fail because the J-Link software had a 5 seconds timeout. Fixed.
- RTT block auto-detection did not work properly for NXP Kinetis MKW20Z160xxx4, MKW30Z160xxx4, MKW40Z160xxx4 if RTT block was located at addr. 0x20003000 or above. Fixed.
- Under special circumstances, software breakpoints did not work. Fixed.
J-Flash
- Under special circumstances, J-Flash could not write the *.ini file when running in parallel mode. Fixed.
Version V6.12e (2017-01-06)
Commander
- Under certain conditions, swospeed displayed an invalid value if the connection to J-Link failed. Fixed.
DLL
- Added new exec command which allows to read a specified memory region into the trace cache. Syntax: ReadIntoTraceCache <Addr> <NumBytes>.
- Cortex-M: When closing a debug session, some "debug power up request" bits were not cleared, which could result in higher power consumption of the target device, after the debug session has been finished. Fixed.
- Extended the "map add" exec command to allow specifying alias regions. Example: map add <SAddr>-<EAddr> <RegionType> <MemType> [<AliasAddr>] [<AliasSize>].
- Implemented command string "SetRTTStreamingMode" to allow to block certain RTT read accesses from certain callers (e.g. to block read accesses via DLL API and only allow TELNET read accesses)
- JLINKARM_EMU_GetDeviceInfo() did not return device info for the selected device if called with iEmu 0xFFFFFFFF. Fixed.
- macOS: Under special circumstances, it could happen that a crash happened when opening/closing a J-Link connection very fast, many times in a row. Fixed.
- NXP LPC824M201 could not be selected as target device. Introduced in V6.12c. Fixed.
DLL Updater
- 64-bit installations of Ozone were not found. Fixed.
- When updating 64-bit installation of supported IDEs, it could happen that a "sJLinkDevices.xml" file (note the 's' at the beginning) was created by accident (no negative side effects). Fixed.
Firmware
- (Flasher): Under special circumstances a configuration conflict between secure and public area was reported, even if it was not the case. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable, Flasher PPC V4, Flasher RX V4
- Added support for VMSD (basis for drag & drop programming support) Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Link EDU V10
- OpenSDA: Under very special circumstances it could happen that when sending data to the target via VCOM, the second byte sent after powering up OpenSDA was swallowed. Fixed. New firmware images: https://www.segger.com/downloads/jlink#JLinkOpenSDABoardSpecificFirmwares
GDB Server
- RTOS plug-in were not found under linux, if the executable has been started using PATH environment variable. Fixed.
J-Flash
- In command-line mode, information message boxes of the J-Link DLL were not omitted. Fixed.
Version V6.12d (2016-12-21)
DLL
- Connecting to TI AM1705 devices could fail with error "Cannot find ICE-Pick (IDCODE mismatch)" even though the IDCODE was read correctly. Fixed.
- Control panel, RTT tab: Added possibility to send CR + LF on <Return> when sending RTT data to target
- When using "MRU device list" feature of J-Link SW (as for example RTT Viewer does), getting the list of the most recently used device names could fail if called after a connection to J-Link was closed before. Fixed.
Firmware
- J-Link did not work properly when long JTAG sequences (> 255 bytes) were output at once. Mainly happens when using legacy ARM 7/9 targets. Introduced with V6.12c. Fixed Affected firmwares: J-Link PRO V4, J-Link ULTRA+ V4
- Tx-Idle level for UART, used for virtual COM port, was LOW instead of HIGH which could cause problems when using VCOM. Fixed. Affected firmwares: ST-LINK OB V2 (available via latest STLinkReflash utility from SEGGER download area), ST-LINK OB V2-1 (available via latest STLinkReflash utility from SEGGER download area)
RTT Viewer
- Now remembers the 5 most recent devices name used.
- While in "Send on Enter" mode, RTT Viewer now has "command-line-like" history
Version V6.12c (2016-12-16)
Commander
- Linux: "selemu" command did show incorrect list of connected J-Links if more than one J-Link was connected to the PC. Introduced in V6.12a. Fixed.
DLL
- Added flash programming support for NXP LPC832M101 and LPC834M101 series devices.
- Added flash programming support for some new Nuvoton MINI51xxx, MINI52xxx, MINI54xxx and MINI55xxx series devices.
- Added flash programming support for the entire User Row Space (256 bytes in size) for the Microchip (Atmel) SAMD, SAMH, SAML, SAMR and SAMW series devices.
- Added JLINK_MemRegion() to J-Link script file language. Further info: See user guide.
- Added support for Nordic Semi nRF52840_xxAA device series.
- Added support for NXP LPC54604, LPC54616, LPC54618, LPC54S606, LPC54S608, LPC54S616, LPC54S618 device series.
- Security of nRF51 devices was not checked on connect. Fixed
- Security of nRF51 devices was not checked on connect. Fixed
- When specifying JLINK_CORESIGHT_CoreBaseAddr in script files, ROM table Coresight component search was not skipped correctly on Cortex-M devices. Fixed.
- When used inside SEGGER Ozone, the warning "Could not find breakpoint with handle 0xFFFFFFFF" was thrown. Introduced in V6.12. Fixed.
Firmware
- Improved memory write speed when using SWD by up to 40% under special circumstances. Affected firmwares: J-Link PRO V4, J-Link ULTRA+ V4
- Improved overall speed for JTAG and SWD transactions by up to 20% Affected firmwares: J-Link PRO V4, J-Link ULTRA+ V4
GDB Server
- Linux version exited itself while sending SWO data, if SWO socket was closed. Fixed.
- The FreeRTOS plugin could crash the GDB Server in case of a zero length task name. Fixed.
J-Flash
- Added file format support for *.s37 (srec) files.
- Added flash programming support for NXP LPC832M101 and LPC834M101 series devices.
- Added flash programming support for some new Nuvoton MINI51xxx, MINI52xxx, MINI54xxx and MINI55xxx series devices.
- Added flash programming support for the entire User Row Space (256 bytes in size) for the Microchip (Atmel) SAMD, SAMH, SAML, SAMR and SAMW series devices.
RTT Viewer
- Option to specify a J-Link script file is shown if "Existing Session" is selected. Fixed.
Version V6.12b (2016-12-05)
DLL
- When used inside SEGGER Ozone, the warning "Could not find breakpoint with handle 0xFFFFFFFF" was thrown. Introduced in V6.12. Fixed.
Version V6.12a (2016-12-02)
DLL
- On STM32F4 devices with 1 MB flash memory, dual bank mode was not handled correctly during erase. Fixed.
- Renesas RZ/T1: Under special circumstances, devices which were locked via an IDCODE were not detected as locked properly, so no authentication was performed, resulting in a non-functional debug session. Fixed.
- When connecting to a Renesas R5F52306 (RX230), an "unknown sub-family" warning was thrown. Fixed.
- Wrong function was used for chip erase. Fixed.
Firmware
- J-Link V10: When a connection to J-Link was opened, with no target connection requested, J-Link started driving the pins of the target interface. Fixed.
- J-Link V9: When a connection to J-Link was opened, with no target connection requested, J-Link started driving the pins of the target interface. Fixed.
- Under special circumstances HSS did not return an error if total number of bytes, to be sampled periodically, exceeded the buffer capacities of J-Link. Fixed. Affected firmwares: J-Link V9, J-Link V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M
J-Flash
- Wrong function was used for chip erase. Fixed.
SWO Viewer
- Added command line switches "-usb <SerialNumber>" and "-ip <IPAddr>" which allows to configure the host interface.
Version V6.12 (2016-11-25)
Commander
- Updated testnrspeed / testnwspeed commands to accept transfer sizes up to 64 KB per loop.
DLL
- Added new script file variable "JLINK_AllowFlashCacheState" which can be used to enable / disable the flash cache.
- Added official names for ARM v8M Baseline and Mainline: Cortex-M23 and Cortex-M33.
- Added official names for ARM v8M Baseline and Mainline: Cortex-M23 and Cortex-M33.
- Added PCodes to JLINKARM_DEVICE_GetInfo().
- Added support for NXP iMX6UL series devices.
- Added support for ST STM32H7 series devices.
- Changed unsecure message box warning text for nRF51.
- Flash programming did not work for Silicon Labs EFR32MG series devices. Fixed.
- For multi-bank devices the flash area information was not created when requesting the device info. Fixed.
- If CPU was reset while SWO running, the device specific initialization was not performed again. Fixed.
- Linux: Connecting to EDBG, running J-Link OB firmware, did not work properly. Fixed.
- macOS: Connecting to EDBG, running J-Link OB firmware, did not work properly. Fixed.
- Removed secured device detection for Nordic Semi nRF51 series devices.
- SWO device specific initialization for LPC5411x was not correct. Fixed.
- Under special circumstances, flash programming did not work for SAMG55 series devices. Fixed.
- Under very rare circumstances, when setting/clearing breakpoints while the CPU was running, the CPU was halted even if not necessary (e.g. clearing hardware breakpoints only and the CPU supports this during program execution)
- When clearing breakpoint after the connection to the CPU was lost (low power state, target disconnected due to bad cable etc.), it could happen that the J-Link software ended up in an endless recursion. Fixed.
- When doing instruction single stepping with streaming trace enabled, it could happen that trace was not restarted correctly after a few steps. Fixed.
GDB Server
- Added additional error checks for "qSeggerSWO:*" commands, added info to these commands to the manual.
- Added new command line argument "-listprobes <Interface>" which can be used to get a list of all connected J-Link debug probes.
- Added new command line argument "-powertarget <DelayMS>" which can be used to enable the J-Link supply voltage via Pin19 to power the target.
- SWO analyzer could crash under special circumstances. Fixed.
J-Flash
- Added error message if not all data could be programmed.
- Added log outputs for each saved/downloaded PCode file.
- Added option to disable flash banks.
- Added PCodes to JLINKARM_DEVICE_GetInfo().
- Added reference project file for nRF51822 devices which unlocks the device in the Init steps.
- Changed the main menu structure.
- Changed the production tab options.
- disabled flash banks should not disable the check if selected data fits into the sectors selected.
Version V6.10n (2016-11-18)
DLL
- Added debug support for TI CC3200 series
- Added flash programming support for Silicon Labs EZR32HG220F32, EZR32HG220F64, EZR32HG320F32 and EZR32HG320F64 series devices.
- Added new script file function to override the reset type used by the J-Link DLL in case of reset is issued.
- Added official names for ARM v8M Baseline and Mainline: Cortex-M23 and Cortex-M33.
- Added QSPI flash programming support for Renesas RZ/A1LU series devices (R7S721030, R7S721031 and R7S721034).
- Added two new J-Link script file functions which are executed right after and before flash programming (e.g. initial flash download or flash breakpoints): HandleBeforeFlashProg() and HandleAfterFlashProg()
- Added unsecure for nRF51.
- Cortex-M: When using backtrace over small code regions (backtrace between 2 breakpoints which have a few subroutines between them), it could happen that an empty list or a list full of addr. 0xFFFFFFF0 was shown (e.g. in Ozone). Fixed.
- Improved trace start/stop setup performance
- In case an error occurred during streaming trace, error messages were not output in a thread-safe way which could cause problems in some environments
- J-Trace PRO Cortex-M V1: Instruction trace in IAR EWARM and Keil uVision did not work correctly (no trace data was shown in instruction trace window). Fixed.
- Under special circumstances, flash programming did not work for NXP (Freescale) KL82 series devices. Fixed.
- Under special circumstances, R7FS5D97 devices were configured incorrectly during restore after a download to flash memory. Fixed.
- Under special circumstances, reset did not work properly for ADuCM350 series devices. Fixed.
Firmware
- OB-SAM3U128-NordicSemi: Mass erase could not be performed, if device was protected with protection level PALL. Fixed.
J-Flash
- Added flash programming support for Silicon Labs EZR32HG220F32, EZR32HG220F64, EZR32HG320F32 and EZR32HG320F64 series devices.
- Added QSPI flash programming support for Renesas RZ/A1LU series devices (R7S721030, R7S721031 and R7S721034).
J-Flash SPI
- CRC on data file open was not calculated correctly. Fixed.
Remote Server
- Switched to SYS functions.
- UDP thread did not terminate on some Linux distributions. Fixed.
Version V6.10m (2016-11-10)
DLL
- Added flash programming support for NXP (Freescale) K27F / K28F device series.
- Added flash programming support for Renesas Synergy S5D9 series devices.
- Added flash programming support for Samsung ARTIK-020 and ARTIK-030 series devices.
- Added flash programming support for Silicon Labs BGMxxx and MGMxxx series devices.
- Clearing DHCSR.C_DEBUGEN and DEMCR.TRCENA on debug session close sth. halts or causes an exception on the target. Introduced with V6.10i. Reverting to previous behavior.
- Improved handling for streaming trace in case trace clock is enabled by application during execution and not available from the point where trace is started by the debugger
- In case the application did not set an external handler for warning outputs, these messages were swallowed. Fixed.
- STRACE could cause an access violation used on cores where STRACE is not supported (e.g. ARM7/9). Fixed.
- Streaming trace could a crash if no trace clock was provided by the target. Fixed.
- Under special circumstances, R7G2 devices were configured incorrectly during restore after a download to flash memory. Fixed.
- When accessing the same J-Link with multiple processes without explicitly selecting the J-Link via its S/N (through the API), an internal error indicating that the USB communication is not locked, could pop-up. Introduced in V6.10k. Fixed.
Firmware
- J-Trace PRO Cortex-M V1: Under special circumstances J-Link software reported unknown trace packets when trace data load was high. Fixed.
- J-Trace PRO Cortex-M V1: When streaming much trace data via IP (>= 80 MB/s) for a longer period of time (> 2 h), under special circumstances the IP interface of J-Trace could become unresponsive. Fixed.
J-Flash
- Added flash programming support for NXP (Freescale) K27F / K28F device series.
- Added flash programming support for Renesas Synergy S5D9 series devices.
- Added flash programming support for Samsung ARTIK-020 and ARTIK-030 series devices.
- Added flash programming support for Silicon Labs BGMxxx and MGMxxx series devices.
Version V6.10l (2016-07-11)
DLL
- ON Semi NCS36510 devices where not recognized by the J-Link DLL. Fixed.
- Some device names passed by CCS to the J-Link DLL where not recognized. Fixed.
- Updated license terms for J-Link BBC micro:bit
Version V6.10k (2016-11-04)
DLL
- Added support to unlock secured Nordic Semi nRF52 series devices.
- Flash programming of Analog Devices ADuCM331 device series did not work. Fixed.
- The ST-Link OB terms of use dialog was not displayed correctly in Embedded Studio. Fixed.
- Under special circumstances, the target MCU was halted when DHCSR.C_DEBUGEN was cleared on debug session close. Introduced with 6.10i. Fixed.
Firmware
- Flasher: Added stand-alone mode support for secured Nordic Semi nRF52 series devices.
GDB Server
- RTOS plugins relative to executable were not found if GDB Server was startet in a different directory. Fixed.
J-Flash
- Under special circumstances, message boxes were not shown correctly (e.g. during data prepare for KL28 devices). Fixed.
Remote Server
- J-Link Remote Server crashed after establishing a target connection. Fixed.
Version V6.10j (2016-10-31)
J-Flash
- Under special circumstances, the address edit box for *.bin files was not handled correctly. Fixed.
Version V6.10i (2016-10-25)
DLL
- Added some missing Silicon Labs EFM8 devices.
- CFI flash programming (Intel based algorithms) did not work for Cortex-AR devices. Fixed.
- CFI flash programming did not work for Cortex-M7 series devices. Fixed.
- macOS: When multiple processes accessed the same J-Link, under special circumstances accesses were not serialized correctly, resulting in incorrect behavior / failure. Fixed.
- Under special circumstances, DEMCR.TRCENA was not cleared on debug session close. Fixed.
- Under special circumstances, DHCSR.C_DEBUGEN was not cleared on debug session close. Fixed.
- Windows: Under special circumstances, when heavily creating and closing processes that connect to multiple J-Links connected to the same PC, it could happen that internal lock count errors occur. Fixed.
Firmware
- Flasher: Stand-alone mode programming of Atmel SAMD20 devices did not work when the data image included option bytes (fuses). Fixed.
GDB Server
- Some targets could put into a state where a connect succeeds but halting the CPU fails (CPU does not respond to debug halt request) and this behavior could be cured by a reset. This has been seen on some Cortex-M devices. The failed halt request made GDB Server to return with an error immediately, instead of trying to "cure" this state via reset. Fixed.
J-Flash
- "Chip erase" did not work for SPIFI flash banks (e.g. RZ/A1H). Fixed.
- Under special circumstances, the -saveas command line argument did not work properly. Fixed.
Version V6.10g (2016-10-19)
Configurator
- The value of the field "Max. SWO speed" of the "Configure J-Link" dialog was handled incorrectly. Fixed.
DLL
- Added flash programming support for Maxim MAX32560 series devices.
- Connecting to Cortex-M targets via JTAG could fail (SWD was not affected), in case there is buggy silicon that implements incorrect ROM tables. Fixed.
- Some Silicon Labs EFM8 derivative names passed bei Keil PK51 were reported as unknown device names. Fixed.
J-Flash
- Flash programming in stand-alone mode could fail under special circumstance. Introduced in V6.10b. Fixed.
- Under special circumstances, data & config file download to the Flasher failed. Fixed.
Version V6.10f (2016-10-19)
DLL
- Linux: On some Linux distributions, the J-Link library could not open an included shared library. Introduced in V6.10e. Fixed.
Version V6.10e (2016-10-14)
DLL
- Added generic debug support for Vorago PA32KAS, VA10800 and VA10820 series devices.
- Added new exec command which allows to specify a J-Link log file.
- Added new Infineon alias for TLE9879QXW40.
- Connecting to TI OMAP5910 failed. Fixed.
- Connecting to TI OMAP5912 failed. Fixed.
- J-Trace PRO Cortex-M: When not having Ethernet connected, it could take up to 2 seconds until streaming trace via USB was started. Fixed.
- Linux: Having multiple processes accessing the same J-Link at the same time did not work (second process failed to open a connection to J-Link). Fixed.
- Linux: Under some Linux distributions it could crash on debug session start when used with SEGGER Embedded Studio. The J-Link lib did not exit a thread gracefully. Fixed.
- Silicon Labs J-Link OB on old EFM32-DK boards: Under special circumstances it could happen, that the J-Link OB firmware hang at debug session start, after flash download. Fixed.
- Some Renesas RXv1 targets (e.g. RX111) could not be programmed correctly and threw errors. Introduced in V5.10i. Fixed.
- Under special circumstances a deadlock could occur when multiple processes accessed the same J-Link and target and one of the processes was IAR EWARM and the target was a Cortex-M device accessed via SWD. Fixed.
- Under special circumstances, reset strategy "core only" for Cortex-M devices did not work correctly when using the JTAG interface (SWD worked fine). Fixed.
- Updated NXP LPC5460x device names.
Firmware
- Flasher: Stand-alone mode programming of secured NXP (Freescale) SKEAZ devices did not work. Fixed.
J-Flash
- When using "Chip" as erase option with AUTO, under curtain conditions, only the selected sectors were erased. Fixed.
J-Link Package
- Added JTAG Load to the macOS and Linux packages.
- We do no longer zip the setup executable files for windows but provide the setup executables directly.
Version V6.10d (2016-10-06)
Commander
- Changed default speed for C2 target interface (used by Silicon Labs EFM8 series) to 1 MHz as 4 MHz are too much for most eval boards.
- Default speed for FINE connections is now 1000 kHz instead of 4000 kHz.
DLL
- Disassembly of data processing instructions and MSR did not process the immediate value correctly. Fixed.
- Linux/Mac: One USB thread was not terminated correctly on debug session close (no side effects so far). Fixed.
- Linux/Mac: Some threads were not terminated correctly which could cause a hang of the DLL on debug session close. Fixed.
- Linux/Mac: Streaming trace could crash on debug session close (possible NULL pointer dereference under special circumstances). Fixed.
- Mac: Streaming trace via IP did not work because failing to configure the receive buffer size on MacOS was treated as an error. Fixed.
- Silicon Labs EFM8 series: Connect could fail with Silicon Labs on-board J-Link (external J-Links work fine). Introduced in V6.10a. Fixed.
- Streaming trace could hang if more than 2 network adapters were installed on the PC. Fixed.
- Webserver thread was not terminated properly on debug session close (no side effects so far). Fixed.
J-Flash
- Some uncommon mot file generators used lower case characters a-f for data + address in mot files, which could throw a checksum error in J-Flash. Fixed.
Version V6.10c (2016-09-28)
DLL
- EEPROM size and RAM size for some ST STM32Lxxx devices was incorrect. Fixed.
- STM32L4 series devices with single bank were not handled correctly. Fixed.
Firmware
- Added error messages from flash module to console output.
- Added HWINFO about IP configuration. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- Return value of _IsBlankUseRAM() was not checked. Fixed.
- Under special circumstances, verify via readback could fail in stand-alone mode. Fixed.
J-Flash
- CFI flash always used 1kB buffers for programming which led to poor programming performance. Fixed.
- Return value of _IsBlankUseRAM() was not checked. Fixed.
Version V6.10b (2016-09-26)
DLL
- Added single stepping workaround for buggy Cortex-M7 r0p0 and r0p1 devices (e.g. ST STM32F74xxx and STM32F75xxx series), so PC does not accidentally end up in ISR on single stepping.
- Under special circumstances, flash programming did not work for Infineon XMC4500 series devices (erase timeout). Fixed.
- When having a n NXP LPCXpresso-OB or LPC-Link2 (running J-Link firmware) connected, all speed selections below 4 MHz resulted in 4 MHz being selected. Fixed.
- When quickly opening + closing multiple instances of the DLL in parallel, each connecting to a separate J-Link, it could happen that a "Could not connect to J-Link" error was thrown. Fixed.
J-Flash
- Overlapping memory areas were not always detected while reading *.mot files. Fixed.
- Project files got corrupted if no sectors for a flash bank were selected. Fixed.
- Stand-alone mode did not work for Infineon TLE98xx series devices. Fixed.
Version V6.10a (2016-09-19)
Commander
- Added unlock command for LPC5460x.
DLL
- Added flash programming support for IDT ZAMC4200 device series.
- Added support for Analog ADuCM4050/ADuCM4150 device series.
- Flash breakpoints were not set on run, if the breakpoint's flash bank end address was 0xFFFFFFFF. Fixed.
- Implemented unlock notification for locked LPC5460x
- J-Trace PRO: Streaming trace via IP did not work properly if J-Trace was in a different subnet as the host PC running the debugger. Fixed.
- Running SystemView in parallel to SEGGER Embedded Studio could cause SystemView to swallow printf() output via RTT that was targeted to Embedded Studio debug terminal. Introduced in V6.10. Fixed.
- Under special circumstances a thread was not terminated in a clean way on DLL close which could cause problems in SEGGER Embedded Studio on debug session close (in very rare cases crashing Embedded Studio on debug session close). Fixed.
- Under special circumstances, connecting to Silicon Labs EFM8BB2 series devices could fail. Introduced in V6.00i. Fixed.
- When using a J-Trace PRO with an ARM7/9 core (not supported) and trying to use STRACE API, the DLL could crash. Fixed.
- ZMDI was acquired by IDT. Updated the vendor name accordingly.
Firmware
- J-Link LITE Cortex-M: Memory leak in firmware could cause problems when starting a debug session that made use of RTT, more than 50 times. Fixed.
Version V6.10 (2016-09-14)
DLL
- Added flash programming support for NXP (Freescale) S32K142, S32K146 and S32K148 series devices.
- Added flash programming support for NXP LPC4367 series devices.
- Added flash programming support for NXP LPC43Sxx series devices.
- Added flash programming support for NXP LPC5460x.
- Added new exec command "map add <SAddr>-<EAddr> <RegionType> <MemType>" which allows to add / define memory regions.
- Added some missing Cypress device aliases.
- Added support for iMX6SX (SoloX) series devices.
- Added support for NXP (Freescale) iMX6SX (iMX6 SoloX) series devices.
- For STM32F0 devices J-Link initializes the ECC RAM with zero, on connect. CPU was restarted by accident after initializing the RAM. Fixed.
- If flash download took a very long time (> 60s due to big QSPI flashes), a error could appear saying "Emulator has been changed or re-enumerated". Fixed.
- Linux: USB lockfiles are now created separately for each interface, allowing to use multiple J-Links at the same time.
- M0APP and M0SUB were not usable on LPC4sxx triple core MCUs. Fixed.
- MacOS: USB lockfile removed, allowing to use multiple J-Links at the same time.
- Message in case of an invalid selected SWO speed was not correct. Fixed.
- Open Flash Loader did not support flashes which needs to be initialized before the J-Link can memory mapped read the flash (e.g. memory mapped SPI flashes). Fixed.
- Open Flash loader did not work with linux x64 build. Fixed.
- Open Flash Loader: Added new attribute JLinkScriptFile to the <ChipInfo> tag.
- Open Flash Loader: Added support for Cortex-A and Cortex-R cores.
- Reset failed with Kinetis CPUs, if chip had been secured before. Fixed.
- Silicon Labs EFR32xG1V devices were displayed as Cortex-M3 devices while they are actual Cortex-M4 based. Fixed.
- Under special circumstances (Flasher 4.2 + Ethernet), the J-Link DLL reported an internal merge command error. Fixed.
- Under special circumstances, connect to TI CC2650 devices did not work properly. Fixed.
- Under special circumstances, software breakpoints did not work in buffered flash regions. Fixed.
- When having multiple network adapters/cards, under special circumstances it could happen that a J-Link / J-Trace PRO was not found via IP. Fixed.
- XML-Parser did not work with linux build. Fixed.
DLL Updater
- Added Micrium uC-Probe.
- Added Ozone - The J-Link Debugger.
- Changed the behavior so that per default, all detected IDEs are selected for the J-Link DLL update.
- DLLs were not been updated correctly for KDS and Atollic. Fixed.
Firmware
- CGI call "GetOSInfo" did not exist. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1, J-Trace PRO V1 Cortex-M, J-Link PRO V4
- Flasher: Programming more then 256 bytes via J-Flash SPI failed. Fixed.
- Improved low battery indication. Low battery LED turns on in case of battery is low and starts blinking in case of battery is too low. Affected firmwares: Flasher Portable V1
- In stand-alone mode, under certain circumstances, chip erase had no effect. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- J-Trace Pro: Created new websites for internal webserver.
- J-Trace Pro: SWD speed was limited to 15MHz. Fixed.
- Relocated websites for internal webserver (PRO/Flasher) from shared folder to application folder.
- Updated some defines, added missing functions, updated build scripts and project files.
GDB Server
- Added monitor command for loading RTOS plugin.
- Added new command line option "-JLinkDevicesXMLPath".
- Added stack size check for embOS RTOS plugin.
J-Flash
- Added new Init / Exit step action "Comment".
- Added new project dialog.
- Added new sample project for Silicon Labs EM.
- Added unsecure for Silicon Labs EM351 targets.
- Changed default of the welcome screen to open recent project.
- Changed defaults when creating a new project.
- Data file got corrupted under special circumstances. Fixed.
- Disabled range check if a flash of unknown size is used.
- Removed all "basic" sample projects (without special configurations) as they are no longer required since we released the "New Project Wizard".
- Removed host interface from the create new project dialog as most custom use USB as connection type.
- Stand-alone mode programming did not work when using Nordic Semi nRF51822 devices. Fixed.
J-Flash Lite
- Removed J-Link settings file as it is not needed for J-Flash Lite.
- The address selection dialog was disabled when selecting a *.bin file. Fixed.
OFL
- Adding a new flash bank for a "aliased" device did not work. Fixed.
Version V6.00i (2016-09-02)
DLL
- Connecting to SiLabs EFM8UB2 series devices did fail. Introduced in V6.00. Fixed.
- Under special circumstances, for devices with ECC RAM, hardware units (e.g. DMAs) could behave unexpected during connect and before Reset. Fixed.
- When using trace on Cortex-M targets, it could happen that the cycle counter suddenly changed to 0x00FFFF00. Fixed.
Firmware
- Reading CFI info caused a stack overflow in Flasher Pro standalone mode. Fixed.
J-Flash
- "Show CFI info" always reported "not supported". Fixed.
- Mass erase did not work on ST STM32L0 series devices. Fixed.
- Reading CFI info caused a stack overflow in Flasher Pro standalone mode. Fixed.
J-Flash Lite
- Dialog windows were not adjusted in size in case of a non-standard system font size. Fixed.
Version V6.00h (2016-09-01)
DLL
- For ARM11 architecture R8-R14+SPSR were not accessible as pseudo registers. Fixed.
- Open Flash Loader: Added support for EraseChip() function.
- Open Flash Loader: Improved error handling when parsing flash algorithm files (elf files).
DLL Updater
- Added support for updating Atollic TrueSTUDIO (DLL + GDB Server)
GDB Server
- Atollic's GDB client crashed after a target reset. Fixed.
J-Flash
- Added unsecure for Silicon Labs EM351 (CIB) targets.
- Under special circumstances (watchdog enabled), Flasher stand-alone mode programming did not work for NXP (Freescale) KE0x series devices. Fixed.
- Under special circumstances, when the open data file did not match the min alignment, stand-alone mode did not work. Fixed.
Version V6.00g (2016-08-17)
DLL
- Exec "SetWorkRAM" did not work correctly. Introduced with V5.12. Fixed.
- Exec "SetWorkRAM" now expects the custom Work RAM area to be at least 256 Bytes in size.
Firmware
- Flasher: Parsing of FLASHER.INI failed if last line did not end with a line break. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- Under special circumstances (VCOM enabled, Linux host and JTAG as target interface), connection to some targets did not work (e.g. TI CC2650). Fixed. Affected firmwares: J-Link V9, J-Link V10
J-Flash
- Under special circumstances, SPIFI flash programming did not work properly (e.g. for Renesas R7S721000). Fixed.
RTT Viewer
- Under special circumstances, issues could pop up when using devices with ECCRAM. Fixed.
Version V6.00f (2016-08-11)
DLL
- ATSAMC20, ATSAMC21, ATSAMD09, ATSAMD10, ATSAMD11, ATSAMD20, ATSAMD21, ATSAMDA1 series devices: Option Bytes will no longer be erased by the Chip erase or erase sectors.
- Microchip PIC32W. Sometimes, downloading to in-package SPI flash was not recognized as a flash download by the DLL and resulted in a "write memory failed" response. Fixed.
- Updated Renesas Synergy device names in the J-Link device data base.
Firmware
- In standalone mode, Flasher could not start the target application via SFR-Access in stand-alone mode. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
J-Flash
- "Unsecure chip" was not executed on "Auto". Fixed.
- Generated configuration files for stand-alone mode did not include App Start Type (reset pin or via SFR-Access) if configured in the J-Flash project. Fixed.
- J-Flash did not check on Program/Verify/Download to Emu/"Save Flasher data file..." if the selected Data matches the selected flash sectors. Introduced with V6.00. Fixed.
- The "Secure Chip" option was not evaluated for "Auto" programming. Introduced in V6.00. Fixed.
Version V6.00e (2016-08-04)
Commander
- When changing the target interface when already being connected to a target via another target interface, new interface was not selected immediately but on next command. Fixed.
DLL
- Changed STM32 unlock behavior: Where possible, the DLL now only resets the Option Bytes that effect the Read/Write protection status of the device (the User Option Bytes stay untouched). If a complete reset to factory defaults of the Option Bytes is desired, the J-Link STM32 Utility (STM32 Utility.exe) can be used. Therefore, the J-Link DLL no longer resets the User Option Bytes of the following device series: STM32L0xx, STM32L1xx, STM32L4xx , STM32F0xx, STM32F1xx, STM32F3xx
- Cortex-M: Under special circumstances the log "Debugger tries to set PC to odd value..." was output by the DLL when used with some debuggers (e.g. SEGGER Ozone), even though everything was O.K. Fixed.
- HSS data was still requested from J-Link even if the target CPU was not running, resulting in unnecessary CPU load on DLL side while there was no activity on the target side. Improved.
- HSS timestamp was not "halted" while target CPU was halted, resulting in non-continuous timestamps in case CPU was halted + started multiple times, which could look like data was lost (due to buffer overflows etc.) even in case no data was lost. Fixed.
- HSS was not temporarily stopped during flash programming which could result in garbage values being read in case a flash download occurred while HSS was active/running. Fixed
- ST STM32F77xxx: Auto-detection of RTT control block did not work if it was in address range 0x20000000 - 0x2000FFFF. Fixed.
- STM32F2xx, STM32F4xx, STM32F7xx series devices: During the unlock procedure, Bits [11:08] of nWRP of the 1st flash bank were not reset to factory default. Fixed.
- STM32F469xx, STM32F479xx series devices: During the unlock procedure, SPRMOD and nWRP of the 2nd flash bank were not reset to factory default. Fixed.
- Under special circumstances, the incorrect verify method has been used resulting in longer verify times. Introduced in V6.00. Fixed.
- Under special circumstances, the J-Link DLL erroneously reported "Emulator does not support RAWTRACE.". Fixed.
- Under special circumstances, the RAM usage calculation did not calculate the optimum amount of RAM for SPIFI flash programming. Introduced in V6.00. Fixed.
- When connecting with multiple processes to the same J-Link in parallel, using different target interface speeds in each process, the processes could hang. Fixed.
Firmware
- HSS sampling was not immediately paused when the target halted. Fixed. Affected firmwares: J-Link V9, J-Link V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M
- HSS was not temporarily stopped during flash programming which could result in garbage values being read in case a flash download occurred while HSS was active/running. Fixed
- Improved error handling in case target entered a low power mode that inhibited J-Link from reading RAM contents Affected firmwares: J-Link V9, J-Link V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, ST-LINK V2, ST-LINK V2-1
RTT
- Improved error handling in case target entered a low power mode that inhibited J-Link from reading RAM contents Affected firmwares: J-Link V9, J-Link V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, ST-LINK V2, ST-LINK V2-1
STM32 Utility
- Added support for STM32F76xxx and STM32F77xxx series devices.
- STM32F2xx, STM32F4xx, STM32F7xx series devices: During the unlock procedure, Bits [11:08] of nWRP of the 1st flash bank were not reset to factory default. Fixed.
- STM32F469xx, STM32F479xx series devices: During the unlock procedure, SPRMOD and nWRP of the 2nd flash bank were not reset to factory default. Fixed.
Version V6.00d (2016-07-29)
DLL
- On SAMV71 series devices, write protection was not handled correctly. Fixed.
- Removed the message box for NXP LPCxxxx devices, which popped up during flash download when no valid checksum has been detected in the vector table.
Firmware
- Under special circumstances, chip erase did not work in stand-alone mode. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- Under special circumstances, USB communication errors could be reported when reading small chunks of memory (Introduced in V6.00). Fixed. Affected firmwares: J-Link V9, J-Link V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace PRO V1 Cortex-M, J-Link-OB-SAM3U
J-Flash
- Improved error handling / output during flash programming.
Version V6.00c (2016-07-28)
DLL
- STML32L4xx devices with 1 Flash Bank (STM32L4x2, STM32L4x3) were not handled correctly during write protection detection. Fixed.
J-Flash
- Under special circumstances, incorrect data have been programmed resulting in an verify error. Introduced in V6.00b. Fixed.
Version V6.00b (2016-07-27)
Commander
- Improved loading time of mot files loaded via "loadfile" command
- Non-existing command "ecp" was listed in help menu. Fixed.
DLL
- Device selection dialog: When entering a unknown device, the dialog crashed. Fixed.
- Device selection dialog: When entering a unknown device, the dialog crashed. Fixed.
- Flash breakpoints could not be set while the CPU was running. Fixed.
- Flash breakpoints did not work, without performing a flash download before. Fixed.
- Improved flash programming speed (reduced time stayed in prepare-phase)
- Improved flash programming speed for Cortex-M devices in border cases where the flash is (nearly) as fast as the J-Link download speed into RAM.
Firmware
- Improved SWD transmission speed Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10
- Improved TIF reaction / transmission speed Affected firmwares: J-Link BASE V10, J-Link PLUS V10, J-Link EDU V10
Version V6.00a (2016-07-25)
DLL
- Open flash loader did not support erase chip. Fixed.
- TI MSP432 was clocked too slow during flash programming. Fixed.
- V2 PCodes were tried to be executed on J-Links that only supported V1, which could cause error messages when connecting to a device. Fixed.
- XMC 1000 series devices did not work with J-Link XMC 4200 OBs. Fixed.
J-Flash
- Performing mass erase for custom added flash banks (using the Open Flash Loader concept), J-Flash crashed when performing EraseChip(). Fixed.
Version V6.00 (2016-07-22)
Commander
- Added command "-RTTTelnetport"
- The selected settings file was passed too late to the J-Link DLL resulting in the DLL searched in the wrong directory for the JLinkDevices.xml file (needed by the open flash loader). Fixed.
DLL
- Added CFI flash programming support for Cortex-R devices.
- Added command string "SetRTTTelnetport"
- Added flash programming support for Atmel ATSAMW25 device series.
- Added flash programming support for Freescale Kinetis MKE14F, MKE16F, MKE18F series devices.
- Added flash programming support for Maxim MAX32620, MAX32621, MAX32630 and MAX32631 series devices.
- Added flash programming support for Nuvoton NUC442, NUC472, M451, M452 and M453 series devices.
- Added flash programming support for NXP LPC1104UK series devices.
- Added flash programming support for NXP LPC11U66 series devices.
- Added flash programming support for NXP PN7362AU series devices.
- Added flash programming support for Spansion S6E1B8/B3 series devices.
- Added flash programming support for Spansion S6E1C1/C3 series devices.
- Added flash programming support for ST STM32F412 series devices.
- Added flash programming support for ST STM32F76/F77 series devices.
- Added flash programming support for the ST STM32L011xx and STM32L021xx series.
- Added flash programming support for the ST STM32L43xx and STM32L44xx series.
- Added flash programming support for TI CC1310F64, CC1310F32 and CC1350F128 devices.
- Added flash programming support for Toshiba TMPM066FWUG series devices.
- Added flash programming support for Toshiba TMPM381 and TMPM383 series devices.
- Added flash programming support for Zilog ZNEO Z32F128 and Z32F384 devices.
- Added flash programming support for Zilog ZNEO32 Z32F064 devices.
- Added MKE18F256xxx15, MKE18F512xxx15 series devices to public.
- Added possibility to add user-specified devices to the DLL.
- Added possibility to add user-specified flash banks to existing devices of the DLL.
- Added special handling for STM32L series on disconnect
- Added support for CMSIS flash algorithms for user-specified devices and flash banks.
- Added support for Microchip PIC32WK series devices.
- Added support for new Infineon XMC1402, XMC1403, XMC1201, XMC1202, XMC1301, XMC1302 and XMC1302 device series.
- Added support for Renesas RX130 series devices.
- Added support for Renesas RX24T series devices.
- Added support for Renesas RZ/G1E and RZ/G1M series devices.
- CFI flash programming did not work properly for Cortex-AR devices. Fixed.
- Connecting to J-Link could fail if there was already another process connected to the same J-Link, using a DLL V5.12j or earlier. Introduced in V5.41j. Fixed.
- DEMCR.TRCENA was not cleared on debug session close. Fixed.
- DHCSR.C_DEBUGEN was not cleared on debug session close. Fixed.
- EFM32PGxxxxxF256 devices were recognized with 128 instead of 256 KB Flash. Fixed.
- Flash programming of secured NXP KE04 series devices did not work in stand-alone mode. Fixed.
- Flash programming of the CCFG area of TI CC2650 devices did not work. Fixed.
- Flash programming of the NVRAM of Micronas HVC4223F devices did not work properly. Fixed.
- Flash programming on Cortex-M devices could fail if target interface speed was below 1 MHz. Introduced in V5.41j (beta). Fixed.
- Flash programming on Cortex-M devices could fail if target interface speed was below 1 MHz. Introduced in V5.41j (beta). Fixed.
- HSS: We do no longer reproduce any data (reproduction-mode) to meet requirements configured by the host when copying the received data into host buffer.
- Improved flash programming verification speed for TI MSP432
- Improved flash programming verification speed for TI MSP432
- Improved the error handling when no or an invalid file has been specified in the JLinkDevices.xml file.
- Improved the error handling when no or an invalid file has been specified in the JLinkDevices.xml file.
- J-Link script files: Added support for user-defined constants that are defined via __constant keyword.
- J-Link script files: Added U8, U16, U32 base types.
- JLink script files: __constant declarations with expressions in the value did not work did not work correctly. Fixed.
- JLink script files: Added JLINK_CORESIGHT_WriteDAP().
- JLinkARMDLL_Lib.c: message box about a missing target DLL was not correct. Fixed.
- Mac OS X: Added support for multiple-processes accessing the same J-Link.
- New boot loader versions of the TI MSP432 series devices may disable the JTAG pins / enter low power mode after 10 seconds. Improved the DLL connect sequence to be able handle this special case.
- New devices added via XML were not shown in device selection dialogs. Introduced with V5.41a. Fixed.
- On Freescale MKV56/58 the RAM ranges (0x2000_0000-0x2001_FFFF) and (0x2F00_0000-0x2F00_FFFF) were not defined as additional RTT search ranges. Fixed.
- Open Flash Loader: The J-Link DLL was allowed to pass multiples of PageSize to the ProgramPage() function. Changed the behaviour so that the DLL passes exactly one page to ProgramPage().
- Open Flash Loader: The J-Link DLL was allowed to pass multiples of PageSize to the ProgramPage() function. Changed the behaviour so that the DLL passes exactly one page to ProgramPage().
- Renesas Synergy S7G2 series devices: Under special circumstances, programming of SPIFI flash was done with a too high SPI clock speed, which could cause programming errors. Fixed.
- Reset of NXP (Freescale) MKE18 series devices was not handled correctly. Fixed.
- RX64M/RX71M: Debugging via FINE did not work properly. Fixed.
- RX64M/RX71M: Flash option setting memory could not be programmed. Fixed.
- Silicon Labs EFM8: Single stepping MOV DPL, #Imm and MOV DPH, #Imm resulted in DPTR not being updated correctly. Fixed.
- Silicon Labs EFM8: When accessing DPTR register via memory instead of J-Link CPU register functions, under special circumstances incorrect values were read/written. Fixed.
- Silicon Labs EFM8: When single stepping instructions that manipulated DPH, incorrect values were written to DPH. Fixed.
- SiliconLabs EFM8SB1: Under special circumstances, connecting to SB1 series devices could fail, if the application entered certain low power modes. Improved handling of this.
- Some Renesas RX23T devices were detected as RX210 devices. Fixed.
- Some Renesas RX23T devices were not detected properly. Fixed.
- Some ST devices passed by Keil uVision, where not recognized by the J-Link DLL. Fixed.
- SPIFI flash programming did not work properly on big endian targets (flash description was not read properly back from RAMCode). Fixed.
- Stackpointer handling on ARMv8M was not correct, if the CPU did not implement security extensions. Fixed.
- STM32: Added read / write (RDP/PCROP/WRP) protection detection and unlock support for ST STM32L4 devices.
- STM32F1xx devices were not reset after executing an Unlock / Lock. As a result, the Unlock / Lock did not become effective until the next reset or power cycle.
- STM32F1xx devices were not reset after executing an Unlock / Lock. As a result, the Unlock / Lock did not become effective until the next reset or power cycle.
- TI CC13xx series: Reset did not work properly. Fixed.
- TI CC26xx series: Reset did not work properly. Fixed
- Turbo mode flash programming for Cortex-M devices with erased value != 0xFF did not work correctly. Fixed.
- Under OSX/Linux, added symbolic links to the DLL (libjlinkarm.so.VERSION / libjlinkarm.VERSION.dylib), following this pattern: libjlinkarm.so -> libjlinkarm.so.5, libjlinkarm.so.5 -> libjlinkarm.so.5.12.4, libjlinkarm.so.5.12.4 (actual library)
- Under special circumstances RTT could cause problems during flash programming when having multiple processes accessing the same J-Link. Fixed.
- Under special circumstances, connect to Silicon Labs EFM32TG series devices did not work properly. Fixed.
- Under special circumstances, flash programming did not work for Cypress CYBL10xxx-256, CY8C4128xxx-BLxxx and CY8C4248xxx-BLxxx series devices. Fixed.
- Under special circumstances, flash programming did not work for NXP / Freescale KE15 series devices. Fixed.
- Under special circumstances, flash programming of NXP KE18F series devices did not work properly. Fixed.
- Under special circumstances, flash programming speed for some devices (e.g. TI MSP432) was slightly slowed down due to an internal mistake in the DLL. Introduced with V5.41a. Fixed.
- Under special circumstances, the J-Link DLL crashed when using J-Link settings file. Has been introduced in V5.41e. Fixed.
- Under special circumstances, the J-Link DLL did not detect an secured TI CC2650 device. Fixed.
- Under special circumstances, the watchdog of NXP (Freescale) Kinetis KE18 was not handled correctly resulting in the application run for a few [us] when performing flash download. Fixed.
- When trying to use monitor mode debugging under OS X and Linux, DLL throw a question without the user having a chance to do a selection. Fixed.
- When using unlimited flash breakpoints, under special circumstances, access violations could occur. Introduced in V5.41a (beta). Fixed.
DLL Updater
- Added updating of GDB Server RTOS plugins
- Changed the backup behaviour so that only the original J-Link DLL will be backed up (JLinkARM_org.dll).
- Crashed. Introduced in V5.41o. Fixed.
- Crashed. Introduced in V5.41o. Fixed.
- From now, the J-Link DLL Updater updates the JLinkDevice.ref file if present in the installation directory.
Firmware
- Added batch processing mode (set in Flasher.ini) Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- Added flash programming support for Atmel ATSAMV7. Affected firmwares: Flasher ARM V4, Flasher PRO V4 and Flasher Portable V1
- Flasher ARM: Infineon XMC1000 series: Added support for BMI mode switching (ASC -> SWD0) for stand-alone mode
- Flasher Portable: When selecting a configuration for which no config file was present, Flasher replied erroneously O.K.. Fixed.
- Flasher PRO: Infineon XMC1000 series: Added support for BMI mode switching (ASC -> SWD0) for stand-alone mode
- Flasher: Flash programming in stand-alone mode did not work for NXP KE02, KE04 and KE06 series devices. Fixed.
- Flasher: PCode variable JLINK_JTAG_Speed was not evaluated by the Flasher. Fixed.
- Flasher: Stand-alone mode did not work for Analog Devices ADuC7023, ADuC7038, ADuC7039, ADuC7124 and ADuC7126. Fixed.
- Flasher: Stand-alone mode did not work for TI CC2650 series devices. Fixed.
- Flasher: Under special circumstances, flash programming of Atmel ATSAMD20 devices did not work properly. Fixed.
- Improved error handling (better logfile and ASCII interface output) Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- Improved memory write speed (via JTAG) for slower running Cortex-M targets (CPU speed <= 12 MHz). Depending on the target & setup, download now is up to 15% faster. Affected firmwares: J-Link V9, J-Link V10, J-Link ULTRA+ V4, J-Link PRO V4, J-Trace V3 Cortex-M, J-Trace PRO V1 Cortex-M
- J-Link-OB-RX621-ARM-SWD: Under special circumstances, J-Link did not enumerate correctly in a VirtualBox environment. For more information, see: https://wiki.segger.com/index.php?title=J-Link-OB-RX621-ARM-SWD
- Under special circumstances, custom RAMCodes did not work properly in stand-alone mode. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- Under special circumstances, Flasher LED did blink in stand-alone mode (supplied via external power supply). Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
GDB Server
- Added -RTTTelnetport <Port> Option.
- Added feature "exception debugging"
- Floating point registers were not displayed correctly on big endian targets. Fixed.
- Floating point registers were not written correctly on big endian targets. Fixed.
- Implemented support for thread debugging with RTOS by using a plug-in
J-Flash
- *.PEX files for Flasher stand-alone mode (only needed for some devices) were only downloaded to Flasher and not created when selecting "Save Flash config file". Fixed.
- Added example project + custom RAMCode for Renesas RZ/G1E and RZ/G1M series devices.
- Added flash programming support for Atmel ATSAMW25 device series.
- Added flash programming support for Freescale Kinetis MKE14F, MKE16F, MKE18F series devices.
- Added flash programming support for NXP LPC11U66 series devices.
- Added MKE18F256xxx15, MKE18F512xxx15 series devices to public.
- Added sample project for Atmel ATSAMS70N21 devices.
- Added sample project for ST SPC560D40 series devices.
- Added SPIFI Flash programming support for Freescale MPC5645S BankB.
- Added SPIFI Flash programming support for Freescale MPC5645S BankB.
- Added support for CMSIS flash algorithms for user-specified devices and flash banks.
- Added support for Renesas RX130 series devices.
- Added support for Renesas RX24T series devices.
- Added support for SPIFI flash programming via target CPU. For a list of devices for which SPIFI flash programming is available, please refer to https://www.segger.com/jlink_supported_devices.html
- Added support for turbo flash programming for Cortex-M target devices.
- Big endian targets did not work properly for Flasher stand-alone mode. (Introduced in V5.41a beta version) Fixed.
- Changed the default value of serial number length when creating an new project from 8 to 4.
- Changed the default value of serial number length when creating an new project from 8 to 4.
- Chip erase did not work. Introduced with V5.41a. Fixed.
- CRC of file data when opening a data file was not identical to CRC shown after successful programming. Fixed.
- Exit steps were not executed. Introduced in V5.41a beta version. Fixed.
- Fixed "Perform blank check before program", reimplemented proper error reporting.
- Flash programming of the NVRAM of Micronas HVC4223F devices did not work properly. Fixed.
- FLASHER.DAT for Flasher stand-alone mode was generated incorrectly in case flash size was non-multiple of 2 KB. Fixed.
- In case a flash programming session failed, it could happen that a subsequent flashing operation crashed J-Flash. Introduced in V5.41a beta version. Fixed.
- J-Flash did erroneously report success instead of error if an invalid flash loader file has been selected in the JLinkDevices.xml file. Fixed.
- J-Flash did erroneously report success instead of error if an invalid flash loader file has been selected in the JLinkDevices.xml file. Fixed.
- J-Flash now omits errors during disconnect. Therefore, J-Flash projects which secure the chip and try to start the core afterwards still exist with success if nothing else failed.
- Line number in error output was not accurate in case a mot file contained incorrect checksums. Fixed.
- New devices added via XML were not shown. Introduced with V5.41a. Fixed.
- Preparing the FLASHER.DAT file for stand-alone mode did not work for data flashes with unaligned data.
- Renesas RX via FINE: If chip erase was performed and then a disconnect was issued, it could happen that the IDCODE bytes where reprogrammed into the device on disconnect, by accident. Fixed.
- RX64M/RX71M: Flash option setting memory could not be programmed. Fixed.
- Serial number programming did not work in J-Flash (introduced in V5.41a). Fixed.
- STM32F1xx devices were not reset after executing an Unlock / Lock. As a result, the Unlock / Lock did not become effective until the next reset or power cycle.
- STM32F1xx devices were not reset after executing an Unlock / Lock. As a result, the Unlock / Lock did not become effective until the next reset or power cycle.
- The "-reloacte" command line option did not handle negative offsets correctly. Fixed
- The actions performed by "Auto" were not evaluated by J-Flash. Fixed.
- The target device has not been selected for the "Start Application" action. Fixed.
- Under special circumstances, "-merge" command line argument did not work properly. Fixed.
- Under special circumstances, flash programming did not work for Cypress CYBL10xxx-256, CY8C4128xxx-BLxxx and CY8C4248xxx-BLxxx series devices. Fixed.
- Under special circumstances, flash programming did not work for devices with target RAM <= 2KB. Fixed.
- Under special circumstances, J-Flash did not take the flash base address into account for custom RAMCodes. Fixed.
- Under special circumstances, merging of *.bin files via command line option did accept the passed address. Fixed.
- Under special circumstances, verify did not work properly for multiple flash banks. Fixed.
- Under specific conditions, J-Flash did not report an error if a download to Flasher failed. Fixed.
- Unsecure / Secure chip could not be executed. Fixed.
- When executing the unlock device step, a separate dialog popped up. Fixed.
- When having multiple flash banks and start addr. of bank 0 was higher than start addr. of bank 1, "Check Blank" and "Read Back" operation could hang. Fixed.
- When having multiple flash banks and start addr. of bank 0 was higher than start addr. of bank 1, "Generate Test Data" operation could fail. Fixed.
- When having multiple flash banks and start addr. of bank 0 was higher than start addr. of bank 1, "Verify" could fail. Fixed.
- When having multiple flash banks, "erase chip" always caused a dialog that not all sectors are selected for erasure, even if they were. Fixed.
J-Flash SPI
- Added GUI for the Init and Exit steps.
- Added new "Init / Exit Step" commands to allow read-modify-write accesses. Further information regarding this can be found in the J-Link UM chapter "11 J-Flash SPI".
- Added new example project which demonstrates read-modify-write operation using the Init / Exit steps.
- Added new Init / Exit step actions: BNE and BNQ.
- Added new Init / Exit step actions: Comment and VerifyByte.
- Changed the Init / Exit step order in the J-Flash SPI project file so that the steps are numerical sorted.
- Extended the "Winbond_ReadModifyWrite_SecurityRegisters.jflash" example project.
J-Link Package
- Debian: The symlink /opt/SEGGER/JLink/ introduced with V5.41e was not created if a directory is already present at this location. Fixed.
- Linux: J-Link software is now installed to /opt/SEGGER/JLink_Vxyyz/. Previous versions were installed to /opt/SEGGER/JLink/ which is now a symlink that is updated on installation to point to the latest installed version.
- OS X: J-Link software is now installed to Applications/SEGGER/JLink_Vxyyz/. Previous versions were installed to Applications/SEGGER/JLink/ which is now a symlink that is updated on installation to point to the latest installed version
J-Link Script Files
- SetDeviceId did not configure the device info (IRLen). Fixed.
RTT Client
- Added -RTTTelnetport <Port> Option.
RTT Viewer
- Suppress output while sending to target.
STM32 Utility
- Added read / write (RDP/PCROP/WRP) protection detection and unlock support for ST STM32L4 devices.
Version V5.40c (2016-07-13)
Version V5.12k (2016-07-19)
DLL
- NXP KE1xF and KE1xZ series devices did not work properly. Fixed.
- TI CC13xx series: Reset did not work properly. Fixed.
- TI CC26xx series: Reset did not work properly. Fixed
Version V5.12j (2016-07-18)
DLL
- Added flash programming support for NXP (Freescale) KE1xF and KE1xZ series devices.
J-Flash
- Under special circumstances, merging of *.bin files via command line option did accept the passed address. Fixed.
Version V5.12i (2016-07-05)
Firmware
- J-Link OB SAM3U: On OS X 10.11 and later, J-Link-OB SAM3U VCOM does not send packages bigger than 64 Bytes in size. Using the most recent firmware, a workaround is now available: https://wiki.segger.com/J-Link-OB_SAM3U .
GDB Server
- Floating point registers were not displayed correctly on big endian targets. Fixed.
- Floating point registers were not written correctly on big endian targets. Fixed.
Version V5.12h (2016-06-29)
Commander
- J-Link command files were opened using single access instead of shared access. Fixed.
DLL
- Flash programming of PIC32 devices sometimes failed with error "Failed to prepare for flash programming" even if all operations were executed successfully. Fixed.
- On some Microchip PIC32MZ devices (e.g. PIC32MZ2048EFM144) when using ICSP interface, flash programming could fail. Fixed.
- Silicon Labs EFM8 series devices: Under special circumstances, it could happen that high-level (C-source) stepping in the IDE did not work correctly. Fixed.
- Silicon Labs EFM8 series devices: Under special circumstances, it could happen, that breakpoints were not hit if a memory read/write request was issued by the IDE, while the CPU was running. Fixed.
- Under special circumstances, disassembly of Cortex-AR big endian devices did not work properly. Fixed.
GDB Server
- GDB 7.10 did not break on bkpt instruction due to wrong stop reason. Fixed.
J-Flash Lite
- Flash programming of PIC32 devices sometimes failed with error "Failed to prepare for flash programming" even if all operations were executed successfully. Fixed.
- On some Microchip PIC32MZ devices (e.g. PIC32MZ2048EFM144) when using ICSP interface, flash programming could fail. Fixed.
Version V5.12g (2016-05-27)
DLL
- Added flash programming support for NXP PN7362AU series devices.
- Added flash programming support for ST STM32F411CD series devices.
- Added flash programming support for the second flash bank (0x00200000 - 0x003FFFFF) of the TI RM57L843ZWT device.
Version V5.12f (2016-05-17)
DLL
- Added missing interface types to control panel.
- Debugging with longer JTAG chains did not work properly. Fixed.
- For ARMv8M Baseline and Mainline presence of security extension was not detected properly. Fixed.
- For ARMv8M Baseline and Mainline were not distinguished correctly. Fixed.
- If exec string "SetCPUConnectIDCODE" was issued, it could happen that "unknown command" error was returned. Fixed.
- J-Link script files: Added global DLL variable CORESIGHT_AHBAPCSWDefaultSettings to allow override of AHB-AP CSW settings for Cortex-M devices that do not work with J-Link defaults.
- When programming the IDCODE on Renesas Synergy S1 and S3 series CPUs, verify errors could occur. Fixed.
Firmware
- Flasher: Flashing with longer JTAG chains did not work properly. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher RX V4, Flasher PPC V4, Flasher Portable V1
- Improved timing for SWD interface to avoid problems with higher frequencies when using a J-Link SWD Isolator. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable V1
- Improved timing for SWD interface to avoid problems with higher frequencies when using a J-Link SWD Isolator. Affected firmwares: J-Link EDU, BASE, PLUS V10
- J-Trace Cortex-M V3: Added ARMv8M support.
- J-Trace PRO V1 Cortex-M: In classic post-mortem backtrace mode, if debugger requested more trace data than available, incorrect trace data was returned by J-Trace PRO. Fixed. Could lead to "failed to read trace data" message in Keil uVision (MDK-ARM).
- Max SWD speed of 12 MHz did not work properly. Fixed. Affected firmwares: Flasher ARM V4, Flasher PRO V4, Flasher Portable V1
- When using the SPI protocol (e.g. in J-Flash SPI) and reading data from the target device, it could happen that the USB communication hang. Fixed. Affected firmwares: J-Link EDU, BASE, PLUS V9, J-Link EDU, BASE, PLUS V10, J-Link ULTRA,+, PRO V4
J-Flash
- Fixed flash base address of Atmel SAME70xxxx devices.
- Flashing with longer JTAG chains did not work properly. Fixed.
- Micronas HVC4223F: erased value of NVRAM was not set to "undefined" which caused problems with blank check operations. Fixed.
- Renesas Synergy S1: Programming of option setting memory was not possible. Fixed.
- When programming the IDCODE on Renesas Synergy S1 and S3 series CPUs, verify errors could occur. Fixed.
J-Flash SPI
- Changed default delay after power up from 20ms to 200ms as 20ms was to short for most SPI flashes.
- Manually specifying flash parameters did not work properly. Fixed.
- removed automatically created init step
- Under special circumstances, blank check did not work properly. Fixed.
J-Link Package
- RTT Files did not compile if compiled with C++ compiler. Fixed.
Manual
- UM08001: Updated section "J-Link script files".
RTT
- SEGGER_RTT_printf() did not call va_end(). Fixed.
RTT Logger
- Added to OSX and Linux packages.
RTT Viewer
- Added command line parser, added more options for RTT configuration.
- Added terminal logging, configurable buffer size, does no longer automatically close if disconnected, changed shortcuts to avoid conflicts, fixed auto-scroll, fixed all terminal output
- Changed method for writing to all terminals window, removed menu for setting of terminal buffer size.
Version V5.12e (2016-04-29)
DLL
- Very old versions of IAR EWARM (e.g. V4.40a) did not pass a device to the J-Link DLL which resulted in the device selection dialog popped up for each debug session start. Fixed.
- Windows: Under special circumstances WSACleanup() was called more often than WSAStartup() which could cause problems if the host process that loaded the DLL also used the socket API.
J-Flash
- Flash programming of the auxiliary space did not work for SAMD20. Fixed.
Version V5.12d (2016-04-27)
DLL
- Improved error handling for TI MSP432 series devices.
Version V5.12c (2016-04-21)
Version V5.12b (2016-04-15)
Version V5.12a (2016-04-12)
DLL
- "STM32L152VD-X" device names were passed by IAR EWARM and not recognized by the DLL. Fixed.
- Added handling for Keil MDK-ARM's device naming scheme for multi-core devices.
- Cortex-M: DFSR was cleared by accident, as soon as JLINK_GetMOEs() was called. Fixed.
- Custom RAMCodes did not work for Cortex-AR. Fixed.
- Kinetis E14/E15 devices had problems with cached flash content under special circumstances. Fixed.
- The "Do not show this message again" was not handled correctly for the flash breakpoints evaluation dialog. Fixed.
GDB Server
- Cortex-M: DFSR was cleared by accident (due to an indirect call of JLINK_GetMOEs), as soon as CPU was halted. Fixed.
J-Flash
- Kinetis E14/E15 devices had problems with cached flash content under special circumstances. Fixed.
J-Flash SPI
- Device was not programmed correctly in auto mode, if pages in an affected sector remained unchanged. Fixed.
- Implemented blank check before programming.
Version V5.12 (2016-03-30)
Commander
- "term" command did not work properly if DCC with SEGGER DCC handler was used on target. Fixed.
- Added short command "con" for "connect"
- If device was not passed via command line but selected in command file instead, error message "unspecified device selected" appeared. Fixed.
- If target interface speed was not passed via command line but selected in command file instead, J-Link Commander asked for speed selection again. Fixed.
DLL
- Added (Q)SPI flash programming support for Freescale K80/K82 series devices (Cortex-M4).
- Added (Q)SPI flash programming support for Xilinx Zynq series devices (Cortex-A9).
- Added API function for reading HSS capabilities.
- Added EEPROM programming support for NXP PN7360AU and PN7462AU series devices.
- Added flash programming support for active-semi PAC52xx series devices (Cortex-M0).
- Added flash programming support for Atmel SAML22 series devices.
- Added flash programming support for Cypress PSoC4A-S1, PSoC4A-S2 and PSoC4B-S0 series devices.
- Added flash programming support for Freescale Kinetis KE14Z128xxx7, KE14Z256xxx7 series devices.
- Added flash programming support for Freescale Kinetis KE15Z128xxx7, KE15Z256xxx7 series devices.
- Added flash programming support for Freescale Kinetis MKW21Z256xxx4, MKW21Z512xxx4 series devices.
- Added flash programming support for Freescale Kinetis MKW31Z256xxx4, MKW31Z512xxx4 series devices.
- Added flash programming support for Freescale Kinetis MKW41Z256xxx4, MKW41Z512xxx4 series devices.
- Added flash programming support for Silicon Labs EFM32JG (Cortex-M3) and Silicon Labs EFM32PG (Cortex-M4) device series.
- Added flash programming support for Silicon Labs EFR32BG, EFR32FG and EFR32MG device series.
- Added flash programming support for Spansion MB9EF226 device series.
- Added flash programming support for ST STM32F410x8 and STM32F410xB series devices.
- Added flash programming support for ST STM32L031xx series devices.
- Added flash programming support for ST STM32L071 device series.
- Added flash programming support for ST STM32L083xx series devices.
- Added flash programming support for TI MSP432P401M series devices (Cortex-M4).
- Added flash programming support for Toshiba TMPM46BF10FG device series (Cortex-M4).
- Added PCode for Infineon XMC1000 series devices which handles the special reset sequence in stand-alone mode.
- Added RTT support for Cortex-A and Cortex-R based devices.
- Added some new NXP devices: MKV56F512xxx20, MKV56F1M0xxx20, MKV58F512xxx20 and MKV58F1M0xxx20 series devices.
- Added support for ARMv8M architecture.
- Added support for Freescale iMX537 (Cortex-A8).
- Added support for new CPU registers of Renesas RXv2 architecture (e.g. for RX64M, RX71M devices)
- Added support for trace start/stop events for Cortex-M devices.
- Cortex-M7: No matter if an accessed address was cachable/bufferable or not, J-Link tried a cachable/bufferable access, which could lead to unwanted side effects on SFR areas. Fixed.
- Implemented CMD_HSS_GET_CAPS in DLL server.
- Microchip PIC32MZ: J-Link did not handle accesses to RAM at 0xA0000000 correctly (Accesses to RAM at 0x80000000 worked correctly). Fixed.
- Programming of option-setting memory for Renesas Synergy S1 devices did not work correctly. Fixed.
- Programming of option-setting memory for Renesas Synergy S7 devices did not work correctly. Fixed.
- RTT was not correctly handled on big endian targets. Fixed.
- Some Silicon Labs EFM32JG / PG devices were not recognized by the J-Link DLL. Fixed.
- STM32: Added write protection detection and unlock support for F2, F4, F7, L0, L1 devices.
- STM32F4 Unlock: SPRMOD bit was neither detected nor cleared if set on STM32F 42xx / 43xx devices. Fixed.
- STRACE: CBZ / CBNZ instruction was not analyzed correctly, resulting in wrong branch destination addr. calculation. Fixed.
- The following device names were passed by IAR EWARM and not recognized by the DLL: STM32L151VD-X, STM32L152VD-X. Fixed.
- Under special circumstances, the DLL detected ST STM32 devices erroneously as read protected. Fixed.
DLL Updater
- NXP Kinetis Design Studio 3.2.0 installation was not detected on 64-bit Windows installations. Fixed.
Firmware
- Cortex-A and Cortex-R: If a debug session was terminated immediately after a CPU restart request (Go) without any other command following before the J-Link connection was closed, it could happen that the CPU was not started correctly. Fixed. Affected firmwares: J-Link EDU, BASE, PLUS V9, J-Link EDU, BASE, PLUS V10, J-Link ULTRA,+, PRO V4
- Cortex-M7: No matter if an accessed address was cachable/bufferable or not, J-Link tried a cachable/bufferable access, which could lead to unwanted side effects on SFR areas. Fixed. Affected firmwares: J-Link EDU, BASE, PLUS V9, J-Link EDU, BASE, PLUS V10, J-Link ULTRA,+, PRO V4, J-Link-OB-SAM3U
- Flasher: Added monitor of target supply voltage (VTref).
- Flasher: Added periodically monitor target reference voltage during flash programming. Needs to be enabled / configured in the J-Flash project settings.
- Flasher: Added stand-alone mode support for active-semi PAC522x series devices.
- Flasher: Added stand-alone mode support for ST STCOMET series devices.
- J-Link EDU, BASE, PLUS V10: Silabs EFM8: Connection to some derivatives like EFM8LB1 could fail if a pull-up resistor was placed on C2D line. Fixed.
- J-Link EDU, BASE, PLUS V9: Silabs EFM8: Connection to some derivatives like EFM8LB1 could fail if a pull-up resistor was placed on C2D line. Fixed.
- J-Link EDU, BASE, PLUS, ULTRA+, PRO: Added support for ARMv8M architecture.
- J-Link EDU/BASE/PLUS V10: Added RTT support for Cortex-A and Cortex-R based devices.
- J-Link EDU/BASE/PLUS V9: Added RTT support for Cortex-A and Cortex-R based devices.
- J-Link PRO V4: Added RTT support for Cortex-A and Cortex-R based devices.
- J-Link ULTRA+ V4: Added RTT support for Cortex-A and Cortex-R based devices.
- J-Link ULTRA,+, PRO V4: Silabs EFM8: Connection to some derivatives like EFM8LB1 could fail if a pull-up resistor was placed on C2D line. Fixed.
- J-Link-OB-SAM3U128-V1: The latest firmware reported an incorrect serial number. Fixed. Buggy firmware has been introduced in V5.10h. We strongly recommended to update to V5.10i.
- RTT was not correctly handled on big endian targets. Fixed.
J-Flash
- Added EEPROM programming support for NXP PN7360AU and PN7462AU series devices.
- Added flash programming support for active-semi PAC52xx series devices (Cortex-M0).
- Added flash programming support for Atmel SAML22 series devices.
- Added flash programming support for Cypress PSoC4A-S1, PSoC4A-S2 and PSoC4B-S0 series devices.
- Added flash programming support for Freescale Kinetis KE14Z128xxx7, KE14Z256xxx7 series devices.
- Added flash programming support for Freescale Kinetis KE15Z128xxx7, KE15Z256xxx7 series devices.
- Added flash programming support for Freescale Kinetis MKW21Z256xxx4, MKW21Z512xxx4 series devices.
- Added flash programming support for Freescale Kinetis MKW31Z256xxx4, MKW31Z512xxx4 series devices.
- Added flash programming support for Freescale Kinetis MKW41Z256xxx4, MKW41Z512xxx4 series devices.
- Added flash programming support for Silicon Labs EFM32JG (Cortex-M3) and Silicon Labs EFM32PG (Cortex-M4) device series.
- Added flash programming support for Silicon Labs EFR32BG, EFR32FG and EFR32MG device series.
- Added flash programming support for Spansion MB9EF226 device series.
- Added flash programming support for ST STM32F410x8 and STM32F410xB series devices.
- Added flash programming support for ST STM32L031xx series devices.
- Added flash programming support for ST STM32L071 device series.
- Added flash programming support for ST STM32L083xx series devices.
- Added flash programming support for TI MSP432P401M series devices (Cortex-M4).
- Added flash programming support for Toshiba TMPM46BF10FG device series (Cortex-M4).
- Added sample projects / script files for Spansion MB9EF226 devices.
- Added sample projects for Atmel ATSAMC20J17, ATSAMC20J18 and ATSAMC21J18 series devices.
- Added sample projects for ST STM32F42V7VG and STM32F42V7VI.
- Added sample projects STM32L051C8_AllowOptBytes.jflash, STM32L486JG.jflash, STM32L486QG.jflash, STM32L486RG.jflash, STM32L486VG.jflash and STM32L486ZG.jflash.
- Added support for new CPU registers of Renesas RXv2 architecture (e.g. for RX64M, RX71M devices)
- Moved all Fujitsu example projects to the Spansion
- Path for J-Link scriptfile is now sent in double quotes (required for filenames with spaces)
- ST STM32F301 series devices were not shown in the device selection list. Fixed.
- Updated NXP LPC2292.jflash sample project
J-Link Package
- Added J-Link License Manager for Linux and MAC OSX.
RDDI
- Improved support up to DS-5 v5.22 (x86 and x64 support).
- Sometimes the device selection dialog popped up when starting the debug session, even if a device was selected. Fixed.
Version V5.10u (2016-03-17)
DLL
- Error "Expected 0, found -" could be thrown if J-Link settings file was modified. Introduced with V5.10t. Fixed.
DLL Updater
- NXP Kinetis Design Studio 3.2.0 installation was not detected. Fixed.
Firmware
- When using monitor mode debugging and the target performed a reset from within the target application, monitor mode got disabled. Fixed.
J-Flash
- Removed core selection "auto" while maintaining compatibility with J-Flash projects saved by older versions which might have selected it.
JTAG Load
- Added command line parameter "-NoAutoExit" to leave JTAGLoad open after successful execution of SVF file.
Manual
- UM08001: Monitor Mode Debugging: Added information about special care needed to be taken in case the target application issues a reset.
Version V5.10t (2016-03-14)
Commander
- "Emulator has trace capabilities" has been shown for all J-Link models, even if trace was not supported. Fixed.
- Under special circumstances, the J-Link DLL reported "unknown device" when using the speed auto command in script mode. Fixed.
DLL
- Added a maximum character limit for the RXIDCode input field which pops up during the authentication process for RX targets.
- Added exec command string "SetSkipInitECCRAMOnConnect".
- Added flash programming support for Freescale Kinetis KE14Z128xxx7, KE14Z256xxx7 series devices.
- Added flash programming support for Freescale Kinetis KE15Z128xxx7, KE15Z256xxx7 series devices.
- Added flash programming support for Freescale Kinetis MKW21Z256xxx4, MKW21Z512xxx4 series devices.
- Added flash programming support for Freescale Kinetis MKW31Z256xxx4, MKW31Z512xxx4 series devices.
- Added flash programming support for Freescale Kinetis MKW41Z256xxx4, MKW41Z512xxx4 series devices.
- Corrected flash sector size for MKV46F256xxx16.
- Flash programming for NXP Kinetis KL33 series devices did not work properly. Fixed.
- Settings file: Added "MonModeDebug" and "MonModeVTableAddr" to CPU section to allow shipping of projects with monitor mode enabled, even if the IDE does not support passing of execs to the DLL.
- SPIFI programming: Added support for Adesto flashes. Full list of devices, see: https://www.segger.com/jlink_supported_devices.html
- Under special circumstances, hardware breakpoints and data breakpoints (watchpoints) were not cleared correctly on debug session close. Fixed.
Firmware
- J-Link (BASE, PLUS, EDU) V10: Under special circumstances, a single byte on SWO could be dropped when starting/stopping SWO multiple times in a row. Fixed.
- J-Link EDU, BASE, PLUS, ULTRA+, PRO: Bug was introduced for ARM Cortex-M7 support with V5.10s, resulting in memory read/write to fail. Problem only occurred when using SWD as debug interface. It did not occur when using JTAG. Introduced by changes added for ARMv8-M support. Fixed.
- J-Link-OB-SAM3U: Nordic nRF52 targets: Under special circumstances, MSD programming did not work on the first attempt but on the second one. Fixed.
J-Flash
- Added flash programming support for Freescale Kinetis KE14Z128xxx7, KE14Z256xxx7 series devices.
- Added flash programming support for Freescale Kinetis KE15Z128xxx7, KE15Z256xxx7 series devices.
- Added flash programming support for Freescale Kinetis MKW21Z256xxx4, MKW21Z512xxx4 series devices.
- Added flash programming support for Freescale Kinetis MKW31Z256xxx4, MKW31Z512xxx4 series devices.
- Added flash programming support for Freescale Kinetis MKW41Z256xxx4, MKW41Z512xxx4 series devices.
- Corrected flash sector size for MKV46F256xxx16.
- Flash programming for NXP Kinetis KL33 32- and 64 KB series devices did not work properly (Wrong RAM base address configured). Fixed.
Version V5.10s (2016-03-09)
DLL
- Under special circumstances it was not detected properly if a write to the J-Link config area failed. Fixed.
- Under special circumstances, the DLL erroneously reported an communication error during authentication process of RX devices (FINE interface, only). Fixed.
GDB Server
- Server did not check if client supports hwbreak. Fixed.
J-Flash SPI
- The "Auto" configuration was not evaluated correctly. Fixed.
- Under special circumstances, when mass erase has been configured for "Auto" procedure, flash programming did not work. Fixed.
Manual
- UM08001: J-Link Manual: Updated the J-Flash SPI section: Added new section describing the "Production" tab.
Version V5.10r (2016-03-08)
Commander
- Added command that allows updating the BTL of certain J-Link OB RX621 models.
DLL
- Added flash programming support for Silicon Labs EFR32BG, EFR32FG and EFR32MG device series.
- Monitor mode: Added exec "SetMonModeVTableAddr" to manually set the base address of the vector table for applications that explicitly forward the monitor interrupt via a veneer.
- Under special circumstances, flash programming did not work for NXP MKL82Z128xxx7 series devices. Fixed.
Firmware
- (all models with monitor mode support): Added support for new exec "SetMonModeVTableAddr".
- J-Link-OB-SAM3U: Added support for monitor mode debugging.
J-Flash
- Added flash programming support for Silicon Labs EFR32BG, EFR32FG and EFR32MG device series.
Version V5.10q (2016-03-04)
Commander
- Commander did try to connect to CPU multiple times in a row even if connected J-Link did not support the selected CPU architecture. Fixed.
DLL
- Linux: Corrected udev rules file from SUBSYSTEM!=="usb_device" to SUBSYSTEM!="usb_device"
- Reset did not work properly for NXP MKL82Z128xxx7 series devices. Fixed.
- SiLabs EFM8/8051: Direct accesses to area 0x20 - 0x3F did not work correctly. Fixed.
Firmware
- J-Link EDBG: Added support for Cortex-A and Cortex-R devices (FW from 160302).
- J-Link EDBG: Firmware did not work correctly under OS X. Fixed in FW from 160302.
- J-Link LITE Cortex-M 5V: Cortex-M7 based target devices were not recognized correctly. Fixed.
- J-Link ULTRA+, PRO: Under special circumstances USB communication could break-down when using J-Link and VCOM functionality in parallel. Fixed.
- J-Link-OB-RX621-ARM-SWD: J-Link OB drove SWDIO pin even if no debugger was connected to it which e.g. caused problems when connecting an external J-Link to a Renesas Synergy board. Fixed.
GDB Server
- Send stop reason when breakpoints or watchpoints are reached (required by Atollic TrueStudio)
Version V5.10p (2016-02-26)
DLL
- Added some missing Cypress devices (CY8C5265xxxLP, CY8C5287xxxLP, CY8C5288xxxLP, CY8C5465xxxLP, CY8C5488xxxLP, CY8C5688xxxLP and CY8C5888xxxLP to the J-Link DLL.
- Added support for Analog Devices CM41x (Cortex M0 and CortexM4) series devices.
- Under special circumstances, the fall back method was not executed correctly, when the ordinary connect failed. Fixed.
J-Flash
- Added sample project for Atmel ATSAMD09D14.
STR91x Utility
- "Unspecified device" message box popped up, when starting the Commander. Introduced in V5.10. Fixed.
Version V5.10o (2016-02-25)
DLL
- Added flash programming support for Nordic Semi nRF51802_xxAA devices.
- Added FlashBP buyout handling for Renesas Synergy devices and J-Link OB RX621-ARM-SWD
- Initial connection attempt via the FINE interface could fail for some buggy RX devices. Fixed.
Firmware
- Flasher: WIN10 automatically creates a "System Volume Information" folder on the MSD of the Flaser. This leaded to issues when using the Authorized Flashing feature. Fixed.
- J-Link-OB-STM32F072: Added Monitor Mode Debugging and High-Speed sampling (HSS) capabilities.
J-Flash
- Added flash programming support for Nordic Semi Device nRF51802_xxAA devices.
- Added sample projects for Nordic Semi nRF51422_xxAC, nRF51802_xxAA, nRF51822_xxAC and nRF52832_xxAA devices.
Version V5.10n (2016-02-19)
DLL
- Added flash programming support for NXP LPC5411x device series.
- Added flash programming support for NXP PN7360AU and PN7462AU device series.
- Flash download into CFI flash: Compare in case flash content has not changed did not work correctly for some Intel flashes. Fixed.
- If more than 8 devices were in a JTAG chain, the core to connect to was not detected correctly. Fixed.
- J-Link-OB on SAM3U basis on Atmel SAMA5 eval boards could refuse further firmware updates. Fixed.
- RTT auto-detection did not work if Id of RTT control block was crossing a 4 KB boundary in memory. Fixed.
- SiLabs EFM8BB3 series devices: SFR P3 at addr 0xB0 was not written correctly, if written through J-Link. Fixed.
- SiLabs EFM8LB1 series devices: SFR P3 at addr 0xB0 was not written correctly, if written through J-Link. Fixed.
- Under special circumstances, (Q)SPI flash programming did not work for Renesas RZ/A1 family devices. Fixed.
J-Flash
- Added flash programming support for NXP LPC5411x device series.
- Added flash programming support for NXP PN7360AU and PN7462AU device series.
Version V5.10m (2016-02-15)
DLL
- Added flash programming support for Analog Devices ADSP-CM411F, ADSP-CM412F, ADSP-CM413F, ADSP-CM416F, ADSP-CM417F, ADSP-CM418F and ADSP-CM419F.
- DLL failed to detect more than 64 J-Links connected in parallel. Fixed.
- Some ST STM32F4xx devices were not recognized by IAR. Fixed.
- Some ST STM32L4xx devices were not recognized by IAR. Fixed.
Firmware
- J-Link-OB-SAM3U128 on Nordic boards: MSD programming could hang with some specific bin files. Fixed.
Version V5.10l (2016-02-11)
DLL
- Added flash programming support for Infineon XMC4300-256 series devices.
- Flash programming did not work for the second bank of ST STM32L4 (256 KB and 512 KB flash density) devices. Fixed
- If CPU was not explicitly halted before performing flash programming, DLL threw errors. Fixed. (CPU is implicitly halted now)
- Write protection detection for ST STM32F0xx devices did not work. Fixed.
- Write protection detection for ST STM32L0xx devices did not work. Fixed.
Firmware
- J-Link-OB-SAM3U128 on Nordic boards: Improved SEGGER RTT transfer speed.
- J-Link-OB-SAM3U128 on Nordic boards: VCOM: RTS line was driven even if hardware-flow-control was not used. Fixed.
GDB Server
- In case of a log file has been specified, the GDB Server did not use the passed path. Fixed.
J-Flash
- Added flash programming support for Infineon XMC4300-256 series devices.
- Unlock of ST STM32Wxx devices did not work. Fixed.
RDDI
- Disconnect from target did not work correctly. Fixed.
- DSTREAM did not work. Fixed.
Version V5.10k (2016-02-09)
DLL
- Added flash programming support for Renesas R5F51116, R5F51117 and R5F51118.
- Corrected SRAM sizes for LPC11Axx.
- Infineon XMC4xxx devices with more than 1 MB flash: When downloading to the cached flash area @ 0x08000000, flash programming beyond the 1 MB boundary failed. Fixed.
- Under special circumstances, (Q)SPI flash programming did not work for NXP LPC4337. Fixed.
- Unlock of ST STM32Wxxx devices did not work properly. Fixed.
DLL Updater
- Added registry search path for Freescale (now NXP) Kinetis Design Studio and Codewarrior for future releases after Freescale acquisition by NXP.
J-Flash
- Added Altera Cyclone V to the device selection dialog of J-Flash.
- Added example projects for Atmel ATSAM4C family.
- Added flash programming support for Renesas R5F51116, R5F51117 and R5F51118.
- Added sample project for Atmel ATSAM4C32C.
- Corrected SRAM sizes for LPC11Axx.
- Under special circumstances, (Q)SPI flash programming did not work for NXP LPC4337. Fixed.
- Unlock of ST STM32Wxxx devices did not work properly. Fixed.
- When passing the "-open" and "-openprj" command via command line option, possibly two data files were opened. Fixed.
RDDI
- Added support for Cortex-A5.
- Added support for devices with multiple cores.
- Memory corruption if more than 15 interfaces are found on debug port. Fixed.
Version V5.10j (2016-02-02)
DLL
- Added flash programming support for NXP MKV56F512xxx24, MKV56F1M0xxx24, MKV58F512xxx24 and MKV58F1M0xxx24.
- New Renesas RX63N devices were not recognized correctly. Fixed.
- Terminal I/O via DCC on Cortex-A and Cortex-R cores did not work properly in IAR EWARM. Fixed.
- The TI CC2650 series seems to contain OTP data in the config area sector which resulted in verify errors during flash programming. Fixed.
- Under special circumstances the TI OMAP-L138 did not work properly. Fixed.
- When opening/loading a hex/mot/bin file, the file was opened exclusively which caused problems when running multiple instances in parallel that shall load and program the same file. Fixed.
J-Flash
- -usb command now also accepts S/N as hexadecimal values of format"0x........"
- Added flash programming support for NXP MKV56F512xxx24, MKV56F1M0xxx24, MKV58F512xxx24 and MKV58F1M0xxx24.
- If connection to a J-Link with a specific S/N was requested/configured, J-Flash always showed S/N = 0 in the log window. Fixed.
- Lifted max. number of devices in a JTAG chain to 16.
- Option byte programming of ST STM32F3 series devices did not work. Fixed.
- The TI CC2650 series seems to contain OTP data in the config area sector which resulted in verify errors during flash programming. Fixed.
- When opening/loading a hex/mot/bin file, the file was opened exclusively which caused problems when running multiple instances in parallel that shall load and program the same file. Fixed.
J-Link Package
- Installer: DLL Updater is now suppressed in silent mode (/S) in order to allow complete silent installations.
STM32 Utility
- Added support for STM32 F74xx / 75xx devices.
- SPRMOD was not cleared if set on STM32 42xx / 43xx devices. Fixed.
Version V5.10i (2016-01-28)
Firmware
- J-Link-OB-SAM3U128-V1: The latest firmware reported an incorrect serial number. Fixed. Buggy firmware has been introduced in V5.10h. We strongly recommended to update to V5.10i.
Version V5.10h (2016-01-21)
DLL
- Added flash programming support for Microchip PIC32MZ0512EFE, PIC32MZ0512EFF, PIC32MZ0512EFK series
- Added flash programming support for Microchip PIC32MZ1024EFE, PIC32MZ1024EFF, PIC32MZ1024EFG, PIC32MZ1024EFH, PIC32MZ1024EFK, PIC32MZ1024EFM series
- Added flash programming support for Microchip PIC32MZ2048EFG, PIC32MZ2048EFH, PIC32MZ2048EFM series
- Added support for MTB on Cortex-M0+ to STRACE API.
- RAM size of ST STM32L151CB-A and STM32L151VB-A devices was incorrect. Fixed.
- Renesas Synergy S1: If LVD detection in option flash memory OFS0 / OFS1 was configured incorrectly, further connection attempts via J-Link could fail. Fixed.
- Renesas Synergy S3: If LVD detection in option flash memory OFS0 / OFS1 was configured incorrectly, further connection attempts via J-Link could fail. Fixed.
- Renesas Synergy S7: If LVD detection in option flash memory OFS0 / OFS1 was configured incorrectly, further connection attempts via J-Link could fail. Fixed.
- Some device names, passed by Atollic Studio were unknown in the J-Link DLL. Fixed.
- Some Microchip PIC32 JTAG Ids were not recognized correctly. Fixed.
- Under special circumstances, the DLL could crash on close if used together with some 3rd party antivirus / network security software. Fixed.
- When being connected to a J-Link (PRO) via IP and starting a J-Link Configurator instance in parallel, it could happen that the DLL instance lost the connection to J-Link. Fixed.
DLL Updater
- Some installations of Microchip MPLAB X were not recognized correctly. Fixed.
Firmware
- J-Link BASE/PLUS V10: Increased parallel connection limit to 5
- J-Link BASE/PLUS V9: Increased parallel connection limit to 5
- J-Link OB-SAM3U128-V2-NordicSemi: MSD drag & drop programming did not work under special circumstances. Fixed.
- J-Link OB-SAM3U128-V2-NordicSemi: Under special circumstances characters could get lost on VCOM. Fixed.
- J-Link OB-SAM3U128-V2-NordicSemi: VCOM did not work properly if hardware flow control was used. Fixed.
- J-Link OB-SAM3U128-V2: Under special circumstances characters could get lost on VCOM. Fixed.
- J-Link OB-SAM3U128-V2: VCOM did not work properly if hardware flow control was used. Fixed.
- J-Link OB-SAM3U128-V3: Under special circumstances characters could get lost on VCOM. Fixed.
- J-Link OB-SAM3U128-V3: VCOM did not work properly if hardware flow control was used. Fixed.
- J-Link ULTRA+/PRO V4: Increased parallel connection limit to 10
- J-Link-OB-XMC4200: Under special circumstances, GetBMI abd SetBMI did not work under properly. Fixed.
J-Flash
- Flash programming did not work for Infineon XMC4700 / XMC4800. Fixed.
- Interface speeds loaded from a J-Flash project were limited to a maximum of 12000 kHz. Fixed.
- RAM size of ST STM32L151CB-A and STM32L151VB-A devices was incorrect. Fixed.
- Reset type was not saved in / loaded from the J-Flash project file (*.jflash). Fixed.
- Under special circumstances, JTAG scan chain information auto-detection did not work in the J-Flash project settings tab. Fixed.
Version V5.10g (2016-01-06)
Control Panel
- Under special circumstances, the control panel was not updated correctly. Fixed.
DLL
- Cortex-M: Simulation did not handle cases correctly, where a non-4-byte aligned values was written to stackpointer (R13/SP). Fixed.
- Cortex-M: Simulation did not handle write accesses to BASEPRI correctly if less than 8 prio bits are implemented. Fixed.
- MinAlign was not taken into account when calculating the RAMUsage which might causes (Q)SPI RAMCodes to fail. Fixed.
- Setting IRPre or DRPre via J-Link script files had not effect since V5.10. Fixed.
- Under special circumstances, flash programming of external CFI flashes did not work. Fixed.
- Under special circumstances, flash programming of secured Atmel SAMD20 devices could fail in stand-alone mode. Fixed.
- Under special circumstances, we did not clear the command locked state (if active) on Renesas RX62N series devices. Fixed.
Version V5.10f (2015-12-22)
Commander
- The low-level SWD CoreSight commands set the overrun detection bit of the SW-DP by accident. Fixed. Affected commands: SWDReadAP, SWDWriteAP, SWDReadDP, SWDWriteDP, SWDSelect
DLL
- On some Analog Devices ADSP devices (Cortex-M4), connecting failed because of a bug in the Cortex-M connect sequence. Fixed.
Version V5.10e (2015-12-21)
DLL
- ARM9 (Samsung S3C2410A) devices were not detected correctly. Introduced in V5.10. Fixed.
- Auto-device-override ignore, in case the current version knows the original device name, sometimes did not work properly. Fixed.
- If debugger called JLINK_GetList() in the background during an active debug session, in some rare conditions, connection to J-Link could be lost. Fixed.
- J-Link USB device was not closed correctly on MAC OS X and Linux. Fixed.
- Logging of JLINK_SWO_ReadStimulus() does not report the return value/data correctly. Fixed.
- Microchip PIC32: Programming of binaries with readout protection set failed. Fixed.
- PLL initialization did not work properly for Renesas RX63T devices. Fixed.
- SPIFI programming: Flash programming of Eon, ISSI, AMIC did not work. Fixed. Full list of devices, see: https://www.segger.com/jlink_supported_devices.html
- The "exec HideDeviceSelection" option was not taken into account. Fixed.
- Under special circumstances, communication with RX63T target devices failed. Fixed.
- Under special circumstances, for ST devices the reset pin was set incorrectly. Fixed.
Firmware
- J-Link-OB-XMC4200: Data reception via VCOM did not work properly when using HTerm terminal application. Fixed.
- J-Link-OB-XMC4200: On some boards a COM LED is present. LED is now toggled while VCOM data transfers are active.
J-Flash
- Added flash programming support for Atmel ATSAMC20xxx and ATSAMC21xxx series devices.
SWO Viewer
- Selected device was not used in SWOVIEWER_DetermineSWOSpeed(). Fixed.
- Status bar disappeared when resizing window. Fixed.
- Uses last found SWO speed as maximum value for next session. Fixed.
Version V5.10d (2015-09-12)
DLL
- The "Do not show again unlock" option for the STM32 "Read protection detected" dialog was not considered. Fixed.
- Under special circumstances, the DLL detected erroneously an active read out protection for ST STM32 devices. Fixed.
Firmware
- J-Link-OB-XMC4200: HSS did not work properly (timestamp was not calculated correctly). Fixed.
Version V5.10c (2015-12-04)
DLL
- Debugging on Cortex-M, Cortex-A, Cortex-R big endian targets did not work properly (e.g. semihosting). Fixed.
- TI RM57L devices (Cortex-R5) were recognized as Cortex-R4 and threw a warning. Fixed.
- TI TMS570LC devices (Cortex-R5) were recognized as Cortex-R4 and threw a warning. Fixed.
GDB Server
- Semihosting did not work properly if SYS_READ or SYS_WRITE commands were used and could only partially read/write the file/stream. Fixed.
- Semihosting did not work properly if SYS_READC command was used. Fixed.
Version V5.10b (2015-12-03)
Commander
- Missing newline added after output of IP configuration for debug probes with ethernet support.
DLL
- (Q)SPI flash programming did not work for Renesas R7FS7G2 if the PLL has been initialized before. Fixed.
- Connecting to J-Link PRO V4 failed. Introduced in V5.10a by incorrect firmware update check change. Fixed.
- External DLL connections might not be closed before closing the DLL. Fixed.
- Under special circumstances, DLL could crash when debugger requested to write 0 bytes. Fixed.
Version V5.10a (2015-12-02)
Commander
- DLL version info was not printed correctly, if no revision character was following version number. Fixed.
DLL
- Generic (Q)SPI flash programming did not work properly for Renesas R7FS7G2. Fixed.
Firmware
- Flasher ARM, RX, PPC, PRO V4: We did not take execute the pcode to perform a reset in cases where a pcode for reset was stored on the Flasher. Fixed.
- Flasher: Flash programming of secured Atmel SAMD20 devices did not work in stand-alone mode. Fixed.
J-Flash
- J-Flash reported an error for *.mot data files which contained empty lines. Fixed.
Version V5.10 (2015-11-27)
Commander
- Added flash programming progress bar for the Linux and MAC version of J-Link Commander.
- Commander does not perform a auto-connect with search on all interfaces any longer, by default.
- Extended "unlock LM3Sxxx" command so that it can be automated (new syntax: unlock LM3Sxxx [<Auto>]).
- If device was selection was done via command file but connection to device was lost during command execution, at next command, Commander asked for device again. Fixed.
- If device was selection was done via command file but connection to device was lost during command execution, at next command, Commander asked for device again. Fixed.
- Linux: Cursor function / command line history did not work properly. Fixed.
- When executing J-Link command files, the "q" command was ignored. Fixed.
- When executing J-Link command files, the "q" command was ignored. Fixed.
DLL
- Added API function MRU_GetList via GetpFunc to retrieve the MRU device and settings files.
- Added authentication support for Renesas RZ/T1 series devices.
- Added Device Support for Atmel ATSAMA5D22 series devices.
- Added firmware for J-Link-OB-SAM3U128 V3
- Added flash programming support for Atmel ATSAMD10D14AU and ATSAMD11D14AU device series.
- Added flash programming support for Atmel ATSAMD10D14AU and ATSAMD11D14AU device series.
- Added flash programming support for Cypress CY8C4245xxx-Dxxx and CY8C4246xxx-Dxxx series devices.
- Added flash programming support for Cypress CY8C4247xxx-BLxxx series devices.
- Added flash programming support for Cypress PSoC4A-DS2 series devices (Cortex-M0).
- Added flash programming support for Infineon TLE984x device series.
- Added flash programming support for Infineon TLE984x device series.
- Added flash programming support for NXP LPC1124 and LPC1125 device series.
- Added flash programming support for NXP LPC1124 and LPC1125 device series.
- Added flash programming support for ST STCOMET series devices (Cortex-M4).
- Added flash programming support for ST STM32F302RE, STM32F302VD, STM32F302VE, STM32F302ZD, STM32F302ZE, STM32F303ZD, STM32F318C8, STM32F318K8, STM32F328C8, STM32F398VE device series.
- Added flash programming support for ST STM32F302RE, STM32F302VD, STM32F302VE, STM32F302ZD, STM32F302ZE, STM32F303ZD, STM32F318C8, STM32F318K8, STM32F328C8, STM32F398VE device series.
- Added flash programming support for ST STM32F469 and STM32F479 series devices (Cortex-M4).
- Added Freescale Kinetis KL82 series devices MKL82Z128VMC7, MKL82Z128VLK7, MKL82Z128VLL7, MKL82Z128VLH7, MKL82Z128VMP7
- Added Freescale Kinetis KS22 series devices MKS22FN128VLL12, MKS22FN128VLH12, MKS22FN256VLL12, MKS22FN256VLH12.
- Added Freescale S32K144 series devices.
- Added generic (Q)SPI flash programming support for NXP LPC407x and LPC408x series devices.
- Added MRU module to save most recently used devices and settings files.
- Added new feature which allows to configure a minimum and maximum target voltage required for programming.
- Added nRF52832_xxAA as public device.
- Added preliminary support for debugging Renesas RX64M and RX71M via FINE interface.
- Added support (via JTAG) for Renesas RX64M series devices.
- Added support for Analog Devices ADUCM362.
- Added support for Renesas RX231 series devices.
- Added support for Renesas RX23T series devices.
- Added unsecure handling for read protected STM32F3 devices to revoke protection on connect.
- Added watchdog handling for TI CC2538 series devices.
- AMS AS7000: Flash downloads to address 0x0 did not work properly, even if flash was mapped at addr. 0x0. Fixed.
- Auto-detection of RTT control block did not work properly for NXP LPC18xx and LPC43xx devices. Fixed.
- Automatic JTAG speed detection did not work properly on ARM7/9 devices with adaptive clocking support and newer J-Link V10 models. Fixed.
- Connect to TI CC2538 devices did not work properly. Fixed.
- Cortex-M: Improved handling cases where device is in an unresponsive state when connecting to it. J-Link now has a higher chance to get control over the device again.
- Cortex-M: Improved handling cases where device is in an unresponsive state when connecting to it. J-Link now has a higher chance to get control over the device again.
- Cortex-M: Improved handling for cases where device enters a low power mode and debug connection is temporarily lost during debugging.
- Cortex-M: Improved handling for cases where device enters a low power mode and debug connection is temporarily lost during debugging.
- Deadlock could happen, if device was re-selected during the debug session. Introduced in V5.03b. Fixed.
- Device name passed to DLL was not recognized if it contained trailing spaces. Fixed.
- Device name passed to DLL was not recognized if it contained trailing spaces. Fixed.
- Disassemble function of J-Link DLL did not handle MOV Rx, <const> for Cortex-A/R cores correctly. Fixed.
- Flash programming during debug session with e2 studio did not work properly for Renesas R7FS7G2 and R7FS3A7 devices. Fixed.
- Flash programming for Infineon XMC4700 and XMC4800 devices did not work properly due to incorrect sectorization in DLL. Fixed.
- Flash programming of empty TI RM57, TMS570 and RM4 devices did not work properly. Fixed.
- Flash programming of Freescale SKEAZN64xxx2 did not work properly. Fixed.
- Flash sectorization of NXP LPC54xx devices was incorrect which could lead to problems when downloading to flash via GDB Server and other IDEs. Fixed.
- Freescale Vybrid: SPIFI flash programming did not work correctly, if boot ROM was executed after debug reset. Fixed.
- From now on, a device or at least a core must be specified when connecting to a target.
- Infineon XMC4200 series: Auto searching for SEGGER RTT block did not work properly. Fixed.
- Lifting of code-protection did not work properly for some PIC32MX devices. Fixed.
- Linux: Added support for multiple processes accessing the same J-Link.
- Mac OS X: Added support for multiple processes accessing the same J-Link.
- New command string added: SetCompareMode
- Reset did not work properly on Infineon TLE98xx devices if the first instruction of the application started on a non-4-byte aligned address. Fixed.
- Reset via Reset pin did not work properly for Infineon TLE98xx. Fixed.
- Sector size for Freescale MKL82Z128xxx7 series devices was incorrect. Fixed.
- Some Infineon XMC1401 device names were not recognized correctly. Fixed.
- Some LPC11A series devices were not listed correctly. Fixed.
- Some TLE98xx series devices were not listed correctly. Fixed.
- The debug interface API pointer were not invalidated on interface close. Fixed.
- Under special circumstances, watchdogs of ST STM32F7-series devices were not correctly handled. Fixed.
- Unsecure handling did not work properly on STM32F051 devices. Fixed.
Firmware
- Flasher ARM V4: Added pin override functionality for half-duplex UART
- Flasher ARM V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- Flasher ARM, RX, PPC, PRO V4: Added monitor target reference voltage during programming option.
- Flasher ARM, RX, PPC, PRO V4: Under very special circumstances, ASCII command interface could hang if commands are sent without waiting for a reply. Fixed.
- Flasher PORTABLE V4: Added pin override functionality for half-duplex UART
- Flasher PPC V4: Added pin override functionality for half-duplex UART
- Flasher PPC V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- Flasher PRO V4: Added pin override functionality for half-duplex UART
- Flasher PRO V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- Flasher RX V4: Added pin override functionality for half-duplex UART
- Flasher RX V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- J-Link PRO V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- J-Link V10: Added pin override functionality for half-duplex UART
- J-Link V10: Rebuild firmware to support HW V10.1
- J-Link V9: Added pin override functionality for half-duplex UART
- J-Link-OB-XMC4200: J-Link continued to receive VCOM data even if no terminal was connected which could result in garbage being received in case baud rate was not correct. Fixed.
- J-Link-OB-XMC4200: Tx line for VCOM was driven, even if no terminal was connected. Fixed.
- J-Link-OB-XMC4200: Under special circumstances, incorrect data was received on USB which could cause problems with VCOM and J-Link usage in parallel. Fixed.
- J-Link-OB-XMC4200: Under special circumstances, terminal application could hang when using VCOM functionality of J-Link. Fixed.
- JLink V9: Pin override implemented
- JLink: Half duplex mode on virtual COM
GDB Server
- Under special circumstances, the selected interface speed was not displayed correctly. Fixed.
- Under special circumstances, the selected interface speed was not displayed correctly. Fixed.
- Under special circumstances, the selected interface speed was not displayed correctly. Fixed.
- Under special circumstances, the selected interface speed was not displayed correctly. Fixed.
J-Flash
- Added flash programming support for Atmel ATSAMD10D14AU and ATSAMD11D14AU device series.
- Added flash programming support for Atmel ATSAMD10D14AU and ATSAMD11D14AU device series.
- Added flash programming support for Atmel ATSAMV70xxx and ATSAMV21xxx device series.
- Added flash programming support for Cypress CY8C4245xxx-Dxxx and CY8C4246xxx-Dxxx series devices.
- Added flash programming support for Cypress CY8C4247xxx-BLxxx series devices.
- Added flash programming support for Cypress PSoC4A-DS2 series devices (Cortex-M0).
- Added flash programming support for Infineon TLE984x device series.
- Added flash programming support for Infineon TLE984x device series.
- Added flash programming support for Infineon TLE9861, TLE9867, TLE9869, TLE9871, TLE9877 and TLE9879 series devices (Cortex-M3).
- Added flash programming support for Nordic Semi nRF52832_xxAA device series.
- Added flash programming support for Nordic Semi nRF52832_xxAA device series.
- Added flash programming support for NXP LPC1124 and LPC1125 device series.
- Added flash programming support for NXP LPC1124 and LPC1125 device series.
- Added flash programming support for ST STCOMET series devices (Cortex-M4).
- Added flash programming support for ST STM32F302RE, STM32F302VD, STM32F302VE, STM32F302ZD, STM32F302ZE, STM32F303ZD, STM32F318C8, STM32F318K8, STM32F328C8, STM32F398VE device series.
- Added flash programming support for ST STM32F302RE, STM32F302VD, STM32F302VE, STM32F302ZD, STM32F302ZE, STM32F303ZD, STM32F318C8, STM32F318K8, STM32F328C8, STM32F398VE device series.
- Added flash programming support for ST STM32F469 and STM32F479 series devices (Cortex-M4).
- Added flash programming support for ST STM32L486xx device series.
- Added Freescale Kinetis KL82 series devices MKL82Z128VMC7, MKL82Z128VLK7, MKL82Z128VLL7, MKL82Z128VLH7, MKL82Z128VMP7
- Added Freescale Kinetis KS22 series devices MKS22FN128VLL12, MKS22FN128VLH12, MKS22FN256VLL12, MKS22FN256VLH12.
- Added Freescale S32K144 series devices.
- Added new command line option "-min" which forces J-Flash to start minimized.
- Added sample project for Atmel AT91SAM4SD32 which shows how to set the security via Exit steps (AT91SAM4SD32_SetSecurity.jflash).
- Added sample project for Freescale MKL17Z64xxx4 (MKL17Z64xxx4.jflash) devices.
- Added sample project for Freescale MKL17Z64xxx4 (MKL17Z64xxx4.jflash) devices.
- Added sample project for Freescale MKV10Z32 series devices, which disables the Watchdog during Init sequence (MKV10Z32_DisableWatchdog.jflash).
- Added sample project for NXP LPC4357.
- Added sample project for Renesas R5F5523T3
- Added sample project for Renesas R5F5523T5
- Added sample project for Renesas R5F571ML
- Added support (via JTAG) for Renesas RX71M series devices.
- Added support for Analog Devices ADUCM362.
- Added support for Renesas RX23T series devices.
- Added watchdog handling for TI CC2538 series devices.
- Did not pass a device to the J-Link DLL on start application / unsecure. Fixed.
- Did not pass a device to the J-Link DLL on start application / unsecure. Fixed.
- Flash programming for Infineon XMC4700 and XMC4800 devices did not work properly due to incorrect sectorization in J-Flash. Fixed.
- Flash programming of Freescale SKEAZN64xxx2 did not work properly. Fixed.
- Flash sectorization of NXP LPC54xx devices was incorrect which could lead to problems when downloading to flash via GDB Server and other IDEs. Fixed.
- For Cortex-M devices, the incorrect labels were used for the Write/Read Register actions in the Exit/Init steps. Fixed.
- Minimum/Maximum value for relocation changed to -0xFFFFFFFF/0xFFFFFFFF.
- New command line options added: verifycrca, verifycrcs & verifycrcc
- Option "start application" in production settings is now configurable, start via SFR or via reset pin can be selected.
- RAM size for Analog Devices ADucM330 was not set correctly. Fixed.
- Sector size for Freescale MKL82Z128xxx7 series devices was incorrect. Fixed.
- Some LPC11A series devices were not listed correctly. Fixed.
- ST STM32F415OG has been missing. Fixed.
J-Flash SPI
- Added new flash devices to the list of known "auto-detect" flashes.
- Implemented support for custom init / exit steps.
J-Flash SPI CL
- Added new command line option -usb<SN> / -ip<HostName | xxx.xxx.xxx.xxx> which allows to specify connection settings.
J-Link Package
- Added an start menu entry for JTAGLoad.exe.
- Added J-Link script files for Renesas RZ/G1 multi-core debugging.
- Added new sample directory for J-Flash SPI example projects (%SEGGER_INST_DIR\Samples\JFlashSPI\Projects\Public\).
- Added separate Windows 2000 USB driver as USB CDC drivers are not supported in Windows 2000.
- Removed J-Scope as it will be distributed in a separate package from now on.
- Removed J-Scope as it will be distributed in a separate package from now on.
Manual
- UM08001: Added chapter "Low power debugging"
- UM08001: Added chapter "Low power debugging"
- UM08001: J-Link Manual: Added "Reference voltage (VTref)" to chapter "Target interfaces and adapters"
- UM08001: J-Link Manual: Added new sub-chapter (Send custom commands) which describes how to use the new "Send custom SPI commands" feature in J-Flash SPI (CL).
- UM08022: Flasher Manual: Updated section "Specifications" for all Flsaher models.
RTT
- Down buffer has been initialized with wrong buffer size. Fixed.
RTT Logger
- Added MRU device as default when device is empty.
Version V5.02l (2015-11-24)
DLL
- Added flash programming support for ST STM32F469 and STM32F479 series devices (Cortex-M4).
- Added support for Silicon Labs LB1 and BB3 series devices.
- Auto-unsecure for read-protected Microchip PIC32MZ devices did not work properly. Fixed.
- DLL could crash when using ARM11 devices and reading floating point registers. Fixed.
- Flash programming did not work for Atmel SAM3U devices. Fixed.
- The maximum supported SPI flash size for ST STA8088 series devices was limited to 2MB. Increased to 16 MB.
Firmware
- Flasher ARM, RX, PPC, PRO V4: Under special circumstances, the Flasher could hang after issuing an operation through the ASCII command interface (Telnet/RS232). Fixed.
J-Flash
- Added flash programming support for ST STM32F469 and STM32F479 series devices (Cortex-M4).
- Flash programming did not work for Atmel SAM3U devices. Fixed.
- Flash programming did not work properly for ARM11. Fixed.
- Incorrect scan chain selection settings were passed to the J-Link DLL when selecting auto detection. Fixed.
- The maximum supported SPI flash size for ST STA8088 series devices was limited to 2MB. Increased to 16 MB.
J-Flash SPI
- Command line agrument -usb was not handled correctly. Fixed.
Version V5.02k (2015-11-13)
Configurator
- Removed USB identification dialog (obsolete).
DLL
- Reduced the initialize time of the J-Link Control Panel.
- Under special circumstances, dual SPI flashes >= 16 MB were handled incorrectly. Fixed.
Firmware
- Flasher ARM, PRO V4, Portable: Added flash programming support in stand-alone mode for STM32F7 device series.
J-Flash
- Some "R5F5631x (allow DataFlash)" devices were not detected correctly. Fixed.
RX Glue DLL
- Flash size for Renesas RX63T series devices were incorrect. Fixed.
Version V5.02j (2015-11-06)
DLL
- Added Freescale Kinetis KS22 series devices MKS22FN128VLL12, MKS22FN128VLH12, MKS22FN256VLL12, MKS22FN256VLH12.
- Flash programming did not work properly for Vybrid (Q)SPI devices in parallel mode with flash images >= 16MB. Fixed.
- Programming of CFI NOR flash with multiple flashes connected in parallel did not work properly if flashes supported multi-item programming. Fixed.
- Under special circumstances, unsecure of locked Kinetis KE02 and KE04 series devices did not work properly. Fixed.
J-Flash
- Added Freescale Kinetis KS22 series devices MKS22FN128VLL12, MKS22FN128VLH12, MKS22FN256VLL12, MKS22FN256VLH12.
- Programming of CFI NOR flash with multiple flashes connected in parallel did not work properly if flashes supported multi-item programming. Fixed.
- RAMSize for 6KB RAM devices (e.g. TMPM372FWUG) was calculated incorrectly. Fixed.
Version V5.02i (2015-11-03)
DLL
- Freescale Vybrid: ROM Bootloader of the device was not executed properly when issuing a reset via J-Link. Fixed.
- Memory and handle leaks may occur when loading and freeing the DLL multiple times without also terminating the calling process. Fixed.
- Renesas Synergy S3 and S7: SWO did not work out-of-the box with SWOViewer etc. because chip-specific registers have not been setup correctly by DLL. Fixed.
Firmware
- J-Link-OB-RX621_SWD: Added support for ARM SWO.
J-Flash
- Under special circumstances, target power supply was turned off before connection has been closed. Fixed.
J-Flash SPI
- Under special circumstances, target power supply was turned off before connection has been closed. Fixed.
J-Flash SPI CL
- Under special circumstances, target power supply was turned off before connection has been closed. Fixed.
J-Link Package
- Added an start menu entry for the J-Link SWO viewer.
STM32 Utility
- Setting back write protection on STM32F42xx and STM32F43xx devices for sectors on second flash bank did not work properly. Fixed.
Version V5.02h (2015-10-29)
DLL
- Added watchdog handling for TI CC2538 series devices.
- Auto-detection of RTT control block did not work properly for NXP LPC18xx and LPC43xx devices. Fixed.
- Flash programming of empty TI RM57, TMS570 and RM4 devices did not work properly. Fixed.
- Flash programming of Freescale SKEAZN64xxx2 did not work properly. Fixed.
- Infineon XMC4200 series: Auto searching for SEGGER RTT block did not work properly. Fixed.
- Some Infineon XMC1401 device names were not recognized correctly. Fixed.
- Under special circumstances, watchdogs of ST STM32F7-series devices were not correctly handled. Fixed.
Firmware
- J-Link-OB-XMC4200: J-Link continued to receive VCOM data even if no terminal was connected which could result in garbage being received in case baud rate was not correct. Fixed.
- J-Link-OB-XMC4200: Under special circumstances, terminal application could hang when using VCOM functionality of J-Link. Fixed.
J-Flash
- Added watchdog handling for TI CC2538 series devices.
- Flash programming of Freescale SKEAZN64xxx2 did not work properly. Fixed.
- Sector size for Freescale MKL82Z128xxx7 series devices was incorrect. Fixed.
Version V5.02g (2015-10-26)
Commander
- Linux: Cursor function / command line history did not work properly. Fixed.
DLL
- Added Device Support for Atmel ATSAMA5D22 series devices.
- AMS AS7000: Flash downloads to address 0x0 did not work properly, even if flash was mapped at addr. 0x0. Fixed.
- Automatic JTAG speed detection did not work properly on ARM7/9 devices with adaptive clocking support and newer J-Link V10 models. Fixed.
- Connect to TI CC2538 devices did not work properly. Fixed.
- Connect under reset did not work properly for ST STM32L4 series devices. Fixed.
- Disassemble function of J-Link DLL did not handle MOV Rx, <const> for Cortex-A/R cores correctly. Fixed.
- Flash programming during debug session with e2 studio did not work properly for Renesas R7FS7G2 and R7FS3A7 devices. Fixed.
- Flash programming for Infineon XMC4700 and XMC4800 devices did not work properly due to incorrect sectorization in DLL. Fixed.
- Flash sectorization of NXP LPC54xx devices was incorrect which could lead to problems when downloading to flash via GDB Server and other IDEs. Fixed.
- Reset did not work properly on Infineon TLE98xx devices if the first instruction of the application started on a non-4-byte aligned address. Fixed.
- Some LPC11A series devices were not listed correctly. Fixed.
- Some TLE98xx series devices were not listed correctly. Fixed.
- The debug interface API pointer were not invalidated on interface close. Fixed.
- Unsecure handling did not work properly on STM32F051 devices. Fixed.
- Write protection detection did not work properly for Freescale Kinetis KV5x (Cortex-M7) series devices. Fixed.
Firmware
- Flasher ARM V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- Flasher ARM, RX, PPC, PRO V4: Under very special circumstances, ASCII command interface could hang if commands are sent without waiting for a reply. Fixed.
- Flasher PPC V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- Flasher PRO V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- Flasher RX V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- J-Link PRO V4: Under very special circumstances, firmware could hang after transmitting large amounts of data via ethernet interface. Fixed.
- J-Link V10: Rebuild firmware to support HW V10.1
- J-Link-OB-XMC4200: Tx line for VCOM was driven, even if no terminal was connected. Fixed.
- J-Link-OB-XMC4200: Under special circumstances, incorrect data was received on USB which could cause problems with VCOM and J-Link usage in parallel. Fixed.
J-Flash
- Added flash programming support for Infineon TLE9861, TLE9867, TLE9869, TLE9871, TLE9877 and TLE9879 series devices (Cortex-M3).
- Flash programming for Infineon XMC4700 and XMC4800 devices did not work properly due to incorrect sectorization in J-Flash. Fixed.
- Flash sectorization of NXP LPC54xx devices was incorrect which could lead to problems when downloading to flash via GDB Server and other IDEs. Fixed.
- For Cortex-M devices, the incorrect labels were used for the Write/Read Register actions in the Exit/Init steps. Fixed.
- Minimum/Maximum value for relocation changed to -0xFFFFFFFF/0xFFFFFFFF.
- RAM size for Analog Devices ADucM330 was not set correctly. Fixed.
- Some LPC11A series devices were not listed correctly. Fixed.
- ST STM32F415OG has been missing. Fixed.
J-Link Package
- Added an start menu entry for JTAGLoad.exe.
Version V5.02f (2015-10-02)
DLL
- Automatic JTAG speed detection when using Rowley Crossworks did not work properly on ARM7/9 devices with adaptive clocking support and newer J-Link V9 models. Fixed
- Connect under reset did not work properly for ST STM32L4 series devices. Fixed.
- Flash Programming did not work properly on Analog Devices ADucM360 devices. Fixed.
- Latest version of Keil MDK-ARM changed device naming scheme for some devices by adding ":<Core" after the device name. This could lead to the error message "The selected device is unknown by this version of the J-Link software". Fixed.
- Linux: In case multiple J-Links were connected to the same PC, an error message that no connection at all could be established, was thrown. As long as dialogs are not available under Linux, the DLL will connect to the first J-Link found.
- OS X: In case multiple J-Links were connected to the same PC, an error message that no connection at all could be established, was thrown. As long as dialogs are not available under OS X, the DLL will connect to the first J-Link found.
- Renamed STR9 "Bootbank: 1" device selections to "Bootbank 1"
- The O.K. button of the RX ID code verification window was displayed incorrectly. Fixed.
J-Flash
- Renamed STR9 "Bootbank: 1" device selections to "Bootbank 1"
- Renesas Synergy R7FS124 devices were missing. Fixed.
- Renesas Synergy R7FS3A7 devices were missing. Fixed.
- Renesas Synergy R7FS7G2 devices were missing. Fixed.
Version V5.02e (2015-09-25)
DLL
- Connecting to Freescale Kinetis V5x series devices (Cortex-M7) could cause an error message "Communication error while accessing AHB-AP". Fixed.
- Enhanced functionality of JLINKARM_GetDebugInfo() function
- Monitor mode support added in V5.02 could cause compatibility problems with Rowley CrossWorks IDE and ARM7/9 devices. Fixed.
- Read protection check did not work reliable for STM32 devices if core is in sleep mode. Fixed
- Some STM32 device names in Keil MDK-ARM were not recognized correctly. Fixed.
- The RX ID code verification edit field did not allow scrolling. Fixed.
- Unnecessary reset has been performed during connect on Atmel SAMD & SAML series devices. Fixed.
Firmware
- Flasher Portable: Under special circumstances, the SPI target interface did not work properly. Fixed.
- Flasher Pro: Added support for SPI interface.
- Flasher V3: Under special circumstances, the Flasher erased the EEPROM in stand-alone mode, even if it was not selected. Fixed.
Version V5.02d (2015-09-18)
DLL
- Added flash programming support for Infineon XMC1301-0064 series devices.
- Added flash programming support for Infineon XMC1401-0064 and XMC1401-0128 series devices.
- Added flash programming support for Renesas R5F563TB, R5F563TC and R5F563TE series devices.
- Added offical support for Atmel ATSAMA5D2x series devices (Cortex-A5).
- Auto-detection of Cortex-A17 cores failed. Fixed.
- Flash programming did not work for Freescale K66FN2Mxxx18 series devices, which were configured to for the high speed run mode (HSRUN). Fixed.
- For sectors > 8KB flash erasing did not work correctly for Atmel ATSAMG55xxx devices. Fixed.
- Sector size for ST STM32F030xC series devices was incorrect. Fixed.
- When overriding core auto-detection via J-Link script files, J-Link still tried auto-detection in some cases. Fixed.
Firmware
- Flasher Portable: Added support for SPI interface.
- Flasher Portable: Added support for SPI interface.
- J-Link V10: Connecting to J-Link did not work properly under OS X 10.11 (El Capitan). Fixed.
- J-Link V10: Under special circumstances, J-Link has toggled the tx-pin when a connection to the VCOM has been established. Fixed.
- J-Link V9: Under special circumstances, J-Link has toggled the tx-pin when a connection to the VCOM has been established. Fixed.
- J-Link-OB-MB9AF312K-Spansion: Under special circumstances, opening a terminal session (connecting to VCOM) in parallel to a debug session could cause the terminal session to freeze/hang. Fixed.
- J-Link-OB-STM32F072: When having multiple sessions accessing the J-Link and one made use of RTT, it could happen that a "failed to allocate 0xFFFFFFFF bytes of memory" error occurred. Fixed.
- JLink Ultra / Pro v4: HSS: Timer was not calculated correctly for sampling periods > 1500us. Fixed.
- LPC-Link2: Connection to LPC-Link did not work properly under OS X 10.11 (El Capitan). Fixed.
- LPCXpresso-OB: Connection to LPC-Link did not work properly under OS X 10.11 (El Capitan). Fixed.
J-Flash
- Added flash programming support for Infineon XMC1301-0064 series devices.
- Added flash programming support for Infineon XMC1401-0064 and XMC1401-0128 series devices.
- Added flash programming support for Renesas R5F563TB, R5F563TC and R5F563TE series devices.
- Added new command line option "-min" which forces J-Flash to start minimized.
- For sectors > 8KB flash erasing did not work correctly for Atmel ATSAMG55xxx devices. Fixed.
- J-Flash filled empty sectors always with 0xFF. Changed, so that it uses the erased value of the flash (which may be 0x00).
- Progress bar was not opened minimized although the main window was minimized. Fixed.
- Sector size for ST STM32F030xC series devices was incorrect. Fixed.
J-Flash SPI
- Added auto-detection support for Winbond W25Q16DW SPI flashes.
J-Link Package
- OS X: Package installer did not run correctly under OS X 10.11 (El Capitan). Fixed.
RTT
- SEGGER_RTT_SetTerminal() always blocked even if RTT mode was set to non-blocking. Fixed.
Version V5.02c (2015-09-10)
DLL
- Added support for Renesas Synergy devices.
- Chip erase did not work for Analog Devices ADucM33x devices. Fixed.
J-Flash
- Chip erase did not work for Analog Devices ADucM33x devices. Fixed.
Version V5.02b (2015-09-08)
DLL
- Added flash programming support for ST STM32F302RD series devices.
- Added generic (Q)SPI flash programming support for Renesas RZ/T1 series devices.
- After reset, programming of RZ/T1 series devices did not work properly. Fixed.
- Connecting to TI CC2650 devices which were in low power modes did not work properly. Fixed.
- MTB tracing did not work properly in uVision when single stepping application. Fixed.
Firmware
- Flasher PRO, RX, Portable V4: Added FINE support for Renesas RX series CPUs.
- J-Link V10: Under special circumstances, TMS did not remain at last output level after JTAG transmission. This could cause problems on TI CC2650 and TI AM3359 devices. Fixed.
- J-Link V9: Under special circumstances, TMS did not remain at last output level after JTAG transmission. This could cause problems on TI CC2650 and TI AM3359 devices. Fixed.
J-Flash
- Added flash programming support for ST STM32F302RD series devices.
J-Flash SPI
- Auto-detection did not work for S25FL256SAIF flashes. Fixed.
Version V5.02a (2015-09-04)
DLL
- Added flash programming support for Freescale KV42F64xxx16, KV42F128xxx16 and KV42F256xxx16 series devices.
- Added generic (Q)SPI flash programming support for Freescale Vybrid series devices.
- Added Quintic QN9020 also as NXP device to allow LPC-Link2 to work with it.
- Changed Realtek device name from "RTL8762" to "RTL8762A".
- Flash Programming of Flash bank 1 did not work correctly for Atmel ATSAMD4SDxxx devices. Fixed.
- Improved monitor mode handling so J-Link does no longer override monitor handler priority automatically, allowing some interrupts to continue while CPU is in monitor (halted).
- Some 32-bit Thumb instructions were not analyzed correctly when using the STRACE API (used by emIDE, J-Link Debugger, ...). Fixed.
- The official device names of Freescales MKV44Fxxxxxx15 and MKV46Fxxxxxx15 series devices have been changed to MKV44Fxxxxxx16 and MKV46Fxxxxxx16.
- Tracing on Cortex-M7 devices did not work correctly. Fixed.
- Under special circumstances, flash programming did not work for NXP LPC17xxx and LPC13xxx series devices. Fixed.
- Uppon request, we have removed the Freescale KV40F / KV43F / KV45F part numbers as device status have been changed to obsoleted.
Firmware
- J-Link V10: Under special circumstances firmware could hang if multiple of 512 bytes were sent in one USB packet. Fixed.
GDB Server
- Link to GDB Server manual in help menu did not work. Fixed.
J-Flash
- Added 6 KB as new entry in the project settings drop down menu for RAM size.
- Added flash programming support for Freescale KV42F64xxx16, KV42F128xxx16 and KV42F256xxx16 series devices.
- Changed Realtek device name from "RTL8762" to "RTL8762A".
- The official device names of Freescales MKV44Fxxxxxx15 and MKV46Fxxxxxx15 series devices have been changed to MKV44Fxxxxxx16 and MKV46Fxxxxxx16.
- Uppon request, we have removed the Freescale KV40F / KV43F / KV45F part numbers as device status have been changed to obsoleted.
J-Link Package
- Installer: J-Flash SPI and J-Link Remote Server (Tunneling mode) were not listed in the windows start menu. Corrected.
Manual
- UM08001: (J-Link User Guide): Added chapter about monitor mode debugging.
Version V5.02 (2015-08-28)
Commander
- Added new command "if <Interface>" which allows to select an interface by name (e.g. if SWD, if JTAG, etc...).
DLL
- Added commands to JLINK_RTTERMINAL_Control() to get buffer description
- Added Exec (Command string) to disable auto-correction of XPSR T-bit for Cortex-M devices. More info, see J-Link User's Guide "DisableCortexMXPSRAutoCorrectTBit".
- Added flash programming support for Analog Devices ADuCM320i, ADuCM322 and ADuCM322i series devices.
- Added flash programming support for Atmel ATSAMD09D14 and ATSAMHA1G16 series devices.
- Added flash programming support for Atmel ATSAMDA0 and ATSAMDA1 series devices (Cortex-M0).
- Added flash programming support for Cypress CY8C4128xxx-BLxxx, CY8C4248xxx-BLxxx, CYBL10xxx-256 series devices (PSoC4-256)
- Added flash programming support for Freescale MK82 series devices.
- Added flash programming support for Freescale MKE18F512xxx15 series devices.
- Added flash programming support for Infineon XMC1402, XMC1403 and XMC1404 series devices.
- Added flash programming support for Infineon XMC4700 and XMC4800 series devices.
- Added flash programming support for MSP432 series devices.
- Added flash programming support for Realtek RTL8762 series devices (Cortex-M0).
- Added flash programming support for Silicon Labs EFM32HGxxxF32 and EFM32HGxxxF64 series devices.
- Added flash programming support for TI TMS570LC4357ZWT series devices (Cortex-R5).
- Added flash programming support for ZMDI ZAMC4100 series devices.
- Added flash programming support for ZMDI ZSSC1956 series devices.
- Added programming for Page10 of the NVMRAM of Micronas HVC4223F series devices.
- Added QSPI flash programming support for Marvell 88MW300 and 88MW302 series devices.
- Added RTT data acquisition via DLL server to get data from multiple instances. Fixed.
- Added special handling for Freescale Kinetis series devices where active write protection has been detected.
- Added special handling for locked ZMDI ZAMC4100 and ZSSC1956 devices to allow to recover from locked state on connect.
- Added STRACE support for Cortex-R + ETB.
- Added support for Ambiq Apollo series devices.
- Added support for Cypress PSoC4A-L series devices (CY8C4246xxx-Lxxx, CY8C4247xxx-Lxxx, CY8C4248xxx-Lxxx)
- Added support for Freescale KL28 series devices
- Added support for STRACE code fetch events on Cortex-A + ETM/PTM
- Added support for STRACE code fetch events on Cortex-M + ETM
- Added support for STRACE code fetch events on Cortex-R + ETM
- Added support for STRACE code fetch events to the J-Link DLL. Currently supported for PTM trace on Cortex-A9.
- Corrected RAM Base addresses for Infineon XMC4700 and XMC4800 series devices. Fixed.
- Device name for KL28Z devices was displayed incorrectly. Fixed.
- Enabled pre and post verify during flash programming of TI MSP432 series devices. Improved.
- Flash cache offset calculation did not work properly. Fixed.
- Flash programming for Ambiq Apollo series devices only reached app. 40 KB/s of programming speed. Improved to app. 100 KB/s.
- Flash programming for Micronas HVC4223F series devices (Cortex M3) added.
- Flash programming of MKL28Z512xxx7 series devices did not work properly. Fixed.
- Flash programming turbo mode: If Prepare() of RAMCode changed CPU clock speed, DLL did not recognize this. Fixed.
- Flash programming: Added support for modifying single bytes in flash at runtime during debug session (via memory window or similar)
- Freescale KW20Z160xxx4, KW40Z160xxx4 and KW40Z160xxx4: Flash size has been set to 128 KB instead of 160 KB. Fixed.
- If a second DLL instance connected to the same core as another one, breakpoint units got disabled by accident, making breakpoints set by first instance non-working. Fixed.
- Improved EFM32xx flash programming algorithm. Added handling for flashes where sectors are protected by the lock bits.
- Improved flash programming speed for Atmel SAM4N, SAM4S, SAM4C & SAM4E.
- Improved maximum flash programming speed of TI MSP432 series devices.
- Improved our ZMDI flash algorithm so that flash download to the mirror address (0x00000000) also works.
- Links in DLL message boxes did not work properly. Fixed.
- MKV11Z128,MKV11Z64, MKV10Z128, MKV10Z64: Sector size corrected to 2KB
- NVRAM programming for Micronas HVC4223F series devices added.
- Programming of the option bytes of STM32L series devices caused a mass erase. Fixed.
- RAM start address of Infineon XMC4700 and XMC4800 series devices were incorrect. Fixed.
- Renesas RZ: After a reset via J-Link has been issued when debugging in RZ QSPI boot mode, sometimes a following Go() request to the CPU failed, causing the CPU to stuck at start of SPIFI flash area. Fixed.
- Spansion S25FL128 S25Fl129 could not be programmed caused by wrong set calculation. Fixed.
- SPIFI programming for NXP LPC4370 did not work properly due to no work RAM being assigned in DLL. Fixed.
- STM32F0, STM32F1, STM32F2, STM32F4, STM32L0 & STM32L1: Added unsecure handling for read protected STM32 devices to revoke protection on connect.
- STRACE for Cortex-A9 did not work properly if 32-bit branch packets were received. Fixed.
- STRACE: Under special circumstances, branch packets were analyzed incorrectly, resulting in incorrect trace information. Fixed.
- STRACE: When tracing on targets with PTM trace cell, branch packets were not analyzed correctly which could lead to incorrect trace. Fixed.
- Tracing on STM32F7 series devices (Cortex-M7) did not work properly. Fixed.
- Under special circumstances, flash download into the QSPI flash of 88MW30x series devices did not work. Fixed.
- Under special circumstances, the watchdog of Analog Devices ADuCM3025 series devices was not handled correctly during flash programming. Fixed.
- When selecting the Freescale MVF61NS151CMK50_A5 / MVF61NS151CMK50_M4, the J-Link DLL complained that this is an unknown device. Fixed.
Firmware
- Flasher ARM, PRO, PPC, RX, Portable V4: SELECT command did not create Flasher.ini properly if no "AUTO" command has been executed in advance. Fixed.
- Flasher RX V1 Firmware: Under special circumstances, select command did not work properly. Fixed.
- Flasher V4: Added new commands #FLIST and #MKDIR to ASCII command interface
- Flasher: Under special circumstances, flash breakpoints did not work properly for Cortex-M0 devices when interrupts where active. Fixed.
- Flasher: Under special circumstances, multi-bank support did not work in stand-alone mode. Fixed.
- If a connection to J-Link was not closed properly and a new one was opened, memory leaks could occur. Fixed.
- J-Link BASE/PLUS/EDU V9: Improved RTT speed
- J-Link EDU/BASE/PLUS V9: When debugging a Cortex-M device via JTAG (SWD is not affected), under special circumstances halting the CPU could fail. Introduced in beta V5.01a. Fixed.
- J-Link OB-SAM3U128-V2-NordicSemi: Sometimes, VCOM did not work properly after flashing a new image to the target device via MSD drag and drop functionality. Fixed.
- J-Link PRO V4: Improved memory reading speed when reading large chunks of data from non 32-bit start addresses.
- J-Link PRO V4: Improved SEGGER RTT reading speed.
- J-Link PRO V4: Under special circumstances, flash breakpoints did not work properly for Cortex-M0 devices when interrupts where active. Fixed.
- J-Link ULTRA+ V4: Improved memory reading speed when reading large chunks of data from non 32-bit start addresses.
- J-Link ULTRA+ V4: Improved SEGGER RTT reading speed.
- J-Link ULTRA+ V4: Under special circumstances, flash breakpoints did not work properly for Cortex-M0 devices when interrupts where active. Fixed.
- J-Link ULTRA+/PRO V4: When debugging a Cortex-M device via JTAG (SWD is not affected), under special circumstances halting the CPU could fail. Introduced in beta V5.01a. Fixed.
- J-Link ULTRA/PRO V4: Improved RTT speed
- J-Link V10: Improved memory reading speed when reading large chunks of data from non 32-bit start addresses.
- J-Link V10: Improved SEGGER RTT reading speed.
- J-Link V10: Under special circumstances, flash breakpoints did not work properly for Cortex-M0 devices when interrupts where active. Fixed.
- J-Link V9: Improved memory reading speed when reading large chunks of data from non 32-bit start addresses.
- J-Link V9: Improved SEGGER RTT reading speed.
- J-Link V9: Under special circumstances, flash breakpoints did not work properly for Cortex-M0 devices when interrupts where active. Fixed.
- J-Link-OB-STM32F072: Improved RTT speed
- J-Link-OB-STM32F072: When debugging a Cortex-M device via JTAG (SWD is not affected), under special circumstances halting the CPU could fail. Introduced in beta V5.01a. Fixed.
- J-Trace: Under special circumstances, flash breakpoints did not work properly for Cortex-M0 devices when interrupts where active. Fixed.
- RTT buffer was not deallocated correctly if connection to J-Link was closed. Fixed.
- SAM-ICE: Under special circumstances, flash breakpoints did not work properly for Cortex-M0 devices when interrupts where active. Fixed.
GDB Server
- GDB Server shows a warning when target connection is lost.
J-Flash
- Added flash programming support for Atmel ATSAMD09D14 and ATSAMHA1G16 series devices.
- Added flash programming support for Atmel ATSAMD21E18 series devices.
- Added flash programming support for Atmel ATSAMDA0 and ATSAMDA1 series devices (Cortex-M0).
- Added flash programming support for Atmel ATSAME70 series devices (Cortex-M7).
- Added flash programming support for Atmel ATSAMH21xxx and ATSAML21xxx series devices.
- Added flash programming support for Freescale MK82 series devices.
- Added flash programming support for Freescale MKE18F512xxx15 series devices.
- Added flash programming support for Infineon XMC1402, XMC1403 and XMC1404 series devices.
- Added flash programming support for Infineon XMC4700 and XMC4800 series devices.
- Added flash programming support for MSP432 series devices.
- Added flash programming support for Realtek RTL8762 series devices (Cortex-M0).
- Added flash programming support for Silicon Labs EFM32HGxxxF32 and EFM32HGxxxF64 series devices.
- Added flash programming support for TI TMS570LC4357ZWT series devices (Cortex-R5).
- Added flash programming support for ZMDI ZAMC4100 series devices.
- Added flash programming support for ZMDI ZSSC1956 series devices.
- Added programming for Page10 of the NVMRAM of Micronas HVC4223F series devices.
- Added sample projects for ST STM32F030RC devices.
- Added support for Ambiq Apollo series devices.
- Added support for Freescale KL28 series devices
- Changed default interface speed of new projects from 1000 kHz to 4000 kHz.
- Corrected RAM Base addresses for Infineon XMC4700 and XMC4800 series devices. Fixed.
- Device name for KL28Z devices was displayed incorrectly. Fixed.
- Flash programming for Ambiq Apollo series devices only reached app. 40 KB/s of programming speed. Improved to app. 100 KB/s.
- Flash programming for Micronas HVC4223F series devices (Cortex M3) added.
- Freescale KW20Z160xxx4, KW40Z160xxx4 and KW40Z160xxx4: Flash size has been set to 128 KB instead of 160 KB. Fixed.
- Implemented a check to make sure that we do not download any configuration to the Flasher which does not contain minimum bytes to program.
- Improved flash programming speed for Atmel SAM4N, SAM4S, SAM4C & SAM4E.
- Improved maximum flash programming speed of TI MSP432 series devices.
- MKV11Z128,MKV11Z64, MKV10Z128, MKV10Z64: Sector size corrected to 2KB
- NVRAM programming for Micronas HVC4223F series devices added.
- RAM start address of Infineon XMC4700 and XMC4800 series devices were incorrect. Fixed.
- Under special circumstances, the watchdog of Analog Devices ADuCM3025 series devices was not handled correctly during flash programming. Fixed.
J-Flash SPI
- The reset pin was toggled incorrect. Fixed.
J-Link Package
- Added J-Flash Lite to the J-Link software and documentation package.
J-Mem
- Added FINE and ICSP interface support in J-Mem.
RTT
- If a connection to J-Link was not closed properly and a new one was opened, memory leaks could occur. Fixed.
- RTT buffer was not deallocated correctly if connection to J-Link was closed. Fixed.
Version V5.00l (2015-08-07)
DLL
- MKV11Z128,MKV11Z64, MKV10Z128, MKV10Z64: Sector size corrected to 2KB
- Spansion S25FL128 S25Fl129 could not be programmed caused by wrong set calculation. Fixed.
- SPIFI programming for NXP LPC4370 did not work properly due to no work RAM being assigned in DLL. Fixed.
- STRACE: When tracing on targets with PTM trace cell, branch packets were not analyzed correctly which could lead to incorrect trace. Fixed.
Firmware
- Flasher ARM, PRO, PPC, RX, Portable V4: SELECT command did not create Flasher.ini properly if no "AUTO" command has been executed in advance. Fixed.
- Flasher RX V1 Firmware: Under special circumstances, select command did not work properly. Fixed.
J-Flash
- MKV11Z128,MKV11Z64, MKV10Z128, MKV10Z64: Sector size corrected to 2KB
J-Link Package
- Changed installer interface.
Version V5.00k (2015-07-31)
DLL
- Attaching to a running DLL instance via the DLL server could cause a race condition and communication breakdown. Fixed.
- Flash download on STM32F051 and F052 devices could fail with the warning "Debugger writes to flash after flash download is completed". Fixed.
- On some Cortex-A and Cortex-R devices setting hardware breakpoints did not work correctly (e.g. some new Atmel SAMA5 devices). Fixed.
- SiLabs EFM8/8051: Under special circumstances the internal error message "EFM8 (C2): SFR remap discarded. Too many remapped SFRs." could occur. Fixed.
Version V5.00j (2015-07-24)
DLL
- Programming of Cypress PSoC4 BLE-256 devices (CY8C4128xxx-BLxxx, CY8C4248xxx-BLxxx, CYBL10xxx-256) did not work properly. Fixed.
- SiLabs 8051 / EFM8: Writing to internal RAM (IDATA) at address 0x20 - 0x2F did not work properly. Fixed.
- SPIFI flash programming: Some Spansion S25FS128S and S25FS256S derivative configurations were not detected properly. Fixed.
Firmware
- Flasher: Added stand-alone mode flash programming support for Realtek RTL8762 series devices.
- Flasher: Added stand-alone mode flash programming support for ST STM32L 4 series devices. `
- Flasher: Added stand-alone mode flash programming support for ZMDI ZAMC4100 and ZSSC1956 series devices.
J-Flash
- Programming of Cypress PSoC4 BLE-256 devices (CY8C4128xxx-BLxxx, CY8C4248xxx-BLxxx, CYBL10xxx-256) did not work properly. Fixed.
Version V5.00i (2015-07-10)
DLL
- Under special circumstances, flash breakpoints did not work properly and could cause read memory errors. Fixed.
Firmware
- J-Link-OB-STM32F072: Handling of main LED was incorrect (Under special circumstances enable / disable LED was interchanged). Fixed.
GDB Server
- CPU was not automatically restarted after non-semihosting SVC calls. Fixed.
Version V5.00h (2015-07-09)
DLL
- Following Dialog Semiconductor devices were unknown in the J-Link DLL: DA14580, DA14581 and DA14583. Added.
GDB Server
- Semihosting did not work properly on big endian targets (Instruction that caused SVC call was read in incorrect endianness). Fixed.
- SVC calls were not handled correctly, when semihosting was enabled but not used by the call. Fixed.
Version V5.00g (2015-07-06)
DLL
- Changed naming of Freescale KW20/30/40 series devices from KWxx128xxx4 to KWxx160xxx4.
- Cortex-M: Instruction trace / STRACE API did not work properly if only short (several hundred) instructions were traced (sometimes STRACE API returned that no instructions have been executed). Fixed.
- Device name for KL28Z device series was displayed incorrectly. Fixed.
Firmware
- J-Link ULTRA+ V4 / PRO V4: When debugging on SiLabs 8051 devices via C2 debug interface, J-Link reported that interface is not supported. Fixed.
J-Flash
- Changed naming of Freescale KW20/30/40 series devices from KWxx128xxx4 to KWxx160xxx4.
- Device name for KL28Z device series was displayed incorrectly. Fixed.
J-Flash SPI
- The reset pin was toggled incorrect. Fixed.
Version V5.00f (2015-06-30)
DLL
- Flash programming did not work for Freescale KL28 series devices. Fixed.
- Linux/Mac: If an unknown device name was passed to the DLL, a segmentation fault could occur. Fixed.
- Renesas Synergy devices: Connecting to devices that were already in low power mode failed. Fixed.
- Renesas Synergy devices: Debugging did not work properly if device entered low power mode that disabled AHB accesses. Fixed.
- STRACE for Cortex-A and Cortex-R: LDR Rn, <label> instruction was interpreted as branch even if Rn was not PC. Fixed.
- Under special circumstances, flash programming could fail for Freescale MKM34Z256 series devices.
- Under special circumstances, flash programming did not work for Spansion S6E1A11/12 devices. Fixed.
J-Flash
- Flash programming did not work for Freescale KL28 series devices. Fixed.
- Under special circumstances, flash programming could fail for Freescale MKM34Z256 series devices.
J-Flash SPI
- The reset pin was not toggled on Connect / Disconnect. Fixed.
Version V5.00e (2015-06-23)
DLL
- Added some EFM8 aliases which were not known by the DLL but used by Keil PK51 V9.54a.
- QSPI flash programming on Renesas RZ could cause a buffer overflow if flash size exceeded 64 MB. Bug has been introduced in V5.00. Fixed.
- SiLabs EFM8: Affected devices: EFM8BB2, EFM8UB1. P3 @ addr. 0xB0 was not read/written correctly. Fixed.
- SiLabs EFM8: Affected devices: EFM8UB2, EFM8SB1, EFM8SB2. P2 @ addr. 0xA0 was not read/written correctly. Fixed.
- SPIFI flash programming: Some older serial NOR flashes from ST were not recognized correctly. Fixed.
GDB Server
- Exit code in semihosting command SysExit (0x18) was not handled correctly. Fixed.
Version V5.00d (2015-06-17)
Commander
- Command "testcspeed" did not work for NordicSemi nRF51 and nRF52 derivatives. Fixed.
- Command "testcspeed" did not work for Spansion FM4 derivatives. Fixed.
DLL
- Added alias for Freescale WPR1516: Now also the device name "WPR1516M2" is accepted.
- Added firmware for J-Link-OB-MB9AF312K-Spansion
- Added support for Freescale KV56F / KV58F series devices
- Added support for Freescale KW20Z / KW30Z / KW40Z series devices
- Added support for NordicSemi nRF52 series devices
- Flash programming did not work properly on some Freescale W-series devices. Fixed.
- SAM4L: Under special circumstances programming could fail with verify errors due to silicon bug in flash controller. Fixed.
- TELNET channel provided by DLL was closed if character 0x03 was received via RTT. Fixed.
Firmware
- Flasher: Flash programming did not work properly if multiple flash banks were used. Fixed.
- Flasher: The ASCII interface command "Select" did not work properly. Fixed.
- Flasher: Under special circumstances, blank check operation failed in stand-alone mode even though no error happened. Fixed.
J-Flash
- Added command line options "-setrxidcode" to allow setting of IDCODE to allow connecting to protected RX targets.
- Added support for Freescale KV56F / KV58F series devices
- Added support for Freescale KW20Z / KW30Z / KW40Z series devices
- Flash programming did not work properly on some Freescale W-series devices. Fixed.
- SAM4L: Under special circumstances programming could fail with verify errors due to silicon bug in flash controller. Fixed.
Version V5.00c (2015-06-11)
DLL
- Selecting a Renesas R5F51104, R5F51114 or R5F564MF lead to the error message "MEM_MAP_AddRegion Function called with start address greater than end address". Fixed. Other devices were not affected by this problem.
- Selecting a SiLabs SiM3C, SiM3L or SiM3U series device, could lead to the error message "Buffer overflow in memory block (1 bytes overflowed)" . Fixed. Other device series were not affected by this problem.
- Selecting an ST STM32F427xI / STM32F429xI device could cause an internal error of type MEM_MAP_AddRegion() or an memory allocation error. Fixed. Other STM series were not affected by this problem.
- Selecting the NXP PCF87750 as device could lead to a misleading error message regarding a pointer being invalid. Fixed. Other devices were not affected by this problem.
J-Flash
- Device ID for R5F56318 devices was incorrect. Corrected.
- Sectorization of Renesas R5F51104, R5F51114 and R5F564MF was incorrect. Fixed.
- Selecting a Renesas R5F51104, R5F51114 or R5F564MF lead to the error message "MEM_MAP_AddRegion Function called with start address greater than end address". Fixed. Other devices were not affected by this problem.
- Selecting a SiLabs SiM3C, SiM3L or SiM3U series device, could lead to the error message "Buffer overflow in memory block (1 bytes overflowed)" . Fixed. Other device series were not affected by this problem.
- Selecting an ST STM32F427xI / STM32F429xI device could cause an internal error of type MEM_MAP_AddRegion() or an memory allocation error. Fixed. Other STM series were not affected by this problem.
- Selecting the NXP PCF87750 as device could lead to a misleading error message regarding a pointer being invalid. Fixed. Other devices were not affected by this problem.
Version V5.00b (2015-06-10)
DLL
- Exec SetRXIDCode did not work properly. Fixed.
- Flash programming for flashes > 1 MB could fail (e.g. STM32F429 series was affected by this). Introduced in V5.00 with QSPI flash support. Fixed.
- QSPI flash programming: Improved read speed on Renesas RZ devices.
- QSPI flash programming: Macronix flash devices were not handled correctly. Fixed.
- Renesas RX R5F56138 devices with ID 0x0D018447 were detected incorrectly. Fixed.
- Renesas RX via FINE: Auto-enable of ongoing debug mode (caused flash programming internally) could fail. Introduced in V5.00 with QSPI flash support. Fixed.
- Under special circumstances, flash programming of Analog Devices ADuCM350 did not work properly. Fixed.
J-Flash
- Under special circumstances, flash programming of Analog Devices ADuCM350 did not work properly. Fixed.
Version V5.00a (2015-06-09)
DLL
- When performing a reset on an empty Kinetis K-series device, subsequent flash programming could fail. Introduced in V5.00 (when performing changes to support a new derivative from the V-series). Fixed.
J-Flash
- When performing a reset on an empty Kinetis K-series device, subsequent flash programming could fail. Introduced in V5.00 (when performing changes to support a new derivative from the V-series). Fixed.
Version V5.00 (2015-06-08)
Configurator
- Added option to increase max. SWO speed on J-Link ULTRA+ V4 and PRO V4 to 100 MHz.
DLL
- Added flash programming support for Atmel ATSAMR21x19 series.
- Added flash programming support for Freescale MK80FN256 devices.
- Added flash programming support for Nuvoton NUC131LC2AE, NUC131LD2AE, NUC131SC2AE and NUC131SD2AE series devices.
- Added flash programming support for ST STM32F746xE and STM32F746xG series devices.
- Added flash programming support for Toshiba TZ1000 and TZ1001 devices.
- Added general debug support for ARM SC000, SC100 and SC300 devices.
- Added support for multi-bank flash programming (Internal flash + CFI NOR flash + QSPI flash + ... can be programmed in one debug session)
- Connecting to J-Link-OB-STM32F103 failed with DLL versions >= V4.98. Fixed.
- Flash read back of empty Toshiba TZ100x devices, did not work correctly. Fixed.
- Freescale Kinetis E-series: Flash programming did not work correctly (bug introduced in beta V4.99a). Fixed.
- Improved connect to Kinetis devices (sometimes a device was reported as "secured" while it was not secured)
- Improved flash programming support (especially erase speed in J-Flash) for STM32L072/073 series devices.
- J-Link now continues identification process, even if DAP power up acknowledge bits in DP-Ctrl-Stat register do not get set.
- NXP LPC18xx / LPC43xx: Added generic SPIFI flash programming support, via J-Link.
- NXP LPC18xx / LPC43xx: Under special circumstances, SysTick was enabled right after reset. Fixed.
- Renesas RZ/A1H and A1L: Added generic SPIFI flash programming support
- SWO tab in J-Link Control did not display the values correctly. Fixed.
- Under special circumstances, the watchdog of Kinetis L-series devices was not correctly handled. Fixed.
- Under special circumstances, unlocking of secured STM32L series devices did not work. Fixed.
DLL Updater
- Added Percepio trace products.
Firmware
- Flasher ARM V4: Added Support for SPI interface.
- Flasher ARM, Portable, PRO, RX: Added functionality to override program and erase timeouts.
- Flasher ARM, Portable, PRO, RX: For flashes, where we are not allowed to perform a blank check, erase chip did not work properly in stand-alone-mode. Fixed.
- Flasher V4: Programming of Cypress PSoC4 device series did not work in stand-alone mode. Fixed.
- Flasher: Added stand-alone mode flash programming support for Toshiba TZ100x series.
- J-Link ULTRA+ V4 / PRO V4: Increased max. SWO speed to 100 MHz
- JLink-OB-SAM3U128-mbedBTL-NordicSemi: Updated MSD files for new nRF52 based boards
- JLink-OB-SAM3U128-NordicSemi: MSD reprogramming of a device that had UICR protection set could fail. Fixed.
- JLink-OB-SAM3U128-NordicSemi: MSD reprogramming of a device that had UICR protection set could fail. Fixed.
J-Flash
- Added an option to the project settings to override the default program and erase timeouts.
- Added command line options "-usb" and "-ip" to allow temporary override of the J-Link connection settings via command line, for the current session.
- Added flash programming support for Atmel ATSAMR21x19 series.
- Added flash programming support for Cypress CY8C4013 and CY8C4014 series devices.
- Added flash programming support for Freescale MK80FN256 devices.
- Added flash programming support for Nuvoton NUC131LC2AE, NUC131LD2AE, NUC131SC2AE and NUC131SD2AE series devices.
- Added flash programming support for ST STM32F746xE and STM32F746xG series devices.
- Added flash programming support for Toshiba TZ1000 and TZ1001 devices.
- Added new commands to init steps to merge target data into the image to be flashed. Var Write File 8bit, Var Write File 16bit, Var Write File 32bit
- Added sample projects for Toshiba TZ100x series.
- Added target voltage information (VTref) to the LOG window on connect.
- Added user row flash programming support for Atmel SAMD and SAMR series.
- Flash read back of empty Toshiba TZ100x devices, did not work correctly. Fixed.
- Under special circumstances, target power supply has not been removed by the J-Link (if configured). Fixed.
- When having multiple flash banks and some of them were using custom RAMCodes, readback data of other banks than bank 0 was incorrect. Fixed.
J-Flash SPI
- New product added (Windows).
J-Flash SPI CL
- New product added (Windows, Linux).
STM32 Utility
- Added a build of the STM32 Utility to the J-Link software package for Linux and MAC.
- Added command line options (e.g. -SetDeviceFamily, -exit, etc...).
- Added support to unlock locked ST STM32F0 series devices.
- Added the STM32 Utility to the Linux and MAC package.
- Reduced minimum target voltage from 2V to 0.5V.
- Under special circumstances, "press any key to exit" did not work. Fixed.
Version V4.98e (2015-05-05)
DLL
- Added flash programming support for STM32L072/073 series devices.
- Connecting to J-Link-OB-STM32F103 failed with DLL versions >= V4.98. Fixed.
- Under special circumstances, the watchdog of Kinetis L-series devices was not correctly handled. Fixed.
Firmware
- JLink-OB-SAM3U128-NordicSemi: MSD reprogramming of a device that had UICR protection set could fail. Fixed.
J-Flash
- Under special circumstances, target power supply has not been removed by the J-Link (if configured). Fixed.
- When having multiple flash banks and some of them were using custom RAMCodes, readback data of other banks than bank 0 was incorrect. Fixed.
Version V4.98d (2015-04-28)
DLL
- Added flash programming support for Nuvoton NUC029L series.
- If a flash sector was only half-way erased but read as empty by the CPU, programming errors could occur during flash download (Mainly seen on Infineon XMC series CPUs). Fixed.
- The watchdog of Kinetis L-series devices has been disabled by the DLL on connect. We removed this behavior and make sure that the watchdog will be fed when enabled.
Firmware
- J-Link-OB-XMC4200: Under special circumstances, glitches could occur when the J-Link DLL opened a connection to the J-Link OB and selected a target interface (SWD, ...). Fixed.
- JLink-OB-SAM3U128-NordicSemi: Under special circumstances, MSD programming did not work properly if hex files contained non 16-byte aligned data segments. Fixed.
J-Flash
- Added flash programming support for Nuvoton NUC029L series.
Version V4.98c (2015-04-23)
DLL
- Added flash programming support for Atmel ATSAML21E18 devices.
- Added watchdog handling to the Atmel SAMD series flash algorithm.
- Breakpoints did not work on SiLabs EFM8UB2x devices. Fixed.
- Cortex-M: Some new CoreSight components where not identified properly. Fixed.
- Kinetis V-series: ROM table address space could not be read correctly, if device was selected. Fixed.
- Microchip PIC32: Overstepping breakpoints in MIPS16e mode (16-bit instructions) did not work properly. Fixed.
- Reading RTT data from Channel 1 and above did not work with older J-Link models. Fixed.
- Restarting RTT causes memory reallocation. Fixed.
- RTT could cause a crash on empty devices and while flash programming was in progress. Fixed.
- Some PIC32MZ derivatives where reported to be "unknown" by the DLL, when selected in Microchip MPLAB X IDE. Fixed.
Firmware
- J-Link V9: Breakpoints did not work on SiLabs EFM8UB2x devices. Fixed.
- JLink-OB-SAM3U128-mbedBTL-NordicSemi: Under special circumstances, incorrect data was received by the OB due to a problem in the USB driver. Fixed.
GDB Server
- Response for "monitor watihalt" command added.
J-Flash
- Added watchdog handling to the Atmel SAMD series flash algorithm.
RTT Client
- If a string ended with \r\n (very unusual), an access violation could occur. Fixed.
Version V4.98b (2015-04-10)
Commander
- Adapted "resetconf" command to be able to handle J-Links with dynamic config area size.
DLL
- Automatic recovery mode implemented in case a debugger selects an SWD speed that is too high for the connected target. (e.g. some versions of Keil ARM-MDK selected 20 MHz which is too high for most targets)
- Infineon XMC4xxx series: In case a sector was not erased completely (e.g. due to power loss during erase), reprogramming could fail. Fixed.
- J-Link-OB-XMC4000: If the XMC device was in a specific state, it could happen that J-Link-OB "hung" when trying to connect to the device. Fixed.
- Some SiLabs EFM8 series devices produced an "Device series: <Unknown> series device" output in J-Link Commander. Fixed.
- STM32F0x/STM32L0x Watchdog was not stopped on halt. Fixed.
- Trace analyzer for STRACE API did not identify LDR R15, [PC + <Off>] instruction as branch, in ARM mode. Fixed.
- Under special circumstances, debugging on Renesas RX63x targets, running at very low speeds (~32 kHz) did not work properly. Fixed.
- Unlocking pages during flash programming for Atmel SAMC, SAMD, SAMR and SAML did not work properly. Fixed.
- Writing CP15 registers on Cortex-A9 targets did not work. Fixed.
Firmware
- Flasher Portable, PRO, RX: When working on slow-running RX63x devices, communication could break down. Fixed.
- J-Trace Cortex-M V3: Firmware reported max. 50 Hz, instead of 1 kHz, sampling rate for J-Link HSS. Fixed.
- JLink-OB-SAM3U128-mbedBTL-NordicSemi: VCOM functionality did not work properly with Non-HW-Flow-Control targets. Fixed.
J-Flash
- Flash size of NXP LPC1519 and LPC1549 was incorrectly shown as 248 KB instead of 256 KB. Fixed.
- Unlocking pages during flash programming for Atmel SAMC, SAMD, SAMR and SAML did not work properly. Fixed.
Version V4.98a (2015-03-26)
Commander
- Nested ROM tables were not detected properly. Fixed.
- Some CoreSight components were not detected properly. Fixed.
DLL
- Flash programming of 2 MB SAM4C devices did not work properly for second MB. Fixed.
- Improved AMD flash RAMCode to support both: Flashes that expect 16-bit offsets and 12-bit offsets.
- PTM-A9 CoreSight component was not detected properly on Renesas RZ device, even if it was selected as device in the DLL. Fixed.
GDB Server
- For Cortex-A/R GDB Server reported wrong registers when no extended register set is used. Fixed.
- GDB Server crashed when requesting unknown register indices. Fixed.
J-Flash
- Flash programming of 2 MB SAM4C devices did not work properly for second MB. Fixed.
- Improved AMD flash RAMCode to support both: Flashes that expect 16-bit offsets and 12-bit offsets.
- NXP LPC54 series was missing. Fixed.
Version V4.98 (2015-03-20)
Commander
- Added command to allow creation/removal of a secure area on Flasher probes.
DLL
- Added a custom connect sequence for Maxim MAX3255x devices which entered shutdown mode.
- Added flash programming suppor for Atmel ATSAM4C4C and ATSAM4CMS4C devices.
- Added flash programming support for AMS AS7000 devices (Cortex-M0).
- Added flash programming support for Atmel ATSAM4E16CB and ATSAM4E8CB devices.
- Added flash programming support for Cypress CYPD21xxx series (CCG2).
- Added flash programming support for EZR32LG230Fxxxxxx, EZR32LG330Fxxxxxx, EZR32WG230Fxxxxxx and EZR32WG330Fxxxxxx devices.
- Added flash programming support for Freescale MK26FN devices (Cortex-M4).
- Added flash programming support for LPC18S10, LPC18S30, LPC18S37, LPC18S50 and LPC18S57 security series.
- Added flash programming support for LPC5410x series devices (Cortex-M4)
- Added flash programming support for MKV10Z64, MKV10Z128, MKV11Z64 and MKV11Z128 devices.
- Added flash programming support for Renesas R7S910017, R7S910018, R7S910117 and R7S910118 devices (Cortex-R4).
- Added flash programming support for Renesas R7S910xxx (RZ/T1) devices (Cortex-R4F).
- Added flash programming support for Silicon Labs EFM32G800, EFM32LG360, EFM32WG360 and EFM32WG900 series.
- Added flash programming support for Spansion S6E2CC1xxx, S6E2CC2xxx, S6E2CC3xxx, S6E2CC4xxxand and S6E2CC5xxx devices.
- Added flash programming support for Spansion S6E2CC8xxx, S6E2CC9xxx and S6E2CC8Axxx devices.
- Added flash programming support for ST STM32F334x4, STM32F334x6 and STM32F334x8 devices (Cortex-M3).
- Added flash programming support for ST STM32F4, STM32F098xC and STM32F303RD devices.
- Added flash programming support for ST STM32L162RE, STM32L162VD-X and STM32L162VE devices.
- Added flash programming support for ST STM32L4 devices.
- Added flash programming support for STM32F756xE and STM32F756xG devices (Cortex-M7).
- Added flash programming support for TI CC1310F128 devices.
- Added flash programming support for TI CC2620F128, CC2630F128, CC2640F128 and CC2650F128.
- Added flash programming support for TI RM57L devices (Cortex-R5).
- Added flash programming support for TI SM470R1B1M devices.
- Added flash programming support for TI TMS570LS0232 devices.
- Added full flash programming support for Freescale KL13Z32/64 and KL33Z32/64 devices.
- Added full flash programming support for Freescale KM34Z256 devices.
- Added full J-Link support for Atmel SAMD21G17AU and SAMD21G18AU devices.
- Added new firmware for NordicSemi nRF51 V2 series kits with MSD programming support. New firmware shows additional constant files on MSD.
- Added new J-Link script file functions: JTAG_StartDR(); JTAG_WriteDRCont(); JTAG_WriteDREnd();
- Added QSPI flash programming support for Renesas RZ/A1L series devices.
- Added special connect for STM32F756xE and STM32F756xG devices which allows connect while CPU is in sleep mode.
- Cortex-M: Detection of CoreSight components improved.
- Erase of MAX32555 devices did not work. Fixed.
- Fixed cyclecount enable when enabling SWO.
- Fixed disassembly of ARM instructions.
- Flash programming of CFI compliant flashes connected to a Cortex-R4 failed. Fixed.
- Flash Programming on Analog Devices CM40x series devices could fail. Fixed.
- Flash size of Spansion MB9AF112K and MB9AF111K devices was incorrect. Fixed.
- Freescale MKM34Z256xxx5 series devices: Corrected sector size of internal flash
- Improved Freescale Kinetis flash algorithm so that supported supported flash programming command wide is auto detected.
- Improved the device specific module for Analog Devices CM40 devices.
- Improved the internal connect sequence for Analog CM408F series.
- Infineon XMC4xxx devices: Under special circumstances, if multi-bit ECC errors in the internal flash occurred (e.g. due to power-loss during programming), flash could not be erased/reprogrammed correctly. Fixed.
- Instruction set simulation for ARMv7-M 32-bit instructions improved.
- J-Link script files: Added new function to pass a script file version to the J-Link DLL (GetScriptVersion()).
- J-Link script files: Added some new _CORESIGHT_ functions.
- Multiple instances might have caused high CPU usage. Fixed.
- Reset on Analog Devices CM40x series devices could fail. Fixed.
- SiLabs EZR32 series: Sector erase did not work properly. Fixed.
- Support for SiLabs EFM8 EFM8BB, EFM8SB, EFM8UB series added.
- Under special circumstances, CYCCNT was disabled by accident. Fixed.
- Under special circumstances, flash programming did not work properly for Renesas RZ/T1 devices. Fixed.
- Under special circumstances, flash programming for (RZ/T1) devices (Cortex-R4F) did not work properly. Fixed.
- Under special circumstances, flash programming for Renesas R7S910xxx (RZ/T1) devices did not work properly. Fixed.
- Under special circumstances, flash programming of flash macro 2 (bank 2) of CY8C4xxxxxx-Mxxx devices did not work properly. Fixed.
- Updated LPCXpresso-OB license text.
DLL Updater
- Added Forth SwiftX to list of IDEs that can be updated.
Firmware
- Flasher ARM/PPC/RX/PRO V4: Added handling for Cntdown.txt file (More info, see manual)
- Flasher ARM/PPC/RX/PRO V4: Added handling for secure area. (More info, see manual)
- Flasher ARM/PPC/RX: Reprogramming secured/read-protected Kinetis L-series devices did not work properly in stand-alone mode. Fixed.
- Flasher: ASCII Interface: When reading large files at once, under special circumstances, Flasher firmware could crash. Fixed.
- Flasher: Improved Key file support for stand-alone mode.
- Flasher: Stand-alone mode might fail, if flash has undefined erase values. Fixed.
- Under special circumstances, for J-Links which support programming via MSD, the name of some files being shown on the OB were corrupted. Fixed.
GDB Server
- Added mode specific CPU registers for info all command for Cortex-A/R.
- Multiple instances might have caused high CPU usage. Fixed.
- Under special circumstances semi-hosting handling started application wrongly. Fixed.
GDB Server CL
- Command-line option '-nogui' added to suppress dialog windows.
J-Flash
- Added flash programming suppor for Atmel ATSAM4C4C and ATSAM4CMS4C devices.
- Added flash programming support for AMS AS7000 devices (Cortex-M0).
- Added flash programming support for Atmel ATSAM4E16CB and ATSAM4E8CB devices.
- Added flash programming support for Cypress CYPD21xxx series (CCG2).
- Added flash programming support for EZR32LG230Fxxxxxx, EZR32LG330Fxxxxxx, EZR32WG230Fxxxxxx and EZR32WG330Fxxxxxx devices.
- Added flash programming support for Freescale MK26FN devices (Cortex-M4).
- Added flash programming support for LPC18S10, LPC18S30, LPC18S37, LPC18S50 and LPC18S57 security series.
- Added flash programming support for MKV10Z64, MKV10Z128, MKV11Z64 and MKV11Z128 devices.
- Added flash programming support for Renesas R7S910017, R7S910018, R7S910117 and R7S910118 devices (Cortex-R4).
- Added flash programming support for Renesas R7S910xxx (RZ/T1) devices (Cortex-R4F).
- Added flash programming support for Silicon Labs EFM32G800, EFM32LG360, EFM32WG360 and EFM32WG900 series.
- Added flash programming support for Spansion S6E2CC1xxx, S6E2CC2xxx, S6E2CC3xxx, S6E2CC4xxxand and S6E2CC5xxx devices.
- Added flash programming support for Spansion S6E2CC8xxx, S6E2CC9xxx and S6E2CC8Axxx devices.
- Added flash programming support for ST STM32F334x4, STM32F334x6 and STM32F334x8 devices (Cortex-M3).
- Added flash programming support for ST STM32F4, STM32F098xC and STM32F303RD devices.
- Added flash programming support for ST STM32L162RE, STM32L162VD-X and STM32L162VE devices.
- Added flash programming support for ST STM32L4 devices.
- Added flash programming support for STM32F756xE and STM32F756xG devices (Cortex-M7).
- Added flash programming support for TI CC1310F128 devices.
- Added flash programming support for TI CC2620F128, CC2630F128, CC2640F128 and CC2650F128.
- Added flash programming support for TI RM57L devices (Cortex-R5).
- Added flash programming support for TI SM470R1B1M devices.
- Added flash programming support for TI TMS570LS0232 devices.
- Added full flash programming support for Freescale KL13Z32/64 and KL33Z32/64 devices.
- Added full flash programming support for Freescale KM34Z256 devices.
- Added sample projects for TI CC1310xx and CC26x0 devices.
- Flash programming of CFI compliant flashes connected to a Cortex-R4 failed. Fixed.
- Flash size of Spansion MB9AF112K and MB9AF111K devices was incorrect. Fixed.
- Freescale MKM34Z256xxx5 series devices: Corrected sector size of internal flash
- Infineon XMC4xxx devices: Under special circumstances, if multi-bit ECC errors in the internal flash occurred (e.g. due to power-loss during programming), flash could not be erased/reprogrammed correctly. Fixed.
- Parameters for command line option -saveas to save as .bin/.c file are now optional. If not set the whole file is saved.
- SiLabs EZR32 series: Sector erase did not work properly. Fixed.
- Under special circumstances, flash programming did not work properly for Renesas RZ/T1 devices. Fixed.
- Under special circumstances, flash programming for (RZ/T1) devices (Cortex-R4F) did not work properly. Fixed.
- Under special circumstances, flash programming for Renesas R7S910xxx (RZ/T1) devices did not work properly. Fixed.
- Under special circumstances, flash programming of flash macro 2 (bank 2) of CY8C4xxxxxx-Mxxx devices did not work properly. Fixed.
Manual
- Flasher User Guide updated.
STM32 Utility
- Changed the generic behavior of the STM32 Utility, so that the device series have to be selected as the auto detection does not work reliable for all ST devices.
Version V4.96m (2015-03-13)
Commander
- By mistake, J-Link Commander returned 1 (exit code for error) even in case no error happened. Fixed.
- Output of "testnet" command was not indented correctly. Fixed.
DLL
- Corrected flash sector size for TI CC26xxF128 devices.
- Flash size of Spansion MB9AF112K and MB9AF111K devices was incorrect. Fixed.
- Instruction set simulation for ARMv7-M 32-bit instructions improved.
- J-Link-OB NordicSemi nRF51 V2 series kits: Under special circumstances, MSD programming under Mac OS X Yosemite did not work properly. Fixed
- Keil MDK: Error message "Invalid ROM table" did pop up if J-Link Script files were used or device needed a special DLL-internal connect. Fixed.
- Under special circumstances, CYCCNT was disabled by accident. Fixed.
J-Flash
- Corrected flash sector size for TI CC26xxF128 devices.
- Flash size of Spansion MB9AF112K and MB9AF111K devices was incorrect. Fixed.
J-Link Package
- Under special circumstances, some strings were not stored to registry correctly. Fixed
Version V4.96l (2015-02-25)
DLL
- Multiple instances might have caused high CPU usage. Fixed.
Firmware
- Flasher: Under special circumstances, flash programming did not work correctly. Fixed.
GDB Server
- Multiple instances might have caused high CPU usage. Fixed.
Version V4.96i (2015-02-19)
DLL
- SiLabs 8051 devices: If no reset was performed after "erase" command in J-Link Commander, old flash contents were still shown on memory read. Fixed.
- SiLabs 8051 devices: On devices with multiple SFR pages, flash programming could fail, if another SFR page than page 0 was selected in SFRPAGE register, at the time the flash was programmed. Fixed.
Firmware
- SiLabs 8051 devices: If no reset was performed after "erase" command in J-Link Commander, old flash contents were still shown on memory read. Fixed.
- SiLabs 8051 devices: On devices with multiple SFR pages, flash programming could fail, if another SFR page than page 0 was selected in SFRPAGE register, at the time the flash was programmed. Fixed.
Version V4.96h (2015-02-13)
DLL
- Added support for Infineon TLE9864 series devices.
- Improved J-Link behavior when connecting to locked SiLabs 8051 devices.
- SiLabs 8051 devices: Added support for "erase" command in J-Link Commander.
- SiLabs 8051: Lock byte was not handled correctly on all devices. Fixed.
- STRACE: Added ETB initialization for NXP LPC43xx.
- Trace using ETB on Cortex-M did not work correctly. Fixed.
- Under some circumstances getting the SerialNo of the connected J-Link did not work on Linux / OS X. Fixed.
Firmware
- Improved J-Link behavior when connecting to locked SiLabs 8051 devices.
- J-Link V9: For SiLabs 8051 devices with data flash, under special circumstances, flash programming did not work correctly.
GDB Server
- Did not close correctly on disconnect on Mac and Linux. Fixed.
Version V4.96g (2015-02-06)
DLL
- On some SiLabs 8051 unlocking a locked device did not work correctly. Fixed.
- SiLabs 8051: If unlock message box was canceled with ESC, this was interpreted as "Yes" by accident. Fixed.
GDB Server
- Under special circumstances semi-hosting handling started application wrongly. Fixed.
Version V4.96f (2015-02-04)
DLL
- SiLabs 8051: Under special circumstances, breakpoint registers were not written correctly, so breakpoints did not work as expected. Fixed.
GDB Server
- More specific exit codes added (for proper error detection / handling)
Version V4.96e (2015-02-02)
DLL
- SiLabs 8051: When writing CPU registers via J-Link DLL and then reading DDATA / IDATA space where CPU registers were located, for some registers incorrect values were read. Fixed.
Version V4.96d (2015-01-29)
Firmware
- Under special circumstances, cache maintenance operations on Cortex-M7 and Cortex-A/R could fail. Introduced in V4.96c by the change for Cortex-M7. Fixed. Affected firmwares: J-Link BASE / PLUS V9, J-Link ULTRA+ / PRO V4, SAM-ICE V8
Version V4.96c (2015-01-28)
DLL
- Added flash programming support for MKL17Z32xxx4, MKL17Z64xxx4, MKL27Z32xxx4, MKL27Z64xxx4 series devices.
- Added some Atmel ATSAMD11 device name aliases.
- Added some Atmel ATSAMD21 device name aliases.
- Added unsecure for locked SiLabs 8051 devices.
- Cortex-M7: Hardware breakpoints could not be used with addresses > 0x1FFFFFFF. Fixed.
- LPC-Link 2: DLL could hang if JTAG/SWD speeds higher than 4 MHz were selected. Fixed.
- SiLabs 8051: Improved J-Link behavior, in case incorrect clock setup has been performed and device is no longer responding.
- Under special circumstances, a message box popped up that Cortex-M7 is not supported by the connected J-Link, even if it was. Fixed.
- Under special circumstances, flash programming on some SiLabs 8051 series devices did not work properly. Fixed.
Firmware
- Cortex-M7: Software breakpoints did not work properly, if I/D cache of core was enabled. Fixed.
- J-Link V9: SiLabs 8051: DDATA accesses which crossed the area boundaries, were not handled correctly. Fixed.
GDB Server CL
- GDB Server did not handle signals correctly. Fixed.
J-Flash
- Added flash programming support for MKL17Z32xxx4, MKL17Z64xxx4, MKL27Z32xxx4, MKL27Z64xxx4 series devices.
- Corrected core ID for R5F5631G
Version V4.96b (2015-01-19)
DLL
- "loadbin" in J-Link Commander did not trigger full flash download on SiLabs 8051 devices. Fixed.
- Debugging on SiLabs C8051F38x series C2 devices did not work properly. Fixed.
- Improved single stepping speed on SiLabs 8051 C2 devices
GDB Server
- Added VFP register support for Cortex-A/R to GDB Server.
Version V4.96a (2015-01-14)
DLL
- Added flash programming support for Freescale MK26FN series devices.
- Cortex-A/R and SWD: Reading current registers failed and caused error messages. Fixed.
- Flash programming Freescale SKEAZN8, SKEAZN16, SKEAZN32 and SKEAZN64 devices did not work properly. Fixed.
- Under special circumstances, breakpoints for Cortex-A/R big endian devices did not work properly. Fixed.
- V9: Some new SiLabs 8051 devices could not be detected via C2 interface. Fixed.
Firmware
- V9: Some new SiLabs 8051 devices could not be detected via C2 interface. Fixed.
J-Flash
- Added flash programming support for Freescale MK26FN series devices.
- Flash programming Freescale SKEAZN8, SKEAZN16, SKEAZN32 and SKEAZN64 devices did not work properly. Fixed.
Version V4.96 (2014-12-22)
Commander
- J-Link V9.2 and V9.3 were identified as V9.0. Fixed.
DLL
- (Second) flash download in the same debug session did not work properly when SEGGER RTT was active. Introduced in V4.95a. Fixed.
- (Second) flash download in the same debug session did not work properly when SEGGER RTT was active. Introduced in V4.95a. Fixed.
- (Second) flash download in the same debug session did not work properly when SEGGER RTT was active. Introduced in V4.95a. Fixed.
- Accesses to XRAM failed on C8051F850 devices. Fixed.
- Added support for TI RM57L843ZWT and TMS570LC4357ZWT devices (Cortex-R5).
- Cortex-A/R: Under special circumstances, connecting to multi-core devices could fail, if one of the cores was not powered (even if this specific core was not addressed in the debug session). Introduced in V4.94c. Fixed.
- J-Link LITE RX firmware update removed FINE support, needed to be used with Serious Integrated RX100 Kits, by accident. Fixed.
- SiLabs 8051: If more breakpoints were set than supported by the target, no error was returned by the DLL. Fixed.
Firmware
- Flasher PRO: Under special circumstances, the option bytes of STM32L0 devices have been programmed to reset values. Fixed.
- J-Link V9: Debugging and speed on SiLabs 8051 devices improved
- J-Link V9: Under special circumstances, TRST was re-initialized to another state. Fixed.
GDB Server
- Added error output on close to command line version.
- Added option '-timeout' to configure connection timeout of GDB Server.
- Changed connection timeout for CL version to 0 seconds.
RTT Viewer
- Added automatic open of Terminal tabs on output.
- Added automatic reconnect and clear for attach mode.
- Terminal tabs got additional newline on Terminal change. Fixed.
STR91x Utility
- Parsing of some commands did not work correctly. Fixed.
Version V4.94j (2014-12-10)
J-Flash
- Windows: "Secure chip" was not greyed out on targets which do not support this option. Fixed.
- Windows: PCode was also tried to be downloaded to Flasher, even in case "Save config file as.." (to store the config file on the PC) was selected. Fixed.
Version V4.94i (2014-12-08)
DLL
- Under special circumstances, flash programming for Freescale MKW01Z128 devices did not work properly. Fixed.
Firmware
- J-Link LITE RX: Logic for RX was removed by accident in V4.91b built. Fixed.
Version V4.94h (2014-11-28)
DLL
- On multi-core Cortex-A/R devices, J-Link accidentally connected to the last core (instead of the first one) by default. Problem has been introduced in V4.94a. Fixed.
Firmware
- J-Link BASE / PLUS V9: Virtual COM port did not work properly (sometimes characters got lost / were sent twice). Fixed.
- J-Link BASE V8: Smaller error handling related improvements.
- J-Link ULTRA+ / PRO V9: Virtual COM port did not work properly (sometimes characters got lost / were sent twice). Fixed.
- J-Link-OB-XMC4200: In case NVMSLEEP bit was set, set/get BMI did not report an error. Fixed.
- OpenSDA: Virtual COM port did not work properly (sometimes characters got lost / were sent twice). Fixed.
- SAM3U-OB on NordicSemi nRF51-DK: MSD drag & drop programming did not work properly under Mac OS X 10.10 (Yosemite). Fixed.
- SAM3U-OB: Virtual COM port did not work properly (sometimes characters got lost / were sent twice). Fixed.
J-Link Package
- Added J-Link script file for Broadcom BCM53014.
Version V4.94g (2014-11-21)
DLL
- When programming config bits on PIC32 devices, a buffer overflow could occur. Fixed.
STM32 Utility
- Incorrect reset values to disable read-protection have been programmed for STM32F302/303 devices. Fixed.
Version V4.94f (2014-11-18)
DLL
- JLINK_SWO_EnableTarget and JLINK_SWO_EnableTarget did not return an error value. Fixed.
- JLINK_SWO_Read did not set NumBytes to 0 on error. Fixed.
GDB Server
- Getting status of running thread command did not respond correctly. Fixed.
Version V4.94c (2014-10-31)
DLL
- Added ETB support for Cortex-A9
- Added flash programming support for ABOV AC33Mxxx devices.
- Added flash programming support for ST STM32F303xE (512KB flash) devices.
- Added trace cache
- Connect/Reset for new silicon revision of CC2650 (Rev 1.2) failed under special circumstances. Fixed.
- IAR EWARM displayed wrong CYCLECOUNT after reset. Fixed.
- STM32F2 / F4 devices: If PLL was configured for a very high speed that is out of spec., device could not be erased anymore. Fixed.
- When writing large blocks into flash on C8051F93xx devices, J-Link USB communication could break down. Fixed.
Firmware
- Flasher: Programming Kinetis KMxx devices could fail under special circumstances in stand-alone-mode. Fixed.
- J-Link PRO V4: J-Link measured 0V target voltage, causing debug sessions to not be started, even though target voltage was present. Introduced in V4.92. Fixed.
- J-Link PRO V4: When using VCOM functionality, some characters sent by the target could get lost. Fixed.
- J-Link ULTRA+ V4: J-Link measured 0V target voltage, causing debug sessions to not be started, even though target voltage was present. Introduced in V4.92. Fixed.
- J-Link ULTRA+ V4: When using VCOM functionality, some characters sent by the target could get lost. Fixed.
GDB Server
- Selecting USB as host interface did not work when not specifying a serial number. Fixed.
J-Flash
- Added flash programming support for ABOV AC33Mxxx devices.
- Added flash programming support for ST STM32F303xE (512KB flash) devices.
- Changed default target interface speeds to 1000 kHz.
- Some J-Flash projects configured with older versions for NordicSemi nRF51 devices, were not opened correctly. Fixed.
- STM32F2 / F4 devices: If PLL was configured for a very high speed that is out of spec., device could not be erased anymore. Fixed.
- When selecting Freescale MPC5602D (PowerPC), the J-Link DLL complained that this is an unknown device. Fixed.
Version V4.92 (2014-09-30)
Commander
- Commander did not behave correctly, if command strings longer than 128 bytes where passed. Fixed.
DLL
- Added "exec SetRTTSearchRanges" to specify memory ranges where an RTT Control Block can be located.
- Added flash programming support for Analog Device ADSP-CM409F series.
- Added flash programming support for STM32L1xxxx-A devices.
- Added support for Renesas RX110 series CPUs
- Cortex-A/R: CPU was temporarily halted on memory accesses but not restarted automatically/correctly. Fixed.
- DLL reported wrong sector size for Spansion MB9AF311K and MB9AF312K devices. Fixed.
- DLL reported wrong sector size for Spansion MB9AF144x, MB9AF344x, MB9AFA44x, MB9AF124x and MB9AF324x devices. Fixed.
- Improved identification of RTT Control Block detection in J-Link.
- RTT did not work correctly if more than 1 MB data was transferred. (Old data was read again). Fixed.
- Some device names used by CodeWarrior were not accepted by the J-Link DLL causing the message box "The selected device is unknown to this version of the J-Link software..." to be popped up. Fixed.
- Some new Cortex-M devices were not detected properly when connecting via SWD, due to an "incorrect" AHB-AP ID check. Fixed.
- Support for Cortex-M7 added.
- Under special circumstances, flash programming for RX63x targets failed. Fixed.
Firmware
- (V8): J-Link could hang after PC left sleep / hibernate mode. Fixed.
- Flasher ARM V3 / V4: Secure chip option for some STM32L100 series devices did not work correctly and caused hanging of target application after securing. Fixed.
- Flasher Portable: Secure chip option for some STM32L100 series devices did not work correctly and caused hanging of target application after securing. Fixed.
- J-Link PRO V4: VCOM functionality added.
- J-Link ULTRA+ V4: VCOM functionality added.
J-Flash
- Added flash programming support for Analog Device ADSP-CM409F series.
- Added flash programming support for Analog Device ATSAM4C32x series.
- Added flash programming support for STM32L1xxxx-A devices.
- Added support for Renesas RX110 series CPUs
- DLL reported wrong sector size for Spansion MB9AF311K and MB9AF312K devices. Fixed.
- For some devices, "Secure chip" option of J-Flash accidentally triggered a DLL flash download. Fixed.
- ID of RX111 series devices was incorrect. Fixed.
- Secure chip option for some STM32L100 series devices did not work correctly and caused immediate crash of target application after securing. Fixed.
Remote Server
- Some J-Link commands were not handled correctly. Fixed.
Version V4.90e (2014-09-08)
DLL
- Device name "KM34Z128AM5" used by Freescale CodeWarrior, was not accepted. Fixed.
- Device names "KM14Z128AM5", "KM14Z64AM5", "KM33Z128AM5", "KM33Z64AM5" and "KM34Z128AM5" used by Freescale CodeWarrior, were not accepted. Fixed.
- RTT Output via channel 1 did not work. Fixed.
DLL Updater
- Kinetis Design Studio V1.1.1 was not detected properly. Fixed.
J-Scope
- Under some circumstances J-Scope crashed while parsing elf-files. Fixed.
RTT Logger
- Initially added.
STR91x Utility
- For new J-Link firmwares, connection could fail. Fixed.
Version V4.90c (2014-08-29)
Commander
- Added "resetconf" command for resetting config area of J-Link.
Configurator
- Added reset config area context menu entry for resetting config area of J-Link.
DLL
- Added "Do not show this dialog again" checkbox for flash breakpoints evaluation dialog.
- Added DLL Server commands for HSS.
- Added flash programming support for Freescale KV40, KV43, KV44, KV45 and KV46 devices. (Cortex-M4)
- Added flash programming support for NXP LPC11E66 series.
- Added flash programming support for ST STM32F303x6, STM32F303x8, STM32F411xx and STM32L06xxx devices.
- Added flash programming support of the "Information Block - Lock Bits" for Silicon Labs EFM32 series devices.
- Added WrEmuMaxNumBytesAtOnce and RdEmuMaxNumBytesAtOnce commands to settings file. These commands allow to limit the max. block size for memory accesses performed by J-Link.
- Flash programming of SiLabs SiM3C and SiM3U devices failed. Fixed.
- Under special circumstances, reading back the internal SPI flash of the Marvell 88MC200 could fail, in cases where the CPU was running at high speeds. Fixed.
Firmware
- Flasher: Stand-alone-mode for devices with small RAM area could fail ( < 2 KB). Fixed.
J-Flash
- Added flash programming support for Freescale KV40, KV43, KV44, KV45 and KV46 devices. (Cortex-M4)
- Added flash programming support for NXP LPC11E66 series.
- Added flash programming support for ST STM32F303x6, STM32F303x8, STM32F411xx and STM32L06xxx devices.
- Added flash programming support of the "Information Block - Lock Bits" for Silicon Labs EFM32 series devices.
- Flash programming of SiLabs SiM3C and SiM3U devices failed. Fixed.
- For devices where "secure chip" is not supported, the option is automatically "greyed". Improvements.
- Sample project R5F56108_IntFlash_16bit_CFIFlash.jflash added. Single flash bank project which allows programming of an external CFI NOR flash connected to an RX610.
- Sample project RX610_16bit_CFIFlash.jflash added. Dual flash bank project which allows programming of the internal flash as well as of an external CFI NOR flash connected to an RX610.
- Under special circumstances, reading back the internal SPI flash of the Marvell 88MC200 could fail, in cases where the CPU was running at high speeds. Fixed.
RTT Client
- Connection lost recovery improved.
- Sending user input to the target added.
Version V4.90b (2014-08-14)
GDB Server
- Under special circumstances, Atollic TrueVERIFIER could fail with latest version, due to incorrect response to a specific GDB packet. Fixed.
J-Link Package
- Linux: New PIDs added to udev rules file.
- Linux: udev rules file was incorrect in deb package and tgz archives. Fixed.
J-Scope
- Under special circumstances, sampling could not be restarted. Fixed
Version V4.90a (2014-08-08)
DLL
- For some self-terminating threads, timeouts exceeded, even in case thread self-terminated successfully, causing unnecessary delays on DLL close. Fixed.
- Improved connect to STM32L0 devices which are in lower-power-mode.
- Linux: Added new product IDs to 99-jlink.rules file.
- Reset on Mars Board (i.MX6, Cortex-A9 based) did not work properly. Fixed.
- Under special circumstances, CPU clock frequency has been calculated incorrectly for Freescale Kinetis devices. Fixed.
- x64: RTT did not work properly, since pointer sizes were handled incorrectly at some points
J-Flash
- Depending on the system window styles, Log window and Project Window positions looked odd. Fixed.
- Under special circumstances, a stack overflow could occur when showing the available command line options. Fixed.
- When hitting "ESC" or "X" in the startup dialog, J-Flash was closed. Changed. Now only the dialog is closed and J-Flash creates a new project.
J-Link Package
- RTT Telnet client added. Automatically reconnects to DLL in case debug session was closed and restarted again.
J-Scope
- Under special circumstances, division by zero exception could occur. Fixed.
Version V4.90 (2014-07-28)
DLL
- Added flash programming support for Atmel ATSAM4CP16C, ATSAMD09C13, ATSAMD10 and ATSAMD11 series.
- Connect on STM32F072/STM32F04 devices failed under special circumstances. Fixed.
- Flash programming for STM32L0 devices did not work properly. Fixed.
- Incorrect FLASH size has been reported for some TI TM4C devices. Fixed.
- Under special circumstances, flash programming (erase) did not work properly on Analog Devices ADUCM320 devices. Fixed.
Firmware
- Flasher: Under special circumstances, stand-alone mode could report an error on Cortex-M devices (Error: Verification of RAMCode failed). Fixed.
- When PC entered/left sleep mode while J-Link was in idle (not in use), under special circumstances, J-Link communication was out of sync and J-Link needed to be power-cycled. Fixed. Affected models: J-Link BASE/EDU/PLUS V9, J-Link ULTRA+ V4, J-Link PRO V4
J-Flash
- Added flash programming support for Atmel ATSAM4CP16C, ATSAMD09C13, ATSAMD10 and ATSAMD11 series.
- Connect on STM32F072/STM32F04 devices failed under special circumstances. Fixed.
- Flash programming for STM32L0 devices did not work properly. Fixed.
- Flasher: Under special circumstances, data file was not correctly downloaded to Flasher. Fixed.
- Incorrect FLASH size has been reported for some TI TM4C devices. Fixed.
- Incorrect FLASH size has been reported for STM32F042xx series devices. Fixed.
- Under special circumstances, flash programming (erase) did not work properly on Analog Devices ADUCM320 devices. Fixed.
- When saving/downloading *.DAT files which do not fit into flash area, J-Flash crashed. Fixed.
Version V4.88b (2014-07-21)
Firmware
- J-Link V9 (also PLUS, EDU based on this HW version): When having "power target via pin 19" activated, firmware update from V4.88 / V4.88a caused problems. Fixed.
Version V4.88a (2014-07-17)
Commander
- Improved error handling for "loadbin" and "loadfile" commands.
- Under special circumstances "flist" command could cause a buffer overflow. Fixed.
DLL
- Connecting to XMC4xxx devices with J-Link LITE + recent DLLs could fail. Fixed.
- HSS: Under special circumstances, buffer overflow could occur. Fixed.
- Reset for Cortex-M4 core of Vybrid device did not work properly. Fixed.
- Under special circumstances, connecting to TI AM335x devices failed since ICEPick did not respond correctly. Improved.
Firmware
- Flasher PPC: Firmware with support Nexus-1 PPC devices did not make it into V4.88. Fixed.
J-Flash
- Added example project for ST SPC560P40 (PowerPC).
- Improved example project for ST SPC560P50 (PowerPC).
Version V4.88 (2014-07-15)
DLL
- Added flash programming support for Nordic Semi nRF51422_xxAC and nRF51822_xxAC devices.
- Added flash programming support for ST STM32L0x1, STM32L0x2 and STM32L0x3 devices. (Cortex-M0)
- Added flash programming support for TMPM343xxxxx devices. (Cortex-M3)
- Added flash programming support for TMPM375FSDMG devices. (Cortex-M3)
- Added flash programming support for TMPM461F10xx, TMPM461F15xx, TMPM462F10xx and TMPM462F15xx devices. (Cortex-M4)
- Added Microchip PIC32MX170 and MX270 series devices.
- Added support for PIC32MZ
- Flash programming for Freescale MK24FN256xxx12 series devices did not work properly. Fixed.
- Mac OS X: For J-Links which support VCOM, Mac CDC drivers needed to be disabled in order to use J-Link functionality. Fixed.
- Under special circumstances, simple trace (STRACE) did not flush the target ETM FIFO properly. Fixed.
Firmware
- Flasher ARM V3 / V4: Programming of the option bytes of STM32L1 devices did not work in stand-alone-mode. Fixed.
- Flasher PPC: Added support for PowerPC devices with Nexus-1 debug interface.
- Flasher: PPC: Added support for SPC560D30, SPC560D40, SPC560P34, SPC560P40
- J-Link ULTRA+/PRO: RX63x: Dual pin implementation of FINE interface did not work correctly. Fixed.
- J-Link V9: Download speed improved (affects all CPU cores).
- J-Link: PIC32: HI & LO registers where not saved/restored correctly. Fixed.
- J-Link: PIC32: Under special circumstances, reading the CPU registers could fail and debug communication was out-of-sync afterwards. Fixed.
- J-Link: Under special circumstances, flash programming could fail if watchdog was enabled. Fixed.
J-Flash
- Added flash programming support for Nordic Semi nRF51422_xxAC and nRF51822_xxAC devices.
- Added flash programming support for ST STM32L0x1, STM32L0x2 and STM32L0x3 devices. (Cortex-M0)
- Added flash programming support for TMPM343xxxxx devices. (Cortex-M3)
- Added flash programming support for TMPM375FSDMG devices. (Cortex-M3)
- Added flash programming support for TMPM461F10xx, TMPM461F15xx, TMPM462F10xx and TMPM462F15xx devices. (Cortex-M4)
- Added Freescale MK24FN256xxx12
- Improved PLL init of LPC29xx sample projects.
Version V4.86b (2014-06-27)
DLL
- Under special circumstances, simple trace (STRACE) did not flush the target ETM FIFO properly. Fixed.
- Unsecure of STM32L1 devices did not work properly. Wrong reset values have been programmed to option bytes. Fixed.
Firmware
- J-Link ULTRA+/PRO: RX63x: Dual pin implementation of FINE interface did not work correctly. Fixed.
J-Flash
- Unsecure of STM32L1 devices did not work properly. Wrong reset values have been programmed to option bytes. Fixed.
Version V4.86a (2014-06-11)
GDB Server
- Thread support did not work with Eclipse IDEs. Fixed.
Version V4.86 (2014-06-06)
Commander
- "macaddr" command did not show last byte of MAC address correctly. Fixed.
- If uppercase 'X' was used for hexadecimal encoded addresses / data in commands, value was not parsed correctly. Fixed.
DLL
- Added flash programming support for Atmel SAMG55 devices.
- Added flash programming support for Atmel SAMG55 devices.
- Added flash programming support for Freescale MKL13, MKL23 and MKL33 devices.
- Added flash programming support for MAXIM MAX32550 devices.
- Added flash programming support for NXP LPC11E67, LPC11E68, LPC11U67 and LPC11U68 devices.
- Added flash programming support for PSoC4A-BLE devices. (Cortex-M0)
- Added flash programming support for Silicon Labs EM358x devices.
- Added flash programming support for ST STA8088 (SAL version) + external 2MB flash devices. (ARM946E-S)
- Added flash programming support for ST STA8088 external SQI flash. (ARM946E-S)
- Added flash programming support for ST STM32F078CB, STM32F078RB and STM32F078VB devices.
- Added flash programming support for ST STM32L162ZE devices.
- Added support for Cortex-A12
- Added support for Cortex-A15
- Added support for Cortex-A17
- Added support for Cortex-A7
- Added support for TI OMAP5432 (Cortex-A15)
- Added workaround to be able to use unlimited flash breakpoints also in Mentor Sourcery CodeBench. See UM08001, chapter "Flash Download" for details.
- Atmel AT91SAM/A3 flash programming: Watchdog was not handled correctly during flash programming. Fixed.
- Atmel ATSAMA5D36 was not recognized as valid device name. Fixed.
- Atmel SAMD20: If watchdog reset occurred during debug session, device connection was lost and debug session was ended. Improved. J-Link recovers target connection state.
- Broadcom BCM56151 was not detected properly (did not behave CoreSight compliant). Fixed.
- Connect under reset did not work properly for STM32L series devices. Fixed.
- Cortex-A/R: In case system reset issued via debugger also reset the debug logic of the device, connection to the core was lost. Fixed.
- Device selection dialog showed "Cortex-R4" as core for Cortex-R5 devices. Fixed.
- ETB reading speed improved by up to 900% (depends on target interface speed and model) for current J-Link models.
- Flash download into QSPI flash on Vybrid devices did not work correctly (Verification errors appeared). Fixed.
- High-Speed sampling (HSS) added.
- ICEPick was not setup correctly if a TI AM37xx series device was selected. Fixed.
- ICEPick was not setup correctly if a TI OMAP4430 series device was selected. Fixed.
- If device "Unspecified" was selected after the CPU has already been identified by the DLL, an internal error could occur. Fixed.
- Incorrect flash size has been reported for Silicon Labs EM351 and EM357 devices. Corrected.
- Incorrect RAM size has been reported for some ST STM32L100 series devices. Fixed.
- Linux / MAC: If J-Link connection was opened / closed multiple times without unloading the shared library explicitly between the connections, subsequent connections after the first one could fail. Fixed.
- Linux/Mac: Energy Micro J-Link-OB: Under special circumstances, communication timeouts could occur. Fixed.
- Linux: Under special circumstances J-Link applications crashed/hang when using multiple instances. Fixed.
- Linux: Under special circumstances when using older kernel versions, USB communication could timed out. Fixed.
- LPC17xx: Flash programming improved.
- On some legacy OKI devices, when downloading to address 0x0, flash download was not triggered correctly. Fixed. Affected devices: ML67Q4002, ML67Q4003, ML67Q5002, ML67Q5003
- PIC32: Setting / clearing data breakpoints without manually halting the CPU did not work correctly. Fixed.
- QSPI flash programming support for Vybrid Cortex-A5 devices added.
- QSPI parallel mode flash programming support for Vybrid Cortex-A5 devices added.
- TI CC2538: DLL now offers to perform an unlock of the actual CC2538 device in case initial connect failed.
- TI CC2538: When using the J-Link flashloader in IDEs or programming flash via J-Link Commander, by accident an deprecated flash algorithm was used which resulted in slower flash programming. Fixed. Programming speed has been improved by 25%.
- Under special circumstances under Mac OSX segfault 11 could happen in case J-Link was unplugged before debug session was closed properly. Fixed.
- Under special circumstances, "Auto speed detection" for legacy ARM7/9 devices did not check adaptive speed for S-cores (worked in older DLL versions). Fixed.
- Under special circumstances, Analog Devices CM40F (Cortex-M4) series devices do not respond correctly via JTAG (SWD works fine). Automatic recovery sequence for such cases added.
- Under special circumstances, reset of main core (M4) on LPC43xx devices could fail. Fixed.
- Under special circumstances, STM32F051 devices where halted by accident after connect, even if not necessary. Fixed.
DLL Updater
- Under special circumstances, parts of the config area of specific J-Link models could be overwritten by accident (Could be restored/fixed via J-Link Commander). Introduced in V4.82. Fixed.
Firmware
- Flasher ARM V3 / V4: If serial number list file or patch data list file feature was used, serial number index was incremented by accident even in case programming failed. Fixed.
- Flasher ARM V3: Under special circumstances, IP communication could lock-up. Fixed.
- Flasher PPC: If serial number list file or patch data list file feature was used, serial number index was incremented by accident even in case programming failed. Fixed.
- Flasher RX: If serial number list file or patch data list file feature was used, serial number index was incremented by accident even in case programming failed. Fixed.
- Flasher: STM32L: Auto-unsecure did not reset all option bytes to their default values, correctly. Fixed.
- Flasher: STM32L: Under special circumstances, EEPROM was not erased correctly. Fixed.
- J-Link PRO: If connection via IP was ungracefully closed (Host process terminated in an unexpected way), J-Link did not free all memory allocated by this connection and so memory leaks could occur. Fixed.
- J-Link V9: VCOM functionality: Sometimes single bytes on Tx data (to target) were lost. Fixed.
- PRO/ULTRA V4: Sampling frequency for HSS improved.
GDB Server
- "jump" command in GDB was not working correctly, since GDB Server overstepped breakpoint automatically on "continue" command. Fixed.
- Added GDB replies to simulate thread support.
- Command line options -nohalt added to prevent stopping target on connect. Counter-part: -halt.
- Under special circumstances J-Link applications crashed/hang when using multiple instances. Fixed.
- When selecting a CirrusLogic EP93xx device and not configuring a RAM area for FPU register access, the error message "Error: RAM needed for writing FPU registers. No RAM area configured." showed up, even in case FPU registers were not accessed. Fixed.
J-Flash
- "Show CFI info" option was not greyed out if no CFI flash was selected in J-Flash. Fixed.
- Added flash programming support for Freescale MKL13, MKL23 and MKL33 devices.
- Added flash programming support for MAXIM MAX32550 devices.
- Added flash programming support for NXP LPC11E67, LPC11E68, LPC11U67 and LPC11U68 devices.
- Added flash programming support for PSoC4A-BLE devices. (Cortex-M0)
- Added flash programming support for Silicon Labs EM358x devices.
- Added flash programming support for ST STA8088 (SAL version) + external 2MB flash devices. (ARM946E-S)
- Added flash programming support for ST STA8088 external SQI flash. (ARM946E-S)
- Added flash programming support for ST STM32F078CB, STM32F078RB and STM32F078VB devices.
- Added flash programming support for ST STM32L162ZE devices.
- Added support for merging data files with overlapping areas.
- Atmel AT91SAM/A3 flash programming: Watchdog was not handled correctly during flash programming. Fixed.
- Changed default core ID mask for Cortex-M/A/R devices.
- Changed default value of CPU clock speed in CPU settings tab from "0 Hz" to "Auto detection".
- Changed default value of Target "Enable target power" when creating new projects from "enabled" to "disabled".
- If "Cancel" was clicked in device selection dialog, previously selected device configuration was not preserved and lost. Fixed.
- Incorrect flash size has been reported for Silicon Labs EM351 and EM357 devices. Corrected.
- Incorrect RAM size has been reported for some ST STM32L100 series devices. Fixed.
- QSPI flash programming support for Vybrid Cortex-A5 devices added.
- QSPI parallel mode flash programming support for Vybrid Cortex-A5 devices added.
- Renesas RX: If CPU is protected via IDCode, IDCode is now extracted from programming data, so manually entering it is no longer necessary.
- So far, "Enable target power" option was only considered when auto programming has been performed. Now, it is always performed when acivated in project settings.
- STM32L: Auto-unsecure did not reset all option bytes to their default values, correctly. Fixed.
- STM32L: Under special circumstances, EEPROM was not erased correctly. Fixed.
Remote Server
- When used with J-Link V6 in combination with Cortex-M devices via SWD interface, communication broke down. Fixed.
STM32 Utility
- Added command line option "-speed <SpeedkHz>" for configuring target interface speed to be used by J-Link.
- STM32F42xx/43xx series devices: Not all option bytes were reset correctly. Fixed.
- STM32L1xx series devices were not auto-detected correctly. Fixed.
SWO Viewer
- Added option to stay on top.
SWO Viewer CL
- Output was buffered when redirected to file or stream which caused output not to be written to file until newlines were received or buffer was full. Fixed.
Version V4.84e (2014-04-28)
DLL
- Fixed bug when using flash breakpoints. Introduced in V4.84d.
Version V4.84d (2014-04-25)
Commander
- If uppercase 'X' was used for hexadecimal encoded addresses / data in commands, value was not parsed correctly. Fixed.
DLL
- Atmel ATSAMA5D36 was not recognized as valid device name. Fixed.
- If device "Unspecified" was selected after the CPU has already been identified by the DLL, an internal error could occur. Fixed.
- Linux / MAC: If J-Link connection was opened / closed multiple times without unloading the shared library explicitly between the connections, subsequent connections after the first one could fail. Fixed.
Firmware
- Flasher ARM V3 / V4: If serial number list file or patch data list file feature was used, serial number index was incremented by accident even in case programming failed. Fixed.
- Flasher PPC: If serial number list file or patch data list file feature was used, serial number index was incremented by accident even in case programming failed. Fixed.
- Flasher RX: If serial number list file or patch data list file feature was used, serial number index was incremented by accident even in case programming failed. Fixed.
- Flasher: STM32L: Auto-unsecure did not reset all option bytes to their default values, correctly. Fixed.
- Flasher: STM32L: Under special circumstances, EEPROM was not erased correctly. Fixed.
J-Flash
- STM32L: Auto-unsecure did not reset all option bytes to their default values, correctly. Fixed.
- STM32L: Under special circumstances, EEPROM was not erased correctly. Fixed.
Version V4.84c (2014-04-16)
Commander
- "macaddr" command did not show last byte of MAC address correctly. Fixed.
DLL
- High-Speed sampling (HSS) added.
Version V4.84b (2014-04-15)
DLL
- Added flash programming support for ST STM32F078CB, STM32F078RB and STM32F078VB devices.
- PIC32: Setting / clearing data breakpoints without manually halting the CPU did not work correctly. Fixed.
- Under special circumstances under Mac OSX segfault 11 could happen in case J-Link was unplugged before debug session was closed properly. Fixed.
- Under special circumstances, "Auto speed detection" for legacy ARM7/9 devices did not check adaptive speed for S-cores (worked in older DLL versions). Fixed.
- Under special circumstances, STM32F051 devices where halted by accident after connect, even if not necessary. Fixed.
DLL Updater
- Under special circumstances, parts of the config area of specific J-Link models could be overwritten by accident (Could be restored/fixed via J-Link Commander). Introduced in V4.82. Fixed.
Firmware
- Flasher ARM V3: Under special circumstances, IP communication could lock-up. Fixed.
J-Flash
- "Show CFI info" option was not greyed out if no CFI flash was selected in J-Flash. Fixed.
- Added flash programming support for ST STM32F078CB, STM32F078RB and STM32F078VB devices.
- So far, "Enable target power" option was only considered when auto programming has been performed. Now, it is always performed when acivated in project settings.
STM32 Utility
- STM32F42xx/43xx series devices: Not all option bytes were reset correctly. Fixed.
Version V4.84a (2014-04-04)
DLL
- Connect under reset did not work properly for STM32L series devices. Fixed.
- Linux/Mac: Energy Micro J-Link-OB: Under special circumstances, communication timeouts could occur. Fixed.
- Linux: Under special circumstances when using older kernel versions, USB communication could timed out. Fixed.
GDB Server
- "jump" command in GDB was not working correctly, since GDB Server overstepped breakpoint automatically on "continue" command. Fixed.
J-Flash
- If "Cancel" was clicked in device selection dialog, previously selected device configuration was not preserved and lost. Fixed.
Remote Server
- When used with J-Link V6 in combination with Cortex-M devices via SWD interface, communication broke down. Fixed.
SWO Viewer
- Added option to stay on top.
SWO Viewer CL
- Output was buffered when redirected to file or stream which caused output not to be written to file until newlines were received or buffer was full. Fixed.
Version V4.84 (2014-03-28)
Commander
- "loadbin" command did not work properly under Linux & Mac. Fixed.
DLL
- Added flash programming support for TI TM4C1294KCPDT, TM4C1297NCZAD, TM4C1299KCZAD, TM4C1299NCZAD, TM4C129EKCPDT, TM4C129LNCZAD, TM4C129XKCZAD
- Added full J-Link support for Actel (now Microsemi) A2F060M3x, A2F200M3x and A2F500M3x devices. (Cortex-M3)
- Added full J-Link support for Freescale KW01 devices. (Cortex-M0)
- Added full J-Link support for NXP LPC15xx devices. (Cortex-M3)
- Added full J-Link support for Spansion MB9AF120/420 devices. (Cortex-M3)
- Added full J-Link support for Toshiba TMPM351 devices. (Cortex-M3)
- PIC32: Flash programming did not work properly if data breakpoint was set. Fixed.
- PIC32: Single stepping did work properly if CPU was halted due to data breakpoint. Fixed.
- Renesas RZ: When programming QSPI flash, original SPI clock settings were not restored correctly after programming. Fixed.
- Reported wrong sector size for TI TM4C123 devices. Fixed.
- Under special circumstances, flash programming did not work properly for TI TM4C devices if watchdog was enabled. Fixed.
- Under special circumstances, when using the unlimited flash breakpoints feature, on some CPUs the flash wait states / flash cache settings were not restored correctly. Fixed.
- When selecting Qunitic QN9020 devices, the message box "The selected device is unknown to this version of the J-Link software..." popped up. Fixed.
Firmware
- Flasher: PPC: Device was not halted immediately after reset. Fixed.
- Flasher: PPC: Flash programming could fail if target watchdog was enabled, since flash algorithm did not handle this case properly. Fixed.
GDB Server
- Handling for semihosting system call angel_SWIreason_ReportException (0x18) added.
J-Flash
- Added flash programming support for TI TM4C1294KCPDT, TM4C1297NCZAD, TM4C1299KCZAD, TM4C1299NCZAD, TM4C129EKCPDT, TM4C129LNCZAD, TM4C129XKCZAD
- Added full J-Link support for Actel (now Microsemi) A2F060M3x, A2F200M3x and A2F500M3x devices. (Cortex-M3)
- Added full J-Link support for Freescale KW01 devices. (Cortex-M0)
- Added full J-Link support for NXP LPC15xx devices. (Cortex-M3)
- Added full J-Link support for Spansion MB9AF120/420 devices. (Cortex-M3)
- Added full J-Link support for Toshiba TMPM351 devices. (Cortex-M3)
- Added sample projects for Actel (now Microsemi) A2F060M3x, A2F200M3x and A2F500M3x devices. (Cortex-M3)
- Added sample projects for NXP LPC15xx devices. (Cortex-M3)
- Reported wrong sector size for TI TM4C123 devices. Fixed.
- Sample projects for Freescale Kinetis V10 series devices were incorrectly configured for Cortex-M3 devices (V10 series is Cortex-M0+). Fixed.
- Under special circumstances, flash programming did not work properly for TI TM4C devices if watchdog was enabled. Fixed.
- Under special circumstances, when programming Freescale MAC71xxx series devices, J-Flash could crash. Fixed.
Remote Server
- In non-tunneling mode, connection to J-Link Remote Server could break down with message "IP communication timeout". Bug introduced with V4.80c. Fixed.
Version V4.82 (2014-03-10)
Commander
- Changed visualization of printed CPU registers for Cortex-M devices.
- Extended command line option -speed so that "adaptive" and "auto" are supported.
- loadbin command extended. Now loading of hex, mot, srec etc. files is also supported.
DLL
- Adapted new naming scheme of Nordic Semi devices.
- Added Atmel ATSAMD21E18/ATSAMD21E18A.
- Added flash programming support for Infineon XMC1100-0008.
- Added flash programming support for Spansion MB9BF128S/T, MB9BF129S/T, MB9BF328S/T, MB9BF329S/T, MB9BF428S/T, MB9BF429S/T, MB9BF528S/T, MB9BF529S/T
- Added full J-Link support (incl. flash programming) for Atmel ATSAMD20E1F and ATSAMD20E18 devices.
- Added full J-Link support for Freescale KE04 series.
- Added full J-Link support for Freescale KE06 series.
- Added full J-Link support for Freescale Kinetis MK22FN256xxx12, MK22FN512xxx12 series devices (Cortex-M4).
- Added full J-Link support for Freescale Kinetis V31-series devices (Cortex-M4).
- Added full J-Link support for Freescale KL03 series.
- Added full J-Link support for Freescale W-series devices. (Cortex-M4)
- Added full J-Link support for Spansion FM0+ series devices. (Cortex-M0+)
- Added full J-Link support for ST LIS331EB (Cortex-M0).
- Added full J-Link support for ST STM32F031 series devices. (Cortex-M0)
- Added full J-Link support for ST STM32F042 series devices. (Cortex-M0)
- Added full J-Link support for ST STM32F071 series devices. (Cortex-M0)
- Added full J-Link support for ST STM32F072 series devices. (Cortex-M0)
- Added full J-Link support for ST STM32F401 series devices. (Cortex-M4)
- Added full J-Link support for ST STM32L151xE, STM32L152xE series devices.
- Added full J-Link support for Toshiba TMPM358 device.
- Added full J-Link support for Toshiba TMPM358FDTFG. (Cortex-M3)
- Added PIC32 support.
- Added support for programming customer information block of Ember/SiLabs EM351/357 devices.
- AM3359: Reset did not halt CPU at start of public ROM code. Fixed.
- ARM7/9 targets: Under special circumstances when single stepping a MOVS PC, LR (return from exception), instruction set simulation did not work properly. Fixed.
- Atmel SAM3U series: Under special circumstances, flash download to address 0x0 did not work properly, since memory mapping was not handled properly. Fixed.
- Atmel SAM4L: Under special circumstances, CYCCNT was not incremented on Go/Continue. Fixed.
- Cirrus Logic EP7312 was reported as ARM9 while it is an ARM7 device. Fixed.
- Cortex-M: CycleCnt was not updated on single stepping. Fixed.
- Cortex-M: Writing the CONTROL register in Freescale CodeWarrior did not work properly. Fixed.
- Cypress PSoC4: Under special circumstances CPU could get stuck when using software breakpoints in flash memory. Fixed.
- Flash programming for Microsemi SmartFusion2 series devices did not work properly. Fixed.
- Flash programming: Implemented double CRC check for flash content comparison.
- Freescale Kinetis V series devices: When inhibiting accidental secure of a device during flash programming, incorrect byte at address 0x40E was modified, instead of byte at address 0x40C. Fixed.
- If error occurred during erasing/programming the QSPI flash on Renesas RZ devices, error flags in flash status register were not reset correctly. Fixed.
- In case of programming errors, flash cache of DLL was not invalidated correctly. Fixed.
- Incorrect RAM size has been reported for some ST STM32F105 / 107 devices. Fixed.
- Infineon XMC1000 series devices device names changed. (Old names are still accepted).
- J-Link script file no longer necessary when connecting to TI AM18xx target devices. Selecting the correct device is sufficient.
- J-Link script file no longer necessary when connecting to TI OMAP-L138 target devices. Selecting the correct device is sufficient.
- PIC32: Physical addresses for internal flash were not mapped correctly during flash programming. Fixed.
- Release notes updated.
- RX: Connecting to J-Link PRO via Ethernet when using HEW / EWRX was not possible. Fixed.
- Some device names passed by IAR EWARM for ADI ADSP-CM40x series devices (Cortex-M4) were not recognized correctly. Fixed.
- Some device names passed by IAR EWARM were not handled correctly. Fixed.
- STM32L: Programming speed of EEPROM area improved.
- SWOViewer did not work properly for STM32L devices. Fixed.
- Under special circumstances flash secure/unsecure for ST STM32F3xx devices did not work properly. Fixed.
- Under special circumstances on devices with multiple RAM areas, PUSH/POP instruction was not simulated properly when using instruction set simulation. Fixed.
- Under special circumstances, an internal error could occur, saying "Invalid memory map, can not un-alias region 0x00000000 - 0xFFFFFFFF". Fixed.
- Under special circumstances, debugging on ARM7/9 S-cores (e.g. ARM926EJ-S) and older IAR EWARM versions could fail. Problem introduced in V4.80 of the J-Link DLL. Fixed.
- Under special circumstances, flash programming on Fujitsu/Spansion FM0+ devices did not work properly. Fixed.
- Under special circumstances, if using old IAR EWARM versions, the error message "DLL function JLINKARM_SetFlashArea(...)" not found, could appear. Fixed.
- Under special circumstances, on some devices when writing to aliased memory areas (e.g. cached-flash range vs. non-cached range) and immediately reading from them, incorrect memory contents were displayed. Fixed.
- Under special circumstances, speed set by debugger was not configured correctly on J-Link which could cause problems on soem targets. Introduced in V4.80a. Fixed.
- Under special circumstances, the error message "MEM_MAP.c, _LogRange2PhysRange()..." could appear. Fixed.
- Under special circumstances, unlimited flash breakpoints feature did not work properly on Fujitsu/Spansion FM0+ series devices. Fixed.
- Under very special circumstances when reading memory areas where software breakpoints were set and flash cache was disabled, incorrect memory contents could be shown. Fixed.
- When selecting a device via "device ?" in J-Link Commander, it was not possible to switch device selection to another device, without restarting J-Link Commander. Fixed.
DLL Updater
- Added ARM DS-5 to DLL Updater.
- Added Freescale CodeWarrior.
Firmware
- Flasher ARM V4: Explicit control of pin 9 via JLINKARM_SetTCK() / JLINKARM_ClrTCK() did not work properly. Fixed.
- Flasher: PPC: Added support for ST SPC5605B, SPC5606B and SPC5607B devices.
- J-Link PRO: Under special circumstances, communication via IP broke down if J-Link and host PC are in different subnets. Fixed.
- J-Link V9: nTRST pin was not set as input of J-Link if SWD was used as target interfaced. It could cause problems if nTRST was shared with GPIO functionality on the target hardware and pin was connected to J-Link. Fixed.
- J-Link-Lite-XMC4200: Under special circumstances, JTAG/SWD communication problems could occur on some eval boards. Fixed.
- J-Link-Lite-XMC4200: Wrong target interface speed reported by firmware (actual speed was higher than reported one). Fixed.
GDB Server
- Added log output to startup.
- Command line option '-notimeout' added to allow powering up a device after starting GDB Server.
- Display target voltage in log on initial connection.
- Starting multiple GDB Server instances from different users via SSH did not work properly. Fixed.
- Under special circumstances unhandled exception could occur when closing GDB Server while target CPU was running. Fixed.
GDB Server CL
- Do not save and load (GUI related) settings anymore.
- Under some circumstances the output contained blank lines after each line. Fixed.
J-Flash
- -openprj command line option did not work properly. Fixed.
- Adapted new naming scheme of Nordic Semi devices.
- Added example project for Renesas RZ (Cortex-A9) parallel CFI NOR flash programming.
- Added example project: STM32F405OE_OptBytes.jflash
- Added flash programming support for Infineon XMC1100-0008.
- Added flash programming support for Spansion MB9BF128S/T, MB9BF129S/T, MB9BF328S/T, MB9BF329S/T, MB9BF428S/T, MB9BF429S/T, MB9BF528S/T, MB9BF529S/T
- Added full J-Link support for Freescale KE04 series.
- Added full J-Link support for Freescale KE06 series.
- Added full J-Link support for Freescale Kinetis MK22FN256xxx12, MK22FN512xxx12 series devices (Cortex-M4).
- Added full J-Link support for Freescale Kinetis V31-series devices (Cortex-M4).
- Added full J-Link support for Freescale KL03 series.
- Added full J-Link support for Freescale W-series devices. (Cortex-M4)
- Added full J-Link support for Spansion FM0+ series devices. (Cortex-M0+)
- Added full J-Link support for ST LIS331EB (Cortex-M0).
- Added full J-Link support for ST STM32F031 series devices. (Cortex-M0)
- Added full J-Link support for ST STM32F042 series devices. (Cortex-M0)
- Added full J-Link support for ST STM32F071 series devices. (Cortex-M0)
- Added full J-Link support for ST STM32F072 series devices. (Cortex-M0)
- Added full J-Link support for ST STM32F401 series devices. (Cortex-M4)
- Added full J-Link support for ST STM32L151xE, STM32L152xE series devices.
- Added full J-Link support for Toshiba TMPM358 device.
- Added full J-Link support for Toshiba TMPM358FDTFG. (Cortex-M3)
- Added new feature which allows turning off power supply via pin-19 when closing J-Flash if configured in project settings.
- Added option byte programming support for ST STM32L series.
- Added parallel NOR flash SST SST39VF1681, SST39VF1682
- Added sample project for ST STM32F4x9I 1x16 CFI NOR flash on nCS0.
- Added sample projects for Freescale Kinetis V31-series devices (Cortex-M4).
- Added sample projects for Freescale KW series.
- Added sample projects for Spansion MB9AFxxxx, MB9BFxxxx and S6E1Axxx devices.
- Added sample projects for ST STM32F072 series devices. (Cortex-M0)
- Added secure/unsecure support for ST STM32L series.
- Added support for Atmel ATSAMG51/53/54 devices.
- Added support for programming customer information block of Ember/SiLabs EM351/357 devices.
- Freescale Kinetis V series devices: When inhibiting accidental secure of a device during flash programming, incorrect byte at address 0x40E was modified, instead of byte at address 0x40C. Fixed.
- If "power target via J-Link" was enabled in production settings and "Start application" was also enabled, "start application" could fail. Fixed.
- If error occurred during erasing/programming the QSPI flash on Renesas RZ devices, error flags in flash status register were not reset correctly. Fixed.
- Incorrect RAM size has been reported for some ST STM32F105 / 107 devices. Fixed.
- Infineon XMC1000 series devices device names changed. (Old names are still accepted).
- Last data file opened with a specific project was not opened automatically on startup. Fixed.
- LPC43xx devices were listed as "Cortex-M3" instead of "Cortex-M4". Fixed.
- Open last data file did not work properly. Fixed.
- RAM base address in NordicSemi nRF51422.jflash example project was configured incorrectly. Fixed.
- STM32L: Programming speed of EEPROM area improved.
- Under special circumstances flash secure/unsecure for ST STM32F3xx devices did not work properly. Fixed.
- Under special circumstances, flash programming on Fujitsu/Spansion FM0+ devices did not work properly. Fixed.
- Under special circumstances, unlimited flash breakpoints feature did not work properly on Fujitsu/Spansion FM0+ series devices. Fixed.
J-Mem
- When reading from addresses at memory boundaries, under special circumstances memory contents could not be displayed. Fixed.
Manual
- RDI manual UM08004_JLinkRDI.pdf has been merged into J-Link manual UM08001_JLink.pdf.
- UM08001: Several corrections / improvements.
- UM08022: Flasher user manual: Added description for STM32F2 / STM32F4 option byte programming support. See device specifics section.
RDI
- Under special circumstances, an internal error could occur, saying "Invalid memory map, can not un-alias region 0x00000000 - 0xFFFFFFFF". Fixed.
STR91x Utility
- Command line option which allows configuring a specific scan-chain has been added. See manual for more detailed description.
SWO Viewer CL
- Added ability to toggle stimulus ports while SWO Viewer is running.
Version V4.80h (2014-02-28)
Commander
- Extended command line option -speed so that "adaptive" and "auto" are supported.
DLL
- Adapted new naming scheme of Nordic Semi devices.
- Cortex-M: Writing the CONTROL register in Freescale CodeWarrior did not work properly. Fixed.
- If error occurred during erasing/programming the QSPI flash on Renesas RZ devices, error flags in flash status register were not reset correctly. Fixed.
- J-Link script file no longer necessary when connecting to TI AM18xx target devices. Selecting the correct device is sufficient.
- J-Link script file no longer necessary when connecting to TI OMAP-L138 target devices. Selecting the correct device is sufficient.
- SWO did not work properly for STM32L devices. Fixed.
Firmware
- J-Link PRO: Under special circumstances, communication via IP broke down if J-Link and host PC are in different subnets. Fixed.
- J-Link ULTRA/PRO V4: POWERTRACE did not work properly in IAR EWARM. Fixed.
GDB Server
- Starting multiple GDB Server instances from different users via SSH did not work properly. Fixed.
- Under special circumstances unhandled exception could occur when closing GDB Server while target CPU was running. Fixed.
J-Flash
- Adapted new naming scheme of Nordic Semi devices.
- If error occurred during erasing/programming the QSPI flash on Renesas RZ devices, error flags in flash status register were not reset correctly. Fixed.
Version V4.80g (2014-02-13)
DLL
- Added full J-Link support for Freescale Kinetis MK22FN256xxx12, MK22FN512xxx12 series devices (Cortex-M4).
- Cirrus Logic EP7312 was reported as ARM9 while it is an ARM7 device. Fixed.
- Some device names passed by EWARM were not handled correctly. Fixed.
J-Flash
- LPC43xx devices were listed as "Cortex-M3" instead of "Cortex-M4". Fixed.
Version V4.80f (2014-02-05)
DLL
- Added Atmel ATSAMD21E18/ATSAMD21E18A.
- Atmel SAM3U series: Under special circumstances, flash download to address 0x0 did not work properly, since memory mapping was not handled properly. Fixed.
- Cypress PSoC4: Under special circumstances CPU could get stuck when using software breakpoints in flash memory. Fixed.
Version V4.80e (2014-01-31)
DLL
- Added flash programming support for Freescale KE04 series.
- Added flash programming support for Freescale KE06 series.
- TI AM335x: Under special circumstances, ROM bootloader was not run properly after reset and device was not fully initialized, which could cause odd behavior of the AM335x device.
- Under special circumstances flash secure/unsecure for ST STM32F3xx devices did not work properly. Fixed.
- Under special circumstances, an internal error could occur, saying "Invalid memory map, can not un-alias region 0x00000000 - 0xFFFFFFFF". Fixed.
- Under special circumstances, on some devices when writing to aliased memory areas (e.g. cached-flash range vs. non-cached range) and immediately reading from them, incorrect memory contents were displayed. Fixed.
GDB Server CL
- Under special circumstances, semihosting did not work properly. (Introduced in V4.80d by the change, not loading GUI related settings anymore)
J-Flash
- Added flash programming support for Freescale KE04 series.
- Added flash programming support for Freescale KE06 series.
- Under special circumstances flash secure/unsecure for ST STM32F3xx devices did not work properly. Fixed.
RDI
- Under special circumstances, an internal error could occur, saying "Invalid memory map, can not un-alias region 0x00000000 - 0xFFFFFFFF". Fixed.
Version V4.80d (2014-01-29)
Commander
- Changed visualization of printed CPU registers for Cortex-M devices.
DLL
- Added flash programming support for Freescale KL03 series.
- AM3359: Reset did not halt CPU at start of public ROM code. Fixed.
- ARM7/9 targets: Under special circumstances when single stepping a MOVS PC, LR (return from exception), instruction set simulation did not work properly. Fixed.
- Atmel SAM4L: Under special circumstances, CYCCNT was not incremented on Go/Continue. Fixed.
- Cortex-M: CycleCnt was not updated on single stepping. Fixed.
- Flash programming for Microsemi SmartFusion2 series devices did not work properly. Fixed.
- Some device names passed by IAR EWARM for ADI ADSP-CM40x series devices (Cortex-M4) were not recognized correctly. Fixed.
- Under very special circumstances when reading memory areas where software breakpoints were set and flash cache was disabled, incorrect memory contents could be shown. Fixed.
GDB Server
- Display target voltage in log on initial connection.
GDB Server CL
- Do not save and load (GUI related) settings anymore.
- Under some circumstances the output contained blank lines after each line. Fixed.
J-Flash
- Added flash programming support for Freescale KL03 series.
- RAM base address in NordicSemi nRF51422.jflash example project was configured incorrectly. Fixed.
Version V4.80c (2014-01-21)
Version V4.80b (2014-01-17)
DLL
- Under special circumstances, if using old IAR EWARM versions, the error message "DLL function JLINKARM_SetFlashArea(...)" not found, could appear. Fixed.
- Under special circumstances, the error message "MEM_MAP.c, _LogRange2PhysRange()..." could appear. Fixed.
J-Flash
- Added parallel NOR flash SST SST39VF1681, SST39VF1682
- Added sample project for ST STM32F4x9I 1x16 CFI NOR flash on nCS0.
- If "power target via J-Link" was enabled in production settings and "Start application" was also enabled, "start application" could fail. Fixed.
Version V4.80a (2014-01-10)
DLL
- Release notes updated.
- Under special circumstances, debugging on ARM7/9 S-cores (e.g. ARM926EJ-S) and older IAR EWARM versions could fail. Problem introduced in V4.80 of the J-Link DLL. Fixed.
Firmware
- Flasher ARM V4: Explicit control of pin 9 via JLINKARM_SetTCK() / JLINKARM_ClrTCK() did not work properly. Fixed.
- J-Link-Lite-XMC4200: Under special circumstances, JTAG/SWD communication problems could occur on some eval boards. Fixed.
- J-Link-Lite-XMC4200: Wrong target interface speed reported by firmware (actual speed was higher than reported one). Fixed.
J-Flash
- Last data file opened with a specific project was not opened automatically on startup. Fixed.
J-Mem
- When reading from addresses at memory boundaries, under special circumstances memory contents could not be displayed. Fixed.
Manual
- UM08001: J-Link manual: Several corrections / improvements.
Version V4.80 (2013-12-20)
Commander
- Shows more detailed information about I-cache and D-cache of Cortex-A/R CPUs.
DLL
- Added flash programming support for Freescale MK21FN1M0xxx12, MK21FX512xxx12, MK22FN1M0xxx12, MK22FX512xxx12 series devices.
- Added flash programming support for Renesas R5F5631F, R5F5631G, R5F5631J, R5F5631K, R5F5631M, R5F5631N, R5F5631P, R5F5631W, R5F5631Y
- Added flash programming support for Renesas R5F563NF, R5F563NG, R5F563NJ, R5F563NK, R5F563NW, R5F563NY
- Added flash programming support for Toshiba TMPM350FDTFG.
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Silicon Labs SiM3C1xx, SiM3L1xx and SiM3U1xx devices.
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Toshiba ATSAM4CMS16C (Cortex-M4).
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Toshiba TMPM36BF10FG (Cortex-M3).
- Added QSPI flash programming support for Renesas RZ devices.
- Added support for Freescale KV10 series devices.
- Added support for MicroSemi SmartFusion2 series devices. (M2S005, M2S025, M2S050, M2S080, M2S120)
- Added support for NXP LPC11U6x series CPUs.
- Atmel ATSAMD20: If target application issued a reset during the debug session (via watchdog etc.), target application did not correctly reboot while J-Link was connected. Fixed.
- Cortex-M: Instruction set simulation caused problems if debugger accidentally set PC to an odd address. Fixed.
- Debugging support for Cortex-A/R via SWD interface added. Note: Support has been added for current J-Link models only (J-Link HW version 9 and later, J-Link ULTRA+/PRO HW version 4 and later)
- DLL flash programming logic: When downloading large applications on STM32 devices to flash, via address 0x0, it could happen that flash programming failed if application size exceeded a specific value. Fixed.
- Flash programming for STM32F2xx / STM32F4xx devices could fail if device was running at <= 2.0V VCC. Fixed.
- Flash programming on nRF51422 devices could fail since non 4 KB aligned start address of nRF51422 RAM was not handled correctly. Fixed.
- Linux / MAC: When being connected to J-Link via IP and having longer idle times where no communication with J-Link was performed by the debugger, it could happen that the IP communication broke down. Fixed.
- Linux: Under special circumstances, connection to J-Link V7 probes could fail. Fixed.
- Reset for Renesas RZ device did not work correctly if boot mode 3 (boot from QSPI flash) was selected. Fixed.
- Some Atmel SAM3/SAM4 devices were reported as unknown devices when using J-Link with EWARM. Fixed.
- SWO did not work properly for Kinetis K-series devices. Fixed.
- Under special circumstances, flash programming failed on Marvell 88MC200 devices. Fixed.
- Under special circumstances, programming of Spansion S29GLxxxS NOR flash devices could fail. Fixed.
- Under special circumstances, target power loss was not detected properly during flash programming. Fixed.
- Under special circumstances, when "auto" target interface speed was selected on ARM7/9 devices, accidentally "adaptive clocking" was selected, even if not supported by the connected core. Fixed.
DLL RX
- RX630 / RX631 F-series devices where not detected properly, which could cause problems during debugging and flash programming in Renesas HEW / e2Studio and IAR EWRX.
Firmware
- Debugging support for Cortex-A/R via SWD interface added. Note: Support has been added for current J-Link models only (J-Link HW version 9 and later, J-Link ULTRA+/PRO HW version 4 and later)
- Flasher (ARM/PPC/RX): Under special circumstances, switching the baud rate did not work properly. Fixed.
- Flasher ARM V3: SetTCK/ClrTCK in J-Link Commander did not work properly. Fixed.
- Flasher ARM V4 / Flasher Portable: Under special circumstances, on recoverable NAND flash failure, Flasher did not allow further writing of the on board NAND flash (causing e.g. firmware updates to be rejected)
- Flasher Portable: Incorrect CFI information reported by some SST39 CFI NOR flash devices was not handled correctly in stand-alone mode. Fixed.
- Flasher Portable: Stand-alone programming of RX6xx devices via JTAG did not work properly. Fixed.
- J-Link ULTRA V1, J-Link PRO V1: Under special circumstances, single stepping on Cortex-A/R devices did not work properly if D-cache was enabled. Fixed.
- J-Link ULTRA+/PRO V4: Improved max. SWO speed to 100 MHz. Needs to be explicitly enabled in firmware. By default, speed is limited to 50 MHz. See UM08001 (J-Link User Guide) for more information.
- J-Link V8 / V9: When debugging on Cortex-M via SWD interface and using a very old DLL (< V4.10 from year 2009) debugging might fail due to a firmware <-> DLL incompatibility. Fixed.
- J-Link-OB-XMC4200: VCOM functionality did not work correctly when receiving data from target system. Fixed.
GDB Server
- Added command line option -SettingsFile.
- DLL flash programming logic: When downloading large applications on STM32 devices to flash, via address 0x0, it could happen that flash programming failed if application size exceeded a specific value. Fixed.
- Mac: Under special circumstances, a seg fault 11 could occur if a GDB-TCP/IP connection was closed. Fixed.
- Semihosting: SYS_FCLOSE command did not work properly. Fixed. (Usually did not cause any real problems)
- Semihosting: SYS_FLEN command did not work properly. Fixed.
- Under special circumstances, when having more than 1 GDB connection open to GDB Server gdb commands got intermixed. Fixed.
J-Flash
- Added command line option for merging data files (-merge).
- Added Cutera LH28F128BFHED-473 parallel NOR flash to the list of selectable NOR flash devices.
- Added flash programming support for Freescale MK21FN1M0xxx12, MK21FX512xxx12, MK22FN1M0xxx12, MK22FX512xxx12 series devices.
- Added flash programming support for Renesas R5F5631F, R5F5631G, R5F5631J, R5F5631K, R5F5631M, R5F5631N, R5F5631P, R5F5631W, R5F5631Y
- Added flash programming support for Renesas R5F563NF, R5F563NG, R5F563NJ, R5F563NK, R5F563NW, R5F563NY
- Added flash programming support for Toshiba TMPM350FDTFG.
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Silicon Labs SiM3C1xx, SiM3L1xx and SiM3U1xx devices.
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Toshiba ATSAM4CMS16C (Cortex-M4).
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Toshiba TMPM36BF10FG (Cortex-M3).
- Added QSPI flash programming support for Renesas RZ devices.
- Added sample projects for Freescale KV10 series devices.
- Added sample projects for MicroSemi SmartFusion2 series devices. (M2S005, M2S025, M2S050, M2S080, M2S120)
- Added sample projects for Renesas RZ devices.
- Added sample projects for Silicon Labs SiM3C1xx, SiM3L1xx and SiM3U1xx devices.
- Added support for Freescale KV10 series devices.
- Added support for MicroSemi SmartFusion2 series devices. (M2S005, M2S025, M2S050, M2S080, M2S120)
- Cortex-M4 devices accidentally were listed as Cortex-M3. Fixed.
- Energy Micro Zero Gecko Devices were listed as Cortex-M3 devices. Fixed.
- Flash programming for STM32F2xx / STM32F4xx devices could fail if device was running at <= 2.0V VCC. Fixed.
- Fujitsu/Spansion FM4 series MCUs were listed as Cortex-M3 instead of Cortex-M4. Fixed.
- If padding of programming data was necessary to achieve flash min. align requirements, data was always padded with 0xFF, even on flashes which have 0x00 as erased value, which caused verification errors. Fixed.
- Some Cortex-M4 target devices were listed as Cortex-M3. Fixed.
- Under special circumstances, "chip erase" for AT91SAM9XE devices failed. Fixed.
- Under special circumstances, flash programming failed on Marvell 88MC200 devices. Fixed.
- Under special circumstances, programming of Spansion S29GLxxxS NOR flash devices could fail. Fixed.
Manual
- UM08001: J-Link manual: Several corrections in GDB Server section.
SWO Viewer
- If no ITM stimulus port is explicitly specified to be enabled, ITM port 0 will be enabled by default.
- SWO did not work properly for Kinetis K-series devices. Fixed.
Version V4.78m (2013-12-18)
DLL
- Flash programming on nRF51422 devices could fail since non 4 KB aligned start address of nRF51422 RAM was not handled correctly. Fixed.
- Some Atmel SAM3/SAM4 devices were reported as unknown devices when using J-Link with EWARM. Fixed.
Version V4.78l (2013-12-12)
DLL
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Toshiba ATSAM4CMS16C (Cortex-M4).
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Toshiba TMPM36BF10FG (Cortex-M3).
- DLL flash programming logic: When downloading large applications on STM32 devices to flash, via address 0x0, it could happen that flash programming failed if application size exceeded a specific value. Fixed.
Firmware
- J-Link-OB-XMC4200: VCOM functionality did not work correctly when receiving data from target system. Fixed.
GDB Server
- DLL flash programming logic: When downloading large applications on STM32 devices to flash, via address 0x0, it could happen that flash programming failed if application size exceeded a specific value. Fixed.
J-Flash
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Toshiba ATSAM4CMS16C (Cortex-M4).
- Added full J-Link / Flasher support (Flash download + unlimited number of breakpoints in flash) for Toshiba TMPM36BF10FG (Cortex-M3).
- If padding of programming data was necessary to achieve flash min. align requirements, data was always padded with 0xFF, even on flashes which have 0x00 as erased value, which caused verification errors. Fixed.
- Some Cortex-M4 target devices were listed as Cortex-M3. Fixed.
Version V4.78k (2013-12-05)
DLL
- Added support for MicroSemi SmartFusion2 series devices. (M2S005, M2S025, M2S050, M2S080, M2S120)
- Linux / MAC: When being connected to J-Link via IP and having longer idle times where no communication with J-Link was performed by the debugger, it could happen that the IP communication broke down. Fixed.
Firmware
- Flasher (ARM/PPC/RX): Under special circumstances, switching the baud rate did not work properly. Fixed.
- Flasher Portable: Stand-alone programming of RX6xx devices via JTAG did not work properly. Fixed.
- J-Link ULTRA V1, J-Link PRO V1: Under special circumstances, single stepping on Cortex-A/R devices did not work properly if D-cache was enabled. Fixed.
- J-Link V8 / V9: When debugging on Cortex-M via SWD interface and using a very old DLL (< V4.10 from year 2009) debugging might fail due to a firmware <-> DLL incompatibility. Fixed.
GDB Server
- Semihosting: SYS_FCLOSE command did not work properly. Fixed. (Usually did not cause any real problems)
- Semihosting: SYS_FLEN command did not work properly. Fixed.
J-Flash
- Added sample projects for MicroSemi SmartFusion2 series devices. (M2S005, M2S025, M2S050, M2S080, M2S120)
- Added support for MicroSemi SmartFusion2 series devices. (M2S005, M2S025, M2S050, M2S080, M2S120)
- Fujitsu/Spansion FM4 series MCUs were listed as Cortex-M3 instead of Cortex-M4. Fixed.
Version V4.78h (2013-11-19)
DLL
- Added flash programming support for Renesas R5F5631F, R5F5631G, R5F5631J, R5F5631K, R5F5631M, R5F5631N, R5F5631P, R5F5631W, R5F5631Y
- Added flash programming support for Renesas R5F563NF, R5F563NG, R5F563NJ, R5F563NK, R5F563NW, R5F563NY
- Cortex-M: Instruction set simulation caused problems if debugger accidentally set PC to an odd address. Fixed.
- Flash programming for STM32F2xx / STM32F4xx devices could fail if device was running at <= 2.0V VCC. Fixed.
- Under special circumstances, programming of Spansion S29GLxxxS NOR flash devices could fail. Fixed.
Firmware
- Flasher Portable: Incorrect CFI information reported by some SST39 CFI NOR flash devices was not handled correctly in stand-alone mode. Fixed.
GDB Server
- Mac: Under special circumstances, a seg fault 11 could occur if a GDB-TCP/IP connection was closed. Fixed.
- Under special circumstances, when having more than 1 GDB connection open to GDB Server gdb commands got intermixed. Fixed.
J-Flash
- Added flash programming support for Renesas R5F5631F, R5F5631G, R5F5631J, R5F5631K, R5F5631M, R5F5631N, R5F5631P, R5F5631W, R5F5631Y
- Added flash programming support for Renesas R5F563NF, R5F563NG, R5F563NJ, R5F563NK, R5F563NW, R5F563NY
- Flash programming for STM32F2xx / STM32F4xx devices could fail if device was running at <= 2.0V VCC. Fixed.
- Under special circumstances, programming of Spansion S29GLxxxS NOR flash devices could fail. Fixed.
Version V4.78g (2013-11-08)
DLL
- Linux: Under special circumstances, connection to J-Link V7 probes could fail. Fixed.
J-Flash
- Cortex-M4 devices accidentally were listed as Cortex-M3. Fixed.
- Energy Micro Zero Gecko Devices were listed as Cortex-M3 devices. Fixed.
Version V4.78f (2013-11-04)
DLL
- Under special circumstances, flash programming failed on Marvell 88MC200 devices. Fixed.
Firmware
- Flasher ARM V4 / Flasher Portable: Under special circumstances, on recoverable NAND flash failure, Flasher did not allow further writing of the on board NAND flash (causing e.g. firmware updates to be rejected)
J-Flash
- Under special circumstances, flash programming failed on Marvell 88MC200 devices. Fixed.
Version V4.78e (2013-10-25)
Firmware
- Flasher: Incorrect CFI information reported by some SST39 CFI NOR flash devices was not handled correctly in stand-alone mode. Fixed.
GDB Server
- Linux/Mac: Under special circumstances segmentation fault could occur when closing the GDB IP connection. Fixed.
- Under special circumstances, when having more than 1 GDB connection open to GDB Server (for example to allow live memory updates of variables), a stop reply packet was sent by GDB Server even on the connection which did not start the target. Fixed.
STM32 Utility
- Unlocking failed for STM32F37xx devices, since the wrong disable bit was pulled. Fixed.
Version V4.78d (2013-10-18)
Commander
- Mac/Linux 64-bit: When using loadbin to program flash memory, under special circumstances, a segmentation fault was caused. Fixed.
Firmware
- J-Link V9 / Flasher ARM V4: Under special circumstances, when using an ARM7/9 device & auto-speed target interface speed detection, J-Link selected adaptive clocking even if RTCK was not connected. Fixed.
GDB Server
- Mac/Linux 64-bit: Under special circumstances, a segmentation fault was caused. Fixed.
J-Flash
- Flasher: When downloading the configuration file to Flasher for an algorithm that needs the CPU speed and CPU speed was not properly selected in J-Flash, no error message was output. Fixed.
- Flasher: When trying to downloading a data file for TMS470, that contains key area data (last 32 bytes of first sector), into Flasher and not having "allow keys" selection selected, J-Flash could hang. Fixed.
J-Link Package
- Linux: Under Fedora, RPM installer tried to change access rights of usr/bin/ folder. Fixed.
Version V4.78c (2013-10-14)
DLL
- Atmel ATSAMD20 devices were not detected/identified correctly. Fixed.
- Special "Connect Under Reset" sequence did not work correctly for ST STM32F0 devices. Fixed.
J-Flash
- Atmel ATSAMD20 devices were not detected/identified correctly. Fixed.
- Special "Connect Under Reset" sequence did not work correctly for ST STM32F0 devices. Fixed.
- STM32F050xG devices were missing in device selection. Fixed.
Version V4.78b (2013-10-14)
DLL
- If multiple J-Links connected to the same PC should be used at the same time and SWO was used, further connections except the one to the first J-Link could fail. Fixed.
Version V4.78a (2013-10-08)
DLL
- Renesas RX220 series devices were missing. Fixed.
- Some device names for Infineon UMF11xx and UMF51xx series devices, used by IAR EWARM, were not recognized correctly. Fixed.
J-Flash
- Renesas RX220 series devices were missing. Fixed.
J-Link Package
- Mac: Installer did not install J-Link software at /Applications/. Fixed.
Version V4.78 (2013-10-04)
Commander
- Added "mem64" command.
DLL
- Added some RX210 derivates that were missing.
- Added support for Analog Device CM40x series.
- Added support for Energy Micro Zero Gecko series.
- Added support for Fujitsu FM4 series.
- Added support for Fujitsu MB9BF16xx, MB9BF36xx, MB9BF46xx, MB9BF56xx devices.
- Added support for STM32F401xB and STM32F401xC devices.
- Added support for Texas Instrument TM4C and TM4E series.
- Flash programming speed for Renesas RX200 devices improved (doubled).
- If Freescale Kinetis devices were in some special low-power mode, debugger connection could fail. Fixed/Improved.
- Under special circumstances, when connected to J-Link via TCP/IP, connection to J-Link could be lost with "Communication timeout" error message. Fixed.
- Under special circumstances, when programming incomplete sectors on Renesas RX devices, remaining data of remaining sector was filled with 0x00 instead of 0xFF. Fixed.
Firmware
- Boot-up time of J-Link ULTRA+/Pro V4 improved.
- Flasher: Under special circumstances, target interface speed was not calculated correctly in stand-alone mode, resulting in a higher speed than configured. Fixed.
GDB Server
- Added FINE to interface selection.
J-Flash
- Added sample project for Analog Device CM40x series.
- Added sample projects for Energy Micro Zero Gecko series.
- Added sample projects for Texas Instrument TMS570LS, RM42 and RM46 devices.
- Added sample projects Texas Instrument TM4C and TM4E series.
- Added some RX210 derivates that were missing.
- Added support for Analog Device CM40x series.
- Added support for Energy Micro Zero Gecko series.
- Added support for Fujitsu FM4 series.
- Added support for Texas Instrument TM4C and TM4E series.
- Flash programming speed for Renesas RX200 devices improved (doubled).
- If Freescale Kinetis devices were in some special low-power mode, debugger connection could fail. Fixed/Improved.
- Max. selectable RAMSize to be used by J-Flash for programming, extended to 512 KB (for devices which provide that much RAM).
- When programming Kinetis devices with "allow security" selection and image data contained Kinetis security byte, under special circumstances security byte was not programmed correctly. Fixed.
- When selecting "Download config & data file to Flasher" the connection to Flasher was left open after download has finished. Fixed.
J-Link Package
- Linux: Installer packages (.deb and .rpm) created.
- Linux: libusb is no longer necessary to be installed.
Remote Server
- When connecting to J-Link via J-Link Remote Server. Target interface could not be selected properly. Fixed.
Version V4.76f (2013-09-27)
DLL
- Under special circumstances, when connected to J-Link via TCP/IP, connection to J-Link could be lost with "Communication timeout" error message. Fixed.
- Under special circumstances, when programming incomplete sectors on Renesas RX devices, remaining data of remaining sector was filled with 0x00 instead of 0xFF. Fixed.
J-Flash
- When programming Kinetis devices with "allow security" selection and image data contained Kinetis security byte, under special circumstances security byte was not programmed correctly. Fixed.
Remote Server
- When connecting to J-Link via J-Link Remote Server. Target interface could not be selected properly. Fixed.
Version V4.76e (2013-09-20)
DLL
- Using the JTAG interface, hardware breakpoints could not be set when debugging on Cortex-M targets. This problem has been introduced in Version V4.76 (first version). Fixed
Version V4.76c (2013-09-13)
DLL
- Under special circumstances, CFI flash programming did not work properly. Fixed.
GDB Server
- Under special circumstances, certain printf outputs on semihosting where not handled correctly by GDB Server and string was "swallowed". Fixed.
Version V4.76b (2013-09-10)
DLL
- Under special circumstances, with old J-Links (Hardware version 6 & 7) debugging on Cortex-M devices with EWARM could cause an exception. Fixed.
Version V4.76a (2013-08-28)
DLL
- Added support for Cortex-R5 devices.
- Under special circumstances, Nordic Semi nRF51 devices were not recognized correctly. Fixed.
DLL RX
- Under special circumstances flash programming logic was not initialized correctly, causing flash programming to be slow. Fixed.
Firmware
- Flasher ARM V4: Under special circumstances, stand-alone mode programming on ARM7TDMI-S devices with high JTAG speeds (>= 4 MHz) could fail. Fixed.
- J-Link-OB-SAM3U128: Under special circumstances, bytes could be lost on virtual COM port. Fixed
J-Flash
- Options -> Project settings -> Flash now shows absolute sector addresses in detailed sector view.
Version V4.76 (2013-08-23)
DLL
- Added sample project for ST STM32F429ZI
- Added support for Analog Devices ADuCM320.
- Added support for Marvell 88MC200 series MCUs.
- Added support for Renesas R-IN32M3 series CPUs.
- Added support for ST STM32F030 series CPUs.
- Added support for ST STM32F052 series.
- Added support for ST STM32F429 series.
- Added support for ST STM32F439 series.
- Corrected flash size for Energy Micro EFMGG devices.
- Flash programming speed for Energy Micro EFM32 devices improved up to 80%.
- Flash sectorization for some Nordic Semi nRF51 devices corrected.
- RAM size for some Nordic Semi nRF51 devices corrected.
- Some TI RM48L device names used by Keil uVision were not recognized correctly. Fixed.
- Under special circumstances, access size of data breakpoints on Cortex-M devices was not considered correctly. Fixed.
- Under special circumstances, erasing of NXP LPC29xx devices could fail. Fixed.
- Under very special circumstances, unlimited breakpoints in flash memory did not work correctly on STM32F2/STM32F4 devices. Fixed.
Firmware
- Flasher: Under very special circumstances it could happen that only the first flashing cycle succeeded. Fixed.
- J-Link PRO/ULTRA+: Added FINE support for Renesas RX series CPUs.
- J-Link V9: Added FINE support for Renesas RX series CPUs.
- J-Link-OB-RX621-RX1xx: Added POWERTRACE support.
J-Flash
- Added sample project for Analog Devices ADuCM320.
- Added sample project for ST STM32F429ZI
- Added sample projects for Renesas R-IN32M3 series CPUs.
- Added sample projects for ST STM32F030 series CPUs.
- Added support for Analog Devices ADuCM320.
- Added support for Marvell 88MC200 series MCUs.
- Added support for Renesas R-IN32M3 series CPUs.
- Added support for Renesas RX111 series devices.
- Added support for Renesas RX210 series devices.
- Added support for ST STM32F030 series CPUs.
- Added support for ST STM32F052 series.
- Added support for ST STM32F429 series.
- Added support for ST STM32F439 series.
- Flash sectorization for some Nordic Semi nRF51 devices corrected.
- RAM size for some Nordic Semi nRF51 devices corrected.
- Sample project for Atmel AT91SAM9261 + DataFlash on SPI0 added.
- Under special circumstances, erasing of NXP LPC29xx devices could fail. Fixed.
Version V4.74b (2013-08-19)
DLL
- Corrected flash size for Energy Micro EFMGG devices.
- Flash sectorization for some Nordic Semi nRF51 devices corrected.
- RAM size for some Nordic Semi nRF51 devices corrected.
- Some TI RM48L device names used by Keil uVision were not recognized correctly. Fixed.
- Under special circumstances, access size of data breakpoints on Cortex-M devices was not considered correctly. Fixed.
- Under special circumstances, erasing of NXP LPC29xx devices could fail. Fixed.
- Under very special circumstances, unlimited breakpoints in flash memory did not work correctly on STM32F2/STM32F4 devices. Fixed.
Firmware
- Flasher: Under very special circumstances it could happen that only the first flashing cycle succeeded. Fixed.
J-Flash
- Flash sectorization for some Nordic Semi nRF51 devices corrected.
- RAM size for some Nordic Semi nRF51 devices corrected.
- Under special circumstances, erasing of NXP LPC29xx devices could fail. Fixed.
Version V4.74 (2013-07-17)
DLL
- Added Cypress PSoC4 series
- Added Energy Micro EFM32WG (Wonder Gecko) series
- Added Nordic Semi nRF51922_xxAA
- Added ST STM32F405OE, STM32F405OG
- Corrected RAM size for NXP LPC1112/101 devices
- ETB tracing support for LPC18xx / LPC43xx devices added.
- Flash erasing/programming speed for Luminary (TI) LM3S devices improved by > 500%.
- Flash programming for RX2xx devices could fail if watchdog was running. Fixed.
- J-Link Pro V4 / ULTRA V4 models could report a missing feature error when connecting to Atmel SAM4L devices. Fixed.
- Reset handling fixed for Cypress PSoC4 series (CY8C4xxxxxx) devices
- Reset support for Freescale i.MX6 added.
- Sectorization information for Nordic Semi nRF51422, nRF51422_xxAA corrected.
- Some device names passed by IAR EWARM were not recognized by the DLL. Fixed.
- Some Freescale Kinetis device names passed by uVision and CodeWarrior were not recognized correctly. Fixed.
- Some Freescale Kinetis device names passed by uVision and CodeWarrior were not recognized correctly. Fixed.
DLL RX
- Under special circumstances, debugging did not work correctly if sleep mode feature of the RX CPU was used in target application.
Firmware
- Flasher ARM: New firmware created to make use of speed optimization for Luminary (TI) LM3S devices.
- Flasher PPC: Under special circumstances, RAM check performed prior to programming, could fail. Fixed.
- J-Link PRO/ULTRA V4: Under special circumstances, when running SWO multiple hours some characters could be lost. Fixed.
- Under special circumstances, when reading from illegal addresses on Cortex-M devices, J-Link did not report an error but incorrect data. Fixed.
GDB Server
- SWO & semihosting printf data output via telnet channel on port 2333 added.
J-Flash
- Added Atmel ATSAM4LC8A, ATSAM4LC8B, ATSAM4LC8C
- Added Atmel ATSAMD20 series
- Added Cypress PSoC4 series
- Added Energy Micro EFM32WG (Wonder Gecko) series
- Added Nordic Semi nRF51422_xxAA, nRF51822_xxAA, nRF51822_xxAB
- Added Nordic Semi nRF51922_xxAA
- Added sample projects for Atmel ATSAMD20 series
- Added sample projects for Cypress PSoC4 series
- Added sample projects for Energy Micro EFM32WG (Wonder Gecko) series
- Added ST STM32F405OE, STM32F405OG
- Added startup dialog/wizard for project creation/selection.
- Corrected flash size for ADuCM331
- Corrected RAM size for NXP LPC1112/101 devices
- Flash erasing/programming speed for Luminary (TI) LM3S devices improved by > 500%.
- Incorrect flash information (custom RAMCode) caused problems in J-Flash. Fixed.
- Sectorization information for Nordic Semi nRF51422, nRF51422_xxAA corrected.
Version V4.72a (2013-06-26)
DLL
- Some device names passed by IAR EWARM were not recognized by the DLL. Fixed.
Version V4.72 (2013-06-12)
DLL
- Added support for Altera Cyclone V Cortex-A9 device.
- Added support for AT91SAM4N8A, AT91SAM4N8B, AT91SAM4N8C, AT91SAM4N16B, AT91SAM4N16C
- Added support for CC2538NF11, CC2538NF23, CC2538NF53, CC2538SF23, CC2538SF53, CM2538SF23, CM2538SF53
- Added support for Freescale MKE02Z16xxx2, MKE02Z32xxx2, MKE02Z64xxx2
- Added support for Infineon's SPD debug interface, used on XMC1000 series devices.
- Added support for Infineon's SPD debug interface, used on XMC1000 series devices.
- Analog Devices ADuCM350: Not the full 384 KB flash could be programmed. Fixed.
- Flash programming of second flash bank did not work properly for Atmel ATSAM4SD16 & ATSAM4SD32 devices. Fixed.
- When downloading into Kinetis data flash, under special circumstances an "address is out of data flash range" error was reported even if this was not the case. Fixed.
J-Flash
- Added sample project CC2538NF11
- Added sample project CC2538NF23
- Added sample project CC2538NF53
- Added sample project CC2538SF23
- Added sample project CC2538SF53
- Added sample project CM2538SF23
- Added sample project CM2538SF53
- Added sample projects AT91SAM4N8A, AT91SAM4N8B, AT91SAM4N8C, AT91SAM4N16B, AT91SAM4N16C
- Added support for AT91SAM4N8A, AT91SAM4N8B, AT91SAM4N8C, AT91SAM4N16B, AT91SAM4N16C
- Added support for CC2538NF11, CC2538NF23, CC2538NF53, CC2538SF23, CC2538SF53, CM2538SF23, CM2538SF53
- Added support for Freescale MKE02Z16xxx2, MKE02Z32xxx2, MKE02Z64xxx2
- Analog Devices ADuCM350: Not the full 384 KB flash could be programmed. Fixed.
- Under special circumstances, flash programming for MB9AF131K/L/M/N and MB9AF132K/L/M/N did not work correctly. Fixed.
- Under special circumstances, flash programming for MB9AF131K/L/M/N and MB9AF132K/L/M/N did not work correctly. Fixed.
- When downloading into Kinetis data flash, under special circumstances an "address is out of data flash range" error was reported even if this was not the case. Fixed.
- When the project specified a SN and this J-Link was not found, J-Flash connected to another one. Fixed.
Version V4.70a (2013-05-14)
DLL
- ARM11: Stepping an SWI/SVC instruction did not work properly. Fixed.
- ARM11: Under special circumstances, reading the SVC CPU registers did not work properly. Fixed.
Firmware
- Flasher: #FREAD command via telnet did not work properly. Fixed.
Version V4.70 (2013-05-07)
Commander
- Linux/Mac: SWOViewer command did not display characters until a \n was received. Fixed.
- Mac: Under special circumstances, a segmentation fault could be caused when J-Link Commander exited without ever trying to communicate with a connected J-Link (error during cleanup of libusb). Fixed.
DLL
- Added support for Atmel SAM4E8E, SAM4E16E
- Added support for Nuvoton M051, M052, M054, M058, MINI51, MINI52, MINI54, NANO100, NANO110, NANO120, NANO130, NUC200, NUC220 series devices
- Added support for Nuvoton NUC100, NUC120, NUC122, NUC123, NUC130, NUC140 series devices
- Linux: Getting SWO data did not work correctly. Fixed
- Some Nuvoton NUC1xx device names selectable in IAR EWARM were not recognized correctly by the DLL, causing unlimited flash breakpoints to not work correctly. Fixed.
- Under special circumstances when reading FPU registers on ARM 7/9, the RAM temporarily used for this operation was not restored properly. Fixed.
- When trying to read FPU registers on ARM7/9 while the FPU was disabled, J-Link could lose connection to the target. Fixed.
- Writing FPU registers on ARM 7 / 9 targets did not work properly. Fixed.
Firmware
- J-Link V9 Max. SWD speed supported by J-Link improved.
GDB Server
- Semihosting output for ARM7/9 and Cortex-M via connection on port 2333 added.
J-Flash
- Added sample project STM32F205ZG_1x16_CFI_NOR_nCS3.jflash
- Added sample project STM32F407IG_1x16_CFI_NOR_nCS0.jflash
- Added sample projects for Nuvoton M052, M054, M058, MINI51, MINI52, MINI54, NANO100, NANO110, NANO120, NANO130, NUC100, NUC120, NUC122, NUC123, NUC130, NUC140, NUC200, NUC220 series devices
- Added support for Atmel SAM4E8E, SAM4E16E
- Added support for Nuvoton M051, M052, M054, M058, MINI51, MINI52, MINI54, NANO100, NANO110, NANO120, NANO130, NUC200, NUC220 series devices
- Added support for Nuvoton NUC100, NUC120, NUC122, NUC123, NUC130, NUC140 series devices
J-Link Package
- Linux: Added SWOViewer
- Mac: *.command scripts failed when they were located in a path that contains space characters. Fixed.
- Mac: Added SWOViewer
- Mac: libusb is no longer necessary to be installed.
SWO Viewer
- Added command line options for ITM port mask (-ITMMask).
- Added command line options for output log file (-OutputFile).
- Added command line options for specifying J-Link settings file (-SettingsFile)
Version V4.68a (2013-04-12)
DLL
- Added support for Freescale MKL02Z8xxx4, MKL02Z16xxx4, MKL02Z32xxx4, MKL16Z32xxx4, MKL16Z64xxx4, MKL16Z128xxx4, MKL16Z256xxx4, MKL26Z32xxx4, MKL26Z64xxx4, MKL26Z128xxx4, MKL26Z256xxx4, MKL34Z64xxx4, MKL36Z64xxx4, MKL36Z128xxx4, MKL36Z256xxx4, MKL46Z128xxx4, MKL46Z256xxx4
Version V4.68 (2013-04-06)
DLL
- Added support for Cypress CY8C5266xxxLP, CY8C5267xxxLP, CY8C5268xxxLP, CY8C5466xxxLP, CY8C5467xxxLP, CY8C5468xxxLP, CY8C5666xxxLP, CY8C5667xxxLP, CY8C5668xxxLP, CY8C5866xxxLP, CY8C5867xxxLP, CY8C5868xxxLP
- Incorrect flash size reported for Freescale: MK10DX64xxx7, MK20DX64xxx7, MK30DX64xxx7, MK40DX64xxx7, MK10DX128xxx7, MK20DX128xxx7, MK30DX128xxx7, MK40DX128xxx7, MK50DX128xxx7, MK51DX128xxx7, MK10DX256xxx7, MK20DX256xxx7, MK30DX256xxx7, MK40DX256xxx7, MK50DX256xxx7, MK51DX256xxx7. Fixed.
Firmware
- J-Link-OB-XMC4200: Under special circumstances, CDC (virtual COM port) + parallel debugging did not work properly. Fixed.
- J-Link-OB-XMC4200: When changing the operating baud rate of the virtual COM port on the J-Link-OB, a unwanted "glitch" (high-to-low transition) was caused on the Tx line of the J-Link-OB. Fixed.
J-Flash
- Added sample project CY8C5266xxxLP.jflash
- Added sample project CY8C5267xxxLP.jflash
- Added sample project CY8C5268xxxLP.jflash
- Added sample project CY8C5466xxxLP.jflash
- Added sample project CY8C5467xxxLP.jflash
- Added sample project CY8C5468xxxLP.jflash
- Added sample project CY8C5666xxxLP.jflash
- Added sample project CY8C5667xxxLP.jflash
- Added sample project CY8C5668xxxLP.jflash
- Added sample project CY8C5866xxxLP.jflash
- Added sample project CY8C5867xxxLP.jflash
- Added sample project CY8C5868xxxLP.jflash
- Added support for Cypress CY8C5266xxxLP, CY8C5267xxxLP, CY8C5268xxxLP, CY8C5466xxxLP, CY8C5467xxxLP, CY8C5468xxxLP, CY8C5666xxxLP, CY8C5667xxxLP, CY8C5668xxxLP, CY8C5866xxxLP, CY8C5867xxxLP, CY8C5868xxxLP
- Some flash sectors were not selected in the sample projects of AT91SAM4S devices by default. Corrected.
Version V4.66a (2013-03-25)
DLL
- Flash programming did not work properly for NXP LPC11xx devices which have less than 2 KB RAM. Fixed.
- Work-RAM for NXP LPC31xx / LPC32xx devices, used for example to read FPU registers, was not selected automatically when selecting the device. Fixed.
Firmware
- Flasher: stand-alone: Erase sectors did not work properly for STM32F0 and STM32F1xxx "allow opt. bytes" selection. Fixed.
- Flasher: stand-alone: Under special circumstances, when using Multi-Bank support in stand-alone mode, Flasher could run into memory-allocation problems causing the flash process to be aborted with error. Fixed.
- Flasher: stand-alone: Unsecure option did not work properly for STM32F0 devices. Fixed.
- Flasher: Under special circumstances, custom RAMCode handling did not work correctly and caused errors. Fixed.
J-Flash
- Under special circumstances, custom RAMCode handling did not work correctly and caused errors. Fixed.
Version V4.66 (2013-03-11)
Commander
- For some models with ethernet support "ipaddr" command did not work properly. Fixed.
Configurator
- For some J-Link models "Product" chart in configurator list view was not filled correctly. Fixed.
DLL
- Flash programming speed improved.
- If a previous debug session was terminated abnormally, When starting SWO in the next session, the error message "SWO buffer size reported by J-Link is too small" could appear. Fixed.
- nRF51xx devices: Support for user configuration area added.
J-Flash
- Erase sectors did not work properly for STM32F0 and STM32F1xxx "allow opt. bytes" selection. Fixed.
- nRF51xx devices: Support for user configuration area added.
- Unsecure option did not work properly for STM32F0 devices. Fixed.
Version V4.64 (2013-02-20)
DLL
- Added support for ST STM32F427IG, STM32F427II, STM32F427VG, STM32F427VI, STM32F427ZG, STM32F427ZI, STM32F437IG, STM32F437II, STM32F437VG, STM32F437VI, STM32F437ZG, STM32F437ZI
Firmware
- Flasher ARM: For Freescale Kinetis devices with built-in DataFlash, erasing in stand-alone mode did not work properly when "Chip" was selected as erase setting in "Production" tab in J-Flash. Fixed.
- Flasher ARM: For STM32F4 devices, erasing in stand-alone mode could fail if "Chip" was selected as erase setting in "Production" tab in J-Flash. Fixed.
J-Flash
- Added sample project STM32F437II.jflash
- Added support for ST STM32F427IG, STM32F427II, STM32F427VG, STM32F427VI, STM32F427ZG, STM32F427ZI, STM32F437IG, STM32F437II, STM32F437VG, STM32F437VI, STM32F437ZG, STM32F437ZI
- When trying to open hex files which contain unknown/custom record types, J-Flash refused to open the file instead of just ignoring the unknown records. Fixed.
J-Link Package
- Installer: When selecting "USB driver for J-Link-OB with CDC" a separate installer was started. Separate installer removed. Installation of this driver is now handled by regular installer.
- Installer: When selecting "USB driver for J-Link-OB with CDC" and this USB driver was already installed under special circumstances, installing it again could cause "Repair/Modify/Remove" dialog. Fixed.
Version V4.62b (2013-02-18)
DLL
- Sectorization for Atmel ATSAM4S series optimized.
- Under special circumstances, cleaning up software breakpoints in flash memory on disconnect could cause an unhandled exception. Fixed.
- Under special circumstances, if configured CFI flash size differed from detected one, CFI flash download could cause an exception. Fixed.
J-Flash
- Sectorization for Atmel ATSAM4S series optimized.
Version V4.62a (2013-02-04)
DLL
- Under special circumstances, using the "unlimited breakpoints in flash memory" could cause an exception. Fixed.
- Workaround for Analog Devices ADuCM330 & ADuCM331 code breakpoint bug implemented.
SWO Viewer CL
- Command line parameter -ITMPort <Port> was not evaluated correctly. Fixed.
Version V4.62 (2013-01-25)
DLL
- Added support for NXP devices LPC810M021, LPC811M001, LPC812M101
- Added support for Fujitsu MB9AF111K, MB9AF112K, MB9AF311K, MB9AF312K, MB9BFD16S, MB9BFD16T, MB9BFD17S, MB9BFD17T, MB9BFD18S, MB9BFD18T
- Added support for Infineon XMC1100 series, XMC1200 series, XMC1201 series, XMC1202 series, XMC1203 series, XMC1301 series, XMC1302 series
- Added support for NXP LPC1812, LPC1813, LPC1815, LPC1817, LPC1822, LPC1823, LPC1825, LPC1827
- Added support for NXP LPC4312, LPC4313, LPC4315, LPC4317, LPC4322, LPC4323, LPC4325, LPC4327, LPC4333, LPC4337, LPC4353, LPC4357
- Flash programming did not work correctly for Fujitsu MB9AF131K, MB9AF131L, MB9AF132K, MB9AF132L. Fixed.
- For some current LPC43xx devices reset did not work properly. Fixed.
- Linux: J-Link OBs with CDC functionality were not detected correctly. Fixed.
- Mac: Under special circumstances, flash programming via DLL could cause a segmentation fault. Fixed.
Firmware
- Flasher: ARM, RX and PPC: Manuals combined.
J-Flash
- Added support for NXP devices LPC810M021, LPC811M001, LPC812M101
- Added sample project AT91SAM4SP32A.jflash
- Added sample project LPC1812M101.jflash
- Added support for Fujitsu MB9AF111K, MB9AF112K, MB9AF311K, MB9AF312K, MB9BFD16S, MB9BFD16T, MB9BFD17S, MB9BFD17T, MB9BFD18S, MB9BFD18T
- Added support for Infineon XMC1100 series, XMC1200 series, XMC1201 series, XMC1202 series, XMC1203 series, XMC1301 series, XMC1302 series
- Added support for NXP LPC1812, LPC1813, LPC1815, LPC1817, LPC1822, LPC1823, LPC1825, LPC1827
- Added support for NXP LPC4312, LPC4313, LPC4315, LPC4317, LPC4322, LPC4323, LPC4325, LPC4327, LPC4333, LPC4337, LPC4353, LPC4357
- Flash programming did not work correctly for Fujitsu MB9AF131K, MB9AF131L, MB9AF132K, MB9AF132L. Fixed.
J-Link Package
- Linux: 45-jlink.rules updated (J-Links with CDC functionality were not covered).
- Linux: 45-jlink.rules updated.
- Linux: README updated.
- Linux: Readme updated.
- Linux: Starter shell scripts updated.
- Mac: Command files updated.
Version V4.60a (2013-01-16)
DLL
- Added support for Atmel devices AT91SAM4SP32A
- Some error message boxes were accidentally created in the backgound on not on top of the debugger window. Fixed.
J-Flash
- Added support for Atmel devices AT91SAM4SP32A
Version V4.60 (2013-01-14)
DLL
- Added Analog Devices ADuCM301
- Added Toshiba TB6865FG
- Flash programming did not work properly under special circumstances. Fixed.
- Flash programming speed highly improved.
- LPC1810, LPC1820, LPC1830, LPC1850 SPIFI flash programming support added.
- Mac: J-Link OBs with CDC functionality were not detected properly. Fixed.
- Under special circumstances, reset for LPC18xx devices did not work properly when target was configured for booting from SPIFI. Fixed.
DLL Updater
- Some installations of Atmel Studio were not recognized correctly. Fixed.
Firmware
- Flasher: ARM: Flash programming did not work properly for STM32F05x devices. Fixed.
- Flasher: PPC: Added support for ST SPC560B54, SPC560B60, SPC560B64
- For J-Links with CDC functionality, under very special circumstances, bytes received from the host (PC) were lost. Fixed.
- Under special circumstances, communication problems could occur with J-Link V9 + i-Chips IP00C753 target device. Fixed.
GDB Server
- Implemented alternative register set with FPU registers for Cortex-M4.
- When Cortex-A9 was connected. GDB Server showed "Cortex-A8 was found". Fixed.
J-Flash
- Added Analog Devices ADuCM301
- Added sample project TB6865FG.jflash
- Added Toshiba TB6865FG
- Cortex-M0 devices did not work properly under special circumstances. Fixed.
- LPC1810, LPC1820, LPC1830, LPC1850 SPIFI flash programming support added.
- Wrong device selected in the sample project ADuCRF101.jflash. Fixed.
Version V4.58a (2012-12-05)
GDB Server
- Command line options -port and -SWOPort did not work properly. Fixed.
- If "Cancel" is selected in the configuration dialog, now dialog settings are not taken into consideration instead of closing the complete GDB Server
- If connection to J-Link failed, under special circumstances, GDB Server could end up in an endless loop, periodically trying to connect to J-Link again. Fixed.
Version V4.58 (2012-11-29)
DLL
- Added Atmel ATSAM4LC1A/B/C, Atmel ATSAM4LC2A/B/C, Atmel ATSAM4LC4A/B/C, Atmel ATSAM4LS1A/B/C, Atmel ATSAM4LS2A/B/C, Atmel ATSAM4LS4A/B/C
- Added Fujitsu MB9AF141L/LA/M/MA/N/NA, Fujitsu MB9AF142L/LA/M/MA/N/NA, Fujitsu MB9AF144L/LA/M/MA/N/NA, Fujitsu MB9AF341L/LA/M/MA/N/NA, Fujitsu MB9AF342L/LA/M/MA/N/NA, Fujitsu MB9AF344L/LA/M/MA/N/NA, Fujitsu MB9AFA41L/LA/M/MA/N/NA, Fujitsu MB9AFA42L/LA/M/MA/N/NA, Fujitsu MB9AFA44L/LA/M/MA/N/NA, Fujitsu MB9AFB41LA/MA/NA, Fujitsu MB9AFB42LA/MA/NA, Fujitsu MB9AFB44LA/MA/NA, Fujitsu MB9BF121K/L/M, Fujitsu MB9BF122K/L/M, Fujitsu MB9BF124K/L/M, Fujitsu MB9BF321K/L/M, Fujitsu MB9BF322K/L/M, Fujitsu MB9BF324K/L/M
- Added Fujitsu MB9DF125, Fujitsu MB9DF126, Fujitsu MB9EF126
- Added NXP LPC11E36/501, NXP LPC11E37/501
- Added Renesas R5F562G7/A, Renesas R5F56307/8/A/B/D/E, Renesas R5F563T4/5/6
- Added support for combination 2x8 bit CFI flash.
- DLL reported wrong sector size for FlexNVM area of Freescale Kinetis K series 72 MHz devices. Fixed.
- Flash programming feature used wrong sector size for some STM32F105/107 devices. Fixed.
- Some TI CC2538 devices were not recognized correctly. Fixed.
- Support for STM32L data flash added.
- Under special circumstances connecting to SAM4L devices could fail even if a connect with "Core Hold Reset" was performed. Fixed.
- Under special circumstances JLINKARM_ReadReg() did not recognize that the CPU was actually halted. Fixed.
- Under special circumstances, flash programming on LPC1788 targets could fail if the CPU was running at >= 100 MHz. Fixed.
DLL Updater
- Some new IAR EWARM installations were not recognized correctly. Fixed.
Firmware
- Flasher: ARM/RX/PPC: Core ID mask which has been configured in J-Flash was not used correctly in stand-alone mode, which could cause problems in stand-alone mode on some MCUs. Fixed.
- Flasher: PPC: Added support for Freescale MPC5605B/606B/607B
GDB Server
- Added startup configuration dialog for GUI version
J-Flash
- Added Atmel ATSAM4LC1A/B/C, Atmel ATSAM4LC2A/B/C, Atmel ATSAM4LC4A/B/C, Atmel ATSAM4LS1A/B/C, Atmel ATSAM4LS2A/B/C, Atmel ATSAM4LS4A/B/C
- Added Fujitsu MB9AF141L/LA/M/MA/N/NA, Fujitsu MB9AF142L/LA/M/MA/N/NA, Fujitsu MB9AF144L/LA/M/MA/N/NA, Fujitsu MB9AF341L/LA/M/MA/N/NA, Fujitsu MB9AF342L/LA/M/MA/N/NA, Fujitsu MB9AF344L/LA/M/MA/N/NA, Fujitsu MB9AFA41L/LA/M/MA/N/NA, Fujitsu MB9AFA42L/LA/M/MA/N/NA, Fujitsu MB9AFA44L/LA/M/MA/N/NA, Fujitsu MB9AFB41LA/MA/NA, Fujitsu MB9AFB42LA/MA/NA, Fujitsu MB9AFB44LA/MA/NA, Fujitsu MB9BF121K/L/M, Fujitsu MB9BF122K/L/M, Fujitsu MB9BF124K/L/M, Fujitsu MB9BF321K/L/M, Fujitsu MB9BF322K/L/M, Fujitsu MB9BF324K/L/M
- Added Fujitsu MB9DF125, Fujitsu MB9DF126, Fujitsu MB9EF126
- Added NXP LPC11E36/501, NXP LPC11E37/501
- Added Renesas R5F562G7/A, Renesas R5F56307/8/A/B/D/E, Renesas R5F563T4/5/6
- Added sample project LM4F120H5QR.jflash
- Added sample project MB9BF618T_1x16_CFI_NORFlash.jflash.
- Added sample project MPC5605B.jflash
- Added sample project MPC5606B.jflash
- Added sample project MPC5607B.jflash
- Added Sample projects for Fujitsu MB9DF / MB9EF devices.
- Added Sample projects for Fujitsu MB9DF / MB9EF devices.
- Added sample projects for SAM4L series.
- Added some new SST Flashes: SST32HF64A2, SST32HF162, SST32HF164, SST32HF802
- DLL reported wrong sector size for FlexNVM area of Freescale Kinetis K series 72 MHz devices. Fixed.
- Flash programming feature used wrong sector size for some STM32F105/107 devices. Fixed.
- J-Flash now asks if project changes shall be saved before exit
- Support for STM32L data flash added.
- Under special circumstances, flash programming on LPC1788 targets could fail if the CPU was running at >= 100 MHz. Fixed.
Remote Server
- Command line version added to software package
Version V4.56d (2012-11-12)
DLL
- Added some Kinetis device name aliases for CodeWarrior.
- Data flash sector size of Kinetis 72 MHz CPUs was incorrect. Fixed.
J-Flash
- Data flash sector size of Kinetis 72 MHz CPUs was incorrect. Fixed.
Version V4.56c (2012-11-08)
J-Flash
- Under special circumstances, programming of some specific parallel NOR flash devices could fail if the flash device was selected explicitly in J-Flash. Fixed. Note: Problem did not occur when using CFI auto-detection.
Version V4.56b (2012-11-07)
Version V4.56a (2012-11-05)
DLL
- Indirect read of fast GPIO registers did not work properly if a certain number of bytes per read request was exceeded. Fixed.
- Reset on Atmel SAM4S devices did not reset the watchdog timer. Fixed.
- Some SST39 CFI NOR flash devices were not detected correctly. Fixed.
DLL RX
- Some new RX62G, RX630 and RX63T series devices were not detected correctly. Fixed.
Firmware
- Flasher ARM/RX/PPC: Connecting to Flasher webserver did not work properly. Fixed.
- Flasher RX: If RX was configured for big endian, under special circumstances stand-alone mode did not work properly. Fixed.
- J-Link-OB-SAM3U128: Under special circumstances it could happen that CDC hang when using a OB with flow-control support. Fixed.
J-Flash
- CFI detection of 1x8 Bit NOR flash combination did not work properly. Fixed.
Version V4.56 (2012-10-22)
DLL
- Added NXP LPC1101LVUK, LPC1102LVUK, LPC1112LV/003, LPC1112LV/103, LPC1114LV/103, LPC1114LV/303
J-Flash
- Added NXP LPC1101LVUK, LPC1102LVUK, LPC1112LV/003, LPC1112LV/103, LPC1114LV/103, LPC1114LV/303
Version V4.54d (2012-10-16)
DLL
- Connecting to Analog Devices ADuC7124 and ADuC7126 devices did not work properly. Fixed.
- Under special circumstances closing the DLL took longer than necessary. Fixed.
- Under special circumstances, reset strategy for Analog Devices ARM7 based devices could hang. Fixed.
Firmware
- J-Link Pro V1 & V3: Under very special circumstances, the firmware of J-Link Pro could hang causing a connection timeout. Fixed.
- J-Link-OB-SAM3U128 on nRF51 Kits: CDC functionality with hardware flow control: Under special circumstances single bytes could be lost when reading target terminal data.
J-Flash
- First entry of device list (MCU.csv) was not shown in device selection dialog. Fixed.
Version V4.54c (2012-10-09)
DLL
- Mac: J-Links with CDC support where not detected correctly. Fixed.
- Some TI device aliases passed by some debuggers where not recognized correctly. Fixed.
Version V4.54b (2012-10-02)
Firmware
- Flasher ARM: Under special circumstances reset was triggered twice on Toshiba TMPA910 devices in stand-alone mode. Fixed.
- Flasher ARM: Under special circumstances, reset pulse with reset strategy 0 on ARM7/9 was too short. Fixed.
J-Flash
- RAMCode for LPC11Axx EEPROM programming did not detect some LPC1Axx devices correctly and reported an incorrect EEPROM size. Fixed.
Version V4.54a (2012-09-17)
DLL
- Some Kinetis device names were not recognized/mapped correctly. Fixed.
- Under special circumstances on STM32 devices the DBGMCU_CR was not written correctly. Fixed.
- Under special circumstances when writing pseudo CPU registers which are part of another CPU register, it could happen that other parts of the CPU register were accidentally changed. Fixed.
- Under special circumstances, it could happen that a memory write access was not routed through the hardware correctly. Fixed.
Version V4.54 (2012-09-11)
DLL
- Added (device name + J-Flash project) Luminary LM3S1110, LM3S1133, LM3S1138, LM3S1150, LM3S1162, LM3S1165, LM3S1166, LM3S1332, LM3S1435, LM3S1439, LM3S1512, LM3S1538, LM3S1601, LM3S1607, LM3S1608, LM3S1620, LM3S1625, LM3S1626, LM3S1627, LM3S1635, LM3S1636, LM3S1637, LM3S1651, LM3S1776, LM3S1811, LM3S1816, LM3S1850, LM3S1B21, LM3S1C21, LM3S1C26, LM3S1C58, LM3S1D26, LM3S1F11, LM3S1G21, LM3S1G58, LM3S1H16, LM3S1J11, LM3S1J16, LM3S1N16, LM3S1P51, LM3S1R21, LM3S1R26, LM3S1W16, LM3S1Z16, LM3S2016, LM3S2276, LM3S2608, LM3S2671, LM3S2776, LM3S2793, LM3S2911, LM3S2918, LM3S2919, LM3S2U93, LM3S3634, LM3S3651, LM3S3654, LM3S5651, LM3S5652, LM3S5656, LM3S5662, LM3S5737, LM3S5739, LM3S5747, LM3S5749, LM3S5752, LM3S5762, LM3S5791, LM3S5956, LM3S5C31, LM3S5C36, LM3S5C51, LM3S5C56, LM3S5K31, LM3S5P3B, LM3S5P51, LM3S5P56, LM3S5R31, LM3S5U91, LM3S6537, LM3S6611, LM3S6618, LM3S6753, LM3S6916, LM3S6950, LM3S6C11, LM3S6C65, LM3S6G11, LM3S8970, LM3S8C62, LM3S8G62, LM3S9781, LM3S9971, LM3S9B81, LM3S9BN2, LM3S9BN5, LM3S9BN6, LM3S9CN5, LM3S9D81, LM3S9D90, LM3S9DN5, LM3S9DN6, LM3S9G97, LM3S9GN5, LM3S9L71, LM3S9U90, LM3S9U92, LM3S9U95, LM3S9U96
- Added Atmel AT91SAM3N00A, AT91SAM3N00B, AT91SAM3N0A, AT91SAM3N0B, AT91SAM3N0C
- Added Atmel AT91SAM4SA16B, AT91SAM4SA16C, AT91SAM4SD16B, AT91SAM4SD16C, AT91SAM4SD32B, AT91SAM4SD32C
- Added Energy Micro EFM32TG225F8, EFM32TG225F16, EFM32TG225F32, EFM32TG825F8, EFM32TG825F16, EFM32TG825F32
- Added Fujitsu MB9AFB41L, MB9AFB41M, MB9AFB41N, MB9AFB42L, MB9AFB42M, MB9AFB42N, MB9AFB44L, MB9AFB44M, MB9AFB44N
- Added NXP LPC1759
- Added Toshiba TMPM061FWFG
- Added work flash programming support for some Fujitsu devices. Affected devices: MB9BF112N, MB9BF112R, MB9BF114N, MB9BF114R, MB9BF115N, MB9BF115R, MB9BF116N, MB9BF116R, MB9BF412N, MB9BF412R, MB9BF414N, MB9BF414R, MB9BF415N, MB9BF415R, MB9BF416N, MB9BF416R, MB9BF512N, MB9BF512R, MB9BF514N, MB9BF514R, MB9BF515N, MB9BF515R, MB9BF516N, MB9BF516R
- LPC18xx flash based devices: Under special circumstances, checksum was accidentally also merged into flash bank 1. Fixed.
- Reset of flash-based LPC18xx devices did not work properly. Fixed.
- Some AT91SAM3N0 devices where not detected correctly by SAM-ICE. Fixed.
- Some Luminary/TI LM3S devices with internal ROM bootloader were not handled correctly, so programming of blank devices caused problems. Fixed. Affected devices: LM3S1621, LM3S1D21, LM3S1H11, LM3S1N11, LM3S2B93, LM3S2D93, LM3S5632, LM3S5732, LM3S5951, LM3S5K36, LM3S5B91, LM3S5R36, LM3S5T36, LM3S5Y36, LM3S6G65
- Some SAM3N devices were not detected properly by SAM-ICE. Fixed.
- Under special circumstances, connecting to blank Kinetis devices did not work properly. Fixed.
- Under special circumstances, debugging on Analog Devices ADuC7023 devices did not work properly. Fixed.
- Work flash support for the following Fujitsu Cortex-M3 based devices added: MB9AFB41L, MB9AFB41M, MB9AFB41N, MB9AFB42L, MB9AFB42M, MB9AFB42N, MB9AFB44L, MB9AFB44M, MB9AFB44N
Firmware
- J-Link Lite XMC4500: Under special circumstances, SWO did not work properly . Fixed.
GDB Server
- 'k' packet was not handled correctly. Fixed.
- Typo in register list for Cortex-M: BASEPRI was printed as "BASPRI". Fixed.
J-Flash
- Added (device name + J-Flash project) Luminary LM3S1110, LM3S1133, LM3S1138, LM3S1150, LM3S1162, LM3S1165, LM3S1166, LM3S1332, LM3S1435, LM3S1439, LM3S1512, LM3S1538, LM3S1601, LM3S1607, LM3S1608, LM3S1620, LM3S1625, LM3S1626, LM3S1627, LM3S1635, LM3S1636, LM3S1637, LM3S1651, LM3S1776, LM3S1811, LM3S1816, LM3S1850, LM3S1B21, LM3S1C21, LM3S1C26, LM3S1C58, LM3S1D26, LM3S1F11, LM3S1G21, LM3S1G58, LM3S1H16, LM3S1J11, LM3S1J16, LM3S1N16, LM3S1P51, LM3S1R21, LM3S1R26, LM3S1W16, LM3S1Z16, LM3S2016, LM3S2276, LM3S2608, LM3S2671, LM3S2776, LM3S2793, LM3S2911, LM3S2918, LM3S2919, LM3S2U93, LM3S3634, LM3S3651, LM3S3654, LM3S5651, LM3S5652, LM3S5656, LM3S5662, LM3S5737, LM3S5739, LM3S5747, LM3S5749, LM3S5752, LM3S5762, LM3S5791, LM3S5956, LM3S5C31, LM3S5C36, LM3S5C51, LM3S5C56, LM3S5K31, LM3S5P3B, LM3S5P51, LM3S5P56, LM3S5R31, LM3S5U91, LM3S6537, LM3S6611, LM3S6618, LM3S6753, LM3S6916, LM3S6950, LM3S6C11, LM3S6C65, LM3S6G11, LM3S8970, LM3S8C62, LM3S8G62, LM3S9781, LM3S9971, LM3S9B81, LM3S9BN2, LM3S9BN5, LM3S9BN6, LM3S9CN5, LM3S9D81, LM3S9D90, LM3S9DN5, LM3S9DN6, LM3S9G97, LM3S9GN5, LM3S9L71, LM3S9U90, LM3S9U92, LM3S9U95, LM3S9U96
- Added Atmel AT91SAM3N00A, AT91SAM3N00B, AT91SAM3N0A, AT91SAM3N0B, AT91SAM3N0C
- Added Atmel AT91SAM4SA16B, AT91SAM4SA16C, AT91SAM4SD16B, AT91SAM4SD16C, AT91SAM4SD32B, AT91SAM4SD32C
- Added Energy Micro EFM32TG225F8, EFM32TG225F16, EFM32TG225F32, EFM32TG825F8, EFM32TG825F16, EFM32TG825F32
- Added Fujitsu MB9AFB41L, MB9AFB41M, MB9AFB41N, MB9AFB42L, MB9AFB42M, MB9AFB42N, MB9AFB44L, MB9AFB44M, MB9AFB44N
- Added NXP LPC1759
- Added Toshiba TMPM061FWFG
- Added work flash programming support for some Fujitsu devices. Affected devices: MB9BF112N, MB9BF112R, MB9BF114N, MB9BF114R, MB9BF115N, MB9BF115R, MB9BF116N, MB9BF116R, MB9BF412N, MB9BF412R, MB9BF414N, MB9BF414R, MB9BF415N, MB9BF415R, MB9BF416N, MB9BF416R, MB9BF512N, MB9BF512R, MB9BF514N, MB9BF514R, MB9BF515N, MB9BF515R, MB9BF516N, MB9BF516R
- LPC18xx flash based devices: Under special circumstances, checksum was accidentally also merged into flash bank 1. Fixed.
- Sample project AT91SAM3N00A.jflash added
- Sample project AT91SAM3N0C.jflash added
- Sample project AT91SAM4SA16B.jflash added
- Sample project AT91SAM4SA16C.jflash added
- Sample project AT91SAM4SD16B.jflash added
- Sample project AT91SAM4SD16C.jflash added
- Sample project AT91SAM4SD32B.jflash added
- Sample project AT91SAM4SD32C.jflash added
- Sample project MB9AFB41L.jflash added
- Sample project MB9AFB41M.jflash added
- Sample project MB9AFB41N.jflash added
- Sample project MB9AFB42L.jflash added
- Sample project MB9AFB42M.jflash added
- Sample project MB9AFB42N.jflash added
- Sample project MB9AFB44L.jflash added
- Sample project MB9AFB44M.jflash added
- Sample project MB9AFB44N.jflash added
- Sample project TMPM061FWFG.jflash added
- Some Luminary/TI LM3S devices with internal ROM bootloader were not handled correctly, so programming of blank devices caused problems. Fixed. Affected devices: LM3S1621, LM3S1D21, LM3S1H11, LM3S1N11, LM3S2B93, LM3S2D93, LM3S5632, LM3S5732, LM3S5951, LM3S5K36, LM3S5B91, LM3S5R36, LM3S5T36, LM3S5Y36, LM3S6G65
- When opening the device selection dialog in J-Flash, it always jumped to the first entry in the device table and not to the one which is currently selected. Fixed.
- Work flash support for the following Fujitsu Cortex-M3 based devices added: MB9AFB41L, MB9AFB41M, MB9AFB41N, MB9AFB42L, MB9AFB42M, MB9AFB42N, MB9AFB44L, MB9AFB44M, MB9AFB44N
License Manager
- utility added.
Version V4.52c (2012-08-30)
DLL
- Under special circumstances, CFI flash programming did not work properly for Cortex-M4 devices. Fixed.
- When setting / clearing hardware breakpoints on Cortex-M targets CPU was always halted temporarily, even if not necessary. Fixed.
GDB Server
- Added command line option -jtagconf which is fully compatible to the jtagconf monitor command.
Version V4.52b (2012-08-24)
Configurator
- Under special circumstances the Configurator/DLL could crash when requesting a list of all connected emulators and many emulators have been found. Fixed.
DLL
- Flash programming dialog took focus away from currently active application. Fixed.
- Reset for LPC18xx flashless(!) devices did not work properly even if correct device was selected in the debugger. Fixed. Affected devices: LPC1810, LPC1812, LPC1813, LPC1815, LPC1817, LPC1820, LPC1822, LPC1823, LPC1825, LPC1827, LPC1830, LPC1850
- Under special circumstances the Configurator/DLL could crash when requesting a list of all connected emulators and many emulators have been found. Fixed.
Firmware
- J-Link Lite XMC4000: SWO did not work properly. Fixed.
- J-Link OB STM32: Reset pin was driven HIGH by J-Link OB which could make problems on boards which also have a reset button. Fixed.
Version V4.52a (2012-08-17)
DLL
- Some Luminary/TI LM3S devices with internal ROM bootloader were not handled correctly, so programming of blank devices caused problems. Fixed. Affected devices: LM3S9790, LM3S9792, LM3S9997, LM3S9B90, LM3S9B92, LM3S9B95, LM3S9B96, LM3S9C97, LM3S9D92, LM3S9D95, LM3S9D96, LM3S9L97, LM3S9U81
- When using the J-Link OB on the Energy Micro DVKs with a specific firmware from October 2011, an incorrect buffer size was reported by the OB which could cause a crash of the DLL when starting SWO capturing. Crash has been fixed.
Firmware
- Flasher: Under special circumstances it could happen that only the first programming cycle worked when using SWD in stand-alone mode. Fixed.
J-Flash
- Some Luminary/TI LM3S devices with internal ROM bootloader were not handled correctly, so programming of blank devices caused problems. Fixed. Affected devices: LM3S9790, LM3S9792, LM3S9997, LM3S9B90, LM3S9B92, LM3S9B95, LM3S9B96, LM3S9C97, LM3S9D92, LM3S9D95, LM3S9D96, LM3S9L97, LM3S9U81
Version V4.52 (2012-08-03)
Commander
- New command line options added. See manual for more detailed description.
DLL
- Added Freescale MK11DX128xxx5, MK11DX128xxx5 (allow security), MK11DX256xxx5, MK11DX256xxx5 (allow security), MK11DN512xxx5, MK11DN512xxx5 (allow security), MK12DX128xxx5, MK12DX128xxx5 (allow security), MK12DX256xxx5, MK12DX256xxx5 (allow security), MK12DN512xxx5, MK12DN512xxx5 (allow security), MK21DX128xxx5, MK21DX128xxx5 (allow security), MK21DX256xxx5, MK21DX256xxx5 (allow security), MK21DN512xxx5, MK21DN512xxx5 (allow security), MK22DX128xxx5, MK22DX128xxx5 (allow security), MK22DX256xxx5, MK22DX256xxx5 (allow security), MK22DN512xxx5, MK22DN512xxx5 (allow security)
- Added Freescale MKL04Z16xxx4, MKL04Z16xxx4 (allow security), MKL04Z32xxx4, MKL04Z32xxx4 (allow security), MKL05Z16xxx4, MKL05Z16xxx4 (allow security), MKL05Z32xxx4, MKL05Z32xxx4 (allow security), MKL14Z32xxx4, MKL14Z32xxx4 (allow security), MKL14Z64xxx4, MKL14Z64xxx4 (allow security), MKL15Z32xxx4, MKL15Z32xxx4 (allow security), MKL15Z64xxx4, MKL15Z64xxx4 (allow security), MKL15Z128xxx4, MKL15Z128xxx4 (allow security), MKL24Z32xxx4, MKL24Z32xxx4 (allow security), MKL24Z64xxx4, MKL24Z64xxx4 (allow security), MKL25Z32xxx4, MKL25Z32xxx4 (allow security), MKL25Z64xxx4, MKL25Z64xxx4 (allow security), MKL25Z128xxx4, MKL25Z128xxx4 (allow security)
- Added Luminary LM3S5P31
- Added NXP LPC11A02UK, LPC11A04UK, LPC11A11/001
- Added NXP LPC1833, LPC1837, LPC1853, LPC1857
- Added NXP LPC4072, LPC4074, LPC4078, LPC4088
- Added NXP LPC4072, LPC4074, LPC4078, LPC4088
- Added ST STM32F302CB, STM32F302CB (allow opt. bytes), STM32F302CC, STM32F302CC (allow opt. bytes), STM32F302RB, STM32F302RB (allow opt. bytes), STM32F302RC, STM32F302RC (allow opt. bytes), STM32F302VB, STM32F302VB (allow opt. bytes), STM32F302VC, STM32F302VC (allow opt. bytes), STM32F303CB, STM32F303CB (allow opt. bytes), STM32F303CC, STM32F303CC (allow opt. bytes), STM32F303RB, STM32F303RB (allow opt. bytes), STM32F303RC, STM32F303RC (allow opt. bytes), STM32F303VB, STM32F303VB (allow opt. bytes), STM32F303VC, STM32F303VC (allow opt. bytes), STM32F372C8, STM32F372C8 (allow opt. bytes), STM32F372CB, STM32F372CB (allow opt. bytes), STM32F372CC, STM32F372CC (allow opt. bytes), STM32F372R8, STM32F372R8 (allow opt. bytes), STM32F372RB, STM32F372RB (allow opt. bytes), STM32F372RC, STM32F372RC (allow opt. bytes), STM32F372V8, STM32F372V8 (allow opt. bytes), STM32F372VB, STM32F372VB (allow opt. bytes), STM32F372VC, STM32F372VC (allow opt. bytes), STM32F373C8, STM32F373C8 (allow opt. bytes), STM32F373CB, STM32F373CB (allow opt. bytes), STM32F373CC, STM32F373CC (allow opt. bytes), STM32F373R8, STM32F373R8 (allow opt. bytes), STM32F373RB, STM32F373RB (allow opt. bytes), STM32F373RC, STM32F373RC (allow opt. bytes), STM32F373V8, STM32F373V8 (allow opt. bytes), STM32F373VB, STM32F373VB (allow opt. bytes), STM32F373VC, STM32F373VC (allow opt. bytes)
- Debugging speed improved.
- DWT cycle counter register (DWT_CYCCNT) is available/accessible as regular CPU register via the DLL.
- Flash programming speed for some devices improved.
- For STM32F1xx devices under special circumstances the TRACE_IOEN in the DBGMCU_CR was accidentally set. Fixed.
- For TMS470M devices now script file is no longer necessary when the device is selected in the debugger.
- Reset for Atmel AT91SAM3A / AT91SAM3X devices did not reset all peripherals. Fixed.
- Software breakpoints on TMS470M devices did not work properly. Fixed.
- Under special circumstances on some PCs there a "divide by zero" exception could occur. Fixed.
- Under special circumstances, handling of mappable memory (areas which can point to flash or RAM or something else depending on special mapping registers) did not work properly. Fixed.
- Under special circumstances, SWO did not work properly on older J-Link hardware versions (V6, V7). Fixed.
- When using Energy Micro EFM32 J-Link OB, the control panel showed "not connected" in the "J-Link" field of the General tab. Fixed.
- Xilinx Zynq-7020 (Cortex-A9) was not detected properly. Fixed.
Firmware
- Flasher: Custom RAMCodes with > 2 KB size were not handled correctly. Fixed.
- Flasher: Serial number programming feature extended. See manual for extension.
- Flasher: Under special circumstances, custom RAMCode could cause a "RAM check failed" error message when using Flasher ARM in stand-alone mode. Fixed.
- Flasher: When downloading a new config + data file into Flasher via J-Flash, the old configuration was not invalidated properly. Fixed.
- J-Link Lite / Lite Cortex-M: JTAG signal quality improved.
- J-Link: For J-Links with CDC support, under special circumstances it could happen that single characters transmitted from the host PC to the J-Link got lost.
GDB Server
- Command line option "-select" updated. See manual for more detailed description.
- Extended GDB register set for Cortex-M. Added: MSP, PSP, PRIMASK, BASEPRI, FAULTMASK, CONTROL
J-Flash
- Added Eon EN29LV800CB, EN29LV800CT
- Added Freescale MK11DX128xxx5, MK11DX128xxx5 (allow security), MK11DX256xxx5, MK11DX256xxx5 (allow security), MK11DN512xxx5, MK11DN512xxx5 (allow security), MK12DX128xxx5, MK12DX128xxx5 (allow security), MK12DX256xxx5, MK12DX256xxx5 (allow security), MK12DN512xxx5, MK12DN512xxx5 (allow security), MK21DX128xxx5, MK21DX128xxx5 (allow security), MK21DX256xxx5, MK21DX256xxx5 (allow security), MK21DN512xxx5, MK21DN512xxx5 (allow security), MK22DX128xxx5, MK22DX128xxx5 (allow security), MK22DX256xxx5, MK22DX256xxx5 (allow security), MK22DN512xxx5, MK22DN512xxx5 (allow security)
- Added Freescale MKL04Z16xxx4, MKL04Z16xxx4 (allow security), MKL04Z32xxx4, MKL04Z32xxx4 (allow security), MKL05Z16xxx4, MKL05Z16xxx4 (allow security), MKL05Z32xxx4, MKL05Z32xxx4 (allow security), MKL14Z32xxx4, MKL14Z32xxx4 (allow security), MKL14Z64xxx4, MKL14Z64xxx4 (allow security), MKL15Z32xxx4, MKL15Z32xxx4 (allow security), MKL15Z64xxx4, MKL15Z64xxx4 (allow security), MKL15Z128xxx4, MKL15Z128xxx4 (allow security), MKL24Z32xxx4, MKL24Z32xxx4 (allow security), MKL24Z64xxx4, MKL24Z64xxx4 (allow security), MKL25Z32xxx4, MKL25Z32xxx4 (allow security), MKL25Z64xxx4, MKL25Z64xxx4 (allow security), MKL25Z128xxx4, MKL25Z128xxx4 (allow security)
- Added Luminary LM3S5P31
- Added NXP LPC11A02UK, LPC11A04UK, LPC11A11/001
- Added NXP LPC1833, LPC1837, LPC1853, LPC1857
- Added NXP LPC4072, LPC4074, LPC4078, LPC4088
- Added NXP LPC4072, LPC4074, LPC4078, LPC4088
- Added ST STM32F302CB, STM32F302CB (allow opt. bytes), STM32F302CC, STM32F302CC (allow opt. bytes), STM32F302RB, STM32F302RB (allow opt. bytes), STM32F302RC, STM32F302RC (allow opt. bytes), STM32F302VB, STM32F302VB (allow opt. bytes), STM32F302VC, STM32F302VC (allow opt. bytes), STM32F303CB, STM32F303CB (allow opt. bytes), STM32F303CC, STM32F303CC (allow opt. bytes), STM32F303RB, STM32F303RB (allow opt. bytes), STM32F303RC, STM32F303RC (allow opt. bytes), STM32F303VB, STM32F303VB (allow opt. bytes), STM32F303VC, STM32F303VC (allow opt. bytes), STM32F372C8, STM32F372C8 (allow opt. bytes), STM32F372CB, STM32F372CB (allow opt. bytes), STM32F372CC, STM32F372CC (allow opt. bytes), STM32F372R8, STM32F372R8 (allow opt. bytes), STM32F372RB, STM32F372RB (allow opt. bytes), STM32F372RC, STM32F372RC (allow opt. bytes), STM32F372V8, STM32F372V8 (allow opt. bytes), STM32F372VB, STM32F372VB (allow opt. bytes), STM32F372VC, STM32F372VC (allow opt. bytes), STM32F373C8, STM32F373C8 (allow opt. bytes), STM32F373CB, STM32F373CB (allow opt. bytes), STM32F373CC, STM32F373CC (allow opt. bytes), STM32F373R8, STM32F373R8 (allow opt. bytes), STM32F373RB, STM32F373RB (allow opt. bytes), STM32F373RC, STM32F373RC (allow opt. bytes), STM32F373V8, STM32F373V8 (allow opt. bytes), STM32F373VB, STM32F373VB (allow opt. bytes), STM32F373VC, STM32F373VC (allow opt. bytes)
- Added support for serial number programming.
- Custom RAMCodes with > 2 KB size were not handled correctly. Fixed.
- Flash ID for EN29LV800BB was incorrect (0x1C22DA changed to 0x1C225B). Fixed.
- Sample project LPC1788_EmbeddedArtistsDevKit_CFI_1x16.jflash added.
- Sample project LPC1857.jflash added.
- Sample project LPC4088.jflash added.
- Sample project MK20DX128xxx5.jflash added.
- Sample project MK21DN512xxx5.jflash added.
- Sample project MKL25Z128xxx4.jflash added
- Sample project STM32F217ZG.jflash added
- Sample project STM32F303VC.jflash added.
- Sample project STM32F407IG.jflash added
- Sample project STM32L152VB.jflash added
- Sample project STM32L152VB_ProgUserOptionByte.jflash added
- Serial number programming feature extended. See manual for extension.
- When downloading data & configuration to Flasher ARM for stand alone mode, on Flashes where not all sectors have 2KB aligned end addresses (e.g. TMS470R1B1M sector 0) an incorrect data file was produced which caused a programming fail in Flasher stand-alone mode. Fixed.
- When having multiple Flashers connected and J-Flash was not configured to connect to a specific one, when selecting "Download to programmer" the emulator selection dialog popped up twice. Fixed.
- When programming serial numbers, J-Flash reported an error that no serial number list file could be found even in cases where no serial number list file was needed.
J-Link Package
- Installer: CDC driver installer added to regular package. CDC installer is NOT started automatically when installing the software package to avoid compatibility problems with older windows versions.
J-Mem
- Configuration dialog updated. Allows connecting to a J-Link via IP now, allows device selection etc.
SWO Viewer
- Additional button for CPU clock "re-measuring" for known devices added.
- SWO Viewer loads latest settings at startup now.
Version V4.50k (2012-07-02)
DLL
- Reset on LPC1113 devices did not work properly. Fixed.
J-Flash
- "Erase chip" option generated a timeout error on Atmel AT91SAM3U1x and AT91SAM3U2x devices. Fixed.
- Save data file as hex file did not work properly. Fixed.
Version V4.50j (2012-06-26)
DLL
- J-Link Lite FSL: Under special circumstances, reading/writing memory did not work properly. Fixed.
- RX600: If the independent watchdog was running, flash programming could fail with timeout errors. Fixed.
DLL RX
- DLL Updater did not find EWRX V2.40.1 installation. Fixed.
Version V4.50i (2012-06-22)
DLL
- Under special circumstances, SWO did not work properly on older J-Link hardware versions (V6, V7). Fixed.
GDB Server
- For some GDBs it could happen that GDB requested non-existing registers causing "Unsupported register..." messages in the GDB Server. Fixed.
Version V4.50h (2012-06-19)
Commander
- loadbin command did not output syntax in case no parameters were given. Fixed.
- When selecting a device in J-Link Commander via device selection dialog it was no longer possible to select another device again until deleting Default.ini in the JLink.exe folder. Fixed.
DLL
- Improved CFI detection algorithm for SST39 devices which report incorrect CFI information.
- J-Link did not work properly with 64-bit libraries of libusb. Fixed.
- Keil MDK is now recognized by DLL Updater.
- Under special circumstances, control panel did appear in task bar even if started minimized. Fixed.
- Under special circumstances, SWO did not work with older J-Link models (Hardware version 7 and 6). Fixed.
Firmware
- Flasher ARM V3: When programming Cortex-A/R devices in J-Link mode, the "emulator does not have intelligence for the selected CPU core..." dialog popped up. Changed/Fixed.
- Improved stability of J-Link for cases where the SWD interface does not run stable (much noise on SWD lines).
GDB Server
- For some GDBs the error "remote 'g' packet reply is too long" appeared. Fixed.
Version V4.50g (2012-06-11)
J-Flash
- Under special circumstances, RAMCode for LPC11A EEPROM programming did not work properly when reading back EEPROM contents. Fixed.
Version V4.50f (2012-06-08)
Firmware
- J-Link / J-Link Ultra: Under special circumstances, power measurements taken by J-Link Ultra were incorrect. Fixed.
RDI
- Multiple flash downloads in one debug session (e.g. when downloading a second image with AXD without closing the debug session) did not work properly. Fixed.
- Under special circumstances, device selection dialog did not pop up if no device has ever been configured. Fixed.
Version V4.50e (2012-06-06)
DLL
- Under special circumstances, single stepping did not work properly on Cortex-M devices. Fixed.
- Under special circumstances, writing a single debug with a 32-bit write did not work properly. Fixed.
Version V4.50a (2012-06-04)
Commander
- Added explanations for the following commands when typing '?': SWDReadAP, SWDReadDP, SWDWriteAP, SWDWriteDP, SWDSelect
DLL
- "Secure Kinetis device detected" now has a "Do not show this message again" option.
- Added NXP LPC11U34/311, LPC11U34/421, LPC11U35/401, LPC11U35/501, LPC11U36/401, LPC11U37/401, LPC11U37/501
- Added ST STM32F050C4, STM32F050C6, STM32F050K4, STM32F050K6, STM32F051C4, STM32F051K4, STM32F051R4
- Added Toshiba TMPM342FXBG, TMPM365FYXBG
- Out of hardware breakpoints dialog now also shows which breakpoints are currently set.
- single stepping speed on Cortex-M devices improved.
- Support for AM335x added. For more information about special handling for this device, please refer to UM08001, chapter "device specifics"
- Under special circumstances, reset did not work properly. Fixed.
- Unlimited breakpoints in flash memory are now also free for evaluation on J-Link OEM products and J-Link Lite.
- When using older versions of Keil MDK (prior to V4.23) with Cortex-M, under special circumstances the CONTROL register was not written correctly by uVision. Workaround.
Firmware
- J-Link Lite: J-Link Lite stability improvement for targets with much noise on JTAG/SWD signals.
- Flasher ARM: (old revision without ethernet): Under special circumstances, SWD communication did not work correctly. Fixed.
- Flasher ARM: Flash programming for AyDeeKay KamCho devices did not work properly.
- J-Link Pro V1: Under special circumstances, SWD communication did not work correctly. Fixed.
GDB Server
- For some GDBs, under special circumstances, debugging on Cortex-M targets could make problems. Fixed.
J-Flash
- Added NXP LPC11U34/311, LPC11U34/421, LPC11U35/401, LPC11U35/501, LPC11U36/401, LPC11U37/401, LPC11U37/501
- Added ST STM32F050C4, STM32F050C6, STM32F050K4, STM32F050K6, STM32F051C4, STM32F051K4, STM32F051R4
- Added Toshiba TMPM342FXBG, TMPM365FYXBG
RDI
- Debugging on big endian targets did not work properly. Fixed.
SWO Viewer
- utility added.
Version V4.46f (2012-05-10)
DLL
- Added ST STM32F051C4, STM32F051K4, STM32F051R4
- Some device names passed to the DLL by IAR EWARM were not recognized correctly. Fixed.
J-Flash
- Added ST STM32F051C4, STM32F051K4, STM32F051R4
Version V4.46e (2012-05-03)
DLL
- Incorrect data flash size reported for RX621/RX62N/RX62T devices. Fixed.
- Under special circumstances, on Atmel AT91SAM3 & AT91SAM4 devices reset did not work properly. Fixed.
- Under special circumstances, single stepping on Cortex-M devices did not work properly when CPU was in handler mode. Fixed.
- When selecting a AT91SAM9G or SAM9X device in the debugger, for some of them the "Selected device xxx is unknown" dialog popped up. Fixed.
J-Flash
- Incorrect data flash size reported for RX621/RX62N/RX62T devices. Fixed.
Version V4.46d (2012-04-24)
GDB Server
- Under special circumstances, GDB Server could crash when GDB reads a single register
RDI
- Device selection dialog did not show up on start of first debug session. Fixed.
Version V4.46c (2012-04-20)
DLL
- For RX63N targets the message "CPU speed is xxx kHz. JTAG speed reduced to xxx kHz." appeared. Fixed.
- For RX63N targets the message "CPU speed is xxx kHz. JTAG speed reduced to xxx kHz." appeared. Fixed.
- Under special circumstances viewing the DataFlash contents in the memory window of EWRX and HEW did not work properly. Fixed.
Firmware
- Flasher ARM: Programming of Atmel AT91SAM3S devices did not work properly in stand-alone mode. Fixed.
J-Flash
- When programming external flash memory, the device selection dialog popped up accidentally. Fixed.
Version V4.46 (2012-04-12)
DLL
- Added Fujitsu MB9BF116S, MB9BF116T, MB9BF117S, MB9BF117T, MB9BF118S, MB9BF118T, MB9BF216S, MB9BF216T, MB9BF217S, MB9BF217T, MB9BF218S, MB9BF218T, MB9BF316S, MB9BF316T, MB9BF317S, MB9BF317T, MB9BF318S, MB9BF318T, MB9BF412N, MB9BF412R, MB9BF414N, MB9BF414R, MB9BF415N, MB9BF415R, MB9BF416N, MB9BF416R, MB9BF416S, MB9BF416T, MB9BF417S, MB9BF417T, MB9BF418S, MB9BF418T, MB9BF512N, MB9BF512R, MB9BF514N, MB9BF514R, MB9BF515N, MB9BF515R, MB9BF516N, MB9BF516R, MB9BF516S, MB9BF516T, MB9BF517S, MB9BF517T, MB9BF518S, MB9BF518T
- Added Luminary LM3S300, LM3S600, LM3S608, LM3S808, LM3S1F16, LM3S1H11, LM3S2616, LM3S5K36, LM3S5P36, LM3S5T36, LM3S5Y36, LM3S6G65, LM3S9D95, LM3S9D96, LM3S9C97, LM3S9U81
- Added NXP LPC1102, LPC1315, LPC1316, LPC1317, LPC1345, LPC1346, LPC1347, LPC1763, LPC1769, LPC2921, LPC2923, LPC2925, LPC2926, LPC2939
- Added ST STM32L162QD, STM32L162RD, STM32L162VD, STM32L162ZD, STM32W108C8
- Added TI LM4F110B2QR, LM4F110C4QR, LM4F110E5QR, LM4F110H5QR, LM4F111B2QR, LM4F111C4QR, LM4F111E5QR, LM4F111H5QR, LM4F112C4QC, LM4F112E5QC, LM4F112H5QC, LM4F112H5QD, LM4F120B2QR, LM4F120C4QR, LM4F120E5QR, LM4F120H5QR, LM4F121B2QR, LM4F121C4QR, LM4F121E5QR, LM4F121H5QR, LM4F122C4QC, LM4F122E5QC, LM4F122H5QC, LM4F122H5QD, LM4F130C4QR, LM4F130E5QR, LM4F130H5QR, LM4F131C4QR, LM4F131E5QR, LM4F131H5QR, LM4F132C4QC, LM4F132E5QC, LM4F132H5QC, LM4F132H5QD, LM4F210E5QR, LM4F210H5QR, LM4F211E5QR, LM4F211H5QR, LM4F212E5QC, LM4F212H5BB, LM4F212H5QC, LM4F212H5QD, LM4F230E5QR, LM4F230H5QR, LM4F231E5QR, LM4F231H5QR, LM4F232E5QC, LM4F232H5BB, LM4F232H5QC, LM4F232H5QD
- Added Toshiba TMPM367FDFG, TMPM367FDXBG, TMPM368FDFG, TMPM368FDXBG, TMPM369FDXBG, TMPM376FDDFG, TMPM376FDFG, TMPM377FDDFG, TMPM377FDFG, TMPM377FYDFG, TMPM377FYFG, TMPM380FDFG, TMPM384FDFG
- RAWTRACE tab in control panel showed an incorrect trace buffer size. Fixed.
- Under special circumstances, flashing of AyDeeKay uSobek devices could fail with "RAM check failed"
Firmware
- Under special circumstances, flashing of AyDeeKay uSobek devices could fail with "RAM check failed"
GDB Server
- Under special circumstances "C/C++ Application" debug configuration in Eclipse Indigo did not work properly. Fixed.
J-Flash
- Added Fujitsu MB9BF116S, MB9BF116T, MB9BF117S, MB9BF117T, MB9BF118S, MB9BF118T, MB9BF216S, MB9BF216T, MB9BF217S, MB9BF217T, MB9BF218S, MB9BF218T, MB9BF316S, MB9BF316T, MB9BF317S, MB9BF317T, MB9BF318S, MB9BF318T, MB9BF412N, MB9BF412R, MB9BF414N, MB9BF414R, MB9BF415N, MB9BF415R, MB9BF416N, MB9BF416R, MB9BF416S, MB9BF416T, MB9BF417S, MB9BF417T, MB9BF418S, MB9BF418T, MB9BF512N, MB9BF512R, MB9BF514N, MB9BF514R, MB9BF515N, MB9BF515R, MB9BF516N, MB9BF516R, MB9BF516S, MB9BF516T, MB9BF517S, MB9BF517T, MB9BF518S, MB9BF518T
- Added Luminary LM3S300, LM3S600, LM3S608, LM3S808, LM3S1F16, LM3S1H11, LM3S2616, LM3S5K36, LM3S5P36, LM3S5T36, LM3S5Y36, LM3S6G65, LM3S9D95, LM3S9D96, LM3S9C97, LM3S9U81
- Added NXP LPC1102, LPC1315, LPC1316, LPC1317, LPC1345, LPC1346, LPC1347, LPC1763, LPC1769, LPC2921, LPC2923, LPC2925, LPC2926, LPC2939
- Added ST STM32L162QD, STM32L162RD, STM32L162VD, STM32L162ZD, STM32W108C8
- Added TI LM4F110B2QR, LM4F110C4QR, LM4F110E5QR, LM4F110H5QR, LM4F111B2QR, LM4F111C4QR, LM4F111E5QR, LM4F111H5QR, LM4F112C4QC, LM4F112E5QC, LM4F112H5QC, LM4F112H5QD, LM4F120B2QR, LM4F120C4QR, LM4F120E5QR, LM4F120H5QR, LM4F121B2QR, LM4F121C4QR, LM4F121E5QR, LM4F121H5QR, LM4F122C4QC, LM4F122E5QC, LM4F122H5QC, LM4F122H5QD, LM4F130C4QR, LM4F130E5QR, LM4F130H5QR, LM4F131C4QR, LM4F131E5QR, LM4F131H5QR, LM4F132C4QC, LM4F132E5QC, LM4F132H5QC, LM4F132H5QD, LM4F210E5QR, LM4F210H5QR, LM4F211E5QR, LM4F211H5QR, LM4F212E5QC, LM4F212H5BB, LM4F212H5QC, LM4F212H5QD, LM4F230E5QR, LM4F230H5QR, LM4F231E5QR, LM4F231H5QR, LM4F232E5QC, LM4F232H5BB, LM4F232H5QC, LM4F232H5QD
- Added Toshiba TMPM367FDFG, TMPM367FDXBG, TMPM368FDFG, TMPM368FDXBG, TMPM369FDXBG, TMPM376FDDFG, TMPM376FDFG, TMPM377FDDFG, TMPM377FDFG, TMPM377FYDFG, TMPM377FYFG, TMPM380FDFG, TMPM384FDFG
- Sample project LM4F232H5.jflash added.
- Under special circumstances, flashing of AyDeeKay uSobek devices could fail with "RAM check failed"
Version V4.44d (2012-03-26)
DLL
- Added Fujitsu MB9AF131K, MB9AF131L, MB9AF132K, MB9AF131L
- If a unknown device name was passed to the DLL, the device selection dialog popped-up every time a debug session was started. Fixed.
DLL RX
- RX200: J-Link OB could lose communication with core if the speed of HOCO was changed. Fixed.
Firmware
- Flasher PPC/RX: Under special circumstances it could happen that a push of the programming button was not recognized correctly. Fixed.
J-Flash
- Added Fujitsu MB9AF131K, MB9AF131L, MB9AF132K, MB9AF131L
Version V4.44b (2012-03-22)
DLL
- Some LPC11xx devices were not recognized correctly by the DLL when using IAR EWARM. Fixed.
- Under special circumstances flash breakpoints did not work properly on STM32F0 devices. Fixed.
- Under special circumstances single stepping on STM32F0 devices did not work correctly. Fixed.
Version V4.44 (2012-03-19)
DLL
- Connection instabilities to Infineon XMC4500 fixed.
- Some STM32F051 device names where not recognized correctly by the DLL when using IAR EWARM. Fixed.
Version V4.42b (2012-02-14)
DLL
- When switching the target interface multiple times without closing the DLL between the switches (e.g. J-Link Commander), it could happen that the target connection broke down. Fix.
Version V4.42a (2012-02-08)
DLL
- Added ST STM32W108CC, STM32W108CZ
- Normal Reset when using SWD interface did not work properly. Fixed.
- Some device names passed by IAR EWARM were not recognized correctly. Fixed.
- The following device names were not recognized correctly: EFM32GG990F1024, EFM32GG995F1024
J-Flash
- Added ST STM32W108CC, STM32W108CZ
Version V4.42 (2012-02-07)
DLL
- Added Analog Devices ADuC7121, ADuC7122, ADuC7124, ADuC7126
J-Flash
- Added Analog Devices ADuC7121, ADuC7122, ADuC7124, ADuC7126
- Added sample project ADuC7124.jflash
Version V4.40c (2012-01-24)
DLL
- Added Infineon XMC4500
J-Flash
- Added Infineon XMC4500
- Sample project XMC4500.jflash added.
Version V4.36l (2011-12-02)
Commander
- On Cortex-M devices, CONTROL/FAULTMASK/BASEPRI/PRIMASK were not printed correctly. Fixed.
DLL
- Under special circumstances, flash download did not work correctly on TMS570 devices. Fixed.
- Under special circumstances, the ROM table was not checked correctly on CoreSight compliant devices which caused unwanted side effects. Fixed.
J-Flash
- If a project-relative script file path were used in the J-Flash CPU dialog, the path was not passed correctly to the DLL. Fixed.
- It was not allowed to select "big endian" for Renesas RX devices. Fixed.
Version V4.36k (2011-11-22)
DLL
- Flash download & flash breakpoints in external CFI NOR flash memory did not work properly. Fixed.
- Sometimes switching to a specific target interface (JTAG/SWD/...) did not work properly. Fixed.
- The following devices names were not recognized correctly by the DLL when passed selected in IAR EWARM. Fixed: RM48L530PGE, RM48L530ZWT, RM48L540PGE, RM48L540ZWT, RM48L550PGE, RM48L550ZWT, RM48L730PGE, RM48L730ZWT, RM48L740PGE, RM48L740ZWT, RM48L750PGE, RM48L750ZWT, RM48L930PGE, RM48L930ZWT, RM48L940PGE, RM48L940ZWT, RM48L950PGE, RM48L950ZWT, RM48L952PGE, RM48L952ZWT
Version V4.36j (2011-11-18)
DLL
- Flash programming support for Freescale Kinetis K70 did not work correctly. Fixed.
- Script files When having loops in if statements that were not executed under special circumstances, it could happen that the script file parser tried to execute the loops and hang. Fixed.
- Some Freescale devices which are already supported, were not selectable. Fixed.
- Target interface voltages below 1.6V where not handled correctly. Fixed.
GDB Server
- Target interface voltages below 1.6V where not handled correctly. Fixed.
J-Flash
- Flash programming support for Freescale Kinetis K70 did not work correctly. Fixed.
- Some Freescale devices which are already supported, were not selectable. Fixed.
- Target interface voltages below 1.6V where not handled correctly. Fixed.
Version V4.36i (2011-11-11)
Control Panel
- When opening the RAWTRACE tab, under special circumstances an internal error "USB communication not locked" could occur. Fixed.
DLL
- Added Samsung S3FN41F
Firmware
- J-Trace for Cortex-M: If the trace clock was stopped while tracing was active, stopping trace could fail, resulting in the firmware to hang. Fixed.
J-Flash
- Added Samsung S3FN41F
- Chip erase for Samsung S3FN21x and S3FN41F devices added.
- For ST STM32F407IG, STM32F407VG and STM32F407ZG J-Flash reported an incorrect flash size. Fixed.
- J-Flash could crash if external flash memory required "soft unlocking" of flash sectors. Fixed.
- Sample project S3FN41F.jflash added.
- The following external NOR flash devices did not work properly. Fixed: Eon EN29LV800BB, EN29LV800BT, EN29LV160BB, EN29LV160BT
Remote Server
- Some emulator commands were not recognized correctly. Fixed.
Version V4.36h (2011-11-04)
Configurator
- When sorting the J-Link list to a specific column, it could happen that the wrong J-Link get a firmware update if "Update firmware" was executed. Fixed.
J-Flash
- J-Flash could crash when creating Flasher ARM data files if a custom RAMCode / Flash auto-detection setting was used. Fixed.
Version V4.36g (2011-10-27)
Firmware
- Flasher ARM: Under special circumstances, stand-alone mode could crash.
Version V4.36f (2011-10-22)
DLL
- Freescale Kinetis devices were no longer recognized correctly in EWARM, since the naming of the devices has been changed in EWARM V6.30
Version V4.36e (2011-10-20)
DLL
- Under special circumstances it could happen that target RAM was not restored correctly after setting flash breakpoints. Fixed.
Version V4.36d (2011-10-20)
DLL
- Under special circumstances, it could happen that ETB identification on ARM7/9 targets caused problems. Fixed.
Version V4.36c (2011-10-17)
Firmware
- J-Link OB on SAM7 basis: Cortex-M targets: If reading memory failed, under special circumstances the J-Link firmware could hang. Fixed.
Version V4.36b (2011-10-14)
DLL
- SAM-ICE: Support for some new Atmel devices added.
J-Link Script Files
- Did not work properly under special circumstances. Fixed.
Version V4.36a (2011-10-14)
DLL
- exec SetETBIsPresent added.
- exec SetETMIsPresent added.
Version V4.36 (2011-10-13)
DLL
- Added ST STM32F405RG, STM32F405VG, STM32F405ZG, STM32F407IE, STM32F407IG, STM32F407VE, STM32F407VG, STM32F407ZE, STM32F407ZG, STM32F415RG, STM32F415VG, STM32F415ZG, STM32F417IE, STM32F417IG, STM32F417VE, STM32F417VG, STM32F417ZE, STM32F417ZG
- ETB trace on ARM7/9 targets did not work properly. Fixed.
- ETM for ARM7/9 devices needs to be enabled via script file. Auto-detection of ETM on non-ETM devices caused problems on some devices.
DLL RX
- Under special circumstances connecting to RX621 devices could make problems. Fixed.
Firmware
- J-Trace Cortex-M V3: 2-bit and 4-bit trace mode sometimes was not detected correctly on new Cortex-M silicon (Cortex-M3 r2p1, Cortex-M4 r0p1). Fixed.
- J-Trace Cortex-M V3: Sometimes multiple full-sync packets were not filtered correctly by J-Trace. Fixed.
J-Flash
- Added ST STM32F405RG, STM32F405VG, STM32F405ZG, STM32F407IE, STM32F407IG, STM32F407VE, STM32F407VG, STM32F407ZE, STM32F407ZG, STM32F415RG, STM32F415VG, STM32F415ZG, STM32F417IE, STM32F417IG, STM32F417VE, STM32F417VG, STM32F417ZE, STM32F417ZG
Version V4.34b (2011-09-01)
DLL
- Under special circumstances, when flash programming on TMS570 devices, the error message "CPSR has unexpected value" appeared. This error message could also cause a crash of the DLL. Fixed.
Version V4.34a (2011-08-29)
Commander
- Specifying a device name caused an API error.
DLL
- Added: Freescale K10DN32V, K10DN64V, K10DN128V, K10DX32V, K10DX64V, K10DX128V, K20DN32V, K20DX32V, K20DN64V, K20DX64V, K20DN128V, K20DX128V
GDB Server
- Specifying a device name caused an API error.
Version V4.34 (2011-08-26)
DLL
- New device names of STM32L devices in IAR EWARM were not recognized correctly by the DLL. This made it impossible to use the J-Link flashloader out of EWARM. Fixed.
- RX200: Big endian support added
- RX200: On-chip trace support added
- RX600: Trace extraction on data accesses did not work properly. Fixed.
- RX630: Big endian support added
Firmware
- Flasher ARM: Under special circumstances, Flasher ARM could hang when trying to program a device in stand-alone mode.
- RX630: Memory read/write did not work properly on very slow CPU speeds. Fixed Affected firmwares: J-Link OB SAM7, J-Link V8, J-Link Pro V1, J-Link Pro V3, J-Link Ultra
Version V4.28c (2011-07-01)
DLL
- HaltAfterBootloader strategy did not let the complete bootloader run on NXP LPC-CortexM devices. Fixed.
- JTAG auto-speed did not work properly on Samsung S3FN60D (Cortex-M0) devices. Fixed.
Firmware
- J-Link firmware: Problem in ARM11 intelligence, potentially caused instabilities under special circumstances when using ARM11 devices. Fixed.
Version V4.28b (2011-06-22)
DLL
- Added Freescale MK10DN512ZVLK10, MK10DN512ZVLL10, MK10DN512ZVLQ10, MK10DN512ZVMB10, MK10DN512ZVMC10, MK10DN512ZVMD10, MK10DX128ZVLQ10, MK10DX128ZVMD10, MK10DX256ZVLQ10, MK10DX256ZVMD10, MK20DN512ZVMB10, MK20DN512ZVMC10, MK20DN512ZVMD10, MK20DN512ZVLK10, MK20DN512ZVLL10, MK20DN512ZVLQ10, MK20DX128ZVLQ10, MK20DX128ZVMD10, MK20DX256ZVLK10, MK20DX256ZVLL10, MK20DX256ZVLQ10, MK20DX256ZVMB10, MK20DX256ZVMC10, MK20DX256ZVMD10, MK30DN512ZVLK10, MK30DN512ZVLL10, MK30DN512ZVLQ10, MK30DN512ZVMB10, MK30DN512ZVMC10, MK30DN512ZVMD10, MK30DX128ZVLQ10, MK30DX128ZVMD10, MK30DX256ZVLQ10, MK30DX256ZVMD10
- ARM 7/9/11 instruction set: Simulation extended
- ARM11: Reset did not work properly
- ARM11: Single stepping did not work properly under special circumstances
J-Flash
- Added Freescale MK10DN512ZVLK10, MK10DN512ZVLL10, MK10DN512ZVLQ10, MK10DN512ZVMB10, MK10DN512ZVMC10, MK10DN512ZVMD10, MK10DX128ZVLQ10, MK10DX128ZVMD10, MK10DX256ZVLQ10, MK10DX256ZVMD10, MK20DN512ZVMB10, MK20DN512ZVMC10, MK20DN512ZVMD10, MK20DN512ZVLK10, MK20DN512ZVLL10, MK20DN512ZVLQ10, MK20DX128ZVLQ10, MK20DX128ZVMD10, MK20DX256ZVLK10, MK20DX256ZVLL10, MK20DX256ZVLQ10, MK20DX256ZVMB10, MK20DX256ZVMC10, MK20DX256ZVMD10, MK30DN512ZVLK10, MK30DN512ZVLL10, MK30DN512ZVLQ10, MK30DN512ZVMB10, MK30DN512ZVMC10, MK30DN512ZVMD10, MK30DX128ZVLQ10, MK30DX128ZVMD10, MK30DX256ZVLQ10, MK30DX256ZVMD10
- J-Flash could crash when programming a LPC device and adding a valid checksum to the data which was programmed. Fixed.
Version V4.28 (2011-06-16)
DLL
- "CPU Regs" tab of Control Panel did not handle pseudo registers correctly
- Added Freescale MK50DN512ZCLQ10, MK50DX256ZCMC10, MK50DX256ZCLL10, MK50DN512ZCLL10, MK50DX256ZCLK10, MK50DX256ZCMB10, MK51DX256ZCLK10, MK51DX256ZCMB10, MK51DX256ZCLL10, MK51DN512ZCLL10, MK51DX256ZCMC10, MK51DN512ZCMC10, MK51DN256ZCLQ10, MK51DN256ZCMD10, MK51DN512ZCLQ10, MK51DN512ZCMD10, MK52DN512ZCLQ10, MK52DN512ZCMD10, MK53DN512ZCLQ10, MK53DN512ZCMD10, MK53DX256ZCLQ10, MK53DX256ZCMD10
- Added Luminary LM3S308
- SAM-ICE: Did not recognize Atmel AT91SC100 correctly. Fixed.
- Under special circumstances, large Freescale Kinetis devices (> 256 KB flash) could not be programmed. Fixed.
Firmware
- Flasher ARM: Under special circumstances, large Freescale Kinetis devices (> 256 KB flash) could not be programmed. Fixed.
GDB Server
- Start Menu entry for "GDB Server via JTAG" and "GDB Server via SWD" added
J-Flash
- Added Atmel AT49BV040, AT49LV040
- Added Freescale MK50DN512ZCLQ10, MK50DX256ZCMC10, MK50DX256ZCLL10, MK50DN512ZCLL10, MK50DX256ZCLK10, MK50DX256ZCMB10, MK51DX256ZCLK10, MK51DX256ZCMB10, MK51DX256ZCLL10, MK51DN512ZCLL10, MK51DX256ZCMC10, MK51DN512ZCMC10, MK51DN256ZCLQ10, MK51DN256ZCMD10, MK51DN512ZCLQ10, MK51DN512ZCMD10, MK52DN512ZCLQ10, MK52DN512ZCMD10, MK53DN512ZCLQ10, MK53DN512ZCMD10, MK53DX256ZCLQ10, MK53DX256ZCMD10
- Added Luminary LM3S308
- Under special circumstances, large Freescale Kinetis devices (> 256 KB flash) could not be programmed. Fixed.
Remote Server
- Error "Unknown EMU command #229 received." appeared. Fixed.
Version V4.26a (2011-04-28)
DLL
- Freescale Kinetis: Debugger can get stuck when accessing certain illegal addresses.
Firmware
- Freescale Kinetis: Debugger can get stuck when accessing certain illegal addresses.
GDB Server
- Cortex-A/R: Registers were not handled correctly. This caused problems when single stepping / restarting / halting the CPU.
Version V4.24e (2011-03-22)
Firmware
- Flasher ARM: Under special circumstances, SWD in stan-alone mode did not work properly.
Version V4.24c (2011-03-04)
Firmware
- Flasher ARM did not work properly when used via JTAG on Cortex-M devices. Fixed.
- update on J-Link PRO V1 did not work properly in some special circumstances. Fixed.
Version V4.24b (2011-02-22)
DLL
- Cortex-M big-endian: Under special circumstances, when writing data to / reading data from the Private Peripheral Bus area (PPB, always little endian), the data was interpreted as big-endian even though this area is always little endian.
Version V4.24a (2011-02-22)
DLL
- Support for Cortex-M big endian targets added
J-Flash
- Big endian support for Toshiba TMPM341 added.
Version V4.24 (2011-02-17)
Commander
- Under special circumstances the "unlock" command for LM3Sxxx devices caused a "Bad JTAG communication" error and unlock failed.
DLL
- Added NXP LPC11C22, LPC11C24
- Added Samsung S3FN60D
- If no settings file was specified, some values for the control panel were not well-initialized which could lead to unexpected behaviour of the DLL.
- Reprogramming flash memory while software breakpoints were set was not allowed.
- When performing a write & verify to CFI flash memory, the data was correctly written into the flash cache but when reading back, data was read from the hardware instead of the flash cache.
- When selecting LM3SxBxx in IAR EWARM, the device was not correctly selected in the DLL.
- When selecting one of the following devices in IAR EWARM, the DLL did not recognize them correctly: ST STM32F100xC, STM32F100xD, STM32F100xE
GDB Server
- "monitor flash CFI = <SAddr>-<EAddr>" and "monitor WorkRAM = <SAddr>-<EAddr>" did not accept "=" in command.
- "monitor reset <Type>" reported wrong reset description for Cortex-M devices
- 'k' command behaves the same way as 'R' command and issues a reset of the target.
J-Flash
- Added NXP LPC11C22, LPC11C24
- Added Samsung S3FN60D
- MAC7 unlock did not work properly.
- Programming Freescale Kinetis devices did not work properly. "Programming canceled by user" message appeared in log window.
Manual
- All Manuals: Updated.
Version V4.20h (2010-10-05)
DLL
- Script file for TMS570 was written in preliminary, incompatible script file syntax. Has been updated to new syntax.
- State of DBGEN signal was not detected properly on Cortex-R4 devices
Version V4.20g (2010-09-30)
DLL
- When using SWO and using a J-Link with non-built-in intelligence, memory allocation for JTAG sequences failed. The DLL now handles this correctly and sends JTAG sequences in smaller chunks.
Firmware
- J-Link V8: When trying to send a JTAG sequence and allocation of memory failed, J-Link did not send the error code back to the host, which screwed up the USB communication.
Version V4.20f (2010-09-29)
Commander
- "Setpc" command did not work correctly for Cortex-M0/M1/M4. Fixed.
DLL
- Added Freescale MK40X256VMD100
- Added Luminary/TI LMS1751
- Control panel now shows which type of reset has been performed (currently numeric value only)
- Cortex-A8: CP15 accesses did not work properly.
- Cortex-A8: On Cortex-A8 cores read/write memory logic did not work properly (since a "read DSCR in order to update the ready flags" was necessary at some positions)
- Cortex-M4 was not handled correctly in flash programming logic
- CP15 accesses did not work properly on Cortex-A8 devices
- If JLINKARM_RESET_NORMAL was selected and a device was selected too, we did not mapped the reset type correctly to the one which was selected in the device table. Fixed.
- New reset strategy for Freescale Kinetis devices added
- RX: Support for big endian added
- Script file for connecting to Freescale Kinetis devices added (FreescaleKinetis.JLinkScript)
- Script file for OMAP-L138 updated and extension changed from *.c to *.JLinkScript
- Scriptfile ScriptBeagleBoard_OMAP3530.JLinkScript added
- Scriptfile variable JTAG_Speed was write-only. Now it is R/W
- Support for Freescale Kinetis devices added
Firmware
- Cortex-A/R: On Cortex-A8 cores read/write memory logic did not work properly (since a "read DSCR in order to update the ready flags" was necessary at some positions) Affected J-Links: V8, Pro V1, Pro V3, Ultra, OB SAM7
J-Flash
- Added Freescale MK40X256VMD100
- Added Luminary/TI LMS1751
RX DLL Updater
- All compilers are selected to be updated, by default.
Version V4.14 (2010-04-09)
DLL
- Cortex-R4: Single-stepping speed & memory/register read speed improved
- Default.JLinkScriptFile was not set and executed correctly - fixed
- TMPM380FxFG (device description passed to DLL by IAR EWARM) was recognized as "unknown" device - fixed
- Under special circumstances and if no device info was passed to J-Link, software breakpoints on Cortex-M3 did not work properly - fixed
J-Flash
- Auto JTAG-detection improved.
Version V4.10e (2009-12-11)
Version V4.08a (2009-06-29)
DLL
- Full support for watchpoints on Cortex-M3.
- Log file can be configured via J-Link control panel.
J-Flash
- Support for some new MCUs: NXP LPC1311, NXP LPC1313
Version V4.06b (2009-06-12)
DLL
- DLL may cause a crash on PID change when using with SWD interface. Fixed.
Version V3.96d (2008-11-21)
DLL
- SWD performance improved.
Version V3.96c (2008-11-20)
DLL
- SWD communication did not work properly. Fixed.
Version V3.96b (2008-11-12)
Firmware
- Flasher ARM handshake control did not work properly. Fixed.
Version V3.96a (2008-11-05)
DLL
- Instruction set emulation did not work properly. Fixed.
- Performance of memory accesses with Cortex-M3 cores via SWD improved.
Firmware
- Flasher ARM: Flasher ARM supports ASCII protocol for remote communication.
J-Flash
- Support for some new flash devices: Eon EN29LV800BT
Version V3.92a (2008-10-06)
DLL
- Reset with Cortex-M3 did not work properly. Fixed.
- TCP/IP communication did not work properly. Fixed.
Version V3.90d (2008-09-01)
DLL
- Reset with SWD did not work properly. Fixed.
Version V3.90c (2008-08-25)
DLL
- JLINKARM_SPEED_INFO structure was not initialized during flash programming. Fixed.
RDI
- JLINKARM_SPEED_INFO structure was not initialized during flash programming. Fixed.
Version V3.90b (2008-08-21)
J-Flash
- Target CPU was not halted automatically. Fixed.
Version V3.80c (2008-04-09)
DLL
- Write register did not work properly on CM3 devices. Fixed.
Version V3.80b (2008-04-08)
DLL
- FlashBP and FlashDL license for LPC2xxx devices did not work properly. Fixed.
Version V3.78d (2008-01-16)
DLL
- Read/write memory with slow speed (<30kHz) did not work properly. Fixed.
RDI
- Path of JLinkRDI.ini file was changed in accident. Fixed.
Version V3.78a (2007-12-04)
DLL
- Adaptive clocking did not work properly. Fixed.
- Cortex-M3 with SWD did not work properly. Fixed.
- Disassembly cache added to improve performance.
- Instruction set simulation did not work properly. Fixed.
- New reset type (JLINKARM_CM3_RESET_TYPE_CORE) for Cortex-M3.
- Single stepping on Cortex-M3 devices did not work properly. Fixed.
- Support for ARM11 devices added.
- Support for Cortex-M1 devices added.
J-Flash
- Auto detection of JTAG scan chain configuration.
- Flash programming speed for blank Infineon XMC4xxx devices improved.
- Programming of second flash bank of ST STR91x devices.
- Support for ADuC7060 devices.
- Support for Cortex-M3 devices: Luminary LM3S series ST STM32 series
- Support for custom RAMCode.
- Support for some new flash devices: Spansion S29WS064J, Spansion S29WS128J, Spansion S29WS128N, Spansion S29WS256N
RDI
- Adaptive clocking with NXP devices did not work properly. Fixed.
- Option to execute macro file after every reset.
- Performance of flash programming improved.
- Single stepping did not work properly. Fixed.
- Support for ADuC7060 devices.
- Support for some new ST devices: ST STR911FW32, ST STR911FW44, ST STR912FW32, ST STR912FW44
Version V3.74f (2007-08-10)
RDI
- GHS debugger with big endian targets did not work properly. Fixed.
Version V3.74e (2007-08-09)
DLL
- Breakpoint handling did not work properly. Fixed.
- Support for Atmel AT91CAP9 and AT91SAM9RL64 added.
J-Flash
- Support for some new flash devices: Spansion S29GL032AxRx, Spansion S29GL032AxWx
Version V3.74d (2007-07-27)
J-Flash
- Open *.bin files from commandline did not work properly. Fixed.
- Support for some new flash devices: Macronix MX29LV160C, Macronix MX29LV400C, Macronix MX29LV800C, Spansion S29WS064J, Spansion S29WS128J, Spansion S29WS128N, Spansion S29WS256N
Version V3.74c (2007-07-16)
J-Flash
- Installer can detect any installed IAR EWARM and update the JLinkARM.dll.
Version V3.60a (2007-02-09)
DLL
- Automatically CPU clock frequency detection also works with J-Link-OC-LPC.
- Better performance on memory write/read with adaptive clocking.
- Instructions may be emulated if they can not be simulated.
- Read/Write memory on Cortex-M3 did not work properly. Fixed.
J-Flash
- Actions performed on "Auto" command can be configured.
- Data window allows to edit items in gap areas.
- New menu entry "File|Merge..." allows merging of data files.
- Verifying CRC of target instead of read back entire program.
RDI
- Always detect CPU clock frequency automatically.
- Option to skip flash download on CRC match.
- Reading GPIOs on NXP LPC214x and LPC23xx devices did not work properly. Fixed.
- Simulate/emulate some instructions on "go" to avoid flash programming.
- Tracing did not work properly. Fixed.
Version V3.58c (2007-01-12)
DLL
- Certified J-Link USB driver.
Version V3.58b (2007-01-12)
DLL
- USB driver with J-Link Rev 3/4 did not work properly. Fixed.
Version V3.58a (2006-12-22)
DLL
- CPU clock frequency detection also works with adaptive clocking.
J-Flash
- Old reset commands of CPU init sequence did not work. Fixed.
Version V3.56i (2006-12-14)
RDI
- Old style reset commands in "*.setup" files did not work. Fixed.
Version V3.56e (2006-12-07)
DLL
- Auto detection of scan chain configuration changed.
- Support for J-Link CE.
RDI
- Semi-hosting SYS_WRITE did not allow large files. Fixed.
Version V3.56b (2006-12-01)
DLL
- Allow higher voltage range up to 3.6 volts for older J-Links.
- Feed watchdog for TI TMS470 devices.
Version V3.56a (2006-11-30)
DLL
- Instruction set simulation did not work properly. Fixed.
- Reset behavior for reset strategy BP@0 improved.
- Reset on J-Link-OC-LPC did not work properly. Fixed.
J-Flash
- Auto unlock flash sectors during programming for Intel flashes and STR7 devices.
- Automatically correction of PLL settings for TI TMS470 series.
- Identification of flash devices by flash ID look up.
- J-Flash commandline did not work properly. Fixed.
- RAM check with auto RAM size detection.
- Support for new flash device Spansion S29AL032D
- Support for some new NXP devices: NXP (Philips) LPC2364, NXP (Philips) LPC2366, NXP (Philips) LPC2368, NXP (Philips) LPC2378
RDI
- Auto unlock flash sectors for STR7 devices.
- Automatically correction of PLL settings for TI TMS470 series.
- Flash download did not work properly. Fixed.
- Support for some new NXP devices: NXP (Philips) LPC2364, NXP (Philips) LPC2366, NXP (Philips) LPC2368, NXP (Philips) LPC2378
- Tool to display RDI configuration dialog.
Version V3.52a (2006-11-16)
J-Flash
- New feature: Automatic CPU clock frequency detection.
Version V3.46a (2006-09-29)
DLL
- Reset handling improved.
- Set speed on J-Link-OC-LPC improved.
J-Flash
- Added new MCU devices: ST STR735F, ST STR736F
RDI
- Added new MCU devices: ST STR735F, ST STR736F
- Added support for new MCU ST STR750F
- Added support for new MCU ST STR751F
- Added support for new MCU ST STR752F
- Added support for new MCU ST STR755F
- Checkbox for verify download added.
- Endian select button added.
Version V3.44a (2006-09-21)
J-Flash
- Added new flash device Atmel AT49BV160D
- Added new flash device Atmel AT49BV320D
- Added new flash device Atmel AT49BV322D
- Added new flash device Atmel AT49BV640D
- Added new flash device Atmel AT49BV642D
- Added new MCU device ST STR750F
- Added new MCU device ST STR751F
- Added new MCU device ST STR752F
- Added new MCU device ST STR755F
Version V3.42b (2006-09-13)
DLL
- Improved performance of verify data.
J-Flash
- Improved performance of verify data.
Version V3.42a (2006-09-12)
DLL
- Improved general performance of J-Link.
- JLINKARM_ReadMemU16() does not work properly. Fixed.
J-Flash
- Added new flash device ST M28W320FC
- Added new flash device ST M28W320FS
- Added new flash device ST M28W640EC
- Added new flash device ST M28W640FC
- Added new flash device ST M28W640FS
- Data files are displayed in target endianness.
- General speed improvement.
- J-Flash crashes sometimes when closing a data window. Fixed.
Version V3.40a (2006-08-21)
DLL
- PC has incorrect value after halt using DBGRQ. Fixed.
J-Flash
- Added new flash deviceAtmel AT49BV163D
- Added new flash deviceSpansion S29AL016D
Version V3.38a (2006-08-16)
J-Flash
- Added new MCU device Philips SJA2010
- Added new MCU device Philips SJA2510
Version V3.36a (2006-08-01)
DLL
- Flash DLL support for some new MCU devices.
J-Flash
- Added new MCU devices: Philips LPC2101, Philips LPC2102, Philips LPC2103, TI TMS470R1B512, TI TMS470R1B768, TI TMS470R1B1M
RDI
- Added new MCU devices: Philips LPC2101, Philips LPC2102, Philips LPC2103, TI TMS470R1B512, TI TMS470R1B768, TI TMS470R1B1M
- Added support for new MCUs: TI TMS470R1A64, TI TMS470R1A128, TI TMS470R1A256, TI TMS470R1A288, TI TMS470R1A384, TI TMS470R1VF288, TI TMS470R1VF688, TI TMS470R1VF689
Version V3.32a (2006-07-24)
J-Flash
- Support for unsecuring MAC71xx devices added.
Version V3.30k (2006-07-07)
DLL
- ARM7/9 bug single stepping mov rx, # if condition was not met. Fixed.
Version V3.30d (2006-06-23)
DLL
- ARM7 bug single stepping BX PC. Fixed.
- ARM7 bug single stepping SUB SP, #immed_7. Fixed.
Version V3.30c (2006-06-22)
DLL
- CM3 write bug. Fixed.
Version V3.30b (2006-06-21)
DLL
- ADI software reset sequence did not work properly. Fixed.
- Support for CM3 rev.1 silicon (different Ids).
RDI
- RDI Semihosting: File size was not returned correctly. Fixed.
Version V3.30a (2006-06-19)
J-Flash
- Added new MCU devices: OKI ML67Q4050, OKI ML67Q4051, OKI ML67Q4060, OKI ML67Q4061
- Improved performance since new DLL is used.
RDI
- Added new MCU devices: OKI ML67Q4050, OKI ML67Q4051, OKI ML67Q4060, OKI ML67Q4061
Version V3.24a (2006-05-31)
DLL
- Download speed for ARM9 cores improved.
- General speed improvements.
- Instruction set simulation improved.
J-Flash
- Added new flash device AMD Am29SL800D
- Added new flash device Sharp LH28F128SPHTD
- Added new flash device SST SST39VF6401B
- Added new flash device SST SST39VF6402B
- Improved performance since new DLL is used.
RDI
- Improved performance since new DLL is used.
Version V3.20a (2006-04-27)
DLL
- Improved auto speed recognition.
- Minor improvements.
- Support for Cortex M3 devices added.
J-Flash
- Added new flash device Intel 28F004B3
- Added new flash device Intel 28F008B3
- Added new flash device Intel 28F016B3
- Added new flash device Intel 28F160B3
- Added new flash device Intel 28F320B3
- Added new flash device Intel 28F400B3
- Added new flash device Intel 28F640B3
- Added new flash device Intel 28F800B3
- Added new flash device SST SST39VF160
- Added new flash device SST SST39VF320
- Added new flash device SST SST39VF640
- Added new flash device ST M29W400D
- Added support for CFI compliant flash devices.
- Added support for securing / unsecuring flash memory.
- Improved auto speed recognition.
- New commands available for CPU init sequence.
RDI
- Added support for new MCU Atmel AT91SAM7A3
- Added support for new MCU Atmel AT91SAM7S321
- Added support for new MCU ST STR715FR0
- Added support for new MCU ST STR730FZ1
- Added support for new MCU ST STR730FZ2
- Added support for new MCU ST STR731FV0
- Added support for new MCU ST STR731FV1
- Added support for new MCU ST STR731FV2
- Added switch to enable flash mirror area @ address 0.
- Improved auto speed recognition.
Version V3.14a (2006-03-14)
DLL
- Breakpoint handling improved.
- Minor improvements.
J-Flash
- Improved handling of AT91SAM7A3.
- Watchdog refresh for ADuC703x devices.
RDI
- Breakpoint handling improved.
- Flash programming for AT91SAM7A3 did not work properly. Fixed.
- Minor improvements.
- Semihosting handling improved.
- Vector catch handling improved.
- Watchdog refresh for ADuC703x devices.
Version V3.12f (2006-03-10)
DLL
- Some settings were overwritten. Fixed.
Version V3.12b (2006-02-24)
RDI
- DLL with ARM RVDS did not work properly. Fixed.
Version V3.12a (2006-02-23)
DLL
- Improved breakpoint handling.
J-Flash
- Added new flash device Spansion S29GL032M
- Added new flash device Spansion S29GL064M
- Added new flash device Spansion S29GL128M
- Added new flash device Spansion S29GL256M
- Minor improvements.
RDI
- Added vector catch for ARM7 / ARM9 devices
- Improved breakpoint handling.
- Improved breakpoint handling.
Version V3.10e (2006-02-21)
DLL
- Improved JTAG handling.
- Improved memory access.
J-Flash
- Improved JTAG handling.
- Improved memory access.
RDI
- Improved JTAG handling.
- Improved memory access.
Version V3.10c (2006-02-10)
DLL
- Improved support for J-Link-OC-LPC.
- New reset strategies added.
J-Flash
- Allow to connect via USB to J-Link devices 0 to 3.
RDI
- Allow to connect via USB to J-Link devices 0 to 3.
- New reset strategies added.
Version V3.10b (2006-02-09)
DLL
- Improved reset behavior.
J-Flash
- Minor improvements.
RDI
- Minor improvements.
Version V3.10a (2006-02-08)
DLL
- Improved reset behavior.
- Support for J-Link-OC-LPC added.
- Support for J-Trace added.
J-Flash
- Added new flash device Spansion S29GL128N
- Added new flash device Spansion S29GL256N
- Added new flash device Spansion S29GL512N
- Calculate CRC when opening data files.
Version V3.00h (2006-02-02)
DLL
- Improved handling of 16-bit and 32-bit read operations.
J-Flash
- Minor improvements.
RDI
- Allow configuration of reset delay.
- Improved RDI logfile.
Version V3.00d (2006-01-13)
DLL
- Some performance improvements.
J-Flash
- Added new flash device AMD S71PL032J
- Added new flash device AMD S71PL064J
- Added new flash device AMD S71PL127J
- Added new flash device Intel 28F128P30B
- Added new flash device Intel 28F128P30T
- Added new flash device Intel 28F256P30B
- Added new flash device Intel 28F256P30T
- Added new flash device Intel 28F640P30B
- Added new flash device Intel 28F640P30T
- Added new MCU device ST STR730FZ1
- Added new MCU device ST STR730FZ2
- Added new MCU device ST STR731FV0
- Added new MCU device ST STR731FV1
- Added new MCU device ST STR731FV2
- Added new MCU device ST STR911FM32x
- Added new MCU device ST STR911FM44x
- Added new MCU device ST STR912FM32x
- Added new MCU device ST STR912FM44x
- Download performance improved.
RDI
- Some performance improvements.
- Support for new ST MCU ST STR911FM32x
- Support for new ST MCU ST STR911FM44x
- Support for new ST MCU ST STR912FM32x
- Support for new ST MCU ST STR912FM44x