On Sun, Dec 22, 2013 at 11:43:02AM +0100, axel wrote:
CPUTAPID is now correct. Furthermore I adjusted the -irlen to 3 and
-ircapture to 0x1 (seen in the appropriate BSDL file).
Even though the BSDL file says IR length is only three bits, it seems
wrong as ADIv5 mandates IR to be of at least 4
On Sun, Dec 22, 2013 at 03:37:33PM +0100, axel wrote:
My fault: JTAGSEL was high; I thought the JTAG is activated instead of
IO operation.
Now the original 'at91sam3nXX.cfg' is working. But the error:
Ok, nice. So it presents the usual Cortex-M ID when it's not in JTAG
Boundary Scan mode.
So I will check my board against the SAM3N00-EK. And there is a job for
my oscilloscope for signal quality.
All of these... work for tomorrow.
BTW: 'reset init' and 'reset halt' in the *.cfg didn't work, unknown
command :-(
NRST of my SAM3 is already connected with SRST
On 22.12.2013 16:59,
On Sun, Dec 22, 2013 at 06:14:04PM +0100, axel wrote:
BTW: 'reset init' and 'reset halt' in the *.cfg didn't work, unknown
command :-(
Wasn't supposed to be used in a config file. Either you perform them
manually (via telnet or gdb) or you add them after init command.
I'd appreciate it if you
Hi,
I tried to use a AT91SAM3N00A on openocd. A scan_chain brought:
_
Info : JTAG tap: at91sam3n.cpu tap/device found: 0x05b2e03f (mfg: 0x01f,
part: 0x5b2e, ver: 0x0)
Warn : JTAG tap: at91sam3n.cpu UNEXPECTED: 0x05b2e03f (mfg: 0x01f,
part: 0x5b2e, ver: 0x0)
Error:
