Failed to read CPUID for Cortex device. ST-Link problems.

[petecarr]

Posted on October 20, 2011 at 02:35

I posted this in the STM32L area by mistake. This was a VL.

--------------------------------------------------------------------------------------------------------I started having problems with STLink  (MDK-ARM - getting an ''Internal Command Error''), and ST Visual Programmer has problems. Log:Hardware configuration set to <ST-LINK on USB with STM32F100xB plugged in and SWD protocol>.Blank check before programming (when available) is OFFVerify after programming is ON.Clear memory before loading a file is ON.Erase device memory before programming (when available) is OFFDisplay a popup window when an error occurs is ON.Log activity is OFF> Reading section [8000000-80003FF] of  PROGRAM MEMORY area...Error : ST-Link error (USB communication error).Error : < PROGRAM MEMORY reading failed.> Reading section [8000400-80007FF] of  PROGRAM MEMORY area...Error : ST-Link error (USB communication error).Error : < PROGRAM MEMORY reading failed.End of Log.  so I switched to IAR  v 6.21 and after some problems with CMSIS (fixed thanks to forum) I got it to link. Now, I get a new messageFailed to read CPUID for Cortex device.Log isWed Oct 19, 2011 16:41:44: Selecting SWD as current target interface. Wed Oct 19, 2011 16:41:44: Hardware reset with strategy 0 was performed Wed Oct 19, 2011 16:41:44: Initial reset was performed Wed Oct 19, 2011 16:41:47: Fatal error: Failed to read CPUID for Cortex device   Session aborted! Wed Oct 19, 2011 16:41:47: Failed to load debugee: C:\Users\pete\Documents\stm32vldiscovery_package\an3268\stm32vldiscovery_package\Project\Demo\EWARMv5\DISCOVER\Exe\ DISCOVER.out 

[Tesla DeLorean]

Posted on October 20, 2011 at 03:03

Did this work at one point, and then stopped after you downloaded some new code?

It's quite easy to brick the VL Discovery, especially with DMA running outside the core. If this might be case here try jumpering the BOOTx pins so it runs the system loader instead of your own application. Check also if IAR is installing it's own drivers for the ST-LINK, and if those are in fact older versions. ST does have newer drivers and firmware for the ST-LINK which might be worth a try.

[petecarr]

Posted on October 21, 2011 at 17:57

I'm pretty certain that's what happened. I have the newer driver for STLINK.

Is there a description on how to jumper the BOOTx pins? I searched around the docs and found SB16 BOOT0 which is already bridged and SB2 BOOT1 which appears to have a resistor across it. Being a software guy, I haven't much of a clue here.

[singamicro]

Posted on October 22, 2011 at 11:52

Please read 1200rata's posting on disabled swd debuging in this forum.

Try: [DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32VLDiscovery/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32VLDiscovery/disabled swd debuging&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000491D59B8574F8049B5DFA3E8B21CBA51&TopicsView=https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32VLDiscovery/AllItems.aspx&currentviews=177]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32VLDiscovery/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fSTM32VLDiscovery%2fdisabled%20swd%20debuging&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000491D59B8574F8049B5DFA3E8B21CBA51&TopicsView=https%3A%2F%2Fmy%2Est%2Ecom%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2FSTM32VLDiscovery%2FAllItems%2Easpx&currentviews=177

[petecarr]

Posted on October 22, 2011 at 21:35I tried various combinations of Boot0 and 1 connections and I definitely get a different result. Now Keil uVision says ''No STLink detected''. Could this be because I have STLink V2 installed? I have an STM32L board which communicates fine using STLink V2.