diff --git a/DDConditioner.exe b/DDConditioner.exe index 6698e42..2f82418 100644 Binary files a/DDConditioner.exe and b/DDConditioner.exe differ diff --git a/Devices/hpmicro/HPM5361/HPM5361xxxx_QSPI.elf b/Devices/hpmicro/HPM5361/HPM5361xxxx_QSPI.elf new file mode 100644 index 0000000..26792fa Binary files /dev/null and b/Devices/hpmicro/HPM5361/HPM5361xxxx_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6200/HPM6280xxxx_QSPI.elf b/Devices/hpmicro/HPM6200/HPM6280xxxx_QSPI.elf new file mode 100644 index 0000000..c8937c1 Binary files /dev/null and b/Devices/hpmicro/HPM6200/HPM6280xxxx_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6200/HPM6284xxxx_QSPI.elf b/Devices/hpmicro/HPM6200/HPM6284xxxx_QSPI.elf new file mode 100644 index 0000000..91a86e9 Binary files /dev/null and b/Devices/hpmicro/HPM6200/HPM6284xxxx_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6300/HPM6360xxxx_QSPI.elf b/Devices/hpmicro/HPM6300/HPM6360xxxx_QSPI.elf new file mode 100644 index 0000000..3acd37d Binary files /dev/null and b/Devices/hpmicro/HPM6300/HPM6360xxxx_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6300/HPM6360xxxx_XPI1_QSPI.elf b/Devices/hpmicro/HPM6300/HPM6360xxxx_XPI1_QSPI.elf new file mode 100644 index 0000000..2843a30 Binary files /dev/null and b/Devices/hpmicro/HPM6300/HPM6360xxxx_XPI1_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6300/HPM6364xxxx_QSPI.elf b/Devices/hpmicro/HPM6300/HPM6364xxxx_QSPI.elf new file mode 100644 index 0000000..dd4c067 Binary files /dev/null and b/Devices/hpmicro/HPM6300/HPM6364xxxx_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6700/HPM6750xANx_QSPI.elf b/Devices/hpmicro/HPM6700/HPM6750xANx_QSPI.elf new file mode 100644 index 0000000..162b8da Binary files /dev/null and b/Devices/hpmicro/HPM6700/HPM6750xANx_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6700/HPM6750xxxx_QSPI.elf b/Devices/hpmicro/HPM6700/HPM6750xxxx_QSPI.elf new file mode 100644 index 0000000..0f2c124 Binary files /dev/null and b/Devices/hpmicro/HPM6700/HPM6750xxxx_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6700/HPM6750xxxx_XPI1_QSPI.elf b/Devices/hpmicro/HPM6700/HPM6750xxxx_XPI1_QSPI.elf new file mode 100644 index 0000000..ae138ac Binary files /dev/null and b/Devices/hpmicro/HPM6700/HPM6750xxxx_XPI1_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6700/HPM6754xxxx_QSPI.elf b/Devices/hpmicro/HPM6700/HPM6754xxxx_QSPI.elf new file mode 100644 index 0000000..97bafb2 Binary files /dev/null and b/Devices/hpmicro/HPM6700/HPM6754xxxx_QSPI.elf differ diff --git a/Devices/hpmicro/HPM6800/HPM6880xxxx_QSPI.elf b/Devices/hpmicro/HPM6800/HPM6880xxxx_QSPI.elf new file mode 100644 index 0000000..f50977f Binary files /dev/null and b/Devices/hpmicro/HPM6800/HPM6880xxxx_QSPI.elf differ diff --git a/Doc/Manuals/UM08001_JLink.pdf b/Doc/Manuals/UM08001_JLink.pdf index 0857fd6..e70a071 100644 Binary files a/Doc/Manuals/UM08001_JLink.pdf and b/Doc/Manuals/UM08001_JLink.pdf differ diff --git a/Doc/Manuals/UM08003_JFlash.pdf b/Doc/Manuals/UM08003_JFlash.pdf index f696c5c..bc09005 100644 Binary files a/Doc/Manuals/UM08003_JFlash.pdf and b/Doc/Manuals/UM08003_JFlash.pdf differ diff --git a/Doc/Manuals/UM08022_Flasher.pdf b/Doc/Manuals/UM08022_Flasher.pdf index 64c6154..ae1ebf9 100644 Binary files a/Doc/Manuals/UM08022_Flasher.pdf and b/Doc/Manuals/UM08022_Flasher.pdf differ diff --git a/Doc/Manuals/UM08039_FlasherHub.pdf b/Doc/Manuals/UM08039_FlasherHub.pdf index 0775cb8..5eef432 100644 Binary files a/Doc/Manuals/UM08039_FlasherHub.pdf and b/Doc/Manuals/UM08039_FlasherHub.pdf differ diff --git a/Doc/Manuals/UM08043_FlasherHub12.pdf b/Doc/Manuals/UM08043_FlasherHub12.pdf new file mode 100644 index 0000000..59178e6 Binary files /dev/null and b/Doc/Manuals/UM08043_FlasherHub12.pdf differ diff --git a/Doc/ReleaseNotes/ReleaseNotes_JLink.html b/Doc/ReleaseNotes/ReleaseNotes_JLink.html index 18aaf94..0f78862 100644 --- a/Doc/ReleaseNotes/ReleaseNotes_JLink.html +++ b/Doc/ReleaseNotes/ReleaseNotes_JLink.html @@ -185,6 +185,1350 @@

Release notes for the J-Link / Flasher Software and Documentation Package +
+
+

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).
    2. +
+

Other changes:

+

DLL

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

