Skip to content

Conversation

VIPQualityPost
Copy link
Contributor

Adding the "new" STM32H503 with nucleo (these are already supported in stm32duino).

@VIPQualityPost
Copy link
Contributor Author

@valeros same for this one 😄

@valeros
Copy link
Member

valeros commented Feb 4, 2025

Hi @VIPQualityPost, thanks for the PR. The latest stable OpenOCD doesn’t support the H5 family, and we don’t use any OpenOCD forks. So, basically, you’ll have to drop st-link and cmsis-dap from the list of upload protocols. That means the board will need to be programmed either through mass storage (which I think the latest ST-Links support) or using an external J-Link debug probe, but that’s going to make the developer experience pretty inconvenient.

},
"frameworks": [
"arduino",
"stm32cube"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

btw, NUCLEO_H503RB is supported in mbed-ce, so you can add mbed-ce to the frameworks if #863 merges first.

@multiplemonomials
Copy link

multiplemonomials commented Sep 14, 2025

fwiw, I think pyocd actually does support these boards now, even though openocd and st-link still do not. So you might want to try adding cmsis-dap as an upload protocol. Though if platformio is still using an old pyocd version that may not be the case.

@VIPQualityPost
Copy link
Contributor Author

I wasn't really paying attention to this PR anymore because of this comment: #853 (comment)

Did the 'new' method for supporting generic hardware get implemented yet? ( @valeros )
I didn't plan to do any changes here until the plan is set for the new support scheme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants