STM32 MPUs

I would like to use node-red on STM32MP157C-DK2 to handle datas computed and shared with IPCC by Cortex-M4.Any advice ?Thank you

Hi,I was looking at the ST Yocto dunfell update and wanted to update tf-a firmware and u-boot:https://github.com/STMicroelectronics/meta-st-stm32mp/tree/dunfell/recipes-bsp/trusted-firmware-aUnfortunately I did not realize which of the tf-a versions I should use and ended up flashing the SSP version (using STM32_Programmer_CLI programmer via USB OTG connection)I had a serial terminal connected open on the other port and saw an error about SSP not being supported on this board when it tried to boot, so I wanted to flash back my old version. Unfortunately, I had to realize that its no longer possible...The USB OTG connection which is being used for DFU is dead, I do not see anything in dmesg on my notebook when plugging or unplugging the the ST board or when powering cycling the board. The other USB port which I use for a serial connection is still being detected, but I see no output in the terminal when powering the board on.Basically I lost the ability to reprogram the board via DFU...

Dear All,According to AN5256 "discrete power supply hardware integration" the power source for VDD is turned off in case of crash to "reset" the hardware using the PWR_ONRST signal. At startup. At cold startup and immediately after a crash the power source for VDD has to be enabled. How the PWR_ONRST signal is drived on in this case as the MPU is not power at all ?Thanks in advance for any help

Hi There,I have a question regarding with DDR3L fly-by topology suggested to use by the design guide.My understanding is that STM32MP1 does not support the write/read leveling feature suggested in the JESD standard.If my above understanding is correct, may I ask then why fly-by topology is still recommended as opposite to the T-topology?I thought the main reason DDR3/DDR3L uses fly-by topology is because the write/read leveling feature allows the controller to compensate the skew between CK/DQS caused by the daisy chain connection from fly-by topology.I have also seen other vendor's hardware development manual (i.e. NXP iMX7) that specifically recommend not to use fly-by topology, as their chip does not support write/read leveling feature.Am I missing something here? or perhaps my understanding is incorrect?Appreciate your assistance in advance.Thanks.Regards,Steven

I cannot find compatible displays for this processor.

In the stm32mp157C-DK2 board, there is a DDR3 memory with size 4GB x 1.I wanted to know why the size defined in the system is 512mb as the next figure show :

I'm trying to build linux-5.4.31 for stm32mp1c-ev1 (tag: v5.4-stm32mp-r1). u-boot loads the kernel successfully, but then nothing happens. I've gone in with GDB, and noticed that the kernel is stuck in start_kernel(), and never leaves it.What is the fix for this?#0 cpu_v7_do_idle () at arch/arm/mm/proc-v7.S:78#1 0xc010a1a4 in arch_cpu_idle () at arch/arm/kernel/process.c:71#2 0xc0158064 in cpuidle_idle_call () at kernel/sched/idle.c:154#3 do_idle () at kernel/sched/idle.c:263#4 0xc01583d8 in cpu_startup_entry (state=CPUHP_ONLINE) at kernel/sched/idle.c:355#5 0xc0acb5b8 in rest_init () at init/main.c:451#6 0xc0f00a40 in arch_call_rest_init () at init/main.c:573#7 0xc0f00f10 in start_kernel () at init/main.c:785#8 0x00000000 in ?? ()

Hello,​I always get following error while building openstlinux-5.4-dunfell-mp1-20-06-24:ERROR: st-image-resize-initrd-1.0-r0 do_rootfs: The postinstall intercept hook 'update_desktop_database' failed, details in /mnt/data/dist-pack/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/st-image-resize-initrd/1.0-r0/temp/log.do_rootfs ERROR: Logfile of failure stored in: /mnt/data/dist-pack/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/st-image-resize-initrd/1.0-r0/temp/log.do_rootfs.3210 ERROR: Task (/mnt/data/dist-pack/openstlinux-5.4-dunfell-mp1-20-06-24/layers/meta-st/meta-st-openstlinux/recipes-st/images/st-image-resize-initrd.bb:do_rootfs) failed with exit code '1'Log file has this content:[...] NOTE: Running intercept scripts: NOTE: > Executing update_desktop_database intercept ... NOTE: Exit code 127. Output: /mnt/data/dist-pack/openstlinux-5.4-dunfell-

