On Wed, Nov 05, 2025 at 10:57:53AM -0000, Mark W wrote: How did you route around it if you're talking about the USB hub integrated on RaspberryPi 5 board? First of all, it's not a full speed hub there (so the forum thread doesn't apply), second, as seen in doc/usb_adapters/stlink/0483_3757_stlinkv3pwr.txt it's a high speed device so no translation is needed in any case. Are you connecting it via an additional full speed hub? It's a rPi CM5, with the TI USB hub on the parent PCB. I understand how...
On Wed, Nov 05, 2025 at 04:36:11AM -0000, Mark W wrote: This problem appears to be caused by a TI UBS hub chip. [1]https://forums.raspberrypi.com/viewtopic.php?t=246248 Hm, but this whole forum discussion doesn't seem to be related, and it's all strange. They reference a forum post on TI E2E that confirms that a certain USB hub model is full speed so naturally it doesn't have any TT (transaction translators) from full/low speed to high speed since it doesn't support any high speed connections at...
Hi Mark! On Tue, Nov 04, 2025 at 07:01:00AM -0000, Mark W wrote: I'm attempting to use openocd to connect to a STLink V3Mods using a Raspberry Pi 5 (arm64) host. I've built OpenOCD on the host using the cloned master repo from [2]https://github.com/openocd-org/openocd. As im guessing this could be libusb related, ive tried the os repo version of libusb, and also built libusb from the github master. The errors i see are (libusb also has debug output enabled): ... Debug: 126 4 stlink_usb.c:3744 stlink_open():...
Hi, On Mon, Sep 29, 2025 at 05:21:32PM -0000, Allan Macdonald wrote: [1][tickets:#459] Unable to Access openocd.org from Ubuntu 22.04LTS with Firefox That is a strange one indeed. If it's consistent I suggest you use Firefox "developer tools" network tab and save all the relevant information about what happens with what request. Also you can copy the request as cURL and compare the result by trying it in the command line. In general please keep in mind that openocd.org is hosted by SF.net themselves,...
Looks totally unrelated to me. You're using debug adapter which is not supported in upstream OpenOCD at all and it's unclear what "sdi" transport is. I suggest you ask whomever provides that "Open On-Chip Debugger 0.11.0+dev-02415-gfad123a16-dirty (2023-05-05-13:43)" fork (WCH?), I doubt anyone here in upstream has any idea about it.
Fixed the issue of incorrect detection of JEDEC bank 16 manufacturers
Hello, Thank you for the patch. Please consider sending it using the established procedure to the OpenOCD Gerrit instance as described by HACKING document. OpenOCD maintainers do not normally handle "merge requests" sent via SF.net, sorry.
jep106: update to revision JEP106BM Jun 2025
Hello, Thank you for the patch indeed. However OpenOCD code review normally happens on project Gerrit instance, can you please resubmit it there following procedure described in HACKING please?
so you recommend not to update the OpenOCD version at the very beginning, but first try to add { } to line 37, right? Updating won't help for sure. Downgrading might but why bother if it's an easy fix. Also whomever is providing that script should be made aware that they should stick to using all the config files that come with OpenOCD, not ship their own.
On Wed, Mar 05, 2025 at 11:30:39PM -0000, Krzysztof Kowalskk wrote: hello I need help, I want to make a copy of the display memory so that I can flash it later of the Ninebot ZT3 D Pro scooter, after clicking on the Dump_ram file I get this error Basically it complaints about using old "expr" syntax, it should look like expr {($old & ~$clearbits) | $setbits} notice expr here has just one argument, and in the older version it was OK to omit the {} braces, now it's not, so just go to that file to line...
On Wed, Mar 05, 2025 at 11:30:39PM -0000, Krzysztof Kowalskk wrote: hello I need help, I want to make a copy of the display memory so that I can flash it later of the Ninebot ZT3 D Pro scooter, after clicking on the Dump_ram file I get this error, I use Windows 10 and ST Link V2, of course I installed the driver for St Link by Zadig I am sending a screenshot, I don't know what I'm doing wrong, what should I do next? please help me 🙏 The script assumes running on much /older/ OpenOCD version. Where...
On Fri, Oct 11, 2024 at 07:44:16PM -0000, Tommy Murphy wrote: Yes - Microchip use a custom(ised) version of OpenOCD, I can't see that the sources/changes were ever published, and you will probably have to contact Microchip support for help with problems like this. Good luck! Also Microchip seems to be violating GPL which is illegal and offensive. I suggest you request full corresponding source code for their OpenOCD fork from them, there's a legal obligation to provide it. Linking with proprietary...
On Tue, Sep 24, 2024 at 01:25:01PM -0000, Antonio Borneo wrote: No big problems for the moment, but if in the future we get other files without any ASCII character in the name, I will be lost. Good point. But is using a pointer to copy it from e.g. "ls" output not a comfortable option? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercerpav@gmail.com
Hey Tommy, I want to echo your statements and probably add a bit more clarification. I was the one who added some non-ASCII file names and I still think it was a good idea. All the other targets are using their official names, so why make an exception for those having non-Latin letters? Single-byte encodings are the memories from the past by now, so what else would be a solid technical reason for that? On Tue, Sep 24, 2024 at 07:28:26AM +0000, Tommy Murphy wrote: I remember a few such filenames in...
Hi, This doesn't look like a bug. On Sun, Sep 22, 2024 at 05:14:23AM -0000, navysummer wrote: Error: The specified debug interface was not found (hla), ... source [find interface/stlink.cfg] source [find target/stm32f1x.cfg] openocd version:0.12.0+dev-01703-ge09bb72da Looks like you configured the binary without having libusb-1.0 development files, please install them and re-run configure and make. os:linux Linux is the name of the kernel. Your OS might be a variant of GNU/Linux. -- Be free, use...
net: socat: add option user
openocd: update to 0.11.0
openocd: update to 0.11.0-rc1; add libgpiod dep; always depend on USB libs
openocd: update to current master, allow building without USB
strongswan: allow to specify per-connection reqid with UCI
openocd: bump version to 0.10.0
Hi, Discovering the syntax to use 'jtag drscan' is not super intuitive : jtag drscan wrong # args: should be "jtag drscan wrong arguments" I hope https://review.openocd.org/c/openocd/+/7652 and https://review.openocd.org/c/openocd/+/7653 help.
On Fri, Apr 28, 2023 at 09:07:14PM -0000, fenugrec wrote: jtag drscan auto0.tap 32 1 Connection closed by foreign host. openocd: src/jtag/drivers/driver.c:166: interface_jtag_add_dr_scan: Assertion `field == out_fields + scan->num_fields' failed. Aborted (core dumped) Should be handled by https://review.openocd.org/c/openocd/+/7654
Hi, jtag drscan auto0.tap 32 1 Connection closed by foreign host. openocd: src/jtag/drivers/driver.c:166: interface_jtag_add_dr_scan: Assertion `field == out_fields + scan->num_fields' failed. This happens because basically all taps are in BYPASS by default, and before manual "drscan" command you naturally need to do the appropriate "irscan" on the same tap (as all DR operations are current instruction-specific). Guess we should introduce a special error message for the case.
On Thu, Apr 20, 2023 at 02:14:24PM -0000, Kristof Mulier wrote: (Paul Fertser) Have you tried using stlink-dap.cfg instead? Yes, we tried that today as well. No effect. Can you please add -d3 log with stlink-dap attempt? Another idea is to try using "reset halt; flash write_image erase ..." instead to see if it might be higher frequency or something else in the reset-init handler that makes the difference. Another thing to try would be using an external swd adapter.
Hi, On Wed, Mar 15, 2023 at 02:30:07PM -0000, Maximilian Gerhardt wrote: Currently, the Dialog DA1469x is unsupported in OpenOCD. Only the proprietary JLinkExe can connect it. I want to be able to use OpenOCD and other debug adapters. Do you also hope to be able to flash this target? As that would require developing a dedicated flash driver. OpenOCD fails at one of the very first steps, which is in the SWD protocol to do a LINERESET followed by the JTAG->SWD switch sequence, a LINERESET again and...
Restore normal development cycle
The openocd-0.12.0 release
configure.ac: fix check for jimtcl submodule
Hi, On Thu, Dec 29, 2022 at 02:25:23PM -0000, Ashi Gupta wrote: I am working on creating a custom JTAG driver for my custom interface. I am ... You have already asked about it in https://sourceforge.net/p/openocd/tickets/374/ . The answer is still the same. And if you plan to violate GPL then you shouldn't expect any support at all. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercerpav@gmail.com
Restore +dev suffix
The openocd-0.12.0-rc3 release candidate
How to add a new JTAG driver support in openocd
Hello, I have created my driver DLL Unless you are releasing source code of that DLL under a GPL-compatible licence you are NOT allowed to distribute OpenOCD that's using it. Please keep that in mind and respect the Copyright law. Regarding your questions, this ticketing system is not a support forum, please write to the devel mailing list instead.
Hello, I have created my driver DLL Unless you are releasing source code of that DLL under a GPL-compatible licence you are NOT allowed to distribute OpenOCD that's using it. Please keep that in mind and respect the Copyright law. Regarding your questions, this ticketing system is not a support forum, please write to the devel mailing list instead.
added sam21 seeeduino xiao board
Improved setup of CPUTAPID for STM32 configuration.
Hello, Thank you for your contribution. The OpenOCD project maintainers are using Gerrit-based workflow to process patches, please see HACKING for detailed instructions. If in doubt, please feel free to ask on the mailing list or the IRC. I'm closing this "merge request" in an anticipation that you will resubmit to Gerrit.
Adding board config for stm32g4 discovery
Enable FreeRTOS integration for Arm chips with FP5
Bug fix for XSDR handling in src/xsvf/xsvf.c
Hello, Thank you for your contribution. The OpenOCD project maintainers are using Gerrit-based workflow to process patches, please see HACKING for detailed instructions. If in doubt, please feel free to ask on the mailing list or the IRC. I'm closing this "merge request" in an anticipation that you will resubmit to Gerrit.
Hello, Thank you for your contribution. The OpenOCD project maintainers are using Gerrit-based workflow to process patches, please see HACKING for detailed instructions. If in doubt, please feel free to ask on the mailing list or the IRC. I'm closing this "merge request" in an anticipation that you will resubmit to Gerrit.
Hello, Thank you for your contribution. The OpenOCD project maintainers are using Gerrit-based workflow to process patches, please see HACKING for detailed instructions. If in doubt, please feel free to ask on the mailing list or the IRC. I'm closing this "merge request" in an anticipation that you will resubmit to Gerrit.
Hello, Thank you for your contribution. The OpenOCD project maintainers are using Gerrit-based workflow to process patches, please see HACKING for detailed instructions. If in doubt, please feel free to ask on the mailing list or the IRC. I'm closing this "merge request" in an anticipation that you will resubmit to Gerrit.
MT7688 and Allwinner H2+/H3/H5/H6/H616 bitbang support (Orange Pi and Onion Omega2)
Hello, Thank you for your contribution. The OpenOCD project maintainers are using Gerrit-based workflow to process patches, please see HACKING for detailed instructions. If in doubt, please feel free to ask on the mailing list or the IRC. I'm closing this "merge request" in an anticipation that you will resubmit to Gerrit.
Added revision 1.1 silicon for STM32WLx
Hello, Thank you for your contribution. The OpenOCD project maintainers are using Gerrit-based workflow to process patches, please see HACKING for detailed instructions. If in doubt, please feel free to ask on the mailing list or the IRC. I'm closing this "merge request" in an anticipation that you will resubmit to Gerrit.
Support for DirtyJTAG probes
Hello, Thank you for your contribution. The OpenOCD project maintainers are using Gerrit-based workflow to process patches, please see HACKING for detailed instructions. I also noticed that you're sending many commits for support of a single feature; please stash them into few (probably just one) isolated changes instead (git rebase -i would come handy there), as the upstream is not interested in your development history. If in doubt, please feel free to ask on the mailing list or the IRC. I'm closing...
Restore +dev suffix
The openocd-0.12.0-rc2 release candidate
Restore +dev suffix
The openocd-0.12.0-rc1 release candidate
Hi, On Wed, Jul 13, 2022 at 01:04:07PM -0000, Matei Barbu wrote: I would ignore the error messages, but gdb fails to run correctly: Reading symbols from ../../target/thumbv7em-none-eabi/release/microbit_v2.elf... (gdb) target extended-remote localhost:3333 Remote debugging using localhost:3333 0x0001ad90 in ?? () What's not correct here? Are you not able to use "load" to flash this target at that point?
On Thu, Mar 17, 2022 at 03:43:46PM -0000, Andrew Eidsness wrote: I think that the stellaris configuration is for the on-board ICDI which is accessible over the board's serial port. I'm experimenting with using an external one. There are alot of good examples in that folder though. I might start with the stellaris one, then see what else I can do. All configs in target/ directory are target configs, they do not include the on-board ICDI or other on-board adapters. Stellaris is the name of the original...
On Thu, Mar 17, 2022 at 11:27:23AM -0000, Andrew Eidsness wrote: Ah, thanks! I don't see a target config for this chip, but I think I can figure that out. In board/ti_ek-tm4c1294xl.cfg you can see it's just sourcing target/stellaris.cfg . This ticket can probably be closed, but I don't see a button that lets me do that. We'll close it later, thank you for caring.
Hi, On Wed, Mar 16, 2022 at 08:53:17PM -0000, Andrew Eidsness wrote: I've checked out the v0.11.0 branch and built openocd with the config parameters listed at the end. I've actually tried several different options, the one listed at the end is "everything I could find". ... I've connected a FlySwatter2 to a 1294xl, but I get an error when trying to launch with: $ openocd -f interface/ftdi/flyswatter2.cfg -f board/ti_ek-tm4c1294xl.cfg -c This looks more like a support request, please consider writing...
On Mon, Feb 28, 2022 at 08:18:41AM -0000, Milan wrote: You mean that it was maybe luck that it works with the 0.10.0 Version? I'm prety sure that was the official Version. I looked around and couldn't see any possibility for it to work the way you described. load_image works neither. Their comes no Exception, but the data is still NULL. Running load_image after unlocking the eeprom did nothing at all? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercerpav@gm...
Hi, On Fri, Feb 25, 2022 at 01:39:15PM -0000, Milan wrote: I try to write data to the eeprom of the stm32l151. In OpenOCD Version 0.10.0 I made a .bin File and write that with >flash write_bank 0 eePromFile.bin 0x80000< in the Eeprom of the device. I can't see how it could have been working, guess you had some OpenOCD non-upstream fork, not vanilla 0.10.0. What I'd probably try is something like this: mww [expr {0x40000000 + 0x20000 + 0x3C00 + 0xC}] 0x89ABCDEF mww [expr {0x40000000 + 0x20000 + 0x3C00...
Hi Oliver, On Mon, Feb 07, 2022 at 03:44:29PM -0000, Oliver Walczak wrote: @Antonio Borneo Thanx for coming back to me so quickly. I would need to compile openocd myself to get the patch both in Mingw and Mac, do I assume correctly? Or can you suggest a binary release e.g. for Mac that would include the patch? Getting latest OpenOCD on macOS is as easy as running $ brew install --HEAD openocd
Hello, On Sat, Jan 08, 2022 at 08:36:24AM -0000, Sachin J wrote: • [2]Screenshot from 2022-01-08 14-03-29.png (165.2 kB; image/png) This doesn't look like a bug in OpenOCD so please use the mailing list or IRC to get help. Also please use text for texts, not image/png. I think you're trying to use old 0.10.0 release with newer stlink v3 adapter. Please upgrade to 0.11.0 or master HEAD. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercerpav@gmail.com
New RISC-V based Miland MCU flashing support
Hello, Thank you for the patch. The OpenOCD maintainers team is using a Gerrit instance for code review, please follow instructions from HACKING and submit your code there. https://review.openocd.org I know it's confusing but SF.net doesn't seem to allow disabling the "merge request" button for the projects, sorry about that.
On Tue, Sep 14, 2021 at 12:32:32PM -0000, Michal Hucik wrote: Here is dbg output from OpenOCD. Error: 81 2255 core.c:1132 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones Error: 82 2255 core.c:1133 jtag_examine_chain_check(): Check JTAG interface, timings, target power, etc. So it looks like no communication happens at all. At this stage there's nothing fancy going on, it's almost like communicating to a regular shift register. Probably you can attach screenshots from your...
Hi, On Tue, Sep 14, 2021 at 12:19:22PM -0000, Michal Hucik wrote: I have connected OpenOCD with PRESTO, however communication with the CPU is failed. If someone wants to take a look, then in the attachment I send communication log on JTAG created by logic analyzer. I have communication log with neorv32 from PRESTO and by J-Link (J-Link communication is OK). Were both performed using OpenOCD? Can you also attach -d3 output from OpenOCD in both cases please?
Hello Michal, On Wed, Sep 08, 2021 at 07:25:38AM -0000, Michal Hucik wrote: I'm trying a first time to use Asix PRESTO with OpenOCD. That's apparently a rather unusual adapter. ==== OpenOCD --debug ==== Debug: 56 5 presto.c:139 presto_open_libftdi(): searching for PRESTO using libftdi Error: 57 7 presto.c:149 presto_open_libftdi(): unable to open PRESTO: usb_open() failed Error: 58 8 presto.c:540 presto_jtag_init(): Cannot open PRESTO Can you possibly join #openwrt on Libera IRC network for an interactive...
Hi Tarek, are you using a custom board without reset line ? if not could you please specify the board you are using ? In any case target config shouldn't assume presence of the reset line unless it's unusable without one (and I expect some comment there in that case).
flash/stm32l4x: use COMMAND_PARSE_NUMBER in command handlers
github/workflow: disable libusb static link for windows build
flash: nor: use binary prefixes consistently
Website Compromised
Thank you! Should be fixed by migrating to Pelican now.
Hello, On Tue, Aug 03, 2021 at 12:40:00AM -0000, sbruton@users.sourceforge.net wrote: just opened ticket #313, looks like someone managed to compromise the openocd.org website Thank you for reporting. I wonder if it's SF.net compromise because apparently it "resolved itself" and now the page is clean again? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercerpav@gmail.com
doc: move the official channel to Libera.Chat
Hello, On Wed, Jul 07, 2021 at 12:53:20AM -0000, Bruno Pimenta de Oliveira wrote: I'm trying to reprogram my board which has at32f403 chip but after install openocd and st link it does't recognize the board. Do you think it's an OpenOCD bug? For support requests please use the mailing list or IRC. I also do not see any log attached, so "doesn't recognise" is too vague to suggest anything. I'm following the steps of the github below, and also add some code in the src/flash/nor/stm32f1x.c with: case...
tcl: Add support for the Digilent Nexys Video board
doc: move the official channel to Libera.Chat
OpenOCD 0.11.0 released
The openocd-0.11.0 release
Restore normal development cycle
steppenprobe: fix file permission
The openocd-0.11.0-rc2 release candidate
Restore +dev suffix
README: add missing items for 0.11
jlink: fix device discovery when network is off
README.macOS: explain how to install suitable Texinfo
README.macOS: explain how to install suitable Texinfo
README.macOS: explain how to install suitable Texinfo
On Sat, Jan 16, 2021 at 09:28:12PM -0000, Maximilian Gerhardt wrote: openocd -f interface\stlink-dap.cfg -f target\stm8s103.cfg -c "load_image {C:\Users\Max\Documents\PlatformIO\Projects\stm8_testing.pio\build\stm8sblue\firmware.bin} 0x8000" Just add "init; reset halt; " before load_image -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercerpav@gmail.com
configure: do not make Capstone dependency automagic
doc: fix over/underfull hboxes in PDF
configure: do not make Capstone dependency automagic
configure: do not make Capstone dependency automagic
contrib: rpc_examples: haskell: fix ftbs with current libraries
configure: do not make Capstone dependency automagic
Add Q&D aspeed JTAG for the version that's currently in OpenBMC
[RFC] jtag: drivers: introduce q&d support for Linux kernel JTAG API