STM32H753 binary fails to run
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
I'm attempting to flash a very basic LED blinky app onto a NUCLEO-H753ZI. When I flash the board with pyOCD I see output indicating the flash was successful: Erased 131072 bytes (1 sector), programmed 54272 bytes (53 pages), skipped 0 bytes (0 pages). But the app doesn't appear to start even after issuing a reset command. I started stepping through the code and it appears to hit a hard fault somewhere during RCC init. The weird thing is that if I flash the same binary using probe-rs it runs without any issue, which makes me believe there's some problem in the flashing process itself rather than the binary.
pyOCD version: 0.36.0
CMSIS pack: Keil.STM32H7xx_DFP version 3.1.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure on a NUCLEO-H753ZI using pyOCD 0.36.0 and the Keil.STM32H7xx_DFP 3.1.1 pack, then compare the result with flashing the same binary through probe-rs. Trace the reset and RCC-init behavior after pyOCD reports a successful flash. Done means the flashed blinky application starts normally without hitting a hard fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100