STM32 MPUs

I understand that there would be great performance penalty for the combination of cortex A35 core with octospi psram, but I want to know if this is possible after all? Of course, without great effort on modification of u-boot and kernel code. Just bring up psram in uboot and hopefully cortex A will treat it as usual without significant difference than that of lpddr4. We have a custom-developed product that requires absolutely active state low current as well as PCIE and Linux (for multiple file system on HDD/SSD). Weird enough, may be mmu-less cortex M such as stm32h7 will do the job either, but, we don't trust linux on mmu-less processors. Cortex A will be much better in stability.

Hello, If I put my new machine conf and device tree in meta-st-stm32mp-addons I can compile device tree and my image without any error. But if I use my own layer meta-my-layer (in meta-st), machine config is used but I have this message : | make[2]: *** No rule to make target 'arch/arm/boot/dts/st/stm32mp153c-linux-platform-mx.dtb'. Stop. I read the forum and documentation but, I don't find a way to have a working project. Could you explain me how to create my own layer to be outside meta-st-stm32mp-addons  (to use my own git) and compile my new machine with associated device tree ?Thank you so much for your help

Hi, I am using STM32MP257F-DK microcontroller. I have never used a dual cortex before. All I want to do is to generate a simple STM32CubeIDE project which also has a .ioc file. I want to debug it via CubeIDE.1) Do I need OpenAmp to successfully flash the code?2) I have already set up the SDK, are there other settings I need to take care of?When I try to flash my current project, It always stops at 78% like shown in the picture below.

Hello everybody,currently i am trying to migrate from KEIL uvision to CubeIDE.CubeIDE Version: 1.13.2Build: 18220_20230914_1601Target: STM32MP157Debug Probe: STLink-v3miniE or othersExample Project: OpenAMP_FreeRTOS_echo_CM4 When I start a debug session in production mode, the M4 firmware is loaded and starts running. I have no problem with this.In Keil it was possible to reset the MCU during a debug session in production mode quite easily by pushing a button. So it was possible to set a breakpoint at the beginning of application in main().In CubeIDE there is no such possibility, am i right? Or can it be done in a similar and convenient way??I have not found a solution to this "problem".The conversation in this Topic deals with the same issue but the answer is not satisfactory for me.I tried several thing under Debug Configurations->Startup->Initialization Commands etc but without success.I hope that it is not necessary to write individual reset bits in the registers by

HelloI am trying to debug M4 firmware on my custom STM32MP157C board.I have a reference operating system built with yocto on which this works correctly.I have to build system with a changed configuration and debugging of the same firmware is not working.Of course I saw this video https://www.youtube.com/watch?v=YIhzzgJmop0When I click the Debug button, the application correctly uploads however it won't start.I get the message:Error in final launch sequence:Failed pre launchFailed pre launchFirmware remoteproc load failed, please:1. make sure that /lib/firmware on your target has space2. make sure that /lib/firmware has write accessOf course my target has space and write access - in other case file transfer will not be successful.Starting the firmware manually works ok with this commands:echo OpenAMP_raw_CM4.elf > /sys/class/remoteproc/remoteproc0/firmwareecho start >/sys/class/remoteproc/remoteproc0/state Question: how to determine more precisely what failed?Or maybe any hin

Hi,Release notes for STM32MPU ecosystem v4.0.0 mention “Add support of Firmware Update feature�?. Is there anymore information available on this feature? Or is it utilising an existing Yocto swupdate layer?Any additional information would be appreciated. Thanks

Hi, I was boot STM32MP135D-ODYSSEY with SD as boot option,using https://wiki.st.com/stm32mpu/wiki/STM32MPU_Distribution_Package and added odyssey dts. facing CRC check failed on FWU metadata and ERROR: loading of Bkup-FWU-Metadata failed. Can you help me with this.  ---- ~$ sudo picocom -b 115200 /dev/ttyACM0picocom v3.1port is : /dev/ttyACM0flowcontrol : nonebaudrate is : 115200parity is : nonedatabits are : 8stopbits are : 1escape is : C-alocal echo is : nonoinit is : nonoreset is : nohangup is : nonolock is : nosend_cmd is : sz -vvreceive_cmd is : rz -vv -Eimap is :omap is :emap is : crcrlf,delbs,logfile is : noneinitstring : noneexit_after is : not setexit is : noType [C-a] [C-h] to see available commandsTerminal readyNOTICE: CPU: STM32MP135D Rev.YNOTICE: Model: Seeed STM32MP135D Odyssey BoardINFO: PMIC version = 0x21INFO: Reset reason (0x35):INFO: Power-on Reset (rst_por)INFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe0000INFO: FCON

