STMicroelectronics feed for OpenWRT

This repository is an OpenWRT feed dedicated to supporting the STMicroelectronics STM32MP1 and STM32MP2 platforms.

Using this project is not strictly necessary as OpenWrt itself has support for stm32 target. But this feed integrates the STMicroelectronics BSP, whereas OpenWrt uses upstream components. And more boards are supported in the feed.

You are using the openwrt-24.10 branch of the feed, which is based on the OpenWrt branch openwrt-24.10. Actually the feed is based on OpenWrt v24.10.0 (Release Note).

Supported devices

STM32MP157F-DK2: minimal support for the STM32MP157F-DK2
STM32MP135F-DK: minimal support for the STM32MP135F-DK
STM32MP257F-EV1: minimal support for the STM32MP257F-EV1
STM32MP257F-DK: minimal support for the STM32MP257F-DK
STM32MP157F-DK2-DEMO: based on the STM32MP157F-DK2 device including additional packages like a web interface to configure the device.
STM32MP135F-DK-DEMO: based on the STM32MP135F-DK device including additional packages like a web interface to configure the device.
STM32MP257F-EV1-DEMO: based on the STM32MP257F-EV1 device including additional packages like a web interface to configure the device.
STM32MP257F-DK-DEMO: based on the STM32MP257F-DK device including additional packages like a web interface to configure the device.

Supported features	STM32MP157F-DK2	STM32MP135F-DK	STM32MP257F-EV1	STM32MP257F-DK
Sysupgrade	yes	yes	yes	yes
Ethernet	yes	yes	yes	yes
Watchdog	yes	yes	yes	yes
RTC	yes	yes	yes	yes
Hardware RNG (Optee)	yes	yes	yes	yes
LED	yes	yes	yes	yes
Button	no	yes (USER2)	yes (USER1/USER2)	yes (USER1/USER2)
Wifi	yes	yes	x	yes
USB Type-A	yes	yes	yes	yes

BSP

This feed is based on the STPM32MP1/STM32MP2 BSP v6.0.

Components	Version
TF-A	2.10-stm32mp-r1
U-Boot	2023.10-stm32mp-r1
OPTEE	4.0.0-stm32mp-r1
Linux	OpenWRT kernel + v6.6-stm32mp-r1

For the kernel, the patches from the v6.6-stm32mp branch until the tag v6.6-stm32mp-r1 were added. They are available in target/linux/stm32/patches-6.1/.

Some patches were removed as they were applied in Linux, or they are already applied by OpenWrt.

2c9b2c9cac5e ("usb: dwc2: keep the usb stack informed of SetPortFeature failure while Host")
6287f3f5f2e4 ("ASoC: stm32: spdifrx: fix dma channel release in stm32_spdifrx_remove")
8a5e18189df4 ("media: i2c: imx335: Enable regulator supplies")
c5540f6a4d9a ("nvmem: stm32: add support for STM32MP25 BSEC to control OTP data")
eb99d7c27da7 ("crypto: stm32/cryp - call finalize with bh disabled")
31286612453a ("perf list: fix arguments order issue for events printing")
fd68ca2e9089 ("i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume")

Some patches had to be modified to fix some conflicts.

950158c37fbf ("usb: dwc2: hcd: fix power down exiting by system resume")
19458fd268c4 ("media: i2c: imx335: add control of an optional powerdown gpio")
393cf701259c ("mtd: spi-nor: add Octal DTR support for Macronix flash")
1e5eedcdaf1c ("firmware: arm_scmi: optee leverage Ocall2 thread provisioning")
9d36363eee52 ("counter: stm32-timer-cnt: add pm runtime support")

Following patches were not applied due to conflicts. They corresponds to the empty patches in target/linux/stm32/patches-6.1/. They could be applied in the future if needed.

