The sample is added to demonstrate mspi_transceive asynchronously.
Apollo3 MSPI controller has hardware command queue and supports
scatter IO and callback management, so no additional software queue
is required.
Signed-off-by: Swift Tian <swift.tian@ambiq.com>
The sample code is copied from spi_flash. To flash API, there is no
difference if the bus is spi or mspi.
Signed-off-by: Swift Tian <swift.tian@ambiq.com>
A collection of simple enablements to match some of the enablement
done for rd_rw612_bga as closely as possible on the frdm_rw612 board.
- i2c
- spi
- dma
- mrt
- ctimer
- os timer
- dac
- adc
- trng (alread was enabled but now listed support)
- watchdog
Signed-off-by: Declan Snyder <declan.snyder@nxp.com>
Do not run the samples/drivers/flash_shell application on the
stm32h745i_disco//m4 as the flash controller is not supported yet
on the M4 core (only M7). Just like the nucleo stm32h745//m4
is excluded.
Also exclude stm32h7rs disco at the moment (still TODO).
Signed-off-by: Francois Ramu <francois.ramu@st.com>
The stm32 xspi node is another possible multi-spi for connecting
with gpDMA channels for Rx and Tx, same request.
Channels 4 and 5 are preferred for AHB periph to/from ext. Mem.
Signed-off-by: Francois Ramu <francois.ramu@st.com>
Rename all Silicon Labs starter kits to always use the official kit name
as board target name. Previous kit names used various naming schemes,
including putting part of the SoC name in the board name. With HWMv2,
SoC names (if needed) should go in the SoC board qualifier.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Rename all Silicon Labs dev kits to always use the official kit name
as board target name. Previous kit names used various naming schemes,
including putting part of the SoC name in the board name. With HWMv2,
SoC names (if needed) should go in the SoC board qualifier.
Use HWMv2 revisions for the two variants of SLTB010A.
Split the xG27 Dev Kit from the EFR32BG22 Thunderboard. This attempt
at deduplication is confusing due to the very different kit names
and use of different ICs (BG22 vs BG27), and was not continued with
the xG24 Dev Kit, meaning that it wasn't consistent.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Replace CONFIG_ESPI_SLAVE by CONFIG_ESPI_TARGET
Replace CONFIG_ESPI_SAF by CONFIG_ESPI_TAF
Replace ESPI_BUS_SAF_NOTIFICATION with ESPI_TAF_BUS_NOTIFICATION in API
Signed-off-by: Jose Alberto Meza <jose.a.meza.arellano@intel.com>
Enable execution of ADC driver tests on nrf54l15.
Overlay file for nrf54l15 already exists.
Signed-off-by: Sebastian Głąb <sebastian.glab@nordicsemi.no>
Get the flash device from the node compatible, instead of an alias.
This removes the need for the `spi-flash0` alias on every board with one
of these drivers.
Signed-off-by: Jordan Yates <jordan@embeint.com>
Add testcases for rk043fn02h_ct and rk043fn66hs_ctg shields to display
and LVGL samples, so these testcases will be built by CI.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
The sample has been modified to work with devices that have
no explicit erase capability.
For that purpose printf messages have been modified to use
"Internal storage" rather than "Flash" when reporting status.
Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
This sample app cycles several colors on an RGB LED forever using the LED
API. It can be built and executed on an Arduino Nicla Sense ME, or on any
board where the devicetree has a similar compatible I2C device node.
Signed-off-by: Luca Burelli <l.burelli@arduino.cc>
In an effort to shave off code size, remove out-of-the-box
enabling of crypto features (except SHA-256).
Configurations are adjusted to enable what they need.
Bonuses:
- When enabled, AES now defaults to using a smaller version
(`CONFIG_MBEDTLS_AES_ROM_TABLES` isn't default enabled anymore,
and if enabled, `CONFIG_MBEDTLS_AES_FEWER_TABLES` defaults to y).
- Conditions around Mbed TLS Kconfig options have been improved
to reflect the reality of the dependencies.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Adds useful context to the charger sample README to help readers
understand what the sample application is doing.
Signed-off-by: Ricardo Rivera-Matos <ricardo.rivera-matos@cirrus.com>
With the addition of the STM32 hardware semaphore MBOX driver, this
sample is now supported by the board.
Signed-off-by: Celina Sophie Kalus <hello@celinakalus.de>
Add a missing space in the regular expression that defines the expected
console output so that it matches what the sample actually produces.
Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
Both nrf54l15pdk/cpuflpr and nrf54l15pdk/cpuflpr_xip have
watchdog on the list of supported periperals.
As a result, Twister tries to build samples/drivers/watchdog
for these two targets.
Since overlays are missing, build is failing.
Add missing overlay files.
Signed-off-by: Sebastian Głąb <sebastian.glab@nordicsemi.no>
RW612 has one FLEXSPI controller, which is capable of supporting
multiple external devices on one board. However, care must be taken when
configuring the FLEXSPI to use multiple devices, as if the FLEXSPI is
configured incorrectly in XIP mode it will fail to read from the
external flash, and the chip will crash.
Make the following changes to the RW configuration for the MEMC sample,
in order to support executing from flash while accessing PSRAM:
- initialize the FLEXSPI MEMC driver first, before the flash or PSRAM
drivers are initialized
- force the FLEXSPI MEMC driver to reconfigure the FLEXSPI at boot, so
we can configure the DQS sampling mode for the PSRAM on port B
- only configure the PSRAM pins during FLEXSPI init, so XIP is not
disrupted
- configure the flash device at boot. This is required so that the MEMC
driver will not replace the LUTs programmed in the FLEXSPI by the
bootrom, as it would otherwise not be aware of their existence.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
The chain-length DTS property is now mandatory, so remove the
optional Kconfig for setting the length
Signed-off-by: Jamie McCrae <spam@helper3000.net>
Adds chain length and colour mapping properties to LED strip devices
on boards where these parameters are now required
Signed-off-by: Jamie McCrae <spam@helper3000.net>
Since the RW612 BGA board's FlexSPI configuration prevents the board
from executing from flash while the PSRAM is configured (unless both are
configured by a bootloader prior to XIP), run the MEMC sample from
internal code SRAM, and write data to the external PSRAM block via the
FlexSPI.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
Convert the ht16k33 to use the input subsystem. This can still be used
with the kscan API with the zephyr,kscan-input driver, or use the
input-keymap one to generate input codes instead.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
