Revisiting /redocumenting debugging with arm-elf-insight because:
cygwin doesn't keep history between sessions anymore on lab PC, and found early debug description in March is missing details, as well understanding the process better now.
Created simple script, so don't have to remember a long path name to forte:
lmsdb.sh:
cd /cygdrive/d/AA_local/eclipseWork/forte_lms_neu/bin/lms/src
arm-elf-insight /cygdrive/d/AA_local/eclipseWork/forte_lms_neu/bin/lms/src/forte
arm-elf-insight /cygdrive/d/AA_local/eclipseWork/forte_lms_neu/bin/lms/src/forte
0. flash lms with fw code updates (flash.bat or Sam-ba)
1. start openocd.bat
in cygwin:
2. when lms is initialized (blinking led stopped), start arm-elf-insight using
./lmsdb.sh
3. In arm-elf-insight:
- connect to target
- remote tcp with port 3333 (for Raven JTAG != 3333 for example: 8888)
- in (view) console:
- monitor halt
- monitor reset
- select (view) breakpoints
- 1 breakpoint only if want to step
- 2 breakpoints max.
- for Raven montitor set hbreak 0xaaaaaa
- where 0xaaaaaa is address from breakpoint window
4. continue
5. start usb connection
6. start application and wait for the breakpoint to be reached
Miscellaneous Notes:
- If variable windows are open, then arm-elf-insight does not remember the host, but does if the variable windows have been closed.
- monitor help
- If a module is not there, then maybe none of its functions are called.
- DS-5 Debugger Commands
No comments:
Post a Comment