STM32 MPUs

Hello,I read the STM32MP boot process in this link.And it is a generic Embedded Linux boot process (ROM, SPL, Uboot, Kernel).But, when I read further about STM32MP I figured out that U-boot UEFI commands are enabled, and there is support for PXE network boot which is supported from UEFI environment which is in this case executed from U-boot. Also I found a GPT support on flash memories (eMMC, ..).I'm asking is there a documentation about UEFI on STM32MP ? Like:Is it optional ? (Can it be disabled ?)Is there support for EDK and UEFI application development ?Is UEFI boot process documented ?Thanks,Talel

I am Korean and a developer with less than a year of experience. Please understand the immaturity of inquiring in the official English language. I am using STM32MP157C-EV1 board. The board has the following settings according to the blog link I referenced. The blog link address is : " http://www.emsyslabs.com/how-to-compile-linux-using-yocto-for-stm32mp1/ ". As you can see, the settings are as follows.STM32MP157C-EV1*Linux Image : OpenSTLinux -> st-example-image-qt*DISTRO=openstlinux-eglfs MACHINE=stm32mp1 source layers/meta-st/scripts/envsetup.shAs you see the anothe address link : https://wiki.st.com/stm32mpu/wiki/OpenSTLinux_distribution"Image : st-example-image-qt is ST example of image based on QT framework "That's right. I'm doing some development to test a Qt example on that STM32MP157C-EV1 Board. Luckily, referring to the blog link, I was able to test the qt example for the target board, including the toolchain." http://www.emsyslabs.com/how-to-compile-linux-using-yocto-for-

openstlinux-5.10-dunfell-mp1-21-07-21 I am building st-image-core image in a Ubuntu 20 container on Fedora 34.Any ideas? ERROR: u-boot-stm32mp-2020.10.r1-r0 do_packagedata: Can NOT get PRAUTO, exception No module named '_sysconfigdata'     NOTE: recipe u-boot-stm32mp-2020.10.r1-r0: task do_packagedata: Failed     ERROR: Logfile of failure stored in: /__w/meta-flutter/stm32mp15-dunfell/build-openstlinuxeglfs-stm32mp1-disco/tmp-glibc/work/stm32mp1_disco-ostl-linux-gnueabi/u-boot-stm32mp/2020.10.r1-r0/temp/log.do_packagedata.1303648       ERROR: Task (/__w/meta-flutter/stm32mp15-dunfell/layers/meta-st/meta-st-stm32mp/recipes-bsp/u-boot/u-boot-stm32mp_2020.10.bb:do_packagedata) failed with exit code '1'Searching the line 1 string indicates it may be related to a host contamination issue.I'm trying to get a CI validation job running for my meta-flutter layer.CI job: https://github.com/meta-flutter/meta-flutter/blob/jw/stm32mp15/.github/workflows/stm32mp

..

..

Hi all, I'm using STM32MP1 and stress it so to understand until the display resolution it can support. I'm using a demo board and the demo SW installed.How can I change the display resolution via shell? Thanks

Hi,We are using Stm32mp157a processor and uboot2018.11 version.We have QSPI interface to NOR flash. We want to write,Read and erase the Data in Qspi Memory(i.e,Nor flash).We want to boot the image from Nor flash,How can we do that ?Thanks in Advance.

Hi,We are using stm32mp157a processor and we are working on uboot-v2018.11 at Linux side. I have an idea on board-debug-uart_init().Path for board_debug_uart_init().Path :board/st/stm32mp1/board.cIn board-debug-uart_init() .We have only UART_TX information i.e They configured only UART_TX pin in board_debug_uart_init() function.I need to know where will we configure UART_RX pin. Refer the below link for uboot-v2018.11 source code Analysis.https://elixir.bootlin.com/u-boot/v2018.11/source

Hello, my main seriale console should be USART2 instead of UART4. I modified the kernel dts as follows: chosen { stdout-path = "serial0:115200n8"; };   aliases { ethernet0 = &ethernet0; mmc0 = &sdmmc1; mmc1 = &sdmmc2; serial0 = &usart2; };and it configures correctly the kernel console. If I try the same modification in tf-a and u-boot dts, at boot i see the log starting on uart4, but it blocks at this point Preparing exit to normal world No serial driver foundShould I modify some boot env too?