Device Support

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

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. +
  2. J-Link EDU Mini V1: Added support for Cortex-M52 core.
    3. +
  3. J-Link EDU/BASE/PLUS V12: Added support for Cortex-M52 core.
    4. +
  4. J-Link ULTRA+ V5: Added support for Cortex-M52 core.
    5. +
  5. J-Link ULTRA+ V5-1: Added support for Cortex-M52 core.
    6. +
  6. J-Link ULTRA+ V6: Added support for Cortex-M52 core.
    7. +
  7. J-Link PRO V5: Added support for Cortex-M52 core.
    8. +
  8. J-Link PRO V5-1: Added support for Cortex-M52 core.
    9. +
  9. J-Link PRO V6: Added support for Cortex-M52 core.
    10. +
  10. J-Link PRO PoE V6: Added support for Cortex-M52 core.
    11. +
  11. J-Link WiFi V1: Added support for Cortex-M52 core.
    12. +
  12. J-Link WiFi V2: Added support for Cortex-M52 core.
    13. +
  13. J-Trace PRO V3 CortexM: Added support for Cortex-M52 core.
    14. +
  14. J-Trace PRO V3 Cortex: Added support for Cortex-M52 core.
    15. +
  15. J-Trace PRO V3: Added support for Cortex-M52 core.
    16. +
  16. Flasher ARM V5: Added support for Cortex-M52 core.
    17. +
  17. Flasher ARM V5-1: Added support for Cortex-M52 core.
    18. +
  18. Flasher ARM V6: Added support for Cortex-M52 core.
    19. +
  19. Flasher PRO V5: Added support for Cortex-M52 core.
    20. +
  20. Flasher PRO V5-1: Added support for Cortex-M52 core.
    21. +
  21. Flasher PRO V6: Added support for Cortex-M52 core.
    22. +
  22. Flasher PRO XL V5: Added support for Cortex-M52 core.
    23. +
  23. Flasher PRO XL V5-1: Added support for Cortex-M52 core.
    24. +
  24. Flasher PRO XL V6: Added support for Cortex-M52 core.
    25. +
  25. Flasher Compact V5: Added support for Cortex-M52 core.
    26. +
  26. Flasher Portable PLUS V5: Added support for Cortex-M52 core.
    27. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  38. Flasher ARM V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    39. +
  39. Flasher ARM V5-1: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    40. +
  40. Flasher ARM V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    41. +
  41. Flasher PRO V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    42. +
  42. Flasher PRO V5-1: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    43. +
  43. Flasher PRO V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    44. +
  44. Flasher PRO XL V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    45. +
  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. +
  46. Flasher PRO XL V6: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    47. +
  47. Flasher Compact V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    48. +
  48. Flasher Portable PLUS V5: After creating or removing a secure area, file operations (e.g. FREAD, FWRITE, FLIST, ...) failed until reboot. Fixed.
    49. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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.
    60. +
+

GDB Server

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

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

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

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. +
  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).
    3. +
+

Other changes:

+

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.
    2. +
  2. Web control panel: RTT Tab: Added search range information.
    3. +
  3. Web control panel: RTT Tab: Added event log.
    4. +
+

Device Support

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

Firmware

+
    +
  1. Flasher ARM V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    2. +
  2. Flasher ARM V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    3. +
  3. Flasher ARM V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    4. +
  4. Flasher PRO V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    5. +
  5. Flasher PRO V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    6. +
  6. Flasher PRO V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    7. +
  7. Flasher PRO XL V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    8. +
  8. Flasher PRO XL V5-1: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    9. +
  9. Flasher PRO XL V6: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    10. +
  10. Flasher Compact V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    11. +
  11. Flasher Portable PLUS V5: SFL: Function SEGGER_FL_GetFlashInfo(): Garbage was passed to parameter <InfoAreaSize>. Fixed.
    12. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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.
    50. +
+

U-Flash

+
    +
  1. U-Flash could not add projects to large FLASHER.ini files. Fixed.
    2. +
+
+
+
+
+

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

+

CCS Plugin

+
    +
  1. Added Cortex-M33 support.
    2. +
+

DLL

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

Device Support

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

Manual

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

U-Flash

+
    +
  1. Selecting a Flasher Hub took a long time. Fixed.
    2. +
+
+
+
+
+

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

+

Highlights:

+

Device Support

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

Other changes:

+

Commander

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

DLL

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

Device Support

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

Firmware

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

U-Flash

+
    +
  1. "Configure project" button was not disabled after creating a new project. Fixed.
    2. +
  2. An error message was displayed, when the user canceled opening a project file. Fixed.
    3. +
  3. Connecting to Flasher Hub did not work correctly. Fixed.
    4. +
  4. Download to Flasher Hub did not work correctly. Fixed.
    5. +
  5. Flasher with old firmware versions will now be marked in the Flasher selection dialog.
    6. +
  6. In certain cases the application did not close after programming. Fixed.
    7. +
+
+
+
+
+

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

Device Support

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

J-Flash

+
    +
  1. EFM32GG11: Production Programming could lead to all flash banks erased but the BTL flash bank. Fixed.
    2. +
  2. Project Settings: Flash: For external flash devices selected manually, the displayed size, number of sectors, sectorization information and sector selection were incorrect. Fixed.
    3. +
+

J-Scope

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

RTT Logger

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

U-Flash

+
    +
  1. PIC18(L)FxxK80: Alternative #MCLR function on Pin#3 with Push-Pull-Function.
    2. +
  2. An error message about missing arguments was always displayed, when using certain CLI commands. Fixed.
    3. +
  3. Selecting a template with the OK button did not work. Fixed.
    4. +
  4. Microchip ATTiny: Wirings and Erase Mode for UPDI devices fixed.
    5. +
  5. Renesas M16C/6NA: Added support for M306NAFGGP.
    6. +
+
+
+
+
+

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. +
  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. +
  3. Under certain circumstances (JLINKARM_Open() call with immediate JLINKARM_Close() call afterwards), J-Link DLL could crash. Fixed.
    4. +
+

Device Support

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

Firmware

+
    +
  1. Flasher ARM V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
    2. +
  2. Flasher ARM V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
    3. +
  3. Flasher PRO V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
    4. +
  4. Flasher PRO V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
    5. +
  5. Flasher PRO XL V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
    6. +
  6. Flasher PRO XL V5-1: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
    7. +
  7. Flasher Compact V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
    8. +
  8. Flasher Portable PLUS V5: Terminal: Command "#AUTO PATCH" did not work properly, if more than 1 patch was supplied. Fixed.
    9. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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.
    33. +
+

J-Flash SPI

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

J-Run

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

J-Scope

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

U-Flash

+
    +
  1. Automatic module detection for Flasher Hub did not work correctly. Fixed.
    2. +
