2025-02-04 Ordinary Meeting Notes

Date

Feb 4, 2025

Disclosures

RISC-V Disclosure Video

Open

Participants

Agenda

• Participation and Voting Rights (link)

• Whitepaper update

  • Current version: fusa-whitepaper.20250204.draft.pdf

  • “Redundancy” chapter status [Thomas]

  • “Partitioning” chapter status [Sandro]

  • Introduction [Daniel]

    • First draft: fusa-whitepaper.20250204.introduction-draft.pdf

• RAS/RERI presentation and discussion [Thomas]

Minutes

• Disclosures

• Participation and voting rights reminder

• Daniel presents current status of the whitepaper and the proposed introduction (not final) for the document. Daniel requests feedback on the proposed introduction and the rest of the document.

• Thomas will provide the reviewed Redundancy shortly (before next meeting)

• Sandro will provide the reviewed Partitioning shortly (before next meeting)

• Thomas presents the RAS Error Register Reporting Interface (RERI) specification

  • Overall a good and scalable interface for reporting errors

  • Questions:

    • Daniel, Monia and Holger ask if errors codes more targeted for functional safety or relative domains (e.g. automotive) could be also standardized. Thomas doesn’t think so, SoC providers can define the ones that better match the actual SoC.

    • Srini asks if the error codes address the fail operational scenarios. Thomas thinks they are two different things, the error codes don’t define how the errors are handled (interrupts, FSMs, …) so no need to modify them for that.

    • Daniel asks if RERI like mechanisms are available in current non-RISCV designs. Thomas: Yes, since quite a while.

    • Daniel asks if guidelines for the RERI usage is something the SIG should work on. Thomas thinks is too dependent on the safety case, so not sure of its usefulness.

    • Holger asks which is the surface impact of a RERI mechanism, specially for small MCUs. Thomas, like the rest of participants, doesn’t know. Jon remarks that the size of the registers is pretty big, but an implementation is not forced to implement all the registers.

  • Thanks Thomas for the presentation.

• Meeting recording and transcript link

Presentations

Notes & Action Items