Debuggers

Cerca 2011 Segger discontinues IAR branded JLink debuggers:

• https://www.embedded.com/segger-discontinues-iar-branded-j-links/

An apparent manual for the cerca 2011 IAR branded Segger debugger:

• http://www.icbase.com/File/PDF/STM/STM30420712.pdf

Wow, save pin two this newer document regarding Segger's JLink pinout shows the same signal arrangement. Need to test this out to see whether same ribbon cable will work with IAR branded debugger:

• https://www.segger.com/products/debug-probes/j-link/technology/interface-description/

Example Segger JLinkExe command script:

ExitOnError 1
erase
reset
loadfile "build/img.hex" 0xa0000000
go
writeDP 1 0 
readDP 1
R0
quit

Call the above Segger script with following, adjust path to above script file when called from another directory:

JLinkExe -nogui 1 -if swd -speed auto -device LPC55S69_M33_0 -CommanderScript ./runner-cpu0.jlink

Note that when the app image can be viewed in dot hex format, those lines which begin with "02000004" indicate the two most significant address bytes. The following snippet describes code which begins at 0x1000000:

   1 :020000041000EA
   2 :1000000058960030E9260010DD200010D52600109B
   3 :10001000D5260010D5260010D5260010D5260010B4
   4 :10002000000000000000000000000000AD270010EC
      | |   |                                 ^^ checksum
      | |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ data
      | ^^^^ address LSBs
      ^^ count of data bytes in line