Hello there,I have been trying to compile the newest release 2.0.0, first with some extra packages and also without them, but at around 90% the compilation process fails with following error:ERROR: Task (/home/paradox/Desktop/workspace/openstlinux-5.4-dunfell-mp1-20-06-24/layers/meta-openembedded/meta-oe/recipes-benchmark/glmark2/glmark2_git.bb:do_configure) failed with exit code '1'I am running the newest Ubuntu 20.04 LTS, which is not under officially supported distributions, however I don't believe that it is the real cause of the problem.EDIT: It seems like it was really the 20.04 Ubuntu being an issue. The package was successfully built on the older 18.04, so my updated question is, will there be support for the newest Ubuntu version 20.04 and if so, approximately when could we expect it to be available?

after click on "stm32wrapper4dbg" link, "Permission error" is appeared (authorization doesn't help)

I'm trying to run STM32MP1 with two CAN FD drivers connected to PD0/1 and PB5/13.I have connected saleae analyzer to all four TX, RX lines and there is no changes during candsend command. I got only " write: No buffer space available" message.How to properly run CAN bus on STM32MP1 ?root@txmp-1530:~# ifconfig -a can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 NOARP MTU:16 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:51 can1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 NOARP MTU:16 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:53 root@txmp-1530:~# ip link set can0 type can bitrate 125000 root@txmp-1530:~# ip link set can0 up root@tx

Hi @martin KJELDSEN​ , I have some questions related to porting touchGFX on STM32MP1 which are as below : 1) Is it possible to run touchGFX on M4 core available on STM32MP1 ? 2) As I understood earlier touchGFX was supported on ARM processors, If I have to port touchGFX on STM32MP1, how should I approach it ?   Regards, Shree

Could you give me some advice on how to debug the kernel through KGDB，

Is there any application note for tamper pins? Which one of the pins is the active tamper?

