Re: [OpenOCD-devel] Debugging LPC1768 with NGX USB => JTAG (FT2322)

[Jörg F. <tu...@gm...>]

Am 27.04.2013 07:44, schrieb rakesh ranjan:
> hardware setup: LPC1768 based board blueboard
> (http://shop.ngxtechnologies.com/product_info.php?cPath=21_33&products_id=97)
> 
> Debugger : USB=> JTAG ( FT2232) from NGX technologies.
> (http://shop.ngxtechnologies.com/product_info.php?cPath=26&products_id=30)
> 
> [...]
> Debug: 150 817 command.c:145 script_debug(): command - ocd_command
> ocd_command type ocd_adapter_khz 10
> Debug: 151 824 command.c:145 script_debug(): command - adapter_khz
> ocd_adapter_khz 10
> Debug: 153 829 core.c:1570 jtag_config_khz(): handle jtag khz
> Debug: 154 833 core.c:1537 adapter_khz_to_speed(): convert khz to
> interface specific speed value
> Debug: 155 839 core.c:1537 adapter_khz_to_speed(): convert khz to
> interface specific speed value
> User : 156 845 command.c:547 command_print(): 10 kHz

You usually want "adapter_khz 500" in your board specific .cfg file,
the LPC176x run with 4 MHz by default.

The 10 kHz in the default config is a workaround, in case somebody plays
whith the PLL and lowers the clock rate - the bootloader does, btw.

> invalid command name "speed"

The gdb command "monitor speed auto" does not exist.
Try "monitor adapter_khz 500".

> JTAG tap: lpc1768.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part:
> 0xba00, ver: 0x4)
> Only resetting the Cortex-M3 core, use a reset-init event handler to >
reset any peripherals

Check your "reset_config". "reset_config none" is a bad idea for this
MCU, because the LPC176x do not support "Sysresetreq". Without the RESET
pin you can only reset the Cortex M3 core but not the numerous
peripherials on the chip, including the clocks configuration for example.
A wrong clock configuration might lead to write failures when flashing
code memory.

> > step
> target not halted

Try "halt" or "reset halt".

HTH
Jörg Fischer