STM32 MPUs

I have a STM32MP257F-DK board and am using the OpenSTLinux image. I want to use the USB C connector on the board, but I noticed that the USB3DR internal peripheral page says that the peripheral can be assigned to the given runtime context, but it is not supported in OpenSTLinux BSP.What would be the easiest way to enable and use the USB C connector? I am somewhat familiar with Yocto, but I am not sure what I should change.

Hello,I am trying to get my ADC using DMA working in my freertos program running on the M33 core of the stm32mp257 processor. I set up ADC1 on HPDMA3 using cube MX see config below.I am getting a few issues.1. If I used the generated code I get a runtime crash because the HAL layer was trying to access of null object hacd->DMA_Handle. I got around that issue by adding this line to HAL_ADC_MspInit()    hadc->DMA_Handle = &handle_HPDMA3_Channel11;    Not sure why this was not getting generated by MX. 2. I was getting another crash because of another reference to null variable pQueueLinkList. MX generated this in HAL_ADC_MspInit(). pQueueLinkList was defined but never initialized to anything. I needed to remove this piece of code as well.    if (HAL_DMAEx_List_SetCircularMode(&pQueueLinkList_HPDMACH11) != HAL_OK) { Error_Handler(); }     Once I got past these issues I was able to start

We have built a SBC using the 257EV as a reference in Altium. We are trying to use debug. We have created a ST14 connector to connect to a STLink3 using UART 2 as the debug serial port.Is this possible, and should we use SWD or JTAG to debug the processor.At present we are stuck at a flashing red led1. At present the DDR & GPU supplies haven't started on the PMIC, the remaining supplies are all present, as is the HSE clock.Any thoughts would be appreciated.

Hi there,I am currently working on upgrading our EV charging solution from OpenSTLinux Ecosystem v4 (Linux kernel 5.15) to Ecosystem v6 (Linux kernel 6.6).As part of the process to ensure we are on the right track, I have successfully upgraded to the minor release: OpenSTLinux release v4.1.0 (Linux 5.15-stm32mp-r2.2), and it is functioning as expected. The next step is to proceed with the upgrade to Ecosystem v6 (Linux kernel 6.6).In preparation for this, I regenerated the DTS files using STM32CubeMX_6.13.0 and loaded the existing .ioc file. While regenerating the DTS files using STM32CubeMX_6.1.3 and loading the existing .ioc file, I selected the Migrate option when prompted by the tool. Could you please confirm if this is the correct choice, or would selecting Continue be more appropriate in this case?Current Setup:I am now attempting to recompile the following components with updated versions:TF-A: v2.8-stm32mpOP-TEE: 3.19.0-stm32mpU-Boot: v2023.10-stm32mp Issue Encountere

When trying to attach to M4 upon Linux boot (autoboot=1), it fails to bind resources:Remoteproc driver attempts to probe m4 resources, but all are waiting for pinctrl@50002000 which does not appear before remoteproc probe has timed out. I can see in the logs that pinctrl is itself waiting for other suppliers to initialize.This issue appear only when M4 has been started from U-boot, which makes me thinking that something is not cleared properly when M4 detaches. Would appreciate any hints.

Hi Team We are looking for Processor or Controller which supports EtherCAT G and SPIAwaiting Your Reply ..

