STM32 MPUs Software development tools

Dear Partners,I am trying to add the optee-example component following the instructions in this link.However, when I attempt to run:bitbake optee-exampleI encounter the following error:ERROR: optee-examples-3.19.0+git-r0 do_compile: oe_runmake failedERROR: optee-examples-3.19.0+git-r0 do_compile: ExecutionError('/home/symeon/Files/STM32MP1/Distribution-Package/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/optee-examples/3.19.0+git/temp/run.do_compile.24459', 1, None, None)ERROR: Logfile of failure stored in: /home/symeon/Files/STM32MP1/Distribution-Package/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/optee-examples/3.19.0+git/temp/log.do_compile.24459I have attached the log file for your reference.Do you have any suggestions on how to resolve this issue?Thank you in advance.Best regards,Symeon Zapis 

Hi,I have to use OpenStLinux 3.0 Developer SDK for my project.I am using stm32cubemx 6.3.0 to generate the project files.I then use Stm32cubeide 1.16.1 to import the project.I was able to specify the location of the installed Developer SDK package 3.0.However, when I proceed to install the OpenStLinux 3.0 source codes plugin, the IDE will just crush!!!!Just to confirm, I read on the wiki that Stm32cubeIDE 1.16.1 will import and support Developer SDK package 3.0.Anyone can help?Thanks 

I want to place my signing keys in secure location, like HSM or softhsm. Keys get placed but the given arguments dont work for signing through the secure keys within object store of PKCS11.- If I provide my slot, it givees se3gmentation fault ept@de3:~/build/senec/yocto$ sudo /home/ept/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/STM32MP_SigningTool_CLI --module /usr/lib/softhsm/libsofthsm2.so -ki 1 -si 5407DACB907 -bin build/tmp/deploy/images/stm32mp1-ems-c2-faa1/arm-trusted-firmware/bl2/tf-a-stm32mp157f-ems-c2-faa1-mx-usb.bin -o tf-a-stm32mp157f-ems-c2-faa1-mx-usb_Signed.stm32 -pwd epteck -type fsbl -la 0x2ffc2500 -ep 0x2ffe9000 ------------------------------------------------------------------- STM32MP Signing Tool v2.15.0 ------------------------------------------------------------------- Error: Invalid slot index valueept@de3:~/build/senec/yocto$ ept@de3:~/build/senec/yocto$ sudo /home/ept/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/STM32MP_SigningTool

Hii,I want to add some files in the home/root/ folder and some services which have executable permission  in /etc/systemd/system I have built the distribution package and i want to add these files in the image so when I flash my device it have these files in predefined locations.Is there any way after the image is generated or during the build process?

Hi, I have a Stm32Mp157a-DK1 board. When I try to used it with the latest Stm32CubeIDE, I notice board selector is no longer supporting for this, is there any work around?Thanks

Hi, I'm developing my project on a custom stm32mp135 board, baremetal. I tried to flash my FSBL into eMMC with the external loaders provided with Cube package for STM32MP13XX_CUSTOM_HW, it didn't work. Then I tried one that is provided for STM32MP135C-DK and it did work, but it only flashes SD card. My suspicion is that custom-hardware uses LPDDR3, and my board has DDR3L and that's why it fails. I can't find sources of that external loader to fix it. Are you planning on publishing it?

We are pleased to announce to you that the release 1.17.0 of STM32CubeIDE is available. What is new in 1.17.0: Microcontrollers, microprocessors, and board lists aligned with STM32CubeMX: Added the support for the STM32N6 series Added the support for the STM32U3 series. Added the support for the STM32WL3x line Added the support for the STM32MP23xx microprocessors Added the support for the STM32MP25xx microprocessors in a TFBGA361 16 mm × 16 mm package Added the support for new microcontrollers in the STM32C0 series and related Nucleo boards (NUCLEO-C051C8 and NUCLEO-C092RC) Added the support for new microcontrollers in the STM32G4 series Added the support for new microcontrollers in the STM32WBA series and the related B-WBA5M-WPAN board Simplified user authentication interface Added support for debug authentication with password for the STM32N6 series. Improved support of OpenSTLinux plugin to be version agnostic Enabled the installation of both STM32MP1 and STM32MP2 flavors o

