Hi All,
> I'm hoping you can give me a hand here. I'm trying to debug a custom board
> (aka not a standard development board, etc) which has the EM357 chip. I'm
> using a Bus Blaster v3c as the OpenOCD interface, using the config file
> shown below.
>
> I'm new to OpenOCD, and -- unfortunately -- even after reading the docs I
> could find and some prior mailing list posts which looked related to EM357
> chips, I couldn't get it to work:
>
> $ openocd -f openocd.cfg
> Open On-Chip Debugger 0.5.0 (2011-12-03-10:15)
> Licensed under GNU GPL v2
> For bug reports, read
> http://openocd.berlios.de/doc/doxygen/bugs.html
> Info : only one transport option; autoselect 'jtag'
> 500 kHz
> adapter_nsrst_delay: 100
> jtag_ntrst_delay: 100
> cortex_m3 reset_config sysresetreq
> 500 kHz
> Info : max TCK change to: 30000 kHz
> Info : clock speed 500 kHz
> Error: JTAG scan chain interrogation failed: all ones
> Error: Check JTAG interface, timings, target power, etc.
> Error: Trying to use configured scan chain anyway...
> Error: em357.cpu: IR capture error; saw 0x0f not 0x01
> Warn : Bypassing JTAG setup events due to errors
> Warn : Invalid ACK 0x7 in JTAG-DP transaction
> Polling target failed, GDB will be halted. Polling again in 100ms
> Polling target failed, GDB will be halted. Polling again in 300ms
> Polling target failed, GDB will be halted. Polling again in 700ms
> Polling target failed, GDB will be halted. Polling again in 1500ms
> ...
>
> I'm connected to JRST, JTMS, JTDI, JTDO, JTCK on the EM357, in addition to
> having the Bus Blaster tied to GND and VREF (I think I have the right test
> point for this one).
>
> Here are my config files:
>
> $ cat busblaster.cfg
> # Bus Blaster
> #
> # http://dangerousprototypes.com/docs/Bus_Blaster
> #
>
> interface ft2232
> ft2232_device_desc "Dual RS232-HS"
> ft2232_layout jtagkey
> ft2232_vid_pid 0x0403 0x6010
>
> $ cat openocd.cfg
> source [find busblaster.cfg]
> set CHIPNAME em357
> source [find target/stm32f1x.cfg]
> jtag_khz 500
>
> As you can see, I've tried to follow ideas at
> http://comments.gmane.org/gmane.comp.debugging.openocd.devel/19498, and
> others -- but I'm not getting anywhere.
>
> Can anyone lend a hand?
>
> -Brian
>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