Hello! everyone. //-------------- Host ------------- OS: Ubuntu 22.04 Kernel: Linux leonsu-MINIPC-VC66-C2 6.8.0-52-generic  //----------- board ---------- STM32MP257F-DK kernel: Linux stm32mp2-e3-aa-db 6.6.48  //----------------------------------------- I followed the STM32MPU Developer Package[1] and  X-LINUX-QT Expansion Package[2] to setup up the SDK and X-LINUX-QT Developer Package, respectively. SDK Version: 6.0.0  X-LINUX-QT Developer Package Version: 2.0.1   I try to build qt example followed the section 7.1[2], I get some error message in following: Spoiler (Highlight to read) /home/leonsu/STM32MPU-Ecosystem/Developer-Package/SDK/sysroots/x86_64-ostl_sdk-linux/usr/libexec/aarch64-ostl-linux/gcc/aarch64-ostl-linux/13.3.0/ld: warning: libicui18n.so.72, needed by /home/leonsu/STM32MPU-Ecosystem/Developer-Package/SDK/sysroots/cortexa35-ostl-linux/usr/lib/libQt6Core.so.6.5.3, not found (try using -rpath or -rpath-link)/home

I have been trying to find a way to increase the icon size for the STM32CubeIDE toolbar. Today I found a way that worked for me.  

