On Tue, Dec 4, 2012 at 8:55 PM, Arnd Begemann
<[email protected]>wrote:
> Hello,
>
> i still can get not connected to my Atmel SAM3X-EK (at91sam3x8h ES2) with
> my Olimex ARM-USB-OCD-H.
> At the same time i have no problem to debug board with other sam3 MCUs
> (SAM3U-EK, olimex SAM3-H256)
>
Then it sounds like an issue with your board or wiring. Have you tried
other software to determine that is is an OpenOCD problem?
Perhaps some code on the target is disabling jtag (pin config, sleep mode)
before OpenOCD has a chance to take control.
I use the latest GIT Master-Branch version.
>
> Open On-Chip Debugger 0.7.0-dev-00095-g27ad96e (2012-12-04-20:08)
> Licensed under GNU GPL v2
> For bug reports, read
> http://openocd.sourceforge.net/doc/doxygen/bugs.html
> Info : only one transport option; autoselect 'jtag'
> srst_only separate srst_gates_jtag srst_open_drain
>
Is the gating required for this chip family? That makes it harder to
connect under reset to avoid the previous.
> adapter speed: 500 kHz
> adapter_nsrst_delay: 100
> jtag_ntrst_delay: 100
> cortex_m3 reset_config sysresetreq
> srst_only separate srst_gates_jtag srst_open_drain
> cortex_m3 reset_config sysresetreq
>
Try with hard srst.
> Info : clock speed 500 kHz
>
Try lower clock.
> Error: JTAG scan chain interrogation failed: all ones
> Error: Check JTAG interface, timings, target power, etc.
>
Do this. Also this isn't the same error as in your last mail. What's
changed?
/Andreas
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
