[nrf fromlist] samples: sensor: qdec #2191
Closed
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
… cores Currently function `z_nrf_grtc_wakeup_prepare()` should be available only for the GRTC manager (`CONFIG_NRF_GRTC_START_SYSCOUNTER` is active). Upstream PR: zephyrproject-rtos/zephyr#73095 Signed-off-by: Adam Kondraciuk <[email protected]>
Fix typo in `PM_S2RAM_CUSTOM_MARKING` description. Upstream PR: zephyrproject-rtos/zephyr#73095 Signed-off-by: Adam Kondraciuk <[email protected]>
…vice Expands driver to cover nRF54L15 features like AIN as GPIO configuration, new reference voltage, different set of supported gain options. Signed-off-by: Karol Lasończyk <[email protected]> (cherry picked from commit 5f1fdc4)
…vice Expands driver to cover nRF54H20 features like 8bit sample width. Signed-off-by: Karol Lasończyk <[email protected]> (cherry picked from commit 13196ec)
Adds full description of the adc node and support for memory regions. Signed-off-by: Karol Lasończyk <[email protected]> (cherry picked from commit 15fa37d)
Adds configuration to play with nRF54H20 PDK board. Signed-off-by: Karol Lasończyk <[email protected]> (cherry picked from commit 3c4ea76)
Adds configuration for making tests work. Signed-off-by: Karol Lasończyk <[email protected]> (cherry picked from commit ba30517)
Enables adc node to make it usable in tests/examples. Signed-off-by: Karol Lasończyk <[email protected]> (cherry picked from commit a04b2ad)
Add support for gains: 1/2, 1/3, 2/5, 1/4. Upstream PR: zephyrproject-rtos/zephyr#74929 Signed-off-by: Karol Lasończyk <[email protected]>
…rted peripherals ADC driver was aligned to nrf54h20 target. Enable ADC Twister tests on that platform. Signed-off-by: Sebastian Głąb <[email protected]> (cherry picked from commit a3e1e39)
…m_allow Enable test execution on nrf54h20dk. Overlay file already exists. Signed-off-by: Sebastian Głąb <[email protected]> (cherry picked from commit cc9bd6d)
…tion on nrf54h20 Add overlay file for nrf54h20 cpuapp target. Add nrf54h20 target to platform_allow. Signed-off-by: Sebastian Głąb <[email protected]> (cherry picked from commit 48fc687)
This change removes the BT_LE_PER_ADV_OPT_USE_TX_POWER option for extended advertisement in BLE Audio PTS tests. The Broadcaster setup options was hardcoded to include the BT_LE_PER_ADV_OPT_USE_TX_POWER option. This causes incompabilities for any controller not support it, and since the option is not required for the audio tests it should not be used here. Upstream PR: zephyrproject-rtos/zephyr#73361 signed-off-by: Frode van der Meeren <[email protected]>
…on Subrating Add Kconfigs to enable experimental subrating HCI commands. Signed-off-by: Timothy Keys <[email protected]> (cherry picked from commit 570c86d) Signed-off-by: Timothy Keys <[email protected]>
Expand testing for QDEC at nrf platforms. It uses general sensor API, however there are also nrf driver specific assumptions. Upstream PR: zephyrproject-rtos/zephyr#74677 Signed-off-by: Piotr Kosycarz <[email protected]>
Extend nrf pwm driver test coverage by testing invalid port number Upstream PR: zephyrproject-rtos/zephyr#75583 Signed-off-by: Piotr Krzyzanowski <[email protected]>
…Connection Subrating" This reverts commit f6325a5. Signed-off-by: Rubin Gerritsen <[email protected]>
This patch removes all uses of the adv auto-resume feature in the host bsim tests, except for the test of that feature itself, and instead makes all adv starts explicit. The auto-resume feature is planned for deprecation. And, explicit starting of adv makes what happens in the test more explicit as well. Signed-off-by: Aleksander Wasaznik <[email protected]> (cherry picked from commit 765b244)
…_disable() Expectation: After calling `bt_disable()` it is possible to use the Bluetooth APIs as if `bt_enable()` was never called. This was not the case for `bt_id_create()`, it was not possible to set the default identity. This prevented an application developer to restart the stack as a different identity. Keys also need to be cleared to avoid the following pattern: 1. Pair two devices 2. Central calls `bt_disable()` and `bt_enable()`. The central will now generate a new identity address. 3. Connect the two devices. 4. Re-establish encryption. Now the central will try to use the previously used keys. The procedure will fail because the peripheral does not have any keys associated with the new central address. The API documentation is updated accordingly. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit 3ce106c)
… timeout Before this commit, the following bugs were present: - When `CONFIG_BT_FILTER_ACCEPT_LIST` was set, connection establishment was cancelled upon RPA timeout. This required the application to restart the initiator every RPA timeout. - When `CONFIG_BT_FILTER_ACCEPT_LIST` was not set, the RPA was not updated while the initiator was running. This commit unifies the RPA timeout handling for both these cases. Upon RPA timeout the initiator is cancelled and restarted when the controller raises the LE Connection Complete event. The workqueue state is checked when restarting the initiator to prevent it being restarted when the timeout is hit. Corresponding test cases have been added to ensure that this feature works. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit ff80c0b)
When using the post_init_f to initialize the `bst_result`, it is not possible to mark the test as passed immediately as the `bst_result` will be initialized after the test completes. This change should overcome this limitation. Bluetooth mesh tests are kept as is as we are not sure if this will change the behavior. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit 1aa33fe)
When reading the error message: "ASSERTION_FAIL: command opcode 0x0c03 timeout with err -11" it may not be obvious what is wrong with their setup unless you are very familiar with HCI. This commit adds some more documentation to make this more obvious. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit 3609d97)
These macros allows us to compare strings in a simpler way. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit a35d5e7)
…meout It seemed like there was lacking test coverage for this functionality. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit b30d2d1)
… RPA timeout zephyrproject-rtos/zephyr#72674 fixed a bug where this configuration did not work. Now that this configuration is tested, we should mark it as supported. The timeout check that was present in the code before was useless and was not working because the check was run before a default timeout of 0 was converted to a timeout. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit 9cf6839)
…llbacks
A naive implementation would look like
```c
void bt_init()
{
bt_le_conn_cb_register();
bt_enable();
}
```
When the app later adds the possibility to enable and disable
Bluetooth, it may happen that the application developer calls
`bt_init()` instead of `bt_enable()`. This results in invalid
behavior. This kind of bug is currently a bit harder to debug
as the callback register APIs do not reject registering a
callback twice.
Improving the API documentation is the first step towards making
this a bit more user friendly.
Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 2712b32)
This commit adds host support for the Path Loss Monitoring feature see Bluetooth Core specification, Version 5.4, Vol 6, Part B, Section 4.6.32. Limited logic is required, just adding a wrapper around the HCI command and callback for HCI event. Add new zone - BT_CONN_LE_PATH_LOSS_ZONE_UNAVAILABLE, to convert 0xFF path loss to a useful zone. Add new Kconfigs and functionality to the bt shell. Signed-off-by: Sean Madigan <[email protected]> (cherry picked from commit 0b327db)
This allows us to use functionality provided by slist. First use case: Avoid adding an element twice. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit 6e6bb26)
Callbacks can only be registered once. Otherwise the slist will become circular. In this commit we have choosen to ignore the second registration call if the callback has already been registed. The alternative is to trigger an assertion. That doesn't work if the assertions are turned off. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit 2ec3cd3)
This improves consistency with other callback lists like scan_cbs and pa_sync_cbs. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit 3eb975d)
If ATT sent callback is delayed until data transmission is done by BLE controller, the transmitted buffer may have an additional reference. The reference is used to extend lifetime of the net buffer until the data transmission is confirmed by ACK of the remote. send_buf function can be called multiple times, if buffer has to be fragmented over HCI. In that case, the callback is provided as an argument only for the last transmitted fragment. The `buf->ref == 1` check is skipped because it's impossible to properly validate number of references for the sent fragments if buffers may have the additional reference. Jira: NCSDK-28624 Signed-off-by: Marek Pieta <[email protected]>
A single trigger of the TASK_FREQ_CHANGE task might not be enough, so trigger twice to make sure the frequency gets updated. Signed-off-by: Karsten Koenig <[email protected]> (cherry picked from commit 16e7e46)
Allow CONFIG_NRF_APPROTECT_LOCK and CONFIG_NRF_SECURE_APPROTECT_LOCK with TF-M with all the SOC's that support TF-M. Signed-off-by: Markus Lassila <[email protected]> (cherry picked from commit c449684)
…g with TF-M RRAMC peripheral is a secure-only peripheral, and the application cannot use it directly. While building an application with TF-M enabled and SOC_FLASH_NRF_RRAM the NRFX_RRAMC selection must be forbidden. Signed-off-by: Arkadiusz Balys <[email protected]> (cherry picked from commit 2de6274)
…evant This commit moves reading nexthop's LL address only if it's supported by a given neighbor and can be used for routing between interfaces. Signed-off-by: Konrad Derda <[email protected]> (cherry picked from commit 5e4e63b)
It is safer to base the SUIT artifacts path on the path of the configuration file than the HEX file that is being flashed. The latter may be overriden by several scripts that merge/transform the final firmware image. Ref: NCSDK-26282 Upstream PR: zephyrproject-rtos/zephyr#76560 Signed-off-by: Tomasz Chyrowicz <[email protected]>
This commit adds thread 1.4 version. Upstream PR: zephyrproject-rtos/zephyr#76881 Signed-off-by: Maciej Baczmanski <[email protected]>
Remove the deprecated PSA_WANT_KEY_TYPE_ECC_KEY_PAIR Kconfig ref: NCSDK-27160 Signed-off-by: Markus Rekdal <[email protected]>
callback_list was renamed to conn_cbs in commit 3eb975d. However plm callback was missed due to it not being built anywhere. Signed-off-by: Sean Madigan <[email protected]> (cherry picked from commit 2e7c488) Upstream PR: zephyrproject-rtos/zephyr#76175 Signed-off-by: Sean Madigan <[email protected]>
…with plm Path loss monitoring was not being enabled anywhere, meaning that issues could be merged in without catching the issue. This commit adds a test case to build the shell with path loss monitoring enabled to catch issues. Signed-off-by: Sean Madigan <[email protected]> (cherry picked from commit 022d339) Upstream PR: zephyrproject-rtos/zephyr#76175 Signed-off-by: Sean Madigan <[email protected]>
…or plm Path loss monitoring does not work without LE Power Control also enabled in the controller, so update the dependencies in the kconfigs so path loss monitoring selects power control. Signed-off-by: Sean Madigan <[email protected]> (cherry picked from commit 2a46ede) Upstream PR: zephyrproject-rtos/zephyr#76175 Signed-off-by: Sean Madigan <[email protected]>
Commit fixes missing dependency for `ot diag cw` command for nrf5xx by adding default vale to `NRF_802154_CARRIER_FUNCTIONS`. Signed-off-by: Przemyslaw Bida <[email protected]> (cherry picked from commit a923a4a)
Version 5.5.1 of nrf-regtool is required for the IPC communication to/from secdom to work after the mbox compatible rename. This commit is to be removed when synchronizing sdk-zephyr with upstream zephyr and a newer version of nrf-regtool is required. Signed-off-by: Andreas Moltumyr <[email protected]>
Change pins that are used for qdec nrf54h20dk Signed-off-by: Piotr Krzyzanowski <[email protected]>
nordic-pikr
requested review from
a team,
alwa-nordic,
anangl,
ankuns,
carlescufi,
de-nordic and
nordic-krch
as code owners
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
61 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.
Change pins that are used for qdec nrf54h20dk
Upstream PR: zephyrproject-rtos/zephyr/pull/80562