nrf-regtool 7.0.0 + nordic,access + J-Link scripts #2075
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NordicBuilder
requested review from
jaz1-nordic,
kl-cruz,
magp-nordic,
masz-nordic and
nika-nordic
57300
force-pushed
the
nordic-owned-memory-update-ncs
branch
from
ef42493 to
94828a2
Compare
57300
force-pushed
the
nordic-owned-memory-update-ncs
branch
2 times, most recently
from
c659a97 to
32fc68f
Compare
|
Please update all commits to fromtree |
57300
force-pushed
the
nordic-owned-memory-update-ncs
branch
from
32fc68f to
982297e
Compare
57300
changed the title
anangl
approved these changes
Oct 15, 2024
57300
force-pushed
the
nordic-owned-memory-update-ncs
branch
from
982297e to
7723959
Compare
NordicBuilder
requested review from
hubertmis,
krish2718,
nordic-krch,
rajb9,
sachinthegreen,
srkanordic and
udaynordic
57300
changed the title
jonathannilsen
approved these changes
Oct 16, 2024
57300
force-pushed
the
nordic-owned-memory-update-ncs
branch
from
7723959 to
fe04ab1
Compare
57300
changed the title
57300
force-pushed
the
nordic-owned-memory-update-ncs
branch
2 times, most recently
from
19ef544 to
fd123a5
Compare
|
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
57300
changed the title
57300
changed the title
…DACv2 Version 2 of the ADAC interface implemented by secure domain firmware changes the ADAC RESET command used in the custom reset handling in the JLink support scripts. The command has been split into two commands, RESET and START, and has different semantics from the previous RESET command. The new RESET command resets both the application and radio domains without starting the CPUs again, and the START command must then be used to start the CPUs. Update the JLink support scripts for nrf54h20dk/nrf54h20/cpuapp, nrf54h20dk/nrf54h20/cpurad, nrf9280pdk/nrf9280/cpuapp and nrf9280pdk/nrf9280/cpurad so that they read out the ADAC interface version from the device and use the newer commands if ADAC version 2 is detected. If the version is lower than 2, the legacy implementation is used. Also improve the CTRL-AP MAILBOX transaction implementation to avoid the need for arbitrary sleeps or unnecessary polling of the MAILBOX. This should improve stability when using the script. Signed-off-by: Jonathan Nilsen <[email protected]> (cherry picked from commit d403d73)
…er for cpurad Some tests are failing on nrf54h20 cpurad in non-obvious manner because of this memory region being too small. Instead of adding overlays to each individual application, make this region larger at expense of cpuapp equivalent. Signed-off-by: Nikodem Kastelik <[email protected]> (cherry picked from commit e0860eb)
This concerns both `nordic,owned-memory` and `nordic,owned-partitions`. Introduce a property named `nordic,access`, which is meant to replace the `owner-id` and `perm-*` properties. It allows for describing how multiple domains should access a single memory region, possibly with different permissions per owner, but without having to create more than one DT node for this purpose. This change is also motivated by updated memory protection requirements on the nRF54H20, which mandate that a given memory region must only be reserved by one domain, even if multiple domains can have access to it. This restriction is now described in the binding itself. Signed-off-by: Grzegorz Swiderski <[email protected]> (cherry picked from commit 365e9d6)
… bindings Apply the following changes to `nrf54h20dk` and `nrf9280pdk`: * Convert `perm-*` properties to the newly introduced `nordic,access`, both in board files and tests. * Redefine shared regions to specify multiple access owners per node, and ensure that each such region is reserved by one domain at a time. `cpuapp_cpurad_ram0x_region` is only enabled by Radiocore, while `cpuapp_cpucell_ram0x_region` is only enabled by Application core. * Divide `shared_ram3x_region` so that each sub-region is owned by a different domain. Their addresses must be rounded down to fit the current UICR format. Signed-off-by: Grzegorz Swiderski <[email protected]> (cherry picked from commit 13b1cfa)
Update the default memory maps for `nrf54h20dk` and `nrf9280pdk` to remove the `shared_ram20_region` and `shared_ram3x_region` nodes, because their child nodes no longer need to be grouped together: * IPC buffers in RAM20 are statically allocated. * DMA buffers in RAM3x have separate access owners. Signed-off-by: Grzegorz Swiderski <[email protected]> (cherry picked from commit 85b0394)
This reverts commit 30b5300. Signed-off-by: Grzegorz Swiderski <[email protected]>
Upstream PR: zephyrproject-rtos/zephyr#79925 This new version introduces a new sub-command `uicr-compile`, which will generate `uicr.hex` based on a new binary format required by an upcoming release of Secure Domain Firmware (SDFW) closer to production. Since this is a breaking change, and SDFW is not finalized yet, we need to support two nrf-regtool versions for a short time, and use different CLI invocations based on which version is installed. Hence, the minimum required version is unchanged. Additionally, retire CONFIG_NRF_REGTOOL_EXTRA_GENERATE_ARGS. There will be no use for it moving forward. Signed-off-by: Grzegorz Swiderski <[email protected]> (cherry picked from commit 6c4eb43567fc82935ccff21ebfe843ccc1ac88e1)
This will be replaced by a different solution upstream (NCSDK-27673). Migrate the existing BICR bindings from NCS 2.4.99-cs3 to NCS 2.7.0. They are updated to remove obsoleted values. Enable generating bicr.hex for Application core by default. LFXO CLOAD value is a resualt of DK's characterization. The BICR LFOSC.LFXOCONFIG.MODE field supports disabling the usage of an external crystal oscillator to disable LFXO as LF clock source. Signed-off-by: Grzegorz Swiderski <[email protected]> Signed-off-by: Karol Lisak <[email protected]> Signed-off-by: Karsten Koenig <[email protected]>
57300
force-pushed
the
nordic-owned-memory-update-ncs
branch
from
fd123a5 to
5952fe7
Compare
carlescufi
approved these changes
Oct 17, 2024
|
was there no sdk-nrf manifest PR for this change? edit: sry, not sure how i missed it. |
It's this one: nrfconnect/sdk-nrf#17717 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
manifest-pr-skip