Hello,we are working on the ST32MP1. The SPI3 works fine with the CubeMX software combining the DMA2 and FIFO when the board works in engineering mode. But if I perform the same software loaded by Linux (rproc start), the DMA2 SPI stream stops working, if I use the function HAL_SPI_Transmit_DMA() instead of using HAL_SPI_TransmitReceive_DMA(). If for example the amount of bytes to be tranferred is larger than 33, the DMA stops with this number of bytes in NDTR DMA register. In engineering mode, this works fine with the same setting. I tested a lot (linker, stack, memory, FIFO on/off...) without any idea, why on M4 only mode, all is working fine. Furthermore, if I take 30 bytes, the first amount of data is transmitted by DMA and then the SPI_ISR is inoved around 15 times to send the rest of the data ... With 40 bytes, the DMA IRQ comes ones but after around 15 bytes and the SPI IRQ is not invoked.Somehow curious but actually, I have no idea what is going wrong using tranmit only in prod

在根�?�ST�??供的tf-a编译阶段，为什么我使用make -f Makefile.sdk TF_A_CONFIG=trusted TFA_DEVICETREE=stm32mp157c-dk2 all这个指令编译的时候会报下�?�这些错误？

..

I have attached an Adafruit LCD (https://www.adafruit.com/product/1770) to my STM32MP157D-DK1 on SPI5 (on the RPi header). I am working with Yocto and the STM32MP1 BSP (but not OpenSTLinux). I am attempting to modify core-image-minimal to enable the SPI5 port and display a console (e.g. framebuffer) to the LCD. Thus far, I have been unsuccessful in getting anything to show up on the LCD (and the SPI lines remain silent when probed with a logic analyzer).I added the following node to the device tree source (.dts):&spi5 { pinctrl-names = "default", "sleep"; pinctrl-0 = <&spi1_pins_a>; pinctrl-1 = <&spi1_sleep_pins_a>; cs-gpios = <&gpiof 6 GPIO_ACTIVE_HIGH>; status = "okay";   display@0{ compatible = "adafruit,yx240qv29", "ilitek,ili9341"; reg = <0>; spi-max-frequency = <32000000>; dc-gpios = <&gpiof 4 GPIO_ACTIVE_HIGH>; reset-gpios = <&gpiof 0 GPIO_ACTIVE_HIGH>; rotation = <270>; /* backlight

On DK2, using devmem2 on linux I read that GPIOH->MODER/ODR (0x50009000/0x50009014) are all zeroes. The same for GPIOA. OTOH some other things can be read out like RTC clock settings. Is there a way to read the GPIO registers?

Hello, I'm designing a board based on STM32MP1 and it's my first time using QUADSPI.I need to boot on a NorFlash (MLO + U-boot), and my Linux filesystem will be on a NandFlash.Those constraint come from the fact that on my previous system (based on a TI MPU), I was using a NorFlash in classic SPI and NandFlash with a parallel bus. I need and I want to keep this "organization".I was wondering if it was possible to put then both on QUADSPI using the reference design shown in AN5031 Figure 40 (page 65) : https://www.st.com/resource/en/application_note/dm00389996-getting-started-with-stm32mp1-series-hardware-development-stmicroelectronics.pdfAre there any recommendations to achieve this? Have you already tried this configuration (NorFlash and NandFlash on QUADSPI) ?If I'm right, as I will be booting from the NorFlash, I need to put in on the bank 1.For information, when kernel will be running (so from NandFlash), access to the NorFlash will be very limited, no to say very rare.Thanks

We are trying to implement a KSZ8041FTL in an embedded design. We are using an STM32MP157 device in a SOC provided by Octavo systems (OSD32MP157C-512M-BAA). We have used design resources provided by Microchip and followed examples provided. We have followed resources provided by STMicro to configure the pin connections and device tree for the PHY. We are not able to connect to the device via MDIO. The device does not respond. The resulting output on the Linux kernel log indicates that MDIO device at address 3 is missing. We have the device strapped to address 1. We see MDC and MDIO activity when the device is being probed but it always reports device missing at address 3. There is no response from the PHY. We have verified the presence of the 50Mhz ref to the PHY and monitored the reset line, configuration pins, and address pins. Nothing appears wrong. What are we missing?  

It seems that I have a problem with DMA, but I'm not sure. Would you please take a look at the below screenDts looksI intend to achieve MII with self-generated quartz.Unfortunately, I'm stuck on this "Failed to reset the DMA".

The ST-Link LEDs are very dimly lit when powered...they are much brighter on my STM32MP157F-DK2 board. I suspect some hardware problem with the MPU board. Also, the CPU LEDs do appear to be running (the Linux Blue LED blinks after a while, and with the SD Card removed the Red LED blinks as in DFU mode). Just not sure why there is no display (no backlight) and no ST-Link function.

..

Hi,I'm using a Wifi/BT module with CYW4343W chip on a custom board with STM32MP157.When booting the system, the driver is loaded correctly and dmesg log shows[ 1.089865] 4000e000.serial: ttySTM1 at MMIO 0x4000e000 (irq = 24, base_baud = 6250000) is a stm32-usart [ 1.105124] stm32-usart 4000e000.serial: interrupt mode used for rx (no dma) [ 1.112211] stm32-usart 4000e000.serial: interrupt mode used for tx (no dma)which indicates, that the BT UART is allocated to ttySTM1. Bluetooth is working correctly as well.Anyway, in the userspace I can't see the ttySTM1 instance under /dev/tty*But driver is loaded and device is shown as serial0-0:board:~# ls -l /sys/bus/serial/devices/serial0-0/ total 0 drwxr-xr-x 3 root root 0 Nov 15 10:46 bluetooth lrwxrwxrwx 1 root root 0 Nov 15 11:00 driver -> ../../../../../../bus/serial/drivers/hci_uart_bcm -r--r--r-- 1 root root 4096 Nov 15 11:00 modalias lrwxrwxrwx 1 root root 0 Nov 15 11:00 of_node -> ../../../../../../firmware/devicetree/base/soc/ser

​为何访问该页�?�没有�?��?去访问

Hi!After starting custom board there are a lot of similar messages in dmesg (10 per second):[ 200.480616] dwc2 49000000.usb-otg: Overcurrent change detected....[ 203.598775] dwc2 49000000.usb-otg: Overcurrent change detectedUSB is not working. LED on USB2514B-AEZC hub blinking several times per sec.What is the reason for this message and how to debug this?USB_OTG circuit have no visible hardware problems.Thank you in advanceLooking forward for your reply

Hi,I am trying to use the lan9303 chip in mdio managed mode on a stm32mp157-based board.I configured the Device tree according to https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next/+/refs/heads/akpm-base/Documentation/devicetree/bindings/net/dsa/lan9303.txtand my .dts file looks like this:#include "stm32mp157.dtsi" #include "stm32mp15xc.dtsi" #include "stm32mp15-qsmp.dtsi"     / { model = "Ka-Ro electronics GmbH QSMP-1570 module on HSW board v1"; compatible = "karo,stm32mp157c-qsmp-1570", "st,stm32mp157"; };   &gpu { status = "okay"; };           &ethernet0 { status = "okay"; pinctrl-0 = <&ethernet0_rmii_pins_a>; pinctrl-1 = <&ethernet0_rmii_pins_sleep_a>; pinctrl-names = "default", "sleep"; phy-mode = "rmii"; max-speed = <1000>;   phy-handle = <&switch>; mdio0 { #address-cells = <1>; #size-cells = <0>; compatible = "snps,dwmac-mdio";    

Hi,We are using the STM32MP157f-ev1 board for our initial development and this is our first time using Linux kernel, we have been following the development package wiki links for building kernel, u-boot and tf-a. We used the STM32CubeIDE's inbuilt cubeMx to generate device trees. For now we have been successful with modifying the kernel device tree to enable couple of USARTs, build it in kernel code base, push it to target, modify the mmc0_extlinux/stm32mp157f-ev1_extlinux.conf in boot partition to load the custom device tree while booting up, test them on the evaluation board and the USARTs are working as expected and we see successful data transfers.However when we modify the clock configuration using the STMCubeIDE/CubeMx we see the changes are being done to the device tree under u-boot and tf-a folders. I have the following questions:If I copy the u-boot and tf-a device trees to their corresponding source code and build them, how to make sure that the device boots up with

As stated in the title, I'm having trouble getting the ST-Link microUSB port connections to enumerate on the PC (Linux). I have two of the dk2 boards, and they have the same behavior. The only way they enumerate on the host is through the DFU mechanism, which is on one of the USB-C ports. For the ST-Link port, dmesg shows nothing when the cable is attached, and lsusb does not list any additional device.Please let me know the settings I must use to get the ST-Link to enumerate.