Doesn't http://openocd.zylin.com/#/c/4508/ make it clear that it never made it
at far as being merged? There was a Jenkins failure and a question posted by a
reviewer that was never answered.
From: Maximilian Gerhardt via OpenOCD-devel
Sent: Sunday, March 14, 20
Did you read this?
https://sourceforge.net/p/openocd/code/ci/master/tree/README.Windows
Do you need to build or can you use pre-built binaries from elsewhere - e.g.:
http://openocd.org/getting-openocd/
My personal preference when building is to use Liviu Ionescu's xPack Project
docker based bu
You need to enable that interface when configuring openocd before building it.
https://repo.or.cz/openocd.git/blob/0dd3b7fa6c7930446967772832a351e90c426d69:/configure.ac#l119
From: avinash chavan via OpenOCD-devel
Sent: Saturday, December 26, 2020 12:50:05 PM
To:
> But it might make sense to instead have this functionality in OpenOCD, so
> standard tools, such as gdb, can be used.
Do gcc/binutils/gdb even support Rabbit MCUs? I can't find any such support.
Adding support for Rabbit to openocd may make sense for other reasons but to
complement gcc/binuti
It's not stuck - it's waiting for a GDB debug connection!
---
** [tickets:#274] openocd error stmlink with stm32l053r8**
**Status:** new
**Milestone:** 0.9.0
**Labels:** stm32lx flash OpenOCD ST-LINK NRST signal
**Created:** Thu Jul 09, 2020 09:04 AM UTC by MURLIDHAR ROY
**Last Updated:** Thu
> openocd -f openocd.cfg -c "program test.bin exit 0x"
> works, that's a start :-)
> but can you still help me with the programmer getting accessible in the IDE?
Then that is an IDE issue and not an OpenOCD issue.
You really need to ask about the IDE issue on the appropriate forum.
---
Is Andries on Debian?
I didn't see that mentioned anywhere...
---
** [tickets:#258] sudo apt install openocd**
**Status:** new
**Milestone:** 0.9.0
**Labels:** openOCD arduino no port
**Created:** Wed Nov 20, 2019 12:22 PM UTC by Andries Oyens
**Last Updated:** Wed Nov 20, 2019 04:25 PM UTC
**
Apologies for the repeated replies above but I was getting bounces from the
mailing list address even though those replies obviously got through anyway
Are you sure that your user is a member of the plugdev group in order to have
non root/su access to the device? That's what the rule that yo
(first attempt to send bounced so trying again)
Did you reboot or manually trigger a reload of the udev rules files (udevadmin
trigger I think)?
I normally just reboot if I change the udev files.
If the rules are in force and the one that you cite is the correct one for your
programmer then open
Did you reboot or manually trigger a reload of the udev rules files (udevadmin
trigger I think)?
I normally just reboot if I change the udev files.
If the rules are in force and the one that you cite is the correct one for your
programmer then openocd should be able to use it when run in non root
Did you reboot or manually trigger a reload of the udev rules files (udevadmin
trigger I think)?
I normally just reboot if I change the udev files.
If the rules are in force and the one that you cite is the correct one for your
programmer then openocd should be able to use it when run in non root
For some reason repeated attempts to email a reply failed.
Anyway here is what I was trying to send...
Did you reboot or manually trigger a reload of the udev rules files (udevadmin
trigger I think)?
I normally just reboot if I change the udev files.
If the rules are in force and the one that yo
Doesn't look like there's any openocd udev rules file installed so?
You need a udev rule for your programmer to allow openocd non root/su access to
your programmer.
If this was working for you before but is no longer working on the same machine
then something obviously must've changed.
http://op
Normally inability to detect/use the programmer except in root/su mode
indicates a problem with the udev files. Are you sure that the relevant udev
files/rules are still installed on your machine? Is there a
/etc/udev/rules.d/xx-openocd.rules installed on your machine and does it
describe the A
I'll leave it to one of the openocd maintainers to make a call on this - i.e.
to close it as invalid or to propose that the variable should be explicitly
initialized to 0.
---
** [tickets:#256] `gdb_actual_connections` is never initialized?**
**Status:** new
**Milestone:** 0.9.0
**Created:**
IIRC the C language standard requires that global variables are automatically
initialized to 0 if not explicitly initialized. Personally I would prefer an
explicit init to 0 here just for clarity (e.g. to avoid the confusion caused in
this ticket).
This code obviously depends on the implicit in
> On my opinin, the way to solve this problem is send reset command after
> device connect
Isn't target/stm32f1x.cfg already doing a reset of the target early on?
https://repo.or.cz/openocd.git/blob/HEAD:/tcl/target/stm32f1x.cfg#l72
---
** [tickets:#199] Undefined msu state after reconnect**
Duplicates?
https://sourceforge.net/p/openocd/tickets/193/
https://sourceforge.net/p/openocd/tickets/194/
---
** [tickets:#195] Accessing CORTEX-M0+ via APB2AHB Bridge**
**Status:** new
**Milestone:** 0.9.0
**Created:** Mon Jul 16, 2018 08:39 AM UTC by SANDEEP BABU
**Last Updated:** Mon Jul 1
> Warn : Flash driver of stm32h7x.qspi does not support free_driver_priv()
Are you sure that you're using the latest openocd which DOES seem to support
free_driver_priv() for that flash device?
https://repo.or.cz/openocd.git/blob/HEAD:/src/flash/nor/stm32h7x.c#l1144
---
** [tickets:#211] Enab
Duplicate of https://sourceforge.net/p/openocd/tickets/207/ perhaps?
---
** [tickets:#202] Command 'echo' writes to stderr, and not to stdout, as stated
in the documentation.**
**Status:** new
**Milestone:** 0.9.0
**Created:** Thu Aug 16, 2018 09:33 AM UTC by rdiez
**Last Updated:** Thu Aug 16
Well it is covered here as mentioned previously...
http://openocd.org/doc-release/README.Windows
---
** [tickets:#214] Error: The specified debug interface was not found (ft2232)**
**Status:** closed
**Milestone:** 0.9.0
**Created:** Thu Dec 06, 2018 10:26 AM UTC by Dr. Peter Oehler
**Last
Apologies Paul bit just to wrap it up...
You don't have the correct driver installed.
You need to replace the windows default one with a suitable libusb/WinUsb one.
Zadig is a common way of doing that but if it doesn't work on vista (which is
obviously very old and arguably defunct) then you'll n
If you're still getting this error then there's almost certainly something
still wrong with the driver setup since OpenOCD is obviously not finding any
ftdi/oocdlink device. Have you checked Windows Device Manager to see how your
device is seen and configured etc?
Error: no device found
Error:
On Windows you'll probably need to install the WinUsb libusb drivers. Zadig is
the easiest way to do this in my experience.
---
** [tickets:#214] Error: The specified debug interface was not found (ft2232)**
**Status:** new
**Milestone:** 0.9.0
**Created:** Thu Dec 06, 2018 10:26 AM UTC by Dr.
FWIW I gave up building openocd on Windows/MinGW/MSYS/Cygwin ages ago and
nowadays instead use Liviu Ionescu's GNU MCU Eclipse Docker based scripts to
build it from Linux for Linux and Windows.
https://github.com/gnu-mcu-eclipse/openocd-build
By default it builds his repo sources but with small
Presumably if the QSPI is mapped into CODE space of the Cortex-M
(0x-0x1fff) then h/w BPs will be used automatically? H/w BPs will
ONLY work in CODE space on a Cortex-M.
Hope this helps.
---
** [tickets:#208] Open OCD for external qspi programming and debugging**
**Status:** close
Liviu's GNU MCU Eclipse scripts will build from his own repos by default but
with a small tweak to the scripts you can point it at your own repo or a
tarball of sources. So you probably want to git clone from the main openocd
development repo and then apply the patch, create a tarball of the sou
FWIW I find it easier to build openocd for windows (and linux) using the method
outlned here rather than Cygwin:
https://github.com/gnu-mcu-eclipse/openocd
https://gnu-mcu-eclipse.github.io/openocd/build-procedure/
Hope this helps.
---
** [tickets:#208] Open OCD for external qspi programmin
Thanks Andreas - I can see the ticket now that it's no longer "private".
---
** [tickets:#205] Olimex ARM-USB-OCD-H Debugger PXA Programming Issue**
**Status:** new
**Milestone:** 0.9.0
**Created:** Wed Aug 22, 2018 04:15 AM UTC by Madhusudhan H Krishnasetty
**Last Updated:** Tue Aug 28, 2018 0
When I click on the link for this issue I get "Forbidden - Sorry, the
permissions for this page don't allow you to access it."
I can see all other issues/tickets.
Any ideas why this one is restricted?
Thanks
From: Madhusudhan H Krishnasetty via OpenOCD-devel
Sent
Any chance the CPU is executing from zeroized or garbage memory on power on
reset thus causing the T bit to be cleared at some stage, and then a double
fault and lockup occurring?
However even if this was happening I would expect the debug connection and
reset init to get it back into a known go
Hi Tim - are you sure that openocd is necessarily fully ready to accept GDB
RSP connections on port (by default) by the time that this LOG_INFO
message is displayed? If it is then why does the original openocd code
(src/server/server.c:add_connection()) only display "accepting 'gdb'
conne
Just looking at the code here:
Would it be safe to wait for the "accepting '%s' connection on tcp/%s" style
messages before launching other software (e.g. gdb) which may then try to
connect to the relevant openocd service/port (e.g. gdb rsp on or whatever)?
I.e. once this message is display
Just wondering if anybody has had any further thoughts on this in the meantime?
In simple terms is there anyexisting mechanism whereby software launching
openocd can know that it is fully initialized and ready to accept connections
(in particular GDB Remote Serial Protocol connections) before la
34 matches
Mail list logo
