Something wrong with compute_crcs
Open
Nobody has claimed this yet.
backlog
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
https://github.com/mbedmicro/pyOCD/blob/b26ea75b525a526a4925ef45770482c490d11b1e/pyocd/flash/flash.py#L154-L163
Try some pairs of addr and size
For example STM32 have a flash at 0x08000000 and sector 2048 bytes. So we got 10000000B as result.
I can't find source of analyzer to understand how it works.
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
Start with pyocd/flash/flash.py lines 154-163 and trace the analyzer referenced by compute_crcs. Reproduce the reported STM32 address and sector-size case, then compare results across several addr and size pairs. Done means the CRC behavior is understood and any incorrect result is covered by an appropriate correction or explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100