m: Abe Lapped
Sent: Tuesday 25 July 2023 20:09
To: Tommy Murphy ; mich...@schwingen.org
; Paul Fertser ;
dietmar@outlook.com ;
openocd-devel@lists.sourceforge.net
Subject: Re: Olimex ARM-USB-OCD-H Driver Issue
Understood, thank you. I'm now at a point where I can interact with the SOC and
w
Understood, thank you. I'm now at a point where I can interact with the SOC
and write to its memory using openOCD, but I can't see or interact with the
flash on the chip? Any idea how I would do this?
On Tue, 25 Jul 2023 at 13:07, Tommy Murphy wrote:
> Please attach/post logs rather than screens
Please attach/post logs rather than screenshots as not everybody can read the
latter easily. I also can't see your post on the mailing list archive so it may
have been blocked because of the images.
On 14.07.23 15:55, Abe Lapped wrote:
Good morning,
Thank you for this. I just checked the pin configuration and retried
on another board. The board is definitely powered on (the status
lights come on) and the cable orientation is correct, but I'm still
getting the same error... could it be so
: Abe Lapped ; openocd-devel@lists.sourceforge.net
; dietmar@outlook.com
; fercer...@gmail.com
Subject: Re: Olimex ARM-USB-OCD-H Driver Issue
What happens when you simply do the following - using the Olimex configuration
script already bundled with OpenOCD and not any custom scripts that you
Thank you for the suggestion. Just measured, and the input voltage (3.3V)
is correct!
On Fri, 14 Jul 2023 at 11:51, Paul Fertser wrote:
> On Fri, Jul 14, 2023 at 11:27:43AM -0400, Abe Lapped wrote:
> > Here is a shot of my pinout, if it helps:
> > [1]image.png
>
> Have you tried measuring the vo
What happens when you simply do the following - using the Olimex configuration
script already bundled with OpenOCD and not any custom scripts that you have
created yourself?
`openocd -f interface/ftdi/olimex-arm-usb-ocd-h.cfg`
On Fri, Jul 14, 2023 at 11:27:43AM -0400, Abe Lapped wrote:
> Here is a shot of my pinout, if it helps:
> [1]image.png
Have you tried measuring the voltage on pin 1 of the connector? It
should be Vcc from the target.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mai
Here is a shot of my pinout, if it helps:
[image: image.png]
On Fri, 14 Jul 2023 at 09:55, Abe Lapped wrote:
> Good morning,
>
> Thank you for this. I just checked the pin configuration and retried on
> another board. The board is definitely powered on (the status lights come
> on) and the cable
Good morning,
Thank you for this. I just checked the pin configuration and retried on
another board. The board is definitely powered on (the status lights come
on) and the cable orientation is correct, but I'm still getting the same
error... could it be something to do with my configuration files?
> I tried unplugging the cable from the target completely and running again,
> and got the same error.
That makes sense since TDO on the Olimex will most likely be pulled or floating
high by default so it'll be read as 1 when disconnected. The fact that it's
reading high when connected is the i
Are you absolutely sure that the debugger connector is orientated correctly
with pin 1's matching?
er...@gmail.com <
> fercer...@gmail.com>
> *Subject:* Re: Olimex ARM-USB-OCD-H Driver Issue
>
> Thank you all for your input. I've downloaded the xPack version and
> updated my drivers (hopefully correctly). Now, when I go to run it, I get
> an "all ones" error.
ent: Thursday, July 13, 2023 9:50:25 PM
To: Tommy Murphy ;
openocd-devel@lists.sourceforge.net ;
dietmar@outlook.com ; fercer...@gmail.com
Subject: Re: Olimex ARM-USB-OCD-H Driver Issue
Thank you all for your input. I've downloaded the xPack version and updated my
drivers (hopefully correct
Thank you all for your input. I've downloaded the xPack version and updated
my drivers (hopefully correctly). Now, when I go to run it, I get an "all
ones" error.
Here is my output:
$ ./openocd -f olimex-arm-usb-ocd-h.cfg -f ks869x.cfg
xPack Open On-Chip Debugger 0.12.0-01004-g9ea7f3d64-dirty (202
Zadig 2.5 is also outdated.
I would use the latest, 2.8.
And, as mentioned earlier, a much more up to date version of OpenOCD.
Note that if you're writing you own scripts then some commands may differ with
a later OpenOCD - e.g. `ftdi vid_pid` rather than the legacy `ftdi_vid_pid`
command althoug
Windows 10/11 w/zadig 2.5
Sent from my iPhone
> On Jul 13, 2023, at 2:25 PM, Paul Fertser wrote:
>
> On Thu, Jul 13, 2023 at 06:16:13PM +, Dietmar May wrote:
>> I’ve used zadig for ARM-USB-OCD-H. (At least for *that* probe), do
>> NOT install for BOTH interface 0 and 1 - ONLY device 0. Int
On Thu, Jul 13, 2023 at 06:16:13PM +, Dietmar May wrote:
> I’ve used zadig for ARM-USB-OCD-H. (At least for *that* probe), do
> NOT install for BOTH interface 0 and 1 - ONLY device 0. Interface 1
> is a standard FTDI comm port, which can be installed using drivers
> from FTDI’s website. You wou
> Please use current version of OpenOCD, not something from year 2015.
I'd second that! If you can't build it yourself or find another binary
distribution then you could try the xPack version:
* https://xpack.github.io/dev-tools/openocd/
* https://xpack.github.io/dev-tools/openocd/releases/
I’ve used zadig for ARM-USB-OCD-H. (At least for *that* probe), do NOT install
for BOTH interface 0 and 1 - ONLY device 0. Interface 1 is a standard FTDI comm
port, which can be installed using drivers from FTDI’s website. You would need
to specify the driver manually. Use the last option in the
Hi,
On Thu, Jul 13, 2023 at 01:46:04PM -0400, Abe Lapped wrote:
> I have recently purchased an Olimex ARM-USB-OCD-U debugger but am
> experiencing a
> driver issue. I used Zadig to install WinUSB (v6.1.7600.16385) drivers for
> ARM-USB-OCD-H (both interfaces 0 and 1).
I think README.Windows says
21 matches
Mail list logo