Hello, at a glance the 40 Pin GPIO on the STM32MP257F-DK appears to be matching the Raspberry Pi standard, is this correct ? 

 Hi all,I am taking my first steps with the STM32MP257F-EV1, following the "Let's Start" guide on the wiki.At startup, I get a blinking RED LD1, which stops blinking as soon as I connect the CN15/USB_OTG port of the STM32MP257F-EV1 motherboard using a USB Type-A to Type-C cable and press the Reset button, as indicated in the guide (https://wiki.stmicroelectronics.cn/stm32mpu/wiki/Getting_started/STM32MP2_boards/STM32MP257x-EV1/Let%27s_start/Populate_the_target_and_boot_the_image#Populate_the_SD_card).The LD1 LED then either stays ON or OFF, but no device is detected under Linux. I have also tried the same procedure on a native Windows machine, but no device appears (even in Device Manager). As a result, no device in DFU mode is detected by CubeProgrammer, either through the GUI or the CLI interface.Having tried several possible workarounds—such as changing cables, reinstalling drivers and VMs, and reinstalling CubeProgrammer and the supporting software—I analyzed the USB_OTG (DRD)

"I want to download the STM32MP2 Developer SW Package.By visiting the page on the wiki (https://www.st.com/en/embedded-software/stm32mp2dev.html#get-software) and accessing the download link below, the file that opens is not 'SOURCE' but 'SDK(en.SDK-x86_64-stm32mp2-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar.gz)'.Where can I download the SOURCE?My location is South Korea."

Where can I configure the Voltage of each individual Buckconverter od LDO?

Hi,I try to couple LCD TFT ili9881c (mipi dsi 2 lanes interface) with stm32mp157caa3. My custom driver seems to be loading correctly. When I type lsmod I getModule Size Used by cfg80211 651264 0 usb_f_rndis 24576 2 u_ether 20480 1 usb_f_rndis libcomposite 49152 10 usb_f_rndis galcore 516096 2 panel_ilitek_ili9881c 20480 0 dwmac_stm32 16384 0 stmmac_platform 20480 1 dwmac_stm32 stm32_adc_core 20480 0 spi_stm32 24576 0 sch_fq_codel 20480 3 ip_tables 24576 0 x_tables 24576 1 ip_tables ipv6 512000 42Unfortunately, the display is not working, only the backlight is working.I checked twice the dts and looks good, driver is loading well. I can't find anything with 'drm'. What I missed? Shall I add some additional driver in the kernel or something install in the roofs?In the log, I can see only[ 0.079013] platform 5a000000.dsi: Fixing up cyclic dependency with 5a001000.display-controllerand[ 13.730531] [drm] Initialized stm 1.0.0 20170330 for 5a001000.display-controller on minor 0

We are pleased to announce that the release 6.14.0 of STM32CubeMX is available. What is new in 6.14.0: Added the support for the STM32WBA6xxx microcontrollers and: Added the support for USBX multi-instance Added the support for the memory management tool (MMT) Added the support for the STM32WBA65I-DK1 Discovery kit and NUCLEO-WBA65RI Nucleo board Deployed the Start From Board feature on the NUCLEO-WBA65RI Improved the Power Delivery (USB PD) functionality for STM32H7Rx/7Sx and STM32N6 microcontrollers by upgrading the USB PD library core to v5.3.0 Adapted STM32CubeMX user interface to allow the user to: Access the Compare Projects utility from the home page and compare two existing projects Compare two existing projects without save down Improved the build process with CMake Update the RIF panels to indicate the peripherals that are not supported by STM32MP2 products. Removed the Secure Manager boot path Main fixed issues in 6.14.0: Refer to the STM32 microcontroller wiki at:http

I'm using the Yocto-based OpenSTLinux embedded software on a STM32MP25x and I don't understand which portion of the SRAM1/2 is free to use at runtime. Aside from the first 4kBytes of the SRAM1 reserved for OTP shadow, can the rest be fully used, or is it also reserved ? Additionally, in chapter 2.4.2 of the reference manual (RM0457), it states that SRAM1/2 can be accessed through the following address ranges [0x0A04 0000, 0x0A08 0000[, [0x0E04 0000, 0x0E08 0000[, [0x2004 0000, 0x2008 0000[ and [0x3004 0000, 0x3008 0000[. Why are there four physical addresses for SRAM ? Should Cortex-A35 and Cortex-M33 use specific regions to communicate with each other ?    

Hello,I created already several SD-cards images (.raw) using the `create_sdcard_from_flashlayout.sh` script, from both starter kit and Yocto build.Note: Currently working on the STM32MP256 evaluation board.We would like to have something similar with USB:1) Create a *.raw image2) Use `dd` or Raspberry Pi Imager to flash the USB memory3) Select the boot pins on the evaluation board (all-zeros for USB boot)4) Insert the USB memory5) Power-on and wait until Linux is loaded.To my surprise, this process that works fine for sdcards does not work for USB (The card does not boot). This also makes sense considering that :* The script is called `create_sdcard....` and not `create_usb`* The *.tsv are either _emmc_ or _sdcard_But why there is not _usb_ tsv or create_usb script?All the documentation found about USB is by connecting the computer and using the USB link to flash the emmc. This is fine in some environments, but not in others.How to create a bootable OpenST-Linux USB memory ?

Hello,We had to switch out an SD card for eMMC and we kept with SDMMC1. I am aware of having to burn the fuses to get eMMC to default to SDMMC1 which I did. I was able to get it to flash successfully, and now when you switch it to 010 it will boot from SDMMC1 using eMMC. It will then get an error message,     Terminal ready gNOTICE: CPU: STM32MP135A Rev.Y NOTICE: Model: STMicroelectronics custom STM32CubeMX board - openstlinux-6.1-yocto-mickledore-mpu-v24.06.26 INFO: PMIC version = 0x21 INFO: Reset reason (0x35): INFO: Power-on Reset (rst_por) INFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe0000 INFO: FCONF: Reading firmware configuration information for: stm32mp_io INFO: FCONF: Reading firmware configuration information for: stm32mp_fuse INFO: Using EMMC INFO: Instance 1 INFO: Boot used partition fsbl1 NOTICE: BL2: v2.8-stm32mp1-r2.0(debug):lts-v2.8.15-dirty(567af710) NOTICE: BL2: Built : 00:51:33, Jan 26 2024 INFO: BL2: Doing platform setup

Hello,I am running a Linux image based on meta-st-stm32mp (hardknott branch).I currently have the following in my host device tree:reserved-memory { #address-cells = <1>; #size-cells = <1>; ranges; mcuram2: mcuram2@10000000 { compatible = "shared-dma-pool"; reg = <0x10000000 0x40000>; no-map; }; vdev0vring0: vdev0vring0@10040000 { compatible = "shared-dma-pool"; reg = <0x10040000 0x1000>; no-map; }; vdev0vring1: vdev0vring1@10041000 { compatible = "shared-dma-pool"; reg = <0x10041000 0x1000>; no-map; }; vdev0buffer: vdev0buffer@10042000 { compatible = "shared-dma-pool"; reg = <0x10042000 0x4000>; no-map; }; mcuram: mcuram@30000000 { compatible = "shared-dma-pool"; reg = <0x30000000 0x40000>; no-map; }; retram: retram@38000000 { compatible = "shared-dma-pool"; reg = <0x38000000 0x10000>; no-map; }; gpu_reserved: gpu@d4000000 { reg = <0xd4000000 0x4000000>; no-map; }; }; mlahb: ahb { compatible = "st,mlahb", "simple-bus"; #address-cel

I need to migrate my project from STM32MP135F-DK board to custom hardware (SoM based on STM23MP135DAF7). To build images I use Yocto Project (Scarthgap) with meta-st-stm32 layer.As a begginer in device trees and BSPs world, I would like to get some review from more experienced developers, to ensure that the path and procedure I have chosen to follow is correct.I found bring-up guide on FAQ: STM32MP1 Bring-up Is this the most detailed and up-to-date guide I can find?According to that FAQ, the modification I have to make is tailoring device trees (for TF-A, Uboot, kernel) to my custom hardware. Is there a requirement to develop custom BSP for this hardware or the BSP stays the same (STM32MP135F-DK BSP, I guess it is the meta-st-stm32 layer)?I've also found this FAQ: How to create DT adapted to your design there is also link to LAB in which creating CubeMX project for some DK boards is presented. This lab is adapted to Ecosystem 5.0, are there any examples for 6.0? Or

Regarding OpenStLinux (yocto) for stm32mp257f. Mickledore: everything works fine for our custom stm32mp257f board. Scarthgap: everything works except 3D graphics. When loading module etnaviv we get the following system hangup (optee panic):  [ 13.139084] etnaviv etnaviv: bound 48280000.gpu (ops gpu_ops [etnaviv]) [ 13.186566] videodev: Linux video capture interface: v2.00 E/TC:1 0 Panic at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r1/core/drivers/clk/clk-stm32mp25.c:1976 <clk_stm32_pll_init> E/TC:1 0 TEE load address @ 0x82000000 E/TC:1 0 Call stack: E/TC:1 0 0x82007ed8 ...<cut>... E/TC:1 0 0x820064b0 I/TC: Halting CPU 0  We understand it can be hard to say "this is your problem", but any information on where to look would be much appreciated! Best regards,Anton

Hello,I am struggling with improper color management for our display connected as LTDC. I prompt for drm state with cat /sys/kernel/debug/dri/0/stateI wonder why I get  format=RG16 (that is true, we use RGB565 LTDC interface) and color-encoding=ITU-R BT.601 YCbCrcolor-range=YCbCr limited rangeat the same time.  I expect color encoding to be RGB.  Am I right ?Here is the whole output:utc:~# cat /sys/kernel/debug/dri/0/state plane[33]: plane-0crtc=crtc-0fb=38allocated by = [fbcon]refcount=2format=RG16 little-endian (0x36314752)modifier=0x0size=1024x600layers:size[0]=1024x600pitch[0]=2048offset[0]=0obj[0]:name=0refcount=3start=00010000size=1228800imported=nocrtc-pos=1024x600+0+0src-pos=1024.000000x600.000000+0.000000+0.000000rotation=1normalized-zpos=0color-encoding=ITU-R BT.601 YCbCrcolor-range=YCbCr limited rangeuser_updates=1fpsplane[36]: plane-1crtc=(null)fb=0crtc-pos=0x0+0+0src-pos=0.000000x0.000000+0.000000+0.000000rotation=1normalized-zpos=0color-

Hello,Whenever I build OpenSt-Linux with Yocto, or download the starter kit, I get several flashlayouts:In images/stm32mp2/flashlayout_st-image-weston:* extensible* fastboot* fastboot-opteemin* optee* opteeminI can make some supposition about: optee, opteemin being a simplified or lighter version of optee, etc.Is there any documentation about:* What are the purpose of each layout* What are the differences between them* Links to documentation about related technologies* ...

Hello,Excuse me, has anyone had experience accelerating the Whisper-tiny model for speech-to-text tasks using the NPU on the STM32MP257-EV1 board? From my understanding, the process involves converting the PyTorch or TensorFlow Whisper model to TensorFlow Lite format and then using the ST Edge AI tool to convert it to .nb format for acceleration.I followed the approach provided by @nyadla-sys on GitHub to obtain the whisper-tiny.en.tflite model (https://github.com/nyadla-sys/whisper.tflite/blob/main/models/generate_tflite_from_whisper.ipynb). However, when I run the following command:./stedgeai generate --target stm32mp2 --model whisper-tiny.en.tfliteI encounter the following error: ST Edge AI Core v2.0.0-20049INTERNAL ERROR: 'NoneType' object has no attribute 'rank' I am unsure why this error occurs. Could it be due to an internal input being None? I am also uncertain whether this approach is correct, or if I should separate and accelerate the encoder and decoder modules ind

Dear all, we use custom board with STM32MP1 SoC onboard.  We use Yocto with OE, STM, Qt and custom layers for building target images. In our device we utilize 7-inch display connected by LVDS with RGB666 wiring.  If I load bitmap image from U-boot, all colors are fine, so I suggest, display wiring is correct.  But if I load the same bitmap from Linux, some colors are spoiled.  For example, grey colors (like 0xA0A0A0 in RGB888) become green (attachment: grey.bmp is original bitmap, grey.jpg is a screen photo).  This is not a Qt issue, as I get the same result using Plymouth splash screen or Gstreamer tool for loading bitmap files.  What might be the culprit ? Any help or hint is appreciated.