Release notes for the J-Link Software and Documentation Package

Version V8.10h (2024-11-20)

Highlights:

Device Support

1. ST STM32C051: Added debug and flash programming support (https://wiki.segger.com/ST_STM32C0).
2. ST STM32WL33: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WL3x).
3. Trident T32CM11: Added debug and flash programming support (https://wiki.segger.com/Trident_T32CM11).
4. Trident T32CZ20: Added debug and flash programming support (https://wiki.segger.com/Trident_T32CZ20).
5. Qorvo QPG6200L: Added debug and flash programming support (https://wiki.segger.com/Qorvo_QPG6200L).

Other changes:

Commander

1. Command "IsHalted" did not print 64-bit addresses properly. Fixed.
2. Command "StepOver" did not print 64-bit addresses properly. Fixed.
3. Command "StepOver" did not work properly for 64-bit addresses. Fixed.
4. Command "Disassemble" did not accept 64-bit addreses as input parameters. Fixed.

DLL

1. BPs set on 64-bit addresses were only hit once. Fixed.
2. RISC-V: JLINK_GetMOEs() did not work properly if core was halted on a code breakpoint in 64-bit address space. Fixed.
3. ST STM32WB0x: Flash programming could fail in case of IWDT was enabled. Fixed.

Device Provisioner

1. ST STM32U5 series: UnlockDevice operation when performing regression RDP1->RDP0, now resets UNLOCK bit in all WRPx registers to 1.
2. ST STM32U5 series: Added GetAuthId operation to display device authentication ID stored in DBGMCU_DBG_AUTH_DEVICE register.

Device Support

1. NXP MCXA18: Reset did not halt at application after reset, but in BOOT ROM. Fixed.
2. NXP MCXA10: Reset did not halt at application after reset, but in BOOT ROM. Fixed.

Firmware

1. 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.
2. 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.
3. Flasher Hub-12 V1: Added support for NTP (https://wiki.segger.com/Flasher_Hub_-_Configuration#System_time).
4. Flasher Hub-4 V1: Added support for NTP (https://wiki.segger.com/Flasher_Hub_-_Configuration#System_time).

Trace

1. 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

1. Qualcomm QCC711: Added debug and flash programming support (https://wiki.segger.com/Qualcomm_QCC711).
2. ST SR6G6xx: Added debug and flash programming support (https://wiki.segger.com/ST_SR6G6).

Trace

1. Published out-of-the-box trace example for TI AM3517: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Published out-of-the-box trace example for TI AM3359: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

DLL

1. Coresight TMC detection incorrect, under certain circumstances ETB was detected. Fixed.
2. 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.

Device Support

1. NXP S32K3xx: Added support for attaching to a running target using the "ForceAttachTarget" command string (https://wiki.segger.com/NXP_S32K3xx#ECC_RAM).

Firmware

1. Flasher Hub-12 V1: WebIF: When opening a tab, the page contents would sometimes take a few [ms] to show. Fixed.
2. Flasher Hub-4 V1: WebIF: When opening a tab, the page contents would sometimes take a few [ms] to show. Fixed.
3. Flasher Hub-12 V1: WebIF: Dashboard: Added LED to "Last program result" in "General information" table.
4. Flasher Hub-4 V1: WebIF: Dashboard: Added LED to "Last program result" in "General information" table.
5. Flasher Hub-12 V1: WebIF: Improved display of links to documentation.
6. Flasher Hub-4 V1: WebIF: Improved display of links to documentation.
7. Flasher Hub-12 V1: WebIF: Changed default for new configurations from "Administrator" to "Operator" mode.
8. Flasher Hub-4 V1: WebIF: Changed default for new configurations from "Administrator" to "Operator" mode.
9. Flasher ARM V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
10. Flasher ARM V5-1: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
11. Flasher ARM V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
12. Flasher PRO V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
13. Flasher PRO V5-1: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
14. Flasher PRO V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
15. Flasher PRO XL V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
16. Flasher PRO XL V5-1: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
17. Flasher PRO XL V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
18. Flasher Compact V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
19. Flasher Compact V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
20. Flasher Portable PLUS V5: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.
21. Flasher Portable PLUS V6: Under certain circumstances standalone programming would fail. Introduced with V8.10e. Fixed.

J-Flash

1. The application crashed when downloading data and config to Flasher on macOS. Introduced with V7.98a. Fixed.

J-Scope

1. Added option to disable auto scale Y-Resolution.
2. Added editing of the Y-Resolution column.
3. Added Measurement lines to show Time and Value differences.
4. J-Scope could crash when filtering for a variable. Introduced with V8.10e. Fixed.

Trace

1. Implemented native buffer trace support for TI AM3517.
2. Implemented native buffer trace support for TI AM3359.

Version V8.10f (2024-11-06)

Highlights:

Device Support

1. Nordic Semiconductor nRF54L15: Added debug and flash programming support for Cortex-M33 core (https://wiki.segger.com/Nordic_Semiconductor_nRF54Lxx).
2. Microchip PIC32CX BZ3: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32CX_BZ3).
3. ST STM32WB06: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB0).
4. ST STM32WB1MMC: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB).
5. ST STM32WL5MOC: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WL).
6. ST STM32WBA50: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WBA).
7. ST STM32WBA54: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WBA).

Other changes:

DLL

1. The CPSR.V flag could get set wrong in certain cases when using the asm CMP function. Fixed.

Device Support

1. NXP S32K3xx: Added support for password authentication (https://wiki.segger.com/NXP_S32K3xx).

Version V8.10e (2024-10-30)

Highlights:

Device Support

1. TI CC2340R53: Added debug and flash programming support (https://wiki.segger.com/TI_CC2340).

Trace

1. Published out-of-the-box trace example for NXP S32K388: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Published out-of-the-box trace example for Altera Arria10: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

Control Panel

1. RTT Tab: Event log would not log events happening before opening the Control Panel. Fixed.

DLL

1. 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.
2. Logging of internal CPU_ReadMem() and CPU_WriteMem() calls did cut of the address at 32-bit in the log output. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.

J-Scope

1. Under certain circumstances triggering on a symbol value change did not work. Fixed.
2. J-Scope could crash when using an ELF file containing large arrays (more than 10,000 elements). Fixed.

RTT Viewer

1. Configuration Dialog: Added link to SEGGER Wiki explaining the "Auto Detection" option.

Trace

1. ST SR5E1 pin tracing did not work for Core 1. Fixed.
2. Implemented native buffer trace support for Altera Arria10.

Version V8.10d (2024-10-24)

Highlights:

DLL

1. Added general support for Renesas RX260 core.
2. Added general support for Renesas RX261 core.

Device Provisioner

1. 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

1. Added debug + flash programming support for Renesas RX260 series devices (R5F52606, R5F52607, R5F52608).
2. Added debug + flash programming support for Renesas RX261 series devices (R5F52616, R5F52617, R5F52618).
3. ST STM32WB07: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB0).
4. Renesas RA8E1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8E1).

Other changes:

Commander

1. FLIST command output could get cut off if there were too many files on the Flasher. Fixed.

Control Panel

1. While the "General" tab was open, the log was getting spammed with JLINK_EMU_FILE_GetVolumeInfo() calls. Fixed.
2. When loading the "General" tab for the first time, there was a delay in displaying some of the information. Fixed.

DLL

1. Under special circumstances, the 32-bit J-Link DLL could crash during trace. Fixed.

Device Support

1. ST STM32G4 CAT2 devices: Option bytes programming could fail for last option byte (SEC1R). Fixed.
2. ST STM32U5 device series: Under certain circumstances internal flash programming could fail. Fixed.
3. Analog ADuCM360/ADuCM361: Under certain circumstances standalone flash programming could fail. Fixed.
4. ST STM32G0 device series: Option bytes programming always programmed reserved areas with zeroes regardless of the actual data value. Fixed.
5. NXP LPC54xx: Auto detection of the RTT block did not work properly. Fixed.
6. NXP Kinetis V: Auto detection of the RTT block did not work properly. Fixed.
7. NXP NCJ29D5: RTT auto detection range extended whole non-secure RAM.
8. Aliased addresses for boot sectors did not work on PIC32MK devices. Fixed.
9. When programming config bits on PIC32MK devices, verification did not work correctly in some cases. Fixed.
10. AlifSemi E1/E3/E5/E7 device series: QSPI flash programming for more than 16 MB did not work. Fixed.
11. NXP iMXRT117x: Under certain circumstances external flash programming verify could fail. Fixed.
12. ST STM32H74xx/STM32H75xx: Added QSPI flash programming support for pin config CLK@PF10_nCS@PG6_D0@PF8_D1@PF9_D2@PF7_D3@PF6.

Firmware

1. Flasher ARM V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
2. Flasher ARM V5-1: The target power could be falsely deactivated when using successive batch projects. Fixed.
3. Flasher ARM V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
4. Flasher PRO V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
5. Flasher PRO V5-1: The target power could be falsely deactivated when using successive batch projects. Fixed.
6. Flasher PRO V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
7. Flasher PRO XL V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
8. Flasher PRO XL V5-1: The target power could be falsely deactivated when using successive batch projects. Fixed.
9. Flasher PRO XL V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
10. Flasher Compact V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
11. Flasher Compact V6: The target power could be falsely deactivated when using successive batch projects. Fixed.
12. Flasher Portable PLUS V5: The target power could be falsely deactivated when using successive batch projects. Fixed.
13. Flasher Portable PLUS V6: The target power could be falsely deactivated when using successive batch projects. Fixed.

GDB Server

1. embOS plugin: GDB Server could crash when used with the embOS plugin. Fixed.
2. Debugging devices in JTAG Daisy chain with default settings not worked. Fixed.

J-Flash

1. Some sample projects (e.g. AT91RM9200_EK.jflash) could not be loaded. Fixed.

Version V8.10c (2024-10-16)

Highlights:

Device Support

1. RaspberryPi RP2350: Added debug and QSPI flash programming support (https://wiki.segger.com/Raspberry_Pi_RP2350).
2. ST STM32C071: Added debug and flash programming support (https://wiki.segger.com/ST_STM32C0).
3. Added device support for Microchip dsPIC33CKxxxMPxxx family.
4. TI MSPM0Gx51x: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0G).

Other changes:

DLL

1. RISC-V RV64: Single stepping in 64-bit address space could cause a "failed to read current instruction" error. Fixed.
2. 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.

Device Support

1. NXP K32/KW45/MCXW: Under certain circumstances flash operations failed. Fixed.
2. NXP S32M241: Flash programming could fail due to incorrect sector size. Fixed.
3. NXP S32M242: Flash programming could fail due to incorrect sector size. Fixed.
4. NXP S32M243: Flash programming could fail due to incorrect sector size. Fixed.
5. NXP S32M24x: Added support for the native block erase command.

Firmware

1. Flasher ARM V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
2. Flasher ARM V5-1: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
3. Flasher ARM V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
4. Flasher PRO V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
5. Flasher PRO V5-1: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
6. Flasher PRO V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
7. Flasher PRO XL V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
8. Flasher PRO XL V5-1: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
9. Flasher PRO XL V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
10. Flasher Compact V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
11. Flasher Compact V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
12. Flasher Portable PLUS V5: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
13. Flasher Portable PLUS V6: PC-based programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
14. J-Link ULTRA+ V5: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
15. J-Link ULTRA+ V5-1: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
16. J-Link ULTRA+ V6: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
17. J-Link PRO V5: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
18. J-Link PRO V5-1: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
19. J-Link PRO V6: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.
20. J-Link PRO PoE V6: Programming of SPI flashes via J-Flash SPI did not work. Introduced in V7.98i. Fixed.

J-Run

1. Application exit value print incorrect. Fixed.
2. Application exit wildcard parsing not robust for intermixed strings. Fixed.
3. Improved output and logging (RTT wildcard commands visible in output, logging format unified).

J-Scope

1. 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

1. Microchip SAMA7G54: Added device support for SAMA7G54D4G.

Trace

1. 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

1. Some message boxes (e.g. unlock dialogs) were shown although "-NoGui" option was active. Fixed.

DLL

1. Pressing the close button in the unsecure device dialog counted as pressing "Yes", while it should count as "No". Fixed.
2. Windows: Under very special circumstances, randomly named (temp) file was accidentally created in current working directory. Fixed.

Device Support

1. Renesas RA4E1, RA4L1, RA4M2, RA4M3, RA4T1 device series: No reset via reset pin was performed if confused core is detected. Fixed.
2. Renesas RA6E1, RA6M4, RA6M5, RA6T2 device series: No reset via reset pin was performed if confused core is detected. Fixed.
3. Renesas RA8D1, RA8M1, RA8T1 device series: No reset via reset pin was performed if confused core is detected. Fixed.
4. AmbiqMicro Apollo5: Reset sequence did not work properly. Fixed.
5. Infineon PSoC 4 HV: Added debug and flash programming support (https://wiki.segger.com/Infineon_PSoC_4_HV).
6. NXP MCXN10: Reset did not work when booting from FLEXSPI. Fixed.
7. NXP MCXN10: Initialization of FLEXSPI did not work when booting from FLEXSPI. Fixed.
8. TI CC1311R3: Added debug and flash programming support.

Firmware

1. 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)
2. 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)
3. 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)
4. 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)
5. 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)
6. 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)
7. 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)
8. 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)
9. 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)
10. 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

1. Windows: Under very special circumstances, randomly named (temp) file was accidentally created in current working directory. Fixed.

J-Flash

1. Windows: Under very special circumstances, randomly named (temp) file was accidentally created in current working directory. Fixed.

J-Flash SPI

1. Windows: Under very special circumstances, randomly named (temp) file was accidentally created in current working directory. Fixed.

Trace

1. Fixed native trace support for Infineon XMC7000 series.

Version V8.10a (2024-10-02)

Highlights:

Device Support

1. NXP NCJ29D5: Added flash programming support for DSP Firmware(https://wiki.segger.com/NXP_NCJ29D5).
2. NXP OL23D0: Added debug and flash programming support(https://wiki.segger.com/NXP_OL23D0).
3. TI CC2651R3: Added debug & flash programming support (https://wiki.segger.com/TI_CC26xx).
4. TI CC2651P3: Added debug & flash programming support (https://wiki.segger.com/TI_CC26xx).

Trace

1. Published out-of-the-box trace examples for NXP MCXN947: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Published out-of-the-box trace example for NXP iMX6ULL: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

Commander

1. "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.

DLL

1. J-Link would show the wrong reset type when setting through J-Link script file. Fixed.
2. Log file output for memory accesses in 64-bit address space did not log target address properly (address was cut to 32-bit). Fixed.
3. Memory accesses (R/W) beyond the 32-bit address space did not work properly and returned data for 32-bit cut address. Fixed.
4. J-Link script files: Added JLINK_FILE_GetSize() API function call. (See https://wiki.segger.com/J-Link_script_files#JLINK_FILE_GetSize())
5. Cadence Xtensa: Added support for HiFi 5 core.

Device Support

1. NXP NCJ29D5: WorkRAM size adjusted to 6KB because of DSP Firmware update requirements.
2. Renesas RA4E1, RA4L1, RA4M2, RA4M3, RA4T1 device series: Under certain circumstances target could lock up when resetting via reset pin and disconnecting afterwards. Fixed.
3. Renesas RA6E1, RA6M4, RA6M5, RA6T2 device series: Under certain circumstances target could lock up when resetting via reset pin and disconnecting afterwards. Fixed.
4. Renesas RA8D1, RA8M1, RA8T1 device series: Under certain circumstances target could lock up when resetting via reset pin and disconnecting afterwards. Fixed.
5. NXP iMXRT117x: Flash verification failed when using MCUExpresso SDK 2.16 on MIMXRT1170-EVK (using SPI NOR flash ISSI IS25WP128). Fixed.

Firmware

1. 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.
2. J-Link EDU Mini V1: Rebuilt firmware with ARMv8-A/R module version 14.
3. J-Link EDU Mini V2: Rebuilt firmware with ARMv8-A/R module version 14.
4. J-Link EDU/BASE/PLUS V11: Rebuilt firmware with ARMv8-A/R module version 14.
5. J-Link EDU/BASE/PLUS V12: Rebuilt firmware with ARMv8-A/R module version 14.
6. J-Link ULTRA+ V5: Rebuilt firmware with ARMv8-A/R module version 14.
7. J-Link ULTRA+ V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
8. J-Link ULTRA+ V6: Rebuilt firmware with ARMv8-A/R module version 14.
9. J-Link PRO V5: Rebuilt firmware with ARMv8-A/R module version 14.
10. J-Link PRO V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
11. J-Link PRO PoE V6: Rebuilt firmware with ARMv8-A/R module version 14.
12. J-Link WiFi V1: Rebuilt firmware with ARMv8-A/R module version 14.
13. J-Link WiFi V2: Rebuilt firmware with ARMv8-A/R module version 14.
14. J-Trace PRO V3 Cortex: Rebuilt firmware with ARMv8-A/R module version 14.
15. J-Trace PRO V3: Rebuilt firmware with ARMv8-A/R module version 14.
16. Flasher ARM V5: Rebuilt firmware with ARMv8-A/R module version 14.
17. Flasher ARM V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
18. Flasher ARM V6: Rebuilt firmware with ARMv8-A/R module version 14.
19. Flasher PRO V5: Rebuilt firmware with ARMv8-A/R module version 14.
20. Flasher PRO V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
21. Flasher PRO V6: Rebuilt firmware with ARMv8-A/R module version 14.
22. Flasher PRO XL V5: Rebuilt firmware with ARMv8-A/R module version 14.
23. Flasher PRO XL V5-1: Rebuilt firmware with ARMv8-A/R module version 14.
24. Flasher PRO XL V6: Rebuilt firmware with ARMv8-A/R module version 14.
25. Flasher Compact V5: Rebuilt firmware with ARMv8-A/R module version 14.
26. Flasher Compact V6: Rebuilt firmware with ARMv8-A/R module version 14.
27. Flasher Portable PLUS V5: Rebuilt firmware with ARMv8-A/R module version 14.
28. Flasher Portable PLUS V6: Rebuilt firmware with ARMv8-A/R module version 14.
29. J-Link-OB-S124: Rebuilt firmware with ARMv8-A/R module version 14.
30. J-Link-OB-RA4M2-Renesas: Rebuilt firmware with ARMv8-A/R module version 14.
31. J-Link-OB-RA4M2-Full: Rebuilt firmware with ARMv8-A/R module version 14.
32. J-Link-OB-K22-Cortex-A: Rebuilt firmware with ARMv8-A/R module version 14.
33. J-Link-OB-K22-Full: Rebuilt firmware with ARMv8-A/R module version 14.
34. RISC-V (e.g. RV64): Increased module version to 4: Memory R/W accesses beyond 32-bit address space did not work properly. Fixed.
35. J-Link EDU Mini V1: Rebuilt firmware with RISC-V module version 4.
36. J-Link EDU Mini V2: Rebuilt firmware with RISC-V module version 4.
37. J-Link EDU/BASE/PLUS V11: Rebuilt firmware with RISC-V module version 4.
38. J-Link EDU/BASE/PLUS V12: Rebuilt firmware with RISC-V module version 4.
39. J-Link ULTRA+ V5: Rebuilt firmware with RISC-V module version 4.
40. J-Link ULTRA+ V5-1: Rebuilt firmware with RISC-V module version 4.
41. J-Link ULTRA+ V6: Rebuilt firmware with RISC-V module version 4.
42. J-Link PRO V5: Rebuilt firmware with RISC-V module version 4.
43. J-Link PRO V5-1: Rebuilt firmware with RISC-V module version 4.
44. J-Link PRO PoE V6: Rebuilt firmware with RISC-V module version 4.
45. J-Link WiFi V1: Rebuilt firmware with RISC-V module version 4.
46. J-Link WiFi V2: Rebuilt firmware with RISC-V module version 4.
47. J-Trace PRO V3 RISC-V: Rebuilt firmware with RISC-V module version 4.
48. J-Trace PRO V3: Rebuilt firmware with RISC-V module version 4.
49. Flasher PRO V5: Rebuilt firmware with RISC-V module version 4.
50. Flasher PRO V5-1: Rebuilt firmware with RISC-V module version 4.
51. Flasher PRO V6: Rebuilt firmware with RISC-V module version 4.
52. Flasher PRO XL V5: Rebuilt firmware with RISC-V module version 4.
53. Flasher PRO XL V5-1: Rebuilt firmware with RISC-V module version 4.
54. Flasher PRO XL V6: Rebuilt firmware with RISC-V module version 4.
55. Flasher Compact V5: Rebuilt firmware with RISC-V module version 4.
56. Flasher Compact V6: Rebuilt firmware with RISC-V module version 4.
57. Flasher Portable PLUS V5: Rebuilt firmware with RISC-V module version 4.
58. Flasher Portable PLUS V6: Rebuilt firmware with RISC-V module version 4.
59. J-Link-OB-RA4M2-Full: Rebuilt firmware with RISC-V module version 4.
60. J-Link-OB-K22-RISCV: Rebuilt firmware with RISC-V module version 4.
61. J-Link-OB-K22-Full: Rebuilt firmware with RISC-V module version 4.
62. 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.
63. 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.
64. Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: After clicking "Reboot", some elements were still visible or accessible while Flasher Hub was rebooting. Fixed.
65. Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: After clicking "Reboot", some elements were still visible or accessible while Flasher Hub was rebooting. Fixed.
66. Flasher PRO V5: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
67. 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.
68. Flasher PRO V6: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
69. 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.
70. 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.
71. 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.
72. Flasher Compact V5: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
73. Flasher Compact V6: Memory leaked when programming a J-Flash project in stand-alone mode that included a manually added external CFI flash. Fixed.
74. 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.
75. 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.
76. 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.
77. 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.
78. Flasher Hub-12 V1: WebIF: Files: When uploading a folder with multiple files inside, not all files inside the folder were actually uploaded. Fixed.
79. Flasher Hub-4 V1: WebIF: Files: When uploading a folder with multiple files inside, not all files inside the folder were actually uploaded. Fixed.
80. J-Link EDU/BASE/PLUS V11: Cadence Xtensa: Added support for HiFi 5 core.
81. J-Link EDU/BASE/PLUS V12: Cadence Xtensa: Added support for HiFi 5 core.
82. J-Link ULTRA+ V5: Cadence Xtensa: Added support for HiFi 5 core.
83. J-Link ULTRA+ V5-1: Cadence Xtensa: Added support for HiFi 5 core.
84. J-Link ULTRA+ V6: Cadence Xtensa: Added support for HiFi 5 core.
85. J-Link PRO V5: Cadence Xtensa: Added support for HiFi 5 core.
86. J-Link PRO V5-1: Cadence Xtensa: Added support for HiFi 5 core.
87. J-Link PRO PoE V6: Cadence Xtensa: Added support for HiFi 5 core.
88. J-Link WiFi V1: Cadence Xtensa: Added support for HiFi 5 core.
89. J-Link WiFi V2: Cadence Xtensa: Added support for HiFi 5 core.
90. J-Link-OB-RA4M2-Full: Cadence Xtensa: Added support for HiFi 5 core.
91. MCU-Link Pro: Cadence Xtensa: Added support for HiFi 5 core.
92. MCU-Link on-board: Cadence Xtensa: Added support for HiFi 5 core.
93. Cadence Xtensa: Increased module version to 5: Under special circumstances, Xtensa-behind-DAP setups did not work properly. Fixed.
94. J-Link EDU/BASE/PLUS V11: Rebuilt firmware with Cadence Xtensa module version 5.
95. J-Link EDU/BASE/PLUS V12: Rebuilt firmware with Cadence Xtensa module version 5.
96. J-Link ULTRA+ V5: Rebuilt firmware with Cadence Xtensa module version 5.
97. J-Link ULTRA+ V5-1: Rebuilt firmware with Cadence Xtensa module version 5.
98. J-Link ULTRA+ V6: Rebuilt firmware with Cadence Xtensa module version 5.
99. J-Link PRO V5: Rebuilt firmware with Cadence Xtensa module version 5.
100. J-Link PRO V5-1: Rebuilt firmware with Cadence Xtensa module version 5.
101. J-Link PRO PoE V6: Rebuilt firmware with Cadence Xtensa module version 5.
102. J-Link WiFi V1: Rebuilt firmware with Cadence Xtensa module version 5.
103. J-Link WiFi V2: Rebuilt firmware with Cadence Xtensa module version 5.
104. J-Link-OB-RA4M2-Full: Rebuilt firmware with Cadence Xtensa module version 5.
105. MCU-Link Pro: Rebuilt firmware with Cadence Xtensa module version 5.
106. MCU-Link on-board: Rebuilt firmware with Cadence Xtensa module version 5.

J-Flash SPI

1. ISSI IS25LP02G: The reported flash size was incorrect (128 MB instead of 256 MB). Fixed.
2. J-Flash SPI did not check if data actually fit in the selected flash when saving a Flasher DAT file. Fixed.

Trace

1. Added native trace buffer support for NXP MCXN10 series.
2. Added native trace buffer support for NXP iMX6ULL series.

Version V8.10 (2024-09-25)

Highlights:

Device Support

1. TI MSPM0L111x: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0L).
2. Espressif ESP32-C2: Added debug support (https://wiki.segger.com/Espressif_ESP32-C2).
3. Espressif ESP32-C3: Added debug support (https://wiki.segger.com/Espressif_ESP32-C3).
4. Espressif ESP32-C6: Added debug support (https://wiki.segger.com/Espressif_ESP32-C6).
5. Espressif ESP32-H2: Added debug support (https://wiki.segger.com/Espressif_ESP32-H2).
6. Microchip PIC32MK: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32MK).

Trace

1. Added native pin and buffer trace support for the Xilinx/AMD Zynq UltraScale+ device family.
2. 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:

DLL

1. LPC-Link2 on-board (aka "LPCXpresso") was false-positively detected as clone. Introduced in V7.98i. Fixed.

Device Support

1. ST STM32WBA55: Flash programming did not work. Introduced in V7.96t. Fixed.

Firmware

1. J-Link ULTRA+ V5: VCOM: For baudrates higher than 4 MBaud, Rx data could be dropped by J-Link because buffer was undersized. Fixed.
2. 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.
3. J-Link ULTRA+ V6: VCOM: For baudrates higher than 4 MBaud, Rx data could be dropped by J-Link because buffer was undersized. Fixed.
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.
5. 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.
6. 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.
7. Flasher Hub-12 V1: WebIF: Moved UI for module firmware update from "Dashboard" to "Configuration > Flasher Hub".
8. Flasher Hub-4 V1: WebIF: Moved UI for module firmware update from "Dashboard" to "Configuration > Flasher Hub".
9. Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: When updating the firmware of a module, the table entry would flicker briefly. Fixed.
10. Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: When updating the firmware of a module, the table entry would flicker briefly. Fixed.
11. Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: Improved page layout.
12. Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: Improved page layout.
13. 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.
14. 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.
15. Cadence Xtensa (e.g. HiFi 3): Increased module version to 3: Interrupts were not disabled during single step. Fixed.
16. J-Link EDU/BASE/PLUS V11: Rebuilt firmware with Cadence Xtensa module version 3.
17. J-Link EDU/BASE/PLUS V12: Rebuilt firmware with Cadence Xtensa module version 3.
18. J-Link ULTRA+ V5: Rebuilt firmware with Cadence Xtensa module version 3.
19. J-Link ULTRA+ V5-1: Rebuilt firmware with Cadence Xtensa module version 3.
20. J-Link ULTRA+ V6: Rebuilt firmware with Cadence Xtensa module version 3.
21. J-Link PRO V5: Rebuilt firmware with Cadence Xtensa module version 3.
22. J-Link PRO V5-1: Rebuilt firmware with Cadence Xtensa module version 3.
23. J-Link PRO PoE V6: Rebuilt firmware with Cadence Xtensa module version 3.
24. J-Link WiFi V1: Rebuilt firmware with Cadence Xtensa module version 3.
25. J-Link WiFi V2: Rebuilt firmware with Cadence Xtensa module version 3.
26. J-Link-OB-RA4M2-Full: Rebuilt firmware with Cadence Xtensa module version 3.
27. MCU-Link Pro: VCOM: Rebuilt firmware with Cadence Xtensa module version 3.
28. MCU-Link on-board: VCOM: Rebuilt firmware with Cadence Xtensa module version 3.
29. 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.
30. J-Link EDU/BASE/PLUS V11: Rebuilt firmware with Cadence Xtensa module version 4.
31. J-Link EDU/BASE/PLUS V12: Rebuilt firmware with Cadence Xtensa module version 4.
32. J-Link ULTRA+ V5: Rebuilt firmware with Cadence Xtensa module version 4.
33. J-Link ULTRA+ V5-1: Rebuilt firmware with Cadence Xtensa module version 4.
34. J-Link ULTRA+ V6: Rebuilt firmware with Cadence Xtensa module version 4.
35. J-Link PRO V5: Rebuilt firmware with Cadence Xtensa module version 4.
36. J-Link PRO V5-1: Rebuilt firmware with Cadence Xtensa module version 4.
37. J-Link PRO PoE V6: Rebuilt firmware with Cadence Xtensa module version 4.
38. J-Link WiFi V1: Rebuilt firmware with Cadence Xtensa module version 4.
39. J-Link WiFi V2: Rebuilt firmware with Cadence Xtensa module version 4.
40. J-Link-OB-RA4M2-Full: Rebuilt firmware with Cadence Xtensa module version 4.
41. MCU-Link Pro: VCOM: Rebuilt firmware with Cadence Xtensa module version 4.
42. MCU-Link on-board: VCOM: Rebuilt firmware with Cadence Xtensa module version 4.
43. Flasher Hub-12 V1: WebIF: Moved user interface of 'Programming' tab into the 'Dashboard' tab.
44. Flasher Hub-4 V1: WebIF: Moved user interface of 'Programming' tab into the 'Dashboard' tab.
45. 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.
46. 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.
47. Flasher Hub-12 V1: WebIF: Dashboard: Removed redundant 'Status' column from 'Overview' table.
48. Flasher Hub-4 V1: WebIF: Dashboard: Removed redundant 'Status' column from 'Overview' table.
49. Flasher Hub-12 V1: WebIF: Dashboard: Removed redundant 'Product' column from 'Overview' table.
50. Flasher Hub-4 V1: WebIF: Dashboard: Removed redundant 'Product' column from 'Overview' table.
51. Flasher Hub-12 V1: WebIF: Dashboard: The 'Last result' column now also shows the DAT file CRC, if available.
52. Flasher Hub-4 V1: WebIF: Dashboard: The 'Last result' column now also shows the DAT file CRC, if available.
53. Flasher Hub-12 V1: WebIF: Configuration > Flasher Hub: Removed redundant 'Product' column.
54. Flasher Hub-4 V1: WebIF: Configuration > Flasher Hub: Removed redundant 'Product' column.

GDB Server

1. embOS Plugin: Updated the plugin to maintain compatibility with the latest version of embOS.

J-Flash SPI

1. When creating a new project with EEPROM and manual settings the default settings were not applied. Fixed.
2. Added a new EEPROM selection "Custom" which allows all EEPROM settings to be edited.

J-Run

1. Added logging support. Added command line options --log and --fileonly.
2. Change and enhance J-Run exit value handling (return -1 on error, application exit code provided by SYS_EXIT when available).

J-Scope

1. In some cases, unnamed arrays were incorrectly displayed in the symbol selection tree. Fixed.

Version V7.98i (2024-09-18)

Device Support

1. ST STM32F0xxxx, STM32F1xxxx, STM32F3xxx8, STM32F3xxxB, STM32F3xxxC: Under certain circumstances, the flash controller was not locked after flash programming. Fixed.
2. STM32F7xxxx: Under certain circumstances, the flash controller was not locked after flash programming. Fixed.
3. AmbiqMicro Apollo5: Verify could erroneously fail when programming small payloads. Fixed.
4. 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.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. Flasher Hub-12 V1: WebIF "Status" tab: Renamed to "Dashboard".
28. Flasher Hub-4 V1: WebIF "Status" tab: Renamed to "Dashboard".
29. Flasher Hub-12 V1: WebIF "Terminal" tab: Renamed to "Status".
30. Flasher Hub-4 V1: WebIF "Terminal" tab: Renamed to "Status".
31. Flasher Hub-12 V1: WebIF "About" tab: Updated contents.
32. Flasher Hub-4 V1: WebIF "About" tab: Updated contents.
33. Flasher Hub-12 V1: WebIF: Added "Terminal" tab, enabling Flasher terminal access from the web interface.
34. Flasher Hub-4 V1: WebIF: Added "Terminal" tab, enabling Flasher terminal access from the web interface.

J-Flash

1. Transfering many (e.g. > 100) files from Flasher to PC at once using the Flasher file dialog could cause J-Flash to freeze. Fixed.
2. Flasher file dialog progress dialog would flicker when transfering multiple small files in one go. Fixed.

J-Flash SPI

1. When creating a new project with EEPROM and manual settings the default settings were not applied. Fixed.
2. 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.
3. Flasher file dialog progress dialog would flicker when transfering multiple small files in one go. Fixed.

J-Run

1. Removed --quit command line option. (Automatic exit is default anyway, so this option was never used)
2. Initialization of PC and SP was incorrect for certain targets (e.g. RP2040 or LPC55S16). Made configurable. Added command line options --pc and --sp.

RTT

1. SEGGER_RTT_Conf.h: Handling for __ARM_ARCH_8_1M_MAIN__ was missing. Fixed.

Version V7.98h (2024-09-11)

Highlights:

Device Support

1. GigaDevice GD32F5: Added option bytes programming support (https://wiki.segger.com/GigaDevice_GD32F5)
2. NXP MCXA13x: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXA10).
3. AmbiqMicro Apollo5: Added debug and flash programming support (https://wiki.segger.com/AmbiqMicro_Apollo5).

Trace

1. Published out-of-the-box trace example for NXP iMX7D: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

DLL

1. Cortex-A15: PTM init did not work properly on certain devices (e.g. Renesas RZ/G1M series devices), resulting in trace not working. Fixed.

Device Support

1. Microchip PIC32CX BZ2: Added WBZ450 and WBZ451 module device names.
2. STM32G0: Verification of option byte memory could fail. Fixed.

Firmware

1. 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.
2. 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.
3. Flasher Hub-12 V1: In rare occasions, a false-positive result would be shown folllowing a programming operation. Fixed.
4. Flasher Hub-4 V1: In rare occasions, a false-positive result would be shown folllowing a programming operation. Fixed.
5. 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.
6. 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.
7. J-Link-OB-K22-NordicSemi: Max. 100mA power consumption was reported in USB config descriptor. Lifted to 500mA.
8. J-Link-OB-SAM3U128-NordicSemi: Max. 100mA power consumption was reported in USB config descriptor. Lifted to 500mA.
9. J-Link-OB-nRF5340-NordicSemi: Max. 100mA power consumption was reported in USB config descriptor. Lifted to 500mA.

Trace

1. Added native trace buffer support for NXP iMX7D series.

Version V7.98g (2024-09-05)

Highlights:

Device Support

1. Renesas RZ/T2ME: Added debug and flash programming support (https://wiki.segger.com/Renesas_RZ/T2ME).

Trace

1. Added native trace buffer support for Renesas RZ/T2M and RZ/N2L series.

Other changes:

Control Panel

1. Added J-Link bootloader version to the "General" tab.

DLL

1. 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.
2. Probe selection dialog: Flasher Hub-4 showed incorrect picture. Fixed.

Device Support

1. Infineon PSoC4: Under certain circumstances, attach was not possible. Introduced in V7.98b. Fixed.

Firmware

1. Flasher ARM V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
2. Flasher ARM V5-1: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
3. Flasher ARM V6: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
4. Flasher PRO V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
5. Flasher PRO V5-1: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
6. Flasher PRO V6: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
7. Flasher PRO XL V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
8. Flasher PRO XL V5-1: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
9. Flasher PRO XL V6: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
10. Flasher Compact V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
11. Flasher Compact V6: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
12. Flasher Portable PLUS V5: Terminal: #SELECT: Improved so that a .CFG project can be selected by passing either "<ProjectName>" or "<ProjectName>.cfg".
13. Flasher ARM V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
14. Flasher ARM V5-1: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
15. Flasher ARM V6: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
16. Flasher PRO V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
17. Flasher PRO V5-1: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
18. Flasher PRO V6: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
19. Flasher PRO XL V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
20. Flasher PRO XL V5-1: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
21. Flasher PRO XL V6: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
22. Flasher Compact V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
23. Flasher Portable PLUS V5: Terminal: Added #NEXTSN command: https://wiki.segger.com/Flasher_-_Remote_control#Commands_to_the_Flasher .
24. 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.
25. J-Link EDU/BASE/PLUS V11: Rebuilt firmware with ARMv8-A/R module version 12.
26. J-Link EDU/BASE/PLUS V11: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
27. J-Link EDU/BASE/PLUS V11: RISC-V: Rebuilt firmware with RISC-V module version 3.
28. J-Link EDU/BASE/PLUS V11: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
29. 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.
30. 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.
31. 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.
32. 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.
33. 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.
34. 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.
35. 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.
36. 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.
37. 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.
38. 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.
39. 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.
40. 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.
41. 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.

GUI Applications

1. Device selection dialog: Improved filtering by manufacturer.

J-Run

1. Enhancement for passing parameters to target application using "--args" command line option.
2. Semihosting SYS_EXIT application status not evaluated correctly. Fixed.

Trace

1. Added trace support for Armv8-A/R architecture in AArch32 and AArch64 mode.

Version V7.98f (2024-08-29)

Highlights:

Device Support

1. GigaDevice GD32E51x: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32E5).
2. GigaDevice GD32G5: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32G5).

Trace

1. 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

1. Extended command "BootMode" to support CMSIS-DAPv2 (https://wiki.segger.com/J-Link_Commander#BootMode).

Control Panel

1. Added J-Link firmware version to the "General" tab.

DLL

1. Cortex-A7: ETM unlock sequence and version detection did not work properly, resulting in trace not working. Fixed.

Device Support

1. TI CC2340: Flash programming failed in case of the user record was not used thus the user record CRC was invalid. Fixed.

Firmware

1. J-Link EDU/BASE/PLUS V12: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
2. J-Link ULTRA+ V6: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
3. J-Link PRO V6: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
4. J-Link PRO PoE V6: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.
5. J-Link WiFi V2: CMSIS-DAPv2: In some cases the communication could stuck. Fixed.

J-Link Package

1. Windows: Qt-DLL files were not signed. Fixed.

Version V7.98e (2024-08-21)

Highlights:

J-Flash SPI

1. Introduced a welcome dialog and a new project dialog.
2. Added a device selection dialog to select a device from the list of supported devices.

Trace

1. 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

1. Renesas RA2L1: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
2. Renesas RA2E1: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
3. Renesas RA2L1: Incorrect CPU frquency was reported during flash programming (500 KHz instead of actual 8 MHz). Fixed.
4. Renesas RA2E1: Incorrect CPU frquency was reported during flash programming (500 KHz instead of actual 8 MHz). Fixed.
5. Renesas S1JA: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
6. Renesas S5D9: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
7. Renesas S7G2: Under certain circumstances, flash programming could fail due to incorrect SPM (stack pointer monitor) configuration. Fixed.
8. Renesas S1JA: Incorrect CPU frequency was reported during flash programming (500 KHz instead of actual 8 MHz). Fixed.
9. Renesas RX140: The R5F51403 was not detected and handled properly. Fixed.
10. Andestech RISC-V: Added debug support for the D23, N225, N25F_SE, D25F_SE, D45_SE, AX65 and AX45MPV cores.

GDB Server

1. Debug session could run wild (GDB ending up in endless halted-resume loop) in case an unknown data BP (watchpoint) was hit. Fixed.
2. 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.

Trace

1. Buffer trace init on Renesas RZ/T1 series could fail. Fixed.

Version V7.98d (2024-08-14)

Highlights:

Device Support

1. ST STM32WB05: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB0).
2. ST STM32WB09: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WB0).
3. Renesas RZ/N1 devices series: Added flash programming support for QSPI1 bank.
4. NXP iMX8X series: Added debug support for the Cortex-A35 cores (https://wiki.segger.com/NXP_i.MX_8X).

Other changes:

DLL

1. Mem access via AP other than AP0 fails for SoC-400. Introduced in V7.96r. Fixed.

Device Support

1. 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.
2. TI CC2340: The device specific reset did not support VTOR (configured via CCFG area). Fixed.
3. NXP MCXN10 series: Flash programming failed on devices marked with MCXNxxx. Device marked with PMCXNxxx are not affected. Fixed.

Firmware

1. Flasher Hub-12 V1: The firmware version reported by #FWVERSIONMOD was cut off for modules at posistion 10 or above. Fixed.
2. Flasher Hub-4 V1: The firmware version reported by #FWVERSIONMOD was cut off for modules at posistion 10 or above. Fixed.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. Flasher Hub-12 V1: Executing the #AUTO PATCH command with a syntax error would return the last result of the target module. Fixed.
15. Flasher Hub-4 V1: Executing the #AUTO PATCH command with a syntax error would return the last result of the target module. Fixed.
16. 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.
17. 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.
18. 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.
19. 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.

Version V7.98c (2024-08-07)

Highlights:

DLL

1. ARMv8-A: Added watchpoint support for AArch32 and AArch64 mode.
2. ARMv8-R: Added watchpoint support for AArch32 and AArch64 mode.

Device Support

1. NXP iMX8M series: Added debug support for the Cortex-A53 cores (https://wiki.segger.com/NXP_i.MX_8M).
2. NXP iMX8MMini series: Added debug support for the Cortex-A53 cores (https://wiki.segger.com/NXP_i.MX_8M_Mini).
3. Nuvoton KM1M4BF6x: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M4BF).

J-Flash Lite

1. Added option to select specific flash loader if multiple loaders are available.
2. Added option to disable/enable specific flash banks.

Trace

1. Published out-of-the-box trace example for ST STM32H7S3: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

DLL

1. 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.

Device Support

1. Renesas RZ/N2L device series: CFI flash programming did not work for addresses ranges larger than 0x1FFFFF. Fixed.
2. ST STM32H7x0: Chip erase could run into a timeout. Fixed.
3. 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.
4. CVA BlueWhale CVM012x: Updated device specific handling such as security detection on connect (https://wiki.segger.com/CVA_BlueWhale_CVM012x).

J-Flash

1. SEGGER Flash Loader (SFL): Improved error handling in case of RAMCode could not be downloaded to the RAM.

J-Scope

1. Increased maximum number of data points per symbol to ~8 million (8 * 1024 * 1024).

Trace

1. Added native trace buffer support for ST SR5E1 device series.
2. Added native trace buffer support for ST STM32H7S3 series.

Version V7.98b (2024-07-31)

Highlights:

Device Provisioner

1. GigaDevice GD32F4(except GD32F403) and GD32A4 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32A4_GD32F4_Option_Bytes_Programming)
2. GigaDevice GD32F5 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32F5_Option_Bytes_Programming)
3. GigaDevice GD32H7 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32H7_Option_Bytes_Programming)
4. GigaDevice GD32W5 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32W5_Option_Bytes_Programming)
5. GigaDevice GD32VW5 series: Added support for option-bytes programming (https://wiki.segger.com/GigaDevice_GD32VW5_Option_Bytes_Programming)

Device Support

1. NXP iMX91 series: Added debug support (https://wiki.segger.com/NXP_i.MX_91).

Other changes:

Device Support

1. Xilinx Zynq UltraScale+: Added support for "attach to a running target" for Cortex-A53 and Cortex-R5 cores.
2. Infineon PSoC4: Under certain circumstances, connect could fail. Introduced in V7.96j. Fixed.
3. ST STM32G0: Under certain circumstances option byte programming could fail. Fixed.
4. AlifSemi AE302F40C1537_HP: Device name mistakenly connected to HE core instead of HP core. Fixed.
5. Analog Devices (CM4xx): Added full part numbers to the device selection dialog.
6. Renesas RA4E1, RA4E2, RA4L1, RA4M2, RA4M3, RA4T1 device series: Reset was not handled correctly in NSECSD state. Fixed.
7. Renesas RA6E1, RA6E2, RA6M4, RA6M5, RA6T2, RA6T3 device series: Reset was not handled correctly in NSECSD state. Fixed.
8. Renesas RA8D1, RA8M1, RA8T1 device series: Reset was not handled correctly in NSECSD state. Fixed.
9. NXP iMX8M Mini Cortex-M4: Attach to a running target caused memory rewrite. Fixed.
10. Renesas RZ/T2 device series: CFI flash programming did not work for addresses ranges larger than 0x1FFFFF. Fixed.
11. Infineon PSoC4 CY8C4046xxx: Work-RAM size not set correctly. Fixed.

GDB Server

1. In some cases GDB Server did not handle semihosting requests with ioclient 2 correctly.

J-Flash

1. Depending on the command line, the process exit code could be 0 even if an error occurred (false positive). Fixed.

J-Flash SPI

1. Depending on the command line, the process exit code could be 0 even if an error occurred (false positive). Fixed.
2. Added command line option "-hide" which starts J-Flash SPI hidden (https://wiki.segger.com/J-Flash_SPI#Command_line_options).

Version V7.98a (2024-07-17)

Configurator

1. Added support for CMSIS-DAPv2 boot mode.

Device Support

1. Added device names for Xilinx Zynq UltraScale+ CG series: XCZU1CG_R5_0, XCZU3TCG_R5_0.
2. Added device names for Xilinx Zynq UltraScale+ EG series: XCZU1EG_R5_0, XCZU3TEG_R5_0.
3. 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.
4. Added debug support for Xilinx Zynq UltraScale+ Cortex-R5_1 core.
5. 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.
6. 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.
7. Added device names for Xilinx Zynq UltraScale+ EV series: XCZU4EV_R5_1, XCZU4EV_R5_1, XCZU5EV_R5_1, XCZU7EV_R5_1
8. 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.
9. Renesas RA8: Under special circumstances (non secure mode), flash programming failed. Introduced in V7.96n. Fixed.

Firmware

1. J-Link EDU/BASE/PLUS V12: Added support for CMSIS-DAPv2 boot mode.
2. J-Link ULTRA+ V6: Added support for CMSIS-DAPv2 boot mode.
3. J-Link PRO V6: Added support for CMSIS-DAPv2 boot mode.
4. J-Link PRO PoE V6: Added support for CMSIS-DAPv2 boot mode.
5. J-Link WiFi V2: Added support for CMSIS-DAPv2 boot mode.

Version V7.98 (2024-07-17)

Device Support

1. Renesas RA8: OSPI flash erase could fail with S28HS512T flash. Fixed.
2. STM32H743xx: Under special circumstances the erase operation could fail. Fixed.

J-Flash

1. 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

1. 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

1. 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

1. SWV tab did not display the host buffer size correctly. Fixed.

DLL

1. Added J-Link command string "SWOSetHostBufferSize". (https://wiki.segger.com/J-Link_Command_Strings#SWOSetHostBufferSize)
2. 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.

Device Support

1. NXP iMXRT1180: When connecting to the Cortex-M7, RAM init could fail under special circumstances. Fixed.
2. SEGGER WireCheck: Did not start and raises "No flash banks defined in U-Flash project". Fixed.

J-Flash

1. 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.
2. Downloading Flasher files would store files with "(null)" placed in front of the actual file name on the Flasher. Introduced with V7.96s. Fixed.
3. Under certain circumstances programming CFI NOR flashes could fail in Flasher standalone mode due to misconfigured configuration file. Fixed.
4. In project settings dialog changing the organization of for CFI banks (Bits/Chips) did not have any effect. Fixed.

J-Flash SPI

1. 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.
2. Downloading Flasher files would store files with "(null)" placed in front of the actual file name on the Flasher. Introduced with V7.96s. Fixed.
3. Added support for ST M95320 EEPROM.

J-Scope

1. Interface dropdown menu was empty when selecting FINE interface. Fixed.
2. Sampling speed input accepted characters. Fixed.

Trace

1. Added StartNTRACETE/StopNTRACETE JLinkScript file functions to be able to replace internal generic trace related N-Trace trace encoder initialization.
2. Added StartNTRACETF/StopNTRACETF JLinkScript file functions to be able to replace internal generic trace related N-Trace trace funnel initialization.
3. Added StartNTRACEPIB/StopNTRACEPIB JLinkScript file functions to be able to replace internal generic trace related N-Trace pin sink initialization.
4. Added StartNTRACESRAM/StopNTRACESRAM JLinkScript file functions to be able to replace internal generic trace related N-Trace SRAM sink initialization.
5. Added StartNTRACEATB/StopNTRACEATB JLinkScript file functions to be able to replace internal generic trace related N-Trace ATB sink initialization.

Version V7.96s (2024-07-04)

Control Panel

1. After submitting a form and refreshing the page in the browser, the last form was resubmitted. Fixed.

DLL

1. macOS would segfault when starting DLL. Introduced in V7.96q. Fixed.

J-Scope

1. Changes to settings were not being applied. Fixed.

Remote Server

1. Added periodic keep alive sequence between remote server and tunnel server while no client is connected to the registered remote server instance.
2. Clicking on menu items had no effect. Fixed.

Remote Server CL

1. 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

1. Microchip PIC32CX BZ2: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32CX_BZ2).

Other changes:

DLL

1. 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.
2. 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.

Device Support

1. TI CC2340: Under certain circumstances (e.g. target power removed while connecting to the target), connect step could hung. Fixed.

Firmware

1. MCU-Link Pro: Added support for second VCOM interface (VCOM1).
2. MCU-Link on-board: Added support for second VCOM interface (VCOM1) on i.MX RT700 boards.
3. ARMvx-M (e.g. Cortex-M4/M33/...): Increased module version to 3: Added support for zoned memory accesses in CoreSight SoC-600 setups.
4. J-Link EDU Mini V1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
5. J-Link EDU/BASE/PLUS V12: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
6. J-Link ULTRA+ V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
7. J-Link ULTRA+ V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
8. J-Link ULTRA+ V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
9. J-Link PRO V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
10. J-Link PRO V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
11. J-Link PRO V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
12. J-Link PRO PoE V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
13. J-Link WiFi V1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
14. J-Link WiFi V2: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
15. J-Trace PRO V3 Cortex: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
16. J-Trace PRO V3 CortexM: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
17. J-Trace PRO V3: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
18. Flasher ARM V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
19. Flasher ARM V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
20. Flasher ARM V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
21. Flasher PRO V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
22. Flasher PRO V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
23. Flasher PRO V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
24. Flasher PRO XL V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
25. Flasher PRO XL V5-1: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
26. Flasher PRO XL V6: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
27. Flasher Compact V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
28. Flasher Portable PLUS V5: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
29. J-Link-OB-RA4M2-Renesas: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
30. J-Link-OB-RA4M2-Full: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
31. J-Link-OB-RA4M2-CortexM: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
32. J-Link-OB-S124: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.
33. J-Link-OB-K22-CortexM: ARMvx-M: Rebuilt firmware with ARMvx-M module version 3.

J-Flash

1. 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

1. Raised max. number of bytes for the "Write Data" custom init/ exit step from 15 to 16 bytes.
2. 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.

Version V7.96q (2024-06-28)

Highlights:

Configurator

1. Added options to enable/disable the FTP, Web, and Telnet server.

Other changes:

DLL

1. macOS would segfault when starting DLL. Introduced in V7.96o. Fixed.

Device Support

1. Renesas RA4M2, RA4M3, RA6M4, RA6M5, RA6E1, RA4E1: Added out of the box SWO support.

Version V7.96p (2024-06-27)

Device Support

1. ST STM32U5 devices series: Programming of internal flash memory could fail. Fixed.

J-Flash SPI

1. Chip Erase could not be executed when using a manual configuration. Fixed.

Version V7.96o (2024-06-26)

Highlights:

Device Support

1. GigaDevice GD32F5: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32F5).
2. GigaDevice GD32A490: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32A4).
3. XHCS HC32L19x: Added debug and flash programming support(https://wiki.segger.com/XHSC_HC32L19x).
4. NXP MCX C: Added debug and flash programming support (https://wiki.segger.com/NXP_MCX_C).
5. NXP MCX W: Added debug and flash programming support (https://wiki.segger.com/NXP_MCX_W).

Other changes:

Device Support

1. TI CC2340: Under certain circumstances (e.g. target power removed while programming), flash programming could hung in stand-alone mode operation. Fixed.
2. TI CC2340: Connect to a locked device could fail. Fixed.
3. Geehy G32A series: The device was detected as unkown device when connecting via JTAG. Fixed.
4. Renesas R9A02G021: Programming of config flash area did not work. Fixed.
5. Infineon Traveo T2G: Programming the flash memory could fail due to a timeout. Fixed.
6. CVA BlueWhale CVM012x: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM012x).
7. ST STM32H7Ax: Readout protection level was reset on every flash access by J-Flash. Fixed.

Firmware

1. 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.
2. J-Link EDU Mini V1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
3. J-Link EDU/BASE/PLUS V12: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
4. J-Link ULTRA+ V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
5. J-Link ULTRA+ V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
6. J-Link ULTRA+ V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
7. J-Link PRO V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
8. J-Link PRO V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
9. J-Link PRO V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
10. J-Link PRO PoE V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
11. J-Link WiFi V1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
12. J-Link WiFi V2: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
13. J-Trace PRO V3 Cortex: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
14. J-Trace PRO V3: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
15. Flasher ARM V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
16. Flasher ARM V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
17. Flasher ARM V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
18. Flasher PRO V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
19. Flasher PRO V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
20. Flasher PRO V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
21. Flasher PRO XL V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
22. Flasher PRO XL V5-1: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
23. Flasher PRO XL V6: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
24. Flasher Compact V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
25. Flasher Portable PLUS V5: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
26. J-Link-OB-RA4M2-Full: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
27. J-Link-OB-K22-Cortex-A: ARMv8-A/R: Rebuilt firmware with ARMv8-A/R module version 13.
28. J-Link-OB-nRF5340-NordicSemi: Added WinUSB (driverless) mode support.
29. J-Link-OB-K22-NordicSemi: Added WinUSB (driverless) mode support.
30. J-Link-OB-SAM3U128-NordicSemi: Added WinUSB (driverless) mode support.

GDB Server

1. 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

1. Added command "BootMode" (https://wiki.segger.com/J-Link_Commander#BootMode).

DLL

1. RISC-V: J-Link would attempt to read optional register DSCRATCH0 even if it is not available. Fixed.
2. RISC-V: Added support for DSCRATCH1 register.

Device Support

1. NXP NCJ29D5: Programming of TX configuration flash failed. Fixed.
2. Cmsemicon CMS32H6157: Added debug and flash programming support.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. Flasher ARM V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
13. Flasher ARM V5-1: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
14. Flasher ARM V6: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
15. Flasher PRO V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
16. Flasher PRO V5-1: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
17. Flasher PRO V6: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
18. Flasher PRO XL V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
19. Flasher PRO XL V5-1: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
20. Flasher PRO XL V6: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
21. Flasher Compact V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).
22. Flasher Portable PLUS V5: Added stand-alone mode support for RAMLess based flash loaders (e.g. CC2340).

J-Flash

1. Parallel NOR flash: Numonyx M58WR series flash devices did not work correctly. Fixed.
2. Enabled the download of RAMLess based flash loaders to the Flasher.

J-Link Package

1. Windows: Added Microsoft redistributable DLL files to shipment.

Version V7.96m (2024-06-19)

Highlights:

Device Support

1. GigaDevice GD32L235: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32L235).
2. TI CC2340R2: Added debug and flash programming support (https://wiki.segger.com/TI_CC2340).
3. HPMicro HPM6330xCEx, HPM6364xDCx: Added debug and (QSPI) flash programming support (https://wiki.segger.com/HPMicro_HPM63).
4. HPMicro HPM6454, HPM64A0, HPM64G0: Added debug and (QSPI) flash programming support (https://wiki.segger.com/HPMicro_HPM64).
5. HPMicro HPM6E devices series: Added debug and (QSPI) flash programming support (https://wiki.segger.com/HPMicro_HPM6E).

Trace

1. Published out-of-the-box trace example for Renesas RA8D1: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Published out-of-the-box trace example for Renesas RA4M3: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
3. Published out-of-the-box trace example for NXP LPC1766: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

Device Support

1. ST STM32H74x, STM32H75x devices series: Under certain circumstances standalone flash programming could fail. Fixed.
2. NXP iMX95 series: Incorrect AP map configuration for Cortex-M33 and Cortex-M7. Fixed.
3. Microchip PIC32CX1025SG: Debugging / flash programming did not work in case of reset extension phase was active. Fixed.

Firmware

1. J-Link-OB-RA4M2-Full: RISC-V: Added support for Cadence Xtensa based cores.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. Flasher ARM V5: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
16. 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.
17. Flasher ARM V6: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
18. Flasher PRO V5: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
19. 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.
20. Flasher PRO V6: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
21. 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.
22. 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.
23. 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.
24. Flasher Compact V5: Stand-alone mode: ARMv8-M: Reset could fail in case of an non secure application was running on the device. Fixed.
25. 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.
26. 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.
27. 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.
28. Flasher Hub-12 V1: Added terminal command #RMDIR: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23RMDIR .
29. Flasher Hub-4 V1: Added terminal command #RMDIR: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23RMDIR .
30. Flasher Hub-12 V1: Improved speed when removing files and folders from a module by removing the respective "MODULE.*" folder.
31. Flasher Hub-4 V1: Improved speed when removing files and folders from a module by removing the respective "MODULE.*" folder.
32. Flasher Hub-12 V1: Removing the "All modules" folder now removes all files and folders from all connected modules.
33. Flasher Hub-4 V1: Removing the "All modules" folder now removes all files and folders from all connected modules.
34. Flasher ARM V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
35. Flasher ARM V5-1: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
36. Flasher ARM V6: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
37. Flasher PRO V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
38. Flasher PRO V5-1: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
39. Flasher PRO V6: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
40. Flasher PRO XL V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
41. Flasher PRO XL V5-1: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
42. Flasher PRO XL V6: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
43. Flasher Compact V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
44. Flasher Portable PLUS V5: Flasher.ini file was generated with a trailing NULL character, causing Windows 11 Notepad to misinterpret it. Fixed.
45. Flasher Hub-12 V1: Wrong contents were displayed for the 'MODULE.024' folder. Introduced in V7.96l. Fixed.
46. Flasher Hub-4 V1: Wrong contents were displayed for the 'MODULE.024' folder. Introduced in V7.96l. Fixed.

Version V7.96l (2024-06-12)

Highlights:

Device Support

1. AmbiqMicro Apollo4 Lite AMAP42KL-KBR: Added debug & flash programming support.
2. AmbiqMicro Apollo4 Blue Lite AMA4B2KL-KXR: Added debug & flash programming support.
3. NXP iMX93 series: Added debug support for the Cortex-A55 and Cortex-M33 cores (https://wiki.segger.com/NXP_i.MX_93).
4. 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:

DLL

1. DLL could crash if an error occurred during the execution of JLINKARM_ExecCommand() (e.g., when a given script file was not found). Fixed.

Device Support

1. AlifSemi E3/E5/E7 device series: Changed J-Links WorkRAM to 0x20000000.
2. TI TMS570LS10106/206: Flash functions (Erase, Programming, Verify, Read, ...) failed. Fixed.
3. Renesas RZ/T2M: Increased max. CFI NOR flash size to 32MB.
4. NXP S32K310: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
5. GigaDevice GD32E235: Added debug and flash programming support(https://wiki.segger.com/GigaDevice_GD32E2).

Firmware

1. Flasher Hub-12 V1: FTP and Web clients ('Files' tab) now see Flasher Hub file system contents unfiltered.
2. Flasher Hub-4 V1: FTP and Web clients ('Files' tab) now see Flasher Hub file system contents unfiltered.
3. 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).
4. 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).
5. Flasher Hub-12 V1: WebIF: "Files" tab: The "Logs" folder could not be removed. Fixed.
6. Flasher Hub-4 V1: WebIF: "Files" tab: The "Logs" folder could not be removed. Fixed.
7. Flasher Hub-12 V1: WebIF: "Files" tab: For some paths (e.g. root folder), uploading files and folders was not enabled. Fixed.
8. Flasher Hub-4 V1: WebIF: "Files" tab: For some paths (e.g. root folder), uploading files and folders was not enabled. Fixed.
9. Flasher Hub-12 V1: Added terminal command #FLIST: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FLIST .
10. Flasher Hub-4 V1: Added terminal command #FLIST: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FLIST .
11. Flasher Hub-12 V1: Added terminal command #FOPEN: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FOPEN .
12. Flasher Hub-4 V1: Added terminal command #FOPEN: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FOPEN .
13. Flasher Hub-12 V1: Added terminal command #FCLOSE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FCLOSE .
14. Flasher Hub-4 V1: Added terminal command #FCLOSE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FCLOSE .
15. Flasher Hub-12 V1: Added terminal command #FWRITE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FWRITE .
16. Flasher Hub-4 V1: Added terminal command #FWRITE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FWRITE .
17. Flasher Hub-12 V1: Added terminal command #FREAD: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FREAD .
18. Flasher Hub-4 V1: Added terminal command #FREAD: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FREAD .
19. Flasher Hub-12 V1: Added terminal command #FSIZE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FSIZE .
20. Flasher Hub-4 V1: Added terminal command #FSIZE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FSIZE .
21. Flasher Hub-12 V1: Added terminal command #FDELETE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FDELETE .
22. Flasher Hub-4 V1: Added terminal command #FDELETE: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FDELETE .
23. Flasher Hub-12 V1: Added terminal command #FCRC: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FCRC .
24. Flasher Hub-4 V1: Added terminal command #FCRC: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FCRC .
25. Flasher Hub-12 V1: Added terminal command #MKDIR: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23MKDIR .
26. Flasher Hub-4 V1: Added terminal command #MKDIR: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23MKDIR .
27. Flasher Hub-12 V1: Implemented terminal command #FFORMAT: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FFORMAT .
28. Flasher Hub-4 V1: Implemented terminal command #FFORMAT: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23FFORMAT .
29. Flasher Hub-12 V1: Renamed feature from "Module terminal server" to "Status port".
30. Flasher Hub-4 V1: Renamed feature from "Module terminal server" to "Status port".
31. J-Link ULTRA+ V5: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
32. 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.
33. J-Link ULTRA+ V6: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
34. J-Link PRO V5: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
35. 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.
36. J-Link PRO V6: VCOM: Baudrate calculation for higher baudrates (> 5 MBaud) did not work correctly and produced a big deviation (> 2.5%). Fixed.
37. 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.
38. 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.
39. 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.
40. 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.
41. 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.
42. Flasher ARM V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
43. Flasher ARM V5-1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
44. Flasher ARM V6: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
45. Flasher PRO V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
46. Flasher PRO V5-1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
47. Flasher PRO V6: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
48. Flasher PRO XL V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
49. Flasher PRO XL V5-1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
50. Flasher PRO XL V6: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
51. Flasher Compact V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
52. Flasher Portable PLUS V5: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
53. Flasher Hub-12 V1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
54. Flasher Hub-4 V1: Stand-alone mode: Other default SPI timeouts were used than in host-based mode. Fixed.
55. 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.
56. 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.
57. 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.
58. 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.

J-Flash

1. 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

1. Host-based mode: Fixed timeouts were always used, although overwrite timeouts were configured. Fixed.

Version V7.96k (2024-06-05)

Highlights:

Device Support

1. Nuvoton KM1M0DF: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M0DF).
2. Infineon WLC: Added debug and flash programming support (https://wiki.segger.com/Infineon_WLC).
3. Nuvoton KM1M7CF: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M7CF).

Other changes:

DLL

1. MacOS: In some cases, a J-Link could show a nickname even though no nickname is configured. Fixed.
2. "SuppressGUI" command string did not suppress device selection dialog. Fixed.

Device Support

1. Puya PY25Q16HB: QSPI flash loaders did not detect the flash. Fixed.
2. Puya P25Q32: QSPI flash loaders were using incorrect flash size (16 Mbit instead of 32 Mbit). Fixed.

Firmware

1. Flasher ARM V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
2. Flasher ARM V5-1: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
3. Flasher ARM V6: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
4. Flasher PRO V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
5. Flasher PRO V5-1: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
6. Flasher PRO V6: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
7. Flasher PRO XL V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
8. Flasher PRO XL V5-1: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
9. Flasher PRO XL V6: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
10. Flasher Compact V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
11. Flasher Portable PLUS V5: Stand-alone mode: J-Flash projects: Max. number of flash banks lifted from 5 to 256.
12. Flasher Hub-12 V1: Enabled terminal via USB BULK (e.g. FlasherControl utility).
13. Flasher Hub-4 V1: Enabled terminal via USB BULK (e.g. FlasherControl utility).
14. Flasher Portable PLUS V5: Some PCode reports were forwarded to a file instead of an ASCII terminal. Fixed.

Version V7.96j (2024-05-29)

Highlights:

Device Support

1. ST STM32H7S3/S7/R3/R7: Added debug and flash (User & XSPI2) programming support (https://wiki.segger.com/ST_STM32H7).
2. NXP QN9080D: Added flash programming support.
3. Microchip PolarFire SOC series: Added debug support for RISC-V E51 and U54 cores (https://wiki.segger.com/Microchip_PolarFire_SOC).

Other changes:

DLL

1. Using HSS with exactly 16 variables would cause a crash. Fixed.
2. RISC-V: Added support for RISC-V JTAG TAPs with != 5-bit IRLen.
3. Microchip PolarFire RISC-V TAP was not detected as a known CPU-TAP. Fixed.

Device Support

1. ST STM32H7: Programming the internal program flash with D-Cache enabled could (erroneously) lead to verification errors caused by improper cache handling. Fixed.
2. 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).
3. 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.

DnD Conditioner

1. Command-line description was incorrect. Fixed.

Firmware

1. Flasher Hub-12 V1: Implemented UART Port: https://wiki.segger.com/Flasher_Hub_-_UART_Port .
2. Flasher Hub-4 V1: Implemented UART Port: https://wiki.segger.com/Flasher_Hub_-_UART_Port .
3. Flasher Hub-12 V1: Added terminal command #RESTART: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23RESTART .
4. Flasher Hub-4 V1: Added terminal command #RESTART: https://wiki.segger.com/Flasher_Hub_-_Remote_control#Command_.23RESTART .
5. Flasher Hub-12 V1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
6. Flasher Hub-4 V1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
7. Flasher ARM V5: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
8. Flasher ARM V5-1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
9. Flasher ARM V6: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
10. Flasher PRO V5: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
11. Flasher PRO V5-1: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
12. Flasher PRO V6: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
13. Flasher PRO XL V5: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
14. 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.
15. Flasher PRO XL V6: Terminal via RS-232: For the #BAUDRATE command, no error was returned for baud rates greater than 1 MBd. Fixed.
16. RISC-V: Increased module version to 3: Added support for RISC-V JTAG TAPs with != 5-bit IRLen.
17. J-Link EDU Mini V1: RISC-V: Rebuilt firmware with RISC-V module version 3.
18. J-Link EDU/BASE/PLUS V12: RISC-V: Rebuilt firmware with RISC-V module version 3.
19. J-Link ULTRA+ V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
20. J-Link ULTRA+ V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
21. J-Link ULTRA+ V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
22. J-Link PRO V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
23. J-Link PRO V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
24. J-Link PRO V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
25. J-Link PRO PoE V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
26. J-Link WiFi V1: RISC-V: Rebuilt firmware with RISC-V module version 3.
27. J-Link WiFi V2: RISC-V: Rebuilt firmware with RISC-V module version 3.
28. J-Trace PRO V3 Cortex: RISC-V: Rebuilt firmware with RISC-V module version 3.
29. J-Trace PRO V3: RISC-V: Rebuilt firmware with RISC-V module version 3.
30. Flasher ARM V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
31. Flasher ARM V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
32. Flasher ARM V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
33. Flasher PRO V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
34. Flasher PRO V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
35. Flasher PRO V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
36. Flasher PRO XL V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
37. Flasher PRO XL V5-1: RISC-V: Rebuilt firmware with RISC-V module version 3.
38. Flasher PRO XL V6: RISC-V: Rebuilt firmware with RISC-V module version 3.
39. Flasher Compact V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
40. Flasher Portable PLUS V5: RISC-V: Rebuilt firmware with RISC-V module version 3.
41. J-Link-OB-RA4M2-Renesas: RISC-V: Rebuilt firmware with RISC-V module version 3.
42. J-Link-OB-RA4M2-Full: RISC-V: Rebuilt firmware with RISC-V module version 3.
43. J-Link-OB-K22-RISCV: RISC-V: Rebuilt firmware with RISC-V module version 3.
44. MCU-Link-OB: UART transfers with high baud rates (>= 115200) could lead to dropped bytes. Fixed.
45. MCU-Link: UART transfers with high baud rates (>= 115200) could lead to dropped bytes. Fixed.
46. Flasher ARM V5: U-Flash: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
47. Flasher ARM V5-1: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
48. Flasher ARM V6: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
49. Flasher PRO V5: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
50. Flasher PRO V5-1: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
51. Flasher PRO V6: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
52. Flasher PRO XL V5: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
53. Flasher PRO XL V5-1: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
54. Flasher PRO XL V6: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
55. Flasher Compact V5: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.
56. Flasher Portable PLUS V5: RISC-V: Under special circumstances, HWUART interface was not working properly (internal race condition). Fixed.

GDB Server

1. Cortex-M: Registers s0-s31 could be exposed twice. Fixed.

J-Flash

1. 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

1. 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

1. Linux: TGZ binary archive: J-Scope was missing. Fixed.

J-Run

1. The PC and SP were not set in some cases. Fixed.

J-Scope

1. When the sampling buffer was full while sampling with RTT, previous timestamps were overwritten. Fixed.

Version V7.96i (2024-05-22)

Highlights:

Device Support

1. NXP NCJ29D5: Added flash programming support for Rx, Tx and custom configuration(https://wiki.segger.com/NXP_NCJ29D5).
2. GigaDevice GD32A503/513x: Added flash programming support for Option Byte 1 (https://wiki.segger.com/GigaDevice_GD32A5).
3. GigaDevice GD32A503/513x: Added flash programming support for Data Flash (https://wiki.segger.com/GigaDevice_GD32A5).

Trace

1. Published out-of-the-box trace example for ST STM32H757: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Published out-of-the-box trace example for Silicon Labs EFR32MG24: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

Device Provisioner

1. PCode_DevPro_ST_STM32U0.pex script file was missing in shipment package. Fixed.

Device Support

1. Renesas RZ/T2L: Flash programming for XSPI1 did not work. Fixed.
2. Geehy G32A1465: Program flash size was incorrect (512 KB instead of 1024 KB). Fixed.

Firmware

1. Flasher Hub-12 V1: NULL packet handling when communicating with modules was not correct, which could lead to USB timeouts. Fixed.
2. Flasher Hub-4 V1: NULL packet handling when communicating with modules was not correct, which could lead to USB timeouts. Fixed.
3. Flasher Hub-4 V1: WebIF: Updated Flasher Hub picture.
4. Flasher Hub-12 V1: WebIF: Updated Flasher Compact picture.
5. Flasher Hub-4 V1: WebIF: Updated Flasher Compact picture.

J-Flash Lite

1. 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

1. 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)
2. ST STM32H523/533 series: Added life-cycle management and provisioning support (https://wiki.segger.com/ST_STM32H5_Security_Product_Lifecycle).

Device Support

1. Microchip SAMA7D65: Added debug support.
2. Infineon PMG1-B1 CYPM1115/1116: Added debug and flash programming support (https://wiki.segger.com/Infineon_PMG1).
3. Macronix MX25V4035F: Added flash programming support.
4. ISSI IS25LP02G: Added flash programming support.

J-Flash SPI

1. Added support for SPI EEPROM with 3 address byte mode (e.g. M95M01).
2. Macronix MX25V4035F: Added flash programming support.
3. ISSI IS25LP02G: Added flash programming support.

Other changes:

Device Support

1. AlifSemi E1: Previous fix for OSPI flash loader not handling flash sizes > 64 MB correctly was incomplete. Fixed.
2. Qorvo QPG5072: Programming failed because chip was not correct identified. Fixed.
3. Renesas RA2A2: Depending on the application running on the target, the data flash could not be programmed. Fixed.
4. 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

1. 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

1. Microchip SAMA7G54: Added device support for SAMA7G54D1G and SAMA7G54D2G.
2. NXP iMX8MNano series: Added debug support for the Cortex-A53 cores (https://wiki.segger.com/NXP_i.MX_8M_Nano).
3. Macronix MX25UW25645G: Added flash programming support for SPIFI flash loaders.
4. Macronix MX66UW1G45G: Added flash programming support for SPIFI flash loaders.
5. GigaDevice GD32A513: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32A5).
6. GigaDevice GD32W515 : Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32W515).
7. ST STM32U031/073/083 series: Added debug and flash programming support (https://wiki.segger.com/ST_STM32U0).

Trace

1. Published out-of-the-box trace example for ST STM32H563 series: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Published out-of-the-box trace example for Nuvoton KM1M4BF and KM1M7AF: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

DLL

1. ARMv8-M: Under special circumstances, the DLL erroneously assumed that the reset has confused the core. Fixed.
2. 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.

Device Support

1. Renesas S7G2 device series: Blank checking of option-setting memory could return wrong result (Introduced with V7.92e). Fixed.
2. AlifSemi E1: OSPI flash loader did not handle flash sizes > 64 MB. Fixed.
3. NXP S32K396: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
4. 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".
5. Added support for Fidelix FM25M4AA.
6. 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.
7. 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.
8. GigaDevice GD32H7: In case of DTCM RAM was disabled, flash programming failed. Fixed.
9. GigaDevice GD32F310/GD32F330/GD32F350: Added option byte flash programming support.
10. Microchip PIC32CX: Added debug and flash programming support for PIC32CX1025SG41064 (https://wiki.segger.com/Microchip_PIC32CX).
11. Renesas RA8x1: Under certain circumstances, reset failed in non-secure debug. Fixed.
12. ST SR5E1E5: Added debug and flash programming support (https://wiki.segger.com/J-Link_ST_SR5E1).

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.

GDB Server

1. -noGUI command line option did not disable all J-Link DLL dialogs. Fixed.
2. 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

1. Chip Erase did not work for STM32H7xxxI series dual bank devices. Fixed.

J-Flash SPI

1. PC-based mode: Programming pages with single SPI failed if no "Init commands" were specified. Introduced with V7.96c. Fixed.

J-Flash SPI CL

1. PC-based mode: Programming pages with single SPI failed if no "Init commands" were specified. Introduced with V7.96c. Fixed.

J-Run

1. J-Run was experiencing issues when Thumb-bit was set on Semihosting address. Fixed.
2. J-Run could have had unexpected behavior because it did not set the program counter. Fixed.

J-Scope

1. J-Scope erroneously tried to halt the target MCU when sampling was stopped. Fixed.

STM32 Utility

1. STM32L4: PCROP_RDP was not reset correctly. Fixed.
2. STM32L4: STM32L4+ devices: PCROPxER was not reset correctly. Fixed.
3. STM32U5 devices: Application would hang up on selection. Fixed.

Version V7.96f (2024-04-24)

Highlights:

Device Support

1. ST STM32U5Fxxx device series: Added debug & flash programming support.

Other changes:

DLL

1. Setting the "SuppressControlPanel" command string did not work and the control panel was created nonetheless. Fixed.
2. Setting the "SuppressGUI" command string did not suppress the control panel. Fixed.

Device Support

1. Renesas S7G2 device series: Programming an application image with option-setting memory could lead to manipulated program flash memory. Fixed.
2. TDK Micronas HVC5xxx device series: Improved erase speed for main flash.
3. I2C_EEPROM: Alias names added for the all generic I2C devices.
4. ST STM32F7 devices series: Flash size for QSPI flashes was erroneously limited to 64 MB instead of 256 MB. Fixed.
5. STM32F2xx: The erase operation could fail due too short timeout. Introduced with V7.94a. Fixed.
6. Microchip PIC32MZ: Programming could fail due to wrong cache handling. Fixed.

Firmware

1. Flasher Hub-4 V1: WebIF: The Flasher Hub-12 image was displayed instead of that for Flasher Hub-4. Fixed.
2. Flasher Hub-12 V1: WebIF: Changed image that depicts a web session to show the Flasher product icon instead of Flasher Hub-12.
3. Flasher Hub-4 V1: WebIF: Changed image that depicts a web session to show the Flasher product icon instead of Flasher Hub-12.
4. 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.
5. J-Link EDU Mini V1: Rebuilt firmware with ARMv8-A/R module version 12.
6. J-Link EDU/BASE/PLUS V12: Rebuilt firmware with ARMv8-A/R module version 12.
7. J-Link ULTRA+ V5: Rebuilt firmware with ARMv8-A/R module version 12.
8. J-Link ULTRA+ V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
9. J-Link ULTRA+ V6: Rebuilt firmware with ARMv8-A/R module version 12.
10. J-Link PRO V5: Rebuilt firmware with ARMv8-A/R module version 12.
11. J-Link PRO V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
12. J-Link PRO V6: Rebuilt firmware with ARMv8-A/R module version 12.
13. J-Link PRO PoE V6: Rebuilt firmware with ARMv8-A/R module version 12.
14. J-Link WiFi V1: Rebuilt firmware with ARMv8-A/R module version 12.
15. J-Link WiFi V2: Rebuilt firmware with ARMv8-A/R module version 12.
16. J-Trace PRO V3 Cortex: Rebuilt firmware with ARMv8-A/R module version 12.
17. J-Trace PRO V3: Rebuilt firmware with ARMv8-A/R module version 12.
18. Flasher ARM V5: Rebuilt firmware with ARMv8-A/R module version 12.
19. Flasher ARM V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
20. Flasher ARM V6: Rebuilt firmware with ARMv8-A/R module version 12.
21. Flasher PRO V5: Rebuilt firmware with ARMv8-A/R module version 12.
22. Flasher PRO V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
23. Flasher PRO V6: Rebuilt firmware with ARMv8-A/R module version 12.
24. Flasher PRO XL V5: Rebuilt firmware with ARMv8-A/R module version 12.
25. Flasher PRO XL V5-1: Rebuilt firmware with ARMv8-A/R module version 12.
26. Flasher PRO XL V6: Rebuilt firmware with ARMv8-A/R module version 12.
27. Flasher Compact V5: Rebuilt firmware with ARMv8-A/R module version 12.
28. Flasher Portable PLUS V5: Rebuilt firmware with ARMv8-A/R module version 12.
29. J-Link-OB-K22-CortexA: Rebuilt firmware with ARMv8-A/R module version 12.
30. J-Link-OB-RA4M2-Renesas: Rebuilt firmware with ARMv8-A/R module version 12.
31. J-Link-OB-RA4M2-Full: Rebuilt firmware with ARMv8-A/R module version 12.
32. J-Link-OB-S124: Rebuilt firmware with ARMv8-A/R module version 12.
33. Flasher Hub-4 V1: WebIF: Modules could be selected for firmware update when they were busy. Fixed.
34. Flasher Hub-12 V1: WebIF: Modules could be selected for firmware update when they were busy. Fixed.
35. Flasher Hub-12 V1: WebIF: Updating the firmware of modules connected behind external USB hubs did not work. Fixed.
36. Flasher Hub-4 V1: WebIF: Updating the firmware of modules connected behind external USB hubs did not work. Fixed.

J-Flash SPI

1. Programming in PC-based mode took more time (ca. 200ms) due to gaps between phases (e.g. between Erase and Program). Fixed.
2. 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.
3. Block protection was cleared even if it was cleared before already (e.g. by a prior Erase), wasting time. Fixed.

J-Flash SPI CL

1. 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.
2. Block protection was cleared even if it was cleared before already (e.g. by a prior Erase), wasting time. Fixed.

J-Scope

1. J-Scope: Added functionality to Highlight a symbol by selecting it in the symbol table.

Version V7.96e (2024-04-17)

Highlights:

Device Support

1. SiliconLabs EFM32PG28: Added debug and flash programming support.
2. ST STM32H523/533 series: Added debug and flash programming support (https://wiki.segger.com/ST_STM32H5).

Other changes:

Control Panel

1. Commander tab: Improved visuals.

DLL

1. Xilinx Zynq UltraScale+: Added debug support for Cortex-A53 cores (https://wiki.segger.com/Xilinx_Zynq_UltraScalePlus).

Device Support

1. ST STM32H74xx/STM32H75xx: Added support for pin configuration "CLK@PF10_nCS@PB10_D0@PF8_D1@PF9_D2@PF7_D3@PF6".
2. NXP JN5189 series: By erasing a single flash sector, the following sector was also erased. Fixed.
3. NXP QN9090 series: By erasing a single flash sector, the following sector was also erased. Fixed.
4. NXP K32W061/41 series: Internal flash: By erasing a single flash sector, the following sector was also erased. Fixed.
5. NXP S32K3xx: Improved device specific handling to initialize the ECC RAM init only on first connect.
6. NXP S32K3xx: Improved device specific handling to support connecting to devices where the main core is disabled.
7. 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.
8. Renesas RA8x1: Data flash size was incorrect (1920 KB instead of 2016 KB). Fixed.
9. ST STM32F7 device series: Added support for pin configuration "CLK@PB2_nCS@PB6_D0@PC9_D1@PD12_D2@PE2_D3@PA1".
10. Renesas RA8x1: Under special circumstances (DLM == OEM_PL2 or DLM == OEM_PL1), flash programming could fail. Fixed.
11. Renesas DA1470x: Flash reading/verification did not work correctly with flash devices with size more than 128 Mbit(32-bit adressing mode). Fixed.
12. Renesas RZ/V2H: Some peripherals did not work properly due to an improper initialization on connect. Fixed.
13. MindMotion MM32SPIN028: Flash programming failed due to an incorrect target RAM size. Fixed.
14. Renesas RA device series: ALeRASE ID code authentication failed in Flasher standalone mode. Fixed.
15. AmbiqMicro Apollo 1 devices series: Under certain circumstances, flash operation (erase, program) would fail. Fixed.

Firmware

1. Flasher Hub-12 V1: WebIF: "Programming" tab: Current programming status was displayed in all uppercase. Fixed.
2. Flasher Hub-4 V1: WebIF: "Programming" tab: Current programming status was displayed in all uppercase. Fixed.
3. Flasher Hub-12 V1: WebIF: Updated GUI of navigation bar.
4. Flasher Hub-4 V1: WebIF: Updated GUI of navigation bar.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. Flasher Hub-12 V1: Lifted number of max. supported modules from 12 to 24.
21. Flasher Hub-4 V1: Lifted number of max. supported modules from 12 to 24.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. J-Link OB RA4M2-Renesas: VCOM functionality: Increased the maximum supported baudrate from 1 MBaud to 3 MBaud.
29. J-Link OB RA4M2-CortexM: VCOM functionality: Increased the maximum supported baudrate from 1 MBaud to 3 MBaud.
30. J-Link OB RA4M2-RISCV: VCOM functionality: Increased the maximum supported baudrate from 1 MBaud to 3 MBaud.
31. J-Link OB RA4M2-Full: VCOM functionality: Increased the maximum supported baudrate from 1 MBaud to 3 MBaud.
32. Flasher ARM V5: "Reboot" command in J-Link Commander was not supported. Fixed.
33. Flasher ARM V5-1: "Reboot" command in J-Link Commander was not supported. Fixed.
34. Flasher ARM V6: "Reboot" command in J-Link Commander was not supported. Fixed.
35. Flasher PRO V5: "Reboot" command in J-Link Commander was not supported. Fixed.
36. Flasher PRO V5-1: "Reboot" command in J-Link Commander was not supported. Fixed.
37. Flasher PRO V6: "Reboot" command in J-Link Commander was not supported. Fixed.
38. Flasher PRO XL V5: "Reboot" command in J-Link Commander was not supported. Fixed.
39. Flasher PRO XL V5-1: "Reboot" command in J-Link Commander was not supported. Fixed.
40. Flasher PRO XL V6: "Reboot" command in J-Link Commander was not supported. Fixed.
41. Flasher Compact V5: "Reboot" command in J-Link Commander was not supported. Fixed.
42. Flasher Portable PLUS V5: "Reboot" command in J-Link Commander was not supported. Fixed.
43. Flasher Hub-12 V1: "Reboot" command in J-Link Commander was not supported. Fixed.
44. Flasher Hub-4 V1: "Reboot" command in J-Link Commander was not supported. Fixed.

Version V7.96d (2024-04-10)

Highlights:

Configurator

1. Configuration dialog: Added VCOM information table.

Device Support

1. Infineon PSoC 4-BLE: Added debug and flash programming support for the CYBLE-224116-01 device.
2. Texas Instruments MSPM0Lx22x: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0L).
3. Toshiba TMPM4k (group2): Added debug & flash programming support for the most recent devices from this series.
4. NXP iMX8XLite series: Added debug support for the Cortex-A35 cores (https://wiki.segger.com/NXP_i.MX_8XLite).
5. NXP iMX8MPlus series: Added debug support for the Cortex-A53 cores (https://wiki.segger.com/NXP_i.MX_8M_Plus).
6. Micronas HVC5422D: Added debug & flash programming support.

Other changes:

DLL

1. Updated image for Flasher Hub-12 in probe selection dialog.
2. 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.

Device Support

1. AlifSemi E3/E5/E7 device series: Added OSPI programming support for IS25WX512.
2. Renesas RZ/N2L: Programming of CFI NOR flash did not work. Fixed.
3. GigaDevice GD32F130: RAM size was incorrect. Under certain circumstances, this could result in errors during flash programming. Fixed.
4. ST STM32U5: Flash programming could fail in Flasher standalone mode. Fixed.

Firmware

1. 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.
2. Flasher Hub-12 V1: Added support for connecting modules behind USB hubs when in flex mode.

Version V7.96c (2024-04-02)

Highlights:

DLL

1. Added native trace buffer support for Xilinx UltraScale+ Cortex-R5 core.

Device Support

1. ST STM32WBA55 series: Added debug & flash programming support (https://wiki.segger.com/ST_STM32WBA).
2. Fidelix FM25M64C: Added flash programming support for SPIFI flash loaders.

J-Flash SPI

1. Fidelix FM25M64C: Added flash programming support.

Other changes:

Device Support

1. ST STM32U5 series devices: Flash programming failed when programming data not aligned to 128 bytes. Fixed.
2. Nuvoton KM1M7: Updated list of supported part numbers / device names.
3. Nuvoton KM1M4: Updated list of supported part numbers / device names.
4. Added flash programming support for Infineon CYBLE-222014-01.
5. NXP RT1064: Added debug & flash programming support for silicon revision B (MIMXRT1064xxx5B / MIMXRT1064xxx6B).
6. 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.
7. Renesas M16C/62, M16C/62L: Added family support via clock synchronized serial I/O mode.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. J-Link-OB-XMC4200 / iMOTION-Link: Cortex-M: Added support for CoreSight SoC-600 debug setups.
30. Flasher Hub-12 V1: WebIF: Updated image of Flasher Hub-12.
31. Flasher ARM V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
32. Flasher ARM V5-1: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
33. Flasher ARM V6: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
34. Flasher PRO V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
35. Flasher PRO V5-1: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
36. Flasher PRO V6: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
37. Flasher PRO XL V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
38. Flasher PRO XL V5-1: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
39. Flasher PRO XL V6: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
40. Flasher Compact V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
41. Flasher Portable PLUS V5: Following a successful operation, the #RESULT command returned an empty string. Introduced in V7.96b. Fixed.
42. 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).
43. 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.
44. 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.
45. 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.

J-Flash SPI

1. 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

1. ArteryTek AT32F40x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32F40x).
2. ArteryTek AT32A40x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32A40x).
3. ArteryTek AT32A41x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32A41x).
4. ArteryTek AT32WB41x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32WB41x).
5. Nuvoton KM1M7: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M7).
6. Nuvoton KM1M4: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_KM1M4).
7. Renesas R9A02G021: Added debug and flash programming support (https://wiki.segger.com/Renesas_ASSP_EASY).
8. Infineon PSoC4000T: Added debug and flash programming support (https://wiki.segger.com/PSoC_4xxx_series).
9. ArteryTek AT32A42x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32AT42x).

Other changes:

Commander

1. Improved error output in case of connect failed.

DLL

1. Trace: Trace file has now shared read flag so it can be read while it is being filled.
2. TI TMS570 series: Minimum flash programming size was incorrectly set to 16 bytes instead of 8 bytes. Fixed.
3. Renesas RX72N, RX72T, RX66N and RX72M cores: DLL would not provide suggested target interfaces. Fixed.

Device Support

1. ArteryTek AT32F43x: Flash bank 2 of the internal flash could not be erased. Fixed.
2. ArteryTek AT32F40x: Add device specific connect and native unlock functionality.
3. ArteryTek AT32A40x: Add device specific connect and native unlock functionality.
4. ArteryTek AT32A41x: Add device specific connect and native unlock functionality.
5. ArteryTek AT32WB41x: Add device specific connect and native unlock functionality.
6. ST STM32H5: Added out of the box SWO support.
7. ArteryTek AT32A42x: Add device specific connect and native unlock functionality.
8. Cmsemicon BAT32G1xx: Flash breakpoints did not work when using the DMA. Fixed.

Firmware

1. 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.
2. Flasher Hub-12 V1: FTP: Uploading into the 'All modules' directory could fail when module #12 was connected. Fixed.
3. Flasher Hub-12 V1: After disabling multiple Flashers, the list of disabled Flashers could be cut off after a reboot. Fixed.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.

J-Flash

1. Renesas RX72N, RX72T, RX66N and RX72M cores: When selecting devices with one of these cores, J-Flash would crash. Fixed.

J-Scope

1. J-Scope crashed when the application was closed while sampling. Fixed.

Version V7.96a (2024-03-14)

Highlights:

Device Support

1. NXP MCXA18: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXA18).
2. Artery Tek AT32F402/AT32F405: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32F40x).
3. Artery Tek AT32F423: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32F42x).
4. Artery Tek AT32F43x: Added flash programming support for user data (https://wiki.segger.com/Artery_AT32F43x).

Other changes:

Device Provisioner

1. Passing only the script file name to open a script file from Script/ subdirectory under the DevPro executable did not work as expected. Fixed.
2. Added log output for script file that has been actually opened, so user can see if fallback (looking under Script/) was performed.

Device Support

1. 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.
2. Renesas RZ/V2H: Added warm reset strategy for both Cortex-R8 cores (https://wiki.segger.com/Renesas_RZ/V2H).
3. Artery Tek AT32F43x: Add device specific connect and native unlock functionality.

Firmware

1. J-Link EDU/BASE/PLUS V12: Reset pin was not released on disconnect. Fixed.
2. 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.
3. 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.
4. 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.
5. J-Link EDU/BASE/PLUS V11: Reset pin was not released on disconnect. Fixed.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. 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.
30. 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.
31. 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.
32. 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.
33. 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-Flash

1. Data window contents could be modified when opened in "Simplified" user interface mode. Fixed.
2. Switching between "Simplified" and "Engineering" user interface modes in the project settings did not update the read-only state of open data windows. Fixed.
3. Project information: Added element that shows "User interface mode" setting if it is not the default.

Version V7.96 (2024-03-07)

Highlights:

Device Provisioner

1. Added script "PCode_DevPro_ST_STM32H5.pex".

J-Link Package

1. Added "Device Provisioner" to software package. (See https://wiki.segger.com/Device_Provisioner)

Other changes:

DLL

1. 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)

Device Support

1. ESWIN EMU32VL170: Added flash programming support for bootloader area.

J-Flash

1. 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

1. GigaDevice GD32F1xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32F1).
2. NXP S32K388: Added debug and flash programming support for Cortex_M7_2 (https://wiki.segger.com/NXP_S32K3xx).
3. NXP S32K388: Added debug and flash programming support for Cortex_M7_3 (https://wiki.segger.com/NXP_S32K3xx).
4. NXP S32K358: Added debug and flash programming support for Cortex_M7_2 (https://wiki.segger.com/NXP_S32K3xx).
5. GigaDevice GD32E5xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32E5).
6. Hilscher NetX90: Added SQI(QSPI) flash programming support for APP Core (https://wiki.segger.com/Hilscher_netX90).
7. GigaDevice GD32VF103: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32VF1).
8. GigaDevice GD32F403: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32F4).
9. AlifSemi E3/E5/E7 device series: Added OSPI programming support (https://wiki.segger.com/AlifSemi_CxEx).

Other changes:

Device Support

1. ESWIN EMU32VL170: Flash loader partially did not restore MCU state. Fixed.
2. Nuvoton M253, M254, M256 and M258 series: Flash programming did not work. Fixed.
3. Nuvoton M254SD2AE: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_M25x).
4. Nuvoton M256SD2AE: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_M25x).
5. ST STM32U5G7xx/9xx: Added debug and flash programming support (https://wiki.segger.com/ST_STM32U5).
6. Nordic Semiconductor nRF9151: Added debug and flash programming support.
7. 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).
8. GigaDevice GD32H7xx: Added native unlock functionality.
9. GigaDevice GD32F4xx: Added native unlock functionality.

J-Scope

1. When sorting the symbol table by changing values, rows could split. Fixed.
2. When the SymbolTable is sorted, the wrong rows got updated. Fixed.

Manual

1. UM08002: Chapter "Introduction" updated, section "What is the J-Link SDK?": Improved wording.
2. UM08002: Chapter "Introduction" updated, section "What is the J-Link SDK?": Improved formatting.
3. UM08002: Chapter "Introduction" updated, section "What is J-Link?": Improved wording.
4. UM08002: Chapter "Introduction" updated, section "What is J-Link?": Improved formatting.
5. UM08002: Chapter "Introduction" updated, section "What is included?": Updated table of J-Link SDK contents.

Version V7.94l (2024-02-29)

Highlights:

Device Support

1. GigaDevice GD32C1xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32C1).
2. GigaDevice GD32E1xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32E1).
3. GigaDevice GD32E2xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32E2).
4. Renesas RA0E1: Moved device support from hidden to public (https://wiki.segger.com/Renesas_RA0E1).
5. Renesas RA2A2: Added debug & flash programming support (https://wiki.segger.com/Renesas_RA2A2).
6. GigaDevice GD32F3xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32F3).
7. GigaDevice GD32L23x: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32L23).
8. Renesas RZ/V2H: Added debug and flash programming support (https://wiki.segger.com/Renesas_RZ/V2H).
9. GigaDevice GD32F2xx: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32F2).

Other changes:

Device Support

1. Renesas RA6M3/RA6T1/S5D3/S5D5/S5D9: Verification of option-setting memory could fail. Fixed.
2. Geehy G32A1: Unsecuring a protected device did not work. Fixed.
3. Geehy G32A1: Added a dialog to trigger a mass erase in case a flash sector is write protected.
4. ST SR6xx: Connect to blank devices failed. Fixed.
5. 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).
6. Geehy APM32F003: Programming of option byte memory did not work. Fixed.

Firmware

1. Flasher ARM V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
2. Flasher ARM V5-1: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
3. Flasher ARM V6: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
4. Flasher PRO V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
5. Flasher PRO V5-1: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
6. Flasher PRO V6: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
7. Flasher PRO XL V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
8. Flasher PRO XL V5-1: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
9. Flasher PRO XL V6: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
10. Flasher Compact V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.
11. Flasher Portable PLUS V5: Stand-alone mode: Programming could fail on ARMv7-A/R targets (e.g. Cortex-A9). Fixed.

GUI Applications

1. macOS: The entries of a combo box or context menu were cut off in height. Fixed.
2. 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.

J-Link Package

1. Windows: Removed obsolete Microsoft DLLs from shipment.

J-Scope

1. J-Scope: Reduced the minimum size of J-Scopes main window.

Version V7.94k (2024-02-21)

Highlights:

Device Support

1. Infineon CCG7S: Added debug and flash programming support(https://wiki.segger.com/Infineon_CCG7S).
2. Infineon CCG7D: Added debug and flash programming support(https://wiki.segger.com/Infineon_CCG7D).
3. GigaDevice GD32A50x: Added flash programming support for the option bytes (https://wiki.segger.com/GigaDevice_GD32A5).
4. Artery AT32F402: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F40x).
5. Artery AT32A403A: Added flash programming support for SPIM (https://wiki.segger.com/Artery_AT32A40x).
6. Artery AT32F403A: Added flash programming support for SPIM (https://wiki.segger.com/Artery_AT32F40x).
7. Artery AT32F407: Added flash programming support for SPIM (https://wiki.segger.com/Artery_AT32F40x).
8. Artery AT32F413: Added flash programming support for SPIM (https://wiki.segger.com/Artery_AT32F41x).

Other changes:

Configurator

1. Systemwide option "Reset 'Don't show again'" did not reset registry key DontShowAgainUnlockSTM32. Fixed.

DLL

1. NXP LPC17xx: RTT: Some devices had dublicated search ranges. Fixed.
2. Vorago VAxxx: Flash programming did not work due to overlapping flash banks. Fixed.

Device Support

1. TI MSPM0: Improved low power mode debugging capabilities.
2. Nuvoton M4xx: Added device specific connect with unlock (formaly only implemented for M45x devices).
3. EFx32 Series 2 devices: Connect would fail when RAM was not readable, but device was in unlocked state. Fixed.
4. GigaDevice GD32 Cortex-M devices: Description of MCU security added (https://wiki.segger.com/GigaDevice_GD32).
5. Renesas RZ/G3S: Added support for some new device names.
6. 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).

Firmware

1. Flasher Hub-12 V1: Implemented module terminal server: https://wiki.segger.com/UM08043_Flasher_Hub-12#Module_terminal_server
2. Flasher Hub-12 V1: WebIF: Added "Terminal" tab.
3. Flasher ARM V5: Added possibility to enable/disable FTP server of probe via config area.
4. Flasher ARM V5-1: Added possibility to enable/disable FTP server of probe via config area.
5. Flasher ARM V6: Added possibility to enable/disable FTP server of probe via config area.
6. Flasher PRO V5: Added possibility to enable/disable FTP server of probe via config area.
7. Flasher PRO V5-1: Added possibility to enable/disable FTP server of probe via config area.
8. Flasher PRO V6: Added possibility to enable/disable FTP server of probe via config area.
9. Flasher PRO XL V5: Added possibility to enable/disable FTP server of probe via config area.
10. Flasher PRO XL V5-1: Added possibility to enable/disable FTP server of probe via config area.
11. Flasher PRO XL V6: Added possibility to enable/disable FTP server of probe via config area.
12. J-Link PRO V5: Added possibility to enable/disable web server of probe via config area.
13. J-Link PRO V5-1: Added possibility to enable/disable web server of probe via config area.
14. J-Link PRO V6: Added possibility to enable/disable web server of probe via config area.
15. J-Link PRO PoE V6: Added possibility to enable/disable web server of probe via config area.
16. J-Link WiFi V1: Added possibility to enable/disable web server of probe via config area.
17. J-Link WiFi V2: Added possibility to enable/disable web server of probe via config area.
18. J-Trace PRO V3 CortexM: Added possibility to enable/disable web server of probe via config area.
19. J-Trace PRO V3 Cortex: Added possibility to enable/disable web server of probe via config area.
20. J-Trace PRO V3: Added possibility to enable/disable web server of probe via config area.
21. Flasher ARM V5: Added possibility to enable/disable web server of probe via config area.
22. Flasher ARM V5-1: Added possibility to enable/disable web server of probe via config area.
23. Flasher ARM V6: Added possibility to enable/disable web server of probe via config area.
24. Flasher PRO V5: Added possibility to enable/disable web server of probe via config area.
25. Flasher PRO V5-1: Added possibility to enable/disable web server of probe via config area.
26. Flasher PRO V6: Added possibility to enable/disable web server of probe via config area.
27. Flasher PRO XL V5: Added possibility to enable/disable web server of probe via config area.
28. Flasher PRO XL V5-1: Added possibility to enable/disable web server of probe via config area.
29. Flasher PRO XL V6: Added possibility to enable/disable web server of probe via config area.
30. J-Link PRO V5: Added possibility to enable/disable TELNET server of probe via config area.
31. J-Link PRO V5-1: Added possibility to enable/disable TELNET server of probe via config area.
32. J-Link PRO V6: Added possibility to enable/disable TELNET server of probe via config area.
33. J-Link PRO PoE V6: Added possibility to enable/disable TELNET server of probe via config area.
34. J-Link WiFi V1: Added possibility to enable/disable TELNET server of probe via config area.
35. J-Link WiFi V2: Added possibility to enable/disable TELNET server of probe via config area.
36. J-Trace PRO V3 CortexM: Added possibility to enable/disable TELNET server of probe via config area.
37. J-Trace PRO V3 Cortex: Added possibility to enable/disable TELNET server of probe via config area.
38. J-Trace PRO V3: Added possibility to enable/disable TELNET server of probe via config area.
39. Flasher ARM V5: Added possibility to enable/disable TELNET server of probe via config area.
40. Flasher ARM V5-1: Added possibility to enable/disable TELNET server of probe via config area.
41. Flasher ARM V6: Added possibility to enable/disable TELNET server of probe via config area.
42. Flasher PRO V5: Added possibility to enable/disable TELNET server of probe via config area.
43. Flasher PRO V5-1: Added possibility to enable/disable TELNET server of probe via config area.
44. Flasher PRO V6: Added possibility to enable/disable TELNET server of probe via config area.
45. Flasher PRO XL V5: Added possibility to enable/disable TELNET server of probe via config area.
46. Flasher PRO XL V5-1: Added possibility to enable/disable TELNET server of probe via config area.
47. Flasher PRO XL V6: Added possibility to enable/disable TELNET server of probe via config area.
48. 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.
49. 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.
50. 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.
51. 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.
52. 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.
53. 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.
54. 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.
55. 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.
56. 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.
57. 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.
58. 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.

J-Mem

1. macOS: Moving the scroll bar of the memory view did not work correctly. Fixed.

J-Scope

1. In some cases, classes were falsely named "<inherited>". Fixed.
2. Anonymous structs or unions were given the wrong name. Fixed.
3. When sampling with RTT, the wrong symbol could be updated when adjusting the Y-Offset. Fixed.

Version V7.94j (2024-02-14)

Highlights:

DLL

1. Trace: Added command string "TRACE_SetBackTraceMaxNumItems". (https://wiki.segger.com/J-Link_Command_Strings#TRACE_SetBackTraceMaxNumItems)

Device Support

1. Artery AT32F403A: Added debug and flash programming (internal flash) support (https://wiki.segger.com/Artery_AT32F40x).
2. Artery AT32A403A: Added debug and flash programming (internal flash) support (https://wiki.segger.com/Artery_AT32A40x).
3. Artery AT32F407: Added debug and flash programming (internal flash) support (https://wiki.segger.com/Artery_AT32F40x).
4. NXP MCXN11: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXN11).

Other changes:

Commander

1. Added command "FDiskInfo" for Flashers. Used to show disk/storage usage on Flashers.

Control Panel

1. "General" tab: Added Disk info for Flashers (production programmers).

Firmware

1. 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)
2. 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)
3. 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)
4. 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)
5. 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)
6. 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)
7. 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)
8. 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)
9. 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)
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.

Version V7.94i (2024-02-07)

Highlights:

Device Support

1. Artery AT32F423: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F42x).
2. Artery AT32F405: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F40x).
3. Artery AT32WB415: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32WB41x).
4. NXP S32K388: Added debug and flash programming support for the second Cortex-M7 core (https://wiki.segger.com/NXP_S32K3xx).
5. HPMicro HPM68xx: Added debug and flash programming support (https://wiki.segger.com/HPMicro_HPM68).
6. Geehy G32A1xx: Added debug and flash programming support (https://wiki.segger.com/Geehy_G32A1xx).
7. Geehy APM32F035: Added debug and flash programming support (https://wiki.segger.com/Geehy_APM32F0xx).
8. Geehy APM32F411: Added debug and flash programming support (https://wiki.segger.com/Geehy_APM32F4xx).
9. Artery AT32F413: Added debug and flash programming (internal flash) support (https://wiki.segger.com/Artery_AT32F41x).

Trace

1. Published out-of-the-box trace example for Renesas RZ/A1L: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Published out-of-the-box trace example for NXP iMXRT106x series: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

Device Support

1. Artery AT32F43x QSPI: PLL Clock initialization changed from 288 MHz to 216 MHz in order to match maximum clock speed on AT32F405.
2. Renesas RA6M1: Incorrect flash base address (0x28000000 instead of 0x60000000) used for the external QSPI flash bank. Fixed.
3. Geehy APM32F4xx: Option-byte programming did not work. Fixed.
4. Geehy APM32F0xx, APM32F1xx: Option-byte programming did not work. Fixed.
5. Renesas DA1470x: Not all registers got restored correctly. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.

GDB Server

1. When activating thread awareness the debug session could fail to start. Fixed.

J-Scope

1. J-Scope now notifies the user if RTT is used without timestamps.

Trace

1. 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)
2. Added command string "CORESIGHT_SetSTMBaseAddr" to allow manual override of STM base address. (https://wiki.segger.com/J-Link_Command_Strings#CORESIGHT_SetSTMBaseAddr)
3. Added command string "CORESIGHT_SetSTMTraceID" to allow manual override of STM trace ID. (https://wiki.segger.com/J-Link_Command_Strings#CORESIGHT_SetSTMTraceID)
4. Added command string "TRACE_SetSTMDataFile" to allow storing STM data into file. (https://wiki.segger.com/J-Link_Command_Strings#TRACE_SetSTMDataFile)
5. Added command string "TRACE_SetSTMDataPort" to allow storing STM data to port. (https://wiki.segger.com/J-Link_Command_Strings#TRACE_SetSTMDataPort)

Version V7.94h (2024-02-01)

Highlights:

Device Support

1. Toshiba TMPM3H Group(2): Added debug and flash programming support for some new part numbers.
2. Artery AT32F425: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F42x).
3. Artery AT32F415: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F41x).
4. ST SR6P3xx: Added debug and flash programming support (https://wiki.segger.com/ST_SR6P3).
5. Artery AT32F421: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F42x).

Other changes:

Device Support

1. Renesas RZ/G3S: Under certain circumstances erase did not work properly. Fixed.
2. Espressif ESP32: Added read support.
3. ST SR6P6xx/SR6P7xx: The watchdog was not handled properly which could result in expired flag was set. Fixed.
4. ST SR6xxxx: The reset did not work properly resulting in an invalid PC after reset. Fixed.

Firmware

1. Flasher ARM V5: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
2. 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.
3. Flasher ARM V6: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
4. Flasher PRO V5: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
5. 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.
6. Flasher PRO V6: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
7. 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.
8. 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.
9. 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.
10. Flasher Compact V5: Terminal: Reading data via USB (e.g. FlasherControl) in chunks smaller than 256 bytes could lead to loss of data. Fixed.
11. 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.
12. 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.
13. 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.
14. 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

1. 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

1. Artery AT32F43x: Added flash programming support for QSPI 1 flash bank (https://wiki.segger.com/Artery_AT32F43x).

Other changes:

DLL

1. Added support for the EON SPI flash EN25QH128 to SPIFI-Lib.
2. EON SPI flash EN25QH64: Block protection was not set correctly. Fixed.
3. RTT: Specifying an RTT search range after/while RTT was running did not work as intended. Fixed.
4. Added support for Cortex-M52 (aka STAR-MC2).

Device Support

1. Artery AT32F437VGT7, AT32F437RMT7, AT32F437RGT7, AT32F437RDT7: J-Link used incorrect flash size. Fixed.
2. NXP iMXRT1180: XCACHE was not handled properly resulting in verification errors after a successful flash program operation. Fixed.

Firmware

1. 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.
2. J-Link EDU Mini V1: Added support for Cortex-M52 core.
3. J-Link EDU/BASE/PLUS V12: Added support for Cortex-M52 core.
4. J-Link ULTRA+ V5: Added support for Cortex-M52 core.
5. J-Link ULTRA+ V5-1: Added support for Cortex-M52 core.
6. J-Link ULTRA+ V6: Added support for Cortex-M52 core.
7. J-Link PRO V5: Added support for Cortex-M52 core.
8. J-Link PRO V5-1: Added support for Cortex-M52 core.
9. J-Link PRO V6: Added support for Cortex-M52 core.
10. J-Link PRO PoE V6: Added support for Cortex-M52 core.
11. J-Link WiFi V1: Added support for Cortex-M52 core.
12. J-Link WiFi V2: Added support for Cortex-M52 core.
13. J-Trace PRO V3 CortexM: Added support for Cortex-M52 core.
14. J-Trace PRO V3 Cortex: Added support for Cortex-M52 core.
15. J-Trace PRO V3: Added support for Cortex-M52 core.
16. Flasher ARM V5: Added support for Cortex-M52 core.
17. Flasher ARM V5-1: Added support for Cortex-M52 core.
18. Flasher ARM V6: Added support for Cortex-M52 core.
19. Flasher PRO V5: Added support for Cortex-M52 core.
20. Flasher PRO V5-1: Added support for Cortex-M52 core.
21. Flasher PRO V6: Added support for Cortex-M52 core.
22. Flasher PRO XL V5: Added support for Cortex-M52 core.
23. Flasher PRO XL V5-1: Added support for Cortex-M52 core.
24. Flasher PRO XL V6: Added support for Cortex-M52 core.
25. Flasher Compact V5: Added support for Cortex-M52 core.
26. Flasher Portable PLUS V5: Added support for Cortex-M52 core.
27. Flasher ARM V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
28. Flasher ARM V5-1: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
29. Flasher ARM V6: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
30. Flasher PRO V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
31. Flasher PRO V5-1: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
32. Flasher PRO V6: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
33. Flasher PRO XL V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
34. 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.
35. Flasher PRO XL V6: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
36. Flasher Compact V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
37. Flasher Portable PLUS V5: TEMRINAL: The #FFORMAT command formatted not only the public area but also the secure area if it was available. Fixed.
38. Flasher ARM V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
39. Flasher ARM V5-1: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
40. Flasher ARM V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
41. Flasher PRO V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
42. Flasher PRO V5-1: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
43. Flasher PRO V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
44. Flasher PRO XL V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
45. Flasher PRO XL V5-1: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
46. Flasher PRO XL V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
47. Flasher Compact V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
48. Flasher Portable PLUS V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
49. 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.
50. 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.
51. 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.
52. 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.
53. 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.
54. 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.
55. 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.
56. 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.
57. 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.
58. 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.
59. 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.

GDB Server

1. Added support for Cortex-M52 (aka STAR-MC2).

J-Flash

1. 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

1. 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

1. Renesas RZ/G3S: Added debug and flash programming support for the Cortex-M33_0 core (https://wiki.segger.com/Renesas_RZ/G3S).
2. 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

1. RTT Tab: Added search range information.
2. RTT Tab: Added event log.

DLL

1. Linux: USB: Improved speed of GetList() function for J-Links connected via USB, so startup of debug session has been speed up as well.

Device Support

1. Renesas M16C/M62P, M16C/N6A: Added programming support for Renesas M30625FGPGP and M306NAFGGP.
2. LPC553x/LPC55S3x: RTT: Added RAMX-RAM4 to auto search ranges.

Firmware

1. Flasher ARM V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
2. Flasher ARM V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
3. Flasher ARM V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
4. Flasher PRO V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
5. Flasher PRO V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
6. Flasher PRO V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
7. Flasher PRO XL V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
8. Flasher PRO XL V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
9. Flasher PRO XL V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
10. Flasher Compact V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
11. Flasher Portable PLUS V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. 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.
30. 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.
31. 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.
32. 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.
33. 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.
34. 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.
35. 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.
36. 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.
37. 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.
38. 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.
39. 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.
40. 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.
41. 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.
42. 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.
43. 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.
44. 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.
45. 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.
46. 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.
47. 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.
48. 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.
49. 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.

Version V7.94e (2024-01-15)

CCS Plugin

1. Added Cortex-M33 support.

DLL

1. Linux: DLL API calls would not work as intended. Introduced in V7.94d. Fixed.

Device Support

1. ST SR6P6xx: Programming the OTP area (e.g. UTEST) could cause a timeout. Fixed.
2. NXP iMXRT1180: Removed some unavailable part numbers.

Manual

1. UM08002: Chapter "Implementation Samples", section "Disabling dialogs": Added sample code for setting "SuppressGUI" command string.
2. UM08002: Chapter "Implementation Samples", section "Disabling dialogs": Added sample code for specifying an error handler.

Version V7.94d (2024-01-11)

Highlights:

Device Support

1. NXP MCXA10: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXA10).

Other changes:

Commander

1. Wrong libc version was used by accident. Introduced with V7.94c. Fixed.

DLL

1. Added new exec command "CORESIGHT_SetETBBufSize" which can be used to override the ETB buffer size autodetection.
2. In rare cases repeated JLINKARM_Open()/JLINKARM_Close() cycles could lead to a stalled DLL. Fixed.
3. Wrong libc version was used by accident. Introduced with V7.94c. Fixed.

Device Support

1. NXP iMXRT1180: Some device names used by the RT1180 CMSIS pack were not supported. Fixed.
2. Renesas R7S721010 and R7S721010 were incorrectly listed as RZ/A1L. Corrected family to RZ/A1M.
3. NXP iMXRT1170: Flash programming did not work. Introduced with V7.88l. Fixed.
4. Trace: TI Jacinto 7: Corrected ETB base addresses and set fixed ETB size as auto-detection is not working on that device.
5. Maxim MAX32690: Added flash programming support for internal program / data flash located at address 0x10300000 (256 KB).
6. Toshiba TMPM3HQF10BFG: Flash programming via CMSIS-DAP did not work. Fixed.
7. STM32U5Axxx: Added debug & flash programming support.

Firmware

1. Flasher ARM V5: Renesas RX26T: Added stand-alone mode support.
2. Flasher ARM V5-1: Renesas RX26T: Added stand-alone mode support.
3. Flasher PRO V5: Renesas RX26T: Added stand-alone mode support.
4. Flasher PRO V5-1: Renesas RX26T: Added stand-alone mode support.
5. Flasher PRO XL V5: Renesas RX26T: Added stand-alone mode support.
6. Flasher PRO XL V5-1: Renesas RX26T: Added stand-alone mode support.
7. Flasher Compact V5: Renesas RX26T: Added stand-alone mode support.
8. Flasher Portable PLUS V5: Renesas RX26T: Added stand-alone mode support.

Version V7.94c (2024-01-03)

DLL

1. Added J-Link script file API function JLINK_RISCV_WriteCSR(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
2. Added J-Link script file API function JLINK_RISCV_ReadCSR(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
3. Under certain circumstances SWO init would not be executed. Introduced with V7.88f. Fixed.
4. Trace: Added trace pin support for TI Jacinto 7 series.

Device Support

1. Infineon S25Hxxxx: Under certain circumstances read did not work correctly. Fixed.
2. Silicon Labs EFR32xG21, EFR32xG22, EFR32xG23, EFR32xG24, EFR32xG25, EFR32xG27, EFR32xG28: Under certain circumstances flash breakpoints did not work. Fixed.
3. NXP iMXRT1180 (Cortex-M7): "FlexSPI 1 (NS)" flash bank: Flash programming did not work. Fixed.
4. NXP iMXRT1180 (Cortex-M7): "FlexSPI 1 (S)" flash bank: Flash programming did not work. Fixed.
5. EFR32xF22xxx, EFR32xF27xxx: Flash programming for UDP region did not work. Introduced in V7.94. Fixed.
6. NXP MCXN10: Boot ROM was not executed after reset resulting in unexpected issues after reset. Fixed.
7. NXP MCXN10: Reset could fail when using JTAG as target interface. Fixed.
8. Renesas RX26T: The J-Link SW did not allow to select JTAG as target interface for RX26T based devices. Fixed.

J-Flash

1. EFM32GG11: Production Programming could lead to all flash banks erased but the BTL flash bank. Fixed.
2. 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

1. J-Scope: Added support to scope symbols of base classes.

RTT Logger

1. Added J-Link Script file support via command line.

Version V7.94b (2023-12-13)

DLL

1. Cadence Xtensa: For "Xtensa behind CoreSight DAP" setups, an APB-AP was not accepted as a valid debug AP and threw an error. Fixed.
2. 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
3. Under certain circumstances (JLINKARM_Open() call with immediate JLINKARM_Close() call afterwards), J-Link DLL could crash. Fixed.

Device Support

1. NXP iMXRT1180: Updated device names to match the official device name scheme.
2. MindMotion MM32xx: Flash programming did not work with Flasher standalone mode. Fixed.
3. NXP iMXRT102x: FlexSPI port B pins were initialized for QSPI flash download, even though they were not being used. Fixed.

Firmware

1. Flasher ARM V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
2. Flasher ARM V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
3. Flasher PRO V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
4. Flasher PRO V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
5. Flasher PRO XL V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
6. Flasher PRO XL V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
7. Flasher Compact V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
8. Flasher Portable PLUS V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. 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.
30. 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.
31. 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.
32. 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-Flash SPI

1. J-Flash SPI projects would always erase on Flasher even if erase was unchecked in project settings. Fixed.

J-Run

1. Some commands of JRun started with "-" instead of "--". fixed.

J-Scope

1. J-Scope: The context menu in the symbol table could not be opened. Fixed.
2. J-Scope: Added support for Bitfields.
3. J-Scope: Added support for Bitfields.

Version V7.94a (2023-12-06)

Highlights:

Device Support

1. Renesas RA8D1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8D1).
2. Renesas RA8T1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8T1).
3. Macronix MX25UW25345G: Added flash programming support.
4. Microchip PIC32CZxxxxCA80, PIC32CZxxxxCA90: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32CZ_CA).

J-Flash SPI

1. Macronix MX25UW25345G: Added flash programming support.

Other changes:

Commander

1. Command "ShowEmus": Extended command so it now also prints the VCOM ports that belong to a specific J-Link.

DLL

1. 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.

Device Support

1. ST STM32H5: Erasing more than 512 KB of internal flash did not work on devices with 1 MB flash size. Fixed.
2. Infineon Traveo: Erase of the workflash could fail. Fixed.
3. LPC11E35/501: Added debug & flash programming support.
4. 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.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. 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.
30. 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.
31. 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.
32. 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.
33. J-Link-OB-K22-CortexA: Added support for ARMv8-A/R based cores (e.g. Cortex-R52).
34. J-Link-OB-RA4M2-Full: Added support for ARMv8-A/R based cores (e.g. Cortex-R52).

GDB Server

1. Setting multiple breakpoints on the same address does not produce a message box anymore, but a log entry only.

J-Flash

1. Project Settings: Init/ Exit steps: The table did not expand in height. Fixed.
2. Project Settings: MCU: While the list of devices was loaded, the project settings dialog could be closed, causing J-Flash to crash. Fixed.
3. 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.
4. New Project Dialog: While the list of devices was loaded, the New Project dialog could be closed, causing J-Flash to crash. Fixed.
5. 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.

J-Scope

1. J-Scope crashed when the symbol table was sorted and a symbol was removed. Fixed.
2. J-Scope crashed in some cases when a symbol was filtered. Fixed.

Version V7.94 (2023-11-29)

Highlights:

Device Support

1. NXP S32M276: Added debug and flash programming support (https://wiki.segger.com/NXP_S32M27x).
2. NXP S32M24x: Added debug and flash programming support (https://wiki.segger.com/NXP_S32M24x).
3. Texas Instruments MSPM0C: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0C).

J-Link Package

1. Windows: Installer: Changed default so "Install a new instance" is checked by default, instead of "Update existing installation".

Other changes:

Device Support

1. ST STM32G4: Program/Erase did not work for specific device configurations. Fixed.
2. ST STM32H7: Device unlock on connect did not work properly. Fixed.
3. Silicon Labs EFR32xG24: Under certain circumstances flash breakpoints did not work. Fixed.

Version V7.92q (2023-11-23)

DLL

1. 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

1. J-Flash now attempts to detect file when opening files without extensions.
2. "Bus error" fix from V7.92p caused a buffer overflow. Fixed.

J-Run

1. Reworked J-Runs ELF file parsing.

J-Scope

1. "Bus error" fix from V7.92p caused a buffer overflow. Fixed.

Version V7.92p (2023-11-22)

DLL

1. 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.
2. ST STM32H7B0xx: Added QSPI flash programming support.
3. 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).
4. ARM dormant mode support: SWD: Added support for connecting via SWD if device was in JTAG State (JTAG -> Dormant -> SWD).
5. Flash programming: If garbage CPU speed was measured (!= 0 but < 1 kHz), it was shown as "0 kHz", instead of the "measured" value. Fixed.

Device Support

1. 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).
2. ST STM32L4R9xx: Increased max. QSPI flash size to 256MB.
3. 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).
4. Renesas RA2L1/RA2E1/RA2E2: Verification of option-setting memory could fail. Fixed.
5. Renesas S1JA/RA2A1: Verification of option-setting memory could fail. Fixed.
6. ST STM32WB55: Improved programming speed for internal flash.
7. Renesas RZ/T2M: Core ID mismatch was reported (warning). Fixed.
8. AlifSemi Ensemble E1: Debugging via SWD did not work because of missing dormant mode support. Fixed.
9. AlifSemi Ensemble E3: Debugging via SWD did not work because of missing dormant mode support. Fixed.
10. AlifSemi Ensemble E5: Debugging via SWD did not work because of missing dormant mode support. Fixed.
11. AlifSemi Ensemble E7: Debugging via SWD did not work because of missing dormant mode support. Fixed.
12. TDK Micronas HVC5xxx: Under certain circumstances, reset did not work with Flasher standalone mode. Fixed.

Firmware

1. Flasher Portable PLUS V5: Reload FLASHER.INI, if configuration had been invalidated (e.g. on file system change).
2. J-Link EDU Mini V1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
3. J-Link EDU/BASE/PLUS V11: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
4. J-Link EDU/BASE/PLUS V12: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
5. J-Link ULTRA+ V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
6. J-Link ULTRA+ V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
7. J-Link ULTRA+ V6: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
8. J-Link PRO V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
9. J-Link PRO V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
10. J-Link PRO V6: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
11. J-Link PRO PoE V6: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
12. J-Link WiFi V1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
13. J-Trace PRO V2 Cortex: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
14. J-Trace PRO V2 CortexM: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
15. J-Trace PRO V3 Cortex: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
16. J-Trace PRO V3 CortexM: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
17. J-Trace PRO V3 RISC-V: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
18. Flasher ARM V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
19. Flasher ARM V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
20. Flasher PRO V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
21. Flasher PRO V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
22. Flasher PRO XL V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
23. Flasher PRO XL V5-1: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
24. Flasher Compact V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
25. Flasher Portable PLUS V5: Added support for Dormant -> JTAG, SWD -> Dormant -> JTAG and JTAG -> Dormant -> SWD switching sequence.
26. 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-Flash

1. Linux arm: J-Flash could crash immediately after launching due to a "Bus error". Fixed.
2. Flash programming: If garbage CPU speed was measured (!= 0 but < 1 kHz), it was shown as "0 kHz", instead of the "measured" value. Fixed.

Version V7.92o (2023-11-08)

Highlights:

Device Support

1. NXP KE1xZ512xxx9: Added debug and flash programming support.
2. AICH 306xH: Added debug and flash programming support (https://wiki.segger.com/AICH_306xH).

Other changes:

Device Support

1. GigaDevice GD32VW553 : Device part numbers completed.
2. Infineon S25HS256T, S25HS512T, S25HS01GT, S25HL256T, S25HL512T, S25HL01GT: Sector size was set to 64 KB instead of correct value of 256 KB. Fixed.

Firmware

1. Flasher ARM V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
2. Flasher ARM V5-1: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
3. Flasher PRO V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
4. Flasher PRO V5-1: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
5. Flasher PRO XL V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
6. Flasher PRO XL V5-1: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
7. Flasher Compact V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
8. Flasher Portable PLUS V5: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
9. Flasher Hub-12 V1: Terminal via TELNET could slow down programming, if a lot of output was generated. Fixed.
10. Flasher Portable PLUS V5: Log output from universal flash loaders (U-Flash) was not forwarded to terminal (VCOM) correctly. Fixed.

J-Scope

1. Reworked J-Scopes ELF file parsing.

RTT Viewer

1. "Clear all terminals" menu action could crash the application fixed.

Version V7.92n (2023-10-31)

Highlights:

Trace

1. Published out-of-the-box trace examples for Renesas EK-RA8M1 board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Added native trace buffer support for Xilinx Zynq device series.

Other changes:

DLL

1. Windows: Updating the firmware of a probe or programmer via IP did not work. Introduced in V7.92l. Fixed.
2. Linux: Attempting to update the firmware of a probe or programmer via IP could cause the application to crash. Fixed.
3. macOS: Attempting to update the firmware of a probe or programmer via IP could cause the application to crash. Fixed.
4. 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.

Device Support

1. ST SR6Pxxx: Programming the OTP area (e.g. UTEST) could cause a timeout. Fixed.

Firmware

1. 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.
2. J-Link EDU Mini V1: Added support for ARMv8-A/R based cores (e.g. Cortex-A53).

GDB Server

1. Monitor command SWO GetMaxSpeed: In some cases, command would return false values. Fixed.

RTT Viewer

1. Added "Clear all terminals" menu action.

Version V7.92m (2023-10-26)

Highlights:

Device Support

1. Renesas RA2E3: Added hidden debug and flash programming support.
2. Nordic Semiconductor nRF9131: Added debug and flash programming support (https://wiki.segger.com/Nordic_Semiconductor_nRF91xx).
3. Nordic Semiconductor nRF9161: Added debug and flash programming support (https://wiki.segger.com/Nordic_Semiconductor_nRF91xx).

Other changes:

Device Support

1. NXP iMXRT1180: Added debug and QSPI flash programming support for the non-secure flash region @ 0x28000000 (https://wiki.segger.com/NXP_iMXRT1180).
2. 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

1. Flasher Hub-12 V1: When uploading multiple files to a module via FTP, the module could get stuck with activity "Writing to files". Fixed.
2. 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.
3. Flasher Hub-12 V1: Module operations failed for modules running firmware compiled 27th Sep 2023 or later. Fixed.
4. Flasher Hub-12 V1: Response strings were sometimes incomplete. Fixed.
5. 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.

J-Flash

1. 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

1. 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

1. GigaDevice GD32VW553 : Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32VW5).
2. Renesas RA8M1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8M1).
3. GigaDevice GD32H7: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32H7).

Other changes:

DLL

1. TI CC1314R10: Incorrect core was displayed in the device selection dialog. Fixed.
2. TI CC1354P10: Incorrect core was displayed in the device selection dialog. Fixed.
3. JLinkDevices XML device entries with core "JLINK_CORE_RISC_V" were not correctly parsed. Fixed.
4. Cortex A/R V8: Under certain circumstances manually defined AP map was not evaluated correctly. Fixed.
5. 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.
6. Improved information output if core base address and/or CTI core base address is set e.g. through J-Link Script file.

Device Support

1. 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.
2. 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).
3. CVA BlueWhale CVM014x: After reset, the core did not halt on the first instruction of the target application, but on the second instead. Fixed.
4. NXP iMXRT1180: Under certain circumstances, debugging could behave unexpected due to some pending interrupts after boot ROM execution. Fixed.
5. NXP K32W14: Programming secure flash bank did not work. Fixed.
6. Programming errors were not detected correctly on STM32WB55xx-series devices. Fixed.
7. NXP RW61x: Added flash programming support for QSPI secure address.
8. NXP RW61x: Connect with JTAG was not working. Fixed.

Firmware

1. Flasher ARM V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
2. Flasher ARM V5-1: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
3. Flasher PRO V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
4. Flasher PRO V5-1: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
5. Flasher PRO XL V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
6. Flasher PRO XL V5-1: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
7. Flasher Compact V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
8. Flasher Portable PLUS V5: Under certain circumstances, the terminal would not respond to commands anymore. Fixed.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. Flasher Portable PLUS V1: Undefined behavior of Flasher after programming of certain project files. Fixed.

GDB Server

1. 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.
2. 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.

J-Flash

1. 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

1. Added support for M95M01 SPI EEPROM.

Manual

1. UM08039 Flasher Hub: Moved to SEGGER wiki: https://wiki.segger.com/UM08039_Flasher_Hub
2. 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)

DLL

1. Added new command string "InhibitConnectRetries" (https://wiki.segger.com/J-Link_Command_Strings#InhibitConnectRetries).
2. Renesas RZ/N2L: Added background access support (used by e.g. RTT).
3. Selecting a J-Link via nickname when a connected J-Link does not have a nickname specified could cause crash. Fixed.
4. JLinkScript Files: Added CORTEX_R52 to known predefined __constants.
5. Probe selection dialog did not show the correct image for J-Link PRO PoE. Fixed.

Device Support

1. NXP S32 series: Write protected devices were not properly detected under special circumstances. Fixed.
2. Renesas M16C/64A: Added flash programming support for R5F364AKxxx.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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

1. Silicon Labs EFR32xG27: Added debug and flash programming support (https://wiki.segger.com/Silicon_Labs_EFR32xG27).

Other changes:

Device Support

1. AlifSemi Ensemble E1: Added support for new derivatives: AE101F4071542
2. AlifSemi Ensemble E3: Added support for new derivatives: AE302F40C1537, AE302F40C1557, AE302F80F5582, AE302F80F55D5
3. AlifSemi Ensemble E5: Added support for new derivatives: AE512F80F5582, AE512F80F55D5
4. AlifSemi Ensemble E1 / E3 / E5 E7 series: Connecting to M55-HE core did not work. Fixed.
5. HPMicro HPM62x4: Programming of SiP flash failed. Fixed.
6. Renesas RA4E1, RA4M2, RA4M3, RA6E1, RA6M5, RA6T2: Programming of option-setting memory could fail. Fixed.

Version V7.92i (2023-10-11)

Highlights:

Trace

1. 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:

DLL

1. Native trace support for Renesas RZ/A1L and RZ/A1LU was not working correctly. Fixed.
2. Added several Infineon CYT4BF series secondary JTAG TAP Ids to list of known TAPs.

Device Support

1. EON SPI Flash EN25QH16B and EN25QH32B: Added flash programming support.
2. TI DRA821: Added debug support for all Cortex-R5 cores (https://wiki.segger.com/TI_Jacinto_7).
3. TI DRA829: Added debug support for all Cortex-R5 cores (https://wiki.segger.com/TI_Jacinto_7).
4. TI TDA4VM: Added debug support for all Cortex-R5 cores (https://wiki.segger.com/TI_Jacinto_7).
5. HPMicro HPM62xx: Flash programming could fail if flash size exceeds 16MB. Fixed.
6. SiliconLabs EFx32 Series 2: Added secure boot debug & flash programming support.
7. SiliconLabs EFx32 Series 2: Connect would always trigger a reset. Fixed.
8. MindMotion MM32F5 / MM32G5: Verification of option bytes could fail after programming. Fixed.
9. MindMotion MM32F5 / MM32G5: Added flash unlock functionality in case active read protection is detected.
10. Infineon S28HL256T, S28HS256T, S28HL512T, S28HS512T, S28HL01GT, S28HS01GT: Added indirect flash programming support.
11. Renesas RA4E1, RA4M2, RA4M3, RA6E1, RA6M4, RA6M5, RA6T2: Verification of option-setting memory could fail. Fixed.

Firmware

1. J-Link-OB-K22-CortexA: Added support for CMSIS-DAP V1 (HID) mode.
2. J-Link-OB-K22-CortexM: Added support for CMSIS-DAP V1 (HID) mode.
3. J-Link-OB-K22-RISCV: Added support for CMSIS-DAP V1 (HID) mode.
4. 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-Flash

1. The stand-alone-mode configuration file was not correct for SEGGER flashloader memory banks. Fixed.

J-Flash SPI

1. Infineon S28HL256T, S28HS256T, S28HL512T, S28HS512T, S28HL01GT, S28HS01GT: Added direct flash programming support.

RTT

1. 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

1. ESWIN EMU32VL170: Added debug and flash programming support(https://wiki.segger.com/ESWIN_EMU32VL170).

Other changes:

Device Support

1. CVA BlueWhale CVM014x: Program flash size was reported incorrect. Fixed.
2. 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.
3. SiliconLabs EFR32xG22: Under special circumstances, connect could fail with higher interface speeds (e.g. 4 MHz). Fixed.

Firmware

1. J-Trace PRO V3 Cortex: Under certain circumstances the first TPIU frame sync packet would not be sampled correctly. Fixed.
2. J-Trace PRO V3 CortexM: Under certain circumstances the first TPIU frame sync packet would not be sampled correctly. Fixed.
3. J-Trace PRO V3 RISC-V: Under certain circumstances the first TPIU frame sync packet would not be sampled correctly. Fixed.

J-Flash SPI

1. J-Flash SPI did not open most recent project or create a new project on startup. Introduced with V7.92a. Fixed.

RTT

1. 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

1. NXP CTN73x: Added debug and flash programming support (https://wiki.segger.com/NXP_CTN73x).
2. Renesas RA6M5: Added missing device support for R7FA6M5BG (1.5 MB flash).
3. NXP iMXRT1180: Added debug and QSPI flash programming support (https://wiki.segger.com/NXP_iMXRT1180).
4. CVA BlueWhale CVM014x: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM014x).
5. PUYA P25Q32SL: Added flash programming support.

J-Flash SPI

1. PUYA P25Q32SL: Added flash programming support.

Other changes:

Device Support

1. Renesas RX26T: The BANKSEL and FAW register (option-setting memory) could not be programmed. Fixed.
2. NXP PN7xxx: Reset could disconnect debug connection. Fixed.
3. NXP PN7xxx: EEPROM moved to separate flashbank.
4. Renesas DA1470x: Flash programming could fail if target firmware changed clock settings. Fixed.
5. MindMotion MM32F5 / MM32G5: Chip erase did not work on option byte. Fixed.
6. ST STM32G4: Chip erase did not work. Fixed.
7. Renesas RA4T1 / RA6E2: Verification of option-setting bytes could fail. Fixed.

Version V7.92f (2023-09-20)

Highlights:

Device Support

1. Microchip PIC32CM JH: Added debug and flash programming support(https://wiki.segger.com/Microchip_PIC32CM_JH).
2. NXP S32K388: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
3. NXP LPC86x: Added debug and flash programming support (https://wiki.segger.com/NXP_LPC86x).

Other changes:

Commander

1. Command files could not be executed correctly if they have carriage returns ('\r') as line breaks. Fixed.

DLL

1. 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.

Device Support

1. HPMicro: Changed naming from HPM53xx to HPM5361xCBx, HPM5361xEGx, HPM5361xCFx, HPM5331xCBx, HPM5331xEGx, HPM5331xCFx, HPM5321xCBx, HPM5321xEGx, HPM5321xCFx, HPM5301xEGx.
2. HPMicro HPM53xx / HPM63xx / HPM67xx: Verification of flash programming could fail. Fixed.
3. NXP LPC55S36: Flash programming for secure bank did not work. Fixed.
4. NXP iMX7D device series: QSPI flash bank size was set to 32 MB instead of 256 MB. Fixed.
5. Hilscher netX90_COM: Normal reset did not work properly. Fixed.

Firmware

1. 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

1. MindMotion MM32F5233: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F5).
2. MindMotion MM32F5333: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F5).
3. MindMotion MM32G0001: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G0).
4. MindMotion MM32G5333: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G5).
5. HPMicro HPM53xx: Added debug and flash programming support (https://wiki.segger.com/HPMicro_HPM53).

Other changes:

Control Panel

1. Added "MemMap" tab.

DLL

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.
2. PIC32MX / MZ: Added command string "PIC32_StayInICSPProgMode". See https://wiki.segger.com/J-Link_Command_Strings#PIC32_StayInICSPProgMode

Device Support

1. Renesas R7G2: Verification of option-setting bytes could fail. Fixed.

Firmware

1. 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.
2. 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.
3. Flasher ARM V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
4. Flasher ARM V5-1: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
5. Flasher PRO V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
6. Flasher PRO V5-1: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
7. Flasher PRO XL V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
8. Flasher PRO XL V5-1: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
9. Flasher Compact V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
10. Flasher Portable PLUS V5: Stand-alone mode programming did not work for NXP S32K3 series MCUs. Fixed.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. J-Link-OB-XMC4200 / iMOTION-Link: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
20. 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.
21. J-Link OB RA4M2-Renesas: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
22. 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.
23. J-Link OB RA4M2-CortexM: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
24. 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.
25. J-Link OB RA4M2-RISCV: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
26. 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.
27. J-Link OB RA4M2-Full: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
28. 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.
29. J-Link-OB-SAM3U128-V3: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
30. 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.
31. J-Link-OB-K22-CortexA: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
32. 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.
33. J-Link-OB-K22-CortexM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
34. 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.
35. J-Link-OB-K22-RISCV: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
36. 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.
37. J-Link-OB-K22-NordicSemi: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
38. 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.
39. J-Link-OB-K22-Qorvo: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
40. 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.
41. J-Link-OB-K22-SiFive: VCOM: Added lower limit and lower limit check for VCOM baud rate. Lower limit is 9600Hz.
42. 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.

XVCD Server

1. Exiting the application by pressing 'any key' after an error occured did not work. Fixed.

Version V7.92d (2023-09-07)

Highlights:

Device Support

1. CVA BlueWhale CVM0114: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM011x).

Other changes:

Commander

1. Command "SetBP": Software instruction breakpoints: RISC-V: Changed breakpoint mode type from "force 32-bit" to "auto".
2. Added USB J-Link selection via nickname to the command line interface (https://wiki.segger.com/J-Link_Commander#USB).
3. The "ShowHWStatus" command could incorrectly report target current measurements of more than 4kA, depending on calibration of connected probe. Fixed.

DLL

1. 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.
2. Extended command string "map add" by optional parameters <RegionName> and <MapType>.
3. CMSIS flash loader: CPU clock speed was not passed to Init() function of loaders that implement this function (there was always 0 passed). Fixed.

Device Support

1. Added 3rd party debug and flash support for Vorago VA108XX and VA416XX devices.
2. ST STM32F446: QSPI flash bank was not selectable. Fixed.
3. Micronas HVC5xxx device series: Reset was not handled correctly. Fixed.
4. ST SR6P6xx: FW cache was not flushed after Reset. Fixed.
5. 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)
6. Renesas R7G2: Verification of option-setting bytes could fail. Fixed.

Firmware

1. Flasher Hub-12 V1: Implemented firmware update via web interface.
2. Flasher Hub-12 V1: Implemented module firmware update via web interface.
3. Flasher Hub-12 V1: Web interface did not reliably detect server connection breakdown. Fixed.
4. Flasher Hub-12 V1: Web server could report "503 Service unavailable" when switching between tabs or opening multiple web sessions in parallel. Fixed.
5. Flasher Hub-12 V1: Changed default for handshake mode from "disabled" to "enabled".
6. 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.
7. Flasher Hub-12 V1: WebIF "UART" tab: Typo "firwmare" --> "firmware". Fixed.
8. Flasher Hub-12 V1: WebIF "Configuration > Flasher Modules" tab: Saving a configuration with one or more modules disabled would always throw an error. Fixed.
9. 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.
10. 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.
11. Flasher Hub-12 V1: Flasher Hub log file updates did not work reliably. Fixed.
12. 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.
13. Flasher Hub-12 V1: FTP: When uploading empty files to one or more modules, no files were created on the modules at all. Fixed.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. J-Link ULTRA+ V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
23. J-Link ULTRA+ V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
24. J-Link ULTRA+ V6: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
25. J-Link PRO V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
26. J-Link PRO V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
27. J-Link PRO V6: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
28. Flasher ARM V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
29. Flasher ARM V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
30. Flasher PRO V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
31. Flasher PRO V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
32. Flasher PRO XL V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
33. Flasher PRO XL V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
34. Flasher Compact V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
35. Flasher Portable PLUS V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.

GDB Server

1. Added USB J-Link selection via nickname to the command line interface (https://wiki.segger.com/J-Link_GDB_Server#-select).
2. Added USB J-Link selection via nickname to the graphical user interface.

GDB Server CL

1. Added USB J-Link selection via nickname to the command line interface (https://wiki.segger.com/J-Link_GDB_Server#-select).

J-Flash SPI

1. Added auto-detect support for SST SST25VF020B SPI flash that does not provide a page buffer but only single-byte programming.

J-Link Package

1. Windows: Installer: Changed to NOT install USB driver by default.

XVCD Server

1. 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

1. NXP RW61x: Added debug and flash programming support(https://wiki.segger.com/NXP_RW61x).
2. Infineon CYT2CL: Added debug and flash programming support(https://wiki.segger.com/Infineon_CYT2CL).
3. ST STM32F446: Added flash programming support for external QSPI flash.

Other changes:

DLL

1. Trace: Overflow counter for ETMv4 was not working correctly. Fixed.
2. Probe selection dialog did not show the correct image for Flasher Hub-12. Fixed.

DLL Updater

1. Added wiki link to DLL updater.

Device Support

1. Renesas RX24T: Incorrect family name was reported ("RX23T" instead of "RX24T"). Fixed.
2. Renesas RX26T: Added debug & flash programming support.

Firmware

1. Flasher Portable PLUS V5: Progress bars for Erase and Program were not updated correctly. Fixed.

Version V7.92b (2023-08-23)

Highlights:

Device Support

1. NXP S32K358: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).

Other changes:

DLL

1. N-Trace: When recording longer periods of time, instruction counters might be lower than they should. Fixed.
2. SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.

Device Support

1. Renesas RX230: Flash programming in big endian mode did not work. Fixed.
2. Renesas RX231: Flash programming in big endian mode did not work. Fixed.
3. Renesas RX23T: Flash programming in big endian mode did not work. Fixed.
4. Renesas RX24T: Flash programming in big endian mode did not work. Fixed.
5. Aurix TC3xx: Device Bulk erase failed on Data Flash DF1. Fixed.
6. ST STM32G4 device series: Loader names contained invalid characters (space). Fixed.
7. ST STM32L4 device series: Loader names contained invalid characters (space). Fixed.
8. Qorvo PAC55xx series: Erase did not work for addresses >= 0x10000. Fixed.
9. Infineon TLE988x/TLE989x: Target reset did not work properly. Fixed.

Firmware

1. Flasher ARM V5: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
2. 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.
3. Flasher PRO V5: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
4. 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.
5. 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.
6. 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.
7. Flasher Compact V5: SFL: When calculating RAM usage for flash programming, the result that was not guaranteed to honor MinAlign requirements of algorithm. Fixed.
8. 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.

J-Link Package

1. Installer: Option to receive update notifications for security updates is now opt-out, instead of opt-in.
2. Installer: Option to receive general update notifications will now use the previously selected option as default (if not available: opt-in).

RTT Viewer

1. Configuration dialog: Serialnumbers with >= 9 didgets could not be entered. Fixed.

Version V7.92a (2023-08-16)

Device Support

1. Infineon Traveo T2G: Programming the supervisory flash could fail due to a timeout. Fixed.
2. ST STM32L476 QSPI support: Added support for pin configuration "CLK@PB10_nCS@PB11_D0@PB1_D1@PB0_D2@PA7_D3@PA6".
3. ST STM32L476 QSPI support: Added support for pin configuration "CLK@PE10_nCS@PE11_D0@PE12_D1@PE13_D2@PE14_D3@PE15".
4. ST STM32L496 QSPI support: Added support for pin configuration "CLK@PA3_nCS@PB11_D0@PB1_D1@PB0_D2@PA7_D3@PA6".

J-Flash SPI

1. When using the '-openprj' option, the last opened project was opened prior to the selected project. Fixed.

Manual

1. UM08022 Flasher: Moved to SEGGER wiki: https://wiki.segger.com/UM08022_Flasher

Version V7.92 (2023-08-11)

Highlights:

DnD Conditioner

1. 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

1. Flasher ARM V5: The JTAG Interface was initialized on startup even when not used. Fixed.
2. Flasher ARM V5-1: The JTAG Interface was initialized on startup even when not used. Fixed.
3. Flasher PRO V5: The JTAG Interface was initialized on startup even when not used. Fixed.
4. Flasher PRO V5-1: The JTAG Interface was initialized on startup even when not used. Fixed.
5. Flasher PRO XL V5: The JTAG Interface was initialized on startup even when not used. Fixed.
6. Flasher PRO XL V5-1: The JTAG Interface was initialized on startup even when not used. Fixed.
7. Flasher Compact V5: The JTAG Interface was initialized on startup even when not used. Fixed.
8. Flasher Portable PLUS V5: The JTAG Interface was initialized on startup even when not used. Fixed.
9. Flasher Portable PLUS V5: Selection of Images did not work properly under certain circumstances. Fixed.
10. Flasher ARM V5: PCodes in Config files were not loaded correctly. Fixed.
11. Flasher ARM V5-1: PCodes in Config files were not loaded correctly. Fixed.
12. Flasher PRO V5: PCodes in Config files were not loaded correctly. Fixed.
13. Flasher PRO V5-1: PCodes in Config files were not loaded correctly. Fixed.
14. Flasher PRO XL V5: PCodes in Config files were not loaded correctly. Fixed.
15. Flasher PRO XL V5-1: PCodes in Config files were not loaded correctly. Fixed.
16. Flasher Compact V5: PCodes in Config files were not loaded correctly. Fixed.
17. Flasher Portable PLUS V5: PCodes in Config files were not loaded correctly. Fixed.
18. J-Link OB-K22-Qorvo: Added WinUSB (driverless) mode support.
19. J-Link OB-K22-Qorvo: Made sure that firmware boots in driverless mode by default.

Version V7.90a (2023-08-09)

Highlights:

DLL

1. ST STM32H562AG, STM32H562IG, STM32H562RG, STM32H562VG, STM32H562ZG: Added debug & flash programming support.

Trace

1. 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

1. TI CC2340: In case of a image with "disable debug interface" configuration was programmed, verify erroneusly failed. Fixed.
2. ST SR6P6x : ECC RAM was not initialized on connect to cluster 0 core 0, but on reset. Now initialized on connect. Fixed.
3. ST SR6Pxxx/ SR6Gxxx : Security watchdog was not disabled when connecting to DME or DSPH core. Fixed.

Firmware

1. 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.
2. Flasher Portable PLUS V5: U-Flash Projects in sub-directories displayed path and not the "display text". Fixed.
3. Flasher Portable PLUS V5: Save and restore image selection on power cycle.
4. J-Link OB-K22-CortexA: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
5. 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.
6. 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)
7. J-Link OB-K22-CortexM: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
8. 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.
9. 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)
10. J-Link OB-K22-RISCV: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
11. 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.
12. 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)
13. J-Link OB-K22-Full: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
14. 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.
15. 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)
16. J-Link OB-K22-Qorvo: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
17. 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.
18. 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)
19. J-Link-OB-K22-NordicSemi: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
20. 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.
21. 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)
22. J-Link-OB-SAM3U128-V2-NordicSemi: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
23. 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.
24. 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)
25. J-Link-OB-SAM3U128-V3: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
26. 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.
27. 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)
28. J-Link-OB-nRF5340-NordicSemi: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
29. 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.
30. 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)
31. J-Link-OB-STM32F072-128KB-CortexM: Drag & Drop programming: Disabled Drag & Drop support for .bin files.
32. 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.
33. 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)

Version V7.90 (2023-08-02)

Highlights:

Device Support

1. ISSI IS25LP512E, IS25WP512E and IS25LQ512B: Added flash programming support to all (Q)SPI flash based algorithms.
2. ISSI IS25LP025E, IS25WP025E and IS25LQ025B: Added flash programming support to all (Q)SPI flash based algorithms.
3. ISSI IS25LP10E, IS25WP10E and IS25LQ10B: Added flash programming support to all (Q)SPI flash based algorithms.

J-Flash SPI

1. ISSI IS25LP512E, IS25WP512E and IS25LQ512B: Added direct mode flash programming support
2. ISSI IS25LP025E, IS25WP025E and IS25LQ025B: Added direct mode flash programming support
3. ISSI IS25LP10E, IS25WP10E and IS25LQ10B: Added direct mode flash programming support

Other changes:

Commander

1. J-Link command files: Lines that only consist of a comment threw "unkown command" errors. Introduced in V7.88l. Fixed.
2. J-Link command files: Added support for C-comments (/* ... */) that spread over multiple lines in command file.

DLL

1. ARMv8-A/R AArch32 (e.g. Cortex-R52): Added support for 64-bit CP15 registers.
2. RTT: Search ranges specified before connect were overridden. Fixed.
3. 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.
4. Added new exec command "DisableSoftwareBPs" which can be used to disable the usage of software breakpoints.
5. DLL: Under certain circumstances the trace analyzer could crash. Fixed.

Device Support

1. 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.
2. 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.

Firmware

1. J-Link EDU Mini V1: Added WinUSB (driverless) mode support.
2. 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.
3. 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.
4. Flasher Portable PLUS V5: Flasher Portable PLUS now supports up to 99 images.
5. Flasher Portable PLUS V5: Changed operating concept: Automatic key repetition for SEL button, decrement on PWR button short press..

GDB Server

1. ARMv8-A/R AArch32 (e.g. Cortex-R52): Added support for 64-bit CP15 registers.

Version V7.88n (2023-07-26)

DLL

1. Pin trace would not start on Renesas RZ/A2M devices. Introduced with V7.80b. Fixed.
2. Trace: RISC-V: Added support for N-Trace in combination with Arm CoreSight peripherals like TPIU etc.
3. Added command strings "RISCV_UseNexusViaATB". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_UseNexusViaATB)
4. Added command strings "RISCV_SetTFBaseAddr". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetTFBaseAddr)
5. Added command strings "RISCV_SetSRAMBaseAddr". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetSRAMBaseAddr)
6. Added command strings "RISCV_SetPIBBaseAddr". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetPIBBaseAddr)
7. Added command strings "RISCV_SetATBBaseAddr". (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetATBBaseAddr)
8. Extended command string "RISCV_SetTEBaseAddr" to accept optional "APIndex" parameter.. (https://wiki.segger.com/J-Link_Command_Strings#RISCV_SetTEBaseAddr)
9. Trace: RISC-V N-Trace: Under certain circumstances SRAM/buffer tracing could crash the device as the wrong SRAM base address was calculated. Fixed.

Device Support

1. ST STM32U5: Connect/unsecure failed in case TZEN == 1 & RDP was set. Fixed.
2. CVA BlueWhale CVM011x: Erase chip will not perform an unlock anymore.
3. CVA BlueWhale CVM011x: When write protected flash areas are detected on connect, there will be no option for a mass erase unlock anymore.

Firmware

1. 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).
2. Flasher ARM V5: An active "Read" task was not clearly signalled by the LED. Fixed.
3. Flasher ARM V5-1: An active "Read" task was not clearly signalled by the LED. Fixed.
4. Flasher Compact: An active "Read" task was not clearly signalled by the LED. Fixed.
5. Flasher PRO V5: An active "Read" task was not clearly signalled by the LED. Fixed.
6. Flasher PRO V5-1: An active "Read" task was not clearly signalled by the LED. Fixed.
7. Flasher PRO V5 XL: An active "Read" task was not clearly signalled by the LED. Fixed.
8. Flasher PRO V5-1 XL: An active "Read" task was not clearly signalled by the LED. Fixed.

GDB Server

1. FreeRTOS plugin: Armv8-M (e.g. Cortex-M33): Thread/Task-specific register values were shown incorrectly (e.g. PC showed LR value). Fixed.
2. 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.
3. ARMv8-A/R AArch32 (e.g. Cortex-R52): Added support for CP15 register "ATS1CPRP".
4. ARMv8-A/R AArch32 (e.g. Cortex-R52): Added support for CP15 register "ATS1CPWP".

J-Flash

1. 'Start Application' issued a Go-Halt-Go sequence instead of a single Go. Fixed.

Version V7.88m (2023-07-19)

Commander

1. Some J-Link command strings (e.g. "EnableEraseAllFlashBanks") were refused as unknown when loaded from a command file. Introduced in V7.88l. Fixed.
2. Command string "SelectModule" did not work properly in conjunction with "usb" command of J-Link Commander. Fixed.

Device Support

1. Micronas HVC5223C: Added debug & flash programming support.
2. NXP MCXN10: Reset did not work properly in case of a bootable application got programmed. Fixed.
3. DiaSemi DA1469x: Programming could fail if target firmware has changed clock settings. Fixed.
4. Renesas R5F21286JSP and R5F21286KSP (R8C Family): Added flash programming support.

Firmware

1. 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).
2. Flasher ARM V5: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
3. Flasher ARM V5-1: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
4. Flasher PRO V5: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
5. Flasher PRO V5-1: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
6. Flasher PRO XL V5: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
7. Flasher PRO XL V5-1: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
8. Flasher Compact: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
9. Flasher Portable PLUS V5: In Universal Flashloader mode, the Flasher continued to perform operations after an error ocurred. Fixed.
10. 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

1. ARM7/9: "monitor reg" now also accepts USR, FIQ, SVC, ABT, IRQ & UND registers (e.g. "monitor reg r13_svc").

RTT

1. 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

1. 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.
2. Artery AT32F435: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F43x).
3. Artery AT32F437: Added debug and flash programming support (https://wiki.segger.com/Artery_AT32F43x).
4. e-peas EDMS105N: Added unprotect mechanism for e-peas EDMS105N.

Trace

1. 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

1. If a C/C++ comment was used in a command that accepts parameters, the comment was accidentally interpreted as parameter. Fixed.

DLL

1. 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.
2. Added command string "SetLogVerbose 1/0" to increase verbosity of J-Link log file.
3. In verbose mode 1 now all data of memory accesses is logged.

Device Support

1. SemiDrive D3xxx/E3xxx: Speed up ECC RAM initialization in connection sequence.
2. ST STM32H74x/STM32H75x: Added new pin configuration "CLK@PB2_nCS@PB10_D0@PC9_D1@PF9_D2@PF7_D3@PF6" for QSPI flash.
3. TI CC2340: Connect to an erased device / device with invalid CCFG block did not work. Introduced in V7.88d. Fixed.
4. e-peas EDMS105N: Device family name was wrong. Fixed.
5. Mediatek MT7697: Programming could fail due to wrong restoration of clock settings. Fixed.
6. NXP iMXRT117x FlexSPI1 support: Added support for pin configuration "nCS@AD18_CLK@AD19_D0@AD20_D1@AD21_D2@AD22_D3@AD23"
7. Reworked Traveo T2G (formerly Traveo II) support.

Firmware

1. Flasher Pro V5: Added QUIT command to CLI to close active telnet connections via script.
2. Flasher Pro V5-1: Added QUIT command to CLI to close active telnet connections via script.
3. Flasher Pro XL V5: Added QUIT command to CLI to close active telnet connections via script.
4. Flasher Pro XL V5-1: Added QUIT command to CLI to close active telnet connections via script.
5. Flasher ARM V5: Added QUIT command to CLI to close active telnet connections via script.
6. Flasher ARM V5-1: Added QUIT command to CLI to close active telnet connections via script.
7. Flasher Portable PLUS V5: Stand-alone mode: Batch programming: U-Flash configurations were not shown correctly on display. Fixed.

GDB Server

1. Improved verify download log message.

J-Flash

1. When connecting via JTAG failed, J-Flash could report "success" for the connect operation, by accident. Fixed.

Version V7.88k (2023-07-05)

Highlights:

DLL

1. Added native trace buffer and pin trace support for Renesas RA6M2 series. Example project is available here: https://wiki.segger.com/Renesas_RA6M2

Device Support

1. ST STM32U595/599: Added SPI flash programming support for CLK@PF4_nCS@PI5_D0@PF0_D1@PF1_D2@PF2_D3@PF3 pin configuration.
2. ST STM32U595/599: Added SPI flash programming support for CLK@PF10_nCS@PA2_D0@PF8_D1@PF9_D2@PF7_D3@PF6 pin configuration.
3. ST STM32U595/599: Added SPI flash programming support for CLK@PH6_nCS@PI5_D0@PI3_D1@PI2_D2@PI1_D3@PH8 pin configuration.
4. Silicon Labs EFR32xG28x: Added debug and flash programming support (https://wiki.segger.com/Silicon_Labs_EFR32xG28).
5. ST STM32U575/585: Added SPI flash programming support for CLK@PF4_nCS@PI5_D0@PF0_D1@PF1_D2@PF2_D3@PF3 pin configuration.
6. ST STM32U575/585: Added SPI flash programming support for CLK@PF10_nCS@PA2_D0@PF8_D1@PF9_D2@PF7_D3@PF6 pin configuration.
7. ST STM32U575/585: Added SPI flash programming support for CLK@PH6_nCS@PI5_D0@PI3_D1@PI2_D2@PI1_D3@PH8 pin configuration.
8. Renesas RA4E1: Added RAMLess support for data flash.
9. Renesas RA4M2: Added RAMLess support for data flash.
10. Renesas RA4M3: Added RAMLess support for data flash.
11. Renesas RA6E1: Added RAMLess support for data flash.
12. Renesas RA6M4: Added RAMLess support for data flash.
13. Renesas RA6M5: Added RAMLess support for data flash.
14. Renesas RA6T2: Added RAMLess support for data flash.
15. TI CC2662R1: Added debug & flash programming support.
16. ST STM32WBAxx: Added debug and flash programming support (https://wiki.segger.com/ST_STM32WBA).
17. e-peas EDMS105N: Added debug and flash programming support(https://wiki.segger.com/e-peas_EDMS105N).
18. ST SR6Gxxx/SR6Pxxx: Added debug support for DME core.

Other changes:

Device Support

1. Renesas RZ/N2L: CFI NOR flash programming did not work. Fixed.
2. Renesas RZ/T2M: Under certain circumstances QSPI flash programming could fail. Fixed.
3. TI MSPM0G: Erasing a single sector would always erase the first sector, regardless which sector was selected.
4. TI MSPM0L: Erasing a single sector would always erase the first sector, regardless which sector was selected.
5. NXP iMXRT117x FlexSPI support: Under certain circumstances writing less than four bytes could fail. Fixed.

Firmware

1. 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

1. NXP i.MXRT500: Added debug support for Cadence Tensilica Fusion F1 DSP (https://wiki.segger.com/NXP_i.MXRT500).
2. Toshiba TMPM3HQF10BFG: Added debug and flash programming support (https://wiki.segger.com/Toshiba_TMPM3H).
3. ST STM32U5A: Added SPI flash programming support for CLK@PF4_nCS@PI5_D0@PF0_D1@PF1_D2@PF2_D3@PF3 pin configuration.
4. ST STM32U5A: Added SPI flash programming support for CLK@PF10_nCS@PA2_D0@PF8_D1@PF9_D2@PF7_D3@PF6 pin configuration.
5. ST STM32U5A: Added SPI flash programming support for CLK@PH6_nCS@PI5_D0@PI3_D1@PI2_D2@PI1_D3@PH8 pin configuration.
6. ST STM32U535/545xx: Added debug and flash programming support(https://wiki.segger.com/ST_STM32U5).

Other changes:

Configurator

1. Configuration dialog: Added elements for configuring a fixed target reference voltage (VTref).

DLL

1. 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

1. FORTH, Inc. SwiftX was not found. Fixed.

Device Support

1. CVA BlueWhale CVM011x: Programming of data flash failed if EEPROM hardware emulation was enabled. Fixed.
2. ST STM32H5: Added device specific connect.
3. Renesas RA family: Added support for protection unlock via ALeRASE code.
4. Renesas Synergy family: Added support for protection unlock via ALeRASE code.

Firmware

1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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

J-Flash

1. Under certain circumstances, using a RAMLess flash loader with J-Flash could fail. Fixed.
2. Under certain circumstances J-Flash could crash on read when using CFI based flash loaders. Fixed.

J-Flash SPI

1. Added support for FRAM Infineon FM25V02A.

Version V7.88i (2023-06-20)

DLL

1. 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
2. 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
3. Under some circumstances, the USB probe selection dialog did not display the probe serial number of nickname. Introduced with V7.88f. Fixed.
4. Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.

Device Support

1. ST STM32U575xG: Erasing of internal flash in single-bank flash mode did not work. Fixed.
2. Micron MT25QU256, MT25QU512, MT25QU01, MT25QU02: Under certain circumstances flash programming could fail. Introduced with 7.88f. Fixed.
3. TI MSPM0G (PG2): NONMAIN programming did not work. Fixed.

Firmware

1. Flasher ARM V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
2. Flasher ARM V5-1: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
3. Flasher PRO V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
4. Flasher PRO V5-1: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
5. Flasher PRO XL V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
6. Flasher PRO XL V5-1: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
7. Flasher Compact V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
8. Flasher Portable PLUS V5: Programming of CFI flashes could cause crash in some cases. Introduced with V7.86. Fixed.
9. 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.
10. Flasher Compact V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
11. Flasher Portable PLUS V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
12. Flasher ARM V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
13. Flasher ARM V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
14. Flasher PRO V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
15. Flasher PRO V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
16. Flasher PRO XL V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
17. Flasher PRO XL V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
18. J-Link PRO V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
19. J-Link PRO V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
20. J-Link PRO V6: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
21. J-Link ULTRA+ V5: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
22. J-Link ULTRA+ V5-1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
23. J-Link ULTRA+ V6: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
24. J-Link EDU/BASE/PLUS V11: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
25. J-Link EDU/BASE/PLUS V12: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
26. J-Link WiFi V1: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
27. J-Trace PRO V3 Cortex: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
28. J-Trace PRO V3 CortexM: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
29. J-Trace PRO V3 RISC-V: When configuring VTref == 1200mV, VTref was still 0V. Fixed.
30. J-Link EDU/BASE/PLUS V12: USB Web Server: Added elements for configuring VTref to "Config" tab.

USB Web Server

1. Landing page: Changed background color to gray when no J-Link is connected.
2. Landing page: Added warning icon when connected J-Link does not support USB Web Server.

Version V7.88h (2023-06-16)

Highlights:

Device Support

1. ST SR6P7Cx: Added debug and flash programming support (https://wiki.segger.com/ST_SR6P7).

Other changes:

DLL

1. SWO: Removed duplicate init steps, making SWO init faster.
2. Linux: The system tray icon was not removed when a J-Link connection was closed. Introduced with V7.88e. Fixed.
3. macOS: The system tray icon was not removed when a J-Link connection was closed. Introduced with V7.88e. Fixed.

RTT

1. 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

1. TI CC1311P3: Added debug and flash programming support (https://wiki.segger.com/TI_CC1311P3).
2. TI CC1314R10: Added debug and flash programming support(https://wiki.segger.com/TI_CC1314R10).

Other changes:

Control Panel

1. Flash tab: Log did not work. Fixed.
2. Menu: Changed order of tabs.

DLL

1. The probe selection dialog showed a generic image for J-Link EDUs. Fixed.
2. The probe selection dialog showed a generic image for J-Link EDU Minis. Fixed.
3. When connecting to a ST-LINK, a warning message box was shown ("Unknown firmware string: [...]"). Introduced with V7.88f. Fixed.

Device Support

1. HDSC HC32F460: Utilization of WDT or SWDT could cause failing of programming. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. Flasher: Storing *.pex files in the *.CFG file is no longer compatible with Flasher ARM/PRO V4 and earlier.
19. 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).
20. 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).
21. 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).
22. 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).
23. 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).
24. 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).
25. 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).
26. 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).
27. 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).

Version V7.88f (2023-06-09)

Highlights:

Device Support

1. CAST BA53: Added debug support (https://wiki.segger.com/CAST_BA53)
2. HPMicro HPM61xx, HPM63xx, HPM64xx, HPM6730 , HPM6750: Added 3rd party flash programming support for XPI1 flash bank.
3. Silicon Labs EFR32FG25x: Added debug and flash programming support (https://wiki.segger.com/Silicon_Labs_EFR32xG25).

Other changes:

Configurator

1. J-Trace PRO RISC-V was listed as "J-Link (unknown)". Fixed.

DLL

1. ST STM32H7: Read of last byte in memory region of QSPI flash could fail. Fixed.
2. ST STM32H7: Max. QSPI flash size has been raised to 256MB.
3. ST STM32F4: OPTCR WRP value after unlock was not the correct production value for all devices. Fixed.
4. Cortex-A/R: Superfluous auto detection of CPU clock frequency could cause fail of programming. Fixed.
5. ST STM32H5: Flash programming did not work with TrustZone enabled and SECWM regions set to non-secure. Fixed.
6. ST STM32G47 device series: Added native single bank support via selectable loader.
7. Infineon TLE988x/TLE989x: Added debug & flash programming support.
8. Silicon Labs EFR32xG23/G24/G25: Watchdog was not feed during programming. Fixed.
9. 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.
10. 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.
11. macOS: When showing dialogs, an additional application icon was shown in the Dock as well as in the App Switcher (Cmd + Tab). Fixed.
12. Probe selection dialog: Changed wording from "emulator" to "probe".
13. Probe selection dialog: Product name, nickname and product image are now displayed for each connected probe.

Device Support

1. ST STM32F7 device series: Added QSPI flash programming support for pin configuration "CLK@PB2_nCS@PB6_D0@PF8_D1@PD12_D2@PF7_D3@PD13".
2. ST STM32H7 single core devices: SWO did not work out of the box. Introduced V7.84b. Fixed.
3. SemiDrive E3 multicore devices: Could not connect to CPU 1-4. Fixed.

Firmware

1. 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)
2. Flasher ARM V5: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
3. 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.
4. Flasher PRO V5: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
5. 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.
6. 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.
7. 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.
8. Flasher Compact V5: U-Flash: Stand-alone ASCII command "#erase" did not work if erase was not part of action mask of "#auto". Fixed.
9. 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.
10. Flasher ARM V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
11. Flasher ARM V5-1: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
12. Flasher PRO V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
13. Flasher PRO V5-1: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
14. Flasher PRO XL V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
15. Flasher PRO XL V5-1: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
16. Flasher Compact V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
17. Flasher Portable PLUS V5: SFL: Increased default stack size of RAMCode from 256 bytes to 512 bytes, if work RAM is large enough.
18. Flasher ARM V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
19. Flasher ARM V5-1: Cortex-A/R: Stand-alone mode did not work. Fixed.
20. Flasher PRO V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
21. Flasher PRO V5-1: Cortex-A/R: Stand-alone mode did not work. Fixed.
22. Flasher PRO XL V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
23. Flasher PRO XL V5-1: Cortex-A/R: Stand-alone mode did not work. Fixed.
24. Flasher Compact V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
25. Flasher Portable PLUS V5: Cortex-A/R: Stand-alone mode did not work. Fixed.
26. Flasher package: Added start menu entry for J-Link commander.

J-Scope

1. Exporting boolean values to CSV did not work. Fixed.

RTT

1. GCC compiler: SEGGER_RTT.c and SEGGER_RTT.h did throw warnings if "-Wcast-align" warning was enabled. Fixed.
2. Added support for ARMv8.1-M architecture (e.g. Cortex-M55 / M85) to RTT sources.

Version V7.88e (2023-05-31)

DLL

1. JTAG auto-detection: Some TI devices were erroneously detected as ICEPick. Fixed.
2. ST STM32H747 device series: Added SPI flash programming support for CLK@PB2_nCS@PG6_D0@PD11_D1@PF9_D2@PF7_D3@PF6 pin configuration.
3. 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.
4. Linux: Added a system tray icon for quick access to the J-Link Control Panel.
5. macOS: Added a system tray icon for quick access to the J-Link Control Panel.
6. Infineon XMC7000 series: Updated device specific handling and added support for additional flash banks.
7. Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".
8. SemiDrive E34xx: Added debug support (https://wiki.segger.com/SemiDrive_E34xx).
9. SemiDrive E36xx: Added debug support (https://wiki.segger.com/SemiDrive_E36xx).
10. SemiDrive D32xx: Added debug and flash programming support (https://wiki.segger.com/SemiDrive_D32xx).

GDB Server

1. Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".

J-Flash

1. Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".

J-Flash Lite

1. Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".

J-Mem

1. Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".

J-Scope

1. Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".

RTT Viewer

1. Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".

SWO Viewer

1. Device selection dialog: Removed unused comboboxes for "Endianness" and "Core index".

Version V7.88d (2023-05-24)

Highlights:

Device Support

1. NXP S32K1422W/S32K144W: Added debug and flash programming support (https://wiki.segger.com/S32Kxxx)
2. TI CC2340: Added support for "attach to a running system" (https://wiki.segger.com/TI_CC2340).
3. SemiDrive E31xx: Added debug and flash programming support (https://wiki.segger.com/SemiDrive_E31xx).
4. SemiDrive E32xx: Added debug and flash programming support (https://wiki.segger.com/SemiDrive_E32xx).
5. SemiDrive E33xx: Added debug and flash programming support (https://wiki.segger.com/SemiDrive_E33xx).
6. NXP NCJ29D5: Added debug and flash programming support (https://wiki.segger.com/NXP_NCJ29D5).
7. NXP MCXN10: Added debug and flash programming support (https://wiki.segger.com/NXP_MCXN10).

Other changes:

DLL

1. Nations N32G032x8 : Flashbank size wrong. Fixed.
2. TI MSPM0G: Added device specific reset, as original reset would not reset peripherals.
3. TI MSPM0L: Added device specific reset, as original reset would not reset peripherals.
4. ST STM32WB: Option byte programming - Flasher stand alone mode: Programming did not work. Fixed.

Firmware

1. J-Link EDU Mini V1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
2. J-Link EDU/BASE/PLUS V11: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
3. J-Link EDU/BASE/PLUS V12: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
4. J-Link ULTRA+ V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
5. J-Link ULTRA+ V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
6. J-Link ULTRA+ V6: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
7. J-Link PRO V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
8. J-Link PRO V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
9. J-Link PRO V6: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
10. J-Trace PRO V2 Cortex: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
11. J-Trace PRO V2 CortexM: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
12. J-Trace PRO V3 Cortex: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
13. J-Trace PRO V3 CortexM: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
14. Flasher ARM V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
15. Flasher ARM V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
16. Flasher PRO V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
17. Flasher PRO V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
18. Flasher PRO XL V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
19. Flasher PRO XL V5-1: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
20. Flasher Compact V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.
21. Flasher Portable PLUS V5: Cortex-M: Under special circumstances, reset did not work (hung). Introduced in V7.88c. Fixed.

Version V7.88c (2023-05-16)

DLL

1. Nations N32xxx : Some Flashbank sizes had wrong sizes. Fixed.
2. SFL / CMSIS flash loader: Sectorization was not determined correctly when absolute addresses were used in SectorInfo. Fixed.
3. 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.
4. 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).
5. TI CC2340: Added debug and flash programming support (https://wiki.segger.com/TI_CC2340).
6. CVA BlueWhale CVM011x: Programming less data than a sector size could fail. Fixed.
7. CVA BlueWhale CVM011x: Allow programming the option byte area with the default flashloader.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. J-Link EDU Mini V1: Cortex-M: Added support for dormant --> SWD switching sequence.
11. J-Link EDU/BASE/PLUS V11: Cortex-M: Added support for dormant --> SWD switching sequence.
12. J-Link EDU/BASE/PLUS V12: Cortex-M: Added support for dormant --> SWD switching sequence.
13. J-Link ULTRA+ V5: Cortex-M: Added support for dormant --> SWD switching sequence.
14. J-Link ULTRA+ V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
15. J-Link ULTRA+ V6: Cortex-M: Added support for dormant --> SWD switching sequence.
16. J-Link PRO V5: Cortex-M: Added support for dormant --> SWD switching sequence.
17. J-Link PRO V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
18. J-Link PRO V6: Cortex-M: Added support for dormant --> SWD switching sequence.
19. J-Trace PRO V2 Cortex: Cortex-M: Added support for dormant --> SWD switching sequence.
20. J-Trace PRO V2 CortexM: Cortex-M: Added support for dormant --> SWD switching sequence.
21. J-Trace PRO V3 Cortex: Cortex-M: Added support for dormant --> SWD switching sequence.
22. J-Trace PRO V3 CortexM: Cortex-M: Added support for dormant --> SWD switching sequence.
23. Flasher ARM V5: Cortex-M: Added support for dormant --> SWD switching sequence.
24. Flasher ARM V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
25. Flasher PRO V5: Cortex-M: Added support for dormant --> SWD switching sequence.
26. Flasher PRO V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
27. Flasher PRO XL V5: Cortex-M: Added support for dormant --> SWD switching sequence.
28. Flasher PRO XL V5-1: Cortex-M: Added support for dormant --> SWD switching sequence.
29. Flasher Compact V5: Cortex-M: Added support for dormant --> SWD switching sequence.
30. Flasher Portable PLUS V5: Cortex-M: Added support for dormant --> SWD switching sequence.

Version V7.88b (2023-05-10)

DLL

1. Programming of RISC-V devices could fail because auto detection of CPU clock frequency is not supported. Fixed.
2. ST SR6G7: Added debug and flash programming support (https://wiki.segger.com/ST_SR6G7)
3. ISSI IS25LX512M, IS25WX512M: Under certain circumstances flash read could fail. Fixed.
4. Added support for command string "CORTEXM_SetNonCacheAwareDebugAHBAP" to workaround debug-related D-cache issues on some Cortex-M85 implementation.
5. ST STM32H5: Flash programming did not work with TrustZone enabled. Fixed.
6. Nuvoton M2354: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_M2354).
7. Nuvoton M2351: Flash programming could fail because of unpowered RAM used. Fixed.

Firmware

1. 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.
2. J-Link OB Apollo4-CortexM: Added WinUSB (driverless) mode support.
3. J-Link OB Apollo4-CortexM: Added auto-enable of WinUSB (driverless) mode support on first boot of OB.
4. J-Link OB RA4M2-Renesas: Added support for reboot command.
5. J-Link OB RA4M2-CortexM: Added support for reboot command.
6. J-Link OB RA4M2-RISCV: Added support for reboot command.
7. J-Link OB RA4M2-Full: Added support for reboot command.

GDB Server

1. 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

1. ISSI IS25LX512M, IS25WX512M: Under certain circumstances flash read could fail. Fixed.

Version V7.88a (2023-05-03)

DLL

1. STM32H5: xSCR_PG bit was set after programming. Fixed.

Firmware

1. MCU-Link-OB: Added support for CAdence / Tensilica Xtensa cores in NXP chips. (e.g. i.MX RT600 series devices)
2. MCU-Link: Added WinUSB (driverless) mode support.
3. MCU-Link-OB: Added WinUSB (driverless) mode support.
4. MCU-Link: Added auto-enable of WinUSB (driverless) mode support on first boot.
5. MCU-Link-OB: Added auto-enable of WinUSB (driverless) mode support on first boot.
6. LPC-Link2 on-board: Added support for Cadence / Tensilica Xtensa cores in NXP chips. (e.g. i.MX RT600 series devices)
7. LPC-Link2: Added support for WinUSB (driverless) mode.
8. LPC-Link2 on-board: Added support for WinUSB (driverless) mode.
9. LPC-Link2: Added auto-enable of WinUSB (driverless) mode on boot.
10. LPC-Link2 on-board: Added auto-enable of WinUSB (driverless) mode on boot.

Version V7.88 (2023-04-27)

Highlights:

Trace

1. 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

1. Configuration dialog: Removed elements for configuring obsolete feature "Eco logic".
2. Replaced "Unhide" dialog with "System settings" dialog.

DLL

1. HPMicro HPM62 family: Added debug and flash programming support (https://wiki.segger.com/HPMicro_HPM62).
2. TI MSPM0G Rev. PG2 devices: Verify after MAIN programming could fail under special circumstances. Fixed.
3. TI MSPM0L Rev. PG2 devices: Verify after MAIN programming could fail under special circumstances. Fixed.
4. 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.
5. J-Link DLL could crash when flash configuration is wrong. Fixed.
6. Renesas R9A02G020: Added debug and flash programming support.
7. MindMotion MM32F5287: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F5).
8. Renesas R9A06G150: Added debug and flash programming support.
9. Microchip SAM4S: Added debug and flash programming support for ATSAM4SD16BB and ATSAM4SD32BB
10. Broadcom BCM89107: Under special circumstances, flash programming > 16 MB could fail. Fixed.
11. Broadcom BCM89107: Added external QSPI flash programming support (address 0x08200000).
12. Infineon TLE986x/TLE987x: Flash programming could fail if NMIs were enabled. Fixed.
13. CVA BlueWhale CVM011x: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM011x).
14. ST SR6P6xx: Added flash programming support for CUT 1.0 devices/revisions.
15. Cypress S6J32x devices series: Under certain circumstances connect did not work. Fixed.
16. ST SR6P6: Core for DSPH was wrong. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.

J-Flash

1. J-Flash did not keep sector selection when using a different loader than the default loader. Fixed.
2. In some cases the sectorization in the Flash device info was displayed repetitive. Fixed.

J-Scope

1. Exporting CSV data for symbols within a struct did not use the extended symbol name. Fixed.

Version V7.86h (2023-04-12)

DLL

1. Alif Semiconductor AE3 series: Devices were no longer listed as supported / displayed in the device selection dialog. Introduced in V7.86g. Fixed.
2. Alif Semiconductor AE5 series: Devices were no longer listed as supported / displayed in the device selection dialog. Introduced in V7.86g. Fixed.

Firmware

1. 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.
2. 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

1. Project settings -> MCU: Renamed "Target RAM" to "J-Link Work RAM".
2. Project settings -> MCU: Added hyperlink to SEGGER Wiki explaining "J-Link Work RAM": https://wiki.segger.com/UM08003_JFlash#J-Link_Work_RAM_settings .

J-Scope

1. Trigger settings were not properly set when project was loaded. Fixed.

Version V7.86g (2023-04-06)

DLL

1. Cypress CYT4BF: Added flash programming support for supervisory flash.
2. NXP MIMXRT1041xxx6B, MIMXRT1042xxx5B: Added debug & QSPI flash programming support.
3. Renesas DA14592: Added QSPI flash programming support.
4. 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
5. 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
6. 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
7. 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
8. ST STM32H7Ax, STM32H7Bx: Set RAM base address used by J-Link to 0x24000000 (AXI SRAM).
9. J-Link script files: Added support for handling missing return statements at the end of non-void functions as errors. (No firmware change)
10. Programming could fail when ARMv8-M PSPLIM register was changed by application. Fixed.
11. NXP LPC55S36: Extended Device Support for A1 revision.
12. 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.
13. 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.
14. Under special circumstances RAMCode did not respond in time and programming flash failed. Fixed.
15. Trace: ETMv4: Stalling was enabled by default, by accident, which could result in intrusive trace. Fixed.
16. Trace: Added support for command string "TRACE_SetEnableStalling" (https://wiki.segger.com/J-Link_Command_Strings#TRACE_SetEnableStalling)

Firmware

1. Flasher PRO V5: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
2. Flasher PRO V5-1: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
3. Flasher PRO XL V5: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
4. Flasher PRO XL V5-1: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
5. Flasher Compact V5: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
6. Flasher Portable PLUS V1: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
7. Flasher Portable PLUS V5: Flasher did not throw an error in case max. number of flash banks was exceeded. Fixed.
8. Flasher PRO V5: Stand-alone: UFLASH: Added support for terminal command "#READ".
9. Flasher PRO V5-1: Stand-alone: UFLASH: Added support for terminal command "#READ".
10. Flasher PRO XL V5: Stand-alone: UFLASH: Added support for terminal command "#READ".
11. Flasher PRO XL V5-1: Stand-alone: UFLASH: Added support for terminal command "#READ".
12. Flasher Compact V5: Stand-alone: UFLASH: Added support for terminal command "#READ".
13. Flasher Portable PLUS V5: Stand-alone: UFLASH: Added support for terminal command "#READ".
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.

GDB Server

1. 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.
2. GDB Server could crash if GDB Server log file was enabled and a packet exceeding max. packet size was received. Fixed.

J-Flash SPI

1. Enable the temporary VTref before enabling power supply via J-Link as VTref is measured after enabling the power supply.

J-Scope

1. ELF file parsing could get stuck with certain ELF files. Fixed.
2. Symbols could get matched up incorrectly when loading a project causing duplicate entries. Fixed.

RTT

1. SEGGER_RTT_Syscalls_KEIL.c: Updated for usage with ARMCC V6.19.
2. 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

1. Reading / writing memory to the topmost address in the 32 bit region (0xFFFFFFFF) resulted in unexpected behavior. Fixed.
2. Added support for Greenhills ELF files.

DLL

1. CAST BA51 (RISC-V): Added debug support for CAST BA51 core. https://wiki.segger.com/CAST_BA51
2. CAST BA51 (RISC-V): Added CAST BA51 as a selectable device.
3. NXP i.MXRT1021 device series: Added support for A1 silicon devices.
4. Geehy APM32F415, APM32F417: Added debug and flash programming support.
5. Geehy APM32A407: Added debug and flash programming support.
6. Microchip ATSAME5x: Native unsecure on connect did not work correctly (introduced V7.82e). Fixed.
7. MindMotion MM32F0040: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F0).
8. Renesas RZ/T2L: Added debug and (QSPI) flash programming support (https://wiki.segger.com/Renesas_RZ/T2L).
9. Geehy APM32F105 / APM32F107: Added debug and flash programming support for internal flash and option bytes.
10. Geehy APM32S103: Added debug and flash programming support for internal flash and option bytes.
11. MindMotion MM32F0160: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F0).
12. MindMotion MM32G0141: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G0).
13. MindMotion MM32G0163: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G0).
14. MindMotion MM32L0020: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32L0).
15. MindMotion MM32L0131: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32L0).
16. MindMotion MM32L0136: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32L0).
17. MindMotion MM32A0144: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32A0).
18. MindMotion MM32SPIN0280: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32SPIN).
19. ST STM32WB: Merged "<DeviceName>" and "<DeviceName> (allow opt. bytes)"
20. 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
21. Geehy APM32A091: Added debug and flash programming support for internal flash and option bytes (https://wiki.segger.com/Geehy_APM32A0xx).
22. Geehy APM32A103: Added debug and flash programming support for internal flash and option bytes (https://wiki.segger.com/Geehy_APM32A1xx).
23. Renesas RX: In case of firmware does not support the current core architecture, multiple connects were issued. Fixed.
24. Added support for the Renesas RX13T core.
25. Renesas R5F513T3 (RX13T): Added debug & flash programming support.
26. Renesas R5F513T5 (RX13T): Added debug & flash programming support.
27. Added new J-Link Command String "SetVTrefTmp" (https://wiki.segger.com/J-Link_Command_Strings#SetVTrefTmp).

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. Flasher PRO V5: Added support for the Renesas RX13T core.
20. Flasher PRO V5-1: Added support for the Renesas RX13T core.
21. Flasher PRO XL V5: Added support for the Renesas RX13T core.
22. Flasher PRO XL V5-1: Added support for the Renesas RX13T core.
23. Flasher Compact V5: Added support for the Renesas RX13T core.
24. Flasher Portable PLUS V1: Added support for the Renesas RX13T core.
25. Flasher Portable PLUS V5: Added support for the Renesas RX13T core.
26. J-Link EDU Mini V1: Added support for the Renesas RX13T core.
27. J-Link EDU/BASE/PLUS V11: Added support for the Renesas RX13T core.
28. J-Link EDU/BASE/PLUS V12: Added support for the Renesas RX13T core.
29. J-Link ULTRA+ V5: Added support for the Renesas RX13T core.
30. J-Link ULTRA+ V5-1: Added support for the Renesas RX13T core.
31. J-Link ULTRA+ V6: Added support for the Renesas RX13T core.
32. J-Link PRO V5: Added support for the Renesas RX13T core.
33. J-Link PRO V5-1: Added support for the Renesas RX13T core.
34. J-Link PRO V6: Added support for the Renesas RX13T core.
35. J-Link WiFi V1: Added support for the Renesas RX13T core.

GDB Server

1. RTOSPlugin for FreeRTOS did not report correct task registers. Fixed.
2. Semihosting: SYS_WRITE0 failed when an empty string was passed. Fixed.
3. Semihosting: SYS_ISTTY did not return 1 for stdin. Fixed.
4. Semihosting: SYS_FLEN was not handling stdin handle correctly. Fixed.
5. Semihosting: Some unsupported commands were handled as errors instead of being handled as "unsupported". Fixed.
6. Semihosting: SYS_ISERROR was not marked as unsupported command, even though it is. Fixed.

J-Flash

1. 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.
2. Added support for Greenhills ELF files.
3. The "Enable VTref" production project setting could be enabled but was not supported in J-Flash mode (stand-alone mode only). Fixed.

J-Flash SPI

1. 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.
2. The "Enable VTref" production project setting could be enabled but was not supported in host mode (stand-alone mode only). Fixed.

J-Flash SPI CL

1. The "Enable VTref" production project setting could be enabled but was not supported in host mode (stand-alone mode only). Fixed.

J-Scope

1. Added support for class keyword.
2. J-Scope will now reparse ELF file on project load.
3. Arrays of structs did no longer display their names within the table widget. Introduct with V7.86d. Fixed.

Version V7.86e (2023-03-22)

Control Panel

1. 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

1. Infineon XMC7200: Added debug and flash programming support.
2. NucleiSys N900 RISC-V TAPs with TAPId == 0x10900A6D were not properly detected as RISC-V TAPs. Fixed.
3. Nuvoton NUC029FAE: Flash programming could fail because of wrong CPU clock settings. Fixed.
4. Nuvoton NUC029 Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
5. Texas Instruments TMS570LS device series: Added programming support for flash OTP and EEPROM OTP.
6. Renesas DA1459x device series: Changed eFlash base address from 0x00A00000 to 0x31000000.
7. Nuvoton NUC100/120 Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
8. NXP iMXRT117x: FlexSPI Flash programming did not work. Introduced with V7.86. Fixed.
9. Added support for Macronix MX25L4006E SPI flash to SPIFI-Lib.
10. 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)
11. Nuvoton NUC1262 series: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_NUC1262x).
12. Nuvoton M463/M467: Added debug and flash programming support (https://wiki.segger.com/Nuvoton_M46x).

Firmware

1. 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
2. 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
3. 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
4. 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.
5. 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.
6. 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-Flash

1. Stand-alone-mode programming did not work for the NXP MKL81/MKL82 series devices. Fixed.
2. Project settings dialog, flash page: Removed "Organization" label and drop down menu for non-CFI-NOR flashes.
3. 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.

J-Flash SPI

1. Added support for Macronix SPI flash MX25L4006E.

Version V7.86d (2023-03-15)

DLL

1. Infineon CY8C6xx, XMC7xxx devices: Chip erase caused J-Link to try to erase SMIF flash bank even if it is not present. Fixed.
2. Cortex-A35 based devices were detected as Cortex-A53. Fixed.
3. SiLabs EFM8: Added support for EFM8BB50 series devices: EFM8BB50F4G, EFM8BB50F4I, EFM8BB50F8G, EFM8BB50F8I, EFM8BB50F16G, EFM8BB50F16I.
4. Added printing of J-Link script file function execution time (e.g. execution time of InitTarget()) to J-Link log output.
5. ST STM32C0: Add device specific connect and native unlock functionality.
6. J-Link script files: Added support for adjacent string literals.
7. J-Link script files: If a string literal contained an unescaped newline character (\n), no error was thrown. Fixed.
8. User was not informed in case J-Link script file function "ResetTarget()" failed. Fixed.
9. Renesas RZ/T2L: BSC pins were erroneously initialized on connect. Fixed.
10. Nuvoton M051 Base Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
11. Nuvoton M051 Base Series: Data flash programming support added.
12. Nuvoton M0519 Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
13. Nuvoton M0519xDx: Data flash programming support added.
14. Nuvoton M0518 Series: Flash programming could fail because of wrong CPU clock settings. Fixed.
15. Nuvoton M0518 Series: Data flash programming support added.
16. Infineon TLE98xx devices series: Flash programming did not work when NMINVM bit was set. Fixed.
17. TI MSPM0G Rev. PG2 devices: NONMAIN programming did not work. Fixed.
18. TI MSPM0L Rev. PG2 devices: NONMAIN programming did not work. Fixed.

J-Flash

1. Project settings dialog, flash tab: SFL based flash banks with dynamic sector layout were erroneously displayed as having static sector layout. Fixed.

J-Scope

1. J-Scope RTT projects did not show previously active symbols on startup. Fixed.
2. J-Scope RTT projects did not have several actions like "Import raw" or "Start sampling" available on startup. Fixed.
3. Trigger symbol selection combobox was too small for many symbol names. Fixed.
4. Cursor time and timestamps were not displayed correctly when graph window size did not align with grid size. Fixed.
5. Member variables of structs or unions now show their parent struct variable name within the symbol table, graph tooltip and symbol trigger selection.
6. Under certain circumstances, J-Scope could crash. Fixed.

STM32 Utility

1. Added ST STM32C0.

Version V7.86c (2023-03-09)

Commander

1. Added optional timeout parameter to "Reboot" command (see: https://wiki.segger.com/J-Link_Commander#Reboot).
2. Added comand "Uptime" (see: https://wiki.segger.com/J-Link_Commander#Uptime).

Control Panel

1. General tab: Added J-Link uptime.
2. Settings tab: Ram download => Verify combobox was filling infinitely with the same two entries. Fixed.
3. Settings tab: Combobox entry selection used to flicker when hovering over them. Fixed.

DLL

1. ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): Added support for RTT and HSS via MEM-AP (AHB-AP, AXI-AP).
2. Hilscher NetX90: Added SQI(QSPI) flash programming support.
3. NXP K32W14x devices: Device reset did not work. Fixed.
4. NXP K32W14x devices: Connecting to the devices while no valid target application was on the device would fail. Fixed.
5. NXP S32K311: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx)
6. Renesas RZ/T2M: Added support for RTT and HSS via AXI-AP.
7. 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
8. NXP LPC55xx devices: SWO would not work correctly when SWO was initialized from within the target application. Fixed.
9. Atmosic ATM333x devices: Added flash programming support for revision B0 silicon.
10. Realtek RTL872xDx devices: Added debug and flash programming support(https://wiki.segger.com/Realtek_Ameba_D).
11. ST STM32H5 device series: Added debug and flash programming support for internal and QSPI flash. For more information: https://wiki.segger.com/ST_STM32H5
12. Added OTP memory bank to STM32F42x series devices.
13. Microchip PIC32CM LS/LE devices: Added debug and flash programming support(https://wiki.segger.com/Microchip_PIC32CM_Lx).
14. JLinkDevicesXML: FlashBankInfo in old format (without LoaderInfo) and with spaces in flash bank name attribute was not handled correctly by J-Link DLL. Fixed.
15. 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.
16. Renesas DA1459x: Added debug and flash programming support for eFlash.

Firmware

1. 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)
2. J-Link EDU Mini V1: Implemented ARMv8-A/R firmware module V9.
3. J-Link EDU/BASE/PLUS V11: Implemented ARMv8-A/R firmware module V9.
4. J-Link EDU/BASE/PLUS V12: Implemented ARMv8-A/R firmware module V9.
5. J-Link ULTRA+ V5: Implemented ARMv8-A/R firmware module V9.
6. J-Link ULTRA+ V5-1: Implemented ARMv8-A/R firmware module V9.
7. J-Link ULTRA+ V6: Implemented ARMv8-A/R firmware module V9.
8. J-Link PRO V5: Implemented ARMv8-A/R firmware module V9.
9. J-Link PRO V5-1: Implemented ARMv8-A/R firmware module V9.
10. J-Link PRO V6: Implemented ARMv8-A/R firmware module V9.
11. J-Link WiFi V1: Implemented ARMv8-A/R firmware module V9.
12. J-Link OB-S124: Implemented ARMv8-A/R firmware module V9.
13. J-Link Lite-S124: Implemented ARMv8-A/R firmware module V9.
14. Flasher ARM V5: Implemented ARMv8-A/R firmware module V9.
15. Flasher ARM V5-1: Implemented ARMv8-A/R firmware module V9.
16. Flasher PRO V5: Implemented ARMv8-A/R firmware module V9.
17. Flasher PRO V5-1: Implemented ARMv8-A/R firmware module V9.
18. Flasher PRO XL V5: Implemented ARMv8-A/R firmware module V9.
19. Flasher PRO XL V5-1: Implemented ARMv8-A/R firmware module V9.
20. Flasher Compact V5: Implemented ARMv8-A/R firmware module V9.
21. Flasher Portable PLUS V1: Implemented ARMv8-A/R firmware module V9.
22. Flasher Portable PLUS V5: Implemented ARMv8-A/R firmware module V9.
23. J-Trace PRO V2 Cortex: Implemented ARMv8-A/R firmware module V9.
24. J-Trace PRO V3 Cortex: Implemented ARMv8-A/R firmware module V9.
25. Renesas RX firmware module V2: RTT: RTT did stop working after app. 24 days of J-Link uptime. Fixed.
26. J-Trace PRO V3 Cortex: Implemented Renesas RX firmware module V2.
27. J-Link EDU Mini V1: Implemented Renesas RX firmware module V2.
28. J-Link EDU/BASE/PLUS V11: Implemented Renesas RX firmware module V2.
29. J-Link EDU/BASE/PLUS V12: Implemented Renesas RX firmware module V2.
30. J-Link ULTRA+ V5: Implemented Renesas RX firmware module V2.
31. J-Link ULTRA+ V5-1: Implemented Renesas RX firmware module V2.
32. J-Link ULTRA+ V6: Implemented Renesas RX firmware module V2.
33. J-Link PRO V5: Implemented Renesas RX firmware module V2.
34. J-Link PRO V5-1: Implemented Renesas RX firmware module V2.
35. J-Link PRO V6: Implemented Renesas RX firmware module V2.

GDB Server

1. FreeRTOS plugin: Threads that are created before the scheduler is running are now marked as "Ready" to prevent confusion.
2. Semihosting: SYS_ERRNO often did not return an error code in case an error occurred. Fixed.
3. Semihosting: Write operations now also accept handle 2 (stderr), which is routed to the Semihosting TELNET-channel.
4. Semihosting: Implemented functionality for SEGGER command extension SYS_IS_CONNECTED (0x00).
5. 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).
6. ARMv7-A/R (e.g. Cortex R5, Cortex-A9, ...): R8-R12 of current mode were displayed incorrectly. Introduced in V7.84e. Fixed.
7. ARMv8-A/R AArch32 (e.g. Cortex R52): R8-R12 of current mode were displayed incorrectly. Introduced in V7.84e. Fixed.

Version V7.86b (2023-03-01)

Commander

1. Added command "w8" to write 64-bit items. (https://wiki.segger.com/J-Link_Commander#Write8)

DLL

1. ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): Added support for zoned memory access (CPU, AXI-AP, ...).
2. Added J-Link script file API function JLINK_MEM_FillEx().
3. Renesas DA1470x: Added debug and QSPI flash programming support.
4. ST SR6P6/SR6P7: Flashing of UTEST area failed. Introduced in V7.86a. Fixed.
5. ST SR6P6/SR6P7: Updated naming of flash banks.
6. 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)
7. Qorvo QM3572x device series: Under certain circumstances flash programming could fail. Fixed.
8. Qorvo QPG5071G / QPG5072: Increased the delay after releasing the reset pin as part of the device specific connect sequence.
9. Qorvo QPG6095x / QPG6100x / QPG6105: Increased the delay after releasing the reset pin as part of the device specific connect sequence.
10. Qorvo GP570xxx: Increased the delay after releasing the reset pin as part of the device specific connect sequence.
11. NXP S32K3xx: Under special circumstances, flash programming (erase / program) did not work. Fixed.
12. NXP S32K3xx: Improved device specific connect to print more detailed information regarding the HSM firmware.

Firmware

1. ARMv8-A/R firmware module V8 (e.g. Cortex-A53, Cortex-R52): Added support for zoned memory access (CPU, AXI-AP, ...).
2. J-Link EDU Mini V1: Implemented ARMv8-A/R firmware module V8.
3. J-Link EDU/BASE/PLUS V11: Implemented ARMv8-A/R firmware module V8.
4. J-Link EDU/BASE/PLUS V12: Implemented ARMv8-A/R firmware module V8.
5. J-Link ULTRA+ V5: Implemented ARMv8-A/R firmware module V8.
6. J-Link ULTRA+ V5-1: Implemented ARMv8-A/R firmware module V8.
7. J-Link ULTRA+ V6: Implemented ARMv8-A/R firmware module V8.
8. J-Link PRO V5: Implemented ARMv8-A/R firmware module V8.
9. J-Link PRO V5-1: Implemented ARMv8-A/R firmware module V8.
10. J-Link PRO V6: Implemented ARMv8-A/R firmware module V8.
11. J-Link WiFi V1: Implemented ARMv8-A/R firmware module V8.
12. J-Link OB-S124: Implemented ARMv8-A/R firmware module V8.
13. J-Link Lite-S124: Implemented ARMv8-A/R firmware module V8.
14. Flasher ARM V5: Implemented ARMv8-A/R firmware module V8.
15. Flasher ARM V5-1: Implemented ARMv8-A/R firmware module V8.
16. Flasher PRO V5: Implemented ARMv8-A/R firmware module V8.
17. Flasher PRO V5-1: Implemented ARMv8-A/R firmware module V8.
18. Flasher PRO XL V5: Implemented ARMv8-A/R firmware module V8.
19. Flasher PRO XL V5-1: Implemented ARMv8-A/R firmware module V8.
20. Flasher Compact V5: Implemented ARMv8-A/R firmware module V8.
21. Flasher Portable PLUS V1: Implemented ARMv8-A/R firmware module V8.
22. Flasher Portable PLUS V5: Implemented ARMv8-A/R firmware module V8.
23. J-Trace PRO V2 Cortex: Implemented ARMv8-A/R firmware module V8.
24. J-Trace PRO V3 Cortex: Implemented ARMv8-A/R firmware module V8.
25. Flasher ARM V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
26. Flasher ARM V5-1: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
27. Flasher PRO V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
28. Flasher PRO V5-1: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
29. Flasher PRO XL V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
30. 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.
31. Flasher Compact V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
32. Flasher Portable PLUS V1: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.
33. Flasher Portable PLUS V5: Stand-alone mode: When using batch mode, FLASHER.ini file handle was not closed properly after last job completed. Fixed.

GDB Server

1. GDB Server was closed with error message if IPv6 was disabled on the host system. Fixed.

J-Flash

1. In the command line no space was allowed between options and parameters. Both variants are now possible.
2. Adapted project settings dialog to be resizeable.
3. Added sectorization information to project settings dialog flash page.

J-Flash SPI

1. In the command line no space was allowed between options and parameters. Both variants are now possible.

Version V7.86a (2023-02-22)

Commander

1. When listing available memory zones for a connected target, the zone name was not surrounded quotation marks. Fixed.

DLL

1. Cortex-M7: D-cache was not properly handled on debugger memory accesses (Could lead to local / global variables to show old values). Fixed.
2. NXP Kinetis family: User JTAG chain selection was ignored for some devices. Fixed.
3. Cypress CYT3, CYT4: DCache was not correctly invalidated. Fixed.
4. NXP Kinetis Series, iMXRT Series: DCache was not correctly invalidated. Fixed.
5. ST STM32H7 Series, STM32F7 Series: DCache was not correctly invalidated. Fixed.
6. ST STM32L4: Added multiple loader support for single bank/dual bank configuration.
7. Infineon(Fujitsu) CY9BF121J(MB9BF121J): Internal flashbank size too big. Fixed.
8. ST STM32L4R: Added multiple loader support for single bank/dual bank configuration.
9. Cortex-A35: Auto detection did not work. Fixed.
10. Added "Cortex-A35" as generic device name to the device selection dialog.
11. TI MSPM0G: Added NONMAIN flash programming support for PG2 revision.
12. TI MSPM0L: Added NONMAIN flash programming support for PG2 revision.
13. J-Link script files: Added output of execution time in [ms] on a successful call to a script file function (e.g. InitTarget()).
14. Analog ADuCM342: Added debug & flash programming support.
15. Cortex-M ARMv8-M (e.g. Cortex-M33): Cache info was not output even if core implemented CPU cache. Fixed.

Firmware

1. Flasher ARM V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
2. Flasher ARM V5-1: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
3. Flasher PRO V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
4. Flasher PRO V5-1: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
5. Flasher PRO XL V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
6. Flasher PRO XL V5-1: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
7. Flasher Compact V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
8. Flasher Portable PLUS V1: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
9. Flasher Portable PLUS V5: Stand-alone mode: Added support for SPI EEPROM CFG files generated by J-Flash SPI.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. 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.
30. 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.
31. 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.
32. 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.
33. 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.
34. 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.
35. 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.
36. 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.
37. Flasher ARM V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
38. Flasher ARM V5-1: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
39. Flasher PRO V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
40. Flasher PRO V5-1: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
41. Flasher PRO XL V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
42. Flasher PRO XL V5-1: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
43. Flasher Compact V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.
44. Flasher Portable PLUS V5: Stand-alone mode: STM8 SWIM interface: Reset pin was not released in case connect to target failed. Fixed.

GDB Server

1. Semihosting: SYS_WRITE0 call was not working correctly and could potentially cause a GDB Server crash. Introduced in V7.68b. Fixed.
2. Semihosting: SYS_WRITEC: Always returned error. Introduced in V7.68b. Fixed.
3. Semihosting: SYS_WRITE: Always returned error. Introduced in V7.68b. Fixed.
4. 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.

J-Flash

1. 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

1. Added support for SPI EEPROM.
2. EEPROM: Added support for Microchip AT25320, AT25640, AT25128, AT25256, AT25512.

Version V7.86 (2023-02-15)

Control Panel

1. Improved sectorization output in <Flash> tab.

DLL

1. S32K3xx: When HSE is installed and used erasing and programming could fail. Fixed.
2. TLE98xx: Ram check failed during erase or program. Fixed.
3. Renesas RZT2: Added flash Parallel CFI NOR flash support for bank @0x70000000.
4. NXP iMXRT117x: Debug connection would fail when debugging both Cortex-M4 and Cortex-M7 cores and performing a reset via Cortex-M7. Fixed.
5. SFL XML: Added support for attribute "Sectorization" in <LoaderInfo> tag.
6. 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)
7. Analog Devices ADuCM430 series: Added debug and flash programming support (https://wiki.segger.com/Analog_ADuCM430).
8. ST STM32MP13: Added debug support.
9. Renesas RX66N and RX72N: The DLL erroneously detected / reported a core mismatch ("Identified core does not match configuration"). Fixed.
10. NXP LPC55Sxx: Reset did not check secure flash for valid boot image, only non-secure flash. Fixed.
11. NXP LPC55Sxx: Erase function mistakenly erased one more sector than desired. Fixed.
12. Syntacore SCR (RISC-V): Added JTAG TAP IDCODEs for SCR3, SCR4, SCR5, SCR6, SCR7 to the list of known TAP Ids.
13. Syntacore SCR (RISC-V): Added debug support for SCR4 (RV32+RV64), SCR5 (RV32+RV64), SCR6, SCR7.
14. Renesas RA4E2: Added debug and flash programming support (https://wiki.segger.com/Renesas_RA4E2).
15. Renesas RA6E2: Added debug and flash programming support (https://wiki.segger.com/Renesas_RA6E2).
16. Trace: Under certain circumstances conditional jumps with RISC-V Nexus Trace might be counted incorrectly. Fixed.
17. ST SR6P6: Added debug and flash programming support (https://wiki.segger.com/ST_SR6P6).
18. Added support for the following Adesto SPI flashes AT25EU0011A, AT25EU0021A, AT25EU0021A to SPIFI-Lib.
19. Added support for the following Micron SPI flashes MT35XL01GCBA, MT35XL02GCBA to SPIFI-Lib.
20. Nations N32G03x: Added debug and flash programming support (https://wiki.segger.com/Nations_N32G03x).
21. Nations N32G4xx: Added debug and flash programming support (https://wiki.segger.com/Nations_N32G4xx).
22. Nations N32WB4xx: Added debug and flash programming support (https://wiki.segger.com/Nations_N32WB4xx).
23. Nations N32L4xx: Added debug and flash programming support (https://wiki.segger.com/Nations_N32L4xx).
24. ST SR6P7G7: Wrong CodeID displayed. Fixed.
25. ST SR6P7G7: Erase did not triger writing 0xFFs to flash. Fixed.

GDB Server

1. Added support for "-version" command line option. https://wiki.segger.com/J-Link_GDB_Server#-version

J-Flash

1. Removed the option to program external parallel (CFI compliant) NOR flashes without the usage of RAM (https://wiki.segger.com/CFI_Flash#J-Flash).
2. 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)
3. New project dialog: Moved "Flash banks" table below "Target interface" and "Speed" group boxes.
4. New project dialog: Depending on the display scaling, the "Flash banks" table would be smaller than it should. Fixed.
5. New project dialog: Dialog can now be resized by the user.

J-Flash SPI

1. Added support for the following Adesto SPI flashes: AT25EU0011A, AT25EU0021A, AT25EU0021A.
2. Added support for the following Micron SPI flashes: MT35XL01GCBA, MT35XL02GCBA.

Version V7.84f (2023-02-07)

DLL

1. ST SR5E1: Added debug support for second core.
2. 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.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. Flasher ARM V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
11. Flasher ARM V5-1: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
12. Flasher PRO V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
13. Flasher PRO V5-1: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
14. Flasher PRO XL V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
15. Flasher PRO XL V5-1: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
16. Flasher Compact V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
17. Flasher Portable PLUS V1: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
18. Flasher Portable PLUS V5: Stand-alone mode: Added support for script file API call of command string "SetcJTAGInitMode".
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. Flasher ARM V5: Stand-alone mode: Added support for RISC-V based MCUs.
29. Flasher ARM V5-1: Stand-alone mode: Added support for RISC-V based MCUs.
30. Flasher PRO V5: Stand-alone mode: Added support for RISC-V based MCUs.
31. Flasher PRO V5-1: Stand-alone mode: Added support for RISC-V based MCUs.
32. Flasher PRO XL V5: Stand-alone mode: Added support for RISC-V based MCUs.
33. Flasher PRO XL V5-1: Stand-alone mode: Added support for RISC-V based MCUs.
34. Flasher Compact V5: Stand-alone mode: Added support for RISC-V based MCUs.
35. Flasher Portable PLUS V5: Stand-alone mode: Added support for RISC-V based MCUs.
36. 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.
37. 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.
38. 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.
39. 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.
40. 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.
41. 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.
42. 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.
43. 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.

J-Flash

1. 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.
2. J-Flash did not display more than 8 internal flash banks. Fixed.
3. 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.

Version V7.84e (2023-02-01)

DLL

1. NordicSemi nRF53: When programming the UICR area, the software reported an verification error. Fixed.
2. NXP MWCT2S: Added debug and flash programming support.
3. NXP S32K3xx: Added RAM initialization for the SRAM0 region (https://wiki.segger.com/NXP_S32K3xx#RAM).
4. NXP S32K322 / S32K324: Added debug support for the secondary Cortex-M7 core (https://wiki.segger.com/NXP_S32K3xx#Multi-Core_Support).
5. Maxim MAX32570: QSPI flash programming did not restore device to the same state as before flash operation. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. Flasher Compact V5: Stand-alone mode: Some target interface pins were still driven after programming was complete. Fixed.
19. Flasher Portable PLUS V5: Some target interface pins were still driven after programming was complete. Fixed.
20. J-Link OB RA4M2-CortexM: VCOM: Added hardware flow control support option.
21. J-Link OB RA4M2-RISCV: VCOM: Added hardware flow control support option.
22. J-Link OB RA4M2-Full: VCOM: Added hardware flow control support option.

GDB Server

1. 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.
2. ARMv8-A/R: AArch32 (e.g. Cortex-R52): Added support for floating point registers fpscr, fpexc, fpsid, mvfr0-2, s0-s31, d0-d31.
3. ARMv8-A/R: Added auto-detection of core execution state (AArch64 / AArch32) and register set selection on connect.
4. Semihosting: SYS_WRITE/printf: When printing lines it could happen that the last 5 characters were printed twice. Introduced in V7.68a. Fixed.
5. GDB Server exited and did not wait for a new connection after connection was closed. Fixed.

J-Flash

1. New project dialog: Added checkbox to enable/ disable flash banks at project creation.
2. 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

1. Microchip ATSAMDxxx, ATSAMExxx: QSPI flash bank was erroneously assumed to be always present. Fixed.
2. Renesas RA-series: Under certain circumstances determining TrustZone configuration on connect did not work. Fixed.
3. 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.
4. ST STM32H7: For some devices, a slightly wrong factory value was programmed to FLASH_OPTSR, in case device security was set. Fixed.
5. Renesas RA-series: Low power mode was not restored on disconnect. Fixed.
6. Renesas RA6M4: QSPI flash programming did not work. Fixed.

Firmware

1. Flasher Package: Installer: Linux: Multiple sample files were missing. Fixed.
2. Flasher Package: Installer: Linux: Debain Package + Archive: GUI folder was missing. Fixed.

J-Link Package

1. Installer: Linux: Multiple sample files were missing. Fixed.
2. 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

1. 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

1. 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

1. 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

1. Debug tab: Some values were displayed under the wrong section. Fixed.

DLL

1. Nuvoton M071x: Added debug & flash programming support (https://wiki.segger.com/Nuvoton_M071x).
2. Nuvoton M26x: Added debug & flash programming support (https://wiki.segger.com/Nuvoton_M26x).
3. Nuvoton M471x: Added debug & flash programming support (https://wiki.segger.com/Nuvoton_M471x).
4. Firmware update dialog: An exclamation mark icon was displayed instead of the intended question mark icon. Fixed.
5. 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.
6. The J-Link DLL refused to work with some older J-Link BASE V9 units. Fixed.
7. ST STM32C0: Added debug & flash programming support (https://wiki.segger.com/ST_STM32C0).
8. ST BlueNRG-LPS: Added debug and flash programming support.
9. 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.
10. Nuvoton M031xB/M031xC/M031xD/M031xE: Flash programming did not work. Fixed.
11. NXP iMXRT117x: Detecting FlexSPI2 boot config and booting from FlexSPI2 did not work. Fixed.
12. NXP LPC55S69: Remapping of the device names "LPC55S69_core0" and "LPC55S69_core1" was incorrect resulting in wrong flash bank information were assumed. Fixed.
13. Xilinx Zynq-7000: Added optional flash loader with PLL initialization. For more information, see https://wiki.segger.com/Xilinx_Zynq-7000
14. 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.

Firmware

1. J-Link-OB-K22-CortexA: Added support for SWD multi-drop to firmware.
2. J-Link-OB-K22-CortexM: Added support for SWD multi-drop to firmware.
3. J-Link-OB-K22-RISCV: Added support for SWD multi-drop to firmware.
4. 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.
5. 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.
6. J-Link ULTRA+ V5: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
7. J-Link ULTRA+ V5-1: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
8. J-Link ULTRA+ V6: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
9. J-Link PRO V5: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
10. J-Link PRO V5-1: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
11. J-Link PRO V6: Eco mode: Modes "Eco Plus" and "Eco Max" re-enabled. Did not work properly before. Fixed.
12. Flasher Portable PLUS V1: UniversalFlasher: unierror.log: For parameterized log outputs, the value after the message was missing. Fixed.
13. Flasher Portable PLUS V5: UniversalFlasher: unierror.log: For parameterized log outputs, the value after the message was missing. Fixed.
14. J-Link EDU/BASE/PLUS V11: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
15. J-Link EDU/BASE/PLUS V12: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
16. J-Link ULTRA+ V5: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
17. J-Link ULTRA+ V5-1: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
18. J-Link ULTRA+ V6: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
19. J-Link PRO V5: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
20. J-Link PRO V5-1: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
21. J-Link PRO V6: Standby mode: Fruther reduced LED intensity in standby mode + normal (no Eco) mode active to save more power.
22. J-Link EDU/BASE/PLUS V11: Standby mode: Further reduced power consumption.
23. J-Link EDU/BASE/PLUS V12: Standby mode: Further reduced power consumption.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. 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.
30. 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.
31. 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.
32. 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.
33. Flasher ARM V5: Added optional output of the DAT file CRC value to the terminal interface after programming.
34. Flasher ARM V5-1: Added optional output of the DAT file CRC value to the terminal interface after programming.
35. Flasher PRO V5: Added optional output of the DAT file CRC value to the terminal interface after programming.
36. Flasher PRO V5-1: Added optional output of the DAT file CRC value to the terminal interface after programming.
37. Flasher PRO XL V5: Added optional output of the DAT file CRC value to the terminal interface after programming.
38. Flasher PRO XL V5-1: SFL: Added optional output of the DAT file CRC value to the terminal interface after programming.
39. Flasher Compact V5: SFL: Added optional output of the DAT file CRC value to the terminal interface after programming.
40. 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.
41. 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.
42. 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.
43. 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.
44. 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.
45. 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.
46. 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.
47. 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.

J-Flash

1. 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.
2. 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.
3. Warning and error messages in the log window are now colored.

Version V7.84b (2023-01-11)

Commander

1. Calling exec functions with Windows 32-bit version could cause J-Link Commander to crash. Introduced with V7.82c. Fixed.

DLL

1. NXP i.MXRT104x device family: Added debug & flash programming (FlexSPI) support.
2. Increased verbosity of error messages if target RAM could not be preserved.
3. NXP KW45: Added debug & flash programming support (https://wiki.segger.com/NXP_KW45).
4. NXP K32W14: Added debug & flash programming support (https://wiki.segger.com/NXP_K32W14).
5. Maxim MAX32570: Added QSPI flash programming support.
6. Trace: Added warning in case an execution address not covered by the trace cache is accessed/traced (referenced by received trace data).

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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

1. 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

1. Improved startup-dialog to include a list of recently used projects.
2. Added -RTTSearchRanges command line option.
3. Added checkbox to symbol table for toggling symbol visibility.

Version V7.84a (2022-12-22)

DLL

1. 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.
2. Renesas RZ/G2UL: Added debug support for R9A07G043U12 and R9A07G043U11.
3. Infineon CY8C6xxx, CYB06xxx, CYW20829xx device series: Updated 3rd party support package provided by Infineon.
4. Infineon XMC7100 device series: Added 3rd party support package provided by Infineon.

Firmware

1. J-Link ULTRA+ V5: Eco Plus mode handling temporarily disabled.
2. J-Link ULTRA+ V5-1: Eco Plus mode handling temporarily disabled.
3. J-Link ULTRA+ V6: Eco Plus mode handling temporarily disabled.
4. J-Link PRO V5: Eco Plus mode handling temporarily disabled.
5. J-Link PRO V5-1: Eco Plus mode handling temporarily disabled.
6. J-Link PRO V6: Eco Plus mode handling temporarily disabled.

Version V7.84 (2022-12-14)

DLL

1. Renesas RZ/G2L: Updated list of supported device names.
2. Renesas RZ/G2LC: Updated list of supported device names.
3. Added support for ARM Cortex-R52+ (Handled as Cortex-R52).
4. Option byte support disabled for GigaDevice GD32A50x devices due to customers request.
5. ST STM32F74x/STM32F75x: Wrong loader was selected as default for QSPI flash bank. Fixed.
6. ST STM32F7: Added QSPI flash programming support for pin configuration CLK@PF10_nCS@PB10_D0@PF8_D1@PF9_D2@PF7_D3@PF6.
7. AUCU AU3x device series: Updated 3rd party support package provided by AUCU.
8. ST STM32H7 device series: For devices with internal flash of 512 KB or less, removing write protection did not work properly. Fixed.
9. ST STM32H7 device series: Erasing entire internal flash did not work. Fixed.
10. Added debug & flash programming support for ST STM32F723VC.
11. NXP KW45: Decreased the initial connect time by improving the device specific connect sequence.

Firmware

1. 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.
2. J-Link EDU Mini V1: Implemented ARMv8-A/R firmware module V7.
3. J-Link EDU/BASE/PLUS V11: Implemented ARMv8-A/R firmware module V7.
4. J-Link EDU/BASE/PLUS V12: Implemented ARMv8-A/R firmware module V7.
5. J-Link ULTRA+ V5: Implemented ARMv8-A/R firmware module V7.
6. J-Link ULTRA+ V5-1: Implemented ARMv8-A/R firmware module V7.
7. J-Link ULTRA+ V6: Implemented ARMv8-A/R firmware module V7.
8. J-Link PRO V5: Implemented ARMv8-A/R firmware module V7.
9. J-Link PRO V5-1: Implemented ARMv8-A/R firmware module V7.
10. J-Link PRO V6: Implemented ARMv8-A/R firmware module V7.
11. J-Link WiFi V1: Implemented ARMv8-A/R firmware module V7.
12. J-Link OB-S124: Implemented ARMv8-A/R firmware module V7.
13. J-Link Lite-S124: Implemented ARMv8-A/R firmware module V7.
14. Flasher ARM V5: Implemented ARMv8-A/R firmware module V7.
15. Flasher ARM V5-1: Implemented ARMv8-A/R firmware module V7.
16. Flasher PRO V5: Implemented ARMv8-A/R firmware module V7.
17. Flasher PRO V5-1: Implemented ARMv8-A/R firmware module V7.
18. Flasher PRO XL V5: Implemented ARMv8-A/R firmware module V7.
19. Flasher PRO XL V5-1: Implemented ARMv8-A/R firmware module V7.
20. Flasher Compact V5: Implemented ARMv8-A/R firmware module V7.
21. Flasher Portable PLUS V5: Implemented ARMv8-A/R firmware module V7.
22. J-Link EDU/BASE/PLUS V11: Implemented LED dimming in Standby mode.
23. J-Link EDU/BASE/PLUS V12: Implemented LED dimming in Standby mode.
24. J-Link ULTRA+ V5: Implemented LED dimming in Standby mode.
25. J-Link ULTRA+ V5-1: Implemented LED dimming in Standby mode.
26. J-Link ULTRA+ V6: Implemented LED dimming in Standby mode.
27. J-Link PRO V5: Implemented LED dimming in Standby mode.
28. J-Link PRO V5-1: Implemented LED dimming in Standby mode.
29. J-Link PRO V6: Implemented LED dimming in Standby mode.
30. 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.
31. 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.
32. 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.
33. 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.
34. 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.
35. 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-Flash

1. Added debug & flash programming support for ST STM32F723VC.

Version V7.82f (2022-12-08)

Configurator

1. 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

1. Commands "Write1", "Write2", "Write4": Added support for 64bit addresses.
2. Commands "Mem", "Mem8", "Mem16", "Mem32": Added support for 64bit addresses.
3. Commands "SaveBin", "VerifyBin": Added support for 64bit addresses.

Configurator

1. Configuration Dialog: Added elements to configure J-Link LPM for models that support the feature (https://wiki.segger.com/J-Link_LPM).

DLL

1. Added Debug & Flash support for Mindmotion MM32F0xx Family (https://wiki.segger.com/MindMotion_MM32F0).
2. Added Debug & Flash support for Mindmotion MM32F3xx Family (https://wiki.segger.com/MindMotion_MM32F3).
3. NXP PN7642: Added debug & flash programming support.
4. NXP LPC55S14: Device did no longer support secure flash bank. Introduced with V7.82d. Fixed.
5. Updated vendor name from "Micronas" to "TDK-Micronas".
6. 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.
7. On slow SPI flashes restoring target state could fail. Fixed.
8. Infineon CY8C6xxx: For some devices of the series WFLASH size was mistakenly defined as 2 KB instead of 32 KB. Fixed.
9. Renesas RA device series: Several devices had a wrong default loader set. Fixed.
10. Renesas RA device series: Added some additional QSPI flash loader pin configurations for several devices.
11. Added flash programming support for TI MSPM0G (https://wiki.segger.com/TI_MSPM0G#NONMAIN).
12. Added flash programming support for TI MSPM0L (https://wiki.segger.com/TI_MSPM0L#NONMAIN).
13. NXP S32K312: Flash programming didn't work for last 10 sectors if HSE was active. Fixed.

Firmware

1. J-Link-OB-XMC4200: Added support for ARM Cortex-M23, Cortex-M33 cores.
2. XMC Link: Added support for ARM Cortex-M23, Cortex-M33 cores.
3. 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)
4. 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)
5. 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)
6. 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)
7. J-Link-OB-XMC4200: VCOM: Added support generating BREAK condition over terminal application.
8. XMC Link: VCOM: Added support generating BREAK condition over terminal application.

Version V7.82d (2022-11-23)

Commander

1. On some Probes, the "Reboot" command failed, even though it was supported by the probe. Fixed.

DLL

1. Renesas RA6M3: Created a wiki article (https://wiki.segger.com/Renesas_RA6M3).
2. Added J-Link script file API function JLINK_RISCV_DMI_ReadRegMultiple(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
3. Added J-Link script file API function JLINK_RISCV_DMI_WriteRegMultiple(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
4. Added J-Link script file API function JLINK_RISCV_DMI_WriteReg(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
5. Added J-Link script file API function JLINK_RISCV_DMI_ReadReg(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
6. Added J-Link script file API function JLINK_RISCV_DMI_ClearState(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
7. Added J-Link script file API function JLINK_RISCV_DMI_AutodetectDMISettings(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
8. Added J-Link script file API function JLINK_RISCV_DMI_SetDMISettings(). https://wiki.segger.com/J-Link_script_files#Script_file_API_functions
9. Added JTAG TAPId 0x06413B47 (Geehy APM32 Boundary Scan) to the list of known TAPIDs.
10. NXP LPC55xx/LPC55Sxx: Some non-secure devices mistakenly supported the secure flash bank while their secure counterpart did not. Fixed.
11. NXP i.MXRT117x: Added flash programming support for FlexSPI 2 flash bank.
12. NXP S32K3xx: Can't flash within last flash block when HSE (Hardware Secure Engine) is activated. Fixed.
13. ST STM32WL5/WLE: Added device specific connect and native unlock functionality.
14. Infineon S6E2C series: Updated RAM addresses and sizes. Fixed.
15. Added JTAG TAPId 0x10999A6D (NucleiSys N900) to the list of known TAPIDs.
16. Added JTAG TAPId 0x10900A6D (NucleiSys N900) to the list of known TAPIDs.
17. ST STM32 devices: Under rare circumstances, connecting to the devices under reset could fail when the device was running in low power mode. Fixed.
18. 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.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. J-Link ULTRA+ V5: VCOM: STOP bit settings from host terminal were ignored. Fixed.
10. J-Link ULTRA+ V5-1: VCOM: STOP bit settings from host terminal were ignored. Fixed.
11. J-Link PRO V5: VCOM: STOP bit settings from host terminal were ignored. Fixed.
12. J-Link PRO V5-1: VCOM: STOP bit settings from host terminal were ignored. Fixed.

STM32 Utility

1. Added ST STM32WB and STM32WL5/WLE.

Version V7.82c (2022-11-16)

Commander

1. 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

1. Geehy APM32 devices: Size of option bytes flash bank was not correctly displayed in device selection dialog. Fixed.
2. ST STM32WB55: Stand-alone programming of option bytes was not possible due to a padding problem in the Flasher data file. Fixed.
3. ST STM32WL55: Stand-alone programming of option bytes was not possible due to a padding problem in the Flasher data file. Fixed.
4. Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
5. CMSemicon BAT32G133: Added debug & flash programming support (https://wiki.segger.com/CMSemicon_BAT32G133).
6. CMSemicon BAT32G157: Added debug & flash programming support (https://wiki.segger.com/CMSemicon_BAT32G157).
7. SEGGER Flash Loader (SFL): Under special circumstances, erase timeout was calculated incorrectly in case of multi sector erase was performed. Fixed.
8. NXP LPC55x3x: Added FLEXSPI flash programming support.
9. Some J-Link features were not enabled for the J-Link OB-nRF5340-NordicSemi. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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
7. 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

GDB Server

1. Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.

J-Flash

1. J-Flash did not work properly for devices with flash banks that had more than 8192 sectors. Fixed.
2. Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.
3. 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

1. Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.

J-Scope

1. Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.

JTAG Load

1. Fixed typo in ExecFREQUENCY() output.

RTT Viewer

1. Device selection dialog: Pressing <Return> to select a device when the table was not in focus did not work. Fixed.

SWO Viewer

1. 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

1. Renesas RA4E1, RA4M2, RA4M3, RA6E1, RA6M4, RA6M5, RA6T2: Under certain circumstances connect via JTAG did not work. Fixed.
2. Renesas RA4T1 / RA6T3: Removed IDCode authentication support for now because we do not have a valid indicator to determine the current security status.
3. Renesas RA4T1 / RA6T3: Added IDCode authentication support.
4. J-Link comand SetInitWorkRAMOnConnect did not work on unkown devices. Fixed.
5. MindMotion MM32F5270: Added debug & flash programming support (internal, external QSPI and option bytes).
6. GigyDevice GD32A50x: Added debug and flash programming support (internal & option bytes).
7. Added debug support for Codasip L11 (RV32) device/core. https://wiki.segger.com/Codasip_L11
8. Added debug support for Codasip L31 (RV32) device/core. https://wiki.segger.com/Codasip_L31
9. Added debug support for Codasip L31F (RV32) device/core. https://wiki.segger.com/Codasip_L31
10. 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.
11. Reset did not work properly on devices where the sticky error bit is erroneously set after reset.

Firmware

1. Flasher Package: DEB package: Trying to install the J-Link software package on WSL2 using dpkg failed. Fixed.
2. Flasher: SiliconLabs EFR32xG21: Stand-alone mode did not work. Fixed.
3. Flasher: SiliconLabs EFR32xG22: Stand-alone mode did not work. Fixed.
4. Flasher: SiliconLabs EFR32xG23: Stand-alone mode did not work. Fixed.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. 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.
30. 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.
31. 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.
32. 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.
33. 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.
34. 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.
35. 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.
36. 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.
37. 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.
38. 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.
39. 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.
40. 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.
41. Flasher ARM V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
42. Flasher PRO V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
43. Flasher PRO XL V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
44. Flasher Compact V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
45. Flasher Portable PLUS V5: Infineon CYT2B95CAC: Stand-alone mode did not work due to an error related to the reset. Fixed.
46. Flasher ARM V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
47. Flasher PRO V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
48. Flasher PRO XL V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
49. Flasher Compact V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.
50. Flasher Portable PLUS V5: Reset did not work properly on devices where the sticky error bit is erroneously set after reset.

GDB Server

1. Updated Zephyr RTOS plugin to latest source base.
2. Added support for GDB "detach" command.
3. Missing support for GDB "detach" command could cause issues in some environments (e.g. VSCode debugging plugins). Fixed.

J-Flash

1. 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

1. 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

1. DEB package: Trying to install the J-Link software package on WSL2 using dpkg failed. Fixed.

Version V7.82a (2022-10-30)

Commander

1. Command "rcp15ex": Changed output in case of error.
2. Command "wcp15ex": Did not indicate errors properly. Fixed.

DLL

1. Renesas RA4T1, RA6T3: Split off PCode for ID code authentication.
2. ST SR6P7x: Connect after executing a reset failed. Fixed.
3. ARMv8-AR: CPU states were not invalidated on reset. Fixed.
4. J-Link did no longer work with SPI flash ISSI IS25LP512M. Introduced with V7.80b. Fixed.
5. Western Digital SweRV_EH1 device selection: Core type was set to RV64 while RV32 is correct. Fixed.
6. ARMv8-AR: If reading a CP15 register failed, following reads of CP15 registers all returned errors and took >= 100ms each. Fixed.
7. NXP i.MXRT1050 devices: RAM size was defined as too large. Introduced in 7.70d. Fixed.
8. NXP i.MXRT1060 devices: RAM size was defined as too large. Introduced in 7.70d. Fixed.

Firmware

1. J-Link EDU/BASE/PLUS V11: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
2. J-Link ULTRA+ V5: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
3. J-Link ULTRA+ V5.1: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
4. J-Link PRO V5: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
5. J-Link PRO V5.1: ARMv8-AR: CPU states were not invalidated on reset. Fixed.
6. J-Link WiFi V1: ARMv8-AR: CPU states were not invalidated on reset. Fixed.

GDB Server

1. ARMv8-AR: Corrected CP15 register name "PMCCFILTRk" -> "PMCCFILTR"
2. ARMv8-AR: Corrected CP15 register name "TLBIALLHc" -> "TLBIALLH"
3. ARMv8-AR: Corrected CP15 register name "TLBIMVAHc" -> "TLBIMVAH"
4. ARMv8-AR: Corrected CP15 register name "TLBIALLNSNHc" -> "TLBIALLNSNH"
5. ARMv8-AR: Corrected CP15 register name "TLBIALLHISc" -> "TLBIALLHIS"
6. ARMv8-AR: Corrected CP15 register name "TLBIMVAHISc" -> "TLBIMVAHIS"
7. ARMv8-AR: Corrected CP15 register name "TLBIALLNSNHISc" -> "TLBIALLNSNHIS"
8. ARMv8-AR: Corrected CP15 register name "ATS1HRc" -> "ATS1HR"
9. ARMv8-AR: Corrected CP15 register name "ATS1HWc" -> "ATS1HW"
10. ARMv8-AR: Corrected CP15 register name "SCRd" -> "SCR"
11. ARMv8-AR: Corrected CP15 register name "CP15DSBi" -> "CP15DSB"
12. ARMv8-AR: Corrected CP15 register name "CP15DMBi" -> "CP15DMB"
13. ARMv8-AR: Corrected CP15 register name 64-bit instance of "PAR" -> "PAR_64"
14. Configuration dialog: On some setups (e.g 13-inch M1 MacBook), the dialog was larger than the screen and some elements were inaccessible. Fixed.
15. 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.
16. ARMv8-AR: If reading a CP15 register failed (e.g. register not implemented), no error was reported to GDB. Fixed.
17. ARMv8-AR: If reading a CP15 register failed, following reads of CP15 registers all returned errors and took >= 100ms each. Fixed.
18. Updated Zephyr RTOS plugin to latest source base.

J-Flash

1. 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

1. When loading projects that specified SPI speeds lower than 1000 kHz, J-Flash SPI changed the speed to 1000 kHz. Fixed.

Manual

1. UM08022: Updated how to enter the file access mode.

RTT Viewer

1. 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.
2. Opening the channel info dialog (F8) could cause the application to freeze or crash. Fixed.

SWO Viewer

1. 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

1. loadfile: The error message when trying to load files of an unknown / unsupported format contained a typo. Fixed.
2. loadbin: The error message when trying to load files of an unknown / unsupported format contained a typo. Fixed.
3. loadfile: Added support for ELF file formats (.elf, .out, .axf).

DLL

1. Cadence Xtensa: Added some Xtensa LX TAPId's to the supported list (e.g. "0x120034E5")
2. Added debug & flash programming support for Cypress CY8C4746xxx-Sxxx and CY8C4747xxx-Sxxx series.
3. Infineon TLE986x: Under special circumstances, verify via CRC could cause issues. Fixed.
4. Infineon TLE987x: Under special circumstances, verify via CRC could cause issues. Fixed.
5. Improved connect time for Cortex-M targets when using SWD.
6. 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.
7. Added support for J-Link-Lite-S124.
8. SEGGER flash loaders (ex open flash loader) with more than 8 elements for FlashDevice.aSectorInfo[] were rejected with an error message. Fixed.
9. In some cases, J-Link DLL did not work with Keil-based flash loaders. Introduced in V7.80. Fixed.

Firmware

1. Flasher ARM V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
2. Flasher PRO V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
3. Flasher PRO XL V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
4. Flasher Compact V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
5. Flasher Portable PLUS V5: Flasher would still drive some target interface pins after standalone programming. Fixed.
6. J-Link OB Apollo4 CortexM: SWO did not work (no data received via SWOViewer). Fixed.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.

GDB Server

1. Breakpoints did not work properly for unaligned (not word aligned) thumb-2 (32 bit code) instructions. Fixed.
2. ARMv7-R (e.g. Cortex-R4F): Some GDBs complained about a too long reply to the remote 'g' packet. Fixed.
3. ARMv8-A/R AArch32 (e.g. Cortex-R52): Added CP15 registers to GDB Server register table.

J-Flash

1. When connecting to a probe/ programmer, J-Flash now prints the serial number to the log.
2. Added more wiki links and manuals to the help menu.
3. 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.
4. 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.
5. SEGGER flash loaders (ex open flash loader) with more than 8 elements for FlashDevice.aSectorInfo[] were rejected with an error message. Fixed.

J-Flash SPI

1. Added more wiki links and manuals to the help menu.
2. 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.
3. After closing a project file, multiple message boxes stating "No project file opened." could appear. Fixed.
4. 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.
5. 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.
6. 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.

J-Scope

1. Repeated ELF file parsing could fail. Fixed.

Manual

1. UM08002: Chapter "General API" updated. Section "API Functions". Added newly supported file formats for "JLink_DownloadFile()".

Version V7.80d (2022-10-04)

Control Panel

1. Settings tab: The tab did not update periodically after it was opened. Introduced with V7.22. Fixed.
2. Settings tab: Added field for configuring the threshold for enabling Read-Modify-Write behavior (https://wiki.segger.com/Read-Modify-Write_Flash).

DLL

1. JLinkDevices.xml: Device entry with missing flashloader could cause DLL to crash. Fixed.
2. JLinkDevices.xml: Increased verbosity of error message for broken device entries.
3. SWO: Added native SWO support for ST STM32U5 series devices.
4. Infineon CYT3DL: Updated supported device list to accept the new part numbers from the latest datasheet.
5. Updated MCU-Link Pro and MCU-Link terms of use dialog to name the covered cores instead of the covered families.
6. AUCU AU3x: Updated device specific reset strategy.
7. 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.
8. Qorvo PAC55xx series: Added debug & flash programming support.
9. EFR32 Series 1 devices: Connect would fail for some devices. Introduced V7.80c. Fixed.
10. Added SPI Flash programming support for onsemi LE25U20AQG.
11. Cadence Xtensa: Added "Xtensa LX6" as supported + selectable device name. (For custom Xtensa LX6 based cores)

J-Flash

1. 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

1. Project settings: Flash: There was whitespace below the "Use Quad Mode" checkbox even when it was not checked. Fixed.
2. 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.
3. When downloading multiple files to a Flasher, multiple progress dialogs were opened and closed swiftly, making it look like a dialog was flashing. Fixed.
4. Added SPI Flash programming support for onsemi LE25U20AQG.

Version V7.80c (2022-09-27)

DLL

1. Geehy APM32E1xx, APM32F1xx, APM32F4xx: Connect via JTAG did not work. Fixed.
2. Infineon PSoC6 devices: SMIF flash bank was mistakenly treated as always present, causing chip erase to fail. Introduced with 7.70d. Fixed.
3. ONSemi RSL15: Reset was not working correctly, which could cause erase operations (and similar) to fail. Fixed.
4. 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.
5. Silicon Labs EFR32 family: User JTAG chain selection was ignored. Fixed.

Firmware

1. 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.
2. 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)
3. 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)
4. 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)
5. 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)
6. 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)
7. 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)
8. 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)
9. 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)
10. 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)
11. 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)
12. 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)
13. 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)
14. 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)
15. 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)
16. 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)

GDB Server

1. 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

1. When "-noLocalhostOnly" was selected ("Localhost only" was not selected), the RTT TELNET port was still only available for localhost. Fixed.

J-Flash

1. 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.
2. 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

1. 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
2. Command line: Connect to existing session: Added option to connect to a specific process via TELNET port.

Version V7.80b (2022-09-20)

Highlights:

Trace

1. 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

1. Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
2. Cortex-M23: ROMTable scan: TPIU and ETM were detected as "Cortex-M23" by mistake. Fixed.
3. Renesas RZ/T2M: Added flash programming support for external flashes connected to xSPI0.

Firmware

1. J-Link EDU/BASE/PLUS V11: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
2. J-Link ULTRA+ V5: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
3. J-Link ULTRA+ V5.1: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
4. J-Link PRO V5: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
5. J-Link PRO V5.1: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.
6. J-Link WiFi V1: Cadence Xtensa: I/D-cache configurations with <NumWays> not being a power of 2 were not supported. Fixed.

GDB Server

1. 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

1. Added SPI Flash programming support for ISSI IS25LX512M, IS25WX512M.

Version V7.80a (2022-09-14)

DLL

1. Geehy APM32E103xx, APM32F030xx, APM32F003xx, APM32F051xx, APM32F072xx, APM32F091xx, APM32F4xx device families: Added option byte programming support.
2. Geehy APM32E103xx, APM32F030xx, APM32F003xx, APM32F051xx, APM32F072xx, APM32F091xx, APM32F4xx device families: Added read- and write-protection detection and unlock.
3. RISC-V: Detection if CSR access via abstract commands is supported did not work correctly if core also had NumProgramBuffers != 0. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.

J-Flash

1. When creating a new project without a project already open, multiple "No project file opened." error dialogs were shown. Introduced with V7.70. Fixed.
2. After creating a new project, no sectors of any flash bank were selected initially. Introduced with V7.70. Fixed.

Manual

1. UM08002: Chapter "General API" updated. Section "Indirect API Functions": Added "JLINK_IFUNC_EMU_GET_NICKNAME". Added "JLINK_IFUNC_EMU_SET_NICKNAME".
2. UM08002: Chapter "RTT" updated. Section "RTT API Functions": Added "JLINK_RTTERMINAL_CTRL_BLOCK_INFO" command to JLINK_RTTERMINAL_Control().

Version V7.80 (2022-09-08)

Control Panel

1. Under rare circumstances, "Data rate", "Total received" and "Buffered" were showing wrong values. Fixed.
2. RTT Tab: Added TELNET port of DLL instance field.

DLL

1. Renesas RZ/N2L: Added flash programming support for external (CFI compliant) parallel NOR flashes.
2. NXP NHS52S04: Added debug and flash programming support.
3. SiliconLabs: EFR32 Series 2: Added native unlock functionality.
4. GigaDevice GD32F3 device family: Sector erase was not working correctly on bank 1. Fixed.

Firmware

1. 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.
2. J-Link-OB-S124: Renesas RZ/N2L: Flash programming did not work. Fixed.
3. Flasher: ST STM32F7: Option byte programming did not work in stand-alone mode. Fixed.

J-Flash

1. 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.
2. Project settings: Flash: The "loader" selection was visible for external banks. Fixed.
3. ST STM32F7: J-Flash rejected to download the data & config file in case of option bytes have been selected.
4. When opening a project, J-Flash would try and check external flash banks for loaders, despite no loaders being available for external banks. Fixed.
5. 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.

J-Scope

1. Tooltip symbol information did not match actual data at cursor position. Fixed.

RTT Logger

1. "Bytes written" > 1 MB was partially displayed incorrectly. Fixed.

RTT Viewer

1. Under rare circumstances, it could happen that the main window was not showing on startup. Fixed.

Version V7.70e (2022-08-31)

DLL

1. Infineon CYxxxx devices: Connect did not work due to missing algo info error. Fixed.

Version V7.70d (2022-08-30)

Commander

1. Added "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).

DLL

1. Added PCode functions "JLINK_SetBP()" and "JLINK_ClrBP()".
2. Added debug support for SiFive E20 device/core. (https://wiki.segger.com/SiFive_E20)
3. Added debug support for SiFive E61, E61-MC device/core. (https://wiki.segger.com/SiFive_E61)
4. Added debug support for SiFive E76-MC device/core.
5. Added debug support for SiFive S61, S61-MC device/core. (https://wiki.segger.com/SiFive_S61)
6. Added debug support for SiFive S76-MC device/core.
7. Added debug support for SiFive U54, U54-MC device/core. (https://wiki.segger.com/SiFive_U54)
8. Added debug support for SiFive U64, U64-MC device/core. (https://wiki.segger.com/SiFive_U64)
9. Added debug support for SiFive U74, U74-MC device/core. (https://wiki.segger.com/SiFive_U74)
10. Added debug support for SiFive P270 device/core. (https://wiki.segger.com/SiFive_P270)
11. Added debug support for SiFive P550 device/core. (https://wiki.segger.com/SiFive_P550)
12. Added debug support for SiFive X280, X280-MC device/core. (https://wiki.segger.com/SiFive_X280)
13. Infineon CYT2B6, CYT2B7, CYT2B9, CYT2BL device series: Under certain circumstances JTAG connect to M4 core did not work. Fixed.
14. Infineon CYT3BB device series: Under certain circumstances JTAG connect to M7 core did not work. Fixed.
15. Infineon CYT4BB, CYT4BF device series: Under certain circumstances JTAG connect to M7 cores did not work. Fixed.
16. Added "SuppressGUI" command string. For more information, refer to https://wiki.segger.com/J-Link_Command_Strings#SuppressGUI .
17. Geehy APM32: Updated list of supported device names.
18. ARMv8-AR: In case of the sticky error bit was set, the DAP could not be powered when using JTAG. Fixed.
19. Added debug and flash programming support for ncoder N4.
20. ARMv8-AR (e.g. Cortex-R52): Software breakpoints did not work correctly. Fixed.
21. Renesas RZ/T2M: By default, the xSPI0 and xSPI1 module were disabled after reset. Fixed.
22. AmbiqMicro Apollo4: Added debug and flash programming support for AMAP42KP-KBR, AMA4B2KP-KXR, AMA4B2KP-KBR.
23. GigaDevice GD32E113 device family: Added debug & flash programming support.

Firmware

1. J-Link-OB-STM32F103: Green LED did not indicate heartbeat & debug interface activity correctly. Fixed.
2. J-Link EDU Mini V1: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
3. J-Link EDU/BASE/PLUS V11: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
4. J-Link ULTRA+ V5: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
5. J-Link PRO V5: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
6. J-Link WiFi V1: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
7. J-Trace PRO V2 Cortex: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
8. J-Trace PRO V2 CortexM: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
9. J-Trace PRO V3 Cortex: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
10. J-Trace PRO V3 CortexM: Added support for J-Link Commander "Reboot" command (https://wiki.segger.com/J-Link_Commander#Reboot).
11. mIDAS-Link: The J-Link DLL rejected to work with Analog ADRF88xx / ADRF89xx device series. Fixed.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. Flasher ARM V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
20. Flasher PRO V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
21. 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.
22. Flasher Compact V5: ARMv8-A/R: I-cache was not invalidated properly on Go/Step if software breakpoints in RAM were set/cleared. Fixed.
23. 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.

GDB Server

1. GUI: Config dialog: Added fields for specifying GDB port, SWO port and telnet port.

J-Scope

1. Added command line option -openprj.
2. Added "Import Raw" functionality.
3. J-Scope now remembers the directory of the last project/ELF/data file opened/saved.
4. Under certain circumstances cursor tooltip did not work correctly. Fixed.

Manual

1. UM08002: Chapter "General API" updated. Section "API Functions": Fixed typos and grammar in description for JLINKARM_Lock().

Version V7.70c (2022-08-18)

J-Flash

1. Some verbose output log messages were printed by default by mistake. Fixed.

Version V7.70b (2022-08-18)

Commander

1. ARMv8-AR AArch32: Added the CPSR register to the list of supported register for the wreg command.
2. List of supported registers for the wreg command were incorrectly formatted. Fixed.

DLL

1. 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.
2. 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.
3. NXP i.MX RT1010 (i.MX RT1011): Device specific reset did not work correctly. Fixed.
4. Added JTAG TAPId 0x10307A6D (RISC-V RV32 TAP) to the list of known TAPIds.
5. Added JTAG TAPId 0x790007A3 (Boundary Scan TAP) to the list of known TAPIds.

Firmware

1. Flasher ARM V5: Terminal ASCII interface: Under special circumstances a #erase, #auto, ... operation could result in multiple #ERR responses being sent by Flasher. Fixed.
2. Flasher PRO V5: Terminal ASCII interface: Under special circumstances a #erase, #auto, ... operation could result in multiple #ERR responses being sent by Flasher. Fixed.
3. 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.
4. Flasher Compact V5: Terminal ASCII interface: Under special circumstances a #erase, #auto, ... operation could result in multiple #ERR responses being sent by Flasher. Fixed.
5. 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.
6. Flasher ARM V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
7. Flasher PRO V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
8. Flasher PRO XL V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
9. Flasher Compact V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.
10. Flasher Portable PLUS V5: Stand-alone mode: SPI direct programming: Target interface was not tri-stated after operation finished. Fixed.

J-Flash

1. 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

1. Performance broke down when viewing the oldest data with full sample ring buffer. Fixed.

Version V7.70a (2022-08-10)

Highlights:

Trace

1. Published out-of-the-box trace example for Toshiba AdBun-M3HQA board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
2. Published out-of-the-box trace example for Toshiba AdBun-M4GR board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
3. Published out-of-the-box trace example for Toshiba AdBun-M4NR board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/
4. Published out-of-the-box trace example for Toshiba AdBun-M4KN board: https://www.segger.com/products/debug-probes/j-trace/technology/tested-devices/

Other changes:

Commander

1. 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

1. Geehy APM32E103xx, APM32F030xx, APM32F003xx, APM32F051xx, APM32F072xx, APM32F091xx, APM32F4xx device families: Added debug & flash programming support.
2. Renesas R5F5140x (RX140): Added debug & flash programming support ("User Area" and "Data Area").
3. Renesas R5F5660x (RX660): Added debug & flash programming support ("data flash", "program flash" and "option setting memory").
4. JLinkDevices.xml files: Aliases were not handled correctly if the aliased device name already existed. Fixed.
5. Cleaned up some ALGO info structs. No functional change.
6. Cypress CYT3, CYT4: DCache was not correctly invalidated. Fixed.
7. NXP Kinetis Series, iMXRT Series: DCache was not correctly invalidated. Fixed.
8. ST STM32H7 Series, STM32F7 Series: DCache was not correctly invalidated. Fixed.
9. NXP MIMX8DL1, MIMX8SL1: Device specific handling was not executed. Fixed.
10. Renesas RZ/A3UL: Added debug & flash programming support (https://wiki.segger.com/Renesas_RZ/A3UL).
11. Renesas RZ/N2L: Added debug & flash programming support (https://wiki.segger.com/Renesas_RZ/N2L).
12. GigaDevice GD32C1 device family: Added debug & flash programming support.

DLL Updater

1. Under rare circumstances the DLL path was cut off in the middle of the window. Fixed.

Firmware

1. Flasher ARM V5.1: HW version was reported as V5.00 instead of V5.10 in utilities like J-Link/Flasher Commander. Fixed.
2. Flasher PRO V5.1: HW version was reported as V5.00 instead of V5.10 in utilities like J-Link/Flasher Commander. Fixed.
3. 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

1. 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

1. Project information: Improved flash bank information display.
2. 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.
3. Removed deprecated / unused function unsecure chip.

Version V7.70 (2022-08-03)

Highlights:

DLL

1. Added support for Cadence Xtensa LX6/LX7 architecture.
2. Cadence Xtensa: Added debug support for HiFi 1, HiFi 3, HiFi 3z, HiFi 4, Fusion F1 cores.

GDB Server

1. Added native debug support for Cadence Xtensa LX architecture via Cadence xt-gdb client (Xtensa Xplorer IDE).

Other changes:

CCS Plugin

1. Added support for ARM7/9.

Commander

1. Added support for Cadence Xtensa LX6/LX7 architecture.
2. Command 'loadbin': Now performs implicit reset before download.
3. Command 'loadfile': Now performs implicit reset before download.
4. Command 'erase': Now performs implicit reset before erase.
5. Command 'loadbin': Added <noreset> option, to inhibit implicit reset before command operation.
6. Command 'loadfile': Added <noreset> option, to inhibit implicit reset before command operation.
7. Command 'erase': Added <noreset> option, to inhibit implicit reset before command operation.

DLL

1. NXP i.MXRT685: Added device selection "MIMXRT685S_HiFi4" for debugging support of HiFi 4 core via J-Link Commander, GDB Server, ...
2. AndesTech A45MP: Added debugging support.
3. AndesTech AX45MP: Added debugging support.
4. Alif Semiconductor AC302, AC512, AC722 device series: Added flash programming support for Cortex-A32 cores.
5. Microchip PIC32CX1025SGxx: Changed device names to "full" device names (e.g. PIC32CX1025SG41 => PIC32CX1025SG41100 & PIC32CX1025SG41128).
6. ST STM32WB: Add device specific connect and native unlock functionality.
7. Renesas R-IN32M4-CL3: Added debug & flash programming support.
8. ST STM32: Some device specific debug bits were not reset on disconnect. Fixed.

Firmware

1. Flasher Compact V5: O2Micro OZ93506: Flash programming did not work in stand-alone mode. Introduced in V6.68. Fixed.
2. Flasher Package: Installer: Start Menu entry for "Flasher Registration".

GDB Server

1. 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

1. 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

1. J-Scope did not parse the addresses of structs nested within structs correctly. Fixed.

Manual

1. UM08003: Chapter "Command Line interface" * Section "Programming multiple targets in parallel": Updated batch file example. Added Python script example.

SWO Viewer

1. Windows: GUI: The SWO Viewer application mistakenly had the icon for "J-Mem". Fixed.

Version V7.68c (2022-07-28)

CCS Plugin

1. Changed TIF selected by default to SWD from JTAG.

DLL

1. Renesas RA4M2 device series: Added SPI flash programming support for CLK@P500_nCS@P501_D0@P502_D1@P503 pin configuration.
2. Renesas RA6M3 device series: Added SPI flash programming support for CLK@P500_nCS@P501_D0@P502_D1@P503 pin configuration.
3. ST SR5E1E3 and SR5E1E7 were not selectable in device selection dialog. Fixed.
4. ST STM32F413/STM32F423: Write protection of the last 4 sectors was not unlocked by unlock procedure. Fixed.

J-Flash

1. ST SR5E1E3 and SR5E1E7 were not selectable in device selection dialog. Fixed.

Version V7.68b (2022-07-22)

CCS Plugin

1. Added Cortex-M0 support.
2. Added SEC AP support.
3. In case the connect was unsuccessful, misleading error messages were printed. Fixed.

DLL

1. ST STM32F7, STM32G0, STM32G4, STM32H7, STM32L0, STM32L1, STM32L4, STM32L5: Flash programming failed if any flash error bits were set before flash operation. Fixed.
2. RaspberryPi RP2040: Reset did not work for B0 and B2 silicon. Fixed.
3. Added debug support for ST SR5E1 series devices SR5E1E3, SR5E1E7. https://wiki.segger.com/J-Link_ST_SR5E1
4. ST SR5E1 series: Added flash programming support for "code flash 1" flash bank.
5. ST SR5E1 series: Added flash programming support for "code flash 2" flash bank.
6. ST SR5E1 series: Added flash programming support for "data flash" flash bank.
7. ST SR5E1 series: Added flash programming support for "HSM code flash" flash bank.
8. ST SR5E1 series: Added flash programming support for "HSM data flash" flash bank.

Firmware

1. 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)
2. 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)
3. 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)
4. 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)
5. 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)
6. 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)
7. 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)
8. 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)
9. 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)
10. 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)
11. 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)
12. 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)
13. 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)
14. 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)
15. 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)
16. 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)
17. 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)

GDB Server

1. GUI: Added field for specifying a J-Link script file.
2. 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

1. 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

1. The "Prog. addr." field is no longer updated when selecting a file format that specifies the data start address.
2. The "Prog. addr." field is now only shown when a .bin file is selected.
3. After selecting a data file, the contained data memory ranges are now printed to the log.

Version V7.68a (2022-07-19)

DLL

1. GigaDevice GD32F4: Some devices were listed twice. Fixed.
2. ST STM32WB15xx: Wireless stack and FUS upgrade did not work. Fixed.
3. JLinkDevices XML <FlashBankInfo> tag entries were not parsed correctly. Introduced in V7.68. Fixed.
4. AUCU AU3x: Changed device names of former AG32 device family.

Firmware

1. J-Link EDU Mini V1: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
2. J-Link EDU/BASE/PLUS V11: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
3. J-Link ULTRA+ V5: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
4. J-Link PRO V5: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
5. J-Link WiFi V1: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
6. J-Trace PRO V2 Cortex: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
7. J-Trace PRO V2 CortexM: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
8. J-Trace PRO V3 Cortex: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.
9. J-Trace PRO V3 CortexM: ARMv8-A/R (AArch32): PC and CPSR could not be set. Introduced in V7.66e. Fixed.

J-Flash

1. 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

1. 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

1. Updated parameter overview for "wreg" and "rreg" commands.
2. Added support for showing J-Link uptime (since boot).

DLL

1. Renesas RZ/T2M: Added debug and (QSPI) flash programming support (https://wiki.segger.com/Renesas_RZ/T2M).
2. Renesas RZ/T2M: Added authentication support (https://wiki.segger.com/Renesas_RZ/T2M#JTAG_Authentication).
3. O2Micro OZ935xx device series: Added flash programming support for EEPROM.
4. Added debug & flash programming support for some new Toshiba TMPM3H devices (e.g. TMPM3HQFDAFG).
5. Added debug & flash programming support for some new Toshiba TMPM4G devices (e.g. TMPM4GRF20FG).
6. Added debug & flash programming support for Toshiba TMPM4N devices (e.g. TMPM4NRF20FG).
7. Added debug and (QSPI) flash programming support for HPMicro HPM63 (https://wiki.segger.com/HPMicro_HPM63).
8. Updated debug and (QSPI) flash programming support for HPMicro HPM61 (https://wiki.segger.com/HPMicro_HPM61).
9. Updated debug and (QSPI) flash programming support for HPMicro HPM64 (https://wiki.segger.com/HPMicro_HPM64).
10. Updated debug and (QSPI) flash programming support for HPMicro HPM67 (https://wiki.segger.com/HPMicro_HPM67).
11. Infineon CY8C6 family: Updated Infineon 3rd party Device Support.
12. GigaDevice GD32F470: Added debug & flash programming support.
13. Added debug and flash programming support for TI MSPM0G (https://wiki.segger.com/TI_MSPM0G).
14. Added debug and flash programming support for TI MSPM0L (https://wiki.segger.com/TI_MSPM0L).
15. Updated debug and (QSPI) flash programming support for HPMicro HPM6x.
16. Maxim (Analog Devices) MAX32690: Added debug and flash programming support.
17. AUCU AG32: Added debug and flash programming support (e.g. for AG32R2080LF).
18. Added debug and flash programming support for missing GD32F4xx devices.
19. NXP MKL81 device series: Added debug and flash programming support.
20. SiliconLabs BGM220, BGM240, MGM220, MGM240, FGM230, ZGM130, ZGM230 devices series: Added debug and flash programming support for various members of those device families.
21. HPMicro HP67xxxANx, HP67xxxVMx : Added support for second core.
22. ESWIN ECR2560: Added debug and flash programming support.
23. GigaDevice GD32L233 devices series: Added debug and flash programming support for internal flash.
24. ST STM32G050/STM32G051 device series: Added support for missing devices of device family.
25. Added debug and flash programming support for PIC32CX1025SGxx devices.
26. Infineon CYT2B9, CYT4BB: More detailed structure of the supervisory flash.
27. Added JTAG TAPId pattern 0xXBBXXX2F as known TI ICEPick JTAG device.
28. Renesas RA4T1: Added debug & flash programming support.
29. Renesas RA6T3: Added debug & flash programming support.
30. Renesas R7FA6M5BF: Added debug & flash programming support.
31. ST STM32L5: Add device specific connect and native unlock functionality.
32. ST STM32U5: Add device specific connect and native unlock functionality.
33. 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
34. Cortex-M: Added support for cascaded AP setups (e.g. ST SR5E1 series devices). https://wiki.segger.com/DAP#DAP_topology_example_-_Cascaded_APs

Firmware

1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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

1. GUI: Configuration dialog: Renamed "Misc. settings" to "Server settings" and moved them out of the "Target interface" group.

J-Flash

1. Added support for ARMv8-AR based devices (AArch32 and AArch64).
2. Added JTAG TAPId pattern 0xXBBXXX2F as known TI ICEPick JTAG device.

J-Mem

1. Data window: Added support to save memory data to file in different formats (.mot, .srec, .s19, .s28, .s, .hex, .bin, .raw, .c).
2. Menu bar: Added "Save memory to data file" action.

J-Run

1. Added command line options "--usb" and "--ip" for selecting a J-Link to connect to without user interaction (e.g. selecting in GUI dialog).
2. Added log message indicating which J-Link J-Run is connected to.

RTT

1. Added special handling for IAR compiler to RTT sources if SEGGER_RTT_CPU_CACHE_LINE_SIZE is defined != 0.

RTT Viewer

1. Added a command line option to extend the window title, so that it is easier to distinguish between mutliple RTT Viewer instances.

STM32 Utility

1. Added ST STM32L5.
2. Added ST STM32U5.

Version V7.66g (2022-07-07)

DLL

1. 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
2. ST STM32F1: Watchdogs were not frozen in debug mode. Fixed.
3. ST STM32G0: Watchdogs were not frozen in debug mode. Fixed.

Version V7.66f (2022-07-05)

DLL

1. Microchip SAMD20/SAMD21: Flash size was incorrect for 128 KB flash devices (64 KB instead of 128 KB). Fixed.

GDB Server

1. Cortex-A57: Connection attempts were rejected with "Device family is not supported by GDB Server" error message. Fixed.

J-Flash

1. 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

1. J-Link OB K22 Cortex-A: cJTAG: Added support for targets with buggy/missing KEEPER logic. https://wiki.segger.com/J-Link_cJTAG_specifics
2. J-Link OB K22 Cortex-M: cJTAG: Added support for targets with buggy/missing KEEPER logic. https://wiki.segger.com/J-Link_cJTAG_specifics
3. 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
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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)
14. Flasher ARM V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
15. Flasher PRO V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
16. Flasher PRO XL V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
17. Flasher Compact V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
18. Flasher Portable PLUS V1: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.
19. Flasher Portable PLUS V5: Direct SPI flash programming: Stand-alone mode: Reset pin was not released after Flasher was finished. Fixed.

Version V7.66d (2022-06-21)

Commander

1. "rreg" command was unable to show 64-bit values for architectures other than ARM AArch64. Fixed.

Firmware

1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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
9. 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
10. 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
11. 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
12. 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
13. 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
14. 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

J-Flash SPI

1. 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

1. Open flashloader: SEGGER_OPEN_Read function parameter "NumBytes" was always zero in turbo mode. Fixed.
2. NXP LPC55S66: Internal flash memory size was incorrectly set to 320KB instead of 256KB. Fixed.
3. ISSI IS25LP512M, IS25WP512M: SPIFI-Lib did not support EXTADD mode. Fixed.
4. ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): AArch32: Accessing FPU registers Q0-Q15 always resulted in Q0 being accessed. Fixed.
5. Infineon MB9BF121J: Flash programming did not work due to incorrect sectorization and incorrect flash algorithm. Fixed.
6. Maxim (Analog Devices) MAX32650: In case of the watchdog was enabled / used, flash programming could fail. Fixed.
7. 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.
8. 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.

Firmware

1. 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.
2. 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.
3. 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.
4. ARMv8-A/R firmware module V2 (e.g. Cortex-A53, Cortex-R52): AArch32: CPU register ELR_HYP could not be read/written. Fixed.
5. 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.
6. 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.
7. J-Link EDU Mini V1: Update to ARMv8-A/R firmware module V2. Fixed.
8. J-Link EDU/BASE/PLUS V11: Update to ARMv8-A/R firmware module V2. Fixed.
9. J-Link ULTRA+ V5: Update to ARMv8-A/R firmware module V2. Fixed.
10. J-Link PRO V5: Update to ARMv8-A/R firmware module V2. Fixed.
11. J-Link WiFi V1: Update to ARMv8-A/R firmware module V2. Fixed.
12. J-Link OB RA4M2: Update to ARMv8-A/R firmware module V2. Fixed.
13. J-Link-OB-S124: Update to ARMv8-A/R firmware module V2. Fixed.
14. J-Trace PRO V2 Cortex: Update to ARMv8-A/R firmware module V2. Fixed.
15. J-Trace PRO V3 Cortex: Update to ARMv8-A/R firmware module V2. Fixed.
16. Flasher V5: GigaDevice GD32F1, GD32F2, GD32F3, GD32F4: Stand-alone-mode did not work. Fixed.
17. 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.
18. 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.

J-Flash

1. 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

1. Under certain circumstances J-Scope could crash when drawing the graph. Fixed.

Version V7.66b (2022-05-30)

DLL

1. 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

1. 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.
2. Emulator config dialog: Increased width of the "product name" field so it can show most product names without them being cut off. Fixed.

DLL

1. Device selection dialog: On displays with high scaling or high pixel density, the initial size for this dialog was too small. Fixed.
2. Cortex-M ARMv8-M: Added support for CPU registers PAC_KEY_P_0-3, PAC_KEY_U_0-3 (including secure / non-secure variants).
3. Cortex-M85: Added support for CPU register VPR.
4. SiliconLabs EFR32xG21, EFR32xG22 device series: Flash operation on internal flash did not work after user data page had been programmed. Fixed.

GDB Server

1. 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.
2. Config dialog: On displays with high scaling or high pixel density, the "command line option" field was too small. Fixed.

J-Flash

1. 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

1. NXP LPC55S14/S16: Added new part numbers to the list of supported devices.
2. NXP LPC5514/16: Added new part numbers to the list of supported devices.
3. NXP RT1061x/RT1062x: Added debug & (QSPI) flash programming support for MIMXRT1061xxx5B, MIMXRT1062xxx5B and MIMXRT1062xxx6B.
4. NXP PN76 device series: Added hidden debug & flash programming support for NXP PN7640.
5. Infineon PSoC4: Updated device database to support most recent part numbers.
6. Microchip ATSAMD21: Added RWW section (EEPROM) flash programming support.
7. Added support for new Cortex-M85 (ARMv8-M) core.
8. Silicon Labs BGM220S devices series: Added debug and flash programming support.
9. Added J-Link OB CALLIOPE MINI V2.1 firmware.
10. GigaDevice GD32F303xB: Added debug and flash programming support (e.g. for "GD32F303CB").
11. Added log information when a Reset via Reset pin is executed by the DLL during the generic connect sequence.
12. TDK Micronas HVC5xxx device series: Added debug and flash programming support for HVC5221D, HVC5222C.
13. Atmosic ATM333x device series: Added debug and flash programming support for ATM3330 and ATM3330e.
14. Silicon Labs EFR32xG14 devices: Bootloader flash bank size was defined with 16KB, should be 18KB. Fixed.
15. Silicon Labs EFM32TG11B devices: Bootloader flash bank size was defined with 32KB, should be 18KB. Fixed.
16. TDK Micronas HVC5xxx device series: Halt after reset did not work properly. Fixed.

DLL Updater

1. Added IAR EWRX as updatable IDE.

GDB Server

1. Updated Zephyr RTOS plugin to latest source base.
2. Cortex-A32 (ARMv8-A): Added support for "monitor regs" command.

J-Flash

1. 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.
2. On displays with high scaling or high pixel density, icons of docked windows were displayed too small. Fixed.
3. On displays with high scaling or high pixel density, the initial window size of J-Flash was too small. Fixed.

J-Flash SPI

1. 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.
2. On displays with high scaling or high pixel density, icons of docked windows were displayed too small. Fixed.
3. On displays with high scaling or high pixel density, the initial window size of J-Flash was too small. Fixed.

J-Link Package

1. 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

1. Improved error message when data sampling could not be started.
2. macOS: J-Scope would crash on project creation. Fixed.
3. Options dialog would always show JTAG selected even if previously another interface was selected. Fixed.

Manual

1. UM08002: Chapter Python support: Updated documentation.

Registration

1. 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

1. SiLabs EFR32xG24: Device specific reset did not work correctly. Fixed.
2. NXP i.MXRTR106x device series: QSPI flash size was limited to 64 MB instead of 512 MB. Fixed.
3. NXP i.MXRTR1064 device: QSPI flash size was limited to 64 MB instead of 256 MB. Fixed.
4. NXP i.MXRTR105x device series: QSPI flash size was limited to 64 MB instead of 512 MB. Fixed.
5. NXP i.MXRTR102x device series: QSPI flash size was limited to 64 MB instead of 512 MB. Fixed.
6. NXP i.MXRTR101x device series: QSPI flash size was limited to 64 MB instead of 512 MB. Fixed.
7. ST STM32WB5x: Device was unnecessarily halted after connect. Fixed.
8. NXP i.MXRT600 device series: With certain hardware configurations reset did not work properly. Fixed.
9. Infineon CYT4BFxxxB: Under certain circumstances, flash programming did not work. Fixed.
10. RAM was not preserved if RAM was changed between reset and the first flash download. Fixed.

Firmware

1. Flasher ARM V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
2. Flasher PRO V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
3. Flasher PRO XL V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
4. Flasher Compact V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
5. Flasher Portable PLUS V1: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.
6. Flasher Portable PLUS V5: Qorvo QPGxxx: Flash programming failed in stand-alone mode. Fixed.

J-Flash

1. Qorvo QPGxxx: J-Flash rejected to download the config & data file. Fixed.

J-Scope

1. Parsing volatile symbols could cause those symbols to be interpreted as a different type. Fixed.

Manual

1. 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

1. 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.
2. RaspberryPi RP2040: When setting a breakpoint before calling the reset function (e.g. using IDEs), the reset did not work as expected. Fixed.
3. Microchip ATSAMC20 / ATSAMC21: Under special circumstances, flash programming could fail depending on the watchdog settings. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. Flasher ARM V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
19. Flasher PRO V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
20. 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.
21. Flasher Compact V5: API function JLINK_UART_Write(): Passing larger chunks of data (> 128 bytes) to firmware could lead to USB communication breakdowns. Fixed.
22. 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.
23. 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.

GDB Server

1. Semi-hosting did not work for ARMv8-AR targets (e.g. Cortex-A32). Fixed.

J-Scope

1. Options dialog: The project settings were not updated after pressing "OK". Introduced with V7.64c. Fixed.

Version V7.64c (2022-04-20)

DLL

1. 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.
2. ARMv8-A/R (e.g. Cortex-A53, Cortex-R52): Added CP15 register support via J-Link API.

J-Flash

1. The merge command did not actually merge the datafiles (introduced V7.60). Fixed.

J-Scope

1. If one instance of J-Scope was running, opening a new instance in parallel would cause that instance to freeze. Fixed.
2. Symbol selection: Members of a union could not be selected. Fixed.
3. Symbol selection: The "Name" column for an anonymous (unnamed) struct or union was empty. Fixed.
4. After creating a new project and J-Scope failed to load the ELF file, J-Scope could hang indefinitely. Fixed.
5. After creating a new project (with 'HSS' for 'Sampling Source'), opening the ELF file for showing the symbol selection would sometimes fail. Fixed.
6. Immediately after starting J-Scope, a rather large window could be seen flashing for a brief moment before disappearing. Fixed.

Version V7.64b (2022-04-08)

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. Flasher ARM V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
7. Flasher PRO V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
8. Flasher PRO XL V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
9. Flasher Compact V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.
10. Flasher Portable PLUS V5: ASCII command interface: Command #SELECT: Omitting the filename / config name did not throw an error response. Fixed.

Version V7.64a (2022-04-07)

DLL

1. NXP iMX8ML: Under special circumstances, reset did not work as expected. Fixed.
2. NXP iMX8MN: Under special circumstances, reset did not work as expected. Fixed.
3. Setting/deactivating permanent powersupply did not work (introduced in V7.62). Fixed.
4. SWO: Disconnecting the USB cable from the J-Link while SWO was running could cause a crash. Fixed.
5. Microchip PIC32MZ: Under special circumstances, flash programming could fail (error while preparing target). Fixed.
6. NXP iMXRT600 device series: QSPI-Flashloader did not work with correctly with SPI flashes that are only 3-byte addressable. Fixed.

Firmware

1. 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.
2. 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

1. When using RTT, linebreaks were ignored. Fixed.

J-Scope

1. Nested structs were not selectable. Fixed.
2. Enumerated types were not handled correctly. Fixed.

Version V7.64 (2022-04-01)

Commander

1. SWOStart ignored device specific SWO init. Fixed.

DLL

1. Improved ECC RAM initialization speed for ST SR6P7G7x series device.
2. ST SR6P7G7x series devicers, RAM intialization speed improved during connect.
3. Added Digi NS9210 and NS9215B series devices debug support.
4. RTT: Flags[31:24] of RTT buffer description are now reserved and must be zero for validity check.
5. Added more verbosity to logging for devices created/modified through *.xml files.
6. ON Semiconductor: Added debug support for Ezario 3800 (https://wiki.segger.com/ONSemi_Ezairo_8300).
7. Added "InheritFrom" attribute for "Device" tag in JLinkDevices.xml files. For more information: https://wiki.segger.com/Open_Flashloader#JLinkDevices.xml_Tags_and_Attributes
8. Added debug support for Cortex-R7 core.
9. Added early warning watchdog check during internal flash programming for Microchip ATSAMD20 and ATSAMD21 series devices.
10. Modified conditions for early warning watchdog check during internal flash programming for Microchip ATSAMD20 and ATSAMD21 series devices.
11. Increased logging-verbosity for parsing of JLinkDevices.xml files.
12. Added SPI Flash programming support for Macronix MX66U1G45G within SPIFI-Lib.
13. Added SPI Flash programming support for Macronix MX66U2G45G within SPIFI-Lib.
14. Raspberry RP2040: Reset did not work properly. Fixed.
15. Analog Devices ADuCM410, ADuCM412, ADuCM420: Added debug and flash programming support.
16. Nuvoton M0A21, M0A23: Added debug and flash programming support.
17. ST STM32WB5x: When a Wireless Stack was already running on the device, another connect or power-cycle was required. Fixed.
18. ST STM32H723/33: SWO did not work out of the box. Fixed.

Firmware

1. 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)
2. 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)
3. 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)
4. 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)
5. Flasher ARM V5: ASCII command interface: #SECUREAREA command resulted in #SECURE command to be executed instead. Fixed.
6. Flasher PRO V5: ASCII command interface: #SECUREAREA command resulted in #SECURE command to be executed instead. Fixed.
7. Flasher PRO XL V5: ASCII command interface: #SECUREAREA command resulted in #SECURE command to be executed instead. Fixed.
8. Flasher Compact V5: ASCII command interface: #SECUREAREA command resulted in #SECURE command to be executed instead. Fixed.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. Flasher Portable PLUS V5: Battery: Under special circumstances, the battery state was incorrect and always showed 100%. Fixed.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.

GDB Server

1. Updated Zephyr RTOS plugin to latest source base.
2. GUI: Passing an invalid command line could cause J-Link GDB Server to crash. Fixed.
3. Windows: Added error code and message to log when loading a RTOS plugin failed.

J-Flash

1. Added Flasher file dialog (File -> "Show files on Flasher...").

J-Flash SPI

1. GUI: Added Flasher file dialog (File -> "Show files on Flasher...").

RTT Viewer

1. Added "Find Bar" for finding occurrences of string inside a terminal. Find Bar can be opened via <Ctrl> + F (<Cmd> + F on macOS).
2. Added an option to start the devices core, if it was halted after connect.

Version V7.62c (2022-03-22)

Configurator

1. 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

1. 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.
2. 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.
3. SiliconLabs EFR32xG21, EFR32xG23, EFR32xG24: Flash programming did not work properly. Fixed.
4. Added new exec command "RISCV_SetHartSel=<HartIndex>" which can be used to set the "Hart" (core) to be used in multi-core
5. NXP MIMXRT106x: Under rare circumstances, a reset could cause the DLL to crash. Fixed.
6. ST STM32WB5x: FUS upgrade did not work for devices < 1MB. Fixed.
7. HPMicro HPM67: Added support for the second core. For details, please refer to https://wiki.segger.com/HPMicro_HPM67#Dual_Core_Debugging.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. Flasher PRO V5: Universal flash loader: ST STM8 programming: If target MCU was running slow, flash programming did fail. Fixed.
10. Flasher PRO XL V5: Universal flash loader: ST STM8 programming: If target MCU was running slow, flash programming did fail. Fixed.
11. Flasher Compact V5: Universal flash loader: ST STM8 programming: If target MCU was running slow, flash programming did fail. Fixed.
12. 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

1. 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

1. 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.
2. 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.
3. 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

1. 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

1. 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.
2. 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.

J-Mem

1. 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

1. Selecting target interface FINE lead to an error message stating BDM3 was selected. Fixed.

RTT Viewer

1. 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.

Registration

1. 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

1. 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.

SWO Viewer

1. 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

1. Added debug and (QSPI) flash programming support for HPMicro HPM61 (https://wiki.segger.com/HPMicro_HPM61).
2. Added debug and (QSPI) flash programming support for HPMicro HPM64 (https://wiki.segger.com/HPMicro_HPM64).
3. Added debug and (QSPI) flash programming support for HPMicro HPM67 (https://wiki.segger.com/HPMicro_HPM67).
4. NXP LPC55xx / LPC55sxx: In case of no valid application was located in flash, the CPU did not halt after reset. Fixed.

DLL Updater

1. MPLAB X: The location of the DLL was not found for MPLAB X v6.00 and later. Fixed.
2. Windows arm64: Embedded Studio was not detected by DLL Updater. Fixed.

Firmware

1. Flasher Portable PLUS V1: Battery mode: Countdown for the last 10 seconds before "auto power off on idle" is now shown on display.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. J-Link PRO V5: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
8. J-Link PRO V5: Webserver: Uptime on emulator status page was showing garbage. Fixed.
9. J-Link ULTRA+ V5: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
10. J-Link WiFi V1: RTT: Added validity check if Flags[31:24] of buffer descriptor are == 0 to better detect uninitialized RTT buffer descriptors.
11. 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.
12. J-Trace PRO V2 CortexM: Webserver: Uptime on emulator status page was showing garbage. Fixed.
13. 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.
14. J-Trace PRO V2 Cortex: Webserver: Uptime on emulator status page was showing garbage. Fixed.
15. 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.
16. J-Trace PRO V3 CortexM: Webserver: Uptime on emulator status page was showing garbage. Fixed.
17. 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.
18. J-Trace PRO V3 Cortex: Webserver: Uptime on emulator status page was showing garbage. Fixed.
19. J-Link WiFi V1: The probe name was shown as "J-Link" and not as "J-Link WiFi" when connected via TCP/IP. Fixed.
20. J-Trace PRO V2 Cortex: Connecting by nickname failed (Nickname feature was not supported by accident). Fixed.
21. J-Trace PRO V2 CortexM: Connecting by nickname failed (Nickname feature was not supported by accident). Fixed.
22. J-Trace PRO V3 Cortex: Connecting by nickname failed (Nickname feature was not supported by accident). Fixed.
23. J-Trace PRO V3 CortexM: Connecting by nickname failed (Nickname feature was not supported by accident). Fixed.
24. J-Trace PRO V2 Cortex: Some probes had sporadic USB connection issues (especially at higher temperatures). Fixed.
25. J-Trace PRO V2 CortexM: Some probes had sporadic USB connection issues (especially at higher temperatures). Fixed.
26. J-Trace PRO V3 Cortex: Some probes had sporadic USB connection issues (especially at higher temperatures). Fixed.
27. J-Trace PRO V3 CortexM: Some probes had sporadic USB connection issues (especially at higher temperatures). Fixed.
28. Flasher ARM V5.1: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
29. Flasher ARM V5: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
30. Flasher PRO V5.1: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
31. Flasher PRO V5: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
32. Flasher Compact V5: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.
33. Flasher Portable PLUS V1: NXP LPC55xx / LPC55sxx: Flash programming in stand-alone mode did not work. Fixed.

J-Link Package

1. Installer: The uninstaller (Uninstall.exe) was not signed, which could cause issues with anti-virus applications. Fixed.

Version V7.62a (2022-02-23)

DLL

1. NXP S32K344: Under special circumstances, the reset did not work as expected. Fixed.
2. MacOS: If JLinkDevices folder did not exist, DLL printed "No such file or directory". Fixed.
3. Infineon CY8C6xx, CYB06xx: Device name for Cortex-M0 core forwarded by Keil uVision was always mapped to Cortex-M4 core. Fixed.
4. RTT: Possible crash when RTT buffers were not initialized correctly. Fixed.
5. NXP MKE13Z, MKE14Z, MKE15Z, internal and EEPROM programming support. Fixed.

Version V7.62 (2022-02-16)

Configurator

1. Improved product names displayed in "Product" column.
2. Some product names contained a redundant "SEGGER" at the start (e.g. "SEGGER J-Link ARM"). Fixed.
3. Some product names contained multiple occurrences of firmware version (e.g. "J-Link V11 compiled <...> V11.00"). Fixed.

DLL

1. Improved error logging for instruction trace if issues with the host interface arise.
2. HDSC HC32F460: Added debug & flash programming support for Huada Semiconductor HC32F460 series.
3. HDSC HC32F460: Improved flash programming and erase speed.
4. Added new ID for Adesto ATXP064B SPI Flash.
5. Added SPI flash programming support for ST STM32U5 series devices.
6. Added debug support for Xilinx XA7Z010, XA7Z020, XQ7Z020 devices.
7. ARMv8-AR: Added generic CFI complaint parallel NOR flash support.
8. Cypress CYT2B and Cypress CYT4B: Added flash programming support for supervisory flash.
9. Analog Devices ADRF88xx: Added debug and flash programming support for Analog Devices ADRF88xx series devices.
10. Added support for Macronix SPI flash MX25UW6345G.
11. Analog Devices ADuCM43x: Flashloader cache handling was not Inited/Uninited correctly. Fixed.
12. Analog Devices ADuCM43x: Core did not halt after reset. Fixed.
13. XHSC HC32F460xC: Added debug & flash programming support for XHSC HC32F460xC devices.
14. ST STM32L5: Added flash programming support for secure flash bank.
15. Silicon Labs EFR32BG24: Added debug and flash programming support.
16. Silicon Labs EFR32MG24: Added debug and flash programming support.
17. ST STM32WB5MMG: Added debug and flash programming support.
18. ST STM32WB15CC: Added debug and flash programming support.
19. ST STM32WB30CE: Added debug and flash programming support.
20. ST STM32WB50CG: Added debug and flash programming support.
21. NXP S32K3x2: Added debug & flash programming support for NXP S32K312, S32K322, S32K342 devices.
22. Added native debug support for the Cortex-M4 core of the i.MX8M.
23. Added native debug support for the Cortex-M4 core of the i.MX8M Mini.
24. NXP LPC553x/LPC55S3x: On connect: CPU would always be reset, even when not required (attach). Fixed.
25. SiliconLabs ExR32xG2x devices series: Added basic TrustZone support.
26. ST STM32G0x0: Size of option bytes flash bank was incorrect. Fixed.
27. ST STM32G0x0 and STM32G0x1: Size of option bytes flash bank and flash algorithm was incorrect. Fixed.
28. Infineon Traveo II (CYT2B6): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
29. Infineon Traveo II (CYT2B7): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
30. Infineon Traveo II (CYT2B9): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
31. Infineon Traveo II (CYT3BB): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
32. Infineon Traveo II (CYT4BB): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
33. Infineon Traveo II (CYT4BF): Added "Device Codes" names to the list of supported devices. So far, we did list the "Ordering Codes" names, only.
34. 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.
35. NXP iMX8, iMX8M, iMX8M Mini: RAM location and size for M4 core was incorrect. Fixed.

Firmware

1. Flasher package: Added J-Link commander to package.
2. Flasher package: Added J-Link registration utility to package.
3. Flasher package: Added JTAGLoad utility to package.
4. Flasher ARM V5: Stand-alone mode: Batch programming: Parsing of config file (.CFG) aborted with error. Fixed.
5. Flasher PRO V5: Stand-alone mode: Batch programming: Parsing of config file (.CFG) aborted with error. Fixed.
6. Flasher PRO XL V5: Stand-alone mode: Batch programming: Parsing of config file (.CFG) aborted with error. Fixed.
7. Flasher Compact V5: Stand-alone mode: Batch programming: Parsing of config file (.CFG) aborted with error. Fixed.

GDB Server

1. Added support for Cortex-A55.

J-Flash

1. 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

1. Added new ID for Adesto ATXP064B SPI Flash.
2. Added support for Macronix SPI flash MX25UW6345G.

J-Scope

1. When opening a project with a changed ELF file, the GUI was not updated after reparsing. Fixed.
2. In some cases(e.g. when using stdint.h types), J-Scope interpreted signed elements of an array as unsigned. Fixed.

Manual

1. UM08001: Chapter "Open Flashloader", Section "General procedure": Updated information regarding usage of JLinkDevices folder.
2. UM08001: Chapter "Open Flashloader", Section "Information for Silicon Vendors": Updated information regarding usage of JLinkDevices folder.

Version V7.60h (2022-02-09)

DLL

1. PTM Trace: Under certain circumstances indirect branches could cause a wrong program flow analysis. Fixed.
2. PTM Trace: Under certain circumstances exceptions could cause a wrong program flow analysis. Fixed.

Firmware

1. Flasher ARM V5: Stand-alone mode: Batch programming: AUTO command did not work properly. Fixed.
2. Flasher PRO V5: Stand-alone mode: Batch programming: AUTO command did not work properly. Fixed.
3. Flasher PRO XL V5: Stand-alone mode: Batch programming: AUTO command did not work properly. Fixed.
4. Flasher Compact V5: Stand-alone mode: Batch programming: AUTO command did not work properly. Fixed.
5. Flasher ARM V5: Stand-alone mode: Batch programming: Batch configurations were not parsed correctly. Fixed.
6. Flasher PRO V5: Stand-alone mode: Batch programming: Batch configurations were not parsed correctly. Fixed.
7. Flasher PRO XL V5: Stand-alone mode: Batch programming: Batch configurations were not parsed correctly. Fixed.
8. Flasher Compact V5: Stand-alone mode: Batch programming: Batch configurations were not parsed correctly. Fixed.
9. Flasher PRO V5: Universal flash loader: Improved performance for sparse data files (data files with many gaps in them).
10. Flasher PRO XL V5: Universal flash loader: Improved performance for sparse data files (data files with many gaps in them).
11. Flasher Compact V5: Universal flash loader: Improved performance for sparse data files (data files with many gaps in them).
12. Flasher PRO V5: Universal flash loader: TIF_UART (e.g. ESP32): Improved performance (reduced gaps and length of gaps) of UART transmission.
13. Flasher PRO XL V5: Universal flash loader: TIF_UART (e.g. ESP32): Improved performance (reduced gaps and length of gaps) of UART transmission.
14. Flasher Compact V5: Universal flash loader: TIF_UART (e.g. ESP32): Improved performance (reduced gaps and length of gaps) of UART transmission.

RTT Viewer

1. 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

1. Command FWRITE: <Offset> parameter was applied to <EmuFile> only but not to <HostFile>. Fixed.

DLL

1. NXP iMXRT106x: Device was always halted after connect. Fixed.
2. Missing register mapping for IAPSR, EAPSR and IEPSR for ARMv8-M devices. Fixed.
3. Under special circumstances, incorrect behavior was executed on dialogs when pressing the escape button. Fixed.
4. NXP iMX8: Under special circumstances, reset did not work (e.g. when using FreeRTOS based applications). Fixed.
5. SiliconLabs EFM32PG22C: Some device names were not recognized by the J-Link software. Fixed.
6. SiliconLabs EFR32BG1: Some device names were not recognized by the J-Link software. Fixed.
7. SiliconLabs EFR32FG1: Some device names were not recognized by the J-Link software. Fixed.
8. SiliconLabs EFR32MG1: Some device names were not recognized by the J-Link software. Fixed.
9. SiliconLabs EFR32MG2: Some device names were not recognized by the J-Link software. Fixed.
10. SiliconLabs EZR32HG22: Some device names were not recognized by the J-Link software. Fixed.
11. SiliconLabs EZR32HG32: Some device names were not recognized by the J-Link software. Fixed.
12. SiliconLabs BGM210PB22: Added debug and flash programming support.
13. SiliconLabs BGM210PB32: Added debug and flash programming support.
14. SiliconLabs BGM210: Some device names were not recognized by the J-Link software. Fixed.
15. NXP Kinetis S32: user JTAG configuration was ignored. Fixed.
16. 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.
17. 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.

J-Flash

1. Fill Memory Area feature did not work correctly. Fixed.

Registration

1. Allowed re-registration for already registered devices.

Version V7.60f (2022-01-25)

DLL

1. NXP Kinetis K80: Under certain circumstances, QSPI flash programming did not work. Fixed.
2. NXP S32K148: FlexNVM programming did not work due to incorrect sector size. Fixed.
3. 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

1. 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.
2. Flasher ARM V5: Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
3. Flasher PRO V5: Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
4. Flasher Compact V5: Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
5. Flasher Portable PLUS V1: Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.

Version V7.60e (2022-01-20)

DLL

1. ST STM32G0B0xx series devices internal flash programming for second flash bank (starting @0x8040000) did not work. Fixed.
2. ST STM32L5: Flash programming with TZEN = 1, RDP = 0 was not possible. Fixed.
3. 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.

Firmware

1. 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.
2. 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.
3. 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.

Version V7.60d (2022-01-17)

DLL

1. ST STM32F2xxx series devices second internal flash bank was not correctly named as option memory. Fixed.
2. Microchip PIC32CX series devices, reset behavior for both cores was not correct. Fixed.
3. Microchip PIC32CX: Connect to the second core did not work. Fixed.
4. Maxim MAX32660 series device, size of used SRAM for flash programming algo. Fixed.
5. ST STM32G0: Improved unlock handling.

Firmware

1. 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.
2. Flasher ARM V4: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
3. Flasher PRO V4: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
4. Flasher ARM V5: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
5. Flasher PRO V5: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
6. Flasher PRO XL V5: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.
7. Flasher Compact V5: Stand-alone mode: Connecting to STM32 devices failed. Introduced in V7.60b. Fixed.

J-Flash SPI

1. 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.
2. After executing "Production programming" with F-RAM, any following operation (e.g. Production Programming, Erase, Program, Verify, ...) could crash J-Flash SPI. Fixed.

J-Link Package

1. Installer: Windows ARM64: The default destination directory was "Program Files (Arm)" instead of "Program Files". Fixed.
2. Installer: Windows ARM64: Code signatures for installed .exe and .dll files were missing. Fixed.
3. 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.

J-Scope

1. J-Scope did not handle bool type symbols correctly. Fixed.
2. The horizontal zoom levels for 20s/div and 50s/div were missing. Fixed.
3. With full sample buffer, J-Scope did wrongfully draw a line from the last sample to the first. Fixed.
4. When assigning default colors to symbols, the seventh symbol would get an invalid color assigned. Fixed.
5. Last column of symbol table was too wide. Fixed.
6. J-Scope did not display boolean variables by their truth value. Fixed.

Version V7.60c (2022-01-07)

DLL

1. MediaTek MT7697 series devices QSPI flash programming support wrong flash base address. Fixed.
2. NXP iMXRT106x: Under special circumstances, the device specific reset did not work properly. Fixed.
3. NXP iMXRT106x: Under special circumstances, flash programming failed. Fixed.
4. NXP iMXRT101x: Under special circumstances, the device specific reset did not work properly. Fixed.
5. NXP iMXRT102x: Under special circumstances, the device specific reset did not work properly. Fixed.
6. Verify command reported wrong mismatch address for CMSIS flash loaders. Fixed.
7. Under special circumstances, flash programming of external parallel CFI compliant NOR flashes could fail. Fixed.
8. PIC32CX series devices second core RSTC_MR register was not correctly restored after core reset. Fixed.

Version V7.60b (2021-12-22)

DLL

1. Microchip PIC32CX series devices reset for second Cortex-M4, fixed.
2. GigaDevice GD32F4xx series devices, RAM size used by flashloader, fixed.
3. NXP iMXRT106x: The power down counter was not handled which could cause issues after ~16s during flash programming. Fixed.
4. Added option byte flash programming support for HSXP HK32F030Mxx series devices.
5. STM32F family: User JTAG chain selection was ignored. Fixed.
6. STM32WB55 - FUS: Improved stability and terminal output.

Firmware

1. J-Link ULTRA+ V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
2. J-Link PRO V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
3. Flasher ARM V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
4. Flasher PRO V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
5. Flasher PRO XL V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
6. Flasher Compact V5: Infineon XMC1000 series: BMI switching from ASC_BSL to SWD0 failed because half-duplex UART handling was broken. Fixed.
7. Flasher PRO V5: Universal flash loader: Renesas RL78: Programming via half-duplex UART did not work properly. Fixed.
8. Flasher PRO XL V5: Universal flash loader: Renesas RL78: Programming via half-duplex UART did not work properly. Fixed.
9. Flasher Compact V5: Universal flash loader: Renesas RL78: Programming via half-duplex UART did not work properly. Fixed.
10. Flasher Portable PLUS V1: PDI interface (AVR XMEGA) did not work. Fixed.

Release Notes

1. Renamed "Flasher PRO-2GB V5" entries to "Flasher PRO XL V5" to match the official product name.

Version V7.60a (2021-12-16)

DLL

1. Added debug and internal flash programming support for HSXP HK32F030Mxx series devices.
2. Connect to some devices (e.g. CY8C6xx4_CM4) failed with error 'Algo error: Cannot find struct "FlashDevice"'. Introduced with V7.60. Fixed.

Firmware

1. 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

1. Added info about USB speed mode (full speed, high speed, ...) when connected via USB.
2. In script mode, currently executed command was not output via stdout. Fixed.

Configurator

1. Added setting to switch between WinUSB and SEGGER USB driver, if supported.

Control Panel

1. Merged STRACE and LIVETRACE tabs.
2. RTT Tab: Users can now switch between ASCII and hex view for all channels.

DLL

1. Added support for second Cortex-M4 core of Microchip PIC32CX series devices.
2. Added debug and internal flash programming support for Microchip PIC32CX series devices.
3. Added debug & flash programming support for Qorvo QPG6105.
4. Added debug and internal flash programming support for ST STM32WB10CC series devices.
5. 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.
6. Renesas RA: Added debug and flash programming support for RA2E2 family of devices.
7. Added PID for Cortex-A72 devices.
8. Added debug support for ST Stellar SR6P7G7x device R52 cores.
9. Added internal flash programming support for ST Stellar SR6P7G7x device cluster 0 R52_0 code flash.
10. Nordic Semiconductor nRF5340 (NET core): No reset was performed for the net core. Fixed.
11. Hilscher NetX90 Com Core RAM base address for RAMCode was wrong. Fixed.
12. Hilscher NetX90 Com core reset and halt after bootloader handling, fixed.
13. Hilscher NetX90 Com core used software reset instead of reset pin toggling within reset routine. Fixed.
14. 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.
15. Added debug and internal flash programming support for Renesas RA6T2 series devices.
16. Added internal flash programming support for ST Stellar SR6P7G7x device EEPROM, UTEST flash and BCS flash.
17. 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.
18. 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.
19. Added debug support for Microchip ATSAMA5D29 series devices.
20. Added debug support for ST Stellar SR6P7G7x device DSPH and DME Cortex-M4 cores.
21. Hilscher NetX90 Com core added support for Reset via reset pin and reset via SYSRESETREQ.
22. 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.

Firmware

1. J-Link ULTRA+ V5: Windows: Added support for switching to WinUSB enumeration / driver mode. (BTL does not support WinUSB)
2. J-Link PRO V5: Windows: Added support for switching to WinUSB enumeration / driver mode. (BTL does not support WinUSB)
3. J-Link EDU/BASE/PLUS V11: Windows: Added support for switching to WinUSB enumeration / driver mode. (BTL does not support WinUSB)
4. J-Link WiFi V1: Windows: Added support for switching to WinUSB enumeration / driver mode. (BTL does not support WinUSB)

GDB Server

1. Log: Warnings and errors are now printed in color.
2. Added AzureRTOS plugin.

J-Flash

1. Added shortcut "Alt+F10" for reading back selected sectors.

J-Link Package

1. Linux: Added multiple libraries as dependencies to the debian package that were missing before.
2. Installer: macOS: Added macOS universal installer.
3. Installer: Windows: Added Windows ARM64 installer.

J-Run

1. J-Run would crash when passing an ELF file generated by GCC 11.2. Fixed.

J-Scope

1. 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

1. "loadbin" command: Downloads to RAM and unknown memory was not verified which could lead to undetected download errors. Fixed.

DLL

1. Instruction trace default timestamp unexpectedly was changed to 64 cycles instead of 1024 as before when Ozone was used. Fixed.
2. Added support for command string "SetVerifyRAMDownload".

Firmware

1. J-Link EDU/BASE/PLUS V11: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
2. J-Link ULTRA+ V5: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
3. J-Link PRO V5: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
4. J-Link WiFi V1: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
5. J-Trace PRO Cortex V2: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
6. J-Trace PRO Cortex V3: ARMv8-A/R (e.g. Cortex-A53): Interrupts were not disabled on single step. Fixed.
7. 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.
8. 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-Scope

1. J-Scope could freeze when adjusting Y-Resolution. Fixed.

Version V7.58d (2021-12-02)

DLL

1. 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.
2. Renesas R7FS3A17C three internal flash banks (program flash, option-setting memory, data flash) were incorrectly displayed as one flash bank. Fixed.

Firmware

1. 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.
2. 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.
3. J-Link EDU/BASE/PLUS V11: VCOM: After closing a debug session, VCOM port became non-functional. Fixed.
4. J-Link WiFi V1: VCOM: After closing a debug session, VCOM port became non-functional. Fixed.
5. J-Trace PRO V2 Cortex: HSS: Sampling speeds < 1kHz (period > 1ms) did not work properly. Fixed.
6. 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.
7. J-Trace PRO V2 CortexM: HSS: Sampling speeds < 1kHz (period > 1ms) did not work properly. Fixed.
8. 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.
9. J-Trace PRO V3 Cortex: HSS: Sampling speeds < 1kHz (period > 1ms) did not work properly. Fixed.
10. 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.
11. J-Trace PRO V3 CortexM: HSS: Sampling speeds < 1kHz (period > 1ms) did not work properly. Fixed.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. Flasher PRO V5: Universal flash loader: ST STM8: Programming via SWIM interface (ACK / NACK handling) did not work properly. Fixed.
26. Flasher PRO XL V5: Universal flash loader: ST STM8: Programming via SWIM interface (ACK / NACK handling) did not work properly. Fixed.
27. Flasher Compact V5: Universal flash loader: ST STM8: Programming via SWIM interface (ACK / NACK handling) did not work properly. Fixed.
28. Flasher Portable PLUS V1: Universal flash loader: When selecting an algorithm that uses HW UART as target interface, the Flasher firmware could hang. Fixed.

GDB Server

1. FreeRTOS plugin: Stepping over a CreateTask() call before scheduler of FreeRTOS was started, could result in CPU not halting after step over operation. Fixed.
2. FreeRTOS plugin: Task creation before scheduler start was not detected / handled properly. Fixed.

J-Scope

1. Under certain circumstances, sample rate label in new project dialog was showing broken letter. Fixed.

Version V7.58c (2021-11-24)

Commander

1. MacOS: Under some circumstances, the commander would close if an empty line was passed. Fixed.
2. If ExitOnError was specified and the initial connection to the J-Link failed, the Commander did not close. Fixed.

DLL

1. Renesas R7FS3A7: Under special circumstances (no pullup on QSPI_IO2/ QSPIIO3), programming an external QSPI flash could fail. Fixed.
2. Renesas R7FS7G2: Under special circumstances (no pullup on QSPI_IO2/ QSPIIO3), programming an external QSPI flash could fail. Fixed.
3. 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.
4. ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): ROM table scan: Some CoreSight SoC-600 components were not identified properly, textoutput. Fixed.
5. 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.
6. NXP iMX8M: Under special circumstances, a debug session did not work as expected. Added a device specific reset. Fixed.
7. Internal flash programming support for Microchip PIC32CX series devices. Fixed.

Firmware

1. J-Link OB-K22-CortexA: Improved drag & drop flash programming support for target devices with erased value != 0xFF.
2. J-Link OB-K22-CortexM: Improved drag & drop flash programming support for target devices with erased value != 0xFF.
3. J-Link OB-K22-Qorvo: Improved drag & drop flash programming support for target devices with erased value != 0xFF.

GDB Server

1. GUI: The configuration dialog had no option to enable "Generate logfile" before starting a GDB session. Fixed.
2. GUI: The location of the generated logfile was not visible. Fixed.
3. 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

1. Under certain circumstances opening the symbol selection dialog could cause a crash. Fixed.

Manual

1. UM08022: Replaced occurrences of "MSD mode" with "file access mode"
2. UM08022: Replaced occurrences of "J-Link mode" with "PC-based mode"

Version V7.58b (2021-11-16)

Configurator

1. Show VCOM port drop down menu only in case J-Link has more than one VCOM available. Fixed.

DLL

1. 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.
2. ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. J-Link EDU/BASE/PLUS V11: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
7. J-Link ULTRA+ V5: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
8. J-Link PRO V5: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
9. J-Link WiFi V1: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
10. J-Trace PRO Cortex V2: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.
11. J-Trace PRO Cortex V3: ARMv8-A/R (e.g. Cortex-A53 / Cortex-R52): Added support for CoreSight SoC-600.

J-Scope

1. macOS: J-Scope would not properly launch. Fixed.

Version V7.58a (2021-11-11)

DLL

1. ST STM32U5 device series: Extended support to include secure flash address.
2. J-Link Commander rreg and wreg command for 64bit CPUs. Fixed.

Firmware

1. J-Trace PRO V2 Cortex: Enable 5V target power did not work properly. Introduced in V7.58. Fixed.
2. 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.
3. J-Trace PRO V2 CortexM: Enable 5V target power did not work properly. Introduced in V7.58. Fixed.
4. 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.
5. 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.
6. 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.
7. 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-Scope

1. When using RTT, trigger settings would not be used. Fixed.
2. Under certain circumstances, changing the options could cause crash. Fixed.

Manual

1. UM08002: Corrected syntax (return value) of JLINKARM_SWD_StoreRaw().

Version V7.58 (2021-11-04)

Control Panel

1. Breakpoints tab: Added commonly used default values.

DLL

1. Rasberry Pi RP2040: Added RTT search ranges.
2. Added functionality for J-Link command string "SetSkipRestoreRAMCode".
3. Added support for the following Macronix SPI flashes MX25UW51245 to SPIFI-Lib.
4. Added missing alias for SiLabs EFM32PG22CxxxF512 series device.
5. NXP MIMXRT11xx_M4: Added FlexSPI (Alias) region.
6. Renesas RA: Added debug and flash programming support for RA4E1 family of devices.
7. Renesas RA: Added debug and flash programming support for RA6E1 family of devices.
8. Added debug and flash programming support for NXP LPC802UK.
9. Added debug and flash programming support for NXP LPC804UK.
10. Silicon Labs EFR32FG23xxx: Added debug and flash programming support for EFR32FG23xxx family of devices.
11. Silicon Labs EFR32ZG23xxx: Added debug and flash programming support for EFR32ZG23xxx family of devices.
12. Added debug and internal flash programming support for Microchip PIC32CMxxxx series devices.
13. Silicon Labs EFM32PG23xxx: Added debug and flash programming support for EFM32PG23xxx family of devices.
14. ST STM32G0 series: Improved remapping detection provided by boot configuration.
15. Added debug support for NucleiSys N203 (RV32) device/core.
16. Added debug support for NucleiSys NX605 / NX607 / NX608 (RV64) device/core.
17. Added debug support for NucleiSys UX605 / UX607 / UX608 (RV64) device/core.
18. Added debug support for NucleiSys N203E (RV32) device/core.
19. Added debug support for NucleiSys N900 / N900MP (RV32) device/core.
20. Added debug support for NucleiSys NX900 / NX900MP (RV64) device/core.
21. Added debug support for NucleiSys UX900 / UX900MP (RV64) device/core.
22. Added OctoSPI flash programming support for STM32H7A3xx and STM32H7B3xx series devices.
23. Added debug and flash programming support for NXP MK22FN128xxx12 series devices.
24. Added flash programming support for RWW section of Microchip ATSAML22 series devices.
25. Added flash programming support for RWW section of Microchip ATSAMHA0 and ATSAMHA1 series devices.
26. 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.
27. When exec command DisableLTRACEAnalysis is used set, backtrace data can now be displayed by debug tools e.g. Ozone.
28. Added flash programming support for RWW section of Microchip ATSAMR30 series devices.
29. Added debug support for Microchip SAM7X7x series.
30. Added debug support for Renesas RZ/V2L series devices (e.g. "R9A07G054L_M33").

Firmware

1. Flasher PRO V5: ESP32: Flash programming via UART could fail due to Tx data failure inside Flasher firmware. Fixed.
2. Flasher PRO XL V5: ESP32: Flash programming via UART could fail due to Tx data failure inside Flasher firmware. Fixed.
3. Flasher Compact V5: ESP32: Flash programming via UART could fail due to Tx data failure inside Flasher firmware. Fixed.

J-Flash SPI

1. Added support for the following Macronix SPI flashes MX25UW25345G and MX25UW51245.

J-Link Package

1. Linux: The .deb package did not name libsm6 as dependency. Fixed.

J-Scope

1. Improved UI handling for graphs with a base line that is out of the visible area.
2. Changed graph Y-Offset to be measured in divs, where one div equals 100px.

Manual

1. UM08022: Added Logfile section and improved some chapters according to the feedback from the "Flasher Reader Test"

Version V7.56d (2021-10-29)

Commander

1. Linux: Due to a bug introduced in 7.56c, the last character of console user input was cut off for some applications. Fixed.

DLL

1. 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

1. J-Trace PRO V2 Cortex: Fixed VTref feature did not work properly. Fixed.
2. J-Trace PRO V2 CortexM: Fixed VTref feature did not work properly. Fixed.

Version V7.56c (2021-10-28)

Commander

1. All Platforms: CTRL + C was not handled correctly. Fixed.
2. Users were not notified that a power-cycle is required after changing VTref from fixed to not fixed. Fixed.

Control Panel

1. Commander tab: Browser autofill feature could interfere with Arrowkey functionality. Fixed.

DLL

1. SiliconLabs EFM32GG12 series devices size of bootloader flash memory. Fixed.
2. Debugging via cJTAG did not work on NucleiSys RV32 cores (N1xx, N2xx, N3xx, N6xx, ...). Fixed.
3. Debugging via cJTAG did not work on NucleiSys RV64 cores (NX6xx, UX6xx, ...). Fixed.
4. Debugging via cJTAG did not work on SiFive E3, E7 series cores. Fixed.
5. Debugging via cJTAG did not work on SiFive S2, S3, S5, S7 series cores. Fixed.
6. PLL init for STM32H7A3xx and STM32H7B3xx for internal flash programming. Fixed.
7. NXP S32K344: Erasing the data flash did not work on recent silicon revisions. Fixed.
8. NXP S32K344: Connection via JTAG as target interface did not work. Fixed.

Firmware

1. 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).
2. J-Link ULTRA+ V5: Cortex-M: Improved memory read speed for SWD interface by up to 20%. (20% for SWD frequencies > 10 MHz).
3. J-Link PRO V5: Cortex-M: Improved memory read speed for SWD interface by up to 20%. (20% for SWD frequencies > 10 MHz).
4. 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

1. Added progress bar for elf parsing process.
2. Improved speed of symbol selection dialog initialization.
3. Added option to directly edit Y-Offset of symbols by double clicking the corresponding Y-Offset cell.
4. "Decrease Y-Resolution" action did not always decrease with the correct step size. Fixed.
5. Graph tooltip was shown even when J-Scope was not the active window. Fixed.
6. Adding new symbols after completely emptying the list of active symbols did not work. Fixed.
7. Changing the ELF file or HSS/RTT mode through the options did not work. Fixed.
8. In some cases, restarting read could lead to crash. Fixed.
9. Under certain circumstances parsing of an elf file could fail. Fixed.
10. Zooming in did not cause autoscroll to turn off when it should. Fixed.
11. It was possible to loose the visibility of the graph when zooming into an area without data. Fixed.
12. Zooming in when in Autoscroll mode caused the first graph to be misaligned. Fixed.
13. The main window was placed wrong when using multi-monitor setups. Fixed.
14. In RTT mode it was possible to remove active symbols from the symbol table. Fixed.
15. Under certain circumstances opening a project could cause a crash. Fixed.

Version V7.56b (2021-10-18)

Commander

1. TestRSpeed: When the target was halted, the measured read speeds were wrong. Fixed.

Configurator

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

DLL

1. Renesas RA6M4: QSPI flash banks were configured as "always present" which could cause issues during erase for hardware without QSPI flash. Fixed.
2. Renesas RA6M5: QSPI flash banks were configured as "always present" which could cause issues during erase for hardware without QSPI flash. Fixed.
3. Firmware update dialog: It could happen that the very last line of text inside the log was cut off vertically. Fixed.
4. J-Link Commander erase + address range command flash bank size calculation. Fixed.
5. Silabs EFM32GG11 series and EFM32TG11 series devices internal flash programming, check for page-aligned programming. Fixed.

DLL Updater

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

Firmware

1. J-Link PRO V5: Under special circumstances, a USB communication timeout could occur during a debug session. Fixed.
2. J-Link ULTRA+ V5: Under special circumstances, a USB communication timeout could occur during a debug session. Fixed.
3. J-Link OB-K22-CortexA: Added pin override function for TCK, TMS, TDI, TDO, NRESET, TRST, Pin17 and RTCK.
4. J-Link OB-K22-CortexM: Added pin override function for TCK, TMS, TDI, TDO, NRESET, TRST, Pin17 and RTCK.
5. J-Link OB-K22-RISCV: Added pin override function for TCK, TMS, TDI, TDO, NRESET, TRST, Pin17 and RTCK.
6. J-Link OB-K22-CortexA: Increased the max. supported baud-rate of VCOM0 and VCOM1 from 1 Mbps to 2 Mbps.
7. J-Link OB-K22-CortexM: Increased the max. supported baud-rate of VCOM0 and VCOM1 from 1 Mbps to 2 Mbps.
8. J-Link OB-K22-RISCV: Increased the max. supported baud-rate of VCOM0 and VCOM1 from 1 Mbps to 2 Mbps.

GDB Server

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

J-Flash Lite

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

J-Flash SPI

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

J-Mem

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

J-Scope

1. Loading ELF-file could cause crash. Fixed.
2. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

License Manager

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

RTT

1. 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

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

Registration

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

Remote Server

1. It could happen that the very last line of text inside the log was cut off vertically. Fixed.

SWO Viewer

1. 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

1. A misleading error message was shown in case a mandatory file used to update an application was missing. Fixed.

J-Scope

1. Symbol view table was not always correctly updated when adding active symbols. Fixed.
2. Parsing ELF files with arrays of size zero would cause crash. Fixed.

Remote Server

1. JLINK_PIN_Override API calls did not work correctly (communication errors were thrown). Fixed.
2. JLINK_TIF_UART API calls did not work correctly (communication errors were thrown). Fixed.

Version V7.56 (2021-10-07)

CCS Plugin

1. Added Cortex-A9 support.

Commander

1. 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

1. 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

1. Changed appearance of the active menu tab to white font on black background.
2. Added Watchpoint functionality (Set/Remove) to the "Breakpoints" tab.
3. Settings: Added section "Application download"
4. Settings: Moved settings for "L1 Verify" and "L2 Verify" from "Flash download" to "Application download"
5. Settings: Added link to SEGGER Wiki for explanation of L1 Verify and L2 Verify.

DLL

1. Added additoinal aliases for Atmel ATSAMA5 series devices.
2. Improved erase and programming speed of Nuvoton M031/M032 series devices.
3. Disabling L1 Verify now also prevents readback when downloading into RAM.
4. 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.
5. Added debug and flash programming support for TI CC2652RB series device.
6. Added debug and internal flash programming support for Maxim MAX32675 series device.
7. Added debug and flash programming support for Infineon CYPM1311 series devices.
8. 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)
9. 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".
10. ST STM32G0x1 series devices base address for second internal flash bank. Fixed.
11. Renesas RA4M2: Option byte programming did not work under certain circumstances. Fixed.
12. Renesas RA4M2: Enabled RAMCode based algorithm by default.
13. 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)
14. Renesas RA6M4: Enabled RAMCode based algorithm by default.
15. 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)
16. Renesas RA6M5: Enabled RAMCode based algorithm by default.
17. 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)
18. Added debug & flash programming support for Qorvo QPG5072 series.
19. Added support for the following Windbond SPI flashes W25Q32JW, W25Q64JW, W25Q128JW, W25Q256JW, W25Q512NW, W25Q01NW, W25Q01JV to SPIFI-Lib.
20. Added support for the following Macronix SPI flashes MX25LW51245, MX25UW12345G, MX25UW25345G to SPIFI-Lib.

Firmware

1. 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).
2. 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).
3. 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).
4. 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).
5. 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).
6. J-Link ULTRA+ V5: cJTAG: Increased max. communication speed: 16 MHz -> 33 MHz.
7. J-Link ULTRA+ V5: ICSP PIC32: Increased max. communication speed: 16 MHz -> 33 MHz.
8. J-Link ULTRA+ V5: VCOM: Added support for odd/even parity.
9. J-Link PRO V5: cJTAG: Increased max. communication speed: 16 MHz -> 33 MHz.
10. J-Link PRO V5: ICSP PIC32: Increased max. communication speed: 16 MHz -> 33 MHz.
11. J-Link PRO V5: VCOM: Added support for odd/even parity.
12. J-Link OB-K22-Qorvo: Added support for new J-Link OB.
13. J-Link ULTRA+ V5: Download speed: Regression was introduced in V7.54c which slowed down download speeds when using higher JTAG/SWD speeds. Fixed.
14. J-Link PRO V5: Download speed: Regression was introduced in V7.54c which slowed down download speeds when using higher JTAG/SWD speeds. Fixed.
15. MCU-Link: Changed the state of some unused pins (pull to no pull resistor etc) as requested by NXP.
16. MCU-Link: VCOM: 1st character received by MCU-Link and forwarded to terminal application could get lost. Fixed.
17. Flasher Compact V5: ASCII command interface could hang on certain commands like "#BAUDRATE" and "#FLIST". Fixed.

GDB Server

1. Mac M1: Connecting to some devices did not work. Fixed.

J-Flash SPI

1. Windows: 64-bit build did crash under certain circumstances when saving configs to Flasher. Fixed.
2. Added StatusRegFormat parameter to Flash settings.
3. Possible crash when erasing sectors but the connect failed. Fixed.
4. Added support for the following Windbond SPI flashes W25Q32JW, W25Q64JW, W25Q128JW, W25Q256JW, W25Q512NW, W25Q01NW and W25Q01JV.
5. Added support for the following Macronix SPI flashes MX25LW51245 and MX25UW12345G.

J-Scope

1. Under certain circumstances, parsing ELF file could cause a crash. Fixed.
2. Searching symbols in symbol selection dialog caused crash. Fixed.

RTT Logger

1. All Platforms: CTRL + C was not handled correctly. Fixed.

Version V7.54d (2021-09-28)

DLL

1. STM32U585QE and STM32U585ZE device descriptions passed to DLL by KEIL uVision were recognized as "unknown" device. Fixed.
2. Microchip ATSAMA5D2x Family: Some device names were not detected by the J-Link software (e.g. "ATSAMA5D27CLD2G"). Fixed.

DLL Updater

1. 64-bit version: Updating the J-Link DLL for Microchip MPLAB X failed. Fixed.

Firmware

1. Flasher Portable PLUS V1: Stand-alone mode: Direct SPI flash programming: Erase/Program/Verify progress bar was not updated properly. Fixed.
2. J-Link EDU Mini V1: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
3. J-Link EDU/BASE/PLUS V10: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
4. J-Link EDU/BASE/PLUS V11: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
5. J-Link ULTRA+ V4: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
6. J-Link ULTRA+ V5: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
7. J-Link PRO V4: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
8. J-Link PRO V5: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
9. J-Link WiFi V1: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.
10. J-Link-OB-K22-RISCV: RISC-V: Debugging of RV32E based MCUs did not work properly. Fixed.

J-Flash SPI

1. Errors due to missing licenses are now always printed to log regardless of the configured log level.

J-Flash SPI CL

1. Errors due to missing licenses are now always printed to log (and stdout) regardless of the configured log level.
2. All log messages (stdout output) were missing, regardless of the configured log level. Introduced with V7.22a. Fixed.

Version V7.54c (2021-09-20)

DLL

1. 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.
2. STM32L5 series devices: Sector erase was not working correctly. Fixed.

Firmware

1. 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.
2. 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-Scope

1. Zoom buttons were not set to active when opening a project. Fixed.
2. Added option to select symbol from struct arrays.
3. Added J-Scope user guide to "Help" menu.
4. Improved performance of graph drawing.

Version V7.54b (2021-09-14)

Commander

1. Calling "erase" command with wrong parameter resulted in chip erase was triggered. Fixed.

DLL

1. NXP K32L2 series: Implemented RAM-ranges were not correct. Fixed.
2. NXP LPC55S0x/LPC550x series: Flash sizes were not correct for the variants with < 256KB internal flash. Fixed.
3. NXP LPC55xx family: Incorrect flash size was used for some 64 KB and 128 KB flash devices. Fixed.
4. NXP LPC55xx family: Some non existing device names were displayed. Corrected.
5. NXP LPC55xx family: The secure flash region was enabled for some devices without TrustZone feature. Fixed.
6. NXP LPC55xx family: The secure flash region was not enabled for the LPC55S36. Fixed.
7. NXP iMXRT101x devices: Added device specific reset behavior.

Firmware

1. Flasher Portable PLUS V1: O2Micro OZ935xx: Flash programming did not work in stand-alone mode. Fixed.
2. Flasher ARM V5: O2Micro OZ935xx: Flash programming did not work in stand-alone mode. Fixed.
3. Flasher PRO V5: O2Micro OZ935xx: Flash programming did not work in stand-alone mode. Fixed.

J-Scope

1. Array base type and base type size were not correctly read from .elf file. Fixed.
2. Trigger selection and symbol view table were not always correctly updated when removing/adding active symbols. Fixed.
3. J-Scope did not save project files correctly. Fixed.
4. It was not possible to read float/double symbols. Fixed.

Version V7.54a (2021-09-07)

Configurator

1. IP settings of a probe could not be changed via IP, only when connecting the probe via USB. Fixed.
2. When a configuration could not be applied (e.g. because the desired probe/ programmer was not connected), no message box was shown. Fixed.
3. 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.
4. The "Check segger.com" text in the host firmware column for a Flasher ATE was not aligned with the text for other rows. Fixed.

DLL

1. ARMv8-AR (e.g. Cortex-A53): When listing processor features, EL2 support was listed twice instead of EL2 and EL3 support. Fixed.
2. CoreSight SoC-600: Having a Cortex-M3/M4 with ETB, the ETB was not correctly detected in the ROM table. Fixed.
3. Multiple Nuvoton device descriptions passed to DLL by KEIL uVision were recognized as "unknown" device. Fixed.
4. Multiple Nuvoton device descriptions passed to DLL by IAR EWARM were recognized as "unknown" device. Fixed.

Firmware

1. 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.)
2. 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.)
3. 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.)
4. 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.)
5. 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.)
6. 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.)
7. 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.)
8. 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.)
9. 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.)
10. 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.)
11. 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.

Version V7.54 (2021-09-01)

Commander

1. Improved documentation of available commands shown with "?".
2. Obsolete/deprecated commands are not shown "?" anymore.
3. Expended functionality of the command "?". "? [<Command>]" now shows additional information about <Command> if passed.
4. Added function WJTAGIR and WJTAGDR which extend & replace functions WJC and WJR.
5. A visual bug could occur when using the "?" command. Fixed.
6. Improved description of "?" command.
7. Rearranged display of commands when "?" command is called to be in a more logical order.
8. Added "ClearWP" as long command for "ClrWP".
9. Added long names for some commands that only had short names.
10. "?" Command: Long and short names are now all printed in CamelCase.
11. ARMv8-M (Cortex-M23, Cortex-M33, ...): Added MSPLIM and PSPLIM to the registers that are shown on halt().

DLL

1. Added native trace buffer support for single core ST STM32H7 series.
2. Added exec command DisableLTRACEAnalysis.
3. Added debug & flash programming support for TI CC1312R7 and CC1352P7 series.
4. Added debug & flash programming support for TI CC2652R7 and CC2652P7 series.
5. Generic SWO init uses devices ROM Table TPIU address now where available.
6. Added debug and flash programming support for not yet listed ST STM32G061 devices.
7. Added debug and flash programming support for Infineon CYPM1011 series devices.
8. Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
9. Added part numbers as additoinal aliases for Infineon PMG1 series devices.
10. 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
11. Tested and verified flash programming support of Winbond W25Q128JV with QSPI based flash algorithms.
12. NXP iMXRT117x devices: Flashloader did not save and restore all used registers. Fixed.
13. Added SPI Flash support in SPIFI-Lib for Adesto AT25FF081A, AT25FF161A and AT25XE161D series devices.
14. Added SPI Flash support in SPIFI-Lib for GigaDevice GD25Q257D series devices.
15. ST STM32H7Axx / STM32H7Bxx series devices issues with voltage scaling (VOS) and flash latency settings for flash programming. Fixed.
16. Infineon CYPM1011 series devices init sequence after restoring VTref configuration. Fixed.
17. Multi-byte units will be displayed without "i" again. (KiB, MiB, GiB,... => KB, MB, GB,...).
18. Suppress continues verbose output when calling J-Link ScriptFile function "HandleBeforeMemAccessWrite".
19. Multiple Nuvoton device descriptions passed to DLL by KEIL uVision were recognized as "unknown" device. Fixed.
20. Multiple Nuvoton device descriptions passed to DLL by IAR EWARM were recognized as "unknown" device. Fixed.
21. ST STM32G0: When the devices was read and write protected, the unlock dialog was shown twice. Fixed.
22. Cypress CYT2Bxxxx and CYT4BFxxx series devices Reset for Coretx-M4 and Cortex-M7. Fixed.
23. GigaDevice GD25LQ256D serial flash enter exit 4 byte address mode, fixed.
24. 64Bit DLL Updater did not find MPLAB-X. Fixed.
25. GigaDevice GD25B512ME serial flash added programming support within SPIFI-Lib.
26. Added flash programming and debug support for NXP LPC553x/LPC55S3x devices.
27. NXP LPC5411x series devices internal flash programming. Fixed.
28. iMXRT10xx devices: Improved reset behavior.

Firmware

1. Flasher ARM V5: Stand-alone mode: Added support for Cortex-A/R (ARMv7) based devices. (E.g. Xilinx Zynq-7000 series)
2. Flasher PRO V5: Stand-alone mode: Added support for Cortex-A/R (ARMv7) based devices. (E.g. Xilinx Zynq-7000 series)
3. Flasher PRO XL V5: Stand-alone mode: Added support for Cortex-A/R (ARMv7) based devices. (E.g. Xilinx Zynq-7000 series)
4. Flasher Portable PLUS V1: Stand-alone mode: Added support for Cortex-A/R (ARMv7) based devices. (E.g. Xilinx Zynq-7000 series)
5. Flasher ARM V5: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
6. Flasher PRO V5: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
7. Flasher PRO XL V5: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
8. Flasher Compact V5: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
9. Flasher Portable PLUS V1: Stand-alone mode: Added support for big endian Cortex-A/R (ARMv7) based devices. (E.g. TI TMS570 series)
10. J-Link OB-K22-CortexA: Added support for cJTAG target interface.
11. J-Link OB-K22-CortexM: Added support for cJTAG target interface.
12. J-Link OB-K22-RISCV: Added support for cJTAG target interface.
13. Flasher PRO V5: Universal flash loader: Under special circumstances, Erase() could hang if flash bank started at addr 0x0. Fixed.
14. Flasher PRO XL V5: Universal flash loader: Under special circumstances, Erase() could hang if flash bank started at addr 0x0. Fixed.
15. Flasher Compact V5: Universal flash loader: Under special circumstances, Erase() could hang if flash bank started at addr 0x0. Fixed.
16. Flasher Portable PLUS V1: Universal flash loader: Under special circumstances, Erase() could hang if flash bank started at addr 0x0. Fixed.

J-Flash

1. Removed support for so called custom RAMCodes as they have been replaced by the Open Flashloader.
2. 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

1. Added SPI Flash support for Adesto AT25FF081A, AT25FF161A and AT25XE161D series devices.
2. Added SPI Flash support for GigaDevice GD25Q257D series devices.
3. GigaDevice GD25LQ256D serial flash enter exit 4 byte address mode, fixed.
4. GigaDevice GD25B512ME serial flash added programming support.

J-Link Package

1. 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
2. Multi-byte units will be displayed without "i" again. (KiB, MiB, GiB,... => KB, MB, GB,...).

J-Scope

1. Crash when using RTT mode. Fixed.
2. When drawing points, the color of the points did not match the selected color. Fixed.
3. Improved usability on displays with scaling factor differing from 100%.
4. It was possible to use invalid characters for the symbol selection of arrays. Fixed.
5. Using the arrow up/down shortcuts to change the zoom level was no longer possible after the symbol table was focused. Fixed.
6. Added arrow key left/right as shortcuts to move the graph to the left/right.
7. Added key "Home" as shortcut to move the graph to the start.
8. Added key "End" as shortcut to move the graph to the end.

RTT Logger

1. The names and indexes of all available buffers are now also printed on connect.

Version V7.52d (2021-08-17)

Commander

1. "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.
2. Linux: Interactive command prompt (via shared libedit) did not work under some Debian-based distributions. Fixed.

DLL

1. Under certain circumstances when tracing multiple stacked exception calls, trace analysis might be incorrect. Fixed for both live and buffered trace.
2. GigaDevice GD32F1xx series devices internal flash programming sector size. Fixed.
3. NXP iMXRT102x: RAM debugging did not work when no valid image was present in the external memory. Fixed.
4. Flash programming SPIFI algorithm for Telink TLSR9518xxx series devices, fixed.
5. 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.
6. ARMv8-M baseline (e.g. Cortex-M23): MSPLIM and PSPLIM were always read as 0 / writes were ignored. Fixed.
7. ST STM32H7Axx and STM32H7Bxx series devices changed RAM address to DTCM RAM for flashalgos. Fixed.

Firmware

1. Flasher Portable PLUS V1: Firmware crashed when using cJTAG as target interface. Fixed.

J-Flash

1. License dialog: Deleting certain licenses did not work. Fixed.
2. License dialog did not display certain licenses correctly. Fixed.
3. 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.
4. NXP iMXRT102x: Flash programming did not work when no valid image was already present in it. Fixed.

J-Flash SPI

1. License dialog: Deleting certain licenses did not work. Fixed.
2. License dialog did not display certain licenses correctly. Fixed.

J-Scope

1. HSS: Using HSS caused a minor memory leak. Fixed.
2. HSS: Using more variables then supported by the J-Link probe caused a crash. Fixed.
3. When starting data sampling failed for some reason, the user was not informed. Fixed.
4. Additional variables could be added while active data sampling, which could cause a crash. Fixed.
5. Improved reading performance.
6. Using shortcuts "+" and "-" to adjust the Y-Resolution caused crash when no symbol was selected. Fixed.
7. When canceling the color selection dialog, the color of the symbol was set to black. Fixed.
8. Crash when using RTT mode due to missing GUI element. Fixed.
9. If at project creation no symbols were selected, it was not possible to add symbols since the relevant button was missing. Fixed.
10. Save dialog did not open when exiting the app and the user was prompted with the option to save. Fixed.
11. When reading data tooltip always showed the symbol data at cursor position, blocking all other tooltips (e.g. button tooltips). Fixed.

Version V7.52c (2021-08-10)

Commander

1. ARMv8-A/R (e.g. Cortex-A53): ELR_EL1/2/3 were not shown on "regs" command. Fixed.
2. ARMv8-A/R (e.g. Cortex-A53): SP_EL1/2/3 were not shown on "regs" command. Fixed.

DLL

1. ARMv8-A/R (e.g. Cortex-A53): Added more information about supported exception levels, FPU implemented, ... to the connect sequence.
2. Big endian Cortex-A and Cortex-R devices flash programming, fixed.
3. Cortex-M ARMv8-M targets: Watchpoint (WP) handling (for Cortex-M23, Cortex-M33) did not work for an address + data matching WP. Fixed.
4. NXP LPC54xx: Under special circumstances, flash programming could fail. Fixed.
5. GUI Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.
6. Restore of SPIFI flash programming algorithm for Xilinx Zynq7000 series devices. Fixed.

Firmware

1. 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.
2. 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.
3. J-Link EDU/BASE/PLUS V11: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
4. J-Link ULTRA+ V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
5. J-Link PRO V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
6. J-Link WiFi V1: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
7. Flasher ARM V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
8. Flasher PRO V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
9. Flasher Compact V5: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
10. J-Trace PRO V2 Cortex: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
11. J-Trace PRO V2 CortexM: Added Exec "VTrefTmp" to set VTref temporarily via Exec during runtime.
12. 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.
13. 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.
14. J-Link ULTRA+ V4: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
15. J-Link ULTRA+ V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
16. J-Link PRO V4: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
17. J-Link PRO V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
18. J-Link WiFi V1: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
19. Flasher ARM V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
20. Flasher PRO V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
21. Flasher Compact V5: ARMv8-A/R (e.g. Cortex-A53): SP_EL3 was not read / written correctly (SP_EL2 was accessed instead). Fixed.
22. 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.
23. 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.
24. LPC-Link2: Updated Terms of Use. See http://www.segger.com/lpc-link-2.html
25. LPC-Link2 on-board: Updated Terms of Use. See http://www.segger.com/lpcxpresso-v2.html
26. MCU-Link: Updated Terms of Use. See http://www.segger.com/mcu-link.html
27. Flasher ARM V5: Raspberry Pi RP2040: Flash programming in stand-alone mode did not work properly. Fixed.
28. Flasher PRO V5: Raspberry Pi RP2040: Flash programming in stand-alone mode did not work properly. Fixed.
29. Flasher PRO XL V5: Raspberry Pi RP2040: Flash programming in stand-alone mode did not work properly. Fixed.
30. Flasher Compact V5: Raspberry Pi RP2040: Flash programming in stand-alone mode did not work properly. Fixed.
31. J-Link EDU Mini V1: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
32. J-Link EDU/BASE/PLUS V11: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
33. J-Link ULTRA+ V5: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
34. J-Link PRO V5: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
35. J-Link WiFi V1: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.
36. J-Link-OB-K22-RISCV: RISC-V: Added support for MCUs that only implement "Abstract Access Memory" (AAM) as memory access method.

GDB Server

1. Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.

J-Flash

1. NXP LPC54xx: Flash programming did not work because unavailable RAM (SRAM1) was used. Fixed.
2. Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.

J-Flash Lite

1. Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.

J-Flash SPI

1. Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.

J-Scope

1. J-Scope did not properly find RTT variables. Fixed.
2. Default window size was not FullHD compatible. Fixed.
3. "Add Symbol" button was visible in RTT mode. Fixed.
4. .out files were not selectable. Fixed.
5. JLinkScript files with a different ending than ".JLinkScript" could not be selected. Fixed.

Remote Server

1. Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.

SWO Viewer

1. Message boxes: Pressing Ctrl + C to copy the messagebox contents did not work. Fixed.

Version V7.52b (2021-08-03)

DLL

1. ARMv8-A: J-Link script files: Specifying an AP map via JLINK_ExecCommand("CORESIGHT_AddAP ..."); did not work properly. Fixed.
2. ARMv8-R: J-Link script files: Specifying an AP map via JLINK_ExecCommand("CORESIGHT_AddAP ..."); did not work properly. Fixed.
3. Microchip SAMA7G54: Updated device name from "ATSAMA7G54" to "SAMA7G54". Fixed.
4. Reset strategy "Reset + Halt after bootloader using watchpoint" did not work for ARMv8M based devices. Fixed.
5. NXP iMXRT11xx devices: SPI flash: Flash download did not work with flashes > 64MB. Fixed.
6. STM32U5: Flash programming/Erase failed when TrustZone is enabled and CPU is in non-secure state. Fixed.

Firmware

1. J-Trace PRO V2 Cortex: Debugging via Infineon SPD target interface did not work properly. Fixed.
2. J-Trace PRO V2 CortexM: Debugging via Infineon SPD target interface did not work properly. Fixed.

J-Flash

1. Welcome Dialog: The "Do not show this message again" checkbox did not have any effect. Introduced with V6.70. Fixed.

J-Link Package

1. Installer: Windows: Renamed J-Link i386 installer from "JLink_Windows_Vxxxx.exe" to "JLink_Windows_Vxxxx_i386.exe"
2. Installer: Windows: Renamed J-Link x86_64 installer from "JLink_Windows_x86_64_Vxxxx.exe" to "JLink_Windows_Vxxxx_x86_64.exe"
3. Installer: Windows: Renamed Flasher i386 installer from "Flasher_Windows_Vxxxx.exe" to "Flasher_Windows_Vxxxx_i386.exe"
4. Installer: Windows: Renamed Flasher x86_64 installer from "Flasher_Windows_x86_64_Vxxxx.exe" to "Flasher_Windows_Vxxxx_x86_64.exe"

Manual

1. UM08002: Added indirect API function "JLINK_IFUNC_CORESIGHT_ACC_APDP_REG_MUL".

Registration

1. Registering a probe/ programmer did not change its "Registered" status inside the utility. Fixed.

Version V7.52a (2021-07-28)

Firmware

1. J-Link ULTRA+ V4: Some older units (4.3, 4.2) were stuck in BTL after firmware update. Introduced with V7.52. Fixed.
2. J-Link PRO 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

1. Added native background memory access for Renesas RZ/A2M series so things like SEGGER RTT work without stop mode.
2. Raspberry RP2040 improved SPI flash programmng speed.
3. Added new reset strategy: Reset + Halt after bootloader using watchpoint. (https://wiki.segger.com/Reset_and_Halt_After_Bootloader)
4. Added new J-Link Command String which can be uesed to specify the watchpoint address when using Reset + Halt after bootloader reset strategy.
5. Added debug support for Microchip SAMA7G54.
6. 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.
7. Added debug and internal flash programming support for Maxim MAX32655 series device.
8. STM32L5: Flash programming did not work properly when Trustzone was enabled and some sectors were set to non-secure while others were secure. Fixed.
9. ST STM32H7Axx series devices flash signal delay during flash programming. Fixed.
10. Microchip ATSAML10 and ATSAML11 series devices added internal data flash programming support.
11. NXP i.MXRT116x Cortex-M4 debug: Software breakpoints did not work correctly in case the LMem caches were enabled. Fixed.
12. NXP i.MXRT116x series: Connect sequence to the Cortex-M4 failed under certain circumstances. Fixed.
13. 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.
14. Microchip SAM9X60 series devices were handled as ARM920T based while they are ARM926EJ-S based. Fixed.
15. GigaDevice GD32F450xx series devices working RAM size, fixed.
16. Added debug support for Syntacore SCR3 (RV32) device/core.
17. Added debug and flash programming support for NXP MKE12Z series.
18. Some device aliases were missing for the NXP MKE13Z series. Fixed.
19. NXP i.MXRT116x series: Some devices passed by ARM KEIL MDK were not detected correctly. Fixed.
20. GigaDevice GD32F450xx series devices: Due to wrong RAM size in MCU database, flash programming could fail. Fixed.
21. NXP iMXRT11xx devices: The available QSPI memory range for FLEXSPI1 was falsly set to 64 MB instead of 256 MB. Fixed.
22. 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.
23. Added debug support for SiLabs BGM220P device series.
24. Added flash programming support for SiLabs BGM220P device series.

Firmware

1. J-Link EDU Mini V1: RISC-V: RTT stop mode did not work. Fixed.
2. J-Link EDU/BASE/PLUS V10: RISC-V: RTT stop mode did not work. Fixed.
3. J-Link EDU/BASE/PLUS V11: RISC-V: RTT stop mode did not work. Fixed.
4. J-Link ULTRA+ V4: RISC-V: RTT stop mode did not work. Fixed.
5. J-Link ULTRA+ V5: RISC-V: RTT stop mode did not work. Fixed.
6. J-Link PRO V4: RISC-V: RTT stop mode did not work. Fixed.
7. J-Link PRO V5: RISC-V: RTT stop mode did not work. Fixed.
8. J-Link WiFi V1: RISC-V: RTT stop mode did not work. Fixed.
9. J-Link-OB-K22-RISCV: RISC-V: RTT stop mode did not work. Fixed.
10. J-Link-OB-K22-SiFive: RISC-V: RTT stop mode did not work. Fixed.
11. J-Trace PRO Cortex-M V1: nCS was released by accident when executing init/exit steps in J-Flash SPI. Fixed.

J-Flash

1. 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.
2. 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.

Manual

1. UM08002: Added chapter "Handling multiple connections at once".

OFL

1. 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.

RTT Viewer

1. If there are < 2 recent devices, the device selection combobox will not show a selection button anymore.

Registration

1. 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.
2. Updated GUI.
3. Updated J-Link picture.
4. Added "nickname" column to J-Link table.
5. Added button to refresh list.
6. The window was not resizable. Fixed.
7. Depending on the desktop resolution, some text was cut off. Fixed.
8. Registering products did not work, log always reported "Multiple selections detected". Fixed.
9. Updated J-Link picture so it also contains J-Trace and Flasher.
10. Updated references to "J-Link" or similar to say "probes and programmers" instead.

Version V7.50a (2021-07-08)

DLL

1. ST STM32H7Axx series devices internal flash programming algo, flash delay calculation. Fixed.
2. STM32L5: TrustZone flash programming did not work correctly, when only a part of the flash was secure. Fixed.
3. STM32U5: Flash programming failed when TrustZone was enabled. Fixed.
4. Linux: NXP MCU-Link CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
5. Linux: NXP LPC-Link 2 CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
6. Windows: NXP MCU-Link CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
7. Windows: NXP LPC-Link 2 CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
8. 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.
9. License dialog: The dialog was not resizable. Fixed.
10. License dialog: On high-resolution displays, only a few lines of license text were visible without scrolling. Fixed.
11. macOS: Connecting to CMSIS-DAP could fail because device path exceeded internal buffer sizes. Fixed.
12. macOS: NXP MCU-Link CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
13. macOS: NXP LPC-Link 2 CMSIS-DAP was shown 2-3 times. Selecting the "wrong" instance could make the IDE hang. Fixed.
14. When using unknown command string with JLINKARM_ExecCommand() / JLINK_ExecCommand(), these calls were not shown in the J-Link log file. Fixed.
15. 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.
16. 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.
17. O2Micro OZ935xx series devices internal flash programming chip erase functionality. Fixed.

DLL Updater

1. Some applications (e.g. Ozone) were listed twice per installation (introduced in V7.50). Fixed.

GDB Server

1. The J-Link GDB Server rejected to work with Cortex-A53 based MCUs. Fixed.

J-Flash

1. Downloading files to modules of Flasher ATE or Flasher Hub did not work correctly. Fixed.
2. Improved speed when downloading multiple files to programmer.
3. Extended Flasher module selection so up to 24 modules can be specified.

J-Flash SPI

1. Files can now be downloaded to modules of Flasher ATE or Flasher Hub.
2. Improved speed when downloading multiple files.

Version V7.50 (2021-07-01)

Commander

1. Added a message when the connect failed because the measured target voltage was too low.

DLL

1. Added support for Macronix MX66UM1G45G to all (Q)SPI based flash algorithms.
2. Added debug support for CloudBEAR BM-310 (RV32) device/core.
3. Added debug support for CloudBEAR BM-610 (RV64) device/core.
4. Added flash programming support for internal flash and internal QSPI flash of NXP K32W041AM device (Details: https://wiki.segger.com/NXP_K32W0_Series).
5. Added debug and flash programming support for Infineon CYPM1111 and CYPM1211 series devices.
6. Holtek HT32: Added debug support for multiple devices of the HT32-Series.
7. Holtek HT32: Added flash programming support for missing HT32F52-family devices.
8. Added debug support for Infineon IMD700A series devices (IMD700A_128, IMD701A_128).
9. Added flash programming support for Infineon IMD700A series devices (IMD700A_128, IMD701A_128).
10. Added debug and flash programming support for Maxim MAX32672 series devices.
11. Added trace related ROM table base addresses natively for STM32H7 series devices.
12. Added debug support for Codasip L10 (RV32) device/core.
13. Added debug support for Codasip L30 (RV32) device/core.
14. Added debug support for Codasip L30F (RV32) device/core.
15. Added debug support for Codasip L50 (RV32) device/core.
16. Added debug support for Codasip L50F (RV32) device/core.
17. Added debug support for Codasip H50X (RV64) device/core.
18. Added debug support for Codasip H50XF (RV64) device/core.
19. ARM MPS3 related devices: Changed naming scheme so that it is unambiguous, as it now contains the FPGA image name.
20. ST STM32: Added debug and flash programming support for multiple missing devices.
21. Multiple ST STM32 device descriptions passed to DLL by KEIL uVision were recognized as "unknown" device. Fixed.
22. ST STM32F750x8 series devices, internal flash size, fixed.
23. Added debug support for Renesas RA6T1 family.
24. Added flash programming support for Renesas RA6T1 family.
25. Added alias for ONSemi RSL15-512 series device.
26. Added debug support for Microchip SAM9X60D5M, SAM9X60D1G, SAM9X60D6K.
27. ST STM32L071, STM32L072, STM32L073, STM32L083 devices with 64 KiB internal flash had their EEPROM misplaced. Fixed
28. NXP i.MXRT117x series: Connect sequence to the Cortex-M4 failed under certain circumstances. Fixed.
29. ST STM32 devices: For some devices the watchdog timers were not frozen correctly. Fixed.
30. NXP S32K148 code flash size (1.5MB), fixed.
31. Added Cortex-M0 debug support for STM32WL55xx and STM32WL54xx series devices.
32. NXP iMXRT102x devices: Reset did not work correctly. Fixed.
33. NXP iMXRT102x devices: Under some circumstances, flash programming did not works after reset. Fixed.
34. NXP iMXRT10xx devices: When a breakpoint was active, the reset would sometimes fail. Fixed.
35. Raspberry Pi RP2040: Power-cycle or reset pin toggle was needed after 1st debug session to allow a new debug session. Fixed.
36. Microchip ATSAML11 series device, added Reset after Enable RAM execution.
37. NXP iMXRT106x devices: Under rare circumstances, the reset could cause to a HardFault. Fixed.
38. Raspberry Pi RP2040: QSPI flash-programming did not work in case the device was still in bootrom under certain circumstances. Fixed.
39. Cortex-M: Command string "CORESIGHT_SetCoreBaseAddr" did not disable ROMBASE check and ROM table scan. Fixed.
40. ST STM32G4 family: During unsecure: If the DEV_ID was unknown the connect was aborted instead of skipping the unsecure. Fixed.
41. OnSemi RSL15, added default reset.
42. NXP i.MXRT117x series: Some devices passed by ARM KEIL MDK were not detected correctly. Fixed.

DLL Updater

1. The 64-bit versions of the more recent IAR Embedded Workbench for ARM were not found shown for update. Fixed.
2. The version number of the IAR Embedded Workbench for ARM > V6.50.1 was not displayed correctly. Fixed.

Firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. J-Link EDU Mini V1: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
11. J-Link EDU/BASE/PLUS V10: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
12. J-Link EDU/BASE/PLUS V11: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
13. J-Link ULTRA+ V4: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
14. J-Link ULTRA+ V5: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
15. J-Link PRO V4: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
16. J-Link PRO V5: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
17. J-Link WiFi V1: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
18. J-Link OB-K22-RISCV: RISC-V: Reading / writing double-precision FPU registers did not work properly. Fixed.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. J-Link EDU/BASE/PLUS V10: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
29. J-Link EDU/BASE/PLUS V11: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
30. J-Link ULTRA+ V4: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
31. J-Link ULTRA+ V5: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
32. J-Link PRO V4: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
33. J-Link PRO V5: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
34. J-Link WiFi V1: RISC-V: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
35. J-Trace PRO V2 Cortex: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
36. J-Trace PRO V2 CortexM: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
37. Flasher ARM V4: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
38. Flasher PRO V4: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
39. Flasher RX V4: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
40. Flasher PPC V4: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
41. Flasher ARM V5: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
42. Flasher PRO V5: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
43. Flasher Portable PLUS V1: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.
44. Flasher Compact V5: Added ExecCommand API to enable/disable power supply pin 19 within Stand-alone-mode.

GDB Server

1. Some commands were not printed to the log immediately (e.g. "monitor reset"). Fixed.
2. Incorrect reply has been replied on target quit / exit signal. Fixed.

J-Flash

1. Improved performance of the "Eliminate blank areas..." option.
2. 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".
3. When passing the "-exit" parameter, the "no license found" dialog will not be shown anymore.
4. 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.
5. 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.
6. Renesas RA6M4 series: Programming of code & data flash did not work properly. Fixed.

J-Flash SPI

1. 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".
2. When passing the "-exit" parameter, the "no license found" dialog will not be shown anymore.
3. 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-Mem

1. 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".
2. 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

1. Added new command-line option for setting the J-Link script file to use: --jlinkscriptfile <str>

RTT

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. RISC-V: Added support for RTT via AHB-AP, for systems where RISC-V is behind a ARM CoreSight DAP.
11. DMB was not defined for 32-bit Cortex-A/R (ARMv7-A, ARMv7-R). Fixed.
12. _DoInit() could cause an unaligned access which caused a DataAbort when accessing strongly-ordered memory. Fixed.
13. 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.
14. Added identification of Cortex-R for automatic locking.

Remote Server

1. Added command line option "-log".

SWO Viewer

1. Command line option "-itmport" did not set <ITMMask> properly. Fixed.

Trace

1. LTRACE: ETMv4 (Cortex-M7, Cortex-M33) packet analyzer could crash under special circumstances. Introduced in Feb 2021 in V6.96. Fixed.