STM32 MPUs

error is logged as > Label or path sram not foundThe DTS file at the failing line reads   &sram{ dma_pool:dma_pool@0{ reg = <0x50000 0x10000>; pool; }; };  I'm assuming this is to specify where the SRAM pool is. But this automatically generated file fails at build.The CubeMX project has worked before, just upgraded to mickledore and the latest CubeMX but I don't think that is the problem.I have done clean bitbakes etcBuilding the sample machines and configs appears to work perfectly its only my own new machine that is failing> looking at the 'equivalent' DTS file in one of the standard builds I dont see SRAM specified anywhere. I think my nachine specification is off although it was build using the tutorial in the docs....... more digging.

Hello, i am using an stm32mp1-dk2 board. For using fw_printenv and other uboot tools from user space one must define a "/etc/fw_env.config" file. I can see that the "/uboot.env" file is driectly saved under the root "/" and so i defined the "fw_env.config" like that:   # cat /etc/fw_env.config # Device name Device offset Env. size Flash sector size /uboot.env 0x0000 0x2000 But every time i run fw_printenv i get following msg: # fw_printenv Warning: Bad CRC, using default environment bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=5 baudrate=115200 As you can it claims about "BAD CRC...". My question is: How should a correct "fW_env.config" looks like for a stm32mp1-dk2 board?   Thanks    

I am not able to launch SPI activation outputs just using datasheet information. I have tried everything and the status outputs do not change. By making use of an oscilloscope, I have checked that the data bytes transmitted (0xAC01, that would entail an activation of OUT1) through MISO line are correctly sent. Moreover, we have changed SPI mode, frequency, mode of sending the bits…but nothing happens. I am not able to switch on/off internal mosfets after command byte writing operation. I also read fault register and get 0x0000, which indicates that no fault is present. I do not know if it is a timing issue or something else. I have changed the MCU used to act as a master, but nothing got.Thanks in advance!

Hello,I'm trying to debug a firmware in production mode using STM32cudeIDE, running on the cortex M4 on the stm32MP157F. When debugger starts it seems g_pfnVectors isn't properly created. When I stops debugger and view the dissambled code I found that it always points on the first line:No source available for "g_pfnVectors() at 0x0"Also, I had changed the linker script to be able to allocated more memory for the SDRAM using both memory regions available (at 0x10000000 and 0x30000000):MEMORY{RETRAM_interrupts (xrw) : ORIGIN = 0x00000000, LENGTH = 0x00000600SRAM1_text (xrw) : ORIGIN = 0x10000000, LENGTH = 256KSRAM2_data (xrw) : ORIGIN = 0x30020000, LENGTH = 200KSRAM3_ipc_shm (xrw) : ORIGIN = 0x10040000, LENGTH = 64KSRAM4 (xrw) : ORIGIN = 0x10050000, LENGTH = 64K}Also, here is my definition for the DT's memory reservation :Spoiler (Highlight to read)reserved-memory {#address-cells = <1>;#size-cells = <1>;ranges; /* USER CODE BEGIN reserved-memory */ mcuram2:mcuram2@1

Hello,I'm trying to debug a firmware in production mode using STM32cudeIDE, but when debugger starts it seems g_pfnVectors isn't properly created. When I stops debugger and view the dissambled code I found that it always points on the first line:00000000: bge.n 0xffffffbabut the address 0xffffffba is not assigned to my firmware; if I go to this point I got the following message: ffffffba: Failed to execute MI command: -data-disassemble -s 4294967226 -e 4294967319 -- 3 Error message from debugger back end: Cannot access memory at address 0xffffffbaHave you any suggestion on how to solve this issue??Here the memory definition of linker script:MEMORY   {   RETRAM_interrupts (xrw) : ORIGIN = 0x00000000, LENGTH = 0x00000298   RAM2_ipc_shm (xrw) : ORIGIN = 0x00001000, LENGTH = 0x00011000   FLASH_text (rx) : ORIGIN = 0x10000000, LENGTH = 0x00040000   RAM1_data (xrw) : ORIGIN = 0x10040000, LENGTH = 0x00020000   }and here's DT's memory reservation :reserved-

