Bluetooth Peripheral HIDS keyboard: nfct node enabled at board level #22695
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
github-actions
bot
added
manifest
changelog-entry-required
|
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 553d86e5157667ba06bd498c7a660557b84d0162 more detailssdk-nrf:
nrfxlib:
Github labels
List of changed files detected by CI (5)Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
kapi-no
force-pushed
the
bluetooth_peripheral_hids_keyboard_nfct_node_enabled_at_board_level
branch
from
6b97787 to
e53dea4
Compare
|
You can find the documentation preview for this PR here. |
kapi-no
force-pushed
the
bluetooth_peripheral_hids_keyboard_nfct_node_enabled_at_board_level
branch
from
e53dea4 to
40ad16f
Compare
nordic-piks
approved these changes
Jun 9, 2025
mkapala-nordic
approved these changes
Jun 13, 2025
maje-emb
approved these changes
Jun 17, 2025
Removed the application-level configuration that enables the NFCT node. The NFCT node is now enabled at the board level for all targets that support the NFCT peripheral. The previous workaround is not needed anymore. Ref: NCSDK-31691 This reverts commit d993161. Signed-off-by: Kamil Piszczek <[email protected]>
Removed the unnecessary DTS overlay that removes the NFCT node from the nRF54LV10 DK target. Signed-off-by: Kamil Piszczek <[email protected]>
Aligned the DTS configuration for the nfct node in the nRF54LM20 PDK board definition. The configuration is now aligned with its Zephyr upstream variant. Signed-off-by: Kamil Piszczek <[email protected]>
kapi-no
force-pushed
the
bluetooth_peripheral_hids_keyboard_nfct_node_enabled_at_board_level
branch
from
40ad16f to
1b62aff
Compare
|
Pure rebase after upmerge. The PR file diff has not changed |
anangl
approved these changes
Jun 17, 2025
Updated the nrfxlib revision to include the Kconfig improvements for the NFC T2T and T4T libraries. Signed-off-by: Kamil Piszczek <[email protected]>
kapi-no
force-pushed
the
bluetooth_peripheral_hids_keyboard_nfct_node_enabled_at_board_level
branch
from
1b62aff to
553d86e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
TODO
Upstream Zephyr PR: boards: nordic: Enable nfct on the supporting boards zephyrproject-rtos/zephyr#88637
CONFIG_HAS_HW_NRF_NFCTKconfig state for the nRF54H20 DK target: soc: nordic: nrf54h: Add option to use NFCT pins as GPIOs zephyrproject-rtos/zephyr#86280 (comment)Suggested fix: [nrf fromlist] soc: nordic: common: Fix HAS_HW_NRF_NFCT condition sdk-zephyr#2942