Latest STM32-H152 board not supported by OpenOCD_0.8.0

jartim · January 28, 2015, 04:10:59 PM

I have a latest Olimex STM32-H152 board that has a 'Z' suffix processor.
This processor is not recognised by OpenOCD 0.8.0 (the latest release) so I cannot debug or load my firmware.

This is delaying my project considerably.
Do you know of any work-arounds to this problem?

Many thanks

JohnS · January 28, 2015, 04:50:40 PM

I think it will be recognised if you use the right things to get it to work. If you can get the right TAPID etc then you're good to go.

By not providing details of what you did and debug ( -d3 ) logs you're failing to give data people probably need.

Best place is bound to be the ML or site for oocd. They will require the above.

John

jartim · February 06, 2015, 02:22:07 PM

Sorry for the delay!
This is the response I get from OpenOCD -

Open On-Chip Debugger 0.8.0 (2014-04-28-08:39)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 100 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
cortex_m reset_config sysresetreq
Info : clock speed 100 kHz
Info : JTAG tap: stm32l.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)
Info : JTAG tap: stm32l.bs tap/device found: 0x06429041 (mfg: 0x020, part: 0x6429, ver: 0x0)
Warn : JTAG tap: stm32l.bs UNEXPECTED: 0x06429041 (mfg: 0x020, part: 0x6429, ver: 0x0)
Error: JTAG tap: stm32l.bs expected 1 of 1: 0x06416041 (mfg: 0x020, part: 0x6416, ver: 0x0)
Error: Trying to use configured scan chain anyway...
Warn : Bypassing JTAG setup events due to errors
Info : stm32l.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection from 3334
Warn : Cannot identify target as a STM32L family.
Error: auto_probe failed

After talking to the FAE at Anglia it seems that the 'Z' revision of the STM32L152 fitted to the board is a pre-production evaluation revision that should not have been shipped to customers!
Hopefully someone at Olimex will look into this and make sure no-one else gets an evaluation revision processor that they cannot use!

JohnS · February 06, 2015, 04:51:13 PM

What happens if you change the config to match what is found?

John

jartim · February 06, 2015, 08:47:57 PM

I can change the OCD script but then GDB falls over. The point is, these processors should never have got into finished items.

JohnS · February 06, 2015, 09:39:32 PM

gdb is some other problem. It doesn't even know or care about the the JTAG / TAP ID etc, does it?

By way of example, you could've got those chips on a board from ST - I have had similar non-production ones on their own eval boards before now and they're fine once you tweak configs. They have errata, as most chips have, but tend to work.

I've no idea if what you've been told is correct but I can't see why the chips can't be used OK, similar to what I've had in the past.

John

luimarma · September 25, 2015, 02:54:43 PM

I make this thread up to see if something is found out about this problem.
I am in the same situation STM32_H152 and STM32L152 chip marked with a Z. I have modified the config file and now openocd starts ok. But when gdb tries to connect, then the following error happens in openocd:
Info : accepting 'gdb' connection from 3333
Warn : Cannot identify target as a STM32L family.
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected
Is there any solution to the problem?

luimarma · September 25, 2015, 09:56:22 PM

Finally solved using latest 0.9 0 openocd.