To Laurent Gauch: Did you received my private email? Jiri Kubias
2009/9/17 Laurent Gauch <laurent.ga...@amontec.com> > Hi Jir(í Kubias, > > Good to know you resolved your problem using GDB / OpenOCD / Amontec > JTAGkey-2 for your lpc2378 board. > Also, thank you for giving the how you have resolved the issue. It is nice > for other users. > > (By the way, I double checked our Amontec email box, but I did not find any > email from you regarding driver troubles.) > Actually, we did not have published the new driver, since we are doing > Microsoft certification for our new driver. For now, Amontec Team gives the > new driver on demand. But we will updated Amontec JTAGkey Dongle Drivers > tomorrow (uncertified one). Please check tomorrow http://www.amontec.com . > The certified one (VISTA 64 bits) should come in the next 2 weeks. > > Regards, > Laurent Gauch > http://www.amontec.com > > Jir(í Kubias wrote: > >> Hi, >> I thought that this email didn't reach opnocd mailing list (I didnt >> recieve copy from mailing list). I solved my problem yesterday - the main >> problem was missconfigured GDB (it was configured only for i686-linux >> platform and not for arm-elf .... The second was enabled code compression - >> eclipse didn't survive this. Well now it works fine. >> >> I have troubles with the drivers provided on amontec web page - the >> windows driver is quied old (DriverVer=12/01/2005, taken from FTD2XX.inf), >> in linux I have the same problems so Im using the second driver usblib for >> ftdi chips. I reported this problem to amontec - but no response. >> >> Jirka >> >> >> >> 2009/9/17 Laurent Gauch <laurent.ga...@amontec.com <mailto: >> laurent.ga...@amontec.com>> >> >> > >> > 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 >> <http://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 <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 >> <mailto:Openocd-development@lists.berlios.de> >> https://lists.berlios.de/mailman/listinfo/openocd-development >> >> >> >> >> -- >> =================================================== >> Bc. Jiri Kubias >> Czech Technical University in Prague >> Faculty of Electrical Engineering >> dept. of Control Engineering >> Karlovo namesti 13/E, 121 35 Prague >> Czech Republic >> >> web page: http://dce.felk.cvut.cz >> e-mail: jiri.kub...@gmail.com <mailto:jiri.kub...@gmail.com> >> mobile: 777 974167 >> =================================================== >> > > -- =================================================== Bc. Jiri Kubias Czech Technical University in Prague Faculty of Electrical Engineering dept. of Control Engineering Karlovo namesti 13/E, 121 35 Prague Czech Republic web page: http://dce.felk.cvut.cz e-mail: jiri.kub...@gmail.com mobile: 777 974167 ===================================================
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