Hi,I have a problem with hanging up my board occasionally when an issue from the console reboot.I read about and the internet says this is a problem with the EMMC memory's power cycle.So I followed by a linkhttps://github.com/orangepi-xunlong/openwrt/commit/14d3a99e17f2ec6097eeef97530cba2d62c58d3c#diff-1335d7b270cc58c5342d5e2843730580bfe5d8048d765abb753050095929d85dbut still, after a few reboots my board stacked.My final message from the console is as follows [ OK ] Stopped Create Static Device Nodes in /dev. [ OK ] Reached target System Shutdown. [ OK ] Reached target Late Shutdown Services. [ OK ] Finished System Reboot. [ OK ] Reached target System Reboot. [ 32.494373] watchdog: watchdog0: watchdog did not stop! [ 32.522678] systemd-shutdown[1]: Using hardware watchdog 'STM32 Independent 0 [ 32.533457] systemd-shutdown[1]: Watchdog running with a timeout of 2min. [ 32.559399] systemd-shutdown[1]: Syncing filesystems and block devices. [ 32.687090] systemd-shutdown[1]: S

Hello. We already have a custom board based on STM32MP151CAD3 with an eMMC. The following pins are different with default eMMC pins.SDMMC2_CMD: PA0SDMMC2_D1: PB7 As not default pins are used, we need to update OTP value. Here are my result. OTP3 = 0x00000004emmc_if_id=2: SDMMC2(uses non default AFmux defined in OTP).OTP5 = 0x27A41094SDMMC2_CMD = PA0 (bits[15:0]: port0=1=GPIOA, pin0=0, afmux0=9, mode0=4=AF;pull-up;medium-speed)SDMMC2_D1 = PB7 (bits[31:16]: port1=2=GPIOB, pin1=7, afmux1=10, mode1=4=AF;pull-up;medium-speed)However, it does not work. I also trace its ROM log. Attached is log.

Hi, let us know, for this development kit,1. Linux customization possible.2. support for development

