On 14/12/2010 17:27, Freddie Chopin wrote:
On 2010-12-14 17:35, Alan Bowman wrote:
I have just connected my JTAGkey2 to a new STM32E-EVAL board, and have
found that I am unable to program/erase the onboard flash. When I
first connected to the target, I was warned that there was an
unrecognised BS tap ID. I added an extra expected-id to my config
file (0x06430041) and that allowed me to connect without errors. When
I came to erase the flash using
stm32x mass_erase 0
I received the following error:
device id = 0x10006430
Cannot identify target as a STM32 family.
I am using openOCD 0.4.0, but looking through the latest repository
code, I think that I would get the same error. I think it is just
that recognition of the larger family of STM32s (I have an STM32F103ZG
on my board, one of the later eval boards) have not been added to
OpenOCD. It looks like it should be a handful of lines to add the
extra devices/flash - is this true, or have I missed some subtle
reason why this isn't easy to support?
I would make the change and try it out but I'm not currently able to
rebuild from source on my Windows platform. I wanted to see if there
was a good reason why it wasn't worth doing before going down that
route.
I guess it's just "not supported yet" - you can add those lines and it
will work.
4\/3!!
I have also got a wip patch for the larger 1MB parts as they use dual
flash banks.
I will get it merged over the next week, but as you suggested adding the
ID will permit you to program the first 512k of the XL parts.
Cheers
Spen
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
