Vector35 / Vector35/binaryninja-api
Add support for C166 family of micro controllers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Datasheet here:
This covers the following variants:
• C161K, C161O, C161PI
• C161CS, C161JC, C161JI
• C163
• C164CI, C164SI, C164CM, C164SM
• C165
• C167CR, C167SR
• C167CS
• SAB 80C166, SAB 80C166W
• SAB 83C166, SAB 83C166W
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
Start by reading the attached c166ism.pdf datasheet and inspect the repository's existing architecture-support entry points and tests, though the issue does not name specific files. Map the listed C166 variants and determine the architecture behavior that must be supported. Done means Binary Ninja can analyze the listed microcontrollers with appropriate support and coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100