Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

2018-02-24 Thread Michael Schwingen 
On 24.02.2018 15:06, jaymayn...@gmail.com wrote:
> The Olimex ARM-JTAG-SWD has a 27 ohm resistor in series with the SRST
> line. I’m using about a 3-inch ribbon cable between it and the board;
> the SWD adapter is plugged directly into the JTAG-TINY, as they recommend.

That sounds good. Anyway, TRST/SRST should not be that critical.

cu
Michael

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

2018-02-24 Thread jaymaynard 
The Olimex ARM-JTAG-SWD has a 27 ohm resistor in series with the SRST line.
I’m using about a 3-inch ribbon cable between it and the board; the SWD
adapter is plugged directly into the JTAG-TINY, as they recommend.


Jay Maynard, K5ZC
http://plus.google.com/+JayMaynard


2018-02-24 12:48:23 + Michael Schwingen  :

> On Sat, 24 Feb 2018 00:52:44 +0100
> Tomas Vanek via OpenOCD-devel 
> wrote:
>
> On 24.02.2018 0:04, Jay Maynard wrote:
> More important is a small series resistor (33 ohm) on SWD - ringing
> prevention. Again not necessary if the cable to adapter is short.
>
>
> However, "short" may mean "really short" - I had signal integrity
> trouble doing SWD on a STM32 using a busblaster (FT2232 - my old version
> of the PCB has no series resistors on board), with 15cm cable. Adding
> series resistors to SWD and SWCLK fixed that.
>
> cu
> Michael
>
> --
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot
> ___
> OpenOCD-devel mailing list
> OpenOCD-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openocd-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

2018-02-24 Thread Michael Schwingen 
On Sat, 24 Feb 2018 00:52:44 +0100
Tomas Vanek via OpenOCD-devel 
wrote:

> On 24.02.2018 0:04, Jay Maynard wrote:
> More important is a small series resistor (33 ohm) on SWD - ringing 
> prevention. Again not necessary if the cable to adapter is short.

However, "short" may mean "really short" - I had signal integrity
trouble doing SWD on a STM32 using a busblaster (FT2232 - my old version
of the PCB has no series resistors on board), with 15cm cable. Adding
series resistors to SWD and SWCLK fixed that.

cu
Michael

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

2018-02-23 Thread Tomas Vanek via OpenOCD-devel 

On 24.02.2018 0:04, Jay Maynard wrote:


With Paul’s help, I wiggled the SRST line from the console. It’s 
showing low pretty much no matter what I do.



Strange. If SRST were asserted why SWD fails randomly?


The SWD lines are pulled up to 3.3V (the same supply that powers the 
processor) by 100K resistors. That strikes me as an awfully high 
value. Too much? Should I try lowering it, to, say, 4.7K?


No, it's not necessary if not used in harsh environment. It's not a 
'working' pullup for OC drivers like in I2C.
The only reason is to prevent signals to roam when not driven - when 
adapter is not connected or inactive.
More important is a small series resistor (33 ohm) on SWD - ringing 
prevention. Again not necessary if the cable to adapter is short.


Did you try to change adapter_khz? I would test 100 and 3000 kHz.
Did you checked all supply pins?

Tom


*From:*Tomas Vanek [mailto:tom_...@users.sourceforge.net]
*Sent:* Friday, February 23, 2018 4:38 PM
*To:* Jay Maynard 
*Cc:* openocd-devel@lists.sourceforge.net
*Subject:* Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete 
at startup


I connected my custom SAME70 board to a FT2232 based adapter just to 
make sure that current git master works.

It does. See attached log in -d4 level as you used.

There must be some electrical problem in SWD signals, grounding or supply.

Tom

On 23.02.2018 23:06, Jay Maynard wrote:

Apologies for the triple post. Can I drop an anvil on Sourceforge now?

Anyway, a couple of updates since that was written:

 1. I tried setting the bits in the write command to 0. Didn’t
change the result.
 2. A scope on the SWD data line shows nice clean square waves for
the signal, so that much is good electrically, at least.

I have a debug log from someone using a SAME70 Xplained
development board, but it uses the CMSIS-DAP debugger interface.
I’d prefer not to buy another debugger dongle, but I will if I
have to. One weisenheimer suggested I get an Atmel-ICE while it’s
on sale for 50% off ($65 for the kit). Anyone out there using a
SAME70 that’s **not** on the Xplained board?

