2025-04-23 12:47 AM
So, a month or two ago, I had an issue where my USB 2.0 wouldn't connect and kept giving an error that the device descriptor wasn't detected. I found out at the time, that it wasn't properly generated, added it and all was fixed. Well, more problems started a week or so ago. My old STM board had damage done to it, and thus I had to swap to a new one. Luckily, the add-ons (ADC and USB 2.0) were undamaged. I have a problem though. The exact same code I used for the original board does not appear to be working on this new board. The boards are close to identical, going from an STM32 h745 to a h755. I have no idea why it wouldn't work, considering it worked fine on the old board. I've tried going back in versions and so dice. It keeps either simply not showing up in the device manager when connected or gives the same old error of device descriptor wasn't detected. I'm kind of stumped and have no idea why it would be doing this. If anyone has any ideas on things to try, I'm all ears and would much appreciate it.
Old post reference is here: https://community.st.com/t5/stm32-mcus-embedded-software/usb-3300-not-detected-by-windows-on-nucleo-h755ziq/td-p/771640
2025-04-24 10:01 AM
Hi @Igneous
Migrating from the H745 to the H755 should be seamless in your case, as the primary difference is the addition of crypto support.
Verify that all connections between the USB3300 and the Nucleo are properly configured. Additionally, confirm that the external crystal oscillator is operating correctly and delivering a stable clock signal to the USB3300.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.