- Wed Jan 23, 2013 9:01 am
#154531
I have build OpenOCD from the Git repository for the TI ICDI support. It appears that it is working for the most part, but I am getting a lot <UNDEFINED> instruction errors when single instruction stepping through code. I know the code is good. I also have access to a JLink and using the Segger GDB server (with the same arm-none-eabi-gdb client) I don't see the <UNDEFINED> instruction errors.
It was recommended that I add "set mem inaccessible-by-default off" to my gdb init but that doesn't seem to have fixed the issue either.
One thing I did notice is that if I am debugging a TI Stellaris board that has one of the older FT2232 JTAG interfaces, when I connect using OpenOCD I get a lot more output, specifically it auto-detects what device is being accessed.:
It was recommended that I add "set mem inaccessible-by-default off" to my gdb init but that doesn't seem to have fixed the issue either.
One thing I did notice is that if I am debugging a TI Stellaris board that has one of the older FT2232 JTAG interfaces, when I connect using OpenOCD I get a lot more output, specifically it auto-detects what device is being accessed.:
Code: Select all
However, when I am debugging on a new board with one of the TI ICDI interfaces I only get:Info : only one transport option; autoselect 'jtag'
adapter speed: 500 kHz
Info : device: 4 "2232C"
Info : deviceID: 67353817
Info : SerialNumber: 082106FCA
Info : Description: Stellaris Evaluation Board A
Info : clock speed 500 kHz
Info : JTAG tap: lm3s.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : lm3s.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection from 3332
Code: Select all
Any ideas?adapter speed: 1000 kHz
Info : clock speed 1000 kHz
Info : ICDI Firmware version: 8790
Info : lm3s.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection from 3332