Mixing fixed position and PIC apps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 59
- Avg merge
- 20h 33m
- Merged PRs (30d)
- 2
Description
Tockloader currently has 2 separate paths for flashing: one for when all apps are PIC and can go anywhere in the flash, and one for when all have fixed positions in the flash (possibly multiple fixed positions).
This separation fundamentally doesn't have to exist, because (presumably) Tock kernel can make sense out of applications and where to put them if it gets a mix of both.
With libtock-c producing PIC binaries, and libtock-rs producing only fixed ones, until this issue is solved, programs using them cannot coexist.
I'm creating this issue as a place to discuss solving this.
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 tracing Tockloader's two flashing paths and reviewing how the Tock kernel places applications. Consider the interaction between PIC binaries from libtock-c and fixed-position binaries from libtock-rs. Done means both kinds of applications can coexist and be flashed successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100