oxidecomputer / oxidecomputer/hubris

Allow for multiple names in memory definitions

Open
#1,247 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3.6k
Forks
239
Avg merge
1d 12h
Merged PRs (30d)
23

Description

It would be nice if we could specify names = ["a", "b", "stage0"] instead of repeating 3x:

[[sram3]]
name = "a"
address = 0x40102000
size = 0x1000
read = true
write = false
execute = false

[[sram3]]
name = "b"
address = 0x40102000
size = 0x1000
read = true
write = false
execute = false

[[sram3]]
name = "stage0"
address = 0x40102000
size = 0x1000
read = true
write = false
execute = false

(from here)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the example in chips/lpc55/memory.toml, especially the repeated sram3 definitions linked in the issue. Trace the configuration entry point that reads memory definitions and determine where a names array should be expanded. Done means the array syntax is accepted and produces the same equivalent memory definitions as repeated entries.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
embedded-iot
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.