Sw or Damaged Board?

[maurosmartins]

Posted on July 26, 2016 at 21:09

Hello all, 

I've recently acquired an STM32 Nucleo-F103RB evalutation board. I've used STM32 cube to generate a sample program for both free versions of atollic true studio and IAR for ARM. When trying to program/Debug the board most of the time I get something like this:when lucky I'm able to debug some lines of code but if I stop the debug session it won't be possible to resume. Even with the stm32 utility I get this:I've measured the voltages on the board they are ok! when connected to USB the drive appears and downloading a .bin from mbed site works.So, I ask you, what does it look like? Sw problem or damaged board?In case of damaged board how does ST handle this?Thanks in advanced, Best regards, Mauro. #!stm32-!cubemx-!bug-!hardware

[Radosław]

Posted on July 26, 2016 at 21:15

Did you use sleep modes?  I check SWD in CUBE.??

[maurosmartins]

Posted on July 26, 2016 at 21:26

Hello dembek.radoslaw.001, thank you for your reply, 

On Cube I've selected this evaluation board and the pins for SWD are already selected. I have no sleep modes not intentional at least.Best regards, Mauro.

[Tesla DeLorean]

Posted on July 26, 2016 at 22:40

Does using ''Connect Under Reset'' help? How about strapping BOOT0 High?

Low power, WFI loops, reprogramming JTAG/SWD pin functionality...

[Walid FTITI_O]

Posted on July 29, 2016 at 17:09

Hi maurosmartins,

Try to use the last version of ST-Link  from here

http://www.st.com/content/st_com/en/products/embedded-software/development-tool-software/stsw-link004.html

-Hannibal-