+
+
+
+
+

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. +
  2. Renesas RA8T1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8T1).
    3. +
  3. Macronix MX25UW25345G: Added flash programming support.
    4. +
  4. Microchip PIC32CZxxxxCA80, PIC32CZxxxxCA90: Added debug and flash programming support (https://wiki.segger.com/Microchip_PIC32CZ_CA).
    5. +
+

J-Flash SPI

+
    +
  1. Macronix MX25UW25345G: Added flash programming support.
    2. +
+

Other changes:

+

Commander

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

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

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. +
  2. Infineon Traveo: Erase of the workflash could fail. Fixed.
    3. +
  3. LPC11E35/501: Added debug & flash programming support.
    4. +
  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.
    5. +
+

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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  33. J-Link-OB-K22-CortexA: Added support for ARMv8-A/R based cores (e.g. Cortex-R52).
    34. +
  34. J-Link-OB-RA4M2-Full: Added support for ARMv8-A/R based cores (e.g. Cortex-R52).
    35. +
+

GDB Server

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

J-Flash

+
    +
  1. Project Settings: Init/ Exit steps: The table did not expand in height. Fixed.
    2. +
  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. +
  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. +
  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. +
  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.
    6. +
+

J-Scope

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

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. +
  2. NXP S32M24x: Added debug and flash programming support (https://wiki.segger.com/NXP_S32M24x).
    3. +
  3. Texas Instruments MSPM0C: Added debug and flash programming support (https://wiki.segger.com/TI_MSPM0C).
    4. +
+

Flasher Package

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

J-Link Package

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

Other changes:

+

Device Support

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

U-Flash

+
    +
  1. Downloading a batch project did not work correctly. Fixed.
    2. +
+
+
+
+
+

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

J-Flash

+
    +
  1. J-Fash now attempts to detect file when opening files without extensions.
    2. +
+

J-Run

+
    +
  1. Reworked J-Runs ELF file parsing.
    2. +
+

MISC

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

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. +
  2. ST STM32H7B0xx: Added QSPI flash programming support.
    3. +
  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. +
  4. ARM dormant mode support: SWD: Added support for connecting via SWD if device was in JTAG State (JTAG -> Dormant -> SWD).
    5. +
  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.
    6. +
+

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

Firmware

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

J-Flash

+
    +
  1. Linux arm: J-Flash could crash immediately after launching due to a "Bus error". Fixed.
    2. +
  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.
    3. +
+

U-Flash

+
    +
  1. PIC24FJxxGAxxx: Added read support. Config word writing failed. Fixed.
    2. +
  2. Renesas RL78. Target connect fails during external reset is applied. Fixed.
    3. +
  3. Added open and save project buttons to the main window.
    4. +
+
+
+
+
+

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

+

Highlights:

+

Device Support

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

Other changes:

+

Device Support

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

Firmware

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

J-Scope

+
    +
  1. Reworked J-Scopes ELF file parsing.
    2. +
+

RTT Viewer

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

U-Flash

+
    +
  1. The FLASHER.INI file was not created correctly in certain cases.
    2. +
  2. It is now possible to reconnect to a selected Flasher without opening the Flasher selection dialog again.
    3. +
  3. The formatting in the console did not work correctly. Fixed.
    4. +
  4. Opening a project was reported as successful although the data file was not found. Fixed.
    5. +
  5. The icons in the footer were turned grey while downloading the configuration to the Flasher. Fixed.
    6. +
  6. The project file path was written in the window title multiple times, when opening multiple projects. Fixed.
    7. +
  7. In certain cases some information was missing in the device selection dialog. Fixed.
    8. +
  8. The console tab will now be disabled until a Flasher is connected.
    9. +
  9. The send to Flasher button was not enabled when generating test data or opening a project. Fixed.
    10. +
  10. The download progress bar will now be reset, when a change is made to the project configuration.
    11. +
  11. The Flasher Portable PLUS will now automatically select the new project after downloading it and restarting the Flasher.
    12. +
  12. The progress bar for firmware updates was missing. Fixed.
    13. +
  13. Renesas M16C. Unsuccessful login in Syncmode did not terminate. Fixed.
    14. +
+
+
+
+
+

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. +
  2. Added native trace buffer support for Xilinx Zynq device series.
    3. +
+

Other changes:

+

DLL

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

Device Support

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

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

GDB Server

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

RTT Viewer

+
    +
  1. Added "Clear all terminals" menu action.
    2. +
+

U-Flash

+
    +
  1. The "Send to Flasher" button will now be disabled after disconnecting from a Flasher.
    2. +
  2. Added the #fformat command to the console.
    3. +
  3. The configured SN settings were not correctly saved in the uni file. Fixed.
    4. +
+
+
+
+
+

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

+

Highlights:

+

Device Support

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

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. +
  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).
    3. +
+

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. +
  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. +
  3. Flasher Hub-12 V1: Module operations failed for modules running firmware compiled 27th Sep 2023 or later. Fixed.
    4. +
  4. Flasher Hub-12 V1: Response strings were sometimes incomplete. Fixed.
    5. +
  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.
    6. +
+

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

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

U-Flash

+
    +
  1. Trailing spaces will now be ignored in the device selection dialog.
    2. +
  2. Added a check mark to manually added Flashers in the Flasher selection dialog.
    3. +
  3. Added the selected target interface to the project settings dialog.
    4. +
+
+
+
+
+

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. +
  2. Renesas RA8M1 (Cortex-M85): Added debug and flash programming support (https://wiki.segger.com/Renesas_RA8M1).
    3. +
  3. GigaDevice GD32H7: Added debug and flash programming support (https://wiki.segger.com/GigaDevice_GD32H7).
    4. +
+

Other changes:

+

DLL

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

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. +
  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. +
  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. +
  4. NXP iMXRT1180: Under certain circumstances, debugging could behave unexpected due to some pending interrupts after boot ROM execution. Fixed.
    5. +
  5. NXP K32W14: Programming secure flash bank did not work. Fixed.
    6. +
  6. Programming errors were not detected correctly on STM32WB55xx-series devices. Fixed.
    7. +
  7. NXP RW61x: Added flash programming support for QSPI secure address.
    8. +
  8. NXP RW61x: Connect with JTAG was not working. Fixed.
    9. +
+

Firmware

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

Flasher Package

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

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. +
  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.
    3. +
+

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

J-Flash SPI

+
    +
  1. Added support for M95M01 SPI EEPROM.
    2. +
+

Manual

+
    +
  1. UM08039 Flasher Hub: Moved to SEGGER wiki: https://wiki.segger.com/UM08039_Flasher_Hub
    2. +
  2. UM08043 Flasher Hub-12: Created new Flasher Hub-12 manual in the SEGGER wiki: https://wiki.segger.com/UM08043_Flasher_Hub-12
    3. +
+

U-Flash

+
    +
  1. The device info table displayed wrong values under special circumstances. Fixed.
    2. +
  2. Parsing of device definition files was aborted under Linux due to wrong case of file names. Fixed.
    3. +
+
+
+
+
+

Version V7.92k (2023-10-18)

+

DLL

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

Device Support

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

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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  9. J-Link-OB-nRF5340-NordicSemi: Under special circumstances, VCOM could hang on COM port open. Fixed.
    10. +
+

U-Flash

+
    +
  1. The "Template" and "3rd party packages" tabs in the device selection dialog will now be disabled, if they are empty.
    2. +
  2. The "Send to Flasher" button was not enabled for devices that do not need a dat file. Fixed.
    3. +
  3. Added TI MSP430FR6047 JTAG support.
    4. +
  4. Terminal always reported "Error occured", because it did not wait for the answer. Fixed.
    5. +
  5. Renesas R8C: Wiring was not correct. Fixed.
    6. +
+
+
+
+
+

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).
    2. +
+

Other changes:

+

Device Support

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

Flasher Package

+
    +
  1. Added FlasherControl for easy terminal access to Flasher Compact.
    2. +
+

U-Flash

+
    +
  1. Made the background of the headers in the Flasher selection dialog blue.
    2. +
  2. "Save dat file" will now open a folder selection dialog instead of a file selection dialog.
    3. +
+
+
+
+
+

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/
    2. +
+

Other changes:

+

DLL

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

Device Support

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

Firmware

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

J-Flash

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

J-Flash SPI

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

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

U-Flash

+
    +
  1. Improved the design of the "Device info" table.
    2. +
  2. Added the number of supported devices to the main window.
    3. +
  3. Added "New project" to the file menu.
    4. +
  4. Moved batch composer to a tab in the main window.
    5. +
  5. Decreased the size of the pictures in the bottom right corner.
    6. +
+
+
+
+
+

Version V7.92h (2023-10-04)

+

Highlights:

+

Device Support

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

Other changes:

+

Device Support

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

Firmware

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

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

RTT

+
    +
  1. GCC compiler: SEGGER_RTT.c and SEGGER_RTT.h did throw warnings if "-Wcast-align" warning was enabled. Fixed.
    2. +
+
+
+
+
+

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. +
  2. Renesas RA6M5: Added missing device support for R7FA6M5BG (1.5 MB flash).
    3. +
  3. NXP iMXRT1180: Added debug and QSPI flash programming support (https://wiki.segger.com/NXP_iMXRT1180).
    4. +
  4. CVA BlueWhale CVM014x: Added debug and flash programming support (https://wiki.segger.com/CVA_BlueWhale_CVM014x).
    5. +
  5. PUYA P25Q32SL: Added flash programming support.
    6. +
+

J-Flash SPI

+
    +
  1. PUYA P25Q32SL: Added flash programming support.
    2. +
+

Other changes:

+

Device Support

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

U-Flash

+
    +
  1. Hid the binary offset input until a bin file is selected.
    2. +
  2. Changed the minimum resolution to 1024x768.
    3. +
  3. The console output from the Flasher is now displayed in monospace font.
    4. +
  4. Infineon Aurix. DFlash pagesize incorrect in NON RAM flasher mode. Fixed.
    5. +
  5. The project settings are now set to basic view mode by default.
    6. +
  6. Added descriptions for the file dialog filters.
    7. +
  7. Downloading additional files selected in the project settings did not work correctly. Fixed.
    8. +
  8. An empty dialog was briefly shown when opening the project settings. Fixed.
    9. +
  9. Set font to arial.
    10. +
  10. Microchip ATMega: Added calibration readout and optional storage in EEPROM.
    11. +
  11. Tooltip formatting was broken. Fixed.
    12. +
  12. Added grey background for sunken elements in the project settings dialog.
    13. +
+
+
+
+
+

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. +
  2. NXP S32K388: Added debug and flash programming support (https://wiki.segger.com/NXP_S32K3xx).
    3. +
  3. NXP LPC86x: Added debug and flash programming support (https://wiki.segger.com/NXP_LPC86x).
    4. +
+

Other changes:

+

Commander

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

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

Device Support

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

Firmware

+
    +
  1. Flasher Portable PLUS V5: Changed behavior and timing of project selection. Long press of SEL will fast forward after 3s.
    2. +
+

U-Flash

+
    +
  1. Added manual flasher selection.
    2. +
  2. PIC16: Device ID comparison might fail with P16F183X.PEX. Fixed.
    3. +
  3. Renesas R8C Family: Added readback support.
    4. +
  4. Renesas R8C Family: Added 'ALeRASE' support.
    5. +
  5. Renesas M16C Family: Added BUSY-Pin support on TRST (PIN3) implemented.
    6. +
  6. Renesas M16C/R8C Family: Updated Wiring Diagrams.
    7. +
  7. Flasher will now automatically get connected after closing the selection dialog.
    8. +
  8. Renamed "Memory info" to "Device info".
    9. +
+
+
+
+
+

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. +
  2. MindMotion MM32F5333: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32F5).
    3. +
  3. MindMotion MM32G0001: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G0).
    4. +
  4. MindMotion MM32G5333: Added debug and flash programming support (https://wiki.segger.com/MindMotion_MM32G5).
    5. +
  5. HPMicro HPM53xx: Added debug and flash programming support (https://wiki.segger.com/HPMicro_HPM53).
    6. +
+

Other changes:

+

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

Device Support

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

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

U-Flash

+
    +
  1. Moved connect button to the main window.
    2. +
+

Web Control Panel

+
    +
  1. Added "MemMap" tab.
    2. +
+

XVCD Server

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

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).
    2. +
+

Other changes:

+

Commander

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

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. +
  2. Extended command string "map add" by optional parameters <RegionName> and <MapType>.
    3. +
  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.
    4. +
+

Device Support

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

Firmware

+
    +
  1. Flasher Hub-12 V1: Implemented firmware update via web interface.
    2. +
  2. Flasher Hub-12 V1: Implemented module firmware update via web interface.
    3. +
  3. Flasher Hub-12 V1: Web interface did not reliably detect server connection breakdown. Fixed.
    4. +
  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. +
  5. Flasher Hub-12 V1: Changed default for handshake mode from "disabled" to "enabled".
    6. +
  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. +
  7. Flasher Hub-12 V1: WebIF "UART" tab: Typo "firwmare" --> "firmware". Fixed.
    8. +
  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. +
  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. +
  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. +
  11. Flasher Hub-12 V1: Flasher Hub log file updates did not work reliably. Fixed.
    12. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  22. J-Link ULTRA+ V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    23. +
  23. J-Link ULTRA+ V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    24. +
  24. J-Link ULTRA+ V6: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    25. +
  25. J-Link PRO V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    26. +
  26. J-Link PRO V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    27. +
  27. J-Link PRO V6: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    28. +
  28. Flasher ARM V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    29. +
  29. Flasher ARM V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    30. +
  30. Flasher PRO V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    31. +
  31. Flasher PRO V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    32. +
  32. Flasher PRO XL V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    33. +
  33. Flasher PRO XL V5-1: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    34. +
  34. Flasher Compact V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    35. +
  35. Flasher Portable PLUS V5: J-Flash SPI: Programming of newly added SST SST25VF020B SPI flash took exorbitantly long. Fixed.
    36. +
+

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. +
  2. Added USB J-Link selection via nickname to the graphical user interface.
    3. +
+

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).
    2. +
+

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

J-Link Package

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

U-Flash

+
    +
  1. Downloading a .dat file did not work correctly. Fixed.
    2. +
  2. Microchip PIC12/16: Devices using P12F67X.PEX were only secured if they were also programmed. Fixed.
    3. +
  3. Microchip PIC12/16: Added readback support for devices using P12F67X.PEX.
    4. +
  4. Microchip PIC16: Devices using P16F7X.PEX were only secured if they were also programmed. Fixed.
    5. +
  5. Microchip PIC16: Added readback support for devices using P16F7X.PEX.
    6. +
  6. Microchip PIC12/16: Devices using P16F8X.PEX were only secured if they were also programmed. Fixed.
    7. +
  7. Microchip PIC12/16: Added readback support for devices using P16F8X.PEX.
    8. +
  8. Microchip PIC18: Devices using P18FXQ10.PEX were only secured if they were also programmed. Fixed.
    9. +
  9. Microchip PIC18: Added readback support for devices using P18FXQ10.PEX.
    10. +
  10. Microchip PIC16: Devices using P16F88X.PEX were only secured if they were also programmed. Fixed.
    11. +
  11. Microchip PIC16: Added readback support for devices using P16F88X.PEX.
    12. +
  12. Renesas RX devices were listed within U-Flash device selection only with the device family name and not with the actual device names. Fixed.
    13. +
  13. Generating test data with U-Flash for Renesas RX devices supported only a single User ROM size. Fixed.
    14. +
  14. Microchip PIC16: Devices using P16F183X.PEX were only secured if they were also programmed. Fixed.
    15. +
  15. Microchip PIC16: Added readback support for devices using P16F183X.PEX.
    16. +
  16. Added a console window and buttons to remote control the Flasher.
    17. +
+

XVCD Server

+
    +
  1. Added J-Link XVCD Server to software package. More info: https://wiki.segger.com/J-Link_XVCD_Server
    2. +
+
+
+
+
+

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. +
  2. Infineon CYT2CL: Added debug and flash programming support(https://wiki.segger.com/Infineon_CYT2CL).
    3. +
  3. ST STM32F446: Added flash programming support for external QSPI flash.
    4. +
+

Other changes:

+

DLL

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

DLL Updater

+
    +
  1. Added wiki link to DLL updater.
    2. +
+

Device Support

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

Firmware

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

U-Flash

+
    +
  1. The application crashed in some cases after a TCP/IP connection timed out. Fixed.
    2. +
  2. Values for some check boxes inside group boxes were not saved in the project file. Fixed.
    3. +
  3. The Flasher selection dialog appeared multiple times while downloading a batch configuration. Fixed.
    4. +
+
+
+
+
+

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

+

Highlights:

+

Device Support

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

Other changes:

+

DLL

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

Device Support

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

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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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. +
  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.
    9. +
+

Flasher Package

+
    +
  1. Installer: Added update notification selection (same as J-Link Installer).
    2. +
+

J-Link Package

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

RTT Viewer

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

U-Flash

+
    +
  1. The "Show wiring" button always stayed disabled, when a project file was opened. Fixed.
    2. +
+
+
+
+
+

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

+

Device Support

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

J-Flash SPI

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

Manual

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

U-Flash

+
    +
  1. In certain cases, erase was set to "1", although it should be "0" in the uni file. Fixed.
    2. +
  2. Displaying the wiring plans did not work correctly on macOS. Fixed.
    3. +
  3. Renamed the tabs inside the device selection dialog.
    4. +
+
+

Version V7.92 (2023-08-11)

@@ -21110,7 +22454,7 @@

RDI

- Copyright 2001-2023 SEGGER Microcontroller GmbH All rights reserved.
+ Copyright 2001-2024 SEGGER Microcontroller GmbH All rights reserved.
For more information, please visit our website www.segger.com or contact us at info@segger.com 

diff --git a/Firmwares/FlasherARM_V5.bin b/Firmwares/FlasherARM_V5.bin index e1f5c20..1d0a2f3 100644 Binary files a/Firmwares/FlasherARM_V5.bin and b/Firmwares/FlasherARM_V5.bin differ diff --git a/Firmwares/FlasherARM_V5_1.bin b/Firmwares/FlasherARM_V5_1.bin index 3f647b5..be262a1 100644 Binary files a/Firmwares/FlasherARM_V5_1.bin and b/Firmwares/FlasherARM_V5_1.bin differ diff --git a/Firmwares/FlasherARM_V6.bin b/Firmwares/FlasherARM_V6.bin new file mode 100644 index 0000000..66f5f3a Binary files /dev/null and b/Firmwares/FlasherARM_V6.bin differ diff --git a/Firmwares/FlasherCompact_V5.bin b/Firmwares/FlasherCompact_V5.bin index 9f22919..284998a 100644 Binary files a/Firmwares/FlasherCompact_V5.bin and b/Firmwares/FlasherCompact_V5.bin differ diff --git a/Firmwares/FlasherHub-12_V1.bin b/Firmwares/FlasherHub-12_V1.bin new file mode 100644 index 0000000..9aabaeb Binary files /dev/null and b/Firmwares/FlasherHub-12_V1.bin differ diff --git a/Firmwares/FlasherPRO_V5.bin b/Firmwares/FlasherPRO_V5.bin index 31fa74e..52b5a97 100644 Binary files a/Firmwares/FlasherPRO_V5.bin and b/Firmwares/FlasherPRO_V5.bin differ diff --git a/Firmwares/FlasherPRO_V5_1.bin b/Firmwares/FlasherPRO_V5_1.bin index ab199bd..abc4658 100644 Binary files a/Firmwares/FlasherPRO_V5_1.bin and b/Firmwares/FlasherPRO_V5_1.bin differ diff --git a/Firmwares/FlasherPRO_V6.bin b/Firmwares/FlasherPRO_V6.bin new file mode 100644 index 0000000..7b163fd Binary files /dev/null and b/Firmwares/FlasherPRO_V6.bin differ diff --git a/Firmwares/Flasher_Portable_PLUS_V5.bin b/Firmwares/Flasher_Portable_PLUS_V5.bin index 581d058..bf9ff8c 100644 Binary files a/Firmwares/Flasher_Portable_PLUS_V5.bin and b/Firmwares/Flasher_Portable_PLUS_V5.bin differ diff --git a/Firmwares/JLinkEDUMini_V1.bin b/Firmwares/JLinkEDUMini_V1.bin index 9a2f15f..351ea72 100644 Binary files a/Firmwares/JLinkEDUMini_V1.bin and b/Firmwares/JLinkEDUMini_V1.bin differ diff --git a/Firmwares/JLink_OB_Apollo4_CortexM.bin b/Firmwares/JLink_OB_Apollo4_CortexM.bin index 62959ba..c040a3d 100644 Binary files a/Firmwares/JLink_OB_Apollo4_CortexM.bin and b/Firmwares/JLink_OB_Apollo4_CortexM.bin differ diff --git a/Firmwares/JLink_OB_Calliope_MINI_V2_1.bin b/Firmwares/JLink_OB_Calliope_MINI_V2_1.bin index 74555e2..619a123 100644 Binary files a/Firmwares/JLink_OB_Calliope_MINI_V2_1.bin and b/Firmwares/JLink_OB_Calliope_MINI_V2_1.bin differ diff --git a/Firmwares/JLink_OB_E1_AlifSemi.bin b/Firmwares/JLink_OB_E1_AlifSemi.bin new file mode 100644 index 0000000..b742c6e Binary files /dev/null and b/Firmwares/JLink_OB_E1_AlifSemi.bin differ diff --git a/Firmwares/JLink_OB_K22_CortexA.bin b/Firmwares/JLink_OB_K22_CortexA.bin index 6873dab..18d58e5 100644 Binary files a/Firmwares/JLink_OB_K22_CortexA.bin and b/Firmwares/JLink_OB_K22_CortexA.bin differ diff --git a/Firmwares/JLink_OB_K22_CortexM.bin b/Firmwares/JLink_OB_K22_CortexM.bin index de18da3..3a06706 100644 Binary files a/Firmwares/JLink_OB_K22_CortexM.bin and b/Firmwares/JLink_OB_K22_CortexM.bin differ diff --git a/Firmwares/JLink_OB_K22_NordicSemi.bin b/Firmwares/JLink_OB_K22_NordicSemi.bin index 40fe2bd..bf2cb2f 100644 Binary files a/Firmwares/JLink_OB_K22_NordicSemi.bin and b/Firmwares/JLink_OB_K22_NordicSemi.bin differ diff --git a/Firmwares/JLink_OB_K22_Qorvo.bin b/Firmwares/JLink_OB_K22_Qorvo.bin index 8d8338d..345b6a5 100644 Binary files a/Firmwares/JLink_OB_K22_Qorvo.bin and b/Firmwares/JLink_OB_K22_Qorvo.bin differ diff --git a/Firmwares/JLink_OB_K22_RISCV.bin b/Firmwares/JLink_OB_K22_RISCV.bin index e3f02e6..10a57b6 100644 Binary files a/Firmwares/JLink_OB_K22_RISCV.bin and b/Firmwares/JLink_OB_K22_RISCV.bin differ diff --git a/Firmwares/JLink_OB_RA4M2_CortexM.bin b/Firmwares/JLink_OB_RA4M2_CortexM.bin index a4bf47f..b59e7bd 100644 Binary files a/Firmwares/JLink_OB_RA4M2_CortexM.bin and b/Firmwares/JLink_OB_RA4M2_CortexM.bin differ diff --git a/Firmwares/JLink_OB_RA4M2_Full.bin b/Firmwares/JLink_OB_RA4M2_Full.bin index 1b7eb57..ca4bc3c 100644 Binary files a/Firmwares/JLink_OB_RA4M2_Full.bin and b/Firmwares/JLink_OB_RA4M2_Full.bin differ diff --git a/Firmwares/JLink_OB_RA4M2_RISCV.bin b/Firmwares/JLink_OB_RA4M2_RISCV.bin index d7ac712..75f30f1 100644 Binary files a/Firmwares/JLink_OB_RA4M2_RISCV.bin and b/Firmwares/JLink_OB_RA4M2_RISCV.bin differ diff --git a/Firmwares/JLink_OB_RA4M2_Renesas.bin b/Firmwares/JLink_OB_RA4M2_Renesas.bin index a72cb0f..432779a 100644 Binary files a/Firmwares/JLink_OB_RA4M2_Renesas.bin and b/Firmwares/JLink_OB_RA4M2_Renesas.bin differ diff --git a/Firmwares/JLink_OB_S124.bin b/Firmwares/JLink_OB_S124.bin index 6d3098c..cc7c7ea 100644 Binary files a/Firmwares/JLink_OB_S124.bin and b/Firmwares/JLink_OB_S124.bin differ diff --git a/Firmwares/JLink_OB_SAM3U128_V1.bin b/Firmwares/JLink_OB_SAM3U128_V1.bin index ef2db5b..38b8cf5 100644 Binary files a/Firmwares/JLink_OB_SAM3U128_V1.bin and b/Firmwares/JLink_OB_SAM3U128_V1.bin differ diff --git a/Firmwares/JLink_OB_SAM3U128_V2_NordicSemi.bin b/Firmwares/JLink_OB_SAM3U128_V2_NordicSemi.bin index 22b5876..c42aef1 100644 Binary files a/Firmwares/JLink_OB_SAM3U128_V2_NordicSemi.bin and b/Firmwares/JLink_OB_SAM3U128_V2_NordicSemi.bin differ diff --git a/Firmwares/JLink_OB_SAM3U128_V3.bin b/Firmwares/JLink_OB_SAM3U128_V3.bin index 603a609..6dcb517 100644 Binary files a/Firmwares/JLink_OB_SAM3U128_V3.bin and b/Firmwares/JLink_OB_SAM3U128_V3.bin differ diff --git a/Firmwares/JLink_OB_STM32F072_Qorvo.bin b/Firmwares/JLink_OB_STM32F072_Qorvo.bin new file mode 100644 index 0000000..a881509 Binary files /dev/null and b/Firmwares/JLink_OB_STM32F072_Qorvo.bin differ diff --git a/Firmwares/JLink_OB_STM32F103.bin b/Firmwares/JLink_OB_STM32F103.bin index 7dfdff9..67571bf 100644 Binary files a/Firmwares/JLink_OB_STM32F103.bin and b/Firmwares/JLink_OB_STM32F103.bin differ diff --git a/Firmwares/JLink_OB_XMC4200.bin b/Firmwares/JLink_OB_XMC4200.bin index 40d1295..047563d 100644 Binary files a/Firmwares/JLink_OB_XMC4200.bin and b/Firmwares/JLink_OB_XMC4200.bin differ diff --git a/Firmwares/JLink_OB_nRF5340_NordicSemi.bin b/Firmwares/JLink_OB_nRF5340_NordicSemi.bin index 71285e7..c8b58bc 100644 Binary files a/Firmwares/JLink_OB_nRF5340_NordicSemi.bin and b/Firmwares/JLink_OB_nRF5340_NordicSemi.bin differ diff --git a/Firmwares/JLink_PRO_PoE_V6.bin b/Firmwares/JLink_PRO_PoE_V6.bin new file mode 100644 index 0000000..9682458 Binary files /dev/null and b/Firmwares/JLink_PRO_PoE_V6.bin differ diff --git a/Firmwares/JLink_PRO_V5.bin b/Firmwares/JLink_PRO_V5.bin index 2b22d11..26d815a 100644 Binary files a/Firmwares/JLink_PRO_V5.bin and b/Firmwares/JLink_PRO_V5.bin differ diff --git a/Firmwares/JLink_PRO_V5_1.bin b/Firmwares/JLink_PRO_V5_1.bin index a17b892..914afda 100644 Binary files a/Firmwares/JLink_PRO_V5_1.bin and b/Firmwares/JLink_PRO_V5_1.bin differ diff --git a/Firmwares/JLink_PRO_V6.bin b/Firmwares/JLink_PRO_V6.bin index 1648cbe..00f47ce 100644 Binary files a/Firmwares/JLink_PRO_V6.bin and b/Firmwares/JLink_PRO_V6.bin differ diff --git a/Firmwares/JLink_ULTRA_V5.bin b/Firmwares/JLink_ULTRA_V5.bin index dd2387a..d0562df 100644 Binary files a/Firmwares/JLink_ULTRA_V5.bin and b/Firmwares/JLink_ULTRA_V5.bin differ diff --git a/Firmwares/JLink_ULTRA_V5_1.bin b/Firmwares/JLink_ULTRA_V5_1.bin index 3d5bb63..56f593a 100644 Binary files a/Firmwares/JLink_ULTRA_V5_1.bin and b/Firmwares/JLink_ULTRA_V5_1.bin differ diff --git a/Firmwares/JLink_ULTRA_V6.bin b/Firmwares/JLink_ULTRA_V6.bin index b63ca26..9f30fb1 100644 Binary files a/Firmwares/JLink_ULTRA_V6.bin and b/Firmwares/JLink_ULTRA_V6.bin differ diff --git a/Firmwares/JLink_V11.bin b/Firmwares/JLink_V11.bin index f2ff9de..21a5f95 100644 Binary files a/Firmwares/JLink_V11.bin and b/Firmwares/JLink_V11.bin differ diff --git a/Firmwares/JLink_V12.bin b/Firmwares/JLink_V12.bin index 141bbec..4d3a727 100644 Binary files a/Firmwares/JLink_V12.bin and b/Firmwares/JLink_V12.bin differ diff --git a/Firmwares/JLink_WiFi_V1.bin b/Firmwares/JLink_WiFi_V1.bin index 8c8fcb6..e65c909 100644 Binary files a/Firmwares/JLink_WiFi_V1.bin and b/Firmwares/JLink_WiFi_V1.bin differ diff --git a/Firmwares/JLink_WiFi_V2.bin b/Firmwares/JLink_WiFi_V2.bin new file mode 100644 index 0000000..f72c46f Binary files /dev/null and b/Firmwares/JLink_WiFi_V2.bin differ diff --git a/Firmwares/JTrace_PRO_V2_Cortex.bin b/Firmwares/JTrace_PRO_V2_Cortex.bin index 17e6016..8834859 100644 Binary files a/Firmwares/JTrace_PRO_V2_Cortex.bin and b/Firmwares/JTrace_PRO_V2_Cortex.bin differ diff --git a/Firmwares/JTrace_PRO_V2_CortexM.bin b/Firmwares/JTrace_PRO_V2_CortexM.bin index d620095..696b1fd 100644 Binary files a/Firmwares/JTrace_PRO_V2_CortexM.bin and b/Firmwares/JTrace_PRO_V2_CortexM.bin differ diff --git a/Firmwares/JTrace_PRO_V3.bin b/Firmwares/JTrace_PRO_V3.bin new file mode 100644 index 0000000..6bb9611 Binary files /dev/null and b/Firmwares/JTrace_PRO_V3.bin differ diff --git a/Firmwares/JTrace_PRO_V3_Cortex.bin b/Firmwares/JTrace_PRO_V3_Cortex.bin index efd7411..a436867 100644 Binary files a/Firmwares/JTrace_PRO_V3_Cortex.bin and b/Firmwares/JTrace_PRO_V3_Cortex.bin differ diff --git a/Firmwares/JTrace_PRO_V3_CortexM.bin b/Firmwares/JTrace_PRO_V3_CortexM.bin index e848405..411e6d8 100644 Binary files a/Firmwares/JTrace_PRO_V3_CortexM.bin and b/Firmwares/JTrace_PRO_V3_CortexM.bin differ diff --git a/Firmwares/JTrace_PRO_V3_RISCV.bin b/Firmwares/JTrace_PRO_V3_RISCV.bin index 64126b0..7e941b8 100644 Binary files a/Firmwares/JTrace_PRO_V3_RISCV.bin and b/Firmwares/JTrace_PRO_V3_RISCV.bin differ diff --git a/GDBServer/RTOSPlugin_Azure.dll b/GDBServer/RTOSPlugin_Azure.dll index 6acbc3b..5675708 100644 Binary files a/GDBServer/RTOSPlugin_Azure.dll and b/GDBServer/RTOSPlugin_Azure.dll differ diff --git a/GDBServer/RTOSPlugin_ChibiOS.dll b/GDBServer/RTOSPlugin_ChibiOS.dll index 230ad0f..9041f1d 100644 Binary files a/GDBServer/RTOSPlugin_ChibiOS.dll and b/GDBServer/RTOSPlugin_ChibiOS.dll differ diff --git a/GDBServer/RTOSPlugin_FreeRTOS.dll b/GDBServer/RTOSPlugin_FreeRTOS.dll index 556dc06..22db3fa 100644 Binary files a/GDBServer/RTOSPlugin_FreeRTOS.dll and b/GDBServer/RTOSPlugin_FreeRTOS.dll differ diff --git a/GDBServer/RTOSPlugin_NuttX.dll b/GDBServer/RTOSPlugin_NuttX.dll index 8d8799f..bf0ab90 100644 Binary files a/GDBServer/RTOSPlugin_NuttX.dll and b/GDBServer/RTOSPlugin_NuttX.dll differ diff --git a/GDBServer/RTOSPlugin_Zephyr.dll b/GDBServer/RTOSPlugin_Zephyr.dll index 3f25a80..a4c7d2d 100644 Binary files a/GDBServer/RTOSPlugin_Zephyr.dll and b/GDBServer/RTOSPlugin_Zephyr.dll differ diff --git a/GDBServer/RTOSPlugin_embOS.dll b/GDBServer/RTOSPlugin_embOS.dll index ac867da..88f0bad 100644 Binary files a/GDBServer/RTOSPlugin_embOS.dll and b/GDBServer/RTOSPlugin_embOS.dll differ diff --git a/JFlash.exe b/JFlash.exe index 06e9e71..3e0a30e 100644 Binary files a/JFlash.exe and b/JFlash.exe differ diff --git a/JFlashLite.exe b/JFlashLite.exe index 684de56..df75c35 100644 Binary files a/JFlashLite.exe and b/JFlashLite.exe differ diff --git a/JFlashSPI.exe b/JFlashSPI.exe index e579c19..af33903 100644 Binary files a/JFlashSPI.exe and b/JFlashSPI.exe differ diff --git a/JFlashSPI_CL.exe b/JFlashSPI_CL.exe index 57d954f..aeb1ce0 100644 Binary files a/JFlashSPI_CL.exe and b/JFlashSPI_CL.exe differ diff --git a/JLink.exe b/JLink.exe index 27cc2ab..f17290c 100644 Binary files a/JLink.exe and b/JLink.exe differ diff --git a/JLinkARM.dll b/JLinkARM.dll index 6b17bab..b57ab92 100644 Binary files a/JLinkARM.dll and b/JLinkARM.dll differ diff --git a/JLinkConfig.exe b/JLinkConfig.exe index 2cc7d5c..bdde2a7 100644 Binary files a/JLinkConfig.exe and b/JLinkConfig.exe differ diff --git a/JLinkDLLUpdater.exe b/JLinkDLLUpdater.exe index d15b16a..0960bb3 100644 Binary files a/JLinkDLLUpdater.exe and b/JLinkDLLUpdater.exe differ diff --git a/JLinkDevices.xml b/JLinkDevices.xml index 43b75fe..f44a464 100644 --- a/JLinkDevices.xml +++ b/JLinkDevices.xml @@ -1,1375 +1,297 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/JLinkGDBServer.exe b/JLinkGDBServer.exe index 146ea84..1163d46 100644 Binary files a/JLinkGDBServer.exe and b/JLinkGDBServer.exe differ diff --git a/JLinkGDBServerCL.exe b/JLinkGDBServerCL.exe index 66aa8b7..dbb66b1 100644 Binary files a/JLinkGDBServerCL.exe and b/JLinkGDBServerCL.exe differ diff --git a/JLinkGUIServer.exe b/JLinkGUIServer.exe index b445e2c..0c1289f 100644 Binary files a/JLinkGUIServer.exe and b/JLinkGUIServer.exe differ diff --git a/JLinkLicenseManager.exe b/JLinkLicenseManager.exe index 82834ad..179327e 100644 Binary files a/JLinkLicenseManager.exe and b/JLinkLicenseManager.exe differ diff --git a/JLinkRTTClient.exe b/JLinkRTTClient.exe index ec9892b..ddd7ebd 100644 Binary files a/JLinkRTTClient.exe and b/JLinkRTTClient.exe differ diff --git a/JLinkRTTLogger.exe b/JLinkRTTLogger.exe index 2b0c0a0..4dc2d60 100644 Binary files a/JLinkRTTLogger.exe and b/JLinkRTTLogger.exe differ diff --git a/JLinkRTTViewer.exe b/JLinkRTTViewer.exe index 9581ae6..05181f3 100644 Binary files a/JLinkRTTViewer.exe and b/JLinkRTTViewer.exe differ diff --git a/JLinkRegistration.exe b/JLinkRegistration.exe index 96622ba..6163118 100644 Binary files a/JLinkRegistration.exe and b/JLinkRegistration.exe differ diff --git a/JLinkRemoteServer.exe b/JLinkRemoteServer.exe index 6144107..95a50ee 100644 Binary files a/JLinkRemoteServer.exe and b/JLinkRemoteServer.exe differ diff --git a/JLinkRemoteServerCL.exe b/JLinkRemoteServerCL.exe index efd62e7..5fd92d6 100644 Binary files a/JLinkRemoteServerCL.exe and b/JLinkRemoteServerCL.exe differ diff --git a/JLinkSTM32.exe b/JLinkSTM32.exe index 4ec6188..42836a0 100644 Binary files a/JLinkSTM32.exe and b/JLinkSTM32.exe differ diff --git a/JLinkSTR91x.exe b/JLinkSTR91x.exe index 2539164..1a918d7 100644 Binary files a/JLinkSTR91x.exe and b/JLinkSTR91x.exe differ diff --git a/JLinkSWOViewer.exe b/JLinkSWOViewer.exe index 64e25a5..0c61a40 100644 Binary files a/JLinkSWOViewer.exe and b/JLinkSWOViewer.exe differ diff --git a/JLinkSWOViewerCL.exe b/JLinkSWOViewerCL.exe index 327e646..9f46b1b 100644 Binary files a/JLinkSWOViewerCL.exe and b/JLinkSWOViewerCL.exe differ diff --git a/JLinkUSBWebServer.exe b/JLinkUSBWebServer.exe index 75561b7..4f64b3b 100644 Binary files a/JLinkUSBWebServer.exe and b/JLinkUSBWebServer.exe differ diff --git a/JLinkXVCDServer.exe b/JLinkXVCDServer.exe new file mode 100644 index 0000000..713456d Binary files /dev/null and b/JLinkXVCDServer.exe differ diff --git a/JLink_x64.dll b/JLink_x64.dll index 2fc7bb5..c31778d 100644 Binary files a/JLink_x64.dll and b/JLink_x64.dll differ diff --git a/JMem.exe b/JMem.exe index 50ef6e1..31be072 100644 Binary files a/JMem.exe and b/JMem.exe differ diff --git a/JRun.exe b/JRun.exe index b275dee..c940b10 100644 Binary files a/JRun.exe and b/JRun.exe differ diff --git a/JScope.exe b/JScope.exe index 097a96b..48e8905 100644 Binary files a/JScope.exe and b/JScope.exe differ diff --git a/JTAGLoad.exe b/JTAGLoad.exe index 1d2c1d5..1b1a538 100644 Binary files a/JTAGLoad.exe and b/JTAGLoad.exe differ diff --git a/RDDI/rddi-debug-router_2.dll b/RDDI/rddi-debug-router_2.dll index 7f623d3..8f84295 100644 Binary files a/RDDI/rddi-debug-router_2.dll and b/RDDI/rddi-debug-router_2.dll differ diff --git a/RDDI/rddi-debug-router_2_x64.dll b/RDDI/rddi-debug-router_2_x64.dll index 6c31db4..d0dc8f2 100644 Binary files a/RDDI/rddi-debug-router_2_x64.dll and b/RDDI/rddi-debug-router_2_x64.dll differ diff --git a/SWOAnalyzer.exe b/SWOAnalyzer.exe index f601c74..fc17d62 100644 Binary files a/SWOAnalyzer.exe and b/SWOAnalyzer.exe differ diff --git a/Samples/RTT/SEGGER_RTT_V794g.zip b/Samples/RTT/SEGGER_RTT_V794g.zip new file mode 100644 index 0000000..c8bb013 Binary files /dev/null and b/Samples/RTT/SEGGER_RTT_V794g.zip differ diff --git a/USBDriver/InstDrivers.exe b/USBDriver/InstDrivers.exe index b18e0ac..82b0a83 100644 Binary files a/USBDriver/InstDrivers.exe and b/USBDriver/InstDrivers.exe differ diff --git a/Uninstall.exe b/Uninstall.exe index 9fd307d..0123119 100644 Binary files a/Uninstall.exe and b/Uninstall.exe differ