Hello, I built an image with the following configuration by using the ST wiki pages:STM32MP157D-DK1 Evaluation BoardYocto KirkstoneSTM32MP1-Ecosystem-v4.1.0meta-java layer (branch kirkstone)I have used the following command to create an image:./create_sdcard_from_flashlayout.sh ../flashlayout_st-image-weston/extensible/FlashLayout_sdcard_stm32mp157d-dk1-extensible.tsvI burnt the image to SD card (came with the board itself) with dd, using the following command:sudo dd if=../flashlayout_st-image-weston/extensible/../../FlashLayout_sdcard_stm32mp157d-dk1-extensible.raw of=/dev/sdb bs=8M conv=fdatasync status=progressWhen I boot the board kernel panics. Please see the following kernel output:bootfs: Updating bad block inode.Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structure Pass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationbootfs: ***** FILE SYSTEM WAS MODIFIED *****bootfs: 54/16384 files (3.7

Hello, In order to use the non-default QSPI boot locations, my understanding is port0-port3, 4 signals need to be defined in OTP words 3, 5, and 6 based on a similar question about SDMMC1 discussed here:https://community.st.com/t5/stm32-mpu-products/how-to-change-emmc-interface/td-p/344994For QSPI the default signals according to the getting started guide, AN5474, are:PB2 QUADSPI_BK1_NCSQUADSPI_BK1_NCSPF10 QUADSPI_CLKPF8 QUADSPI_BK1_IO0PF9 QUADSPI_BK1_IO1What is the mapping for the OTP ports 0-3 to the functional signal names NCS, CLK, IO0, IO1?i.e. port 0=NCS, CLK, IO0, or IO1? Same for the other three ports.I was not able to find this described or an example for QSPI and OTP.Thanks.  

Hi,we're using STM32MP1 for our project. we have connected super cap to VBAT.our expectation is to have VBAT supply power to RTC *alone*. we dont want RAM content to be retained. so that RTC shall remain powered for long time. currently the VBAT is supplying back up power for both RAM contents & also for RTC, so we're experiencing RTC back up for just 5 hours instead of expected 5 days. Kindly help out. should we use RREN/BREN in this case?

Hello,We are using the STM32MP151 custom board microprocessor with an external flash memory (emmc). At start-up the board and linux boot correctly, but when reboot it, the board keeps in uart/usb boot loader mode and doesn't boot. It happen also when we reboot with a push button in rst pin and with software reboot.When we reboot in software reboot, the last traces we get are:Could you help us? Thanks.Regards.

I have done the yocto build, and i used below bitbake command to generated distribution package.bitbake st-image-weston --runall=deploy_archivesBut i have updated the sources now how to clean and rebuild the archives.used board : STM32MP135FEco system: v4.1.0With Regards,Shashi

Hello, I have an interprocessor communication problem using the OpenAMP_TTY_echo example on the STM32MP157C-EV1 board.I am tring example OpenAMP_TTY_echo, to comunicate between M4 and A7 on the STM32MP157C-EV1 board.I can't find the solution, and I need your help.I installed Linux (en.flash-stm32mp1-openstlinux-6-1-yocto-mickledore-mp1-v23-06-21.tar.gz) downloaded from:https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-EV1/Let%27s_start/Populate_the_target_and_boot_the_imageand installed to the STM32MP157-EV1 with STM32 Cube Programmer V2.14.0On my PC: I am using Keil V5.36, compiled the example OpenAMP_TTY_echo without error.The example code runs without problem. either with the Tools: STM32MP1 Load and Run command, or from the Debugger.I traced the code and it runs normally in the while(1) loop of app_main (main.c)(without going through an "Error_Handler")When I execute ssh command to connect to the STM32MP157-EV1 board, it seems that none of the devices tt

Hello,I've been trying to boot my STM32MP157F-EV1 evaluation board from the SD card but I get the result that is shown in the image when using minicom. I used to work on the board for a long time with no problem, but recently I tried booting it again and this happened. I'm not sure if it's a hardware or a software problem. I made sure that the SD card is inserted correctly and that the boot switch configuration is set for SD card. I tried ping and ssh commands with the IP address but no connection is visible.Is there a way to fix this problem? Any help would be appreciated.

Hello,I try to connect a popular Arduino board PCM5102a with my board which is base on STM32MP135.I read some documentation from the linkhttps://wiki.st.com/stm32mpu/wiki/ALSA_overviewhttps://wiki.st.com/stm32mpu/wiki/Soundcard_configurationhttps://wiki.st.com/stm32mpu/wiki/SAI_device_tree_configurationhttps://wiki.st.com/stm32mpu/wiki/SAI_Linux_driverbut pcm, i2s and sound topics are something I have only a base knowledge of, so please give some advice and hints.My dts looks like / { sound { compatible = "audio-graph-card"; label = "STM32MP1-audio-test-card"; routing = "Playback" , "MCLK", "Capture" , "MCLK", "MICL" , "Mic Bias"; dais = <&i2s1_port>; status = "okay"; }; codec: pcm5102a-codec { compatible = "ti,pcm5102a"; #sound-dai-cells = <0>; clocks = <&i2s1>; /* The codec is a consumer of I2S2 master clock */ clock-names = "MCLK"; /* Feed MCLK codec clock with I2S2 master clock provider */ codec_port: port { codec_endpoint:

Hi,my question is how to set up resolv.conf with the DNS nameserver not to lose it after reboot.Some of the manuals on the internet want to modify /etc/systemd/resolved.conf by uncomment DNS line and provide a valid ip. Unfortunately, it's not working for Openstlinux.The DNS only works when updated /etc/resolv.conf.Of course, I can update /etc/resolv.conf automatically during the system boot-up, but in my opinion this method is not too elegant.Can You have some solution for my issue?ThanksBRMichał

Hi,what's the state of the S24_LE format support on the STM32MP1 line of boards? It seems that S16_LE and S32_LE formats are supported on the I2S dai, however S24_LE is rather unavailable. Is there a way to somehow enable it (maybe through Cube MX) or is it completely unsupported?When running alsa speaker-test utility with hardware devices (not default) the S24_LE format is being rejected.Thanks!

Hi all.In my openstlinux yocto image has been included the SGTL5000 audio codec management. I have a problem. On the headphone output I heard only a continuous pink noise.These are some information from my system:zcat /proc/config.gz | grep SGTL CONFIG_SND_SOC_SGTL5000=y:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: STM32MP1 [i.Core STM32MP1], device 0: 4400b004.audio-controller-sgtl5000 sgtl5000-0 [4400b004.audio-controller-sgtl5000 sgtl5000-0] Subdevices: 1/1 Subdevice #0: subdevice #0 :~# aplay -L null Discard all samples (playback) or generate zero samples (capture) pulse PulseAudio Sound Server default Default ALSA Output (currently PulseAudio Sound Server) sysdefault:CARD=STM32MP1 i.Core STM32MP1, 4400b004.audio-controller-sgtl5000 sgtl5000-0 Default Audio Device The command:~# speaker-test -c 0 -t sine -f 2500seems to add a "sine" signal on the output but the pink noise always remains.The command:~# amixer -c0 sset Headphone 0switch-off the signal outputHow can

Try to conduct the DDR test to my STM32MP135 customized board,  following the instruction in the DDR test util:https://github.com/STMicroelectronics/STM32DDRFW-UTILwhile after successfully download the test binary file, the test code didn't start,  I am using serial only for this test (not usb + uart),  seems the parameter  –-start 0x01 not accepted,  anyone has an idea of what is going on with it?following is the full log:xx@ubuntu:~/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin$ ./STM32_Programmer_CLI -c port=ttyUSB0 -w STM32MP135C-DK_DDR_UTILITIES_A7_signed.stm32 0x01 –-start 0x01-------------------------------------------------------------------STM32CubeProgrammer v2.14.0-------------------------------------------------------------------Serial Port ttyUSB0 is successfully opened.Port configuration: parity = even, baudrate = 115200, data-bit = 8,stop-bit = 1.0, flow-control = offActivating device: OKBoard : --Chip ID: 0x501BootLoader protocol version:

STM32CubeProgrammer v2.14.0 release information New features:• Updated the support for the entire STM32H5 series: – Debug authentication with password or certificate – Authentication key provisioning – Key generation – Firmware encryption and signing – Certificate generation – SFI support, secure manager install, and module install/update• Added support for microcontrollers in the STM32L5 series and STM32WL series: – SFI integrity check• Updated support for the STM32U5 series: – SFI support for the STM32U535/545, STM32U575/585, STM32U595/5A5, and STM32U599/5A9product lines• Added support for the STM32U5Fxxx and STM32U5Gxxx microcontrollers: – SFI support: user interface and command-line interface – SFIx support:   ◦ Via debug: user interface and command-line interface   ◦ Via bootloader: command-line interface onlyRefer to the STM32CubeProgrammer software description user manual (UM2237) for details Fixed issues:1296

Hey,I am designing a board based on the STM32MP157F using the OSD32MP157F SOM as a base. I want to have a usb-c connector acting as a host and/or as hs_otg. Reviewing the DK boards schematics I see that the STUSB1600 is being used. I also see on the dts that STUSB1600 is used in conjuction with I2C4. I was wondering whether I can use an alternative like the TPS25820 or other USB-C source controller and if there are any recommendations on this manner, preferably with a compatible or easily portable kernel module.Any ideas or suggestions are highly appreciated.

STM32CubeIDE 1.13.0 was released today on st.com as well as an in-tool update patch. What is new in 1.13.0? Added the support for new microcontrollers in the STM32U5 series Added the support for new microcontrollers in the STM32WBA series Added the support for two new boards related to the STM32U5 series: STM32U5G9J-DK1 and STM32U5G9J-DK2 Added the support for one new board related to the STM32L4+ series: STEVAL-SMARTAG2 Added the user authentication interface to permit package download Updated to Eclipse® 2023-03 Updated to GCC 11 support by default Added CMake project support Updated debug: Changed values highlighted in yellow in the SFRs view Debug authentication for STM32H5 products Support for programming using multiple external loaders with OpenOCD Updated for microprocessors: Support for the latest release 5.0.0 of OpenSTLinux Addition of the TCP console for semihosting output Main fixed issues 109036 [UC5-REGENERATE][CubeIDE][Examples]Build failed when changing

Could someone point me to some documentation about how to control the oversampling for ADC1 and ADC2 for the STM32MP157C?    Using OpenSTLinux 4.1.0, buildroot.   I looked around but couldn't find anything. Thanks!

Hi,My STM32MP157f-DK2 contains the OpenSTLinux image FlashLayout_sdcard_stm32mp157f-dk2-trusted.tsv. The sdcard is 16GB in size. I am unsure whether this is the right OpenSTLinux image to use when i would like to deploy a React / Electron application on the board. Does anyone have experience with running a React / Electron app on this board? The problem i am facing now is that the total free mem shown is 160MB (free -t -m) while my React package is 477MB in size. Help is appreciated.