STM32F4DISCOVERY : Cannot connect to the MCU device

[nedelec]

Posted on April 16, 2012 at 13:18

Hello,

I just bought an STM32F4 discovery board. I installed the USB drivers (

ST-LINK/V2 USB driver for Windows 7, Vista and XP

) and the

STM32 ST-LINK utility programmer.  As a first step I would like to connect the ST-Link v2 to the device and then load an example binary file.

The programmer do not reconize the device. When trying to connect, the green/red led is blinking, and them goes to green. But the programmer give me the following message:

''

21:57:55 : Connected via SWD.

21:57:55 : Cannot connect to the MCU device!

''

I tried to do a firmware update. When the board has just been connected i'm able to see the firmware version, it is up to date (i'm also able to update it). But if i try to connect the device, then after firmware update is not possible any more until rebooting the board.

I think i have à driver problem. I tried everything i found on the web (like removing daemon tool) and also tried to instal the drivers on an other computer. I do not manage to connect to the device !!!

Can someone may confirm that i can use the

''STM32 ST-LINK utility programmer'' by itself as a very first step (to check connectivity)?

Does someone know what may I do to connect this device?

I use windows 7, on a core i3 (64bits) based computer.

Regards,

Ronan

[yana5]

Posted on April 19, 2012 at 08:36

Hi ronan22,

My STM32F4-Discovery is also the same condition.

In STM32VLDISCOVER, it is connectable without a problem in the same environment.

MPU on a STM32F4 is the revision Z.

How is your MPU?

ya75

[johanevers9]

Posted on April 19, 2012 at 09:29

Hi Ronan22 and Ya75,

I have 5 of those boards (don't ask why...;-) and two of them show the same failure. The other three work perfectly.

Your remark that your board with silicon revision Z did not work triggered me. So I checked my boards. And indeed, both my non-functional boards have silicon revision Z. And the three good boards have silicon revision A.

To me it looks like we have a good suspect here; the silicon revision...!!!

I do not think of a driver issue (unless the driver is silicon revision dependant), because I plug and unplug all my 5 boards in the same (Virtual) machine under Win-XP. Clearly only the silicon revision A boards works and the Z boards don't....

Can anybody else confirm this?

Does anybody have a suggestion how to solve it?

Best regards, Johan.

[Tesla DeLorean]

Posted on April 19, 2012 at 19:58

Can confirm ''A'' silicon STM32F4DISCOVERY working on Win7 64-bit, Vista 32-bit.

[nedelec]

Posted on April 19, 2012 at 21:17

Thanks for your help, it seems i can stop looking on driver install/uninstall...

It seems the STM32 device on my board is 'Z' type :

top line : STM32F407

then :      VGT6          Z

              HPAFD      VG

              KOR   HP   203     

What could i do with this board? If it is confirmed that the device type ''Z'' is giving this problem, may we expect a driver update that could be able to be connected?

Or do i have to buy a new one expecting to be lucky on the STM32 type? And trying to send back the one I bought?

Or do there is a way to configure the progammer for handling this device?

Regards,

Ronan

[nutzlos]

Posted on April 20, 2012 at 10:20

Hi,

I can confirm the problem, same error message on Win7 (32-bit) with a 'Z' device.

I get it to work though by using st visual programmer (http://www.st.com/internet/evalboard/product/210568.jsp). I hope they add support for the 'Z' device soon to 

STM32 ST-LINK utility programmer.

Regards,

Boris

[Tesla DeLorean]

Posted on April 20, 2012 at 14:05

Any chance some ST staff might actually participate in the forum?

[yana5]

Posted on April 20, 2012 at 15:31

Hi,

Thank you for your reacting.

Those who have many boards like Johan are enviable. :)

It has connected, when trying on ''st visual programmer'' which Boris taught.

Thank you.

I thought that I wanted ST staff to ship after checking it exactly.

Regards,

Ya75

[marouanbm]

Posted on April 24, 2012 at 17:19

Hi,

The Device ID of the STM32F4xx

Rev.Z

has been changed to

0x413 (instead of 0x411 for

Rev.A

).

Thus,

ST-LINK Utility

can't recognize the device ID of STM32F4 Rev.Z (Only Rev.A is supported).

This issue will be fixed in the next version which will be released soon.

In the meanwhile, the attached patch adds the support of STM32 F4 rev.Z in the current version(v2.2).

Regards,

Marwen

________________

Attachments :

ST-LINK_Utility_V2.2Patchv10.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HzhW&d=%2Fa%2F0X0000000bP3%2Fl0GLi3nX0K_fRqLWj2Khu5Gi5O7twDxS6ZJIMPxWv3s&asPdf=false

[johanevers9]

Posted on April 25, 2012 at 12:07

Dear Marwen,

Thank you for posting the patch.

I can confirm that this patch works perfectly. Now I can connect to all my kits.

Best regards from the Netherlands.

Johan.

[nedelec]

Posted on April 25, 2012 at 19:16

Thanks, this is well working now with the patch... :)

Regards,

Ronan