> > Hi, > Im newbie to debugging under linux at all. Im tying to make work openocd > 0.3.0 + jtagkey2 + gdb + eclipse working. However Im not sucessfull. I > found several problems: > > 1) Maybe this is not problem, but when i open opencd with jkagkey script and > lpc2378 (im using lpc2364 - config is wery similar) I get this output > Error: EmbeddedICE v7 handling might be broken > but everything seems that is working > > 2) but when i use eclipse with CDT pluguin from Zylin and configure GDB with > this init command; > target remote localhost:3333 > set mem inaccessible-by-default off > monitor halt > monitor arm7_9 dcc_downloads enable > monitor gdb_breakpoint_override hard > monitor arm7_9 fast_memory_access enable > monitor wait_halt > break main > continue > > It always fails see this log from openocd > > Open On-Chip Debugger 0.3.0-in-development (2009-09-16-11:44) svn:2714 > $URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ > For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS > jtag_nsrst_delay: 200 > jtag_ntrst_delay: 200 > Warn : use 'lpc2378.cpu' as target identifier, not '0' > 500 kHz > Info : max TCK change to: 30000 kHz > Info : clock speed 500 kHz > Info : JTAG tap: lpc2378.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: > 0xf1f0, ver: 0x4) > Error: EmbeddedICE v7 handling might be broken > target state: halted > target halted in ARM state due to breakpoint, current mode: Supervisor > cpsr: 0x20000013 pc: 0x00000238 > Info : accepting 'gdb' connection from 0 > Warn : acknowledgment received, but no packet pending > Warn : memory read caused data abort (address: 0x08000000, size: 0x4, count: > 0x2) > Warn : memory read caused data abort (address: 0x08000000, size: 0x4, count: > 0x1) > dcc downloads are enabled > force hard breakpoints > fast memory access is enabled > Info : dropped 'gdb' connection - error -400 > > the log from eclipse > > source .gdbinit > target remote localhost:3333 > 0x08000000 in ?? () > set mem inaccessible-by-default off > monitor halt > monitor arm7_9 dcc_downloads enable > dcc downloads are enabled > monitor gdb_breakpoint_override hard > force hard breakpoints > monitor arm7_9 fast_memory_access enable > fast memory access is enabled > monitor wait_halt > break main > Breakpoint 1 at 0x64c: file > /home/data/robot/eurobot/sysless-lpc21xx/app/test222/main.c, line 141. > Note: automatically using hardware breakpoints for read-only addresses. > continue > > So please help me. Im not sure if is not somethig wrong with eclipse, but is > wery hard to find wiking exaple for Amontec Jtagkey2 , the lastest openocd > and eclipse. > > OpenOCD - 0.3.0 svn build: 2741 > Eclipse 3.4.1 > GDB 6.8 > system Gentoo > > Jiri Kubias
The Amontec JTAGkey-2 is the new generation of Amontec JTAGkey Dongle Family. The main new features are : High-Speed / Hi-Speed USB 2.0 compliant / 30 MHz JTAG / RTCK support / auto-sense1.2V to 5.5V JTAG IOs voltage / 32 mA output drivers for all JTAG IOs / TVS protections on all IOs / Amontec JTAG hot-plug certified / USB plug-and-play/ 4 onboard LEDs for easy first-uses / http//www.amontec.com The Amontec JTAGkey-2 is supporting RTCK (return clock for adaptive TCK Frequency controlled by your Target itself ). RTCK feature makes the debug much more stable since the Target frequency could change at any time using a ARM -s processor. RTCK is a very nice feature allowing the Amontec JTAGkey-2 to be synchronized depending on the Target frequency (your LPC23xx). For the ARM processors, the RTCK is implemented for any -s version. Now, you should enable the rtck signal in your OpenOCD configuration file and try again. ... jtag_rtck ... Let us know your result enabling RTCK. If it is not better, try to add more delay for TRST and SRST ... Regards, Laurent Gauch http://www.amontec.com Note : please use last FTD2XX drivers. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
