-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: fast_pair: Describe nRF54H20 support #19269
Conversation
Release notes will be moved to release notes PR once they are approved here. |
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publish GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 6e5f1aef8fcdee9d68a86572677045c2a002ced1 more detailssdk-nrf:
Github labels
List of changed files detected by CI (4)
Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
When building the Fast Pair in the |NCS|, the build system automatically calls the Fast Pair provision script and includes the resulting hexadecimal file in the final firmware hexadecimal file that can be flashed onto the device. | ||
For devices with the :ref:`partition_manager` support for which the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option is automatically enabled by the Fast Pair build system, the ``bt_fast_pair`` partition is automatically created by the build system. | ||
For other devices, you must declare the ``bt_fast_pair_partition`` partition manually in the device tree. | ||
See :file:`samples/bluetooth/fast_pair/input_device/boards/nrf54h20dk_nrf54h20_cpuapp.overlay` for example how it can be done. |
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.
When building the Fast Pair in the |NCS|, the build system automatically calls the Fast Pair provision script and includes the resulting hexadecimal file in the final firmware hexadecimal file that can be flashed onto the device. | |
For devices with the :ref:`partition_manager` support for which the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option is automatically enabled by the Fast Pair build system, the ``bt_fast_pair`` partition is automatically created by the build system. | |
For other devices, you must declare the ``bt_fast_pair_partition`` partition manually in the device tree. | |
See :file:`samples/bluetooth/fast_pair/input_device/boards/nrf54h20dk_nrf54h20_cpuapp.overlay` for example how it can be done. | |
When building Fast Pair in the |NCS|, the build system automatically calls the Fast Pair provision script. | |
It then includes the resulting hexadecimal file in the final firmware that you can flash onto the device. | |
For devices that support :ref:`partition_manager` and have the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option automatically enabled by the Fast Pair build system, the system also automatically creates the ``bt_fast_pair`` partition. | |
For other devices, you must declare the ``bt_fast_pair_partition`` partition manually in the devicetree. | |
To see how to do this, refer to the example in the :file:`samples/bluetooth/fast_pair/input_device/boards/nrf54h20dk_nrf54h20_cpuapp.overlay` file. |
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.
@annwoj edited your suggestion a bit. Active voice and device tree -> devicetree
@@ -556,6 +560,9 @@ Bluetooth libraries and services | |||
* Updated the :c:func:`bt_hogp_rep_read` function to forward the GATT read error code through the registered user callback. | |||
This ensures that API user is aware of the error. | |||
|
|||
* :ref:`bt_fast_pair_readme` library: |
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 entries should be moved to the release notes PR, as it's already open
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 this one #19241, please. As a comment.
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.
Yes, I want to get approves here and then I will move it to the release notes PR.
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 #19241 is merged now. Hence, we could keep this entry in the PR itself.
@@ -167,7 +167,7 @@ Partition Manager | |||
----------------- | |||
|
|||
The Fast Pair provisioning data is preprogrammed to a dedicated flash memory partition. | |||
The GFPS selects the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option to enable the :ref:`partition_manager`. | |||
For targets that have the :ref:`partition_manager` support, the GFPS selects the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option to enable the :ref:`partition_manager`. |
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.
For targets that have the :ref:`partition_manager` support, the GFPS selects the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option to enable the :ref:`partition_manager`. | |
For targets that support the :ref:`partition_manager`, the GFPS selects the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option to enable it. |
@@ -556,6 +560,9 @@ Bluetooth libraries and services | |||
* Updated the :c:func:`bt_hogp_rep_read` function to forward the GATT read error code through the registered user callback. | |||
This ensures that API user is aware of the error. | |||
|
|||
* :ref:`bt_fast_pair_readme` library: | |||
* Added support in build system for devices that do not support the :ref:`partition_manager`. |
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.
* Added support in build system for devices that do not support the :ref:`partition_manager`. | |
* Added support in build system for devices that do not support the :ref:`partition_manager`. | |
The :ref:`zephyr:nrf54h20dk_nrf54h20` board target is the only example of such a device. |
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'd like to add this entry to NCS 2.9.0 release changelog, because the support is already introduced in this release. @peknis, what is the process for that?
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.
Remove the changelog entry from this PR and add it as a comment to #19240, if this is going to 2.9.0 (not 2.9.0-nRF54H20).
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.
Done here: #19240 (review).
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
@@ -646,7 +653,7 @@ This section provides detailed lists of changes by :ref:`integration <integratio | |||
Google Fast Pair integration |
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.
My small observation (for technical writers):
We had this "Integrations" section in NCS 2.7 documentation but removed it for NCS 2.8.
It seems that it is back again.
I think we should consistently use one solution. It may be confusing to the users to sometimes report these updates in the "Integrations" section and other times in the "Documentation" section.
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.
@divipillai, what should we do with that?
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 process we follow is, While create the release notes PR, if there are no entries for a section, we remove that section. This could have been the case. But, the team can surely point to the correct sections the entries belong to (or add new sections) like we normally do for the Changelog file.
In this case, I agree, we should keep updates in one place and would say the "Integrations" section would be apt.
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.
Okay, thanks! I'm leaving it as is then.
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.
Maybe, I wasn't specific enough.
In NCS 2.7 we documented the changes to the Google Fast Pair integration guide as part of the Integrations section.
In NCS 2.8 we documented the changes to the same content (the Google Fast Pair integration guide) as part of the Documentation section.
bbe654f
to
64b6671
Compare
64b6671
to
c5bc993
Compare
Addressed review comments. |
c5bc993
to
ce8f063
Compare
Rebased on main. |
ce8f063
to
26978b8
Compare
* :ref:`fast_pair_input_device` sample: | ||
|
||
* Added support for the :ref:`zephyr:nrf54h20dk_nrf54h20` board target. | ||
|
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.
This part I would also like to add to 2.9.0 release.
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.
26978b8
to
db76ab5
Compare
Removed entries that should be added to 2.9.0 release changelog. |
|
||
Partition definition using the Devicetree (DTS) | ||
----------------------------------------------- | ||
For devices that don't support :ref:`partition_manager`, you must declare the ``bt_fast_pair_partition`` partition manually in the devicetree. |
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.
For devices that don't support :ref:`partition_manager`, you must declare the ``bt_fast_pair_partition`` partition manually in the devicetree. | |
For devices that do not support :ref:`partition_manager`, you must declare the ``bt_fast_pair_partition`` partition manually in the devicetree. |
Partition definition using the Devicetree (DTS) | ||
----------------------------------------------- | ||
For devices that don't support :ref:`partition_manager`, you must declare the ``bt_fast_pair_partition`` partition manually in the devicetree. | ||
Currently the :ref:`zephyr:nrf54h20dk_nrf54h20` board is the only device that requires manual partition definition. |
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.
Currently the :ref:`zephyr:nrf54h20dk_nrf54h20` board is the only device that requires manual partition definition. | |
Currently, the :ref:`zephyr:nrf54h20dk_nrf54h20` is the only device that requires manual partition definition. |
@@ -167,7 +167,8 @@ Partition Manager | |||
----------------- | |||
|
|||
The Fast Pair provisioning data is preprogrammed to a dedicated flash memory partition. | |||
The GFPS selects the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option to enable the :ref:`partition_manager`. | |||
For targets that support the :ref:`partition_manager`, the GFPS selects the :kconfig:option:`CONFIG_PM_SINGLE_IMAGE` Kconfig option to enable it. | |||
The :ref:`zephyr:nrf54h20dk_nrf54h20` board target is the only example of a device that doesn't support it. |
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 :ref:`zephyr:nrf54h20dk_nrf54h20` board target is the only example of a device that doesn't support it. | |
The :ref:`zephyr:nrf54h20dk_nrf54h20` is the only device that does not support this feature. |
* Added instruction on how to provision the Fast Pair data onto devices without the :ref:`partition_manager` support. | ||
The :ref:`zephyr:nrf54h20dk_nrf54h20` board target is the only example of such device. |
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.
* Added instruction on how to provision the Fast Pair data onto devices without the :ref:`partition_manager` support. | |
The :ref:`zephyr:nrf54h20dk_nrf54h20` board target is the only example of such device. | |
* Added instructions on how to provision the Fast Pair data onto devices without the :ref:`partition_manager` support, specifically for the :ref:`zephyr:nrf54h20dk_nrf54h20`. |
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.
SML update should be done as part of a separate PR that is cherry-picked into NCS 2.9
Partition definition using the Devicetree (DTS) | ||
----------------------------------------------- | ||
For devices that don't support :ref:`partition_manager`, you must declare the ``bt_fast_pair_partition`` partition manually in the devicetree. | ||
Currently the :ref:`zephyr:nrf54h20dk_nrf54h20` board is the only device that requires manual partition definition. |
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.
Wouldn't write that as we will have to maintain it with every new board. Maybe change that nrf54h20 is an example of SoC which uses it
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'd leave it as is and remove this sentence completely once new target without partition manager support appears.
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 this line of code:
select PM_SINGLE_IMAGE if !(SOC_SERIES_NRF54HX) |
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.
ok :)
Jira: NCSDK-30350 Signed-off-by: Aleksander Strzebonski <[email protected]>
db76ab5
to
6e5f1ae
Compare
@peknis, please rereview :) |
Jira: NCSDK-30350