I am developing an industrial tablet with only one task - to display and record videoIt should be ready to work in a few seconds after turning on (that's why I also think about using STM32H7)I need to show on the display 720p (ideally 1080p) 30 frames per second, as well as encode and decode them in H264 / 265Is STM32MP capable of doing this?If so, could you please give me some material to start exploring embedded Linux?Before that, I wrote only for microcontrollers, to be honest, it's easier for me to work with bare metal and would really like to be able to generate HAL code using CubeMXWhen trying to work with the IMX6, I stopped at the fact that I just can't switch the output from HDMI to LVDS. Not to mention more complicated things like setting up custom DDR and NANDWhere can I find out?I know how this peripheral works at the "iron" level and I think I can write drivers for it. But my problem is that I just can't sort through this huge heap of Linux code, I don't even know where to

Hi i have a ltdc tft display RGB parallel display connected to stm32mp15 series,unable t0 get drm link to DPI connector, the code flow is breaking at following files,using DISTRO              = "openstlinux-weston"i have no idea where to start to debuglinux-4.19.49/drivers/gpu/drm/drm_modes.c       if (mode->flags & ~DRM_MODE_FLAG_ALL)               return MODE_BAD;--- failing here not moving furtherDTS:   panel_rgb: panel-rgb {      compatible = "okaya,rs800480t-7x0gp";   status = "okay";   dvdd-gpios = <&gpioc 13 GPIO_ACTIVE_HIGH>;   avdd-gpios = <&gpiod 7 GPIO_ACTIVE_HIGH>;   cs-gpios = <&gpioa 12 GPIO_ACTIVE_HIGH>;   pinctrl-names = "default", "sleep"

Hello!We have a problem of LCD image quality with our custom STM32MP157C-based board: we see artefacts, wrong colours, ghosts of previous images and rainbows. The LCD is a Winstar WF40CTYAQM, linked with MIPI DSI, much like the Orise Tech LCD of the DK2.What strange is: when on the DK2, the same LCD shows good images. On our custom board, it shows those artefacts and ghosts in particular. The artefacts happen even if we use the Video Pattern Generator in BER mode, grey stripes.There is one difference between the boards: the DK2 has an STM32MP157CAC SoC, while our custom board has a STM32MP157CAD SoC, i.e. the package is different and has less pins.Is there a DSI limitation on the CAD package?Tests were done in 4 steps:Show the ST splash screen, with the butterfly and Tux, during 10 minutes. Blue and green are too dark on the CAD package. "IMG_20200603_095341.jpg" <https://lh3.googleusercontent.com/u/0/d/1q3H5w46XKUTFXd5PLQ0CjDe-h4cuGvsA=w1920-h1006-iv1>Show the SMPTE pattern: art

I try to walk through this example:https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-DK2/Develop_on_Arm%C2%AE_Cortex%C2%AE-M4/Modify,_rebuild_and_reload_a_firmwareMy problems start at Step 6.The "Open Console On MPU Serial Device" button (with the Butterfly symbol) doesn't find a serial connection. As a test I connected via Putty to the device and managed to login successfully. In my case it's COM17 named "Serielles USB-Gerät" in the hardware manager.The debug Configuration Window also does not allow to press "Debug" although I can access and login to the IP which is set there in the connection segment.Did anyone mange to debug the M4 Core tru Linux in a Win 10 environment?RegardsChristian

Our self-made board contains emmc and lpddr3 (1GB, 32bit). The error message when downloading the image is as the attachment. Use Uart to monitor during the download process to get the following information:NOTICE: CPU: STM32MP157AAC Rev.Z NOTICE: Model: Thinta TTU Board INFO: Reset reason (0x15): INFO: Power-on Reset (rst_por) INFO PMIC version = 0x21 INFO: Using USB INFO: Instance 2 INFO: Boot used partition fsbl1 NOTICE: BL2: v2.2-r1.0(debug):v2.2-dirty NOTICE: BL2: Built : 13:36:23, Oct 22 2019 INFO: Using crypto library 'stm32_crypto_lib' INFO: BL2: Doing platform setup INFO: RAM: LPDDR3 8Gb 533MHz v1.45 ERROR: DDR addr bus test: can't access memory @ 0xc0000004I have tried to replace multiple boards. Can you help find the cause of the failure?

If I configure SAI 2 in cubeMX I get a greyed out option that the synchronous slave is not available unless I have one SAI as master, but I have set SAI A as master (or master with master clock out). So what am I doing wrong?It doesn't matter if I configure it for the A7NS or the cortex-m4, the option is greyed out.The pins are available for both the SAI2 A/BIs this a limitation of cubeMX? Or am I missing something?Thanks, Robert

I have a generic parallel LCD screen. 24 bits RGB, vsync, hsync, pclk, data_enable, disp_on,..The examples I see on the wiki only shows the HDMI connection and DSI. How do you configure this for DPI?Is this a good start? (In the device tree)panel_backlight: panel-backlight { compatible = "gpio-backlight"; gpios = <&gpiob 0 GPIO_ACTIVE_HIGH>, <&gpioc 4 GPIO_ACTIVE_HIGH>; default-on; status = "okay"; };   lcd0: display@0 { compatible ="panel-dpi"; label = "lcd"; enable-gpios = <&gpioh 15 GPIO_ACTIVE_HIGH>; backlight = <&panel_backlight>;   port { lcd_in: endpoint { remote-endpoint = <&ltdc_out_rgb>; }; };   panel-timing { clock-frequency = <33000000>; hactive = <800>; vactive = <480>; hfront-porch = <40>; hback-porch = <40>; hsync-len = <24>; vback-porch = <29>; vfront-porch = <13>; vsync-len = <3>;   hsync-active = <0>; vsync-active

For STM32MP1 device we can able to check the M4 device in keil 5 . We are un able to get the cortex A7 device . Can you please suggest the supported IDe for A7. We don't want to use the os We want to use freeRtos.

Hi I'm trying to read the OTP bits on the discovery board STM32MP157C-DK2 using the STM32CubeProgrammer v2.4.0. The GUI version can't read the OTP bits, but I tried with the Command Line Interface and it gave me the following error:C:\Program Files (x86)\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>stm32_programmer_cli.exe --connect port=usb1 -otp displ ------------------------------------------------------------------- STM32CubeProgrammer v2.4.0 -------------------------------------------------------------------       USB speed : High Speed (480MBit/s) Manuf. ID : STMicroelectronics Product ID : DFU in HS Mode @Device ID /0x500, @Revision ID /0x0000 SN : 002A00413338510939303435 FW version : 0x0110 Device ID : 0x0500 Device name : STM32MPxxx Device type : MPU Device CPU : Cortex-A7     UPLOADING OTP STRUCTURE ... Partition : 242 Size : 1024 Bytes   Uploading OTP data: ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒Error:   Error: u

we using  raspberry pi 4 to run Apache python , mysql an c kernal and it runs excellent om 4 Giga ram.we would like to move to stm32p1 , can it being compare and be replaceable ?

I am on windows 10 and would like to use sub-system for linux (WSL) to cross-compile OpenST. So far i made it trough all the steps...until i saw that the cubeprogrammer is using a GUI installer...witch doesnt work on WSL....Are there plans to make that cubeprogrammer available in "non gui" installer?Thanks