Could you send me the config file you used ?

Thanks,
jesus

2009/4/8 Magnus Lundin <lun...@mlu.mine.nu>

> Hi,
>
> I have resently made some test on the same board but with a ft2232 based
> interface.
> The configuration that works best so far uses:
>
> #use combined on interfaces or targets that can't set TRST/SRST separately
> reset_config trst_and_srst srst_pulls_trst
> jtag_nsrst_delay 10
> jtag_khz 1000
>
> The LPC2129 based boards should work with the same config files.
>
> Regards,
> Magnus
>
> Jesus Sanchez-Palencia wrote:
> > Hey guys,
> >
> > I'm trying to "translate" and old config file for LPC-E2124 (Olimex),
> > because it has some deprecated functions. I'm sending attached both
> config
> > files, the old one and the one I'm working on right now.
> >
> > I've already managed to communicate with the board, but something still
> > seems to be wrong. This is my first experience with OpenOCD, but as soon
> as
> > this cfg file becames ready I intend to send it to your svn. (yes, I'll
> > clean it a little bit)
> >
> > So, I can start OpenOCD and can connect to its GDB server but at this
> point
> > I already have some warnings. If I give some "monitor step" or "monitor
> > resume" everything just go fine. I can even set a BP, with just some
> "data
> > abort" message. But if I try to do some "monitor reset [anything]" I have
> > some errors, and have to do a hard-reset at the board (reset button).
> >
> > Below are the messages from OpenOCD with the steps above mentioned. What
> do
> > you think ?!
> > Anything wrong with my new config file ?
> >
> >
> > ------------------------ CUT -----------------------------------------
> >
> > j...@andaluzia ~/dev/openocd/trunk/src $ sudo ./openocd -f
> > lpc2124+armjtag.cfg
> > Open On-Chip Debugger 1.0 (2009-04-06-19:24) svn:1435
> >
> >
> > BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
> >
> >
> > $URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $
> > jtag_speed: 0
> > Info : JTAG tap: lpc2124.cpu tap/device found: 0x4f1f0f0f (Manufacturer:
> > 0x787, Part: 0xf1f0, Version: 0x4)
> > Info : JTAG Tap/device matched
> > Warn : no tcl port specified, using default port 6666
> > Info : accepting 'gdb' connection from 0
> > target state: halted
> > target halted in Thumb state due to debug-request, current mode: System
> > cpsr: 0x600000ff pc: 0x00003e58
> > Warn : acknowledgment received, but no packet pending
> > Warn : memory read caused data abort (address: 0x08080808, size: 0x4,
> count:
> > 0x2)
> > Warn : memory read caused data abort (address: 0x08080808, size: 0x4,
> count:
> > 0x1)
> >
> >
> > target state: halted
> > target halted in Thumb state due to single-step, current mode: System
> > cpsr: 0x600000ff pc: 0x00003e5a
> > target state: halted
> > target halted in Thumb state due to single-step, current mode: System
> > cpsr: 0x800000ff pc: 0x00003e5c
> > Warn : memory read caused data abort (address: 0x20000000, size: 0x2,
> count:
> > 0x1)
> > breakpoint added at address 0x20000000
> >
> >
> > Info : JTAG tap: lpc2124.cpu tap/device found: 0x4f1f0f0f (Manufacturer:
> > 0x787, Part: 0xf1f0, Version: 0x4)
> > Info : JTAG Tap/device matched
> > Error: invalid mode value encountered
> > Error: cpsr contains invalid mode value - communication failure
> >
> >
> > ------------------------ CUT -----------------------------------------
> >
> >
> >
> >
> > Thanks in advance,
> > jesus
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Openocd-development mailing list
> > Openocd-development@lists.berlios.de
> > https://lists.berlios.de/mailman/listinfo/openocd-development
> >
>
> _______________________________________________
> Openocd-development mailing list
> Openocd-development@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/openocd-development
>
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to