Add initial support for Nuvoton NuMaker-M333x SoC series,
including basic initialization and device tree includes.
Signed-off-by: cyliang tw <cyliang@nuvoton.com>
Product photo from https://learn.adafruit.com/assets/130701
with license CC BY-SA 3.0
Tested with command mentioned in the index.rst page.
Signed-off-by: Jonas Berg <jonas.s.t.berg@gmail.com>
Adds a sample which demonstrates how to use DTLS over UDP. This
copies the certificate files from the echo server sample to use as
dummy certificates
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Issue:
- The calibration value had the correct elements but false operations
- This leads to wrong values or even saturation
Changes:
- Added explenation of formula
- Moved constant from MACRO into formula to get rid of the
confusing 10000000ULL constant
- Added rounding for better results
Signed-off-by: Martin Koehler <koehler@metratec.com>
Button 0 and LED 0 share a GPIO pin on slwrb4311a. Remove the
`led0` alias in a board overlay to make the button sample work
out of the box.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Add SLWRB4182A, a radio board for EFR32MG22, as well as SLWRB4311A,
a radio board for BGM220. The boards have similar pinout, but with
some differences to the LED and enable pins.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Add bg22_ek4108a board definition for the EFR32BG22 Explorer Kit.
The board has similar pinout to the other xg22 explorer kits.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Move to explorer_kits directory, share configuration between
bgm220_ek4314a and xg22_ek2710a, as their pinouts are similar.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Reset cause API was expanded with two more reset causes.
These are RESET_BOOTLOADER and RESET_FLASH.
Add handling of RESET_BOOTLOADER and RESET_FLASH to reset_cause test.
Signed-off-by: Sebastian Głąb <sebastian.glab@nordicsemi.no>
Add support for WeAct Studio ESP32-C6 Mini development board.
The WeAct ESP32-C6 Mini is a compact development board based on the
ESP32-C6FH4 chip (QFN32 package) with 4 MB in-package flash. This
board features complete Wi-Fi 6, Bluetooth LE 5.3, Zigbee, and Thread
support.
Key features:
- ESP32-C6FH4 chip (RISC-V 32-bit, up to 160 MHz)
- 4 MB in-package flash
- 22 GPIOs
- USB Type-C connector with USB Serial/JTAG
- Boot and reset buttons
- RGB LED
Unlike the ESP32-C6-DevKitC which uses the ESP32-C6-WROOM-1 module,
this board has the ESP32-C6FH4 chip directly mounted in QFN32 package.
Signed-off-by: Siratul Islam <sirat4757@gmail.com>
The net capture sample is likely one application that does rely on linking
against the native C library rather than Picolibc, since it needs to hook
into Linux's tun / tap interfaces.
However, after removing `<zephyr/posix/...h>` from the default search
path, a number of conflicts appear between the native libc socket types
and Zephyr's in `net_ip.h`.
Issue 97050 already captures this partially. However, there seems to be
some confusion about POSIX headers and types and ISO C headers and types.
There are C libraries that do not include all of the necessary POSIX
headers and types that Zephyr depends on. For example:
* minimal libc
* IAR
* newlib
* picolibc
The latter two might surprise some.
In any case, the work required to properly namespace `net_ip.h` constants
and types is well out of the scope of the current release cycles, so this
small workaround should suffice.
A non-exhaustive list of constants and types from `net_ip.h` that conflict
with native types are
* PF_INET
* PF_INET6
* PF_PACKET
* PF_CAN
* PF_LOCAL
* SOCK_STREAM
* SOCK_DGRAM
* SOCK_RAW
* struct iovec
* struct msghdr
* struct cmsghdr
* struct sockaddr
* struct sockaddr_storage
A non-exhaustive list of errors that arise are of the form(s) below:
```shell
In file included from $HOME/../zephyr/net/ethernet.h:21,
from $HOME/../samples/net/capture/src/main.c:15:
../zephyr/net/net_ip.h:45: warning: "PF_INET" redefined
45 | #define PF_INET 1 /**< IP protocol family version 4. */
|
/usr/include/bits/socket.h:45: note: this is the location of the previous \
definition
45 | #define PF_INET 2 /* IP protocol family. */
|
In file included from /usr/include/bits/socket.h:38:
$HOME/zephyrproject/zephyr/include/zephyr/net/net_ip.h:89:9: error: \
redeclaration of enumerator ‘SOCK_STREAM’
89 | SOCK_STREAM = 1, /**< Stream socket type */
| ^~~~~~~~~~~
/usr/include/bits/socket_type.h:26:3: note: previous definition of \
‘SOCK_STREAM’ with type ‘enum __socket_type’
26 | SOCK_STREAM = 1, /* Sequenced, reliable,...
| ^~~~~~~~~~~
$HOME/zephyrproject/zephyr/include/zephyr/net/net_ip.h:250:8: error: \
redefinition of ‘struct iovec’
250 | struct iovec {
| ^~~~~
In file included from /usr/include/sys/socket.h:26:
/usr/include/bits/types/struct_iovec.h:26:8: note: originally defined here
26 | struct iovec
| ^~~~~
```
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
The bluetooth hci on silabs siwx91x depends on the nwp
(network coprocessor). This patch allows to check for the correct
initialization of the nwp before using bt hci on siwx91x.
Signed-off-by: Martin Hoff <martin.hoff@silabs.com>
The goal of this patch is to switch from the nwp.c and nwp.h soc files
to the new nwp driver. During this transition, we also renamed
CONFIG_WISECONNECT_NETWORK_STACK to CONFIG_SILABS_SIWX91X_NWP which are
a better naming to let the user knows that the network coprocessor files
will be added to the compilation.
The switch from a soc file to a driver device introduce a notion of nwp
device that allows us to check for good initialization and ressources
allocation.
Before this patch, it is not possible to know if the nwp have booted
successfully or not. We can now check if the device driver is ready
or not before trying to do operation related to the nwp.
Signed-off-by: Martin Hoff <martin.hoff@silabs.com>
The firmware interprets the client idle timeout in units of 32 beacon
intervals, not in milliseconds. This mismatch caused the applied timeout
to be higher than the configured value.
Fix the driver to use the correct unit.
Signed-off-by: Arunmani Alagarsamy <arunmani.a@silabs.com>
Added pinctrl and dts nodes for uSDHC1 and uSDHC2, they are disabled
by default, and provided overlay files to enable them if needed.
Signed-off-by: Lei Xu <lei.xu@nxp.com>
Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
Update release-notes about the following additions:
- CONFIG_PSA_CRYPTO
- CONFIG_PSA_CRYPTO_PROVIDER_TFM
- CONFIG_PSA_CRYPTO_PROVIDER_MBEDTLS
- CONFIG_PSA_CRYPTO_PROVIDER_CUSTOM
Signed-off-by: Valerio Setti <vsetti@baylibre.com>
Remove previous Kconfig choices CONFIG_BT_MESH_USES_MBEDTLS_PSA and
CONFIG_BT_MESH_USES_TFM_PSA and use CONFIG_PSA_CRYPTO instead.
This commit also updates test code accordingly.
Signed-off-by: Valerio Setti <vsetti@baylibre.com>
The goal of new Kconfig PSA_CRYPTO_PROVIDER is to automatically enable
any of the PSA Crypto API provider available for the platform without
having the user to manually pick the proper one. This provider can be
either TF-M, if that's enabled in the build, or Mbed TLS otherwise.
PSA_CRYPTO_PROVIDER simplifies also modules/subsystem Kconfigs removing
blocks as:
select MBEDTLS if !BUILD_WITH_TFM
select MBEDTLS_PSA_CRYPTO_C if !BUILD_WITH_TFM
Kconfig PSA_CRYPTO_PROVIDER_CUSTOM is also added to allow the end user
to add a custom implementation of PSA Crypto API instead of TF-M or
Mbed TLS ones.
Signed-off-by: Valerio Setti <vsetti@baylibre.com>
The driver code only relies on legacy Mbed TLS crypto, not on PSA API, so
enabling MBEDTLS_PSA_CRYPTO_C is not needed here.
Signed-off-by: Valerio Setti <vsetti@baylibre.com>
The dependency should be PSA_CRYPTO_CLIENT and not
MBEDTLS_PSA_CRYPTO_CLIENT because the former is more generic. TF-M can
indeed provide PSA Crypto API, not only Mbed TLS.
Signed-off-by: Valerio Setti <vsetti@baylibre.com>
The function `log_backend_std_get_flags` was not documented.
Create a doxygen style documentation for it.
Signed-off-by: Kiara Navarro <knavarro@paltatech.com>
Adding the sparkfun samd21 dev breakout board. This will work with the
basic blinky sample. Link attached to the boards info page.
Link: https://www.sparkfun.com/sparkfun-samd21-dev-breakout.html
Signed-off-by: Rickey Fehr <ric@rf3.xyz>
Refactor internal event bits to use state enum values
and define set_state() and wait_state() so we don't need
two set of variables to maintain.
Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no>
Fix for collecting and presenting measured data.
During verify measured values, the test skipped all results
after the first incorrect one. Furthermore, it duplicated
already collected data on the output list. So in this case the
result list include wrong data.
Signed-off-by: Artur Wilczak <arturx.wilczak@intel.com>
From the analysis of the the masurments so far it follows that
the expected value of the state_1 is too hight.
Change expected value of state_1 from 0.14 to 0.12.
Regarding the test:
tests/subsys/pm/power_states
Signed-off-by: Artur Wilczak <arturx.wilczak@intel.com>
The `/connector` node conflicts with
`boards/raspberrypi/rpi_pico/rpi_pico-common.dtsi` definition.
Renaming it to `connector_arduino` to avoid conflict with that.
Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
soc_prep_hook() is always called from z_prep_c() which is implemented
as a C function. As such, there is no need to check for the associated
CONFIG_SOC_PREP_HOOK since the platform/hooks.h header will define hooks
as no-op function-like macros if their associated Kconfig isn't enabled.
Remove the Kconfig check from all arch implementations of z_prep_c() and
call soc_prep_hook() directly instead, to avoid duplicating the Kconfig
check already performed in platform/hooks.h
Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
Document the expected early boot sequence and when platform hooks should be
called by the arch-specific coode, and under what conditions.
Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
Clean up the top-level comment in the platform hooks header which is used
when generating documentation:
- capitalize "soc" as "SoC"
- capitalize "zephyr"
- simplify "soc and board specific" -> "SoC/board-specific"
Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
The hooks' signature was not visible to Doxygen due to preprocessor
conditionals - instead, the dummy no-op implementation was seen instead.
Update #ifdef guard to make the hooks' signature and the associated
documentation visible to Doxygen such that it appears in docs.
Also fix a tiny typo on soc_reset_hook()'s documentation comment.
Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
Add DSA Qbv support, add set_config/get_config to set and get
Qbv configuration. support enable/disable, set/get times,
set/get list length and set/get gate control list.
Signed-off-by: Qiang Zhao <qiang.zhao@nxp.com>
Add NET_QBV in Kconfig, Qbv is Enhancements for Scheduled Traffic (EST),
one feature of TSN. The PTP clock provides the time reference for Qbv
Signed-off-by: Qiang Zhao <qiang.zhao@nxp.com>
Use THREAD_ANALYZER_LONG_FRAME_PER_INTERVAL config to reset
longest frame value to zero after printing so that longest frame
now represents longest frame for the most recent interval. The
longest overall frame is often at startup and this modification
allows one to observe subsequent long frames.
Signed-off-by: Jay Lawlor <jlawlor@amperecomputing.com>
Signed-off-by: Dan Kalowsky <dkalowsky@amperecomputing.com>
This commit excludes it8xxx2_evb platform for gen_isr_table
test since it8xxx2 soc don't support software triggering
interrupts.
Fixes issue #94382.
Signed-off-by: Ren Chen <Ren.Chen@ite.com.tw>
Replace CONFIG_PM with CONFIG_PM_DEVICE to include pm_lock
in cc23x0 UART driver in struct uart_cc23x0_data
Signed-off-by: Stoyan Bogdanov <sbogdanov@baylibre.com>
In power management, add support to take into account the alarms
set in RTC. Alarm from RTC is processed like any other from SYSTIM.
This prevents from missing interrupts.
Signed-off-by: Stoyan Bogdanov <sbogdanov@baylibre.com>
