The LED 4 is connected to the STMPS2151STR on the FAULT output pin which
is pulled low, automatically turning on the LED, in case of current
limit faults. Therefore, pin D4 should not be configured as a LED but
rather as an input to detect the fault condition.
Additionally, it should be noted that the board's silkscreen labels this
LED as "OC" (OverCurrent) rather than usr{1,2,3}, as is the case for the
other LEDs described in the DTS.
Fixes: cc5ae49133
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Added timer3 and pwmleds configuration to the nucleo_wba55cg board DTS
file. This includes setting the prescaler, enabling the pwm3 node with the
appropriate pin control settings, and configuring the pwmleds node with
green_pwm_led.
Signed-off-by: Lubos Koudelka <lubos.koudelka@st.com>
Added the USART2 definition to the nucleo_wba55cg device tree source file.
This enables the use of USART2 on the nucleo_wba55cg board.
Signed-off-by: Lubos Koudelka <lubos.koudelka@st.com>
Update documentation to indicate that DMA is available on Nucleo N657x0-Q
and STM32N6570 DK boards.
Signed-off-by: Guillaume Gautier <guillaume.gautier-ext@st.com>
- add nucleo_c071rb overlay file to setup adc node
- The C0 serie has two HSI clock sources, HSI48 and HSI48USB.
To make it simpler and compatible with the existing clock driver,
HSI48 is renamed to HSI (node already present in the stm32c0.dtsi).
HSI48USB will correspond to HSI48.
With SYNC mode, we have an overrun on the ADC, so we configure it
in ASYNC mode.
- Update STM32 HSI macro according to changes
Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com>
- Change SPI pin signals due to conflict with USB pins
(see UM3353, section 6.10).
- Add i2C2 node needed for I2C test driver.
- Add adc as supported peripheral in the board Yaml file.
Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com>
Update stm32n6 based boards documentation to reflect addition
of new sb variant and how it could be used for twister tests automation.
Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
On STM32N6 based series, there is no flash available and tests
are performed using load and run in RAM.
From twister point of view, we should consider a flash is available
with the same size as RAM.
(We may tune these values later as the RAM will actually be shared
between code and variables).
Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
When flashing STM32N6 in USB-DFU mode, as required when running test
automation using twister, it is first required to power-off/power-on the
board to set board ready for USB-DFU (thanks to specific BootROM
configuration).
Provide a script that performs this operation using STM32CubeProgrammer.
This scipt could be provided in twister map.yaml file on 'pre_script'
property of board entry.
Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
Fix some missing/erroneous docs and metadata for a few
boards post v4.0.0 so that they make the most of the
new zephyr-board Sphinx directive & role.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
The stm32l4r9i_disco has a 2nd LED (Orange) which can be controlled
via the mfx gpio controller.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
Since the ospi@ node does not exist anymore for the stm32u5 device
there is no more need for this pre_dt_board.cmake file.
Signed-off-by: Francois Ramu <francois.ramu@st.com>
On the nucleo_g071rb , nucleo_g070rb and nucleo_g0b1re boards,
the CN7 MORPHO_L_9 to 11 pin are not correctly defined
in the st_morpho_connector.dtsi. This PR is fixing this.
Signed-off-by: Francois Ramu <francois.ramu@st.com>
This commit removes all references to the `xtools` toolchain variant in the
board YAML files.
Note that the `xtools` toolchain variant has been deprecated since Zephyr
v3.3.0 and now removed.
The removal process was automated using the following command line:
git grep -l xtools -- boards/*.{yml,yaml} | \
xargs -n 1 -P $(nproc) \
yq -i 'del(.toolchain[] | select(. == "xtools"))'
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
Enabling `CONFIG_INPUT_FT5336_INTERRUPT` if the ft5336 node in DT
has `int-gpios` property.
As a result of this change, some boards can eliminate lines that
explicitly configure `CONFIG_INPUT_FT5336_INTERRUPT`.
Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
Add the PWM LED to Nucleo-WB07CC board and mark as compatible with PWM.
Also mark counters as supported (but don't enable by default).
Signed-off-by: Mathieu Choplain <mathieu.choplain@st.com>
Add the PWM LED to Nucleo-WB05KZ board and mark as compatible with PWM.
Also mark counters as supported (but don't enable by default).
Signed-off-by: Mathieu Choplain <mathieu.choplain@st.com>
Add the PWM LED to Nucleo-WB09KE board and mark as compatible with PWM.
Also mark counters as supported (but don't enable by default).
Signed-off-by: Mathieu Choplain <mathieu.choplain@st.com>
Moves the LV_DRAW_DMA2D_HAL_INCLUDE to the soc instead of the development
kit since the hal include is the same across all boards using the soc.
Signed-off-by: Fabian Blatz <fabianblatz@gmail.com>
There are 4 Kconfig names about the "Draw Buffer". Rename 'VBD' to 'VDB'
in Kconfig option 'LV_Z_*VBD*_CUSTOM_SECTION' to make name consistent.
config LV_Z_VDB_ALIGN
int "Rending buffer alignment"
config LV_Z_VBD_CUSTOM_SECTION
bool "Link rendering buffers to custom section"
config LV_Z_DOUBLE_VDB
bool "Use two rendering buffers"
config LV_Z_VDB_SIZE
int "Rendering buffer size"
default 100 if LV_Z_FULL_REFRESH
And the draw buffer definition is now:
static uint8_t buf0[BUFFER_SIZE]
#ifdef CONFIG_LV_Z_VDB_CUSTOM_SECTION
Z_GENERIC_SECTION(.lvgl_buf)
#endif
__aligned(CONFIG_LV_Z_VDB_ALIGN);
Signed-off-by: Haiyue Wang <haiyuewa@163.com>
The stm32l562e_dk board uses a ft6x06 i2c controller for the touchscreen.
The zephyr driver ft5336 can control it.
Signed-off-by: Luc BEAUFILS <luc.beaufils@savoirfairelinux.com>
Add the stm32f413h_disco target to the boards/st
Add the PLLi2S when needed by the USB or SDMMC or RNG.
Signed-off-by: Francois Ramu <francois.ramu@st.com>
Test "drivers.gpio.1pin.aw9523b" fails on stm32u083c_dk platform
because "arduino_i2c" definition does not exists in the device tree
of stm32u083c_dk board. Also updated the baord yaml
Signed-off-by: Arif Balik <arifbalik@outlook.com>
Added aliases to nucleo_l4r5zi/stm32f4_disco/stm32f411e_disco for
die_temp die_temp/vref/vbat nodes so that the die_temp_polling
and soc_voltage samples work for them.
Signed-off-by: Yishai Jaffe <yishai1999@gmail.com>
This commit enables support for DMA,
SPI, RNG, Crypto, USB and RTC.
Signed-off-by: Mohammad Badawi <zephyr@exalt.ps>
Signed-off-by: Sara Touqan <zephyr@exalt.ps>
In all STM32 dtsi and board dts, update the st,adc-sequencer and the
st,adc-clock-source properties so they are strings.
Signed-off-by: Guillaume Gautier <guillaume.gautier-ext@st.com>
fu dts: arm: st: use string instead of enum
The board hardware has no network interfaces, although the ECM/EEM class
implementation can provide Ethernet-like functionality and export it to
the host, this is no reason to default to a specific USB class
implementation.We do not make this kind of configuration for other
boards that have a USB device controller. Also, it may not be what a
user expects when using these boards with networking and a USB stack.
Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no>
Remove all USB and CDC ACM configuration in favor of common
configuraiton.
Do not adapt board-specific configurations such as unknown PID/VID or
string descriptors. There is no justification for using them on specific
boards, and we do not have formal approval to use them in the project
tree. Also, we need more uniform configuration, since the main reason
for enabling CDC ACM here is to allow users to run examples like
hello_world right out of the box. Of course, anyone is free to customize
these settings in their fork or downstream project.
Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no>
