lnls-dig / lnls-dig/openMMC

Configure VADJ according to the FMC FRU information

Open
#85 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C
Stars
46
Forks
34
PR merge metrics
No merged PRs in 30d

Description

In the current state, the firmware has a hard-coded VADJ level (2.5V) upon payload initialization.
This configuration should ideally be read from the FMC FRU information storage (EEPROM), which contains all power supplies voltages and tolerances descriptions.

Contributor guide

No contributing guide indexed for this repository

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 by tracing payload initialization and locating the FMC FRU information storage and EEPROM access paths. Determine how the FRU power-supply voltage and tolerance descriptions can provide VADJ instead of the hard-coded 2.5V value; done means VADJ is configured from the FMC FRU information during initialization.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.