STM32 MPUs

Hi, I use boot1 pin as gpio key function. The boot1 is PI5, and I configure it in kernel dts code. When the system boot up, the input event0 device is shows, but I use hexdump can not get any key code data. Currently, my board is boot from sdcard. gpio-keys { compatible = "gpio-keys"; #size-cells = <0>;   user { label = "user"; linux,code = <BTN_1>; gpios = <&gpioi 5 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>; }; };

1. Can the display interface be driven by the M4 core while the A7 core is powered down?1a. Can the AXI interconnect peripherals be driven by the M4 while the A7 cores are powered down?2. Display controller - is there any loss in performance if using an external display controller via SPI interface instead of using the native RGB LTDC interface directly to a display?

..

..

Hi all,I updated my project from Morty (2.2) to Kirkstone (4.1). After doing the required fixes/updates on the recipes, I have problems booting the FSBL. I am using the Cube Programmer to flash the image. Below is the log:STM32CubeProgrammer API v2.13.0 | Windows-64Bits Read TSV File: C:\temp\stm32mp1-customized-img-kirkstone-alpha2\flashlayout_custom-os-image-debug\trusted\FlashLayout_nand-4-256_stm32mp153a-customized-img-cubemx-mx-trusted.tsv Number of partitions: 11 UR connection mode is defined with the HWrst reset mode Device Descriptor: |_bLength : 0x12 |_bDescriptorType : 0x01 |_bcdUSB : 0x0200 |_bDeviceClass : 0x00 |_bDeviceSubClass : 0x00 |_bDeviceProtocol : 0x00 |_bMaxPacketSize : 0x40 |_idVendor : 0x0483 |_idProduct : 0xdf11 |_bcdDevice : 0x0200 |_iManufacturer : 0x01 |_iProduct : 0x02 |_iSerialNumber : 0x03 |_bNumConfigurations : 0x01 Configuration Descriptor: |_bLength : 0x09 |_bDescriptorType : 0x02 |_wTotalLength : 0x48 |_bNumInterfaces : 0x01 |_bConf

Hi ST Community,   We have planned to use STM32MP131A MPU in one of our custom designs with low power consumption as the main target.   We have come across STM32 CubeMX v6.8.1 for estimating the individual current consumption in various modes and while utilizing different peripherals.   Unfortunately the current consumption details for necessary peripherals are not available for STM32MP1 series.   Can you provide us the details of any latest version which can support our requirement if available.  

I am trying to use the UART4 TX: H13 and RX: H14 pins for the tty console access.The TX from the MPU works fine as I can see the kernel boot logs, but cannot access the kernel command line. No prompt shows up on hitting ENTER.Here are my stm32mp15-pinctrl.dtsi UART4 configurations:   uart4_pins_a: uart4-0 {    pins1 {      //pinmux = <STM32_PINMUX('G', 11, AF6)>; /* UART4_TX */      pinmux = <STM32_PINMUX('H', 13, AF8)>;  /* UART4_TX */      bias-disable;      drive-push-pull;      slew-rate = <0>;    };    pins2 {      //pinmux = <STM32_PINMUX('B', 2, AF8)>; /* UART4_RX */      pinmux = <STM32_PINMUX('H', 14, AF8)>; /* UART4_RX */      

Hello.I'm trying to make simple openAMP with STM32MX(with STM32cubeIDE, .ioc file).The code is simiar to OpenAMP_TTY_echo. I include virt_uart.h and use VIRT_UART_Init code inside main function and others like making RxCpltCallback and registor callback is same as the example code. But the virtual Uart is not shown in /dev directory.I checked it with console inside cubeIDE.So, I debug it and find out the breakpoint in main function not work.the first image is about not working debug break point.second image is about no RPMSG tty in devafter I Suspend manually by clicking the button and make expression(VIRT_UART_Init(&huart1) like in the image below, the virtio is initialized and the ttyRPMSG0 is seen in /dev directoryWhat Is the problem of this?If I do wrong, what is the right way to deal with OpenAMP?

My hardware:STM32MP135FAE SLC NAND(MT29F4G08ABAF):256MB page:4K block:256K excuse me,How to configure makefile.sdk when compiling TF-A?​Here's what I tried：# Init default config settingsTF_A_DEVICETREE_nand ?= stm32mp135f-dkTF_A_EXTRA_OPTFLAGS_nand ?= STM32MP_RAW_NAND=1 PSA_FWU_SUPPORT=1 STM32MP_FORCE_MTD_START_OFFSET=0x00200000TF_A_BINARY_nand ?= tf-aTF_A_MAKE_TARGET_nand ?= all-----------------------------------------------------------------​FlashLayout_sdcard_stm32mp135f-dk-optee.tsv#Opt Id Name Type IP Offset Binary- 0x01 fsbl-boot Binary none 0x0 tf-a-stm32mp135f-dk-usb.stm32- 0x03 fip-boot FIP none 0x0 fip-stm32mp135f-dk-optee.binP 0x04 fsbl Binary nand0 0x00000000 tf-a-stm32mp135f-dk-nand.stm32P 0x05 fsbl Binary nand0 0x00080000 tf-a-stm32mp135f-dk-nand.stm32PE 0x06 metadata1 Binary nand0 0x00100000 metadate.binPE 0x07 metadata2 Binary nand0 0x00180000 metadate.binPE 0x08 fip-a1 FIP nand0 0x00200000 PE 0x09 fip-a2 FIP nand0 0x00600000 PE 0x0A fip-b1 FIP nand0 0x00a00000 PE

Hi I have problems with our custom board bringing up the VREFBUF. I eddited the devicetree as follows (also in U-Boot).&vrefbuf{ status = "okay"; compatible = "st,stm32-vrefbuf"; reg = <0x50025000 0x8>; regulator-min-microvolt = <2500000>; regulator-max-microvolt = <2500000>; clocks = <&rcc VREF>; vdda-supply = <&vdd>; };I also tried vdda-supply vdda. Did not change anything. When i check through the kernel messages there is no sign that the VREFBUF module is started or any error concerning VREFBUF.Also the VREFBUF is not working what is verified by the ADC Values.We use the ADC only on the M4 Core.The VREFBUFF can be activated from the M4 and the ADC is working fine.What am I doing wrong?I would be very grateful for some advice!.

I am trying to creating u-boot files for self definded project.Unfortunately i get the error during individual building (see https://wiki.st.com/stm32mpu/wiki/STM32MP1_Developer_Package#Installing_the_OpenSTLinux_BSP_packages:(Device Tree Source (arch/arm/dts/stm32mp153c-***-mx.dtb) is not correctly specified.The issue itself is correct. How do i create the *.dtb from STM32 Project (Device Tree Source available for all 4-5 Phases)? In which phase is the generation of this *.dtb File done (Kernel,TF-A,OPTEE,...)?

Hi,​Does anyone know how to enable dts and driver for ANA0/ANA01 ? We tried normal ADC and they are working well but can't find where relates to ANA0/ANA01Many thanks,

Hey there, I am working with a custom board based on an OSD32MP157F SoM. The pinout is very similar with the DK2 board with some minor differences, mainly the DSI_RESET pin. I have done several tests on STM32MP157f-dk2 boards with an eDP display that connects through a MIPI/eDP bridge to the DSI port of the DK. This works fine for a while now. In the custom board I do not have included any ltdc peripheral as I thought that it is not needed for driving the DSI bridge. I made a new image with the corresponding pinout and the bridge i2c driver initializes normally as seen in the bootlog. [ 1.735336] lt8911exb 0-0029: Success request pwr-gpio [ 1.740362] lt8911exb 0-0029: Success request rst-gpio [ 1.747446] lt8911exb 0-0029: LT8911EXB i2c test success chipid: 0xe0517 [ 1.785822] lt8911exb 0-0029: LT8911 tx pll locked [ 1.833083] lt8911exb 0-0029: video check: Vtotal = 0 [ 1.838486] lt8911exb 0-0029: video check: Hact(word counter) = 0 [ 1.844158] lt8911exb 0-0029: video check: Vact = 0 [

Hi, I designed a board with stm32mp135 and YT8531 phy chip. The ETH1 is not working and ETH2 is work good. They all output 125Mhz from phy to mac. But the ETH1 has reset dma failed. I had measure the 125Mhz is correct on phy side.Below is my dts code&eth1 { status = "okay"; pinctrl-0 = <&eth1_rgmii_pins_a>; pinctrl-1 = <&eth1_rgmii_sleep_pins_a>; pinctrl-names = "default", "sleep"; phy-mode = "rgmii-id"; max-speed = <1000>; phy-handle = <&phy0_eth1>;   mdio1 { #address-cells = <1>; #size-cells = <0>; compatible = "snps,dwmac-mdio"; phy0_eth1: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <1>; reset-gpios = <&gpiog 10 GPIO_ACTIVE_LOW>; reset-assert-us = <10000>; reset-deassert-us = <1000>; }; };   };   &eth2 { status = "okay"; pinctrl-0 = <&eth2_rgmii_pins_a>; pinctrl-1 = <&eth2_rgmii_sleep_pins_a>;   pinc

There are a number of functions used by the STM32_Programmer_CLI to accomplish secure firmware install and secure secrets provisioning (STM32U5 and STM32MP13 being the targets). I'm looking at what's needed to integrate this process into build/program/test harness - ideally via the API.   None of the examples seem to describe how to accomplish this via API. I was able to retrieve the chip certificate for the U5 via the API after wiretapping/verbose debugging of the CLI tool. It pretty straight forwardly reads a specific address via the DFU. What I couldn't figure out is where this address is coming from. On another board (L5) its a different address. I'd really like a general solution for this.   Is there documentation or examples of using the API to accomplish the tasks described in AN4992 (STM32MCUs secure firmware install (SFI) overview) or AN5510 (Overview of the secure secret provisioning (SSP) on STM32MP1 Series)?    

Please suggest a MCU that is available in market to develop camera-based solution with following capability/interfacing: camera max up to 3mp and upto VGA/1080P resolution). with JPEG saving and Video recording options, LCD interface.Please suggest a MCU that is available in market to develop camera-based solution with following capability/interfacing: camera max up to 3mp and upto VGA/1080P resolution). with JPEG saving and Video recording options, LCD interface.

Does STM32MP13 support decryption on the fly binary code on SD/MMC, entire SD/MMC or just TF-A firmware?We have customers need protect their code on SD/MMC, does STM32MP13 have any feature to support that?Thanks

I need to create an application that can handle text translations with gettext() in C code.How to add localizations to the image to be generated?I added these configurations in the build recipe:ENABLE_BINARY_LOCALE_GENERATION = "1"GLIBC_GENERATE_LOCALES = "en_US.UTF-8 it_IT.UTF-8 en_GB.UTF-8 ro_RO.UTF-8 es_CO.UTF-8 es_CL.UTF-8 pt_BR.UTF-8"IMAGE_LINGUAS = "en_us it_it en_gb ro_ro es_co es_cl pt_br"With the following errors:ERROR: image-rel-1.0-r0 do_rootfs: Unable to install packages. Command 'openstlinux-5.10-dunfell-mp1-21-11-17/build/tmp-glibc/work/board-ostl-linux-gnueabi/image-rel/1.0-r0/recipe-sysroot-native/usr/bin/ apt-get install --force-yes --allow-unauthenticated --no-remove locale-base-en_us locale-base-it_it locale-base-en_gb locale-base-ro_ro locale-base-es_co locale-base-es_cl locale -base-pt_br' returned 100:Reading package lists...Building dependency tree...E: Unable to locate package locale-base-en_usE: Unable to locate package locale-base-it_itE: Unable to locate pack

..

hiI am working on a project using stm32mp157fad.For the project created using stm32cubemx and stm32cubeide, I created a custom image by referring to the site below and uploaded it to the sd card using the dd command.But openstlinux is not booting up so I want to check if there is a problem with the schematic.1.Create an OpenSTLinux image​https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machine​2.dd commandhttps://wiki.st.com/stm32mpu/wiki/How_to_populate_the_SD_card_with_dd_commandFirst of all, I would appreciate it if you could tell me if the circuit diagram is written correctly.1.power circuit diagram2.SD Card Used Pin Second, I would like to know if the Boot-related program is entered in the ROM when the STM32MP1 series is shipped from the factory.thank you

...

Have tried building U-Boot with a few changes compared to the default ones using the STM32MP1 Android distribution.When changing the ssbl-trusted-fbemmc.img which contains the U-Boot binaries, the U-Boot start fails showing the following boot logs:/TC: OP-TEE version: 3.9.0-22-gc2249e24d (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 Sun May 21 22:35:04 UTC 2023 armD/TC:0 0 check_ta_store:635 TA store: "early TA"D/TC:0 0 check_ta_store:635 TA store: "Secure Storage TA"D/TC:0 0 check_ta_store:635 TA store: "REE"D/TC:0 0 early_ta_init:248 Early TA 023f8f1a-292a-432b-8fc4-de8471358067 size 38396D/TC:0 0 mobj_mapped_shm_init:446 Shared memory address range: 2dc00000, 2fc00000I/TC: Platform stm32mp1: flavor PLATFORM_FLAVOR - DT stm32mp157f-ev1.dts.........D/TC:0 0 stm32_bsec_shadow_register:235 BSEC shadow warning: OTP lockedD/TC:0 0 check_rcc_secure_configuration:790 RCC/PWR secure hardening: TZEN enable, MCKPROT disableI/TC: Initializ

Hello all,I am used to the regular MCUs STM32Fx families where I'm used that the main.h has all the #defines of the GPIOs and other peripherals.I'm now using STM32MP1 generating code for CM4 and noticed it is generate any #define information.also, it is not initializing GPIOs state.Why is it generating no initialization of GPIOs or other user label #defines?

Hello,We have a design that uses an STiD337-DCB CPU.We're trying to find out if we can use an STiD337-YCB instead.However I can't find any documentation that explains what DCB/YCB stands for ?

Hi there,we are in the process of developing a product based on the STM32MP151F which will be USB powered (USB 2.0 device).We are aiming to have it connected to an eMMC for mass storage and we would like to achive the highest R/W speed which should be 200MB/sec using HS200.1) If my understanding is correct we cannot use the STM32MP157F-EV1 as starting point as the boards is using the STPMIC1A which regulates the eMMC VCCQ @3.3V and it incompatible with HS200, is it correct?2) Has the STM32MP151 ever been tested at HS200 speed with a commercially available eMMC? Is there e refence design that e can use as starting point?3) We have read the "2.3.19 DLYB limits SDMMC throughput" errata. Does it implies that HS200 is unusable? Or we can use it and it is just enough to disable the DLYB? If so why should we enable the DLYB in the first time?4) If we use the STPMIC1B which regulates VDD at 1.8V making it compatible with HS200, is there any drop in the MPU performances?5) Is there a refer