-
Notifications
You must be signed in to change notification settings - Fork 1.4k
doc: Added user guide for nRF54H20 Ironside #22940
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: f422b426d1fb696c57e70e078101176f524f62e3 more detailssdk-nrf:
Github labels
List of changed files detected by CI (1)
Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
e8990e9
to
94ec585
Compare
7c56ea1
to
4d89d31
Compare
4d89d31
to
ab98c99
Compare
As discussed on chat, I won't review this @FrancescoSer until you poke me with information that the doc is ready for review. |
2442f40
to
27d5b64
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In its current form, this is a great documentation of hardware that does not however tell me how to work with IronSide SE in the nRF Connect SDK. I understand hardware parts cannot be moved to hardware datasheet, which is not available. However, the guide should include more information that ties it together with the software nRF Connect SDK documentation.
Global Resource configuration | ||
***************************** | ||
|
||
You can configure some global resources through the applications running on local domains (like the Application core). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can I configure this? The section does not give me a link.
|
||
IronSide SE provides the following features: | ||
|
||
* Global memory configuration (via UICR.MPCCONF) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Global memory configuration (via UICR.MPCCONF) | |
* Global memory configuration (through UICR.MPCCONF) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to be checked if still implemented
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IronSide doesn't currently apply UICR.MPCCONF. We have only defined the format/interface.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have to clarify how to configure UICRs then @jonathannilsen
|
||
IronSide SE provides the following features: | ||
|
||
* Global memory configuration (via UICR.MPCCONF) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that here you're not using any formatting for peripherals and registers, yet later you do use ``. As per https://nordicsemi.atlassian.net/wiki/spaces/TECHDOC/pages/120291747/Typographical+conventions no formatting is required -- caps are enough.
* ``ERASEPROTECT`` - Enables erase protection for the ``UICR``. | ||
* ``PROTECTEDMEM`` - Specifies a memory region, starting at the end of IronSide SE memory, that is protected for integrity. | ||
* ``RECOVERY`` - Contains the application-defined recovery mechanism details. | ||
* ``ITS`` - Sets the location and size of the Internal Trusted Storage for the application and radio domains. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does IronSide SE use and implement ITS?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jonathannilsen Is ITS implemented? I remember recent feedback about it not being implemented yet, but cannot find source.
4151028
to
c9383dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tomchy @FrancescoSer should we also add any chapter related to running MCUboot on Ironside?
Moving the BICR migration guide here: #23448 |
c9383dc
to
cde5048
Compare
@@ -0,0 +1,519 @@ | |||
:orphan: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: add feedback from Jon "The configuration nrf-regtool looks at is spread across the entire devicetree, for example it looks at the status property on the peripheral nodes and some properties like "owned-channels" etc. on specific node types like DPPIC. In general it tries to reuse existing DT properties where possible, so for example for GPIO pins it looks at all the pins that are referenced by peripheral nodes etc.
---- compile a list with the mapping between the devicetree and output in the PERIPHCONF"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jonathannilsen Just a reminder :)
Added user guide for nRF54H20 Ironside. Removed SUIT docs. Signed-off-by: Francesco Domenico Servidio <francesco.servidio@nordicsemi.no>
cde5048
to
f422b42
Compare
Added user guide for nRF54H20 Ironside.