426e1c78e4c1 ("drm/stm: ltdc: set transparency after plane disable")
8d235ec212fa ("drm/stm: ltdc: support of rotation on crtc output")
89f5b97c79ac ("drm/stm: ltdc: add support of plane upscaling")
326eea71a0e4 ("drm/stm: ltdc: refactor interrupt management")
c4ffda2683bb ("drm/stm: ltdc: set color look-up table for each plane")
4909e4745e9c ("drm/stm: ltdc: refactor crtc start sequence")
a3f784f44512 ("drm/stm: ltdc: remove encoder helper functions")
c273a5bad2aa ("drm/stm: ltdc: add lvds clock")
6a508bd6b305 ("drm/stm: refactor probe sequence")
b90306b377d3 ("drm/stm: ltdc:  add property default-on")
66d934a13b5c ("drm/stm: ltdc: move mode valid & fixup to encoder helper functions")
e40cd2b4b75b ("drm/stm: ltdc: Check rotation buffer length")
3d63eeb9313b ("drm/stm: ltdc: Check panel width")
1102333ad31b ("drm/stm: ltdc: set default parent of pixel clock")
1bc5bac55257 ("drm/stm: support of new hardware version for soc MP21")
dc9d876018c6 ("drm/stm: ltdc: Check the security of layer 2.")
73c7bd933066 ("drm/stm: ltdc: remove mode_set_nofb callback")
759efa7b4959 ("drm/stm: ltdc: add plane_atomic_enable callback")
73cc2db18231 ("drm/stm: ltdc: replace pm_runtime_get_sync by pm_runtime_resume_and_get")
662800081ef7 ("drm/stm: ltdc: flush remaining vblank event")
6e8b50d319c9 ("drm/stm: ltdc: Check the security of layer 3.")
3682d604ecbd ("drm/stm: ltdc: reset ltdc on crtc enable")

Getting started

Pre-requisites

In order to use OpenWRT, you need to have a Linux or Unix like distribution installed on your workstation. And you need to install a set of packages as described in the OpenWRT Build system setup.

Getting the code

The feed is designed to work with the openwrt-24.10 branch of OpenWRT (last tested commit is v24.10.0).

$ git clone https://git.openwrt.org/openwrt/openwrt.git
$ cd openwrt
$ git checkout v24.10.0

Next step is to add the STMicroelectronics feed in the feeds.conf.default file.

$ cat feeds.conf.default
src-git st /~https://github.com/bootlin/openwrt-feed-st.git
src-git packages https://git.openwrt.org/feed/packages.git
src-git luci https://git.openwrt.org/project/luci.git
src-git routing https://git.openwrt.org/feed/routing.git
src-git telephony https://git.openwrt.org/feed/telephony.git
#src-git video /~https://github.com/openwrt/video.git
#src-git targets /~https://github.com/openwrt/targets.git
#src-git oldpackages http://git.openwrt.org/packages.git
#src-link custom /usr/src/openwrt/custom-feed

Then fetch the code of all feeds

$ ./scripts/feeds update -a

Install the feeds

Install stm32 target

$ ./scripts/feeds install -f stm32

Install all other packages

$ ./scripts/feeds install -a -f

(Some overriding warnings can occur, if you used -f please ignore them).

Configure and build

Run make menuconfig

$ make menuconfig

Then select STMicroelectronics STM32 for the Target System, STM32MP1 or STM32MP2 for the Subtarget, and select the Target Profile corresponding to your hardware (for example STMicroelectronics STM32MP135F-DK).

Then to start the build.

$ make -j$(nproc)

Flashing and booting the system

All images generated for are stored in bin/targets/stm32/stm32mp1/ for subtarget stm32mp1 and in bin/targets/stm32/stm32mp2/ for subtarget stm32mp2. The images to flash on the SDCard are openwrt-stm32-stm32mpX-stm32mpXXXXX-ext4-factory.img.gz.

$ gzip -d -c bin/targets/stm32/stm32mp1/openwrt-stm32-stm32mp1-stm32mp135f-dk-ext4-factory.img.gz | dd of=/dev/sdX

(Note: this assumes your SD card appears as /dev/sdX on your system.)

Then:

