Ask questions and find answers on STM32 microprocessors and dedicated embedded software solutions, such as Yocto SDK, Qt, and OP-TEE.
Most recent activity
I'm trying to build the standard st-image-weston image following this guide:https://wiki.st.com/stm32mpu/wiki/STM32MP1_Distribution_PackageAfter starting the build with bitbake st-image-westonWhen it reaches around the 68% of the process I get the following error:ERROR: tf-a-stm32mp-2.2.r1-r0 do_compile: oe_runmake failed ERROR: tf-a-stm32mp-2.2.r1-r0 do_compile: Execution of '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/tf-a-stm32mp/2.2.r1-r0/temp/run.do_compile.21431' failed with exit code 1: make: Entering directory '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/stm32mp1/tfa-source' make: *** No targets specified and no makefile found. Stop. make: Leaving directory '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/stm32mp1/tfa-source' WARNING: exit code 1 from a shell command. ERR
Hi all, I am trying to switch to using FIT images and I am looking at the example .its file here:https://github.com/STMicroelectronics/u-boot/blob/0e6522cbd1bfccd7281acdf8ab5ebbd37d29eab1/board/st/stm32mp1/fit_kernel_dtb.itsI am trying to understand why 0xC0008000 is used for the load address/entry point. If I understand correctly:By default, U-boot will load the FIT image to address 0xC2000000Then it will copy the kernel image to load address 0xC0008000, and jump to itThe kernel image needs to decompress itself to final address 0xC0008000; however since the entry point of the zImage is 0xC0008000, it will need to relocate itself first to some address which is higher than (0xC0008000 + uncompressed kernel length)And then finally decompress to final location 0xC0008000Wouldn't it be possible to skip the relocation in step 3 by choosing a different address for the load address/entry point in the FIT image?Thanks,Guillermo
Hi all,The file include/configs/stm32mp1.h in U-boot defines CONFIG_LOADADDR to 0xc2000000. I understand this is the address in RAM where u-boot puts the uImage loaded from persistent storage (SD, NAND, etc).At the same time, according to [2], the kernel uImage is built with LOADADDR set to 0xc2000040. I understand this is the address where the kernel is relocated.Wouldn't this be a problem, as the address of the loaded uImage and the address used for relocation seem to overlap?Also, I think that common convention for ARM is to use <base RAM address> + 0x8000 for relocating the kernel; what is the reason to use 0xc2000040 here? [1]: https://github.com/STMicroelectronics/u-boot/blob/v2020.01-stm32mp/include/configs/stm32mp1.h [2]: https://github.com/STMicroelectronics/meta-st-stm32mp/blob/dunfell/recipes-kernel/linux/linux-stm32mp/README.HOW_TO.txt
..
Hello.I created a custom device tree in CubMH and added its instructions "How to create your own machine" (https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machine)I wanted to run I2C5 in production mode. Running my code stops CM4 and CA9, which then leads to a reboot. At the same time, there are no signals on the pins.Running the example I2C_TwoBoards_ComIT (STM32CubeMP1 / Projects / STM32MP157C-DK2 / Examples / I2C / I2C_TwoBoards_ComIT) CM4 loops at the following code fragment:while (HAL_I2C_GetState (& hi2c5)! = HAL_I2C_STATE_READY) { }In this case, CA9 is working normally.In engineering mode, my code and example code work fine, signals appear on pins.I2c5 setup:m4_i2c5_pins_mx: m4_i2c5_mx-0 { pins { pinmux = <STM32_PINMUX('A', 11, RSVD)>, /* I2C5_SCL */ <STM32_PINMUX('A', 12, RSVD)>; /* I2C5_SDA */ };};&m4_i2c5{ pinctrl-names = "default"; pinctrl-0 = <&m4_i2c5_pins_mx>; status = "okay"; /* USER CODE BEGIN m4_i2c5 */
Hey Team, I'm trying to get through a board bring up with the STM32MP157 silicon ver 2001 marked with a Z. We are trying to boot the system from the on board eMMC (Insignis Technology Corp P/N: NSEC53K008-IT 8GB eMMC ) and are having issues. We have configured the boot pins correctly and also confirmed emmc hardware connections are correct by successfully reading and writing the emmc from linux while booting from the SD card. There seems to be a lack of documentation on how to configure the eMMC and partition it. Is there any specific partition scheme that needs to be followed for the MP1? And link to an app note that documents how to configure the eMMC via STM32Programmer or UBoot for booting would be extremely helpful.Jason
Hi,I am currently using the STM32MP1-DK1 board in engineering modeWhen I am debugging the program and stepping instruction by instruction in IAR, the debugging process is lost at a time during the execution.I can execute the program and and I can insert breakpoint wherever I want. But, before the instruction msr msp, r0 in the function vPortStartFirstTask in the file portasm.s has been executing, if we stop the program execution by inserting a breakpoint, the debugging process is lost with the error:A vector table read fault has occurred. The processor has escalated a configurable-priority exception to HardFault. An MPU or Execute Never (XN) default memory map access violation has occurred on an instruction fetch (CFSR.IACCVIOL, MMFAR). A precise data access error has occurred (CFSR.PRECISERR, BFAR) at data address 0x34020000. Exception occured at PC = 0x1000ced8, LR = 0x10006e9d
I'm trying to get the OpenSTLinux build environment up & running for the 1st time, following the instructions on the wiki step-by-step.So far I have:Built a Ubuntu 18 Virtual machine in Virtualbox - (18.04.5LTS, 4 cores, 8GbRAM, 500Gb HDD)Followed all the Starter package / Distribution package install & setup stepsProgrammed the DK2 and EVB with the Starter Packages (tip: you need Virtualbox Extensions enabling USB2.0 & add STMicroelectronics* as a USB filter)But now I am trying to actually build the whole project using BitBake and it keeps failing.I have not modified the OpenSTLinux at all, I have set it all up using the directory structure suggested in the Wiki, initialised the environment per the instructions, and invoked:bitbake -v st-image-weston 2>&1 | tee build.logAnd the process appears to have failed, which is rather dissappointing, although I can't tell if the error is a "real" error or just something that doesn't really matter.Here's errors from the log:ER
In our custom board we are using I2C1 to control and configure STPMIC1. I'd like to use I2C1 in TF-A so PMIC can be configured to power DDR during boot. I2C1 is not supported by default in TF-A, but looks like there is a way to do it as described in https://wiki.st.com/stm32mpu/wiki/PMIC_hardware_components#TF-A I followed the procedure described in the above link, but still when I include the reference to &i2c1 in my stm32mp153c-<project>.dts it throws the following build error| Building stm32mp1| Error: fdts/stm32mp153c-<project name>.dts:355.1-6 Label or path i2c1 not found| FATAL ERROR: Syntax error parsing input treeAm I missing something?Thanks,Nikhil
I'm trying to boot an STM32MP157 using the v5.4-stm32mp branch of ST's Linux kernel, and it doesn't appear that peripherals under the simple-bus node in the DTS file are getting probed. I copied the stm32mp157d-dk1.dts file as a starting point, but since my board doesn't have a PMIC, I commented out the PMIC element and instead pass a dummy regulator to the SDMMC peripherals. With no other changes, I got absolutely no output from the console. When I enabled earlyprintk support, I got output that stopped at "printk: console [tty0] enabled." I thought, "hmm, that's weird. Why isn't it loading my UART driver?" I edited the boot arguments to pass console=ttySTM0,115200 to the kernel (obviously it should be getting picked up from the device tree file), and this fixed the console printing issue, but I now have the attached log file.As you can see, the device tree is getting loaded, and the memory pools / CPU settings are handled. However, none of the STM32 peripheral drivers are getting load
I am on environment 2.0.0 and a custom board with PMIC and STM32MP151 booting via serial interface with the STM32CubeProgrammer using UART4 for debug output.I managed to get the TF-A running up until it is in BL32 (sp_min) and prints "Preparing exit to normal world". This seems to be the last message before U-Boot is supposed to print something. Which it does not.I tried to enable early debug, but i am not exactly sure where and how to set those options.I added CONFIG_DEBUG_UART_BOARD_INIT=yCONFIG_DEBUG_UART=yCONFIG_DEBUG_UART_STM32=yto the stm32mp15_basic_defconfig, but this has no effect.I did fill all the user sections in the DT as far as i can think of. Using one of the eval boards as a template.I attached both DT for TF-A and U-Boot as well as a UART Trace.Any idea where to start looking?
Hello ST Teams!I'd like to know if it's possible to upgrade Python version and at the same time stay at 1.2 SDK.I've read the "STM32MP1 Ecosystem known bugs and common pitfalls" post and "https://community.st.com/s/question/0D53W00000Ab3toSAB/how-to-upgrade-to-python-36"its seems we cannot do it easily?Any advice?We aim to build a st-image-core with embedded upgraded python version.Have a nice weekend!
Hi, i moved to new ecosystem v2.0 "dunfell" and added my layers of wifi,camera, openCV and python packages from old Yocto ecosystem. first boot serial-getty@ttySTM0 working fine. on second boot it died and in /var/log/messeges i got: Unit serial-getty@ttySTM0.service is bound to inactive unit dev-ttySTM0.device. Stopping, tooI can't understand what i did wrong in Yocto layers that making this bug. did someone had this issue?
I have generated a project with cubemx and tried all the instructions from this article..https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Distribution_PackageMy layer.conf look like thisBBPATH .= ":${LAYERDIR}" BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \ ${LAYERDIR}/recipes-*/*/*.bbappend" BBFILE_COLLECTIONS += "meta-my-demo-layer" BBFILE_PATTERN_meta-my-demo-layer = "^${LAYERDIR}/" BBFILE_PRIORITY_meta-my-demo-layer = "6" EULA_FILE_ST_stm32mpmydemo = "${LAYERDIR}/conf/eula/${MACHINE}" EULA_FILE_ST_MD5SUM_stm32mpmydemo = "8b505090fb679839cefbcc784afe8ce9" LICENSE_PATH += "${LAYERDIR}/files/licenses" STM32MP_MY_DEMO_BASE = "${LAYERDIR}" LAYERVERSION_meta-my-demo-layer = "1" LAYERDEPENDS_meta-my-demo-layer = "stm-st-stm32mp-mx" LAYERVERSION_meta-my-demo-layer = "1" LAYERDEPENDS_meta-my-demo-layer = "core" LAYERSERIES_COMPAT_meta-my-demo-layer = "dunfell"My machine configurations look like this ...#@TYPE: Mac
I see that the page related to the installation on java is still under construction on the wiki, but I urgently want to install jre and want help in doing so.I am using st-example-image-qt for my project and I need to add java to it, I have already added other packages like python, etc. using the IMAGE_INSTALL_append = python3, but when I add openjdk-7-jre in it after adding the meta-java layer, it gives an error that x11 is required in DISTRO_FEATURES.Please help me fix this.Thanks and Regards
I'm trying to generate dtb files (kernet, u-boot, tf-a) for a custom board with STM32MP157C (OSD32MP157C by Octavo Systems) following the instructions from ST (https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package).Here some details:*.dts and *.dtsi files are generated with CubeMXIde 1.4.0Environment is setup in a Ubuntu 20.04 LTS (using WSL).Source files: en.SOURCES-stm32mp1-openstlinux-5-4-dunfell-mp1-20-06-24.tar.xzSDK files: en.SDK-x86_64-stm32mp1-openstlinux-5.4-dunfell-mp1-20-06-24.tar.xzError log: arch/arm/dts/stm32mp157c-test_master_1-mx.dtb: ERROR (duplicate_label): /sram@10050000: Duplicate label 'sram' on /sram@10050000 and /soc/sram@10000000ERROR: Input tree has errors, aborting (use -f to force output)make[2]: *** [scripts/Makefile.lib:308: arch/arm/dts/stm32mp157c-test_master_1-mx.dtb] Error 2make[1]: *** [dts/Makefile:38: arch-dtbs] Error 2make: *** [Makefile:1087: dts/dt.dtb] Error 2Checking inside the files and includes I can see "
Hello.I'm trying to connect MP1's eth to Marvell 88E6352. Switch connected to cpu via RGMII.Because switch don't have output 125MHZ clock, eth configured to use internal clock, how described in this article: https://community.st.com/s/question/0D50X0000B8iBSB/stm32mp157-ethernet-problem After all connections and configurations Linux can see Marvell's switch. But when I try to enable eth, it's not started and write this to console:root@stm32mp1:~# ifconfig eth0 up [ 107.460160] Generic PHY fixed-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:00, irq=POLL) [ 108.476843] stm32-dwmac 5800a000.ethernet: Failed to reset the dma [ 108.481623] stm32-dwmac 5800a000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed [ 108.490893] stm32-dwmac 5800a000.ethernet eth0: stmmac_open: Hw setup failed ifconfig: SIOCSIFFLAGS: Device or resource busyI can't solve this problem by myself.
Hi all,I am trying to understand this commit [1] in u-boot, which removes the fdt_high variable from the environment for stm32mp1 boards.Before this commit, the FDT was initially loaded from persistent storage to address 0xc4000000, and then used in place:## Flattened Device Tree blob at c4000000 Booting using the fdt blob at 0xc4000000 XIP Kernel Image ... OK Using Device Tree in place at c4000000, end c40160d0After this commit, the FDT is loaded from persistent storage to address 0xc4000000, and then relocated to a different position:## Flattened Device Tree blob at c4000000 Booting using the fdt blob at 0xc4000000 XIP Kernel Image Loading Device Tree to cffea000, end cffffc12 ... OKWhy is the extra relocation needed? What problem does it solve?Thank you,Guillermo [1]: https://github.com/STMicroelectronics/u-boot/commit/ec244f6770454e8fd0bb3a33a36339de53e5f59a
I've a custom board with STM32MP153C MPU. I used STM32CubeMX to generate the device tree for kernel, tf-a and uboot. I would like to include these device tree files and create a distribution package. Followed the steps listed in https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machine but during bitbake the build fails as it cannot find stm32mp153.dtsi and other related STM32MP153 files required by the device tree. I made sure the conf for my custom project includes STM32MP153c as the custom reference board, but it still can't find the files for this MPU, and it gets all the files for STM32MP157c MPU in arch/arm/dts. What do I need to do get the files for STM32MP153 and create a distribution package?
I have noticed that in BSP 2.0.0, two different TF-A binaries are built, one installed as fsbl and one used only for communications with STM32CubeProgrammer (the "serialboot" binary). I believe this was not necessary in BSP 1.2.0, where a single TF-A binary was used for both purposes.I am just curious why this split is needed. Isn't it possible to build one single TF-A binary which would work for both purposes? What has changed from BSP 1.2.0 to 2.0.0 that makes it necessary to use separate binaries?Thanks.
I would like to disable bluetooth & USB-OTG from the distribution package. I have removed Usbgadget,usbip, bluetooth,bluez5 from the distribution and also try to remove it from the local.conf file by using PACKAGE_EXCLUDE ="" but somehow its still built in the image. I have tried to search all the packages inlcuded in my image using this command bitbake -g image_name && cat pn-buildlist | grep -ve "native" | sort | uniqand some of the packages which i excluded in the local.conf file is still there. One of the package is "linux-firmware-bluetooth-bcm4343". This package is coming from the machine. can i remove it somehow using local.conf?I have also tried it using bitbake menuconfig..after all the configurations i generatedthe fragment.cfg with.bitbake -c diffconfig virtual/kernelThen i make a .bbappend file in recipes-kernel/linux directory and bitbake my image.Now the problem is that all the configuration which i did is reset to the default everytime for some reason. h
Function : uint32_t SD_UltraHighSpeed(SD_HandleTypeDef *hsd)bug : Array Bounds Writecode : uint32_t SD_hs[16] = {0}; if (__HAL_SD_GET_FLAG(hsd, SDMMC_FLAG_RXFIFOHF)) { for (count = 0U; count < 8U; count++) { SD_hs[(8U*loop)+count] = SDMMC_ReadFIFO(hsd->Instance); } loop += 8U; }
Hi,I'm trying to build yocto environment setup for stm32mp157a Board with link https://github.com/dh-electronics/manifest-av96during build operation i'm facing below python related error:| + printf %b\0 bbfatal_log 'python3 setup.py install --root=/home/kaushendra/Avenger96/build-openstlinuxweston-stm32mp1-av96/tmp-glibc/work/x86_64-linux/python3-setuptools-scm-native/2.1.0-r0/image --prefix=/home/kaushendra/Avenger96/build-openstlinuxweston-stm32mp1-av96/tmp-glibc/work/x86_64-linux/python3-setuptools-scm-native/2.1.0-r0/recipe-sysroot-native/usr --install-lib=/home/kaushendra/Avenger96/build-openstlinuxweston-stm32mp1-av96/tmp-glibc/work/x86_64-linux/python3-setuptools-scm-native/2.1.0-r0/recipe-sysroot-native/usr/lib/python3.5/site-packages --install-data=/home/kaushendra/Avenger96/build-openstlinuxweston-stm32mp1-av96/tmp-glibc/work/x86_64-linux/python3-setuptools-scm-native/2.1.0-r0/recipe-sysroot-native/usr/share' execution failed. | + exit 1 | + bb_exit_handler &n
I'm having trouble with TF-A. I'm trying to build a custom distribution for the STM32MP153AAC, but I can reproduce the issue I'm having by using STM32MP157C-DK2 as a base.The differences between DK2 and my board is that the PMIC is connected to I2C4 on pins B7 and E2 instead of GPIOZ. Another difference is that the serial port is connected to UART7 instead of UART4.So, using devtool, I modified the TF-A DTS file stm32mp157c-dk2.dts to include these changes:/ { model = "STMicroelectronics STM32MP157C-DK2 Discovery Board"; compatible = "st,stm32mp157c-dk2", "st,stm32mp157"; aliases { serial0 = &uart7; }; chosen { stdout-path = "serial0:115200n8"; }; }; &pinctrl { i2c4_pins_a: i2c4-0 { pins { pinmux = <STM32_PINMUX('B', 7, AF6)>, /* I2C4_SDA */ <STM32_PINMUX('E', 2, AF4)>; /* I2C4_SCL */ bias-disable; drive-open-drain; slew-rate = <0>; }; }; uart7_pins_mx: uart7_mx-0 { pins1 { pinmux = <STM32_PINMUX('F', 6, AF7)&
Hi AllI am running the DDR test on stm32mp157c-dk2 board using CubeMX 6.0.1>Tools>TestSuiteTest no 9: Intensive Random test fails and the board resets.I am using the dk2 development board with the stock SD card (SPL), so my guess is that it should pass the test as all necessary DDR tuning has been pre performed by ST.I am not sure where these tests are defined and also what needs doing to make the test pass.Any help is much is appreciated
WATCH ON-DEMAND | STM32 Summit 2026
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.