-
Notifications
You must be signed in to change notification settings - Fork 621
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
tests: bluetooth: tester: build with sysbuild #2011
Draft
AyturkDuzen
wants to merge
614
commits into
nrfconnect:main
Choose a base branch
from
AyturkDuzen:bluetoth_tester_sysbuild_downstream
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
tests: bluetooth: tester: build with sysbuild #2011
AyturkDuzen
wants to merge
614
commits into
nrfconnect:main
from
AyturkDuzen:bluetoth_tester_sysbuild_downstream
Conversation
This file contains 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
Upstream PR: zephyrproject-rtos/zephyr#75768 Add a new offload API to reset Wi-Fi statistics from the Wi-Fi driver. Signed-off-by: Kapil Bhatt <[email protected]>
Upstream PR: zephyrproject-rtos/zephyr#75768 Add "reset" as a subcommand of wifi statistics. Also add help option in statistics command. Signed-off-by: Kapil Bhatt <[email protected]>
…mits are provided Current implementation will not work if comits were not provided. ie. use case with list of changed files will fail as args.commits is None. Upstream PR: zephyrproject-rtos/zephyr#75927 Signed-off-by: Piotr Kosycarz <[email protected]>
Upstream PR: zephyrproject-rtos/zephyr#72857 In the `Board` class, the `dir` member was renamed to `directories`, both to indicate that it is now a list (in HWMv2 with board extensions) and to reflect the addition of the `BOARD_DIRECTORIES` CMake variable. Considering that the build system also keeps the `BOARD_DIR` variable, and for the sake of backwards compatibility and brevity, it should be useful to retain `Board.dir` in Python as well, symmetrically. Signed-off-by: Grzegorz Swiderski <[email protected]> (cherry picked from commit 25fd4b16e8c488792d0d8450e1b822292f94d3c3)
Upstream PR: zephyrproject-rtos/zephyr#72857 `Board.dir` can be used in place of `Board.directories[0]` for brevity. Signed-off-by: Grzegorz Swiderski <[email protected]> (cherry picked from commit 103f7b59548cf5d809d1f105c5c0e2e94396cdfc)
Add triggers for SUIT DFU tests. Signed-off-by: Krzysztof Szromek <[email protected]>
adjusting region resolution to match erase-block-size Signed-off-by: Mateusz Michalek <[email protected]>
Add fast PWM instance for the nRF54H20 device. Upstream PR: zephyrproject-rtos/zephyr#75047 Signed-off-by: Adam Kondraciuk <[email protected]>
This commit provides an additional threshold value for comparison when a custom k_busy_wait() implementation is chosen. Upstream PR: zephyrproject-rtos/zephyr#73068 Signed-off-by: Adam Kondraciuk <[email protected]>
The nRF54H20 PPR target has not enough memory to run some of kernel/timer tests. Upstream PR: zephyrproject-rtos/zephyr#73068 Signed-off-by: Adam Kondraciuk <[email protected]>
Enable the device runtime power management on the SPIM shim. Upstream PR: zephyrproject-rtos/zephyr#75715 Signed-off-by: Adam Kondraciuk <[email protected]>
Add configuration for testing SPI with device runtime PM enabled for nRF platforms. Upstream PR: zephyrproject-rtos/zephyr#75715 Signed-off-by: Adam Kondraciuk <[email protected]>
Add overlay and enable test for nrf52840dk. Upstream PR: zephyrproject-rtos/zephyr#76088 Signed-off-by: Bartlomiej Buczek <[email protected]>
Add overlay and enable test for nrf54h20dk. Upstream PR: zephyrproject-rtos/zephyr#76088 Signed-off-by: Bartlomiej Buczek <[email protected]>
Add overlay and enable test for nrf54l15pdk. Upstream PR: zephyrproject-rtos/zephyr#76088 Signed-off-by: Bartlomiej Buczek <[email protected]>
…r nrf54. It will increase test coverage for adc driver, no test uses ADC_GAIN_2_3 setting yet. Upstream PR: zephyrproject-rtos/zephyr#76088 Signed-off-by: Bartlomiej Buczek <[email protected]>
Tests are checking error codes returned from adc_read() and adc_setup_channel() used with invalid configurations. Upstream PR: zephyrproject-rtos/zephyr#76191 Signed-off-by: Bartlomiej Buczek <[email protected]>
…piini Allow for users to provide a --qspiini parameter that is passed directly to the nrfjprog executable but only in the --program operation. This is required since e073210 enabled the -O/--tool-opt for all operations, but --qspiini is only allowed combined with --program. Upstream PR: zephyrproject-rtos/zephyr#75731 Signed-off-by: Carles Cufi <[email protected]>
… text The current option used as an example, --recover, is actually a separate option in the runner itself. Instead use --clockspeed as an example, which is applicable to all nrfjprog commands. Upstream PR: zephyrproject-rtos/zephyr#75731 Signed-off-by: Carles Cufi <[email protected]>
Packets are routed between OT and Zephyr net stacks. For IPv4 these packets are managed by NAT64 by default. Upstream PR: zephyrproject-rtos/zephyr#75012 Signed-off-by: Marcin Gasiorek <[email protected]>
Implementation of functionality whitch configure CIDR for OT NAT64. Upstream PR: zephyrproject-rtos/zephyr#75012 Signed-off-by: Marcin Gasiorek <[email protected]>
When multicast packet is forwarded to the OpenThread stack it has to have its "multicast loop" flag enabled to be processed by the stack itself instead of only propagating it further. Upstream PR: zephyrproject-rtos/zephyr#76086 Signed-off-by: Konrad Derda <[email protected]>
Add nRF54H20 cpu PPR target to GRTC tests. Upstream PR: zephyrproject-rtos/zephyr#76215 Signed-off-by: Adam Kondraciuk <[email protected]>
…uracy On nrf boards expected accuracy from ref voltage is 64 instead of 32. Upstream PR: zephyrproject-rtos/zephyr#76088 Signed-off-by: Bartlomiej Buczek <[email protected]>
…en interface Before packet is routed there is a check verifying if the destination address is not the device's one. However, the check should be limited to the packet's original interface. Otherwise, packet cannot be routed if it is destined for an other interface of the device. Upstream PR: zephyrproject-rtos/zephyr#76150 Signed-off-by: Konrad Derda <[email protected]>
…ess for NS When a packet's transmission is prepared and Neighbor Solicitation is sent its souce address is always the same as of a packet awaiting - also for packets routed from an other interface. Quote from the RFC: If the source address of the packet prompting the solicitation is the same as one of the addresses assigned to the outgoing interface, that address SHOULD be placed in the IP Source Address of the outgoing solicitation. Otherwise, any one of the addresses assigned to the interface should be used. This commit fixes the behavior. Upstream PR: zephyrproject-rtos/zephyr#76150 Signed-off-by: Konrad Derda <[email protected]>
…ckets If the packet was routed between interfaces by IPv6 module it should not be looped back but has to be passed to the destination interface instead. Upstream PR: zephyrproject-rtos/zephyr#76150 Signed-off-by: Konrad Derda <[email protected]>
…dress When IPv6 packet is received, there is a check of the packet's source address to verify that it is not interface's non-tentative address. This commit moves this check to the later stages of processing as packets that can be routed are dropped in the early stage otherwise. Upstream PR: zephyrproject-rtos/zephyr#76150 Signed-off-by: Konrad Derda <[email protected]>
The test case for SO_BINDTODEVICE socket option was flaky, the client socket always sent the datagram to the IP address of the second interface, so in theory every packet should end up on that interface. In practice though, due to imperfect loopback packet handling, the test worked as the packet ended up on the interface it was sent from. The test should send datagrams to the IP addresses of the interface 1 and 2 alternatively. The server socket binds to ANY address, so w/o interface binding it should receive all datagrams, so it allows to verify if SO_BINDTODEVICE filtering works fine. Upstream PR: zephyrproject-rtos/zephyr#76150 Signed-off-by: Robert Lubos <[email protected]>
While forwarding a multicast packet decrement hop limit in a common net buffer. Also, packets with hop limit equal to 0 should not be forwarded. Signed-off-by: Konrad Derda <[email protected]> (cherry picked from commit 30c38179e8998253195de58f3b8fb394cd26b092)
The RADIO models now contain the radio, let's stop removing it, but as they do not support DFE, let's disable DFE. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 64a53d0)
Mention that we have the RADIO peripheral, but no encryption accelerators yet. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit fa9a596)
Provide a replacement for CMSIS' NVIC_GetEnableIRQ() as some applications use it. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 68adc77)
So the nRF clock driver is built in as in real targets. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 61db569)
Just as for the other simulated targets. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit e998741)
As now we have a sufficient model of the CLOCK peripheral, let's mention it in the docs, and correct the warning about not supporting the BLE stack. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 329dbea)
Set the radio status as ok as the SOC/CPU DT include does not do it for us. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 4b64e00)
…argets The simulated targets support the same power levels as the real targets. Let's correct the kconfig dependencies accordingly. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit c9491a8)
…ters in nRF54 In some nRF54 devices, DATAWHITEIV was renamed to DATAWHITE, and the CRCCNF SKIADDR field was renamed OFFSET. The nrf HAL hid this change internally, so let's use it so we don't need to ifdef these in the Bluetooth Controller HAL code. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 3577388)
…PORT selection For the Nordic HW, the BT_CTLR_DATA_LEN_UPDATE_SUPPORT does not require CCM HW enabled, hence support Data Length Update if Encryption Support is disabled. Signed-off-by: Alberto Escolar Piedras <[email protected]> Signed-off-by: Vinayak Kariappa Chettimada <[email protected]> (cherry picked from commit a3218b0)
Ensure that we call the host libC when allocating space for a possible set of test arguments even if we are building Zephyr with an embedded libC. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 7826f7c)
Select the newly introduced nrf54lx compatible kconfig option. This is common both for real HW and for simulated HW, allowing SW to behave appropriately for both. Signed-off-by: Vinayak Kariappa Chettimada <[email protected]> Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit fb774fe)
fixup! [nrf noup] scripts: west: build: Use sysbuild by default if in NCS dir Enables sysbuild by default for all repositories, NCS or otherwise Signed-off-by: Jamie McCrae <[email protected]>
…efault" This reverts commit 7a0f9ef. Signed-off-by: Rubin Gerritsen <[email protected]>
Added: nrf54h20dk_nrf54h20_cpuapp.overlay: Choose uart136 hwfc 115200 nrf54h20dk_nrf54h20_cpuapp.conf Signed-off-by: Aytürk Düzen <[email protected]> (cherry picked from commit 5f00c18)
…er.log Keep new lines at handler.log. (cherry picked from commit f0bfaa4) Signed-off-by: Piotr Kosycarz <[email protected]>
…8 test Configure the I2C test speed with K-config Signed-off-by: Bartosz Miller <[email protected]> (cherry picked from commit 7f3c08b)
For both UARTs connected to debugger chip. Upstream PR: zephyrproject-rtos/zephyr#78033 Signed-off-by: Piotr Kosycarz <[email protected]>
Add more test cases for nRF GRTC timer Signed-off-by: Bartosz Miller <[email protected]> (cherry picked from commit a49c649)
Remove 3 delete-node directives which do not apply to this SOC. They made it in originally thru a copy paste mistake from the nrf5340bsim dts file. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit f2711b2)
This target does not yet support the PSA random generator. Lets explicitly set it to disabled, to even if the SOC definition sets it to "okay" it is not built in by default. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit b03db5e)
These peripherals are now included. Let's mention them and remove the warning about them being missing. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 8a7c16c)
…the PDK The nrf54l15dk is now avaliable in the tree. Let's compare the simulated board to this one instead. Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit c2c17ea)
Update the HW models module to: 4b0b020e25dbf1a11ccccf7b7741d6ca991ba9e4 Including the following: * 4b0b020 54L CLOCK: Generate XOSTARTED event * 79287fb hal: RADIO: support also triggering TASK_SOFTRESET from HAL Signed-off-by: Alberto Escolar Piedras <[email protected]> (cherry picked from commit 1dd139f)
AyturkDuzen
force-pushed
the
bluetoth_tester_sysbuild_downstream
branch
from
September 6, 2024 12:33
a4e488f
to
0e74479
Compare
nrf-squash! [nrf noup] dts: nordic: Add support for BICR generation The BICR LFOSC.LFXOCONFIG.MODE field supports disabling the usage of an external crystal oscillator to disable LFXO as LF clock source. This adds the enum to the binding, the rest of the codebase already supports the feature. Signed-off-by: Karsten Koenig <[email protected]>
To enable common sysbuild hci_ipc build for rad core: Kconfig.sysbuild sysbuild/prj.conf added for multicore devices (nRF53/54H) Signed-off-by: Aytürk Düzen <[email protected]>
AyturkDuzen
force-pushed
the
bluetoth_tester_sysbuild_downstream
branch
from
September 6, 2024 13:01
0e74479
to
609992e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To enable common sysbuild hci_ipc build for rad core: Kconfig.sysbuild
sysbuild/prj.conf
added for multicore devices (nRF53/54H)