Flash programming performance dropped
Open
Nobody has claimed this yet.
backlog
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
The changes to make the flash algo call sequence match the specification had a side effect of reducing flash programming performance by about 5 kB/s. This needs to be fixed by using a target-resident call sequencer.
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
The issue names no files or tests. Start by locating the flash algorithm call-sequence implementation and comparing it with the specification, then measure the reported programming-speed regression. The work is complete when a target-resident call sequencer restores performance without breaking the specified sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100