Skip to content

# Release notes BSP 2.x

Release notes for BSP version 2.x, based on the Yocto dunfell version.

See hardware descriptions for a quick overview which devices are supported with at least basic functionality (serial console, boot from sd card and flash, ethernet communication).

Version numbers appended with '-dev' suffix indicate the current work in progress situation for the final release without suffix.

## Changes from BSP version 2.1.0 to 2.1.1

This is a bugfix version. Changes to the latest feature version includes

- Fix SWUpdate package build
  The SWUpdate packages for the provided `image-ktn-swu` and `image-ktn-qt-swu` images now contain valid update contents. The dedicated `swupdate-img*` images are therefore obsoleted now, but currently held for compatibility.

## Changes from BSP version 2.0.0 to 2.1.0

- Update all Yocto layers to dunfell version (3.1.25+, poky 23.0.25+)
- Align ST Microelectronics Yocto layers with STM32MP15-Ecosystem 3.1.1 version
- Update linux kernel to version 5.10.116 (5.10-stm32mp-r2.1+)
- Update u-boot bootloader to version 2020.10 (2020.10-stm32mp-r2.1+)
- Update arm-trusted-firmware bootloader to version 2.4 (2.4-stm32mp-r2.1+)
- CAN, RS232, RS485 interfaces are supported
- DPI, HDMI and LVDS display interface is supported (see documentation for restrictions)
- LVDS display configurations for BL boards are added
  - Jenson JT60050 LVDS 7 inch (stm32mp-t1000-k-70) and
  - Jenson JT60180 LVDS 10 inch (stm32mp-t1000-k-101)
- USB OTG interface can operate in device and host mode on Kontron BL boards
- Userspace SPI can be activated in device tree with `compatible="kontron,user-spi"` for device trees of customer board designs
- ADC inputs are supported on Kontron BL boards

### Known issues and limitations

This BSP has limited hardware support. So only a few devices are supported and they have also limited hardware support.

Currently supported hardware:

- SL STM32 MP157 512MB/512MB (t1000)
- BL STM32 MP157 512MB/512MB (t1000-k)
- DK STM32 MP157 512MB/512MB with 5 inch display and captouch (t1000-k-50)

Currently supported yocto images:

- image-ktn-minimal
- image-ktn
- image-ktn-swu and swupdate-img
- image-ktn-qt (only demo image, not suited for NAND due to size)

Supported functionality:

- Serial console
- Boot from SD card
- Boot from flash (NOR-NAND, NOR-EMMC)
- Ethernet communication (u-boot, linux)
- Secure shell communication
- RTC support
- OTP fuse programming via `mptool`
- USB host interface
- GPIO access (u-boot, linux)
- CAN interface
- RS232 interface
- RS485 interface
- Display interfaces (DPI)
- Display interfaces (HDMI, LVDS)
- Beeper
- USB OTG interface
- I2C integration
- SPI integration
- ADC support
- GPU support
- M4 core

Not yet supported functionality, experimental or demo:

- Qt5 integration (demo, version Qt 5.15.9+)

Known issues

- GPIO input access by `sysfs` is broken for gpios located on the SOC chip. Use the `libgpiod` interface instead.
- Framebuffer screen blanking does not work (`echo 0 > /sys/class/graphics/fb0/blank`).
- DK/BL boards: HDMI usage is very limited. Only a few monitors and resolutions work

### Compatibility information

Currently here are no major compatibility issues.

## Changes from BSP version 1.6.0 to 2.0.0

- Update all Yocto layers to dunfell version (3.1.13, poky 23.0.13+)
- Align ST Microelectronics Yocto layers with STM32MP15-Ecosystem 3.1 version
- Update linux kernel to version 5.10.61 (5.10-stm32mp-r2+)
- Update u-boot bootloader to version 2020.10 (2020.10-stm32mp-r2+)
- Update arm-trusted-firmware bootloader to version 2.4 (2.4-stm32mp-r2+)
- Update CubeIDE board configuration files to CubeIDE version 1.8.0 (CubeMx 6.4.0)
- U-boot uses a redundant environment by default
- U-boot flashes the default environment with the provided boot commands if no environment is already stored in flash
- Same u-boot bootloader can be used in flash and SD card (auto detection of u-boot environment storage location)
- Support of AB double copy boot scheme with boot to fallback copy if boot counter exceeds
- Support of SWUpdate embedded software update framework (see https://sbabic.github.io/swupdate/) on AB boot scheme and `image-ktn-swu`

### Known issues and limitations

This BSP has limited hardware support. So only a few devices are supported and they have also limited hardware support.

Currently supported hardware:

- BL STM32 MP157 512MB/512MB (t1000-k)
- SL STM32 MP157 512MB/512MB (t1000)

Currently supported yocto images:

- image-ktn-minimal
- image-ktn
- image-ktn-swu

Supported functionality:

- Serial console
- Boot from SD card
- Boot from flash (NOR-NAND, NOR-EMMC)
- Ethernet communication (u-boot, linux)
- Secure shell communication
- RTC support
- OTP fuse programming via `mptool`
- USB host interface
- GPIO access (u-boot, linux)

Not yet supported functionality:

- Display interfaces (Parallel, HDMI, LVDS)
- GPU support
- M4 core
- USB OTG interface
- CAN interface
- RS232 interface
- RS485 interface
- I2C integration
- SPI integration
- ADC support
- Beeper

Known issues

- GPIO input access by `sysfs` is broken for gpios located on the SOC chip. Use the `libgpiod` interface instead.

### Compatibility information

Due to fundamental rework of the secure and non-secure world interface between the first stage bootloader (`tf-a`, secure world) and non-secure world component (`u-boot`, `linux kernel`), a mix between the components `tf-a`, `u-boot` and `linux kernel` of BSP 1.x and BSP 2.x is not possible!

So upgrading a device from 1.x BSP to 2.x BSP requires the update of all components: tf-a secure bootloader, u-boot bootloader and linux kernel.

Further compatibility information:

- NOR flash layout changed due to redundant u-boot environment
- sysfs base adress of gpios located on i2c port expander (gpiochip8) changed from 504 to 1016
- extlinux boot scheme is a deprecated feature and support for it will be removed in future