STM32F407-DISC1 Startup

[Syed Jaffar]

Posted on February 28, 2018 at 09:29

Hello there, Greetings.

I bought a Discovery board recently. Following are the details:

1] STM32F407G-DISC1

2] Model MB997D

3] ST-LINK both Jumpers in place

4] JP1, JP2 and JP3 in place

5] Using Windows 10 

I downloaded the proper drivers from the ST website. The drivers installed but I cannot find the board in the Device Manager! So when I upgrade the firmware, it does not detect the board! I have attached that images too. Please NOTE that the LD1 is not steady, it blinks constantly at a certain rate.

Someone suggested that this is an OS issue. Additionally, also that the miniUSB-USB cable might be another issue but I have used 2 such brand new cables [1 meter in length]. Then, is there an issue with the USART to USB dongle? Am I supposed to use such dongle to make the board transfer data over the USB? Is the miniUSB-USB connection not sufficient?

I am in dire need of help. Please help. I will appreciate it. Have a great day.♯

#stm32f407-discovery-startup

[Bogdan Golab]

Posted on February 28, 2018 at 10:33

I would test the board on another computer, if possible with Windows 7. Usually cable is the root cause form my experience.

But now looks like a problem with drivers. I believe you use the latest & greatest.

[Bogdan Golab]

Posted on February 28, 2018 at 10:51

LD1 is showing USB connectivity which actually fails in this case. Using ST-LINK for Virtual COM is good approach. So we need to fix the main problem first - the device driver problem.

[Syed Jaffar]

Posted on March 01, 2018 at 22:41

Thank a ton Golab! Please pardon me for a late reply.

I tried all the options you suggested but none worked. I also made the

Antivirus to allow the ST executables to pass through. But that did not

improve the situation: The ST-Link was not to be recognized by the system.

I think I have exhausted all possibilities with no results. I am surprised

as this is a new brand board and the drivers have been installed yet the

ST_Link is not being recognized.

One thing I am wondering is that a small brochure that came with the

Discovery board says the following:

'Ensure that the jumpers JP1 and CN3 are set to 'on' (Discovery mode)'

What does this mean? We already have the jumperJP1 and ST-LINK placed in

the slots, meaning the jumpers are set ... What do they mean by ON and by

Discovery mode? Simply confusing to someone new to this board. I thought I

bring up this point. This may have a bearing on what I am doing ...

Can't I use the micro USB connection somehow to talk to the board? This

might be a way out ... If yes, then what process is involved to use the

micro USB?

Please pardon me for disturbing you with these requests.

Thanks again and have a great day.

Best regards.

Thanks again and have a wonderful day.

On Wed, Feb 28, 2018 at 1:52 PM, Bogdan Golab <

[Bogdan Golab]

Posted on March 02, 2018 at 07:27

JP1 need to be on to close the power the MCU here. You can connect instead of JP1 an amperometer to measure the current consumption of the MCU. See the circuit for the details:

http://www.st.com/content/ccc/resource/technical/document/user_manual/70/fe/4a/3f/e7/e1/4f/7d/DM00039084.pdf/files/DM00039084.pdf/jcr:content/translations/en.DM00039084.pdf

 

Mini-USB is for ST-LINK connection (programming and debugging). And for some boards to emulate Virtual COM. This boards should support this feature.

Micro-USB can be used by the target MCU  - the MCU can be device or a host (OTG) from the USB perspective.

Have you tried to install and discover the st-link from non Windows 10? I do not have Windows 10 - I use it on 64 bit machines with Windows 7, Windows 8.1.

Do you have any experience in VMWare stuff - I mean setup a VM where you can install Windows 7 (some free versions are / were available in Microsoft for 30 days use), then move the Host machine USB stuff to the VM and try on Windows 7. This way you can test Windows 7 with the st-link software without reinstalling your host system.

I know it is complex of you did not do it earlier.

[Syed Jaffar]

Posted on March 02, 2018 at 13:18

Thank a lot for your prompt and sincere response to help me out. Great.

Yes, I have tried to discover the board in Windows 7 Enterprise and Windows

Vista. None worked. So I am not sure what is the problem. I will try

another mini USB cable, yet the 3rd time using Windows 7 Enterprise and and

see if cable is the culprit. If not, then I would really be flabbergasted

with the issue.

Additionally, I am not at all experienced with the VMWare stuff ...

I am surprised that the drivers successfully install [Windows 7, Windows

10] BUT the ST-Link is not discovered. There has to be a sound reason for

such an anomaly. I thank you tons for such care and concern. Best wishes

from my side.

Have a wonderful day and best regards.

Syed M J

On Fri, Mar 2, 2018 at 10:28 AM, Bogdan Golab <

[Bogdan Golab]

Posted on March 02, 2018 at 13:25

Looks like a hardware problem - usb-mini cable, st-link....

The st-link itself is quite decent (both windows software and firmware - assumed recent version) - I have over 20 boards with build-in, and external st-link and seen no such problem. I mean good boards, not broken

[Syed Jaffar]

Posted on March 02, 2018 at 13:52

Thank you much. Will try out another cable! Good day.

On Fri, Mar 2, 2018 at 4:26 PM, Bogdan Golab <st-microelectronics@jiveon.com

[Syed Jaffar]

Posted on March 03, 2018 at 13:56

Success. Thanks a ton.

This is the same cable that connects digital cameras or printers to the PC!

I tried others but those MUST NOT have been universal. Those cables must be

dedicated hardware based although the female end was a mini USB!!!!

Thanks again. I can finally make some progress.

Take care.

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

Virus-free.

www.avast.com

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

<&sharpDAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Mar 2, 2018 at 4:51 PM, Syed Murtaza Jaffar <smurtz14@gmail.com>