Problem in MSC_Standalone, STM32F4

[voyvoda .]

When I compile and download the code. I see a USB problem.

What could be the possible solution ?

[Pavel A.]

It is USB enumeration error. Win10 usually displays better/more detailed reason than older versions so try it.

Debug the USB code on the STM32 side to get to the root case.

-- pa

[voyvoda .]

I have already used Win10.

Which I should pay attention in the STM code side ?

[Tesla DeLorean]

The descriptors might be a good starting point?

Make sure your clock, PLL, and HSE_VALUE sets are correct.

Make sure the stack and heap sizes are sufficient.

Instrument your code to see what interactions are occuring, and where things stop functioning.

[voyvoda .]

This is the example which should run out of the box. Am I wrong ?

Why should I check the PLL, HSE_VALUE, stack and heap sizes ?

[Pavel A.]

Is this on your custom board or some "Discovery", "Nucleo" or other ST product?

-- pa

[Tesla DeLorean · Accepted solution]

>>Why should I check the PLL, HSE_VALUE, stack and heap sizes ?

Cause stuff isn't working, and this would take a couple of minutes to cross-check? You need a check-list or script to do the debugging, start with this.

>>This is the example which should run out of the box. Am I wrong ?

I don't know, you've been unsuccessful, what does that tell you about the situation and your expectations?

I don't know you, I don't know what hardware you have. STM32F4 covers dozens of different chips, and thousands of boards. You're lack of specificity make remote diagnosis really hard to do.