USB device example

[maac]

Hello everyone,

I have an stm32f303cbt6 design (see image below) connected to an hub(USB2533) and an adum for isolation, i'm trying to run a USB device CDC example by creating a new project in the Stm32CubeIDE using device tool configuration.

 

I selected :

- RTC : HSE Bypass clock source (24Mhz)

- SYS : Serial wire debug 

- USB : fs device

- Middleware : USB device CDC

 

When i build and i compil to my board, windows doesn't recognise it, can you help me with that ?

(i tried also to put the connect_usb pin to 3.3 V, i got same thing)

 

Thanks.

 

 

 

 

[Andrew Neil]

---

@maac wrote:

windows doesn't recognise it,

---

Does it not see it at all? give an error? other?

[maac]

I don't have windows message.
I got this in USBTree (the hub has 3 downstream), it seems like the hub is detected but not the device (stm32).

 

[Andrew Neil]

---

@maac wrote:

it seems like the hub is detected but not the device (stm32).

---

Is the device detected without the Hub ?

If you don't get any messages, and nothing appears in Device Manager, then the PC is not even seeing that anything has been plugged it.

Are you sure that you are using a good data cable - not just a charging cable?

[gbm]

Too little information give for a reasonable help, but maybe you should start by increasing the default stack and heap sizes to twice the value.

[maac]

I gave informations as possible as i know, you can ask for information so i can put it.

The default configuration seems to make the USB detected at least, i don't undrestand what do you mean by increasing.

[Andrew Neil]

---

@maac wrote:

i don't understand what do you mean by increasing.

---

"increasing" = "making bigger/larger"

ie, Whatever size your Heap and Stack currently are, trying making them twice that size.

[FBL]

Hi @maac 

It seems USB root hub does not set address to your device. You need to ensure that the STM32 and the USB hub are properly powered.

• Verify the connections between the STM32 and the USB hub. Ensure that the DP and DM lines are correctly connected and there are no short circuits.
• Check the isolator connections to make sure it is properly isolating the USB lines without introducing signal integrity issues.
• Ensure that the 24MHz crystal is properly connected and oscillating. Incorrect crystal connections can cause USB communication failures.

Follow the recommendations in the schematics provided in Nucleo F303 

Provide USB traffic so that we can help you investigate further. In your case, using USBPcap in Wireshark could be helpful.

[maac]

As i said before, the current fw is a Vendor Specific device and it's running(at least it's detected by Windows and the PC software), So i don't think there is a problem in the design. I'm looking to change or get better(i don't know for the moment) that USB fw because there is no documentation about, and i'm trying to run examples first. I can't sniff the communication cause the USB is not detected as i said.

[Andrew Neil]

---

@maac wrote:

As i said before, the current fw is a Vendor Specific device and it's running.

---

So where has this FW come from?

Do you have the source? Do you have debug access? Do you have a contact for support?

 

---

@maac wrote:

 i'm trying to run examples first.

---

I would strongly suggest that you start by running the examples on the hardware they were intended for.

Then they should work, and you can spend time studying how they work.

If they don't work, you will be able to get support - as it's known hardware.

Once you understand how the examples work, then you'll be better equipped to find what's going wrong on your custom hardware - maybe it has other things which need to be enabled and/or configured ... ?

[maac]

Hello,

 

I'm back to know if you have any idea why a simple USB example can't work looking the schematics i sent knowing that there is a USB fw working on it that i want to change.

 

Thanks.

[Andrew Neil]

As suggested, have you got any examples working on the hardware they were intended for?

[maac]

I will give a feedback when i'll try with a dev board.