The sample output is not rendered properly, as can be seen on
https://docs.zephyrproject.org/latest/samples/sensor/pressure_polling/README.html
Adjust the formatting so that the code block is rendered properly.
The text "## Default configuration" does not appear in the sample output.
Signed-off-by: Jonas Berg <jonas.s.t.berg@gmail.com>
Use CMAKE_C_COMPILER_TARGET to allow clang to correctly determine
the runtime library for the target architecture.
Otherwise, the default runtime library will be selected.
Signed-off-by: Mikhail Siomin <victorovich.01@mail.ru>
Add support for the Adafruit Feather Canbus board.
The image is from https://learn.adafruit.com/assets/120914, with
the license CC BY-SA 3.0.
Signed-off-by: Jonas Berg <jonas.s.t.berg@gmail.com>
Multiple handlers were setting status/reason in slightly different ways,
but the code was mostly trying to do the same. Put this code in the
handler class and implement in one place.
This fixes an issue where in some cases qemu failures were not handled
correctly and status of cases was not updated, leading to multiple
failures.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
The misra severity is being treated as relevant to whether a guideline
should be followed or not in the context of the zephyr project.
Remove from the table, the MISRA severity can be looked up in many
public places or in the MISRA coding guielines themselves.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Honor the --flash-before option when using a serial-pty script with
--device-serial-pty <script> and start the script only after
flashing the device.
Signed-off-by: Tim Pambor <tim.pambor@codewrights.de>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
While reasonably straightforward, ensure the signature of the
comparator_callback_t is properly documented.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Modify values in audio.conf to reduce memory usage.
Most notably disabling logs reduced the FLASH requirements.
Ideally the shell works as expected without debug logs, but
there are far too many profiles and services to verify them all.
All the log options are left in audio.conf so they can easily be
re-enabled when needed.
Memory before this change:
Memory region Used Size Region Size %age Used
FLASH: 1018512 B 1 MB 97.13%
RAM: 423146 B 448 KB 92.24%
IDT_LIST: 0 GB 32 KB 0.00%
Memory after this change:
Memory region Used Size Region Size %age Used
FLASH: 791308 B 1 MB 75.47%
RAM: 369090 B 448 KB 80.46%
IDT_LIST: 0 GB 32 KB 0.00%
Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
Add ST nucleo_h503rb board to I2C driver i2c_target_api test.
The board configuration make it testing transfer of 300 bytes data
to ensure the ReloadMode of the SoC I2C controller nicely handles
exchanges of more than 256 byte.
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Add CONFIG_I2C_TEST_DATA_MAX_SIZE to I2C driver i2c_target_api tests
to set the max data size of tested I2C transfer. The effective I2C
transfer data size depends on that value and the size of the
EEPROM defined in the board DTS file.
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Add configuration options CONFIG_I2C_RTIO_LOOPBACK_DATA_READ_MAX_SIZE
and CONFIG_I2C_RTIO_LOOPBACK_DATA_WRITE_MAX_SIZE to set the number
of bytes exchanged during I2C transfers in I2C driver rtio_loopback
sample.
Add also a bit of verbosity when exchanged data are corrupted.
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
System designers may want to change the behavior of assert_print, such as
storing the message off into retained RAM and instantly rebooting. Adding
__weak allows customatization
Signed-off-by: Clay Wynn <cwynn@meta.com>
The various DT helpers benefit from being shown in their respective
device sections as it's expected that some users will be looking there
rather than generic Devicetree help pages.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
At the moment, "blinky" sample can be built for Pico 2 W, but it doesn't
work as expected because the board has no LED connected to GPIO.
rpi_pico2.dtsi is a common dtsi, used by Pico 2 and Pico 2 W, it
shouldn't contain board specific stuff (like LEDs).
So, include "rpi_pico-led.dtsi" directly in Pico 2 board dts.
Signed-off-by: Andrei Lalaev <andrey.lalaev@gmail.com>
when compiling net-samples then the required gpio is disabled.
the installed vsc8541 phy requires gpio for reset. additionally,
we enable NET_L2 when network is enabled.
Signed-off-by: Sven Ginka <s.ginka@sensry.de>
when compiling net-samples then the required gpio is disabled.
the installed vsc8541 phy requires gpio for reset. additionally,
we enable NET_L2 when network is enabled.
Signed-off-by: Sven Ginka <s.ginka@sensry.de>
Rather than keeping limits defined in a common way, controllable with one
Kconfig, move posix definitions out of the standard common libc header
`<limits.h>` into `<zephyr/posix/posix_limits.h>`, not controlled with
Kconfig. Additionally, include `<zephyr/posix/posix_limits.h>` wherever
an in-tree C library includes a custom `<limits.h>`.
Note: the only reason any of the `<limits.h>` files exist, is to define
the POSIX limit PATH_MAX without declaring `_POSIX_C_SOURCE`, which would
be necessary according to the standard, and each of the custom `<limits.h>`
files is nearly identical in this regard.
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
In order to reduce conflicts with limits defined in external C libraries,
move Zephyr's POSIX limits from posix_features.h to limits.h in the
common C library sources.
In order to give the implementation better control over where POSIX
limit definitions originate, use `#include_next <limits.h>` to pull in
the corresponding header of the C library, and provide a non-user
configurable option `CONFIG_TC_PROVIDES_POSIX_LIMIT_DEFS` that may be set
in order to ensure that the C library version of POSIX limits are used.
Note: this may mean that runtime invariant values are inconsistent with
parts that are actually in use within Zephyr, so applications are
encouraged to use `sysconf()` with external C libraries that implement
parts of the POSIX standard to query system configuration values at
runtime.
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
Fix building with Privacy feature without enabling LE
Encryption support. This should allow being either Observer
or Broadcaster role with Privacy features.
Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
Add a bullet point for this new, relatively important deviation from
the official specification.
Also, advertise the Zephyr-specific zephyr/psa/* header files as they
are related and probably need more attention from end users.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Instead of literally having 0x in the format string, use the %# flag
character so the printf implementation adds the 0x for us.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
nrf54l15dk/nrf54l15/cpuapp already covers the non-emulated case as
part of the integration_platforms.
Having ophelia4ev/nrf54l15/cpuapp does not bring any additional value
and increases CI load, so remove it.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Add a migration guide entry regarding the modification of the UID size
as it is by default a breaking change.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
77f19eb1b5 made ZMS depend on
FLASH_MAP.
Enable that Kconfig option in the ZMS Kconfig overlay file.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Add test scenarios for the newly-added CONFIG_SECURE_STORAGE_64_BIT_UID
enabled with both the ZMS and Settings backends.
They don't test backward compatibility but it makes sure that secure
storage compiles and works fine with this configuration.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Cast the UIDs to unsigned long when they are 32 bits.
This allows to use a single %l length modifier instead of the double
one for long long.
Certain printf implementations only support the former and not the
latter length modifier, so this has the advantage to work with them
now that the UIDs are 32-bit by default.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>