We are pleased to announce to you that the release 6.13.0 of STM32CubeMX is available. What is new in 6.13.0: Added support for the following series, microcontrollers and microprocessors: STM32N6, STM32U3, STM32WL3x, STM32G411xx and STM32C0 Added the support for the following Nucleo boards: NUCLEO-N657X0-Q, NUCLEO-C051C8, NUCLEO-C092RC, NUCLEO-U385RG-Q, NUCLEO-WL33CC1 and NUCLEO-WL33CC2 Added the support for a new Discovery kits and a new expansion boards: STM32N6570-DK and B-WBA5M-WPAN Extended the implementation of the CMake and Makefile build generators taking into account the memory management tool (MMT) features: Single-core microcontrollers without Arm® TrustZone®(a), excluding STM32H7Rx/7Sx, or with disabled TrustZone® Dual-core microcontrollers without TrustZone® (such as in the STM32H7 series) Add the support of the memory management tool on STM32H7 dual-core and STM32WBA5Mxx microcontrollers Added the compare projects feature to make user able to differentiate b

STM32CubeProgrammer v2.18.0 release information New features:  Added the support for the STM32N6 series– OTP programming– External memory programming– Serial boot via USB/UART– FSBL signature with stm32header V2.3 through the signing tool• Added the support for the STM32U3 series– Internal memory programming– Option byte/OTP programming– Core register programming– Regression with password (close/open)– SFI support– Key wrapping– Native services:◦ Key generation◦ Firmware encryption and signing• Added the support for the STM32WL3x product line– Internal memory programming– Option byte/OTP programming– Firmware authentication• Added the support for devices in the STM32C0 series with 64 Kbytes and 256 Kbytes of flash memory– Internal memory programming– Option byte/OTP programming• Updated the support for the STM32H7R3/7S3 and STM32H7R7/7S7 microcontrollers– MCE encryption• Updated the support for the STM32MP13xx, STM32MP15xx, STM32MP23xx, and STM32MP25xxmicroprocessors– PMIC NVM man

 Hi everyone,I'm trying to install PyInstaller on a system and am running into a couple of errors. Here's what I've done so far:1. ApproachBuilt the latest distribution packages.Ran apt update to update the system packages.Installed pip3 via apt as part of the setup. (apt install python3-pip)(I encounter an error related to ldd. To resolve this, I tried installing ldd via apt:)(I have also try to install the build-essential then it was showing that it is unable to locate)When I try to install PyInstaller using the following command:pip3 install pyinstaller"Building wheels for collected packages: pyinstallerBuilding wheel for pyinstaller (pyproject.toml) ... errorerror: subprocess-exited-with-error× Building wheel for pyinstaller (pyproject.toml) did not run successfully.│ exit code: 1╰─> [18 lines of output]running bdist_wheelrunning clean'build/lib' does not exist -- can't clean it'build/bdist.linux-armv7l' does not exist -- can't clean it'build/scripts-3.11' does not exi

Hello,We have produced a board using the STM32MP257FAI3 that we are trying to bring up. I previously had followed the following guide: Getting started - stm32mpu To bring up the STM32MP257F-EV1 development board; I applied the same process to the debug/run configurations for my own board and we are unable to connect to the processor using the STLink-V3 nor program the eMMC over USB. We have checked the ST-Link connections to the processor, and all appears to be correct (i.e., matching the EV1 board). We also texted the voltages going to the processor and those appear as expected.1. Should we expect to be able to connect to the STM32MP2 processor using the ST-Link alone?  We're seeing that "Examination Failed" when the ST-Link is trying to connect to the processor.  We are able to get past this step with the EV1 board, though we've not really been able to do anything useful with the CubeIDE at this point. 2. Since we are unable to connect to the STM32MP2, we are

I am trying to cross compile a simple helloworld.cpp program.   #include <iostream> int main(int argc, char** argv) { std::cout << "Hello World" << std::endl; return 0; }   The makefile is   PROG = helloworld SRCS = helloworld.cpp CLEANFILES = $(PROG) # Add / change option in CFLAGS and LDFLAGS CFLAGS += -Wall $(shell pkg-config --cflags gtk+-3.0) LDFLAGS += $(shell pkg-config --libs gtk+-3.0) all: $(PROG) $(PROG): $(SRCS) $(CC) -o $@ $^ $(CFLAGS) $(LDFLAGS) clean: rm -f $(CLEANFILES) $(patsubst %.c,%.o, $(SRCS))   I have the developer package installed and I am able to compile the gtk_hello_world.c example just fine but If I try the above code it complies just fine but during the link it complains about std::cout and std::endl amoung other things related to iostream.   /home/lharris/STM32CubeIDE/Developer-Package/SDK/sysroots/x86_64-ostl_sdk-linux/usr/libexec/arm-ostl-linux-gnueabi/gcc/arm-ostl-linux-gnueabi/12.3.0/ld: /tmp/ccoeJuW6

