The errors and the line numbers show that you are using OpenOCD v0.10.0, that
is 4 years old.
Please switch to OpenOCD v0.11.0.
If you have any reason to stay on that old version, then please notice that
modern compilers will trigger many more warnings, so you need to add the flag
"--disable-wer
On 2021-06-19 22:58, Oleksandr Redchuk wrote:
FT2232D-based adapter
The same behavior as Ali Tekin reported:
"Error: error writing to flash at address 0x0800 at offset
0x"
On 2021-06-17 14:51, ali tekin wrote:
Do you get this warning below, too? Could you post the cfg file?
> Wa
I've checked it with the latest HEAD on my board based on STM32L051 and two
different programming HW
ST-LINK V2 clone with patched HW: STM8 reset output is cut and STM32 reset
is routed to reset output
(reset is necessary because firmware uses SWD pin disabling and deep sleep)
Works as expected.
It might help if you describe the full set of steps that you carry out in an
attempt to build OpenOCD. And on what OS variant and version.
From: Bruno Pimenta de Oliveira
Sent: Saturday, June 19, 2021 7:34:40 PM
To: openocd-devel@lists.sourceforge.net
Subject: [o
---
** [tickets:#309] openocd src/svf/svf.c:663:7: error: this statement may fall
through [-Werror=implicit-fallthrough=]**
**Status:** new
**Milestone:** 0.10.0
**Created:** Sat Jun 19, 2021 06:34 PM UTC by Bruno Pimenta de Oliveira
**Last Updated:** Sat Jun 19, 2021 06:34 PM UTC
**Owner:**
On Sat, Jun 19, 2021 at 01:19:40PM +0100, Tarek BOCHKATI wrote:
> I have seen that you have helped getting openocd 0.11.0-rc2 into both
> bullseye (testing) and sid (unstable). but unfortunately the official
> v0.11.0 release has never made it to buster (stable).
>
> IMO, it would be nice if peop
On Sun, Jun 13, 2021 at 7:02 PM Xiaofan Chen wrote:
> > I can see that there is an issue with ST-Link now. I can
> > reproduce it myself.
> > https://sourceforge.net/p/openocd/tickets/308/
> > https://github.com/libusb/libusb/issues/928
>
> Based on my investigation, the issue is not with libusb
I always forget about Windows!
Have you tried either "CON" or "CON:" ?
https://superuser.com/questions/241272/windows-how-to-redirect-file-parameter-to-stdout-windows-equivalent-of-dev-s
If it doesn't work we would need adding hooks in OpenOCD to intercept the
string "/dev/stdout" or "stdout" and
