When TF-M is enabled, Mbed TLS's MD module (which is used to generate
v5 UUIDs) will dispacth hash operations to TF-M. Unfortunately TF-M
does not support SHA-1 (because it's a weak algorithm) so the
computation will fail.
Signed-off-by: Valerio Setti <vsetti@baylibre.com>
- "bt_le_adv_update_data()" func calls just after bt_enable() call
without completion of bt_ready() which is called as part of worker
thread within init_work() causes issue where bluetooth controller
has not been initialized and provides cb to app before app requests
advertise_update to the stack.
- remove bt_ready() func and place content within main() post
bt_enable() fixes this issue.
Signed-off-by: Nirav Agrawal <nirav.agrawal@nxp.com>
Some IPM devices return an error if we request to transfer data.
Use IPM_MAX_DATA_SIZE to determine if the virtio ID can be transferred
through the IPM device.
Send data to IPM only if CONFIG_IPM_MAX_DATA_SIZE is not zero.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
The ipm_send() allows transferring data through the IPM device.
However, depending on the platform, the mailbox peripheral may either
transmit a limited amount of data or not transfer data at all.
Introducing this configuration allows exposing the IPM capability to the
application.
This commit defines a default value of 1024 bytes to avoid impacting
existing IPM drivers and sets the value to 0 for the STM32 IPCC and
STM32 HSEM devices.
This allows, in a next step, other devices to use this configuration to
expose their capabilities instead of using proprietary configuration or
a static definition.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
The name of the boards was incorrect in the documentation,
Fix the name of the board according to the official name.
Signed-off-by: Miguel Gazquez <miguel.gazquez@bootlin.com>
In almost all WCH boards doc, the name of the processor had a typo:
QingKe 32-bit RISC-V4F instead of QingKe V4F 32-bit RISC-V
Fix the doc for all relevant boards.
Signed-off-by: Miguel Gazquez <miguel.gazquez@bootlin.com>
Fix issues reported by string validation which was added to strings
used in zassert macros.
Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
In enum tcp_state {}, the CLOSED state was put at the last one.
When we do Sequence & Ack validation, we will need to skip the
CLOSED, LISTEN, SYNSENT states. It is easier for coding if we
put the CLOSED to the front, e.g. if state > SYNSENT. And, in
other OSes, the state sequence is normally defined like this.
Signed-off-by: Shrek Wang <inet_eman@outlook.com>
Update to a revision of the manifest action that includes:
https://github.com/zephyrproject-rtos/action-manifest/pull/21
Also add the corresponding binary blobs labels parameters to the
workflow.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
This test only works for 64-bit values. On targets which use 32 bits for
double, skip this version. The float test will check the 32-bit math for
that.
This is the 'nicer' version of this fix which uses sizeof rather than
relying on __SIZEOF_DOUBLE__.
Signed-off-by: Keith Packard <keithp@keithp.com>
When both CONFIG_NET_IPV6_DAD and CONFIG_NET_IPV4_ACD are disabled, the
anonymous union in struct net_if_addr ends up with no members, which
results in a different struct layout between C and C++.
In C, an empty union has size 0, while in C++ it has size >=1, which
shifts the offsets of the following fields.
Add a 1-byte dummy member to the union to ensure consistent layout
across both compilers.
Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no>
The spi_loopback_transceive() helper currently only prints a
message if a configuration is invalid, continuing the test
case as if it succeeded. This results in the test case using the
helper trying to validate the result from a spi transaction that
was skipped.
Fix this by explicitly skipping the test using the ztest
framework's ztest_test_skip() function, which skips the entire
test case.
Signed-off-by: Bjarki Arge Andreasen <bjarki.andreasen@nordicsemi.no>
- Add devicetree for AM6232, the dual core AM62 processor without GPU
- Used in revision A0 of PocketBeagle 2
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- AM6232 is a dual core variant of AM6234 with everything being same.
- Used in the first batch of PocketBeagle 2
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
With e337b7b65d, the test started to
fail with stack overflows in the no_optimizations scenario, so give
the ztest thread a little more space.
Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
Update the lfxo node load-capacitance-femtofarad to
match the chosen external lfxo on the nRF54L15-DK design.
Previous stray capacitance value was incorrect, which
resulted in a too low load capacitance.
Signed-off-by: Håkon Alseth <haal@nordicsemi.no>
- Setting default value of passive scan
dwell time of 400ms as SDK doesn't
configure default value.
Signed-off-by: Nitin Pandey <nitin.pandey@silabs.com>
Add cmake linker generator things for .last_section.
Follow up to #88970. Fixes bug #89719, for gcc/ld & iar
Signed-off-by: Björn Bergman <bjorn.bergman@iar.com>
This is a host driver for ESP32 chips running the esp-hosted
firmware, which turns ESP32s into a WLAN/BT co-processor.
Signed-off-by: Ibrahim Abdalkader <i.abdalkader@gmail.com>
As TinyCrypt gets deprecated, we need to remove all bsim tests that use
it. This commit switches all Bluetooth mesh bsim tests to PSA as a
default crypto backend.
This includes:
- removing `CONFIG_BT_MESH_USES_TINYCRYPT` as PSA is default crypto
backend for mesh. `CONFIG_BT_MESH_USES_MBEDTLS_PSA` is not required to
be enabled;
- merging `overlay_psa.conf` into `prj.conf` as this configuration
becomes default for all mesh bsim tests;
- merging `overlay_ss.conf` into `overlay_pst.conf` as secure storage is
required for running persistent storage bsim tests with PSA;
Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
This is a preparation commit for switching all bsim tests to PSA as
TinyCrypt will be removed soon.
Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
Allow ESP32 devices to test the scenario where
when alarm should not be triggered after being cancelled.
Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com>
As part of counter API updates, RTC timer will be removed from
counter API driver and can be removed from the test list.
Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com>
Currently to set/clear the pins, we do a logical OR of the value with the
existing values in set/clear registers. However, reading these registers
always returns the value in out_data register. This is undesirable as it
can cause unnecessary complications. Consider the following scenario:
We need to set PIN 0:
set_data |= BIT(0)
We need to clear PIN 1:
clr_data |= BIT(1)
The latter would also clear the 0th bit due to the aforementioned
behaviour.
This patch fixes this by writing the mask directly without ORing.
Signed-off-by: Amneesh Singh <a-singh7@ti.com>
This patch fixes memory corruption that can happen when running in
multi-thread and multi-core environment with heavy scheduling stress.
In SMP configuration, we must ensure that all thread's context is
stored before writing the switch_handle flag. Otherwise some of the
thread context writes could be delayed after another CPU begins to
schedule this thread which could lead to memory corruptions.
Signed-off-by: Sylvain Chouleur <schouleur@snapchat.com>
There is an issue that the buffer cannot be allocated by the function
`read_payload()` in UART ISR context. Then the UART RX will be
disabled. The H4 driver hopes to get the receive buffer in the HCI RX
thread and then open the UART RX again. However, there is a situation
where the HCI RX thread is blocked in getting the received data
buffer. However, since the UARt RX has been disabled, the HCI RX
thread cannot get the received data buffer. Therefore, the RX thread
is always blocked here, causing the Bluetooth host to not work
properly.
Add a semaphore `rx.ready` to notify new received data buffer has
been added to H4 RX queue.
Wait for the semaphore `rx.ready` instead of H4 RX queue in HCI RX
thread.
Wake up the HCI RX thread when failing to allocate the RX buffer.
Fixes#89879.
Signed-off-by: Lyle Zhu <lyle.zhu@nxp.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Indent with tabs.
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
Also remove a few spurious space characters.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
