cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with upgrade STM32F0DISCOVERY to V2J16S0

fabiocatalano9
Associate II
Posted on January 23, 2013 at 17:28

Today I update my STM32F0DISCOVERY ST-Link/V2 from version V2J14S0 to V2J16S0.

I use an evaluaton version oh KEIL (version 4.60.0.0). Before the update I succeed in set breakpoints in my code. After the update I can't set breakpoint. There is some incompatibility beetween the two version of ST-Link and Keil compiler?

I have another STM32F0DISCOVERY (not updated) and this works fine.

What can I do for downgrade the ST-Link V2 on my board?

Thank you in advance.

Fabio
4 REPLIES 4
frankmeyer9
Associate II
Posted on January 23, 2013 at 19:17

Possibly a PC driver problem - have you tried the latest ST-Link USB driver ?

There is some incompatibility beetween the two version of ST-Link and Keil compiler?

 

If the USB driver is no fix, this would be a question to ask in the Keil forum. Not sure if they actively support an evaluation version.

But for a downgrade, older versions of the STLinkUpgrade EXE might do the job. But possibly it refuses a downgrade ...

I'm going to check this tomorrow, as I had updated a F0 discovery to V2J16S0 today, but not yet tested with Keil.

frankmeyer9
Associate II
Posted on January 24, 2013 at 08:31

Sorry, I can't confirm your problem.

It is still working for me, with  uVision V4.60.0 (Evaluation), on WinXP.

Building and debugging a stm32f0-discovery example succeeded without any issues.

I had installed the ST-Link USB driver only recently (2 days ago), so possibly an OS or driver issue.

fabiocatalano9
Associate II
Posted on January 24, 2013 at 12:45

I tried to re-install everything: Keil, ST-Link Utility and USB driver.

Now everything works fine.

Thank you

Fabio

fabiocatalano9
Associate II
Posted on January 24, 2013 at 12:46

I tried to re-install everything: Keil, ST-Link Utility and USB driver.

Now everything works fine.

Thank you

Fabio