Insert the microSD card
- STM32MP157: connector CN15
- STM32MP135: connector CN3
- STM32MP257: connector CN1
Plug a micro-USB cable or USB-C for STM32MP257 and run your serial communication program on /dev/ttyACM0
- STM32MP157: connector CN11
- STM32MP135: connector CN10
- STM32MP257: connector CN21
Configure the SW1 switch to boot on SD card
- STM32MP157: BOOT0 and BOOT2 to ON
- STM32MP135: BOOT0 to ON, BOOT1 to OFF, BOOT2 to ON
- STM32MP257: BOOT0 to ON, BOOT1 and BOOT2 and BOOT3 to OFF
Plug a USB-C cable or Barrel cable for STM32MP257 to power-up the board.
- STM32MP157: connector CN6
- STM32MP135: connector CN12
- STM32MP257: connector CN20
The system will start, with the console on UART. The default user is root with no password. The login is automatic.

Note that STM32MP257 can be powered using the USB-C (CN21) if the jumper JP4 is set to the positioin [2-3].

BusyBox v1.36.1 (2024-02-14 15:44:53 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r24943+13-3a073a0212
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/#

Additional informations

This chapter contains some informations which are specific to the stm32 target. For the generic informations, please refer to the Official OpenWRT documentation.

Ethernet

The configuration of Ethernet interfaces is the default OpenWRT configuration:

STM32MP157F-DK2: lan interface
STM32MP135F-DK: lan interface (ETH1) and wan interface (ETH2)
STM32MP257-EV1: lan interface (ETH1) and wan interface (ETH2)
STM32MP257F-DK: lan interface

The lan interface is configured with a static ip address 192.168.1.1 and a dhcp server is running.
The wan interface is in dhcp mode.
By default the management protocols are only accessible from the lan interface.

System upgrade

For a system upgrade, an upgrade image shall be used (image labelled ...-sysupgrade.img.gz).

The demo and non-demo profiles are compatible, it means you can update a STM32MP135F-DK profile with a STM32MP135F-DK-DEMO image (vice versa) for example.

By default, the sysupgrade mechanism updates the partitions one by one. If the partition table is different (for example the rootfs partition is 10MiB bigger), the full image is written.

The U-Boot environment variables are always preserved during an upgrade.
To erase the environment variables, flash the factory image on the SDCard or use the env erase command from U-Boot.

Useful link: Upgrading OpenWrt firmware using LuCI and CLI

Button

The kernel module gpio-button-hotplug is used to support buttons.

To easily test the button:

mkdir -p /etc/hotplug.d/button

cat << "EOF" > /etc/hotplug.d/button/buttons
logger "the button was ${BUTTON} and the action was ${ACTION}"
EOF

root@OpenWrt:/# logread -f
Fri Mar 15 14:28:09 2024 user.notice root: the button was BTN_1 and the action was pressed
Fri Mar 15 14:28:09 2024 user.notice root: the button was BTN_1 and the action was released

Useful link: Attach functions to a push button

LED

One LED is defined and labelled blue:heartbeat (LD8 for STM32MP157F-DK2, LD3 for STM32MP135F-DK and LED1 for STM32MP257F-EV1). By default it is configured to use the heartbeat trigger.

Useful link: LED Configuration

USB

Only mass storage are supported on the USB Type-A by default.

Hardware RNG

By default OpenWrt uses urngd, a micro non-physical true random number generator based on timing jitter. To use Hardware RNG as entropy source, rng-tools package shall be used.

uci set system.@rngd[0].enabled="1"
uci set system.@rngd[0].device="/dev/hwrng"
uci commit system
service urngd disable && service urngd stop
service rngd restart

Name		Name	Last commit message	Last commit date
Latest commit History 135 Commits
.github/workflows		.github/workflows
docs		docs
package		package
target/linux/stm32		target/linux/stm32
README.md		README.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

STMicroelectronics feed for OpenWRT

Supported devices

BSP

Getting started

Pre-requisites

Getting the code

Install the feeds

Configure and build

Flashing and booting the system

Additional informations

Ethernet

System upgrade

Button

LED

USB

Hardware RNG

Going further

About

Releases

Packages

Languages

bootlin/openwrt-feed-st

Folders and files

Latest commit

History

Repository files navigation

STMicroelectronics feed for OpenWRT

Supported devices

BSP

Getting started

Pre-requisites

Getting the code

Install the feeds

Configure and build

Flashing and booting the system

Additional informations

Ethernet

System upgrade

Button

LED

USB

Hardware RNG

Going further

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages