particle-iot / particle-iot/binary-version-reader
As a device owner, I'd like to be able to dump a memory region containing a module view the metadata
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 4
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 1
Description
The key difference with this usecase is that the file length will longer than the actual module, so the real module length should be determined from the start-end address metadata, which is then used to determine the location of the module suffix info.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named in the issue. Start at the module-parsing entry point and trace how a dumped memory region is interpreted, then identify how the start and end address metadata can determine the actual module length and the suffix-info location. Done means a longer dump is parsed using the real module boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- embedded-iot, reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100