*From:* Jay Maynard [mailto:jmayn...@kahlerautomation.com]
*Sent:* Friday, February 23, 2018 3:28 PM
*To:* openocd-devel@lists.sourceforge.net
<mailto:openocd-devel@lists.sourceforge.net>
*Subject:* [OpenOCD-devel] Atmel ATSAME70 examination incomplete
at startup

I’m trying to get an Atmel ATSAME70Q20A working with OpenOCD. I
have an Olimex JTAG-TINY and ARM-JTAG-SWD connected, and the
system works with our previous board running an AT91SAM7X. This is
a new board design, so there may be a hardware issue. I’ve tried
both the 0.10.0 distribution release and the tip of the git
repository tree built today (from the Czech mirror, since
Sourceforge seems not to have git access running yet).

The results vary some between runs. Sometimes, it doesn’t power up
the debug domain (see https://pastebin.com/NHXavQQL for an
example). Other times, it gets the debug domain powered up, but
can’t find the AHB-AP (see https://pastebin.com/X4XeFdam ). Still
others, it finds the AHB-AP, but then gets a fault trying to write
to it (see https://pastebin.com/KQtpF537 ). The last case, at
least, seems to have a problem: two bits are being written as 1 to
a register that the architecture defines as should be zero.

I’ve spent some time online on the IRC channel trying to get this
running with the help of some folks there, but no luck. They
suggested I ask you folks. Any ideas?

Jay Maynard | *Software Engineer*

Kahler Automation<http://www.kahlerautomation.com/>| 808
Timberlake Road, Fairmont, MN 56031 | Main: 507-235-6648

jmayn...@kahlerautomation.com <mailto:jmayn...@kahlerautomation.com>

/The information in this communication, including any attachments,
is intended only for the person or entity to which it is addressed
and may contain confidential, proprietary, and/or privileged
material. Any review, retransmission, dissemination or other use
of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the
sender and delete the material from all computers./





--

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org!http://sdm.link/slashdot




___

OpenOCD-devel mailing list

OpenOCD-devel@lists.sourceforge.net
<mailto:OpenOCD-devel@lists.sourceforge.net>

https://lists.sourceforge.net/lists/listinfo/openocd-devel



--
Check out the

Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

2018-02-23 Thread Jay Maynard 
With Paul's help, I wiggled the SRST line from the console. It's showing low 
pretty much no matter what I do.

The SWD lines are pulled up to 3.3V (the same supply that powers the processor) 
by 100K resistors. That strikes me as an awfully high value. Too much? Should I 
try lowering it, to, say, 4.7K?

From: Tomas Vanek [mailto:tom_...@users.sourceforge.net]
Sent: Friday, February 23, 2018 4:38 PM
To: Jay Maynard 
Cc: openocd-devel@lists.sourceforge.net
Subject: Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

I connected my custom SAME70 board to a FT2232 based adapter just to make sure 
that current git master works.
It does. See attached log in -d4 level as you used.

There must be some electrical problem in SWD signals, grounding or supply.

Tom

On 23.02.2018 23:06, Jay Maynard wrote:
Apologies for the triple post. Can I drop an anvil on Sourceforge now?

Anyway, a couple of updates since that was written:

  1.  I tried setting the bits in the write command to 0. Didn't change the 
result.
  2.  A scope on the SWD data line shows nice clean square waves for the 
signal, so that much is good electrically, at least.

I have a debug log from someone using a SAME70 Xplained development board, but 
it uses the CMSIS-DAP debugger interface. I'd prefer not to buy another 
debugger dongle, but I will if I have to. One weisenheimer suggested I get an 
Atmel-ICE while it's on sale for 50% off ($65 for the kit). Anyone out there 
using a SAME70 that's *not* on the Xplained board?

From: Jay Maynard [mailto:jmayn...@kahlerautomation.com]
Sent: Friday, February 23, 2018 3:28 PM
To: 
openocd-devel@lists.sourceforge.net<mailto:openocd-devel@lists.sourceforge.net>
Subject: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

I'm trying to get an Atmel ATSAME70Q20A working with OpenOCD. I have an Olimex 
JTAG-TINY and ARM-JTAG-SWD connected, and the system works with our previous 
board running an AT91SAM7X. This is a new board design, so there may be a 
hardware issue. I've tried both the 0.10.0 distribution release and the tip of 
the git repository tree built today (from the Czech mirror, since Sourceforge 
seems not to have git access running yet).

The results vary some between runs. Sometimes, it doesn't power up the debug 
domain (see https://pastebin.com/NHXavQQL for an example). Other times, it gets 
the debug domain powered up, but can't find the AHB-AP (see 
https://pastebin.com/X4XeFdam ). Still others, it finds the AHB-AP, but then 
gets a fault trying to write to it (see https://pastebin.com/KQtpF537 ). The 
last case, at least, seems to have a problem: two bits are being written as 1 
to a register that the architecture defines as should be zero.

I've spent some time online on the IRC channel trying to get this running with 
the help of some folks there, but no luck. They suggested I ask you folks. Any 
ideas?



Jay Maynard | Software Engineer
Kahler Automation<http://www.kahlerautomation.com/> | 808 Timberlake Road, 
Fairmont, MN 56031 | Main: 507-235-6648
jmayn...@kahlerautomation.com<mailto:jmayn...@kahlerautomation.com>

The information in this communication, including any attachments, is intended 
only for the person or entity to which it is addressed and may contain 
confidential, proprietary, and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in 
reliance upon, this information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, please contact the 
sender and delete the material from all computers.





--

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot




___

OpenOCD-devel mailing list

OpenOCD-devel@lists.sourceforge.net<mailto:OpenOCD-devel@lists.sourceforge.net>

https://lists.sourceforge.net/lists/listinfo/openocd-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

2018-02-23 Thread Tomas Vanek via OpenOCD-devel 
I connected my custom SAME70 board to a FT2232 based adapter just to 
make sure that current git master works.

It does. See attached log in -d4 level as you used.

There must be some electrical problem in SWD signals, grounding or supply.

Tom

On 23.02.2018 23:06, Jay Maynard wrote:


Apologies for the triple post. Can I drop an anvil on Sourceforge now?

Anyway, a couple of updates since that was written:

 1. I tried setting the bits in the write command to 0. Didn’t change
the result.
 2. A scope on the SWD data line shows nice clean square waves for the
signal, so that much is good electrically, at least.

I have a debug log from someone using a SAME70 Xplained development 
board, but it uses the CMSIS-DAP debugger interface. I’d prefer not to 
buy another debugger dongle, but I will if I have to. One weisenheimer 
suggested I get an Atmel-ICE while it’s on sale for 50% off ($65 for 
the kit). Anyone out there using a SAME70 that’s **not** on the 
Xplained board?


*From:* Jay Maynard [mailto:jmayn...@kahlerautomation.com]
*Sent:* Friday, February 23, 2018 3:28 PM
*To:* openocd-devel@lists.sourceforge.net
*Subject:* [OpenOCD-devel] Atmel ATSAME70 examination incomplete at 
startup


I’m trying to get an Atmel ATSAME70Q20A working with OpenOCD. I have 
an Olimex JTAG-TINY and ARM-JTAG-SWD connected, and the system works 
with our previous board running an AT91SAM7X. This is a new board 
design, so there may be a hardware issue. I’ve tried both the 0.10.0 
distribution release and the tip of the git repository tree built 
today (from the Czech mirror, since Sourceforge seems not to have git 
access running yet).


The results vary some between runs. Sometimes, it doesn’t power up the 
debug domain (see https://pastebin.com/NHXavQQL for an example). Other 
times, it gets the debug domain powered up, but can’t find the AHB-AP 
(see https://pastebin.com/X4XeFdam ). Still others, it finds the 
AHB-AP, but then gets a fault trying to write to it (see 
https://pastebin.com/KQtpF537 ). The last case, at least, seems to 
have a problem: two bits are being written as 1 to a register that the 
architecture defines as should be zero.


I’ve spent some time online on the IRC channel trying to get this 
running with the help of some folks there, but no luck. They suggested 
I ask you folks. Any ideas?


Jay Maynard| *Software Engineer*

Kahler Automation| 808 Timberlake 
Road, Fairmont, MN 56031 | Main: 507-235-6648


jmayn...@kahlerautomation.com __

/The information in this communication, including any attachments, is 
intended only for the person or entity to which it is addressed and 
may contain confidential, proprietary, and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of 
any action in reliance upon, this information by persons or entities 
other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from all 
computers./




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel


Open On-Chip Debugger 0.10.0+dev-00310-g58c3ebb-dirty (2018-02-23-22:49)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
User : 13 7 command.c:544 command_print(): debug_level: 4
Debug: 14 8 options.c:184 add_default_dirs(): bindir=/usr/local/bin
Debug: 15 8 options.c:185 add_default_dirs(): pkgdatadir=/usr/local/share/openocd
Debug: 16 8 options.c:186 add_default_dirs(): exepath=/home/vanekt/openocd/src
Debug: 17 8 options.c:187 add_default_dirs(): bin2data=../share/openocd
Debug: 18 8 configuration.c:42 add_script_search_dir(): adding /ssdh/vanekt/.openocd
Debug: 19 8 configuration.c:42 add_script_search_dir(): adding /home/vanekt/openocd/src/../share/openocd/site
Debug: 20 8 configuration.c:42 add_script_search_dir(): adding /home/vanekt/openocd/src/../share/openocd/scripts
Debug: 21 8 configuration.c:82 find_file(): found openocd.cfg
Debug: 22 8 command.c:143 script_debug(): command - ocd_command ocd_command type ocd_interface ftdi
Debug: 23 8 command.c:143 script_debug(): command - interface ocd_interface ftdi
Debug: 25 8 command.c:364 register_command_handler(): registering 'ocd_ftdi_device_desc'...
Debug: 26 8 command.c:364 register_command_handler(): registering 'ocd_ftdi_serial'...
Debug: 27 8 command.c:364 register_command_handler(): registering 'ocd_ftdi_location'...
Debug: 28 9 command.c:364 register_command_handler(): registering 'ocd_ftdi_channel'...
Debug: 29 9 command.c:364 register_command_handler(): registering 'ocd_ftdi_layout_init'...
Debug: 30 9 command.c:364

Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

2018-02-23 Thread Jay Maynard 
Apologies for the triple post. Can I drop an anvil on Sourceforge now?

Anyway, a couple of updates since that was written:

  1.  I tried setting the bits in the write command to 0. Didn't change the 
result.
  2.  A scope on the SWD data line shows nice clean square waves for the 
signal, so that much is good electrically, at least.

I have a debug log from someone using a SAME70 Xplained development board, but 
it uses the CMSIS-DAP debugger interface. I'd prefer not to buy another 
debugger dongle, but I will if I have to. One weisenheimer suggested I get an 
Atmel-ICE while it's on sale for 50% off ($65 for the kit). Anyone out there 
using a SAME70 that's *not* on the Xplained board?

From: Jay Maynard [mailto:jmayn...@kahlerautomation.com]
Sent: Friday, February 23, 2018 3:28 PM
To: openocd-devel@lists.sourceforge.net
Subject: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

I'm trying to get an Atmel ATSAME70Q20A working with OpenOCD. I have an Olimex 
JTAG-TINY and ARM-JTAG-SWD connected, and the system works with our previous 
board running an AT91SAM7X. This is a new board design, so there may be a 
hardware issue. I've tried both the 0.10.0 distribution release and the tip of 
the git repository tree built today (from the Czech mirror, since Sourceforge 
seems not to have git access running yet).

The results vary some between runs. Sometimes, it doesn't power up the debug 
domain (see https://pastebin.com/NHXavQQL for an example). Other times, it gets 
the debug domain powered up, but can't find the AHB-AP (see 
https://pastebin.com/X4XeFdam ). Still others, it finds the AHB-AP, but then 
gets a fault trying to write to it (see https://pastebin.com/KQtpF537 ). The 
last case, at least, seems to have a problem: two bits are being written as 1 
to a register that the architecture defines as should be zero.

I've spent some time online on the IRC channel trying to get this running with 
the help of some folks there, but no luck. They suggested I ask you folks. Any 
ideas?



Jay Maynard | Software Engineer
Kahler Automation | 808 Timberlake Road, 
Fairmont, MN 56031 | Main: 507-235-6648
jmayn...@kahlerautomation.com

The information in this communication, including any attachments, is intended 
only for the person or entity to which it is addressed and may contain 
confidential, proprietary, and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in 
reliance upon, this information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, please contact the 
sender and delete the material from all computers.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel