[OpenOCD-devel] [openocd:tickets] #233 Issue flashing STM32L071 processor

[Tom <to...@us...>]

1) You are using an modified OpenOCD source from https://github.com/sysprogs/openocd
We do not know what eventual changes was made by sysprogs. Please run the officialOpenOCD code if you want to report bugs - see http://openocd.org/getting-openocd/

2) Be aware of https://sourceforge.net/p/openocd/tickets/231/

3) Your log shows that you want to program more than 64kB code in configuration with 64kB flash only. 
If you used OpenOCD flash programming command, you would get an error message. Unfortuantelly the gdb happily writes your code above 0x8010000 as it were RAM area and no warning is issued.

It looks you should use 'stm32l0_dual_bank.cfg' instead of 'stm32l0.cfg' as a target config for 128kB flash device. This is required since commit b375052c58a4ef9b855ce9aa119cc1abf432d0c8, merged two years ago.



---

** [tickets:#233] Issue flashing STM32L071 processor**

**Status:** new
**Milestone:** 0.9.0
**Created:** Thu Apr 25, 2019 03:49 PM UTC by Jim
**Last Updated:** Thu Apr 25, 2019 03:49 PM UTC
**Owner:** nobody
**Attachments:**

- [OpenOCD-New.txt](https://sourceforge.net/p/openocd/tickets/233/attachment/OpenOCD-New.txt) (1.4 MB; text/plain)
- [OpenOCD-Old.txt](https://sourceforge.net/p/openocd/tickets/233/attachment/OpenOCD-Old.txt) (1.9 MB; text/plain)


Using openOCD 0.9.0 we were able to program and debug our STM32L071 boards.  We had to upgrade to version 0.10.0 when the new L496 processor came out, but ever since then we've been unable to program our L0 boards.  We ended up forking and modifying 0.9.0 to support the L496, but now that even newer shinier processors are coming out and we still have issues with the latest version, I figured I'd take a whole bunch of data and chime in.

I'm attaching two files, one of them is the openOCD log log from our custom build based off of 2017-04-14 and one of them is the latest (2018-12-12).  Both of them have -d3 turned on.

The old version works every time.  I can put a break point at the first instruction of main() and I'll get there every time.  The new version I don't think ever works.  It says it's done loading but it never hits the break point.  If I hit pause its lost off in the weeds and the processors registers don't look like they have valid information:  R0 through R12 all have a value of 0xffffffff.  SP is 0x20004fe0.  LR is 0xfffffffe.  PC is 0xfffffffe.

If I program the processor with ST-Link and then attach to a running firmware, then I can debug fine, it just appears to have issues with flashing it.  I have confirmed this using a Nucleo board and there is no firmware running on it (I erase it with St-Link and power cycle the board before attempting to program it).


---

Sent from sourceforge.net because ope...@li... is subscribed to https://sourceforge.net/p/openocd/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/openocd/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.