On 13/07/2023 23:06, Liviu Ionescu wrote:
On 13 Jul 2023, at 23:48, Tommy Murphy wrote:
I presume that the breakpoints used to implement semihosting (e.g. 0xBEAB for Cortex-M7)
do actually cause the target to go into debug halt for a period of time even if they're
subsequently automatically
> 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
> and I thought that perhaps OpenOCD can do it. Was I too optimistic?
To be fair, there is no clear evidence so far that the problem that you're
hitting here - with the SysTick handler stopping as if there was a breakpoint -
is the fault of OpenOCD and not, perhaps, a bug in the target Cortex-M7
Are you absolutely sure that the debugger connector is orientated correctly
with pin 1's matching?
This is an automated email from Gerrit.
"Erhan Kurubas " just uploaded a new patch set to
Gerrit, which you can find at https://review.openocd.org/c/openocd/+/7815
-- gerrit
commit ce35bc9067799c98c888d0d6c45b5b984307e7e6
Author: Erhan Kurubas
Date: Thu Jul 13 23:06:14 2023 +0200
target
> On 13 Jul 2023, at 23:48, Tommy Murphy wrote:
>
> I presume that the breakpoints used to implement semihosting (e.g. 0xBEAB for
> Cortex-M7) do actually cause the target to go into debug halt for a period of
> time even if they're subsequently automatically resumed as part of the
> semiho
Thank you for the input!
The target device is a KSZ8695X with a 20 pin ICE connector. It has its own
external power supply and the status lights are up. I tried unplugging the
cable from the target completely and running again, and got the same error.
The Olimex debuggers light stays solid yellow
> Error: JTAG scan chain interrogation failed: all ones
Almost certainly the target TDO is stuck at 1 for some reason, so you need to
check your target, debug connection, wiring etc.
What is the nature of your target device/board?
From: Abe Lapped
Sent: Thursday
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
>> BTW combining semihosting with interrupts is not a good practice anyway.
>> Except some basic tests the interrupts are unusable due
>> to giant latencies caused by debug halts.
> Hmmm... Can you be more specific on this? What halts do you mean? I
> definitely do not set any breakpoints in my
> On 13 Jul 2023, at 23:17, Michael Schwingen wrote:
>
> I would propose to add a switch to ignore breakpoints and automatically resume
Yes, this is a possible solution.
However I would like to clarify if OpenOCD is able to run in standalone
semihosting mode, in order to conveniently run un
On 13.07.23 20:30, Liviu Ionescu wrote:
On 13 Jul 2023, at 19:12, Liviu Ionescu wrote:
... change OpenOCD to resume it when running with semihosting enabled but
standalone (i.e. not in a debug session).
Question: what do you think should be a correct behaviour for OpenOCD when an
explicit
> On 13 Jul 2023, at 22:46, Tommy Murphy wrote:
>
> Even if all ports (GDB, Tcl, telnet) are disabled (and there is no pipe
> connection from GDB?) and the only commands used are passed from the OpenOCD
> command line directly or via scripts? Wouldn't that be a sort of "standalone"
> mode?
> On 13 Jul 2023, at 22:09, Tomas Vanek wrote:
>
> It should *NOT* resume. The main purpose of a breakpoint is to stop the
> execution.
Actually "to stop the execution **during a debug session**".
> Connecting OpenOCD to a target implies enabling the debug mode of the device
> so IMO there
> so IMO there is nothing like "standalone" mode.
Even if all ports (GDB, Tcl, telnet) are disabled (and there is no pipe
connection from GDB?) and the only commands used are passed from the OpenOCD
command line directly or via scripts? Wouldn't that be a sort of "standalone"
mode?
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
On 13/07/2023 20:30, Liviu Ionescu wrote:
On 13 Jul 2023, at 19:12, Liviu Ionescu wrote:
... change OpenOCD to resume it when running with semihosting enabled but
standalone (i.e. not in a debug session).
Question: what do you think should be a correct behaviour for OpenOCD when an
explici
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 13 Jul 2023, at 19:12, Liviu Ionescu wrote:
>
> ... change OpenOCD to resume it when running with semihosting enabled but
> standalone (i.e. not in a debug session).
Question: what do you think should be a correct behaviour for OpenOCD when an
explicit BKPT 0 (regular breakpoint) is en
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
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).
https://imgur.com/a/Rjl58i3
https://imgur.com/a/eb11sSZ
After restarting my computer (Windows 10 Ente
This is an automated email from Gerrit.
"Tim Newsome " just uploaded a new patch set to Gerrit, which
you can find at https://review.openocd.org/c/openocd/+/7814
-- gerrit
commit 23acdc9c21ee13cc4ad367998c9e607e7ac4461f
Author: eolson
Date: Thu Jun 22 13:02:21 2023 -0500
Add null pointe
This is an automated email from Gerrit.
"Tim Newsome " just uploaded a new patch set to Gerrit, which
you can find at https://review.openocd.org/c/openocd/+/7813
-- gerrit
commit 5cab0003bd9d9f0028a00c463d86f882d648de50
Author: Tim Newsome
Date: Thu Jul 13 09:38:44 2023 -0700
jtag/drive
I did some more tests, and exactly the same code runs just fine on Rapsberry
RP2040, STM NUCLEO-F411 and a board with STM32H743.
On STM32F767 the issue occurred in 2 of the 3 tests, in different locations at
different moments in time, differently on slow (RPI4) and fast (MacMini).
A simple loop
This is an automated email from Gerrit.
"Name of user not set " just uploaded a new
patch set to Gerrit, which you can find at
https://review.openocd.org/c/openocd/+/7812
-- gerrit
commit 35e3ca73024e9f79bc0cbc83417a799a83e95cd0
Author: Ahmed boughanmi
Date: Thu Jul 13 17:25:44 2023 +0200
This is an automated email from Gerrit.
"Steve Sims " just uploaded a new patch set to
Gerrit, which you can find at https://review.openocd.org/c/openocd/+/7792
-- gerrit
commit fcbb7557f1e235d118cda2117ee3d705abc57017
Author: Steve Sims
Date: Thu Jul 13 16:27:52 2023 +0100
Patch set 3
29 matches
Mail list logo
