Boundary Scan failure

peterruddock · ‎2011-04-11

Posted on April 11, 2011 at 21:23

Tesla DeLorean · ‎2011-05-17

Posted on May 17, 2011 at 14:31

I think the problem on you're green line is just that the boundary scan device does not have a nice decoding string within the Segger tool, it shows up in Google as an ST device, and you are programming the core not the boundary chain.

You should check that the STM3210E-EVAL template is even remotely valid for your board, it has external RAM and NAND/NOR FLASH.

You should check the flash algorithm you picked in the debugger/flash section matches the flash characteristics for your new part.

Calling out your exact part number might help with your request.

It looks to be an XL part, which definitely have a different flash configuration than the classic STM32 parts.

http://www.st.com/stonline/products/literature/rm/13902.pdf

+ # XL line devices, Rev A + set _BSTAPID6 0x06430041

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

peterruddock · ‎2011-05-17

Posted on May 17, 2011 at 14:31

Thanks. We were assuming that our template was valid, and it was not. We now have all of the values from the hardware vendor.