Skip to content

[New Variant] WeAct STM32H503 Core Board #2736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Avamander opened this issue May 24, 2025 · 4 comments
Closed

[New Variant] WeAct STM32H503 Core Board #2736

Avamander opened this issue May 24, 2025 · 4 comments
Labels
new variant Add support of new bard

Comments

@Avamander
Copy link
Contributor

Avamander commented May 24, 2025

Board description (please complete the following information):

It also seems like my physical board has a STM32H503CBT6 but the schematic has a STM32H503CBU6, unsure how much of a difference it makes though.

Note that user can add a STM32 based board following this wiki

Any contribution is welcome, so do not hesitate to submit a PR.

All new variant request will be moved to [New Variant] request list #722 and the related issue will be closed.

@Avamander
Copy link
Contributor Author

Avamander commented May 24, 2025

For some reason I also can't get USB CDC serial working with the following configuration "Generic STM32H503CBTx", "CDC (Generic Serial)", "U(S)ART (Generic Serial)". The device fails to respond (to URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE) and the result is "This device cannot start. (Code 10)" under Windows 11. At the same time DFU works and enumerates properly on the same board.

@fpistm
Copy link
Member

fpistm commented May 24, 2025

You should check the clock configuration to ensure USB clock is 48 MHz.

@Avamander
Copy link
Contributor Author

Avamander commented May 24, 2025

Reading this, it should be: https://github.com/stm32duino/Arduino_Core_STM32/blob/main/variants/STM32H5xx/H503CB(T-U)/generic_clock.c

It also doesn't seem like USB communication is failing completely, if I fiddle with the clocks then it fails sooner and the error is also about failing to enumerate (not just "This device cannot start.").

I found this thread on ST's forums, but it's unclear if it affects the STM32H503x: https://community.st.com/t5/stm32cubemx-mcus/missing-hal-pwrex-enablevddusb-when-generating-peripheral/m-p/719700

A few other people have also had difficulties with H5's USB: hathach/tinyusb#2203

@fpistm
Copy link
Member

fpistm commented May 26, 2025

USB is know to work on Nucleo H503RB with generic or dedicated target. I do not have this hardware so can't help on this.

Moved to [New Variant] request list #722.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new variant Add support of new bard
Projects
Development

No branches or pull requests

2 participants