I program a simple program on the board SAM3X-EK Board by using the build in
SAM-BA boot program.
No i could connect to the Cortex M3 JTAG tab. But the device is not
controllable.
:
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
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
Info : clock speed 500 kHz
Info : JTAG tap: sam3.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part:
0xba00, ver: 0x4)
Error: sam3.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: JTAG-DP STICKY ERROR
Error: MEM_AP_CSW 0x23000041, MEM_AP_TAR 0xd8c00000
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
Polling target failed, GDB will be halted. Polling again in 3100ms
Regard, Arnd
Am 05.12.2012 um 09:07 schrieb Freddie Chopin <[email protected]>:
> W dniu 2012-12-05 08:44, Andreas Fritiofson pisze:
>> You may be right, but then it sounds like a misfeature. Why shouldn't a
>> target specific behavior override the generic mechanism?
>
> It was like this when this cortex-m3 option was introduced, but
> fortunately it was changed, because then all targets used soft resets
> even if h/w reset was available, and that last one is always better
> (especially for targets where sysrstreq is not working and vectreset
> doesn't reset peripherals - like LPC17xx where you have to explicitly
> state the core clock to flash it). If user specifies that there is a
> reset than this reset should be used. cortex-m3 soft reset is defined in
> cortex-m3 target configs and there's really no point in editing this
> every time you change something...
>
> You'll probably be able to easily find the discussion about that thing
> back then - I think it all goes down to not-very-lucky design of OpenOCD
> where everything is imperative, while it would be better if it would
> work like that:
> - interface specifies what it supports (what reset signals it has)
> - target/board specifies what it supports (what resets are supported,
> what lines are routed and how, ...)
> - OpenOCD chooses the best possible combination (interface has 2 resets
> but target has only 1? use "srst_only" then)
> - user can optionally override that
>
> With current design (almost) no interface and no target config specifies
> resets as this wouldn't work as expected - users always have to specify
> them by hand and usability suffers... No one will change the fact that
> the most "user friendly" software is the one that doesn't need much
> configuration and OpenOCD is not among such programs.
>
> 4\/3!!
>
> ------------------------------------------------------------------------------
> 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
------------------------------------------------------------------------------
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
