DAP_PACKET_SIZE >= 256 not fully used
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
Hello,
while debugging #1871 I observed, that the possible packet sizes aren't used to full extent. Probe setup was to use 2048 bytes.
- read_ap_multi() limits its request to 64 bytes, resulting in a response with only 227 bytes
- flashing creates requests with a maximum of 334 bytes
Regards
Hardy
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 by tracing read_ap_multi() and the flashing request path, then inspect how DAP_PACKET_SIZE is applied with a 2048-byte probe setup. Reproduce the reported 64-byte read limit and 334-byte flashing limit; done means available packet capacity is used without producing invalid responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100