The resource reservation header is now included according to a Kconfig
value. The Kconfig can be overriden out-of-tree in case a different
header is needed.
Signed-off-by: Rafał Kuźnia <rafal.kuznia@nordicsemi.no>
Moving the blob client, dfd server and dfu server to their own
elements and increasing the CONFIG_BT_MESH_TX_SEG_MAX to 8 to fit
new composition data into composition data page status message.
Standalone mesh blob client and DFU distributor/update server models
requires one element and those elements only contain the main models
and the models they extend to.
Referring to MshMBT_v1.0 Section 6.1:
The BLOB Transfer Client model defines the messages listed in Table 6.1
, and requires one element: the BLOB Transfer Client Main element. The
BLOB Transfer Client Main element contains the BLOB Transfer Client
main model.
And referring to MshDFU_v1.0 Sections 6.1.1 and 6.2.1:
6.1.1
The Firmware Update Server model adds the state instances listed in
Table 6.1 and Table 6.2 and the messages listed in Table 6.3 to the
model it extends, and requires one element: the Firmware Update Main
element. The Firmware Update Main element contains the Firmware Update
Server main model and all the models that the main model extends.
6.2.1
The Firmware Distribution Server model adds the state instances listed
in Table 6.7 and Table 6.8 and the messages listed in Table 6.9 to the
model it extends, and requires one element: the Firmware Distribution
Main element. The Firmware Distribution Main element contains the
Firmware Distribution Server main model and all the models that the
main model extends.
Signed-off-by: alperen sener <alperen.sener@nordicsemi.no>
Referring to MshDFU_v1.0 Sections 6.1.1, 6.2.1 and 7.1.1 model
descriptions: DFU/DFD server/clients extend BLOB Transfer root models
and DFD server requires Firmware Update Client on the same element. For
this reason we need to make sure that those main models or root models
exist on the same element. And also firmware update client can not be
forced to be in the first element.
For all model extention call return the error code in case of an error.
Signed-off-by: alperen sener <alperen.sener@nordicsemi.no>
update test cases for twister
1. test_errors.py add protection.
2. test_handlers.py change call to status
3. test_testsuite.py change call to status
The log traces for TwisterException objects only.
And the stack trace output follow the same rules for all exceptions,
but StatusAttributeError with its dedicated handlers.
Signed-off-by: Hake Huang <hake.huang@oss.nxp.com>
Remove the deprecated can_get_min_bitrate() (replaced by
can_get_bitrate_min()) and can_get_max_bitrate() (replaced by
can_get_bitrate_max()) CAN API functions.
Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
Remove the deprecated CAN_MAX_STD_ID (replaced by CAN_STD_ID_MASK) and
CAN_MAX_EXT_ID (replaced by CAN_EXT_ID_MASK) macros.
Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
One of the tests is failing since it was split out in 1a633609a0
triggering an assertion:
ASSERTION FAIL [((((size_t)(16)) << 10) - (((uintptr_t) (&_end)) -
0x20000000)) >= 8192] @
WEST_TOPDIR/zephyr/lib/libc/newlib/libc-hooks.c:139
Fix it by making the min_flash and min_ram parameters up to overall
test level.
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
The ruff linter and formatter should get a locked version to be installed
for compliance. This prevents new linter issues because of ruff updates
itself.
Ruff version 0.8.0 removed the deprecated UP027 rule so it's removed from
the ignore list.
Update the excludes file to match the actual reported issues.
Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>
This definition is deleted in the follwoing commit;
8233b70
as a part of "cleanup", however this definition is
used by smp_log
Signed-off-by: Arif Balik <arifbalik@outlook.com>
Use the "do { } while (0)" construct so the macro behaves like an actual
C statement in all cases. Also evaluate the macro argument only once.
Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
Add support for Norik Systems Octopus IO-Board based on
Norik Systems Octopus SoM.
Supported features:
- LTE-M/NB-IoT
- GPS
- LED
- 3-axis accelerometer
- Battery charger
- Solar charger
- SPI NOR flash
- Nano SIM connector
Signed-off-by: Florijan Plohl <florijan.plohl@norik.com>
Add support for Norik Systems Octopus SoM based on nRF9160 SiP.
Supported features:
- LTE-M/NB-IoT
- GPS
- LED
- 3-axis accelerometer
Signed-off-by: Florijan Plohl <florijan.plohl@norik.com>
Add support for setting the sample frequency via `attr_set` and the
output data rate from device tree source.
Signed-off-by: Jeppe Odgaard <jeppe.odgaard@prevas.dk>
Add build tests for the IT8801 MFD drivers, including GPIO,
Input and PWM functionalities.
GPIO, Input test: west build -p always -b native_sim
PWM test: west build -p always -b it82xx2_evb
Signed-off-by: Tim Lin <tim2.lin@ite.corp-partner.google.com>
IT8801 support GPIO alternate function switching.
Some GPIO pins can be switched as KSO or PWM function.
Signed-off-by: Tim Lin <tim2.lin@ite.corp-partner.google.com>
The IT8801 is an I/O expander that provides GPIO, PWM, Keyboard
functions via the I2C bus.
Signed-off-by: Tim Lin <tim2.lin@ite.corp-partner.google.com>
For Zephyr Cortex-A Core supports on NXP boards imx8mm, imx8mn, imx8mp,
imx93 and imx95, currently use DDR DRAM memory as Zephyr memory, so
change RAM dts nodes name to be "dram" in order to reduce confusion.
Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
Rename "nxp,kinetis-adc12" compatible to "nxp,adc12" to remove the
device family from its name.
Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com>
The initial proposal had the assert included, however this could break
downstream users and it was opted to not add assert in the driver API
calls.
Update the documented example to reflect that.
Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>
For the C sources the offloaded raw TX mode wasn't considered and else
case picks up system mode files causing build issues.
Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
- Adds 'supported: flash' to all NXP board .yaml
with enabled flash controller support.
- Sorts supported features alphabetically.
Signed-off-by: Andrej Butok <andrey.butok@nxp.com>
Correctly selects the Kconfig symbols for viper CPU clusters
instead of having a reverse hwmv1 setup where the symbol has
a choice
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Add `se` variant to support the low-cost CoreS3 SE.
- Add configuration files
Add `m5stack_cores3_procpu_se(.dts|.yaml|defconfig)` files.
Reorganize dts files to split common parts.
- Update .yaml file
Add gpio, can, counter, entropy, pwm, and pinmux to the supported
feature group. Remove the `ignore_tags:` section.
- Update documents
Add and modify information about CoreS3 SE.
Add more description about sysbuild.
Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
Disable the IPC communication between the domains
for the arm_thread_swap test since it is not needed
and it causes a flash oveflow for the no opmitization
test case.
Signed-off-by: Georgios Vasilakis <georgios.vasilakis@nordicsemi.no>
Enable the cpusec IPC and the bellboard nodes for
the nrf54h20dk cpuapp and cpurad targets to enable
communication between domains.
Also enables the region cpurad_ram0x_region since
it is also required for the communication.
Signed-off-by: Georgios Vasilakis <georgios.vasilakis@nordicsemi.no>
For the inverted pulse measurements, that should reflect
the duty-cycle off interval, the 1% deviation in test_capture
should be adjusted so it reflects duty-cycle off.
Signed-off-by: Ioannis Karachalios <ioannis.karachalios.px@renesas.com>
As per the PWM API definition, -EBUSY should be returned
when pwm_enable_capture is called and capturing
is already enabled. This commit deals with adding
a ztest_suite_before_t function that should disable
capturing at the end of a single test. Some tests, though,
such as test_pulse_capture, execute two sub-tests
and so, capturing is disabled in between. In fact, the omission
of pwm_disable_capture should not only result in aborting
a single test, but it can also raise system exception
due to invalid context. This is the case for
z_impl_pwm_capture_cycles where z_pwm_capture_cycles_callback
can be fired whilst the routine has already aborted and so
struct z_pwm_capture_cb_data data, defined within function
declaration, should not longer be valid.
Signed-off-by: Ioannis Karachalios <ioannis.karachalios.px@renesas.com>