please help me on how to integrate Qt with STM32CubeIDE so that clicking a button in a Qt application sends data to the DAC on the STM32MP157D-DK1

Hello, I am currently trying to being up the STM32MP257F-EV1 development board and running into a problem. I am using CubeIDE following the following guide: https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP2_boards/STM32MP257x-EV1/Develop_on_Arm%C2%AE_Cortex%C2%AE-M33/Modify,_rebuild_and_reload_the_firmware.Specifically I am on step 8 when you have to create the run and debug configurations. I followed the guide and created the configurations correctly but now when I run the example application (OpenAMP_ttyecho_CM33_NonSecure) I get the following error: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 access> you can open a Console View for this.. Any help would be greatly appreciated. Thanks! Carson

I am trying to flash custom board which uses an eMMC storage device. The custom board uses STM32MP133F MPU.While flashing I get the error:Message from Embedded Flash Loader : <partition-name> (0x10): not aligned address : 0x988000 on erase size 0x80000Received PhaseID == 0xFF, system is going to reboot What I would like to understand who and why enforces the 0x80000 alignment size for partitions?Can this me configured somehow?On the eMMC manufacturer data sheet I do not see any restrictions for 512 KiB  alignment. Best regards,

This post can be removed as I found out what was wrong...But otherwise when you want to do DDR tuning some experienced quirks:- RTFM twice!- Make sure the target board is in Engineering Boot Mode!!- Notices that latest CubeMX and STM32CubeProgrammer (2.17) does not find the path to the .._CLI even after setting it in CubeMX. Using an older version (2.16) did work.- Besides the wiki, it is necessary to check the community too just to make sure you have the latest info. In the wiki there was mention of the U-Boot SPL to use. Then moment later the community post revealed that it was depreciated. So I got a copy of the DDRFW package from GitHub.- The DDRFW package could generate a problem when building the software. I traced it back to a python script used as post build command. Installing `python-is-python3` solved that problem. I managed to get the firmware running using STM32CubeIDE and debug mode. The use of the binary with CubeMX and CubeProgr (Tools/DDR Test Suite) needs to be t

Hi there ST team!I'm asking this because I'm overwhelmed with all the different process and I'm not sure what's the correct way to do this. I have a qt quick app developed in qt creator for the stm32mp157. I already tested it in my target using the QT creator and it works as expected. Now, I would like to build an embedded Linux image and add this qt application into it. As far as I understand, I need to install the starter package on my target because that will configure some stuff. Then...I'm lost. If someone can explain a high level overview of how to do this it would be really nice. Thanks a lot in advance 

