[OpenOCD-devel] [openocd:tickets] Re: #293 STM8 program command fails with "invalid subcommand write_image erase.."

2021-01-16 Thread Paul Fertser via OpenOCD-devel
On Sat, Jan 16, 2021 at 09:28:12PM -, 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

[OpenOCD-devel] [openocd:tickets] Re: #286 Deprecated warnings with libftdi 1.5

2020-10-27 Thread Paul Fertser via OpenOCD-devel
On Tue, Oct 27, 2020 at 10:38:10PM -, Antonio Borneo wrote: > At a first check, seams enough replacing ftdi_usb_purge_buffers() with > ftdi_tcioflush(). > The prototype of the functions is exactly the same, so simply run > sed -i s/ftdi_usb_purge_buffers/ftdi_usb_purge_buffers/ > src/jtag/driv

[OpenOCD-devel] [openocd:tickets] Re: #280 stlink-v2 not working with bcm2835 raspberry pi

2020-10-15 Thread Paul Fertser via OpenOCD-devel
On Thu, Oct 15, 2020 at 04:25:48PM -, Christian Tenllado wrote: > Thank you a lot Antonio for the information, I have to find an alternative > debugger then. Another raspberry pi would work as an alternative debugger by jtag bitbanging. -- Be free, use free (http://www.gnu.org/philosophy/fre

[OpenOCD-devel] [openocd:tickets] Re: #280 stlink-v2 not working with bcm2835 raspberry pi

2020-10-15 Thread Paul Fertser via OpenOCD-devel
Hello, On Thu, Oct 15, 2020 at 02:42:26PM -, Christian Tenllado wrote: > I am trying to use a stlink-v2 to debug a raspberry pi (bcm2835) using jtag, > but This is not possible, stlink-v2 is not a generic JTAG adapter, it only supports Cortex-M targets. --- ** [tickets:#280] stlink-v2 not

[OpenOCD-devel] [openocd:tickets] Re: #208 Open OCD for external qspi programming and debugging

2020-08-20 Thread Paul Fertser via OpenOCD-devel
On Mon, Aug 17, 2020 at 03:58:59AM -, Eddie Garcia wrote: > I downloaded your patch and applied it. Is it not possible to use the "load" > command from GDB? I can use the built-in OpenOCD commands to program the > external flash, but the "load" command from GDB seems to fail all the time. It s

[OpenOCD-devel] [openocd:tickets] Re: #275 ST-Link v3 refuses to work with non-ST targets, RE help needed

2020-07-27 Thread Paul Fertser via OpenOCD-devel
On Mon, Jul 27, 2020 at 12:03:12PM +0200, b...@elektron.ikp.physik.tu-darmstadt.de wrote: > > I'm surprised I get no constructive feedback on this ticket. Now that > > it's trivial to try a firmware with patched-out IDCODE check why isn't > > anybody trying that? > > This is caused probably by di

[OpenOCD-devel] [openocd:tickets] Re: #275 ST-Link v3 refuses to work with non-ST targets, RE help needed

2020-07-27 Thread Paul Fertser via OpenOCD-devel
On Mon, Jul 27, 2020 at 11:21:00AM +0200, b...@elektron.ikp.physik.tu-darmstadt.de wrote: > Rejecting non-ST MCU probably has also a deeper impact. The need to > read the MCUID! This has often problems when in sleep or even when in > reset. Even with stprog, STLINKV3 often does to to a board the >

[OpenOCD-devel] [openocd:tickets] #275 ST-Link v3 refuses to work with non-ST targets, RE help needed

2020-07-24 Thread Paul Fertser via OpenOCD-devel
--- ** [tickets:#275] ST-Link v3 refuses to work with non-ST targets, RE help needed** **Status:** new **Milestone:** 0.9.0 **Created:** Fri Jul 24, 2020 04:26 PM UTC by Paul Fertser **Last Updated:** Fri Jul 24, 2020 04:26 PM UTC **Owner:** Paul Fertser For the reasons yet to be discovered

[OpenOCD-devel] [openocd:tickets] #274 openocd error stmlink with stm32l053r8

2020-07-09 Thread Paul Fertser via OpenOCD-devel
- **status**: new --> closed - **discussion**: enabled --> disabled - **Resolution**: --> notabug - **Comment**: The bug tracking system is not meant for end-user support. Please read the official User Manual and if you still have any questions reach through the support channels. --- ** [ti

[OpenOCD-devel] [openocd:tickets] Re: #274 openocd error stmlink with stm32l053r8

2020-07-09 Thread Paul Fertser via OpenOCD-devel
Hello, On Thu, Jul 09, 2020 at 09:04:09AM -, MURLIDHAR ROY wrote: > embedded:startup.tcl:26: Error: Can't find target/stm32l0x.cfg There's stm32l0.cfg, probably you meant that? Please close the ticket if it's indeed just a typo. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.h

[OpenOCD-devel] [openocd:tickets] Re: #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-02 Thread Paul Fertser via OpenOCD-devel
Hi Noel, On Thu, Jul 02, 2020 at 12:59:09PM -, Noel Diviney wrote: > Info : Strange unsecure mode 0xde requested in the programmed file, set FSEC > = 0xfe in the startup code! > Info : FOPT requested in the programmed file differs from current setting, > set 'kinetis fopt 0xf9'. > Info : Try

[OpenOCD-devel] [openocd:tickets] Re: #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-02 Thread Paul Fertser via OpenOCD-devel
Hi Noel, On Thu, Jul 02, 2020 at 11:12:37AM -, Noel Diviney wrote: > I have not applied patches to openocd build before so can you please show me > whats involved. > I am using a Msys64 commandline terminal as inicated above. Basically, you have ready-made commands in the "Download" drop-down

[OpenOCD-devel] [openocd:tickets] Re: #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-02 Thread Paul Fertser via OpenOCD-devel
On Thu, Jul 02, 2020 at 02:16:17PM +0300, Paul Fertser wrote: > Basically, you have ready-made commands in the "Download" drop-down > menu on Gerrit change page. In this specific case I'd do ... That said, in this particular case of two patches, the second having the first as its parent (in other

[OpenOCD-devel] [openocd:tickets] #259 stlink-3 fail to read 1 byte alignment RAM

2020-01-28 Thread Paul Fertser via OpenOCD-devel
- **status**: new --> closed --- ** [tickets:#259] stlink-3 fail to read 1 byte alignment RAM** **Status:** closed **Milestone:** 0.9.0 **Labels:** stlink **Created:** Mon Nov 25, 2019 01:44 PM UTC by Pawel **Last Updated:** Tue Jan 28, 2020 09:49 AM UTC **Owner:** nobody Hi all, I have a

[OpenOCD-devel] [openocd:tickets] Re: #258 sudo apt install openocd

2019-11-20 Thread Paul Fertser via OpenOCD-devel
On Wed, Nov 20, 2019 at 06:23:43PM -, Andries Oyens wrote: > openocd command gives: ... > Info : at91samd21e18.cpu: hardware has 4 breakpoints, 2 > watchpoints So the adapter is working just fine, what's the problem? And why do you need any IDE to flash the target?.. -- Be free, use free (h

[OpenOCD-devel] [openocd:tickets] Re: #258 sudo apt install openocd

2019-11-20 Thread Paul Fertser via OpenOCD-devel
On Wed, Nov 20, 2019 at 04:25:56PM -, Jonathan McDowell wrote: > FWIW the Debian package installs the udev rules to > lib/udev/rules.d/60-openocd.rules, as they are part of the package. However > they > do not have the 2141 PID in them, just 03eb/204f, so if it was working before It should ge

[OpenOCD-devel] [openocd:tickets] Re: #254 “Error: this statement may fall through” when compiling from source

2019-11-03 Thread Paul Fertser via OpenOCD-devel
On Sun, Nov 03, 2019 at 09:48:35PM -, Miguel PA via OpenOCD-devel wrote: > Thank you very much for your help Paul, I really appreciate it. I managed to > generate the scripts with the bootstrap script, but now I'm running with a new > error with the make. It's the following: Just do configure

[OpenOCD-devel] [openocd:tickets] Re: #254 “Error: this statement may fall through” when compiling from source

2019-11-03 Thread Paul Fertser via OpenOCD-devel
On Sun, Nov 03, 2019 at 09:38:53PM -, Miguel PA wrote: > Thanks, I'm not very familiar with SF. I managed to clone the repo but there > doesn't seem to be configure or make scripts on the repo, am I doing something > wrong? Or should I use the scripts from the 0.10 tarball? Sorry if this is a >

[OpenOCD-devel] [openocd:tickets] Re: #254 “Error: this statement may fall through” when compiling from source

2019-11-03 Thread Paul Fertser via OpenOCD-devel
On Sun, Nov 03, 2019 at 08:00:18PM -, Miguel PA wrote: > The download pointed at by the sourceforge site is not the newest one? > Where can I obtain the master branch? "Code" pane on SF.net has links for cloning the repo. Some mirrors are mentioned on openwrt.org website too. -- Be free, use

[OpenOCD-devel] [openocd:tickets] Re: #254 “Error: this statement may fall through” when compiling from source

2019-11-03 Thread Paul Fertser via OpenOCD-devel
Hello, On Sun, Nov 03, 2019 at 01:48:05AM -, Miguel PA wrote: > I'm using version 0.10.0, but the ticket milestone option did not listed this > version Please build current git master branch instead. Or disable Werror in configure. -- Be free, use free (http://www.gnu.org/philosophy/free-sw

[OpenOCD-devel] [openocd:tickets] Re: #249 Not works on USB3.0 port

2019-08-06 Thread Paul Fertser via OpenOCD-devel
On Tue, Aug 06, 2019 at 02:03:44PM -, Dmytro wrote: > In attachment my config from device manager. As I understood, I have no > NEC/Renesas usb 3.0 controllers. Or i need to install libusb via Zadig? Is it > libusb issue? I think it is a Windows issue which makes using libusb problematic. Open

[OpenOCD-devel] [openocd:tickets] Re: #249 Not works on USB3.0 port

2019-08-06 Thread Paul Fertser via OpenOCD-devel
Hello, On Tue, Aug 06, 2019 at 11:32:17AM -, Dmytro wrote: > Not works on USB3.0. I have tested on different platforms (Intel and AMD) - > same > problem. Via USB2.0 works perfectly. Have you checked https://github.com/libusb/libusb/wiki/Windows#USB_30_Support ? -- Be free, use free (http:

[OpenOCD-devel] [openocd:tickets] Re: #245 Stm32f2 Architecture Rejected tarjet supplied description

2019-07-17 Thread Paul Fertser via OpenOCD-devel
Hello, On Wed, Jul 17, 2019 at 12:14:56PM -, Natalia Aramayo wrote: > I am using now OpenOCD 0.8.0 version. Why ancient version? > 301 target remote localhost: I recommend extended-remote so that "start" and "run" would be available. > &"warning: Architecture rejected target-supplied d

[OpenOCD-devel] [openocd:tickets] Re: #235 Communicating with OpenOCD's north bound API's?

2019-05-21 Thread Paul Fertser via OpenOCD-devel
Hi Tim, On Tue, May 21, 2019 at 04:53:03PM -, Tim Smith wrote: > Hi Paul, We wanted to run OpenOCD with in our process preferably by linking it > as a DLL. Is this something possible? Is your software GPLv2+ compatible? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) softw

[OpenOCD-devel] [openocd:tickets] Re: #235 Communicating with OpenOCD's north bound API's?

2019-05-02 Thread Paul Fertser via OpenOCD-devel
Hello, On Wed, May 01, 2019 at 09:12:09PM -, Tim Smith wrote: > We have a debugger that supports halt() , step() and go() high level run > control > commands. We wanted to add ARM run control support utilizing OpenOCD. > Wondering > if OpenOCD has north bound API's or pinch points for our C+

[OpenOCD-devel] [openocd:tickets] Re: #232 semihosting_fileio read return wrong number of read bytes

2019-04-21 Thread Paul Fertser via OpenOCD-devel
Hello, Thank you for the report and the patch. On Sun, Apr 21, 2019 at 08:31:05PM -, hogthrob wrote: > I have no idea how to use Gerrit, is there some kind of instructions > available. There certainly is, the file is called HACKING in the root of the OpenOCD sources. Fortunately, it doesn'

[OpenOCD-devel] [openocd:tickets] Re: #230 How to play svf from command line

2019-03-28 Thread Paul Fertser via OpenOCD-devel
Hello, On Thu, Mar 28, 2019 at 10:29:12AM -, Maarten Brock wrote: > When I try to run the svf command with -c on the command line of openocd I get > the following error: > Error: The 'svf' command must be used after 'init'. Please just prepend "init; " before svf command. -- Be free, use fr

[OpenOCD-devel] [openocd:tickets] Re: #224 samde53 openocd 0.10.0 Error: Failed to read memory at 0x400e0944

2019-01-29 Thread Paul Fertser via OpenOCD-devel
On Tue, Jan 29, 2019 at 01:02:59PM -, Andres Vahter wrote: > I also have SAME54 Xplained board and flashing also worked for that. > What do you mean by it wasn't removed from anywhere - I couldn't find it from > latest version. It wasn't removed from the sources as it wasn't ever merged in the

[OpenOCD-devel] [openocd:tickets] Re: #224 samde53 openocd 0.10.0 Error: Failed to read memory at 0x400e0944

2019-01-29 Thread Paul Fertser via OpenOCD-devel
On Tue, Jan 29, 2019 at 10:04:32AM -, Andres Vahter wrote: > gdb_memory_map disable This shouldn't be used for normal microcontroller development workflow. > So this worked very nicely. Not sure why atsame5x.cfg was removed in first > place. It wasn't removed from anywhere AFACT. Can you ple

[OpenOCD-devel] [openocd:tickets] Re: #224 samde53 openocd 0.10.0 Error: Failed to read memory at 0x400e0944

2019-01-28 Thread Paul Fertser via OpenOCD-devel
So please try http://openocd.zylin.com/#/c/4272 and report how it works for you. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com --- ** [tickets:#224] samde53 openocd 0.10.0 Error: Failed to read memory at 0x400e0944** **Status:** new **

[OpenOCD-devel] [openocd:tickets] Re: #224 samde53 openocd 0.10.0 Error: Failed to read memory at 0x400e0944

2019-01-28 Thread Paul Fertser via OpenOCD-devel
Hello, On Mon, Jan 28, 2019 at 08:51:32PM -, Andres Vahter wrote: > I tried to flash atsame53j18 with openocd 0.10.0. I used following .cfg file: ... > source [find target/atsamv.cfg] Are you sure samv flash driver supports your target controller? > # this disables Failed to read memory at 0

[OpenOCD-devel] [openocd:tickets] Re: #222 Flashing NXP Kinetis with ST-LINK V2 dongle fails, leaves flash locked

2019-01-27 Thread Paul Fertser via OpenOCD-devel
Hello, Thank you for the report and investigation. On Sat, Jan 26, 2019 at 09:43:34PM -, Bill Paul wrote: > The first has to do with the way the ST-LINK V2 performs write accesses. It > performs an automatic verify on write, which means that after a write > transaction is issued, it then pefo

[OpenOCD-devel] [openocd:tickets] Re: #219 SAMD21 OpenOCD

2019-01-04 Thread Paul Fertser via OpenOCD-devel
On Fri, Jan 04, 2019 at 12:40:23PM -, Ahmet Hamza wrote: > Im working on a custom board and I want to flash my microcontrollers with > Raspberry Pi and SA636 adapter. When I use "sudo openocd" command it gives me > that. Everything is fine about it? So what is your actual bug report? -- Be f

[OpenOCD-devel] [openocd:tickets] #214 Error: The specified debug interface was not found (ft2232)

2018-12-07 Thread Paul Fertser via OpenOCD-devel
- **status**: new --> closed - **Comment**: The ticket system is meant to track problems with OpenOCD, it's not a support forum. --- ** [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

[OpenOCD-devel] [openocd:tickets] Re: #214 Error: The specified debug interface was not found (ft2232)

2018-12-06 Thread Paul Fertser via OpenOCD-devel
On Thu, Dec 06, 2018 at 02:30:48PM -, Dr. Peter Oehler wrote: > which I've found at > > [2]https://github.com/arduino/OpenOCD/blob/master/tcl/interface/ftdi/oocdlink.cfg You should be using config files that are installed along with the OpenOCD, not download random versions from the Internet.

[OpenOCD-devel] [openocd:tickets] Re: #214 Error: The specified debug interface was not found (ft2232)

2018-12-06 Thread Paul Fertser via OpenOCD-devel
On Thu, Dec 06, 2018 at 12:49:34PM -, Dr. Peter Oehler wrote: > But I got problems, because in the interface configuration, which I've got, > there are some special statements not known by ftdi: > > interface ft2232 > ft2232_layout oocdlink > ft2232_vid_pid 0x0403 0x6010 > adapter_khz 100 Jus

[OpenOCD-devel] [openocd:tickets] Re: #214 Error: The specified debug interface was not found (ft2232)

2018-12-06 Thread Paul Fertser via OpenOCD-devel
Hello, On Thu, Dec 06, 2018 at 10:26:13AM -, Dr. Peter Oehler wrote: > Error: The specified debug interface was not found (ft2232) This is not a bug, ft2232 was deprecated since long. Please use ftdi interface instead. If you're on windows, don't forget to read README.Windows. Feel free to j

[OpenOCD-devel] [openocd:tickets] Re: #210 How to do patching on OpenOCD

2018-10-07 Thread Paul Fertser via OpenOCD-devel
On Sun, Oct 07, 2018 at 11:00:05AM -, Laxmi wrote: > From google, i understand that we need to path ath79 driver. Not sure how to > do > that. Can someone guide me step by step as how to patch to beginner like me. This ticket system is meant to track issues with OpenOCD, not as a support tick

[OpenOCD-devel] [openocd:tickets] Re: #209 Error: Start address out of range, Error: error reading to flash at address 0xbf000000 at offset 0x00000000

2018-10-07 Thread Paul Fertser via OpenOCD-devel
Hi, On Sun, Oct 07, 2018 at 10:35:39AM -, Laxmi wrote: > ./openocd -f interface/ftdi/flyswatter2.cfg -f board/ath79.cfg I do not see board/ath79.cfg in the upstream sources. > Info : Found flash device 'win w25q128fv' (ID 0x001840ef) > Error: Start address out of range > Error: error reading

[OpenOCD-devel] [openocd:tickets] #208 Open OCD for external qspi programming and debugging

2018-09-30 Thread Paul Fertser via OpenOCD-devel
- **status**: new --> closed - **Comment**: This is a discussion rather than an issue ticket. Please continue on the devel mailing list. --- ** [tickets:#208] Open OCD for external qspi programming and debugging** **Status:** closed **Milestone:** 0.9.0 **Labels:** QSPI Flash **Created:** S

[OpenOCD-devel] [openocd:tickets] #208 Open OCD for external qspi programming and debugging

2018-09-30 Thread Paul Fertser via OpenOCD-devel
- **private**: Yes --> No --- ** [tickets:#208] Open OCD for external qspi programming and debugging** **Status:** new **Milestone:** 0.9.0 **Labels:** QSPI Flash **Created:** Sat Sep 29, 2018 08:58 PM UTC by Praveen **Last Updated:** Sat Sep 29, 2018 08:58 PM UTC **Owner:** nobody Hi, We

[OpenOCD-devel] [openocd:tickets] Re: #203 programming st_nucleo_f7 (stm32f767) bank 2 consistently fails

2018-08-30 Thread Paul Fertser via OpenOCD-devel
On Wed, Aug 29, 2018 at 06:49:55PM -, Cody Schafer wrote: > Ah, found out why xPSR.T was 0: ... So obvious in the hindsight but boy what a rough trip you had finding it! Thank you so much for your persistence and sharing the result. -- Be free, use free (http://www.gnu.org/philosophy/free-sw

[OpenOCD-devel] [openocd:tickets] Re: #200 Fix stm32f3discovery.cfg to support interface/stlink-v2-1.cfg

2018-08-06 Thread Paul Fertser via OpenOCD-devel
On Mon, Aug 06, 2018 at 01:50:11PM -, John Hagen wrote: > I tested this on openocd 0.10.0 installed on macOS with Homebrew. So I > understand, is the fix you referred to only in master and just not released > into > a stable release yet? Yes. You should be able to install the latest git versi

[OpenOCD-devel] [openocd:tickets] Re: #200 Fix stm32f3discovery.cfg to support interface/stlink-v2-1.cfg

2018-08-05 Thread Paul Fertser via OpenOCD-devel
Hello, On Sun, Aug 05, 2018 at 07:45:17PM -, John Hagen wrote: > All new [2]STM32F3DISCOVERY boards include ST-LINK/V2-B which should use: > > source [find interface/stlink-v2-1.cfg] It's using source [find interface/stlink.cfg] since 31c58c139 (2017-01-26), the stlink version is autodetecte

[OpenOCD-devel] [openocd:tickets] Re: #173 "ThreadSetCurrentIp" sometime fails.

2018-01-24 Thread Paul Fertser via OpenOCD-devel
This specific command P19=2041 can mean only one thing: set register 0x19 to 0x2041 value. The question is why IDA decided to change that register? Is it supposed to touch floating point registers (which are not present on stm32f1) at all at that point? The address looks like some SRAM ad

[OpenOCD-devel] [openocd:tickets] Re: #173 "ThreadSetCurrentIp" sometime fails.

2018-01-24 Thread Paul Fertser via OpenOCD-devel
On Wed, Jan 24, 2018 at 07:22:42PM -, Artamonov Dmitry wrote: > ">" means packet TO gdbserver > "<" means packet FROM gdbserver > I tried to change PC from 08000DF0 to 08000DE2 > > Packet #0> > 02 00 00 00 45 02 00 37 20 74 40 00 80 06 00 00 E..7 t@. > 0010 7f 00 00 01 7f 00 00 01

[OpenOCD-devel] [openocd:tickets] Re: #173 "ThreadSetCurrentIp" sometime fails.

2018-01-24 Thread Paul Fertser via OpenOCD-devel
Hello Dmitry, Thank you for the report. To investigate it properly, more info is needed, please see below. On Wed, Jan 24, 2018 at 05:01:12PM -, Artamonov Dmitry wrote: > When i try to change IP debug session drops: > Debug: 7908 326686 gdb_server.c:2812 gdb_input_inner(): received packet: >

[OpenOCD-devel] [openocd:tickets] #171 SVF crashes with 5 CPLDs

2018-01-12 Thread Paul Fertser via OpenOCD-devel
- **status**: new --> closed - **Comment**: Welcome :) --- ** [tickets:#171] SVF crashes with 5 CPLDs** **Status:** closed **Milestone:** 0.9.0 **Created:** Wed Dec 20, 2017 04:04 PM UTC by Maarten Brock **Last Updated:** Fri Jan 12, 2018 09:49 AM UTC **Owner:** nobody **Attachments:** - [Op

[OpenOCD-devel] [openocd:tickets] Re: #171 SVF crashes with 5 CPLDs

2017-12-21 Thread Paul Fertser via OpenOCD-devel
Hi Maarten, On Wed, Dec 20, 2017 at 04:23:53PM -, Maarten Brock wrote: > /opt/sys/openocd/bin/openocd --version > Open On-Chip Debugger 0.9.0-dev-00358-gd3c2679-dirty (2016-01-11-16:24) Please retry with a current version, the one you're using is pre-0.9.0, and it doesn't contain 874f0157