Hi Alex, On Tue, May 17, 2011 at 8:11 PM, Austin, Alex <[email protected]> wrote: > I am attempting to use OpenOCD with a cellular chipset with an ARM11 and an > ARM7+DSP core. I can access it with the Lauterbach debugger, but I find the > interface very difficult to use and would prefer OpenOCD. > > It looks like some sort of TAP controller, perhaps like an OMAP3. Has anyone > seen anything like this? Any idea how to get past it? > > Upon a scan, OpenOCD shows me: > > alex@msp-clx-aaustin:~$ openocd -f interface/jtagkey2.cfg -c jtag_khz\ 10000 > Open On-Chip Debugger 0.5.0-dev-00219-g737c9b6-dirty (2010-05-06-14:21) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > 10000 kHz > Info : max TCK change to: 30000 kHz > Info : clock speed 10000 kHz > Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!! > Warn : AUTO auto0.tap - use "jtag newtap auto0 tap -expected-id 0x30180083 > ..." > Warn : AUTO auto0.tap - use "... -irlen 8" > Warn : gdb services need one or more targets defined > I'm just starting working on OpenOCD and not familiar with it, so I don't know if it has a command with similar functionality, but the detect command in UrJTAG might give you more information about the TAPs in your target if you have not tried it yet. After you know the TAPs in your target, you can create a config file for your target for OpenOCD.
Regards, Jie _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