Hello, I am working with the STM32MP257F-EV1 on version 1.16.0 of CubeIDE. Specifically I am following the guide laid out in this link: https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP2_boards/STM32MP257x-EV1/Develop_on_Arm%C2%AE_Cortex%C2%AE-M33/Modify,_rebuild_and_reload_the_firmwareI am trying to run the debug but when I do I get the following output:Open On-Chip Debugger 0.12.0+dev-00597-ga5a21219f (2024-06-03-11:02) [https://github.com/STMicroelectronics/OpenOCD]Licensed under GNU GPL v2For bug reports, readhttp://openocd.org/doc/doxygen/bugs.htmlsrst_only srst_pulls_trst srst_gates_jtag srst_open_drain connect_deassert_srstInfo : Listening on port 6666 for tcl connectionsInfo : Listening on port 4444 for telnet connectionsInfo : STLINK V3J15M7B5S1 (API v3) VID:PID 0483:3753Info : Target voltage: 3.284210Info : Unable to match requested speed 5000 kHz, using 3300 kHzInfo : Unable to match requested speed 5000 kHz, using 3300 kHzInfo : clock speed 3300 kHzInfo : stlin

STM32CubeIDE 1.16.0 was released today on st.com as well as an in-tool update patch. What is new in 1.16.0? Microcontroller and board lists aligned with STM32CubeMX v6.12.0 : STM32C0 ,STM32WB0 and STM32MP25XX Added CMake support for multicontext projects (Multi-Context ,Trust zone , Multi-core) Added new features for CMake project configuration Basic CMake support now also with Ninja Added the OZ in the optimization level to the build settings Main fixed issues: Refer to the STM32 microcontrollers wiki under this link. Known issues fixed and problems and limitations: Refer to the STM32 microcontrollers wiki under this link. Where do I obtain STM32CubeIDE 1.16.0? https://www.st.com/stm32cubeide … Or update your current installation of STM32CubeIDE using: Help > Check for updates

Hello, I am working on getting the Developer Package for the STM32MP257F-EV1 board up and running. I am confused on the step where tells us to do the following command:[ "${ARCH}" = "arm" ] && imgtarget="uImage" || imgtarget="Image.gz"export IMAGE_KERNEL=${imgtarget}Followed bymake ${IMAGE_KERNEL} vmlinux dtbs LOADADDR=0xC2000040 O="${OUTPUT_BUILD_DIR}"I am assuming that for ARCH I should be writing arch64 which is proved by the fact that when I try to run that I am getting an error for the first Image target, But I keep getting the error *** No rule to make target 'uImage' or whatever I put for the Image, I have tried a variety of Image names that I found in some of the files like: Image, uImage, zImage, Image.gz, and bzImage. The only one that will not get this error is bzImage, which will end up getting errors with the files later about undeclared variables and it seems that it is making it for x86 architecture. So what is the Image target I should be using and where do I fi

Hello, I am working with the STM32MP257F-EV1 Development board and I am getting stuck. I am following the following guide: https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP2_boards/STM32MP257x-EV1/Develop_on_Arm%C2%AE_Cortex%C2%AE-A35/Modify,_rebuild_and_reload_the_Linux%C2%AE_kernel. I am doing the step make ${IMAGE_KERNEL} vmlinux dtbs LOADADDR=0xC2000040 O="${OUTPUT_BUILD_DIR}" and when I run make I get the following output:make[1]: Entering directory '/home/carson.kirk@internal.etherform.com/STM32MPU_Workspace/STM32MPU-Ecosystem-v5.1.0/Developer-Package/stm32mp2-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26/sources/aarch64-ostl-linux/linux-stm32mp-6.1.82-stm32mp-r2-r0/build'GEN MakefileHOSTLD scripts/dtc/dtc/home/carson.kirk@internal.etherform.com/STM32MPU_Workspace/STM32MPU-Ecosystem-v5.1.0/Developer-Package/SDK/sysroots/x86_64-ostl_sdk-linux/usr/lib/gcc/x86_64-ostl_sdk-linux/12.3.0/../../../../lib/libc.so: file not recognized: file format not recognizedcollect2: error: l

Using the latest CubeMX 6.9.0 on Ubuntu  23.04  The following has happened quite a few times in the past years , also on  previous Linux and CubeMX versions. Now would like to raise this  issue as it's becoming very annoying now doing more work in CubeMX. There are now more situations where the keyboard just does not respond anymore. The mouse does.1. When creating a new project and entering an partnumber, the dialog box  sometimes get stuck. Mostly after entering a partnumber that does not exists.  You can continue by  selecting from the drop down list and then creating the project,  but when trying to save you are out of luck, you cannot enter a filename so you have to start all over again. a lot of wasted time.2. When entering a pin number in the dialog box. sometimes this text box get stuck. Luckily you can save the project, but need to close CubeMX and restart it gain. A lot of time wasted. This happens no matter it is an MCU or MPU pro

Hello, I am trying to implement a Hi-Speed USB Device on STM32 baremetal project for STM32MP131Axx by using STM32Cube_FW_MP13_V1.1.0. I am using the internal DMA of USB OTG to get faster the bulk transfer. I have 2 questions since I would like to know the suitable FIFO size when using the internal DMA. Q1I found the following comment in HAL_PCDEx_SetTxFiFo() function in stm32mp13xx_hal_pcd_ex.c.When DMA is used 3n * FIFO locations should be reserved for internal DMA registers I am using the endpoint 1 as bulkout that the max packet size is 512 bytes. In this case, is the comment mean that I need to pass 384 words to HAL_PCDEx_SetTxFiFo() as below? HAL_PCDEx_SetTxFiFo(&hpcd, 1, // Use DIEPTXF1 for endpoint 1. 0x180); // 384 words = 1536 bytes  Q2I refered the following post. Is it same for STM32MP13 line that I should not allocate more than (4096 – 72 (for DMA descs)) bytes in total -> 0x3EE words when using DMA?https://com

Hello, I am trying to install the SDK to work on the STM32MPU257F-EV1 Development board and I followed the instructions for the x86_64 Architecture, however when I use the command echo $ARCH it says the architecture is arm64? Is that what should be displaying? I feel like it should be x86_64 right? Thanks! Carson