I am working with the STM32MP1 and using the STM32MP1 Ecosystem v6.0.0, Developer Package. have successfully enabled and configured the tamper detection feature using OP-TEE and the device tree. The tamper detection works as expected when the device is powered on. However, I am facing difficulties in detecting tamper events while the device is powered off.I want to detect tamper events even when the device is powered off. From my understanding, the TAMP (Tamper) unit and RTC can operate from the VBAT domain, allowing tamper detection in power-off states. However, I have not been able to achieve this functionality. Enabled the TAMP unit and configured the tamper pins in the device tree.stm32mp135f-dk.dts: &tamp {st,tamp-passive-nb-sample = <4>;st,tamp-passive-sample-clk-div = <16384>;st,tamp-passive-precharge = <4>; //wakeup-source;//wakeup-parent = <&exti>; /* Tamper button */tamp-button {tamper-gpios = <&gpioc 3 GPIO_PULL_UP&g

Hi,In Vbat mode (No Vdd), is it possible to pull up the tamper pins and detect tamper in High-Level.We did it in run mode. We enabled the pullups on the tamper pins which are connected to a detect switch. We detect tamper and erase backup registers when the switch released.But in VBat mode. We couldnt succedded.We are runing Passive tamper with precharge enable and trig on. Only PC3,PF10 and PI2 pins are available on the board for tamper inputs. We configure the tamp block both in Optee and TFA with same configuration.Below is our device tree for both Op-tee and TFA configuration. &tamp {    st,tamp-passive-nb-sample = <4>;    st,tamp-passive-sample-clk-div = <16384>;    st,tamp-passive-precharge = <4>;    wakeup-source;    wakeup-parent = <&exti>;    /* Tamper button */    tamp-button {        tamper-gpios = &l

Hello,We are trying to run Tamper block in VBat (Vsw) mode. When we powered off the device, Vbat pin consumes 3 - 5uA from the battery as specified in device user manual.As we understood from the documentation, the source of Vsw domain (either Vbat or VDD) is switched automatically by internal switch harware, so zero power consumtion is expected from battery when VDD is on. In our custom board, when the board is powerd-up, VDD is on, VBat pin's power consumtion from battery increases up to 50-60uA. Any recomendation about hardware or software would be very helpfull.   -The PDRON pin is pulled-up to VDD on the schematics.  - Battery is CR1216 - 3V Lithium Manganese Dioxide- Battery is connected to the Vbat pin directly, no serial diode,resistor, etc...- Battery cahrging feature is not enabled form device tree.    

Hi, I want to use the M4 core to handle all Audio DSP workI can see that MXCube allows the SAI ports to be enabled on the M4 coreBut it appears the I2S ports are not. I am Missing something hereUnfortunately the Pins I need to be  the PZ0-1-2-3 as PCB is doneElse If Its only possible to use the I2S from the Linux A7 then is it even possible to transfer audio data between the cores?Thanks

Hello everybody,i use "meta-st-x-linux-qt"  with "meta-qt6" on STM32MP157https://github.com/STMicroelectronics/meta-st-x-linux-qtwhen I use "QMediaPlayer" to play an audio file it gives me the following error: could not load multimedia backend "ffmpeg" QtMultimedia is not currently supported on this platform or compiler. Aborted (core dumped) if I understand correctly, "ffmpeg" would be missing on my platform, how can I add it to yocto when generating it?Thank you very muchLoupi

I am in the process of starting a board with an STM32MP153CAB processor, unfortunately due to an error in the design, the I2C4 interface is not available( i2c4 is connected to the PMIC by default). I am able connect I2C2 directly to the PMIC, but this interface is not supported in TF-A, other solution is connect I2C6 using wires. The question is how to force using of i2c6 or i2c2 instead of I2C4 by dts config files (Yocto kikrcore).

I am developing a new board and would like to know if the STPMIC25 is recommended over the STPMIC1 as a PMIC for STM32MP157 MPU.Which one should I choose?Thanks. 

According to this article the signing tool is a part of STM32CubeProgrammer. I need a signing tool during my Yocto build to be able to build signed images. The best way to guarantee a reproducibility of the build is to launch it in a dedicated container (to make sure the host system is the same on all developer / CI machines).So the few questions are:I can't automatically download only the signing tool, can I? The download of STM32CubeProgrammer package requires for me to accept the license.It seems that STM32CubeProgrammer installer doesn't have any command line options. I would like to at least have unattended installation, automatically accepting the license and setting installation path in a non-interactive way. CubeProggrammer installation manual doesn't mention any. All that is required, for example, during 'docker build' execution.Is there an open source signing tool alternative?

While reviewing the schematic of the STM32MP157 EVAL development board, I came up with the following questions:I apologize in advance if the translation isn’t perfectly accurate as I used a translator.The Line Out JACK (CN4) outputs via coupling capacitors from SPKOUTLP (A2, B3). Why are the Line Out pins (B5, B4) not used instead?The codec supports differential audio output, but why is the negative pin not connected? (Wouldn’t it prevent distortion if the signal is converted to single-ended using an op-amp before connecting to the audio jack?)Why are the Speaker Out pins used instead of the Line Out pins? (Is it because of the built-in amplifier, or is there another specific reason?)I have some additional questions regarding the microphone circuit. (Sorry if these are silly questions!)If I am using a digital microphone (IMP34DT05TR), can I apply a different power supply (3.3V) to the microphone module instead of the MIC bias voltage from the audio codec (A7, B6), and leave the bias pi

I am trying a simple CM33 ELF test. This one just has the STM32CubeMX boilerplate for the CM33 (non secure). I added a toggle on GPIOJ[6]. I stripped out a ton of the inits leaving just the GPIOJ[6] and pin toggle. after the seq below LED3 *does* toggle.But... the system watchdogs after ~30secs. How to kick off a CM33 program and not have start hang?Is there some way the CM33 can tell the CA35s to keep going and leave the CM33 running?echo -n /home/hedley > /sys/module/firmware_class/parameters/pathecho start >/sys/class/remoteproc/remoteproc0/state   <<<<<<<< this will not return to the prompt... hang./home/hedleylrwxrwxrwx 1 hedley hedley 27 Jan 20 16:50 rproc-m33-fw -> test_mp2_CM33_NonSecure.elf-rwxr-xr-x 1 hedley hedley 3216664 Jan 20 16:51 test_mp2_CM33_NonSecure.elftnxHedley 

Hello, I would like to know if it is possible from a stm32mp135-dk1 card to put a game emulator for example NES games, gameboy,... if so how to do it? Can we start from the image that we can generate on stm32mpu ecosystem (openstlinux under yocto)How can i do it ?

There is a problem about PLL3 while using engineering mode on STM32MP157A-DK1 board. By STM32CubeMX, I configed the clock of M4 core, using PLL3P to get 209MHz, generated code, rebuild it and entered the debug mode. But it shut down and get into an Error. I debuged it bt step, found that it failed in the intial function HAL_StatusTypeDef HAL_RCC_OscConfig(RCC_OscInitTypeDef *RCC_OscInitStruct). When it get to configure PLL3, failed and enter the error. So what I missed? May someone can help me. Thanks! 

Hello, I'm trying to remove the packages which is not required to free up the memory.I tried modifying the layers/meta-st/meta-st-openstlinux/recipes-st/images/st-image-weston.bb file with the below code, But it couldn't help.Here i tried to remove the alsa packag.#To Disable the ALSA PackageIMAGE_INSTALL:remove = "\alsa-conf \alsa-plugins \alsa-state \alsa-state-script \alsa-state-stm32mp1 \alsa-states \alsa-topology-conf \alsa-ucm-conf \alsa-utils \alsa-utils-aconnect \alsa-utils-alsabat \alsa-utils-alsactl \alsa-utils-alsaloop \alsa-utils-alsamixer \alsa-utils-alsatplg \alsa-utils-alsaucm \alsa-utils-amixer \alsa-utils-aplay \alsa-utils-aseqdump \alsa-utils-aseqnet \alsa-utils-iecset \alsa-utils-midi \alsa-utils-scripts \alsa-utils-speakertest \"How can I remove the package. Thanks and Regards,Ezvan.  

1. Does the STM32MP157D-DK1 board have 3.0 USB ports? Does the USB C connector have USB 3.0 capabilities?2. If no to the questions above, what STM32MP board should we use if we want to have USB 3.0 capabilities?

I'm trying to get SecureBoot running on STM32MP157.After opening and reading about 30 pages of your wiki and basically following [1] I was able to create keys and convinced yocto into generating "*_Signed*" files.Sadly I then got confused with publicKeyHash00.bin and publicKeysHashHashes.bin and uploaded the latter one into my OTPs (all instructions always point to publicKeyhash.bin - never the correct file name). My bad.When I now try to upload new signed images onto the emmc, the process outputs: NOTICE: Bootrom authentication failed NOTICE: BL2: v2.8-stm32mp1-r1.0(release):lts-v2.8.6-dirty(ff0bd5f9) NOTICE: BL2: Built : 17:57:15, Apr 21 2023 NOTICE: TRUSTED_BOARD_BOOT support enabled ERROR: BL2: Failed to load image id 1 (-80) Authentication in boot ROM fails as expected. That's okay. But from the last line I think loading of the fip image also fails.Page [2] says "The process ends with error authentication error -80 in case of incorrect provisioning.".Does this mean the b

Where can I find the STM32MP25_CM33.svd file?

When attempting to install the MP1 SDK again on a machine that previously had the SDK installed in a different location I see the error:Argument list too long SDK could not be set up. Relocate script failed. Abort!What is the best method for uninstalling a previous installation of the SDK?My objective was to relocate the SDK.The console output is:./st-image-weston-openstlinux-weston-stm32mp1.rootfs-x86_64-toolchain-5.0.3-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.sh -d /development/stm32mpuv5/Developer-Package/SDKST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 5.0.3-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06==================================================================================================================================You are about to install the SDK to "/development/stm32mpuv5/Developer-Package/SDK". Proceed [Y/n]? YExtracting SDK.......................................................................................................

Hello,I am working with STM32MP135F-DK and Yocto (Kirkstone), using poky, meta-openembedded, meta-st-stm32mp layers. I am creating my custom image for the board. I want to implement OTA to my board and I have chosen swupdate package to achive that. I have also chosen to follow the "dual-copy" stategy. And that's where I had to start dealing with U-boot, it's environment, and environment variables. I am certainly a beginner in Yocto and Embedded Linux. I did some research, I have followed U-boot bootcmd all way down through all ST scripts there, and as far as I can understand:configuration (setting CONFIG_...) of U-boot and environment variables is done in .patch files located in meta-st-stm32mp/recipes-bsp/u-boot/u-boot-stm32mpthere is a boot.scr.cmd in stm32mp-extlinux folder but it should not be used in production, it's there to handle all availiable dev-boards and types of storagewhen my board boots it uses mmc0_extlinux/st32mp135f-dk_extlinux.conf file. The content of this file is:

Hi,Migrating to STs ecosystem v.5.1.0 from v.3 right now and having an issue with M4 where remoteproc is unable to attach to running M4 and consequently fails. From what I can see in the logs there is a timeout while waiting for the resources, in fact only m4_dma2 becomes available (see attached log dyndbg.txt).I am following this guide How to assign an internal peripheral to an execution context - stm32mpu to configure DT files (see attached DT.txt). As you can see all corresponding soc peripherals have been disabled and all m4_ peripherals enabled, but for some reason only dma2 gets probed. What am I missing here?Thanks!