Nrfx 5244 align i2 s tests to tdm #2315
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
Add entry for comparator drivers Signed-off-by: Bjarki Arge Andreasen <[email protected]> (cherry picked from commit e40fa89)
The comparator drivers area contains the following incorrect area: files: - include/zephyr/dt-bindings/clock/ and contains the following duplicate area: files: - include/zephyr/drivers/comparator/ this commit removes them. Signed-off-by: Bjarki Arge Andreasen <[email protected]> (cherry picked from commit 1635d77)
Add test suite which uses GPIO loopback to produce a "very low" and "very high" voltage at the positive input of the comparator using the output of a GPIO. The negative input is set to a voltage between the high and low output voltages of the GPIO using whichever internal reference is available to the comparator. Signed-off-by: Bjarki Arge Andreasen <[email protected]> (cherry picked from commit 3272db8)
Change integration_platform -> platform_allow to not build the shell test suite for all supported boards. Upstream PR: zephyrproject-rtos/zephyr#80049 Signed-off-by: Bjarki Arge Andreasen <[email protected]> (cherry picked from commit 0502189)
Update DK naming - NRF54L15PDK is deprecated. Signed-off-by: Bartlomiej Buczek <[email protected]> (cherry picked from commit 8cd361a)
…h20dk Change pins that are used for qdec nrf54h20dk to align with shield (loopbacks) used in internal CI. This change is needed to start qdec driver power management testing. Upstream PR #: 80562 Signed-off-by: Piotr Krzyzanowski <[email protected]>
We no longer render Doxygen content in Sphinx after the removal of breathe, so let's remove rst related aliases from Doxyfile. Also adjust some headers that contained rst content. Upstream PR: zephyrproject-rtos/zephyr#80362 Signed-off-by: Gerard Marull-Paretas <[email protected]> (cherry picked from commit b8cd03a1e512229cd60dc70b2cd038a087b808bb)
Doxygen was getting confused when expanding @kconfig (verbatim block within []). Upstream PR: zephyrproject-rtos/zephyr#80362 Signed-off-by: Gerard Marull-Paretas <[email protected]> (cherry picked from commit da385a518ec3dc4b87fafd07cd05f899d376dc18)
This reverts commit 52b1d22. Signed-off-by: Bartlomiej Buczek <[email protected]>
Tests are checking error codes returned from adc_read() and adc_channel_setup() used with invalid configurations. Signed-off-by: Bartlomiej Buczek <[email protected]> (cherry picked from commit da81490)
DCDC regulator on nRF54L may not always works as intended. Apply a fix addressing that. Upstream PR #: 80635 Signed-off-by: Nikodem Kastelik <[email protected]>
Let's run tests with security/privacy with the HW models acutually running the encryptions, so in case of missaligned keys tests fail. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 53adf2c)
Let's run tests with security/privacy with the HW models acutually running the encryption, so in case of missaligned keys tests fail. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 342e298)
Let's run tests with security/privacy with the HW models acutually running the encryptions, so in case of missaligned keys tests fail. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 9182a7e)
…cryption Let's run tests with security/privacy with the HW models acutually running the encryptions, so in case of missaligned keys tests fail. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 3726cf3)
Changed the scan option type from uint32_t to uint8_t. There are 2 reasons for this: 1) This reduces the size of the struct bt_le_scan_param. Since we are now storing two copies of scan parameters statically in the host, this is not insignficant. 2) This fixes a "hole" in the struct. There are no longer 3 empty octets between the `type` and the `options`, which caused valgrind warnings when using `memcpy` and `memcmp` of the struct. Currently we only need 8 bits for the options available. If additional options are added later, the field need to be increased. For the above reasons some additional refactoring my be required to avoid significant size increases and the valgrind issue. Signed-off-by: Emil Gydesen <[email protected]> (cherry picked from commit e1e4f2a)
Update the string formatter according to the type of the variables that it is printing to eliminate compilation warnings. Signed-off-by: Yong Cong Sin <[email protected]> Signed-off-by: Yong Cong Sin <[email protected]> (cherry picked from commit d250664)
…me in shell Added a timeout for active scans (instead of using the host's scan timeout) in the shell by submitting a k_work that stops the scan after a specified period. Fixes #78659 Signed-off-by: Babak Arisian <[email protected]> (cherry picked from commit d8c1d4d)
Currently, the bonding type of Authentication _Requirements parameter is always `Dedicated Bonding` if the device is pairing initiator. But if the bonding is performed during connection setup or channel establishment as a precursor to accessing a service, the bonding type should be `General bonding`. Add a flag BT_CONN_BR_GENERAL_BONDING. Set the flag if the bonding is performed in the L2CAP_BR/RFCOMM channel establishment. Set bonding type depends on the flag when receiving IO cap request. Signed-off-by: Lyle Zhu <[email protected]> (cherry picked from commit 08ceb14)
Add a function bt_get_bondable to get the bonding setting. Signed-off-by: Lyle Zhu <[email protected]> (cherry picked from commit c0ce5b4)
Correct the `help` of the configuration `BT_BONDABLE`. Signed-off-by: Lyle Zhu <[email protected]> (cherry picked from commit 0ed8866)
The timeout state is local and can block new ATT operations, but does not affect the remote side. Disconnecting the GATT connection upon ATT timeout simplifies error handling for developers. This reduces rare failure conditions to a common one, without needing special cases for ATT timeouts. Signed-off-by: Pavel Vasilyev <[email protected]> (cherry picked from commit f712bde)
This commit tests that the host correctly disconnects from peer when ATT timeout happens. Signed-off-by: Pavel Vasilyev <[email protected]> (cherry picked from commit f7e8a87)
…nd_buf" This reverts commit 687cefa. Signed-off-by: Pavel Vasilyev <[email protected]>
…p_send_pdu" This reverts commit b0ce7fe. Signed-off-by: Pavel Vasilyev <[email protected]>
…ng PDU In case of UATT, if a connection was lost while user was holding a read or write attribute callback, `bt_l2cap_send_pdu` (called from `att.c::chan_send`) will anyway queue a PDU and trigger tx work. The PDU won't be sent eventually, but neither will hold an error code, which will allow it to bypass the error check in `att_on_sent_cb` and call `att_sent` function. For EATT `bt_l2cap_chan_send` is used which already handles this case and the error code is passed to `att_on_sent_cb`. This change adds connection state check to `bt_l2cap_send_pdu` preventing from unnecessary code execution when connection does not exist anymore. Signed-off-by: Pavel Vasilyev <[email protected]> (cherry picked from commit 74972e6)
Allow for an additional buffer reference if callback is provided. This can be used to extend lifetime of the net buffer until the data transmission is confirmed by ACK of the remote. Signed-off-by: Marek Pieta <[email protected]>
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]>
This commit adds a warning and a Kconfig option to `bt_conn_le_create` and `bt_conn_le_create_synced` functions which are meant to warn a user of a potential leakage of an active connection object. This change is implemented due to frequent incorrect use of the connection pointer where a pointer to an existing connection object is overwritten by `bt_conn_le_create` and `bt_conn_le_create_synced` functions which in turns leads to sporadic critical bugs. See zephyrproject-rtos/zephyr#78284 (comment) for more details. The Kconfig option is introduced instead of always returning the error to not affect current implementations. However, it is recommended to keep this option enabled to avoid potential bugs. Signed-off-by: Pavel Vasilyev <[email protected]> (cherry picked from commit 8acb1cc)
…it test Add a test that checks behavior of CONFIG_BT_CONN_CHECK_NULL_BEFORE_CREATE Kconfig option. Signed-off-by: Pavel Vasilyev <[email protected]> (cherry picked from commit 1fbcc0e)
Extract code useful for an RTIO implementation to a separate file. Signed-off-by: Jordan Yates <[email protected]> (cherry picked from commit 0218b36)
Change the callback context to the dev pointer instead of the data pointer, as the dev pointer is needed by RTIO. Signed-off-by: Jordan Yates <[email protected]> (cherry picked from commit 627be7d)
Add native support for RTIO to the TWIM hardware IP. Signed-off-by: Jordan Yates <[email protected]> (cherry picked from commit f443363)
…DARD Instead of forcing a definition in Devicetree. Right now, SoC DT files contain this default, but it should not be part of SoC DT files. Signed-off-by: Gerard Marull-Paretas <[email protected]> (cherry picked from commit 92c3495)
Device driver now defaults to I2C_BITRATE_STANDARD if not specified. Signed-off-by: Gerard Marull-Paretas <[email protected]> (cherry picked from commit 4e5df11)
This reverts commit 4081b2e. Signed-off-by: Carles Cufi <[email protected]> (cherry picked from commit 9643ca2)
See zephyrproject-rtos/hal_nordic#257. Signed-off-by: Carles Cufi <[email protected]> (cherry picked from commit e92323f)
Update the HW models module to: 42737c8ec8485987c7c9b0262b136de623e1ded2 Including the following: 42737c8 TIMER: Support devices without TASK_SHUTDOWN nrfx3.9 MDK 8.68 5fe6873 54 UARTE: Add frametimeout functionality dc086d7 UARTE: Add basic 54 support b046745 UARTE: Support better not having UART functionality 1c5f58c README: Mention the nRF54L15 models cover the L10 and L05 597c7d0 TEMP: Also build hal replacement for 54 and define NRF_TEMP_NS/S fb2ca83 Makefile: Let's build libraries (specially HAL) as pic 200a1e3 Makefiles: move some common options to common snippet Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 30f0d85)
…ith nrfx3.9
Update the HW models module to:
3cfca0192ff84da919e9bc7978bcc2239cd6a395
This includes 2 changes:
* 3cfca01 UART: Model more accurately TASKS_FLUSH behaviour
* 25cbd28: 54L15: Change CLOKPOWER IRQ line (MDK 8.68, nrfx 3.9.0)
WARNING! This change breaks backwards compatibility with SW
which expected this line to be 270 for 54L15 devices,
and therefore with MDKs < 8.68 & nrfx < 3.9.0.
This change requires updating to the MDK >=8.68 and nrfx >=3.9.0
if building using the 54L15 models.
52 and 53 models are not affected.
Change the CLOCK_POWER interrupt line from 270 to 261.
This has changed in the latest MDK (8.68) and the new
value is used in the latest nrfx (3.9.0) drivers.
Signed-off-by: Alberto Escolar Piedras <[email protected]>
(cherry picked from commit ef55d65)
TASK_SHUTDOWN was deprecated in newer SOCs and now removed in MDK 8.68 (nrfx 3.9.0) Signed-off-by: Alberto Escolar Piedras <[email protected]> Signed-off-by: Vinayak Kariappa Chettimada <[email protected]> (cherry picked from commit 4294814)
There are many common options to all ICs of the 54L series. Consolidate them in a single entry so that they do not need to be re-typed for each SoC series member. Signed-off-by: Carles Cufi <[email protected]> (cherry picked from commit 0b3a150)
These two new ICs are variants of the nRF54L15 with different memory sizes: - nRF54L05: 500KB RRAM, 96KB RAM - nRF54L10: 1022KB RRAM, 192KB RAM - nRF54L15: 1524KB RRAM, 256KB RAM Signed-off-by: Carles Cufi <[email protected]> (cherry picked from commit e788320)
Use the rather logical convention for the name that is applied to other Nordic boards: <board>_common.dtsi for definitions that are common to the board itself (LEDs, buttons, etc). Signed-off-by: Carles Cufi <[email protected]> (cherry picked from commit 1b84958)
…L05 and L10 ICs The nRF54L05 and nRF54L10 are identical to the nRF54L15 except for their memory sizes. Add support for emulating those ICs on the nRF54L15DK. This commit only adds support for the main application core. Support for the FLPR core may be added later. Signed-off-by: Carles Cufi <[email protected]> (cherry picked from commit 2147577)
This adds the nrf54l15dk/nrf54l15/cpuapp/ns board variant to sdk-zephyr. It allows to build nRF54l15dk with TF-M in nRF Connect SDK. This is done as a noup as the out-of-tree board extension feature is not available. When zephyrproject-rtos/zephyr#69548 is completed this commit can be reverted and the variant be placed in sdk-nrf. Signed-off-by: Tomi Fontanilles <[email protected]> (cherry picked from commit 6b4c840)
This is a long-term noup patch because crypto driver support is NCS-only for both cryptocell and CRACEN. Set HAS_HW_NRF_CC3XX to be defined in NS build when cryptocell is accessed through the PSA API. We need to know which CC3XX features are available. Set PSA as the entropy source for 54L. PSA is the only NCS-supported interface to CRACEN. Signed-off-by: Georgios Vasilakis <[email protected]> Signed-off-by: Joakim Andersson <[email protected]> Signed-off-by: Dominik Ermel <[email protected]> Signed-off-by: Sebastian Bøe <[email protected]> Signed-off-by: Robert Lubos <[email protected]> Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit d643f17)
The SoftDevice Controller is a different controller than the open source link layer with a different set of quirks. It should therefore have its own device tree binding. This commit converts the SoftDevice Controller driver to use this new DTS binding instead of reusing the existing one. This commit updates or adds additional overlays for existing samples, applications and tests that were using the open source link layer. Signed-off-by: Rubin Gerritsen <[email protected]> (cherry picked from commit 8d6a853)
…54l05 counter_basic_api, i2s_api, i2s_speed, uart_async_api Upstream PR #: 82028 Signed-off-by: Piotr Kosycarz <[email protected]>
…05 and L10 This is a follow-up to 2147577, extending the number of tests and samples that use the new L05 and L10. (cherry picked from commit b06bf51) Signed-off-by: Carles Cufi <[email protected]>
Basic verification of output. Upstream PR #: 81706 Signed-off-by: Piotr Kosycarz <[email protected]>
…for nrf54l15 flpr Missing after PDK->DK. Upstream PR #: 82200 Signed-off-by: Piotr Kosycarz <[email protected]>
Add Kconfig options for TDM130 and TDM131. Upstream PR #: 82144 Signed-off-by: Adam Kondraciuk <[email protected]>
Add HAL glue Kconfig options for TDM130 and TDM131. Upstream PR #: 82144 Signed-off-by: Adam Kondraciuk <[email protected]>
Add support for configuring pins of the nRF TDM peripheral. Upstream PR #: 82144 Signed-off-by: Adam Kondraciuk <[email protected]>
Add TDM130 and TDM131 nodes. Upstream PR #: 82144 Signed-off-by: Adam Kondraciuk <[email protected]>
Add a shim that allows using the nRF TDM (Time division multiplexed audio interface) HAL by I2S Zephyr API. Upstream PR #: 82144 Signed-off-by: Adam Kondraciuk <[email protected]>
Signed-off-by: Adam Kondraciuk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
67 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.
No description provided.