-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
doc: Release notes for 2.9.0-nRF54H20-1 #19715
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: f64b263cb47fb972ff925294d4794cb8aa710039 more detailssdk-nrf:
Github labels
List of changed files detected by CI (33)
Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
ed98a65
to
d64f1d9
Compare
d64f1d9
to
68f862c
Compare
68f862c
to
f5b745d
Compare
doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nRF54H20-1.rst
Outdated
Show resolved
Hide resolved
2ab556e
to
7f63324
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.
Please add the following note (as described in https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/releases/release-notes-changelog.html#bluetooth_le)
- Fixed an issue where Bluetooth applications built with the nordic-bt-rpc
snippet (in the :ref:bt_rpc
configuration) did not work on the nRF54H20 devices due to incorrect memory mapping.
PR: #20038
a546db2
to
f7802a5
Compare
f7802a5
to
cd4a2dc
Compare
|
||
To do that you can simply paste the following code snippet into your configuration files: | ||
|
||
.. code-block:: cfg | ||
|
||
CONFIG_SUIT_RECOVERY=y | ||
CONFIG_NRF_REGTOOL_GENERATE_UICR=n | ||
CONFIG_NRF_REGTOOL_GENERATE_BICR=n | ||
CONFIG_SOC_NRF54H20_GENERATE_BICR=n |
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.
I don't think the commits that transition away from using nrf-regtool
to generate BICR have been merged yet, from what I could tell they will be pulled in with the upmerge. Not sure what the plans are there, but unless that change will be part of this release, I believe the Kconfigs before the edit are still the correct ones to use.
doc/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nRF54H20-1.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nRF54H20-1.rst
Outdated
Show resolved
Hide resolved
336950b
to
9eaeb8b
Compare
9eaeb8b
to
2eeae26
Compare
doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nRF54H20-1.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nRF54H20-1.rst
Outdated
Show resolved
Hide resolved
2eeae26
to
b1f5750
Compare
b1f5750
to
ff617ce
Compare
Added release notes for 2.9.0-nRF54H20-1. Added migration guide for 2.9.0-nRF54H20-1. Added other release edits for 2.9.0-nRF54H20-1. Signed-off-by: Francesco Domenico Servidio <[email protected]>
ff617ce
to
f64b263
Compare
|
||
nrfutil device recover --core Application --serial-number <serial_number> | ||
nrfutil device recover --core Network --serial-number <serial_number> | ||
nrfutil device reset --reset-kind RESET_PIN --serial-number <serial_number> |
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.
The nrf-regtool
requirements in the NCS build system are incorrectly set for SoC binaries v0.9.0. The STM logging functionality does not work with the minimum required version of the nrf-regtool
and that is v8.0.0
. Should we mention in the migration guide that the user should migrate to the newest version of nrf-regtool
(v8.1.2
)?
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.
I would also recommend bumping the minimum required version in the build system so users of this NCS release will get a clear build failure if they attempt to build nRF54H projects with an incorrect nrf-regtool
version:
https://github.com/nrfconnect/sdk-zephyr/blob/main/modules/hal_nordic/CMakeLists.txt#L18
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.
See the similar migration note for the nrf-regtool from the NCS 2.8 migration guide:
Added release notes for 2.9.0-nRF54H20
Added migration guide for 2.9.0-nRF54H20
Added other minor release edits for 2.9.0-nRF54H20