2008-07-13 10:11 PM
jtag part identification - openocd problems
2011-05-17 03:39 AM
FYI - identification marks on the part with 0xfffffff are:
stm32f103zet6 220898 vc mlt 3r816 03 Perhaps I have an early chip? Thanks.2011-05-17 03:39 AM
I have qty 2 eval boards, I am trying to get them to work with openocd jtag, I am having problems.
Board (1) stm32f103vbt6 using openocd - dumping memory @ 0x1ffff7e0 I get this: > mdw 0x1ffff7e0 16 0x1ffff7e0: 00140080 066906c7 ffffff37 31383836 43095836 fffcf0ff 00ff9768 3fc0bc43 0x1ffff800: 00ff5aa5 00ff00ff 00ff00ff 00ff00ff ffffffff ffffffff ffffffff ffffffff Which is correct, 0x00140080 - means 20K ram, 128K flash. (PER rm0008 - section 25.1 - that is) Board #2 has: stm32f103zet6 - 512K part. Dumping memory @ 0x1ffff7e0 I get this: > mdw 0x1ffff7e0 16 0x1ffff7e0: ffffffff ffffffff ffffffff ffffffff ffffffff fffcffff 00ff9768 3fc0c33c 0x1ffff800: 00ff5aa5 ffffffff 00ff00ff 00ff00ff ffffffff ffffffff ffffffff ffffffff This is flatly wrong, it appears - that per RM0008- section 25.1 - memory size registers - these are not programed correctly on the part. I need some other means to identify the part present on the board. The goal being - proper & complete support for the stm32 parts using openocd, gdb, etc. (hint: Visit the openocd mailing list) For example - is there a 'boundry scan part id' (not the generic 'i am an arm tap' identifier? If so - where can I get documentation about what numbers in the 'st family' mean? Further, can somebody explain what is meant by Section 26.6 - ''ST Strongly recommends tools designers to lock their debuggers using the MCU DEVICE ID located in external PPB memory map at address 0xe0042000'' - what benifit is that? All that tells me is ''High/Low'' density - and a rev letter. That does not tell me the *part* number or the flash size. Thanks.2011-05-17 03:39 AM
you have early sample silicon - these have no id programmed.
Cheers Spen