STM32 MPUs Products and hardware related

..

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.

Hi,We are using stm32mp157a processorin Ubootv2018.11-stm32mp1-r2.1 version. In this DDR has 512MB of memory. We want to change DDR size 512MB to 1 GB ,how can we do that? and what are the files we need to modify for changing ddr size in uboot? Please help us.

I have been told that the STM32MP1 fit that criteria. ie if the board is deployed to the field, then it is not easy to reverse engineer the SD card, ripping code and configuration details.Is this indeed true?What is the equivalent model to the Pi in the STM32mp1 family of products?Please don't shoot me down, if this sounds a bit naïve, just learning...Any STM32 experts out there that can advice?

is there any way find dts config /sys/ file to check stm32mp1  in linux sdk ?cpu temp freq battery voltage vbat measurement.

We are using stm32mp157a_dk1. we want to know cortex_A7 core0 is in secure or non secure mode? How will come to know processor mode is in secure/non secure? If it is secure how to change it to non secure?

Hi,I tried to let "en.FLASH-stm32mp1-openstlinux-5.10-dunfell-mp1-21-03-31.tar_v3.0.0" work on the ODYSSEY STM32MP157C board.Please advise when will produce error : "Starting version 244.5+[  5.236977] blk_update_request: I/O error, dev mmcblk1, sector 173056 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0[  5.246675] Buffer I/O error on dev mmcblk1p4, logical block 0, lost sync page write[  5.254488] EXT4-fs (mmcblk1p4): I/O error while writing superblock[  5.260725] EXT4-fs (mmcblk1p4): mount failed[  5.269862] VFS: could not find a valid V7 on mmcblk1p4." and how to solve it.The attachment is the output log.Thanks,QiZhang

I am wondering what number I should expect in terms of encryption performance with STM32MP157C. Below is that I getOpenSSL 1.1.1l 24 Aug 2021 # openssl engine -c (devcrypto) /dev/crypto engine [DES-CBC, DES-EDE3-CBC, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-CTR, AES-192-CTR, AES-256-CTR, AES-128-ECB, AES-192-ECB, AES-256-ECB, MD5, SHA1, SHA224, SHA256, SHA384, SHA512] (dynamic) Dynamic engine loading support   ## without devcrypto openssl speed -evp aes-128-cbc -engine devcrypto -elapsed The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-128-cbc 7533.57k 9109.38k 9611.86k 9747.11k 9786.71k 9781.25k   ## with devcrypto openssl speed -evp aes-128-cbc -elapsed type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-128-cbc 1898.27k 5383.32k 9960.87k 12648.11k 13443.07k 13538.65kAre these numbers to be expected?

Hi ST Community,We are using STM32MP157C-DK2 board and OpenSTlinux Firmware (v3.1-Openstlinux-5-4-dunfell-mp1-20-11-12) for our development. We have a requirement to drive the Blue LED (LD8) always ON even during sleep / suspend. Currently the GPIO PD11 connected to the LED becomes LOW when we issue "systemctl suspend" command in Linux.Below is the DTS snippet:     led {        compatible = "gpio-leds";        led-blue {            label = "heartbeat";            gpios = <&gpiod 11 GPIO_ACTIVE_HIGH>;            linux,default-trigger = "heartbeat";            default-state = "off";      &n

On the STM32MP1, when booting from serial NOR flash, the STM32 MPU Wiki states "In dual mode, BK1_NCS shall be connected to BK2_NCS on board." Should MPU BK1_NCS and BK2_NCS GPIOs actually be connected, or rather is BK2_NCS GPIO unused? I'm just confused since other kits (ex: STM32H750B-DK) have provisions for jumping the 2 lines together, but the wiki does not indicate the BK2_NCS GPIO (from the MPU) is even used by the BootROM. I wanted clarification of the statement made on the wiki article, mainly to be sure that shorting the BK1_NCS and BK2_NCS lines weren't required to put the QuadSPI in dual-bank mode. The statement on the wiki might be misleading.

Hi, i'm using Yocto to build a custom openstlinux image for a stm32mp157d-dk1, but i would like to upload the image using the mass storage mode, enabled with u-boot, or something like that.

My device tree is the following:&sdmmc1 { pinctrl-names = "default", "opendrain", "sleep"; pinctrl-0 = <&sdmmc1_b4_pins_a>; pinctrl-1 = <&sdmmc1_b4_od_pins_a>; pinctrl-2 = <&sdmmc1_b4_sleep_pins_a>; cd-gpios = <&gpiog 1 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>; disable-wp; cd-debounce-delay-ms = <500>; no-1-8-v; max-frequency = <1000000>; //st,sig-dir; //st,neg-edge; //st,use-ckin; bus-width = <4>; vmmc-supply = <&vdd_sd>; //vqmmc-supply = <&sd_switch>; sd-uhs-sdr12; sd-uhs-sdr25; sd-uhs-sdr50; sd-uhs-ddr50; status = "okay"; };Sd schematics is the following:

Good afternoon, I wrote a program for controlling the railway scoreboard in Python 3 for the STM32MP157A-DK1 board. I have a problem. It is described by the link https://bugs.launchpad.net/ubuntu /+source/gnome-control-center/+bug/1264368Troubleshooting:Warning: Source ID *** was not found when attempting to remove it.I have a question which boards from the STM32MP157 family do not have this problem?Sincerely, Alexander.