STM32 MPUs Embedded software and solutions

Hi,I am using a PCM3060 codec connected to a STM32MP135 MPU over I2S1 and I2C, and compiling STM Linux (v6.1) (along with STM's version of TF-A, Optee, and U-Boot) using Buildroot.I had some trouble getting ALSA to output to the codec, it kept giving the response:  44004000.audio-controller-pcm3060-dac: ASoC: pcm3060-dac <-> 44004000.audio-controller No matching formats  I managed to work around the issue by changing the formats entry in snd_soc_dai_driver, in pcm3060.c (https://github.com/STMicroelectronics/linux/blob/7928f69738d2e57ee2a0dba6e9e680a3bf75ded9/sound/soc/codecs/pcm3060.c#L189) to SNDRV_PCM_FMTBIT_S32_LE.  #define PCM3060_FORMATS (SNDRV_PCM_FMTBIT_S32_LE) static struct snd_soc_dai_driver pcm3060_dai[] = { { .name = "pcm3060-dac", .id = PCM3060_DAI_ID_DAC, .playback = { .stream_name = "Playback", .channels_min = 2, .channels_max = 2, .rates = PCM3060_DAI_RATES_DAC, .formats = PCM3060_FORMATS, }, .ops

The LPTIM_TypeDef struct that is used throughout many of the HAL header files contains a few RESERVED fields that cover unused address offsets in the peripheral's memory map.The first of these, RESERVED1, is declared as uint16_t. I believe that this is incorrect and that it should be a uint32_t field to ensure that the address offsets of the subsequent fields are correct.Could someone please double-check and correct this if necessary?

Hi, I tried the Hello World application on Cortex-A7, I want to try linking my custom application library in this example. Can I do that?I changed the print_hello function and calling another function from my custom library.I tried linking custom library in Makefile byLDFLAGS += $(shell pkg-config --libs gtk+-3.0) -lxxxxx.aThe library file is in the same folder. But Get the below error: arm-ostl-linux-gnueabi-gcc -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=/home/usr-x/STM32MPU_workspace/Developer-Package/SDK/sysroots/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi -o gtk_hello_world gtk_hello_world.c -O2 -pipe -g -feliminate-unused-debug-types -Wall -pthread -I/home/usr-x/STM32MPU_workspace/Developer-Package/SDK/sysroots/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/usr/include/gtk-3.0 -I/home/usr-x/STM32MPU_workspace/Developer-Package/SDK/sysroots/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/usr/include/gio-unix-2.0 -I/home/usr-x/STM32MPU_workspace/Developer-Package

Dear ST community,I am currently trying to install an 8bit 8080 LCD , and i figured out that it needs FMC $ to be set up in devicetree in order to interface with it using DRM in Linux. i have the following device tree pinctrl nodes setup   fmc_pins_mx: fmc_mx-0 { pins { pinmux = <STM32_PINMUX('D', 0, AF12)>, /* FMC_D2 */ <STM32_PINMUX('D', 1, AF12)>, /* FMC_D3 */ <STM32_PINMUX('D', 4, AF12)>, /* FMC_NOE */ <STM32_PINMUX('D', 5, AF12)>, /* FMC_NWE */ <STM32_PINMUX('D', 7, AF12)>, /* FMC_NE1 */ <STM32_PINMUX('D', 14, AF12)>, /* FMC_D0 */ <STM32_PINMUX('D', 15, AF12)>, /* FMC_D1 */ <STM32_PINMUX('E', 7, AF12)>, /* FMC_D4 */ <STM32_PINMUX('E', 8, AF12)>, /* FMC_D5 */ <STM32_PINMUX('E', 9, AF12)>, /* FMC_D6 */ <STM32_PINMUX('E', 10, AF12)>, /* FMC_D7 */ <STM32_PINMUX('F', 0, AF12)>, /* FMC_A0 */ <STM32_PINMUX('G', 9, AF12)>; /*

I am bitbaking the core-image-minimal image, for a plain yocto poky distribution (Kirkstone), using stm32mp1 as my machine, and I am trying to figure out how the various st partition images are included in the build process. That is, how and where are the st-image-bootfs.bb, st-image-userfs.bb  and st-image-vendorfs.bb included in the core-image-minimal build? Everything is build as intended, but I cannot figure out how.I cannot find anywhere, where the recipes are added to any of the environment variables I usually use to include recipes, (IMAGE_INSTALL, PACKAGE_INSTALL, etc.).The only place I can find a reference to, for instance the bootfs recipe, is in meta-st-stm32mp/conf/machine/include/st-machine-common-stm32mp.incSTM32MP_BOOTFS_IMAGE ?= "st-image-bootfs" But I cannot trace that to how the recipe is included in the build.Please help.

My device tree:spi4_pins_csa: spi4-0 { pins { pinmux = <STM32_PINMUX('E', 12, AF5)>, /* SPI4_SCK */ <STM32_PINMUX('E', 14, AF5)>; /* SPI4_MOSI */ bias-disable; drive-push-pull; slew-rate = <1>; }; pins2 { pinmux = <STM32_PINMUX('E', 13, AF5)>; /* SPI4_MISO */ }; };     &spi4 { pinctrl-names = "default"; pinctrl-0 = <&spi4_pins_csa>; cs-gpios = <GPIO_CO_CS GPIO_ACTIVE_LOW>; status = "okay";   spidev@0{ compatible = "spidev"; reg = <0>; spi-max-frequency = <4000000>; }; };The output:root@apollo-e2412:~# spidev_test -D /dev/spidev1.0 spi mode: 0x4 bits per word: 8 max speed: 500000 Hz (500 kHz) [ 609.925039] spidev spi1.0: SPI transfer timed out [ 609.928391] spi_master spi1: failed to transfer one message from queue can't send spi message: Connection timed out Aborted

I have an STM32MP157D-DK1 development board and have built a buildroot image using the bootlin buildroot-external-st (st_stm32mp157d_dk1_demo_defconfig) external build tree. I have an Acubrite 12" 1080p touchscreen monitor that I am trying to get working at the monitor's native 1920x1080 resolution for use with a QT5 application but it is not working.The monitor works fine but is limited to 1280x720 resolution. Modetest does not report anything higher than 1280x720: root@stm32mp1:~# modetest -M stm Encoders: id crtc type possible crtcs possible clones 31 38 DPI 0x00000001 0x00000001 Connectors: id encoder status name size (mm) modes encoders 32 31 connected HDMI-A-1 250x140 5 31 modes: index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot #0 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver #1 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver #2 800x600 75.00 800 816 896 1

i have been trying to use the LTDC peripheral on the Linux kernel to use it on the ILI9340 / ILI9340 in 8 bit mode.i use this in the device tree:  &ltdc { status = "okay"; port { #address-cells = <1>; #size-cells = <0>; ltdc_ep1_out: endpoint@1 { reg = <1>; remote-endpoint = <&dsi_in>; }; }; }; &dsi { #address-cells = <1>; #size-cells = <0>; status = "okay"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; dsi_in: endpoint { remote-endpoint = <&ltdc_ep1_out>; }; }; port@1 { reg = <1>; dsi_out: endpoint { remote-endpoint = <&panel_in>; }; }; }; panel_ili9341: panel-ili9341@0 { compatible = "displaytech,dt024ctft", "ilitek,ili9341"; reg = <0>; reset-gpios = <&gpioe 4 GPIO_ACTIVE_LOW>; power-supply = <&v3v3>; status = "okay"; port { panel_in: endpoint { rem

board : STM32MP157F-DK2os : OpenSTLinux Kirkstonebuild command : bitbake st-image-coreroot@stm32mp1:~# rfcommCan't open RFCOMM control socket: Protocol not supported

Having doing a workshop regarding OpenST linux boot customisation (https://www.youtube.com/watch?v=hqGA5Krk0mU), I stumbled on a problem with a mass storage mount. Doing "ums 0 mmc 0" in uboot gives me partitions within an sdcard but only to see them as read only, unable to be mounted.Mounting sdb1 via terminal gave me error of "wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program or other error".St link is working, only problem is with usb download gadget.Unfortunately I am a beginner within the stm ecosystem so any help is greatly appreciated.Host is Macos Ventura 13.6, virtual virtualbox 7.0.6 as sudo (because of a problem with VERR_SHARING_VIOLATION in usb in regards to st link) 

Hello, I am using the STM32MP157F-DK2 board, I also developed a carrier board in order to use external peripherals. I am using a 5V external power supply and I supply it through pin headers CN2 expansion, since I don't want to use the USB type C connector. I would like to skip the current verification in the boot process in software, maybe from the device tree or a recipe. I am using yocto to develop my custom image. If I connect first the USB-type-C and the external power supply at the same time, the boot process finishes correctly, if I disconnect the USB-Type-C after that, the operating system can run correctly with the external power supply, but the USB-type-C is needed in order to finish the boot process. Is it possible to skip that 3A verification on software? I am in the kirkstone branch, 5.15.67 kernel version.Regards, @obedPH 

Hi Im using a STM32MP157-DK2 with a OpenSTlinux. I load my .elf file of for the M4 to /lib/firmware/ and starts it by chaning the state to start in remoteproc. The problem I have is that remoteproc seems to not run the code from the beginning of the main function. I have added some GPIO debugging outputs to see if they are activated but not all of them are activated. The code seems however to be work fine and the UARTs and ADC etc that are initialized and do work. So they are obviously initialized correctly...  If I then stops the process by sending stop to remoteproc and then re-starts by sending start, all debug outputs are activated. Meaning that the program restarts from the beginning of main. In the below example, the GPIO will not toggle at first start, but it toggle during the second start.   int main(void) { /* USER CODE BEGIN 1 */ //HAL_Init(); MX_ADC1_Init(); MX_ADC2_Init(); HAL_DeInit(); /* USER CODE END 1 */   /* MCU Configuration---------------------------

Hi there,I have a custom board based on STM32MP157F, with USB2 connected to STM32CubeProgrammer for flashing the eMMC. No USB-ID, no USB-VBUS connected.The STM32CubeProgrammer downloads the FSBL and U-Boot, but the software does not reconnect as "USB download gadget", it starts again. I believe the problem is related to the following, but not sure.We have tried quite a few things in the u-boot dts and dtsi, but nothing gets it working as it should be.I appreciate any help, thanks.

Hello! Is it feasible to start FBSD kernel?So far I stuck with following error (seems to be from tf-a):  Loading kernel... /boot/kernel/kernel text=0x1b4 text=0x5ad698 text=0x17e3d0 data=0xa4860 data=0x0+0x20c000 0x4+0x88d70+0x4+0xea43b| Loading configured modules... can't find '/etc/hostid' can't find '/boot/entropy' Using DTB compiled into kernel. Kernel entry at 0xc0400200... Kernel args: (null) metadata: filename:/boot/kernel/kernel, size=11874740 loadaddr=0xc0400000 ERROR: Illegal access to 0xffff0010: ERROR: FAIL_ID = 0x4c0 ERROR: Non-Secure ERROR: Privilege ERROR: Read PANIC at PC : 0x2ffc97b1 Exception mode=0x00000016 at: 0x2ffc97b1   I'm sure, that control passes to the kernel _start point. Any clues?  

https://community.st.com/s/question/0D53W00000PoivmSAB/changing-the-emmc-pins-with-otpI have the same pin mapping as above: SDMMC2_CK - PE3 (AF09)SDMMC2_D0 - PE6 (AF07)SDMMC2_CMD - PG6 (AF10)I programmed the OTP fuses as follows:WORD 3: 0x23000004 (I also program SD as primary and eMMC as secondary)WORD 5: 0x56755395WORD 6: 0x000076A4The problem is that even after flashing the eMMC with the TFA image as per the following procedure: https://u-boot.readthedocs.io/en/latest/board/st/stm32mp1.html#prepare-emmc I still get nothing on the UART4 console.We also put a scope on the SDMMC2_CK line and no clock is detected. Does it mean the BootROM is not accessing the eMMC?Am I missing something?

Hello,   I'm changing the DDR3 size from 512MB to 1GB on the STM32MP135F-DK board. The modifications were done as below. After that, I met the OPTEE header parse error. Compilation and updating software on board was conducted according to the ST wiki. ( https://wiki.st.com/stm32mpu/wiki/How_to_cross-compile_with_the_Developer_Package ) Please help me to solve this problem. change from 0x20000000 to 0x40000000 stm32mp135f-dk.dts in Linux Kernel, U-Boot, TF-A, and OP-TEE stm32mp135f-dk-fw-config.dts in TF-A stm32mp13-ddr3-1x8Gb-1066-binF.dtsi in TF-A (DDR_ADDRMAP6 0x0F070707 ==> 0x07070707) conf.mk in OP-TEE Thanks. NOTICE: CPU: STM32MP135F Rev.YNOTICE: Model: STMicroelectronics STM32MP135F-DK Discovery BoardNOTICE: Board: MB1635 Var1.0 Rev.E-02INFO: PMIC version = 0x21INFO: Reset reason (0x35):INFO: TF-A simple example helloINFO: Power-on Reset (rst_por)INFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe0000INFO: FCONF: Reading firmware configuration

The STM32MP133A supports Linux, and has PTP support in its ethernet peripheral. However, there doesn't seem to be a driver, or port of ptpd for that specific hardware.The peripheral seems similar to other STM32 parts for which there are community ports of ptpd, buta) not officially supportedandb) for FreeRTOS, not Linux. Has anyone used ptpd with a STM32MP133A and Linux? Does ST support it at all?

Hello Madam/sir, Recently we have purchased STM32MP157F-DK2 development board, and we are very new to this board. We are trying to install PyQt5 on this board but we are getting error "Package not found" and also we are not getting proper link to install Python "GPIO Libraries" So we required kind support for our future development by using this board.     Thanks and regards Shailesh Parashar Sr. R&D Engineer Scientific Mes Technik Pvt. Ltd. Indore    

Hi all.I'm developing a QT/QML application for my embedded openSTLinux project. This application has to play some videos with relative audio. I'm trying to play a mp4 file. If I use the following gst-launch-1.0 playbin uri=file:///home/root/media/my_video.mp4 video-sink="waylandsink sync=false"audio and video are played correctly. Instead, if I use QML code, for example this  Item { id: idVideo visible: true width: 1024 height: 600 Video { id: videoExample anchors.fill: parent source: "file:///home/root/media/my_video.mp4" autoPlay: true focus: true } }or thisItem { id: idVideo visible: true width: 1024 height: 600 MediaPlayer { id: mdpExample source: "file:///home/root/media/my_video.mp4" autoPlay: true } VideoOutput { id: videoExample anchors.fill: parent source: mdpExample } }the display shows nothing (black screen) but the audio is played correctly.Below the "gstreamer" plugins I have installed in my openSTLinux imagegstreamer1.

Hi all,I'm part of a software team that's working on a product based on the stm32mp15, running Yocto images based on the V4.1.1 ecosystem release. We're currently thinking of upgrading the Qt version in our images from Qt5 to Qt6, and while we are able to get it working, we've noticed that the performance is slightly slower than Qt5's - at least in the example applications we provide.We ran some tests on the stm32mp15-eval board and built two sets of st-example-image-qtwayland images from a openstlinux-weston distro based on the v4.1.1 ecosystem, using Qt5 in one image and Qt6 on the other. We applied the following changes:For the Qt5 images, install an alternative version of the cinematicexperience package built from this fork on commit 5d44dd7d4fd563b33570a14c2274e7fa9cc7d84f: https://github.com/alpqr/qt5-cinematic-experienceFor Qt6 images, install the same cinematicexperience package, but using commit fea04d7004a1608308c11189d74bb92d3decbe3d instead (basically, modifying the sources

STM32MP157AAAC custom board. Ethernet works with ECO 1 & 3.1. Used CubeMX to a add ethernet.  PHY provided clock to MAC. RGMII interface. 1000Mb/s2. Applied changes exactly as based on the WIKI and as generated by CubeMX to  OP-TEE U-boot and KernelBoot Log shows[ 1.548830] stm32-dwmac 5800a000.ethernet: IRQ eth_lpi not found   => this also happens on working boards.[ 1.689460] stm32-dwmac: probe of 5800a000.ethernet failed with error 1[ 22.383311] using random self ethernet address[ 22.386439] using random host ethernet addressu-boot seems the interface  and mii command workifconfig does not show eth0 interfaceNo other dwmac messages in boot log that those above

Dear I am creating an image for the stm32mp157c_dk2_defconfig board. Using buildroot the following error appears: Building stm32mp1CC drivers/io/io_block.cCC drivers/io/io_dummy.cCC drivers/io/io_mtd.cCC drivers/io/io_storage.cCC drivers/st/crypto/stm32_hash.cCC drivers/st/io/io_stm32image.cCC plat/st/common/stm32mp_auth.cCC plat/st/common/bl2_io_storage.cCC plat/st/stm32mp1/bl2_plat_setup.cCC drivers/mmc/mmc.cdrivers/st/io/io_stm32image.c: Na função ‘stm32image_partition_read’:drivers/st/io/io_stm32image.c:249:13: erro: ‘result’ may be used uninitialized [-Werror=maybe-uninitialized]249 | int result;| ^~~~~~cc1: todos os avisos estão sendo tratados como errosmake[2]: *** [Makefile:1131: /home/ubu/projects/buildroot/output/build/arm-trusted-firmware-v2.5/build/stm32mp1/release/bl2/io_stm32image.o] Erro 1make[2]: ** Esperando que outros processos terminem.CC drivers/partition/gpt.cmake[1]: *** [package/pkg-generic.mk:293: /home/ubu/projects/buildroot/output/build/arm-trusted-firmware-

Hi,in our STM32MP project, we have some unused securable peripherals. We generate our devicetree bindings with CubeMX where we have not selected anything for these peripherals. Accordingly, they do not show up in the `st,decprot` attribute in the `&etzpc` block in the devicetree.At boot, TF-A prints e.g.: "INFO: ETZPC: UART1 (3) could be non secure". What should this info tell us? Is there anything we need to be concerned about?According to the reference manual, the default register setting for USART1 should be "0b00" which corresponds to "secured". So in my opinion, USART1 should implicity be secured.Thanks in advance

HelloI would like to understand the EDMK (Encryption Decryption Master Key). This key is used to decrypt and encrypt BL2 and FIP binaries.Are there any other application of this key? For example, can it be used for LUKS ?Is it possible to access some API to encrypt/decrypt using this key? Or is it reserved to the ROM code?Thanks

on the left CubeMX generated for STM32MP157AAAC and on the right, dk1 dts included: stm32mp15-pinctrl.dtsi  (kernel dtsi)The biases are reversed and the pin controls are in separate groups in the DK1 dtsi files. and the slew rates are diferent.i am wondering if this is the reason why mmc dev 1 , mmc info uses 4 bits for GPIO even 8 bits bus is declared.