ARMmbed / ARMmbed/uvisor

Document the per-box memory layout

Open
#362 1 comment 0 reactions 0 assignees View on GitHub
mirrored
Dominant language
C
Stars
135
Forks
72
PR merge metrics
No merged PRs in 30d

Description

It's annoying to have to read the code or "be familiar with uVisor" in order to see what could be easily explained by a picture. We should document the per-box memory layout: what goes where in relation to each other. This means showing where exist the process heap, box context, process stack, box index, and so forth.

Contributor guide

Open the contributing guide

Research direction

The issue names no file or test; start by reading the uVisor memory-layout code and tracing the per-box regions listed in the request. Document their relative placement with a picture and labels covering the process heap, box context, process stack, box index, and other regions identified by the implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
documentation, embedded-iot
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.