[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"package:cask:segger-jlink:en":3,"releases:stats:cask:segger-jlink:en":579,"releases:cask:segger-jlink:1:false:false:en":580,"releases-count:cask:segger-jlink:true:en":696,"markdown:3:4366:98tgdn":703,"markdown:3:14454:pfgygn":704,"markdown:3:7338:2qi7rd":705},{"accentColor":4,"artifacts":5,"autoUpdates":47,"categories":48,"caveats":54,"conflictsWith":55,"dependsOn":58,"deprecated":47,"description":66,"descriptionEn":67,"developer":68,"disabled":47,"displayName":69,"downloadSha256":70,"downloadSize":71,"downloadUrl":72,"editorChoice":47,"formulaeUrl":73,"homepage":74,"iconUrl":75,"installCommand":76,"installs":77,"installs30d":78,"isFont":47,"isLibrary":47,"kegOnly":47,"kind":81,"latestRelease":82,"machineTranslated":47,"name":96,"names":97,"platforms":99,"primaryCategory":555,"rank30d":556,"releaseCount":557,"releaseStats":558,"screenshots":565,"sourceLocale":90,"sourceUrl":566,"summary":567,"summaryTranslation":568,"supports":569,"tags":571,"tap":577,"token":98,"version":95,"versionChangedAt":578},"#33304A",{"apps":6,"binaries":7,"entries":8,"pkgs":46},[],[],[9,23,30],{"declaration":10,"phase":21,"sources":22,"type":21},{"uninstall":11},[12],{"pkgutil":13,"quit":14},"com.segger.pkg.JLink",[15,16,17,18,19,20],"com.segger.JFlashLite.*","com.segger.JLinkGDBServer.*","com.segger.JLinkLicenseManager.*","com.segger.JLinkRegistration.*","com.segger.JLinkRemoteServer.*","com.segger.JLinkRTTViewer.*","uninstall",[],{"declaration":24,"phase":27,"sources":28,"type":29},{"pkg":25},[26],"JLink_MacOSX_V984_universal.pkg","install",[26],"pkg",{"declaration":31,"phase":43,"sources":44,"type":45},{"zap":32},[33],{"trash":34},[35,36,37,38,39,40,41,42],"~\u002F.SEGGER","~\u002FLibrary\u002FApplication Support\u002FSEGGER","~\u002FLibrary\u002FSaved Application State\u002Fcom.segger.JFlashLite.*savedState","~\u002FLibrary\u002FSaved Application State\u002Fcom.segger.JLinkGDBServer.*savedState","~\u002FLibrary\u002FSaved Application State\u002Fcom.segger.JLinkLicenseManager.*savedState","~\u002FLibrary\u002FSaved Application State\u002Fcom.segger.JLinkRegistration.*savedState","~\u002FLibrary\u002FSaved Application State\u002Fcom.segger.JLinkRemoteServer.*savedState","~\u002FLibrary\u002FSaved Application State\u002Fcom.segger.JLinkRTTViewer.*savedState","cleanup",[],"zap",[26],false,[49],{"icon":50,"machineTranslated":47,"name":51,"slug":52,"sourceLocale":53},"lucide:code-xml","Developer Tools","developer-tools","zh-CN","Installing segger-jlink means you have AGREED to the license at:\n  https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FJLink_MacOSX_V984_universal.pkg\n",{"casks":56,"formulae":57},[],[],{"arch":59,"casks":62,"formulae":63,"requirements":64},[60,61],"arm64","x86_64",[],[],{"macos":65},{},"The J-Link Software and Documentation Pack provides SEGGER tools, manuals, and firmware updates for J-Link and J-Trace debug probes. This Homebrew cask installs the official macOS package; it is not a replacement for the physical debug probe.\n\nJ-Link Commander is a command-line utility for checking the connection between a J-Link probe and the target system. Its commands can inspect memory, halt the processor, single-step execution, resume execution, and program flash. The installer also includes components identified by the Homebrew cask such as J-Flash Lite, J-Link GDB Server, Remote Server, License Manager, and RTT Viewer. Capabilities and licensing depend on the connected J-Link or J-Trace model.\n\nSEGGER provides software builds for Intel and Apple Silicon Macs; the recorded 9.84 Homebrew artifact is the universal macOS installer. Install with `brew install --cask segger-jlink`. Homebrew warns that installation constitutes agreement to the SEGGER license. Review the official download and licensing documentation before installing or using the software.\n\nOfficial downloads and documentation: https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002F\nCommander overview and licensing: https:\u002F\u002Fwww.segger.com\u002Fproducts\u002Fdebug-probes\u002Fj-link\u002Ftools\u002Fj-link-commander\u002F\nOfficial release notes: https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html","Software and Documentation pack for Segger J-Link debug probes","SEGGER Microcontroller GmbH","SEGGER J-Link Command Line Tools","cbc843e5f076b41cef4b226ab97c8da3d362053e4ac5ad5f808a71f0b2e1c7f9",124691382,"https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FJLink_MacOSX_V984_universal.pkg","https:\u002F\u002Fformulae.brew.sh\u002Fcask\u002Fsegger-jlink","https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink","https:\u002F\u002Fcdn.opennavo.com\u002Ficons\u002Fuploads\u002F547ec33a05ea\u002F2dd8e0373e35-256.png","brew install --cask segger-jlink",{"d30":78,"d365":79,"d90":80},142,2452,535,"cask",{"bodyMarkdown":83,"brewCommittedAt":84,"hasNotes":85,"id":86,"isLatest":85,"isPrerelease":47,"machineTranslated":47,"publishedAt":87,"sections":88,"source":89,"sourceLocale":90,"summary":91,"title":92,"translation":93,"version":95},"## Version V9.84 (2026-10-07)\n\n### Device Support\n\n- Giantec GT25Q32EB-H: Added flash programming support.\n\n- GigaDevice GD55B01GE: Added flash programming support.\n\n- Infineon PSC3xxE, PSC3xxF: Added support for secure debug (https:\u002F\u002Fkb.segger.com\u002FInfineon_PSC3#Secure_Debug).\n\n- ST SR6P6: Improved flash programming speed (https:\u002F\u002Fkb.segger.com\u002FST_SR6P6#Flash_programming).\n\n- ST SR6P7: Improved flash programming speed (https:\u002F\u002Fkb.segger.com\u002FST_SR6P7#Flash_programming).\n\n- TDK Micronas HVC5 series: Added debug and flash programming support for HVC5222C-C1, HVC5221D-C1, HVC5223C-C1 (https:\u002F\u002Fkb.segger.com\u002FTDK-Micronas_HVC_5x).\n\n- Telink TL721: Removed devices without JTAG support.\n\n### DLL\n\n- Improved error code information for external QSPI flash loaders in case the flash loader detects an unknown flash ID.\n\n### Firmware\n\n- Flasher ARM V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher ARM V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher ARM V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher ARM V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher Compact V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher Compact V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher Compact V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher Portable PLUS V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher Portable PLUS V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher Portable PLUS V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher PRO V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher PRO V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher PRO V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher PRO V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher Pro V8: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher PRO XL V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher PRO XL V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher PRO XL V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher PRO XL V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n- Flasher Pro XL V8: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\n\n### J-Flash\n\n- Improved error code information for external QSPI flash loaders in case the flash loader detects an unknown flash ID.\n\n### J-Flash SPI\n\n- Giantec GT25Q32EB-H: Added flash programming support.\n\n- GigaDevice GD55B01GE: Added flash programming support.\n\n- Infineon CY15B116QN: Added FRAM memory support.\n\n- Infineon CY15V116QN: Added FRAM memory support.\n\n### SWO Viewer\n\n- Manually configured SWO frequency settings could be overridden on macOS. Fixed.\n\n- The application could crash under special circumstances when closing the configuration dialog. Fixed.\n\nOfficial source: https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html","2026-10-07T19:51:25Z",true,3739,"2026-10-07T00:00:00Z",[],"editorial","en-US","Adds device and flash-memory support, improves ST flash-programming speed and QSPI loader errors, fixes Flasher app-memory access, and fixes macOS SWO settings and a viewer crash.","SEGGER J-Link 9.84",{"locale":90,"machineTranslated":47,"sourceLocale":90,"status":94},"source","9.84","Segger J-Link Command Line Tools",[96,98],"segger-jlink",[100,133,165,198,230,263,295,328,360,393,425,458,490,523],{"arch":61,"artifacts":101,"conflictsWith":122,"dependsOn":125,"downloadSha256":70,"downloadUrl":72,"macos":131,"requiresRosetta":47,"tag":132,"version":95},{"apps":102,"binaries":103,"entries":104,"pkgs":121},[],[],[105,111,115],{"declaration":106,"phase":21,"sources":110,"type":21},{"uninstall":107},[108],{"pkgutil":13,"quit":109},[15,16,17,18,19,20],[],{"declaration":112,"phase":27,"sources":114,"type":29},{"pkg":113},[26],[26],{"declaration":116,"phase":43,"sources":120,"type":45},{"zap":117},[118],{"trash":119},[35,36,37,38,39,40,41,42],[],[26],{"casks":123,"formulae":124},[],[],{"arch":126,"casks":127,"formulae":128,"requirements":129},[61],[],[],{"macos":130},{},"27","golden_gate",{"arch":60,"artifacts":134,"conflictsWith":155,"dependsOn":158,"downloadSha256":70,"downloadUrl":72,"macos":131,"requiresRosetta":47,"tag":164,"version":95},{"apps":135,"binaries":136,"entries":137,"pkgs":154},[],[],[138,144,148],{"declaration":139,"phase":21,"sources":143,"type":21},{"uninstall":140},[141],{"pkgutil":13,"quit":142},[15,16,17,18,19,20],[],{"declaration":145,"phase":27,"sources":147,"type":29},{"pkg":146},[26],[26],{"declaration":149,"phase":43,"sources":153,"type":45},{"zap":150},[151],{"trash":152},[35,36,37,38,39,40,41,42],[],[26],{"casks":156,"formulae":157},[],[],{"arch":159,"casks":160,"formulae":161,"requirements":162},[60],[],[],{"macos":163},{},"arm64_golden_gate",{"arch":61,"artifacts":166,"conflictsWith":187,"dependsOn":190,"downloadSha256":70,"downloadUrl":72,"macos":196,"requiresRosetta":47,"tag":197,"version":95},{"apps":167,"binaries":168,"entries":169,"pkgs":186},[],[],[170,176,180],{"declaration":171,"phase":21,"sources":175,"type":21},{"uninstall":172},[173],{"pkgutil":13,"quit":174},[15,16,17,18,19,20],[],{"declaration":177,"phase":27,"sources":179,"type":29},{"pkg":178},[26],[26],{"declaration":181,"phase":43,"sources":185,"type":45},{"zap":182},[183],{"trash":184},[35,36,37,38,39,40,41,42],[],[26],{"casks":188,"formulae":189},[],[],{"arch":191,"casks":192,"formulae":193,"requirements":194},[61],[],[],{"macos":195},{},"26","tahoe",{"arch":60,"artifacts":199,"conflictsWith":220,"dependsOn":223,"downloadSha256":70,"downloadUrl":72,"macos":196,"requiresRosetta":47,"tag":229,"version":95},{"apps":200,"binaries":201,"entries":202,"pkgs":219},[],[],[203,209,213],{"declaration":204,"phase":21,"sources":208,"type":21},{"uninstall":205},[206],{"pkgutil":13,"quit":207},[15,16,17,18,19,20],[],{"declaration":210,"phase":27,"sources":212,"type":29},{"pkg":211},[26],[26],{"declaration":214,"phase":43,"sources":218,"type":45},{"zap":215},[216],{"trash":217},[35,36,37,38,39,40,41,42],[],[26],{"casks":221,"formulae":222},[],[],{"arch":224,"casks":225,"formulae":226,"requirements":227},[60],[],[],{"macos":228},{},"arm64_tahoe",{"arch":61,"artifacts":231,"conflictsWith":252,"dependsOn":255,"downloadSha256":70,"downloadUrl":72,"macos":261,"requiresRosetta":47,"tag":262,"version":95},{"apps":232,"binaries":233,"entries":234,"pkgs":251},[],[],[235,241,245],{"declaration":236,"phase":21,"sources":240,"type":21},{"uninstall":237},[238],{"pkgutil":13,"quit":239},[15,16,17,18,19,20],[],{"declaration":242,"phase":27,"sources":244,"type":29},{"pkg":243},[26],[26],{"declaration":246,"phase":43,"sources":250,"type":45},{"zap":247},[248],{"trash":249},[35,36,37,38,39,40,41,42],[],[26],{"casks":253,"formulae":254},[],[],{"arch":256,"casks":257,"formulae":258,"requirements":259},[61],[],[],{"macos":260},{},"15","sequoia",{"arch":60,"artifacts":264,"conflictsWith":285,"dependsOn":288,"downloadSha256":70,"downloadUrl":72,"macos":261,"requiresRosetta":47,"tag":294,"version":95},{"apps":265,"binaries":266,"entries":267,"pkgs":284},[],[],[268,274,278],{"declaration":269,"phase":21,"sources":273,"type":21},{"uninstall":270},[271],{"pkgutil":13,"quit":272},[15,16,17,18,19,20],[],{"declaration":275,"phase":27,"sources":277,"type":29},{"pkg":276},[26],[26],{"declaration":279,"phase":43,"sources":283,"type":45},{"zap":280},[281],{"trash":282},[35,36,37,38,39,40,41,42],[],[26],{"casks":286,"formulae":287},[],[],{"arch":289,"casks":290,"formulae":291,"requirements":292},[60],[],[],{"macos":293},{},"arm64_sequoia",{"arch":61,"artifacts":296,"conflictsWith":317,"dependsOn":320,"downloadSha256":70,"downloadUrl":72,"macos":326,"requiresRosetta":47,"tag":327,"version":95},{"apps":297,"binaries":298,"entries":299,"pkgs":316},[],[],[300,306,310],{"declaration":301,"phase":21,"sources":305,"type":21},{"uninstall":302},[303],{"pkgutil":13,"quit":304},[15,16,17,18,19,20],[],{"declaration":307,"phase":27,"sources":309,"type":29},{"pkg":308},[26],[26],{"declaration":311,"phase":43,"sources":315,"type":45},{"zap":312},[313],{"trash":314},[35,36,37,38,39,40,41,42],[],[26],{"casks":318,"formulae":319},[],[],{"arch":321,"casks":322,"formulae":323,"requirements":324},[61],[],[],{"macos":325},{},"14","sonoma",{"arch":60,"artifacts":329,"conflictsWith":350,"dependsOn":353,"downloadSha256":70,"downloadUrl":72,"macos":326,"requiresRosetta":47,"tag":359,"version":95},{"apps":330,"binaries":331,"entries":332,"pkgs":349},[],[],[333,339,343],{"declaration":334,"phase":21,"sources":338,"type":21},{"uninstall":335},[336],{"pkgutil":13,"quit":337},[15,16,17,18,19,20],[],{"declaration":340,"phase":27,"sources":342,"type":29},{"pkg":341},[26],[26],{"declaration":344,"phase":43,"sources":348,"type":45},{"zap":345},[346],{"trash":347},[35,36,37,38,39,40,41,42],[],[26],{"casks":351,"formulae":352},[],[],{"arch":354,"casks":355,"formulae":356,"requirements":357},[60],[],[],{"macos":358},{},"arm64_sonoma",{"arch":61,"artifacts":361,"conflictsWith":382,"dependsOn":385,"downloadSha256":70,"downloadUrl":72,"macos":391,"requiresRosetta":47,"tag":392,"version":95},{"apps":362,"binaries":363,"entries":364,"pkgs":381},[],[],[365,371,375],{"declaration":366,"phase":21,"sources":370,"type":21},{"uninstall":367},[368],{"pkgutil":13,"quit":369},[15,16,17,18,19,20],[],{"declaration":372,"phase":27,"sources":374,"type":29},{"pkg":373},[26],[26],{"declaration":376,"phase":43,"sources":380,"type":45},{"zap":377},[378],{"trash":379},[35,36,37,38,39,40,41,42],[],[26],{"casks":383,"formulae":384},[],[],{"arch":386,"casks":387,"formulae":388,"requirements":389},[61],[],[],{"macos":390},{},"13","ventura",{"arch":60,"artifacts":394,"conflictsWith":415,"dependsOn":418,"downloadSha256":70,"downloadUrl":72,"macos":391,"requiresRosetta":47,"tag":424,"version":95},{"apps":395,"binaries":396,"entries":397,"pkgs":414},[],[],[398,404,408],{"declaration":399,"phase":21,"sources":403,"type":21},{"uninstall":400},[401],{"pkgutil":13,"quit":402},[15,16,17,18,19,20],[],{"declaration":405,"phase":27,"sources":407,"type":29},{"pkg":406},[26],[26],{"declaration":409,"phase":43,"sources":413,"type":45},{"zap":410},[411],{"trash":412},[35,36,37,38,39,40,41,42],[],[26],{"casks":416,"formulae":417},[],[],{"arch":419,"casks":420,"formulae":421,"requirements":422},[60],[],[],{"macos":423},{},"arm64_ventura",{"arch":61,"artifacts":426,"conflictsWith":447,"dependsOn":450,"downloadSha256":70,"downloadUrl":72,"macos":456,"requiresRosetta":47,"tag":457,"version":95},{"apps":427,"binaries":428,"entries":429,"pkgs":446},[],[],[430,436,440],{"declaration":431,"phase":21,"sources":435,"type":21},{"uninstall":432},[433],{"pkgutil":13,"quit":434},[15,16,17,18,19,20],[],{"declaration":437,"phase":27,"sources":439,"type":29},{"pkg":438},[26],[26],{"declaration":441,"phase":43,"sources":445,"type":45},{"zap":442},[443],{"trash":444},[35,36,37,38,39,40,41,42],[],[26],{"casks":448,"formulae":449},[],[],{"arch":451,"casks":452,"formulae":453,"requirements":454},[61],[],[],{"macos":455},{},"12","monterey",{"arch":60,"artifacts":459,"conflictsWith":480,"dependsOn":483,"downloadSha256":70,"downloadUrl":72,"macos":456,"requiresRosetta":47,"tag":489,"version":95},{"apps":460,"binaries":461,"entries":462,"pkgs":479},[],[],[463,469,473],{"declaration":464,"phase":21,"sources":468,"type":21},{"uninstall":465},[466],{"pkgutil":13,"quit":467},[15,16,17,18,19,20],[],{"declaration":470,"phase":27,"sources":472,"type":29},{"pkg":471},[26],[26],{"declaration":474,"phase":43,"sources":478,"type":45},{"zap":475},[476],{"trash":477},[35,36,37,38,39,40,41,42],[],[26],{"casks":481,"formulae":482},[],[],{"arch":484,"casks":485,"formulae":486,"requirements":487},[60],[],[],{"macos":488},{},"arm64_monterey",{"arch":61,"artifacts":491,"conflictsWith":512,"dependsOn":515,"downloadSha256":70,"downloadUrl":72,"macos":521,"requiresRosetta":47,"tag":522,"version":95},{"apps":492,"binaries":493,"entries":494,"pkgs":511},[],[],[495,501,505],{"declaration":496,"phase":21,"sources":500,"type":21},{"uninstall":497},[498],{"pkgutil":13,"quit":499},[15,16,17,18,19,20],[],{"declaration":502,"phase":27,"sources":504,"type":29},{"pkg":503},[26],[26],{"declaration":506,"phase":43,"sources":510,"type":45},{"zap":507},[508],{"trash":509},[35,36,37,38,39,40,41,42],[],[26],{"casks":513,"formulae":514},[],[],{"arch":516,"casks":517,"formulae":518,"requirements":519},[61],[],[],{"macos":520},{},"11","big_sur",{"arch":60,"artifacts":524,"conflictsWith":545,"dependsOn":548,"downloadSha256":70,"downloadUrl":72,"macos":521,"requiresRosetta":47,"tag":554,"version":95},{"apps":525,"binaries":526,"entries":527,"pkgs":544},[],[],[528,534,538],{"declaration":529,"phase":21,"sources":533,"type":21},{"uninstall":530},[531],{"pkgutil":13,"quit":532},[15,16,17,18,19,20],[],{"declaration":535,"phase":27,"sources":537,"type":29},{"pkg":536},[26],[26],{"declaration":539,"phase":43,"sources":543,"type":45},{"zap":540},[541],{"trash":542},[35,36,37,38,39,40,41,42],[],[26],{"casks":546,"formulae":547},[],[],{"arch":549,"casks":550,"formulae":551,"requirements":552},[60],[],[],{"macos":553},{},"arm64_big_sur",{"icon":50,"machineTranslated":47,"name":51,"slug":52,"sourceLocale":53},659,100,{"brewLag":559,"cadence":563,"count30d":564},{"compared":560,"earlierCount":561,"medianMinutes":562},3,0,853,"weekly",5,[],"https:\u002F\u002Fgithub.com\u002Fhomebrew\u002Fhomebrew-cask\u002Fblob\u002FHEAD\u002FCasks\u002Fs\u002Fsegger-jlink.rb","Software, manuals, and firmware updates for SEGGER J-Link and J-Trace debug probes, including command-line target inspection and flash programming tools.",{"locale":90,"machineTranslated":47,"sourceLocale":90,"status":94},{"arm64":85,"requiresRosetta":47,"status":570,"x86_64":85},"known",[572,573,574,575,576],"embedded","debugging","J-Link","flash programming","command line","homebrew\u002Fcask","2026-10-07T20:45:22.274484Z",null,{"current":581,"records":582,"size":693,"stats":694,"total":557},1,[583,586,596,606,613,618,623,628,633,638,643,648,653,658,663,668,673,678,683,688],{"bodyMarkdown":83,"brewCommittedAt":84,"hasNotes":85,"id":86,"isLatest":85,"isPrerelease":47,"machineTranslated":47,"publishedAt":87,"sections":584,"source":89,"sourceLocale":90,"summary":91,"title":92,"translation":585,"version":95},[],{"locale":90,"machineTranslated":47,"sourceLocale":90,"status":94},{"bodyMarkdown":587,"brewCommittedAt":588,"hasNotes":85,"id":589,"isLatest":47,"isPrerelease":47,"machineTranslated":47,"publishedAt":590,"sections":591,"source":89,"sourceLocale":90,"summary":592,"title":593,"translation":594,"version":595},"## Version V9.82 (2026-09-30)\n\n### Highlights:\n\n### Device Provisioner\n\n- NXP MCX L: Added support for Secure Installer erase (https:\u002F\u002Fkb.segger.com\u002FNXP_MCX_L_SiErase).\n\n### Device Support\n\n- HPMicro HPM51 devices series: Added debug and (QSPI) flash programming support (https:\u002F\u002Fkb.segger.com\u002FHPMicro_HPM51).\n\n- Microchip PIC32CM: Added debug & flash programming support for PIC32CM PL10 subfamily (https:\u002F\u002Fkb.segger.com\u002FMicrochip_PIC32CM_PL10).\n\n- SinoWealth SH30F2 series: Added debug and flash programming support (https:\u002F\u002Fkb.segger.com\u002FSinoWealth_SH30F2).\n\n- TI MSPM33: Added programming support for NONMAIN flash (https:\u002F\u002Fkb.segger.com\u002FTI_MSPM33).\n\n### Other changes:\n\n### Configurator\n\n- Added product images to configuration dialog.\n\n- Removed Flasher \u002F J-Link banner from main window.\n\n### Device Provisioner\n\n- Infineon PSC3: Added the required 'Device' parameter (https:\u002F\u002Fkb.segger.com\u002FInfineon_PSOC_Control_C3_Debug_Port_Authentication#Usage).\n\n- Infineon PSC3: Debug authentication could fail when using the JTAG interface. Fixed.\n\n- Infineon PSC3: Debug authentication failed in LCS SECURE. Fixed.\n\n### Device Support\n\n- BYT BY25FQ64EL: Added SPI flash programming support.\n\n- BYT BY25Q64ES: Added SPI flash programming support.\n\n- C*Core CCRC4086S: Added support for reset pin strategy.\n\n- C*Core CCRC4086S: Software breakpoints could fail. Fixed.\n\n- Nordic Semi nRF54L series: UICR programming failed when data was written to undefined addresses between the UICR registers. Fixed.\n\n- NXP i.MX RT1180: Flash programming failed when using loader \"PortA_CLK@EMC_B1_41_nCS@EMC_B1_39_D0@EMC_B1_35_D1@EMC_B1_36_D2@EMC_B1_37_D3@EMC_B1_38\". Introduced with v9.80. Fixed.\n\n- NXP MCXA173 & MCXA174: Flash programming consistently failed with a timeout during the preparation step. Introduced in v9.54. Fixed.\n\n- NXP MCXA343 & MCXA344: Flash programming for CMPA bank consistently failed with a timeout during the preparation step. Introduced in v9.54. Fixed.\n\n- Raspberry Pi: Added device names for RP2350A, RP2350B, RP2354A and RP2354B.\n\n- Renesas RA8: Flash programming in standalone mode could fail after changing the protection level \u002F DLM state. Introduced in v9.40. Fixed.\n\n- ST SR6G3: Improved flash programming speed (https:\u002F\u002Fkb.segger.com\u002FST_SR6G3#Flash_programming).\n\n- ST SR6G6: Improved flash programming speed (https:\u002F\u002Fkb.segger.com\u002FST_SR6G6#Flash_programming).\n\n### DLL\n\n- Added command option \"Zca\" for \"RISCV_ForceExtensions\" to override detection of compressed instruction extension.\n\n- Added command string \"RISCV_ForceExtensions\" to override auto detection results (https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#RISCV_ForceExtensions).\n\n- Added command string \"SetMemCacheExpiration\" (https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#SetMemCacheExpiration).\n\n- Added J-Link command string \"AllowLTRACEPageAllocOnUnknown\". (https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#AllowLTRACEPageAllocOnUnknown)\n\n- RISC-V: Hardware breakpoint detection could fail. Introduced in V9.76. Fixed.\n\n### Firmware\n\n- Flasher ARM V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher ARM V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher ARM V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher ARM V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher Compact V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher Compact V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher Compact V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher Compact V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher Compact V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher Compact V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher Compact V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher Compact V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher Compact V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher Portable PLUS V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher Portable PLUS V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher Portable PLUS V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher Portable PLUS V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher Portable PLUS V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher Portable PLUS V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher Portable PLUS V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher Portable PLUS V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher Portable PLUS V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO V5-1: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher PRO V5-1: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher PRO V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher PRO V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher PRO V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher PRO V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher PRO V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher PRO V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher PRO V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO XL V5-1: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher PRO XL V5-1: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher PRO XL V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO XL V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher PRO XL V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher PRO XL V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO XL V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher PRO XL V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher PRO XL V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO XL V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\n\n- Flasher PRO XL V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\n\n- Flasher PRO XL V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO XL V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- Flasher PRO XL V8: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link BASE\u002FPLUS V12: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link BASE\u002FPLUS V13: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link EDU Mini V1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link EDU Mini V2: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link OB RA4M2-Full: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link PRO PoE V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link PRO PoE V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link PRO V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link PRO V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link PRO V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link PRO V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link Pro V8: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link Ultra V8: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link ULTRA+ V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link ULTRA+ V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link ULTRA+ V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link ULTRA+ V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link WiFi V2: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Link-OB-K22-CortexA: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Trace PRO V3 Cortex: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Trace PRO V3: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Trace PRO V4 Cortex: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n- J-Trace PRO V4: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\n\n### J-Flash SPI\n\n- BYT BY25FQ64EL: Added SPI flash programming support.\n\n- BYT BY25Q64ES: Added SPI flash programming support.\n\n### J-Link USB Web Server\n\n- Application always opened a terminal window on macOS. Fixed.\n\n### Trace\n\n- Improved detection of wrongly sampled trace data due to e.g. signal integrity issues.\n\nOfficial source: https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html","2026-09-30T14:13:59Z",3741,"2026-09-30T00:00:00Z",[],"Expands device support and secure-installer erase, adds RISC-V and memory-cache command controls, and fixes debug authentication, flash programming, breakpoint detection, and probe firmware issues.","SEGGER J-Link 9.82",{"locale":90,"machineTranslated":47,"sourceLocale":90,"status":94},"9.82",{"bodyMarkdown":597,"brewCommittedAt":598,"hasNotes":85,"id":599,"isLatest":47,"isPrerelease":47,"machineTranslated":47,"publishedAt":600,"sections":601,"source":89,"sourceLocale":90,"summary":602,"title":603,"translation":604,"version":605},"## Version V9.80 (2026-09-23)\n\n### Commander\n\n- J-Link Commander crashed under certain circumstances on Linux\u002FmacOS. Fixed.\n\n### Device Provisioner\n\n- Root-relative paths were not resolved correctly on Windows. Fixed.\n\n### Device Support\n\n- Added additional Microchip part numbers for SAM9X family.\n\n- Added additional Microchip part numbers for SAMA5 family.\n\n- Added additional Microchip part numbers for SAMA7 family.\n\n- Added FlexSPI2 Port A flash programming support for pin config \"CLK@EMC_B1_41_nCS@EMC_B1_39_D0@EMC_B1_35_D1@EMC_B1_36_D2@EMC_B1_37_D3@EMC_B1_38\" (https:\u002F\u002Fkb.segger.com\u002FNXP_i.MX_RT1180).\n\n- BYT BY25D20FV: Added SPI flash programming support.\n\n- BYT BY25D40ES: Added SPI Flash programming support.\n\n- BYT BY25FQ128EL: Added SPI flash programming support.\n\n- BYT BY25FQ16EL: Added SPI flash programming support.\n\n- BYT BY25FQ16ES: Added SPI flash programming support.\n\n- BYT BY25FQ256ES: Added SPI flash programming support.\n\n- BYT BY25FQ32EL: Added SPI flash programming support.\n\n- BYT BY25FQ32ES: Added SPI flash programming support.\n\n- BYT BY25FQ64ES: Added SPI flash programming support.\n\n- BYT BY25Q16AW: Added SPI flash programming support.\n\n- BYT BY25Q16ES: Added SPI Flash programming support.\n\n- BYT BY25Q20AW: Added SPI flash programming support.\n\n- BYT BY25Q256FS: Added SPI Flash programming support.\n\n- BYT BY25Q32ES: Added SPI Flash programming support.\n\n- BYT BY25Q40GW: Added SPI flash programming support.\n\n- BYT BY25Q80AW: Added SPI flash programming support.\n\n- BYT BY25Q80BS: Added SPI flash programming support.\n\n- BYT BY25Q80ES: Added SPI Flash programming support.\n\n- CVA CHIP CVM011x: Added flash programming support for Info Region (https:\u002F\u002Fkb.segger.com\u002FCVA_CHIP_CVM011x).\n\n- CVA CHIP CVM011x: During flash programming watchdog was not fed correctly if windowed mode was active. Fixed.\n\n- Geehy G32M3101: Added debug and flash programming support (https:\u002F\u002Fkb.segger.com\u002FGeehy_G32M3101).\n\n- Giantec GT25Q16A: Added SPI flash programming support.\n\n- NXP i.MX RT1180: Renamed existing FlexSPI1\u002FFlexSPI2 flashloaders (https:\u002F\u002Fkb.segger.com\u002FNXP_i.MX_RT1180).\n\n- Removed non-existant Microchip part number ATSAMA5D25C.\n\n- Renesas AT25QF0321C: Added SPI flash programming support.\n\n- Renesas AT25QF0641C: Added SPI flash programming support.\n\n- Renesas AT25SF0321C: Added SPI flash programming support.\n\n- Renesas AT25SF0641C: Added SPI flash programming support.\n\n- Renesas RA4E1, RA4M2, RA4M3: Flash erase operation on code flash memory could time out prematurely before the operation completed. Fixed.\n\n- Renesas RA6E1, RA6M4, RA4M5, RA6T2: Flash erase operation on code flash memory could time out prematurely before the operation completed. Fixed.\n\n- Renesas RX24T: Added debug and flash programming support for part numbers R5F524TB, R5F524TC and R5F524TE (https:\u002F\u002Fkb.segger.com\u002FRenesas_RX24T).\n\n- ST Stellar SR6 : Added new part numbers (SR6P6C6 and SR6G6C4).\n\n- TDK Micronas HVC4xxx: Flash programming on devices with small RAM failed. Introduced with V9.32. Fixed.\n\n- TDK Micronas HVC4xxx: Flash programming on NVRAM Page10 failed. Introduced with V9.32. Fixed.\n\n### DLL\n\n- Root-relative paths were not resolved correctly on Windows. Fixed.\n\n### Firmware\n\n- Flasher ARM V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher ARM V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher ARM V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher ARM V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Compact V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Compact V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Compact V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Portable PLUS V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Portable PLUS V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Portable PLUS V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher PRO V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher PRO V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher PRO V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher PRO V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Pro V8: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher PRO XL V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher PRO XL V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher PRO XL V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher PRO XL V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Pro XL V8: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\n\n- Flasher Pro XL V8: Setting an adjustable target supply voltage of 1500mV could sometimes fail. Fixed.\n\n### J-Flash SPI\n\n- BYT BY25D20FV: Added SPI flash programming support.\n\n- BYT BY25D40ES: Added SPI flash programming support.\n\n- BYT BY25FQ128EL: Added SPI flash programming support.\n\n- BYT BY25FQ16EL: Added SPI flash programming support.\n\n- BYT BY25FQ16ES: Added SPI flash programming support.\n\n- BYT BY25FQ256ES: Added SPI flash programming support.\n\n- BYT BY25FQ32EL: Added SPI flash programming support.\n\n- BYT BY25FQ32ES: Added SPI flash programming support.\n\n- BYT BY25FQ64ES: Added SPI flash programming support.\n\n- BYT BY25Q16AW: Added SPI flash programming support.\n\n- BYT BY25Q16ES: Added SPI flash programming support.\n\n- BYT BY25Q20AW: Added SPI flash programming support.\n\n- BYT BY25Q256FS: Added SPI flash programming support.\n\n- BYT BY25Q32ES: Added SPI flash programming support.\n\n- BYT BY25Q40GW: Added SPI flash programming support.\n\n- BYT BY25Q80AW: Added SPI flash programming support.\n\n- BYT BY25Q80BS: Added SPI flash programming support.\n\n- BYT BY25Q80ES: Added SPI flash programming support.\n\n- Giantec GT25Q16A: Added SPI flash programming support.\n\n- Renesas AT25QF0321C: Added SPI flash programming support.\n\n- Renesas AT25QF0641C: Added SPI flash programming support.\n\n- Renesas AT25SF0321C: Added SPI flash programming support.\n\n- Renesas AT25SF0641C: Added SPI flash programming support.\n\n### RTT Logger\n\n- Root-relative paths were not resolved correctly on Windows. Fixed.\n\nOfficial source: https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html","2026-09-23T13:52:59Z",3743,"2026-09-23T00:00:00Z",[],"Fixes J-Link Commander crashes on Linux and macOS, expands device and SPI flash support, and fixes flash erase, authorized flashing, and Windows path handling.","SEGGER J-Link 9.80",{"locale":90,"machineTranslated":47,"sourceLocale":90,"status":94},"9.80",{"brewCommittedAt":607,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":608,"source":609,"translation":610,"version":612},"2026-09-16T16:42:30Z",[],"homebrew",{"status":611},"none","9.78",{"brewCommittedAt":614,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":615,"source":609,"translation":616,"version":617},"2026-09-09T17:02:40Z",[],{"status":611},"9.76",{"brewCommittedAt":619,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":620,"source":609,"translation":621,"version":622},"2026-09-14T17:14:09Z",[],{"status":611},"9.76a",{"brewCommittedAt":624,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":625,"source":609,"translation":626,"version":627},"2026-09-02T13:47:41Z",[],{"status":611},"9.74",{"brewCommittedAt":629,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":630,"source":609,"translation":631,"version":632},"2026-08-26T14:16:33Z",[],{"status":611},"9.72",{"brewCommittedAt":634,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":635,"source":609,"translation":636,"version":637},"2026-08-19T13:49:59Z",[],{"status":611},"9.70",{"brewCommittedAt":639,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":640,"source":609,"translation":641,"version":642},"2026-08-12T16:49:10Z",[],{"status":611},"9.68",{"brewCommittedAt":644,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":645,"source":609,"translation":646,"version":647},"2026-08-17T13:58:49Z",[],{"status":611},"9.68a",{"brewCommittedAt":649,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":650,"source":609,"translation":651,"version":652},"2026-08-05T11:24:39Z",[],{"status":611},"9.66",{"brewCommittedAt":654,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":655,"source":609,"translation":656,"version":657},"2026-07-29T14:10:07Z",[],{"status":611},"9.64",{"brewCommittedAt":659,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":660,"source":609,"translation":661,"version":662},"2026-07-22T13:51:16Z",[],{"status":611},"9.62",{"brewCommittedAt":664,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":665,"source":609,"translation":666,"version":667},"2026-07-15T13:47:06Z",[],{"status":611},"9.60",{"brewCommittedAt":669,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":670,"source":609,"translation":671,"version":672},"2026-07-09T17:17:41Z",[],{"status":611},"9.58",{"brewCommittedAt":674,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":675,"source":609,"translation":676,"version":677},"2026-07-01T17:09:56Z",[],{"status":611},"9.56",{"brewCommittedAt":679,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":680,"source":609,"translation":681,"version":682},"2026-06-25T17:26:59Z",[],{"status":611},"9.54",{"brewCommittedAt":684,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":685,"source":609,"translation":686,"version":687},"2026-06-18T17:53:07Z",[],{"status":611},"9.52",{"brewCommittedAt":689,"hasNotes":47,"isLatest":47,"isPrerelease":47,"sections":690,"source":609,"translation":691,"version":692},"2026-06-10T11:43:52Z",[],{"status":611},"9.50",20,{"brewLag":695,"cadence":563,"count30d":564},{"compared":560,"earlierCount":561,"medianMinutes":562},{"current":581,"records":697,"size":581,"stats":701,"total":557},[698],{"bodyMarkdown":83,"brewCommittedAt":84,"hasNotes":85,"id":86,"isLatest":85,"isPrerelease":47,"machineTranslated":47,"publishedAt":87,"sections":699,"source":89,"sourceLocale":90,"summary":91,"title":92,"translation":700,"version":95},[],{"locale":90,"machineTranslated":47,"sourceLocale":90,"status":94},{"brewLag":702,"cadence":563,"count30d":564},{"compared":560,"earlierCount":561,"medianMinutes":562},"\u003Ch3 class=\"on-md-heading-1\">Version V9.84 (2026-10-07)\u003C\u002Fh3>\n\u003Ch4 class=\"on-md-heading-2\">Device Support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Giantec GT25Q32EB-H: Added flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>GigaDevice GD55B01GE: Added flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Infineon PSC3xxE, PSC3xxF: Added support for secure debug (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FInfineon_PSC3#Secure_Debug\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FInfineon_PSC3#Secure_Debug\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>ST SR6P6: Improved flash programming speed (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FST_SR6P6#Flash_programming\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FST_SR6P6#Flash_programming\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>ST SR6P7: Improved flash programming speed (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FST_SR6P7#Flash_programming\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FST_SR6P7#Flash_programming\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>TDK Micronas HVC5 series: Added debug and flash programming support for HVC5222C-C1, HVC5221D-C1, HVC5223C-C1 (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FTDK-Micronas_HVC_5x\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FTDK-Micronas_HVC_5x\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Telink TL721: Removed devices without JTAG support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">DLL\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Improved error code information for external QSPI flash loaders in case the flash loader detects an unknown flash ID.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Firmware\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Flasher ARM V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Pro V8: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5-1: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V6: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V7: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Pro XL V8: Reading or writing app memory prior to execution (e.g. via Flasher App Builder \"w4\" command) failed with error -5. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">J-Flash\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Improved error code information for external QSPI flash loaders in case the flash loader detects an unknown flash ID.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">J-Flash SPI\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Giantec GT25Q32EB-H: Added flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>GigaDevice GD55B01GE: Added flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Infineon CY15B116QN: Added FRAM memory support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Infineon CY15V116QN: Added FRAM memory support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">SWO Viewer\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Manually configured SWO frequency settings could be overridden on macOS. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>The application could crash under special circumstances when closing the configuration dialog. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Official source: \u003Ca href=\"https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html\u003C\u002Fa>\u003C\u002Fp>\n","\u003Ch3 class=\"on-md-heading-1\">Version V9.82 (2026-09-30)\u003C\u002Fh3>\n\u003Ch4 class=\"on-md-heading-2\">Highlights:\u003C\u002Fh4>\n\u003Ch4 class=\"on-md-heading-2\">Device Provisioner\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>NXP MCX L: Added support for Secure Installer erase (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FNXP_MCX_L_SiErase\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FNXP_MCX_L_SiErase\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Device Support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>HPMicro HPM51 devices series: Added debug and (QSPI) flash programming support (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FHPMicro_HPM51\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FHPMicro_HPM51\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Microchip PIC32CM: Added debug & flash programming support for PIC32CM PL10 subfamily (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FMicrochip_PIC32CM_PL10\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FMicrochip_PIC32CM_PL10\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>SinoWealth SH30F2 series: Added debug and flash programming support (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FSinoWealth_SH30F2\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FSinoWealth_SH30F2\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>TI MSPM33: Added programming support for NONMAIN flash (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FTI_MSPM33\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FTI_MSPM33\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Other changes:\u003C\u002Fh4>\n\u003Ch4 class=\"on-md-heading-2\">Configurator\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Added product images to configuration dialog.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Removed Flasher \u002F J-Link banner from main window.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Device Provisioner\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Infineon PSC3: Added the required 'Device' parameter (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FInfineon_PSOC_Control_C3_Debug_Port_Authentication#Usage\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FInfineon_PSOC_Control_C3_Debug_Port_Authentication#Usage\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Infineon PSC3: Debug authentication could fail when using the JTAG interface. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Infineon PSC3: Debug authentication failed in LCS SECURE. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Device Support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>BYT BY25FQ64EL: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q64ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>C*Core CCRC4086S: Added support for reset pin strategy.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>C*Core CCRC4086S: Software breakpoints could fail. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Nordic Semi nRF54L series: UICR programming failed when data was written to undefined addresses between the UICR registers. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>NXP i.MX RT1180: Flash programming failed when using loader \"PortA_CLK@EMC_B1_41_nCS@EMC_B1_39_D0@EMC_B1_35_D1@EMC_B1_36_D2@EMC_B1_37_D3@EMC_B1_38\". Introduced with v9.80. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>NXP MCXA173 & MCXA174: Flash programming consistently failed with a timeout during the preparation step. Introduced in v9.54. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>NXP MCXA343 & MCXA344: Flash programming for CMPA bank consistently failed with a timeout during the preparation step. Introduced in v9.54. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Raspberry Pi: Added device names for RP2350A, RP2350B, RP2354A and RP2354B.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas RA8: Flash programming in standalone mode could fail after changing the protection level \u002F DLM state. Introduced in v9.40. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>ST SR6G3: Improved flash programming speed (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FST_SR6G3#Flash_programming\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FST_SR6G3#Flash_programming\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>ST SR6G6: Improved flash programming speed (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FST_SR6G6#Flash_programming\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FST_SR6G6#Flash_programming\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">DLL\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Added command option \"Zca\" for \"RISCV_ForceExtensions\" to override detection of compressed instruction extension.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Added command string \"RISCV_ForceExtensions\" to override auto detection results (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#RISCV_ForceExtensions\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#RISCV_ForceExtensions\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Added command string \"SetMemCacheExpiration\" (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#SetMemCacheExpiration\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#SetMemCacheExpiration\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Added J-Link command string \"AllowLTRACEPageAllocOnUnknown\". (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#AllowLTRACEPageAllocOnUnknown\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FJ-Link_Command_Strings#AllowLTRACEPageAllocOnUnknown\u003C\u002Fa>)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>RISC-V: Hardware breakpoint detection could fail. Introduced in V9.76. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Firmware\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Flasher ARM V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5-1: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5-1: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5-1: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5-1: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V6: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V6: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V7: Apps: Cancelling an app (#CANCEL) could take up to 10 seconds when the app was in a blocking call to SYS_IP_ResolveHost(). Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V7: Apps: Cancelling an app (#CANCEL) had no effect when the app was in a blocking IP service call, e.g. SYS_IP_Connect(), SYS_IP_Send(), SYS_IP_Recv(), etc. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V8: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link BASE\u002FPLUS V12: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link BASE\u002FPLUS V13: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link EDU Mini V1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link EDU Mini V2: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link OB RA4M2-Full: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link PRO PoE V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link PRO PoE V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link PRO V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link PRO V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link PRO V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link PRO V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link Pro V8: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link Ultra V8: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link ULTRA+ V5-1: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link ULTRA+ V5: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link ULTRA+ V6: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link ULTRA+ V7: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link WiFi V2: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Link-OB-K22-CortexA: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Trace PRO V3 Cortex: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Trace PRO V3: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Trace PRO V4 Cortex: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>J-Trace PRO V4: On ARMv8-A\u002FR targets in AArch64 state, SP_EL1 could be displayed as the current stack pointer when executing in EL1t. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">J-Flash SPI\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>BYT BY25FQ64EL: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q64ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">J-Link USB Web Server\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Application always opened a terminal window on macOS. Fixed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Trace\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Improved detection of wrongly sampled trace data due to e.g. signal integrity issues.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Official source: \u003Ca href=\"https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html\u003C\u002Fa>\u003C\u002Fp>\n","\u003Ch3 class=\"on-md-heading-1\">Version V9.80 (2026-09-23)\u003C\u002Fh3>\n\u003Ch4 class=\"on-md-heading-2\">Commander\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>J-Link Commander crashed under certain circumstances on Linux\u002FmacOS. Fixed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Device Provisioner\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Root-relative paths were not resolved correctly on Windows. Fixed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Device Support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Added additional Microchip part numbers for SAM9X family.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Added additional Microchip part numbers for SAMA5 family.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Added additional Microchip part numbers for SAMA7 family.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Added FlexSPI2 Port A flash programming support for pin config \"CLK@EMC_B1_41_nCS@EMC_B1_39_D0@EMC_B1_35_D1@EMC_B1_36_D2@EMC_B1_37_D3@EMC_B1_38\" (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FNXP_i.MX_RT1180\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FNXP_i.MX_RT1180\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25D20FV: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25D40ES: Added SPI Flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ128EL: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ16EL: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ16ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ256ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ32EL: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ32ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ64ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q16AW: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q16ES: Added SPI Flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q20AW: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q256FS: Added SPI Flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q32ES: Added SPI Flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q40GW: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q80AW: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q80BS: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q80ES: Added SPI Flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>CVA CHIP CVM011x: Added flash programming support for Info Region (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FCVA_CHIP_CVM011x\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FCVA_CHIP_CVM011x\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>CVA CHIP CVM011x: During flash programming watchdog was not fed correctly if windowed mode was active. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Geehy G32M3101: Added debug and flash programming support (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FGeehy_G32M3101\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FGeehy_G32M3101\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Giantec GT25Q16A: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>NXP i.MX RT1180: Renamed existing FlexSPI1\u002FFlexSPI2 flashloaders (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FNXP_i.MX_RT1180\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FNXP_i.MX_RT1180\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Removed non-existant Microchip part number ATSAMA5D25C.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas AT25QF0321C: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas AT25QF0641C: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas AT25SF0321C: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas AT25SF0641C: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas RA4E1, RA4M2, RA4M3: Flash erase operation on code flash memory could time out prematurely before the operation completed. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas RA6E1, RA6M4, RA4M5, RA6T2: Flash erase operation on code flash memory could time out prematurely before the operation completed. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas RX24T: Added debug and flash programming support for part numbers R5F524TB, R5F524TC and R5F524TE (\u003Ca href=\"https:\u002F\u002Fkb.segger.com\u002FRenesas_RX24T\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fkb.segger.com\u002FRenesas_RX24T\u003C\u002Fa>).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>ST Stellar SR6 : Added new part numbers (SR6P6C6 and SR6G6C4).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>TDK Micronas HVC4xxx: Flash programming on devices with small RAM failed. Introduced with V9.32. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>TDK Micronas HVC4xxx: Flash programming on NVRAM Page10 failed. Introduced with V9.32. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">DLL\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Root-relative paths were not resolved correctly on Windows. Fixed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">Firmware\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>Flasher ARM V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher ARM V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Compact V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Portable PLUS V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Pro V8: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5-1: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V5: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V6: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher PRO XL V7: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Pro XL V8: Authorized flashing: Files were not correctly moved to the secure partition. Introduced in V9.74. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Flasher Pro XL V8: Setting an adjustable target supply voltage of 1500mV could sometimes fail. Fixed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">J-Flash SPI\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>BYT BY25D20FV: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25D40ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ128EL: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ16EL: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ16ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ256ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ32EL: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ32ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25FQ64ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q16AW: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q16ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q20AW: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q256FS: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q32ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q40GW: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q80AW: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q80BS: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>BYT BY25Q80ES: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Giantec GT25Q16A: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas AT25QF0321C: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas AT25QF0641C: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas AT25SF0321C: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Renesas AT25SF0641C: Added SPI flash programming support.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4 class=\"on-md-heading-2\">RTT Logger\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Root-relative paths were not resolved correctly on Windows. Fixed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Official source: \u003Ca href=\"https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html\" target=\"_blank\" rel=\"noopener noreferrer\">https:\u002F\u002Fwww.segger.com\u002Fdownloads\u002Fjlink\u002FReleaseNotes_JLink.html\u003C\u002Fa>\u003C\u002Fp>\n"]