Sentinel value interaction with loadable flash addresses not clear
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Start at kernel.c line 26 and trace how the sentinel value is used with the flash app load address. Check the related relocation or load-address handling in this ePIC example to determine why the subtraction is needed. Done means adding a concise comment that explains the address adjustment and verifying that the example still builds.
Written by the indexing model from the issue text.
Description
I am unsure why the sentinel value is subtracted from the flash app load address in kernel.c. It doesn't seem to be re-added anywhere so does this mean that the flash image is loaded at a different address to the one specified or is this just to compensate for a fixed offset encoded into the relocations? Might be worth a comment explaining what is happening:
https://github.com/lowRISC/epic-c-example/blob/535d1a5fe2b1b5201d35612ae27ea7e5db02dee2/kernel.c#L26
- Dominant language
- C
- Stars
- 14
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from lowRISC/epic-c-example
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
lowRISC/epic-c-example#2 · 1 comment ·
All issues in lowRISC/epic-c-example
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Ryan-Millard/Img2Num#681 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tursodatabase/libsql#2285 ·