STM32 MPUs

Hello!I see many having similar issues, but I have have yet to find a solution to the reason my boot is not happening.ATF: v2.2-stm32mp-r2.1U-Boot: 2021.01Linux: v4.19-stm32mp-r3.3Works just fineATF: v2.2-stm32mp-r2.1U-Boot: 2021.01 (Edit: and v2020.01-stm32mp-r2.1)Linux: kernel-stm32mp1-openstlinux-5-4-dunfell-mp1-20-11-12.tar.xzResults in the kernel outputting the following (LL debug enabled with highest level)[   0.398268][   T1] pinctrl core: initialized pinctrl subsystem...[   0.628638][   T1] bus: 'platform': add driver stm32mp157-pinctrl...[   1.831777][   T1] device: 'soc:pin-controller@50002000': device_add[   1.838307][   T1] bus: 'platform': add device soc:pin-controller@50002000[   1.845361][   T1] PM: Adding info for platform:soc:pin-controller@50002000[   1.852543][   T1] bus: 'platform': driver

Hello,I have a custom board based on STM32MP151c with an eMMC on it (no SD card). The eMMC is successfully found in the U-Boot and has the following partitioning:part list mmc 0   Partition Map for MMC device 0 -- Partition Type: EFI   Part Start LBA End LBA Name Attributes Type GUID Partition GUID 1 0x00000400 0x000013ff "ssbl" attrs: 0x0000000000000000 type: 8da63339-0007-60c0-c436-083ac8230908 guid: 81ae02b5-e823-4dfa-909e-f18021275bd7 2 0x00001400 0x000213ff "boot" attrs: 0x0000000000000004 type: 0fc63daf-8483-4772-8e79-3d69d8477de4 type: linux guid: 8691f7b3-c55d-4979-ad45-ab006af4d469 3 0x00021400 0x000293ff "vendorfs" attrs: 0x0000000000000000 type: 0fc63daf-8483-4772-8e79-3d69d8477de4 type: linux guid: c1241248-0452-4a9d-a181-dd26b1b8dc4a 4 0x00029400 0x001a93ff "rootfs" attrs: 0x0000000000000000 type: 0fc63daf-8483-4772-8e79-3d69d8477de4 type: linux guid: e91c4e10-16e6-4c0e-bd0e-77becf4a3582 5 0x001a9400 0x0075fbff "userfs" attrs: 0x0000000000

Hi!So I was reading the wiki here https://wiki.st.com/stm32mpu/wiki/How_to_configure_system_resourcesand they tell you to use PERIPH_LOCK, which is a function that can be found here:https://github.com/STMicroelectronics/STM32CubeMP1/blob/1.3.0/Projects/STM32MP157C-DK2/Templates/Src/lock_resource.cHowever, HAL_HSEM_FastTake does a read lock and not a write lock.When should I be using HAL_HSEM_FastTake() vs HAL_HSEM_Take()? Why does PERIPH_LOCK call HAL_HSEM_FastTake() to get a read lock when it is writing to GPIO/EXTI registers?

I want to know the difference of device tree compiling the with the Developer Package and Distribution Package.​I understand that when I create my own machine, I can create device tree by following 2 method. Method 1) Building device trees with Developer Package (separately from bitbake) This method is described in following Wiki page. https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package Method 2) Building device trees with Distribution Package (included in bitbake) This method is described in following Wiki page. https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machineWhen I checked the operation with the device tree created by above two methods, the behavior was different even though the device tree source before compiling was the same.Specifically​, with device trees build with Developer Package I can use remoteproc to exchange data with Cortex-M4, but with device trees build with Distribution Package I can

I have modified STM32MP157C-DK2 board with NAND flash connected through FMC and it works properly with linux kernel 5.4-stm32mp-r1. I notice that there are some changes to FMC in 5.4-stm32mp-r2 and tried to build my custom linux using the newer release. Unfortunately, the kernel always crashed because it can't open the MTD device. The device can boot TF-A and u-boot properly but it always stuck at the kernel.in 5.4-stm32mp-r1 version I only modify the DK2 device tree by stripping unused nodes, removing nodes that use the same pin as FMC, and adding FMC node by copying the configuration from stm32mp15xx-evx.dtsi. I use the same approach in 5.4-stm32mp-r2 as I assume the configuration from stm32mp15xx-evx.dtsi is enough to make the device boot from NAND.[ 1.158408] UBI error: cannot open mtd UBI, error -2 [ 1.162737] stm32_rtc 5c004000.rtc: setting system clock to 2000-01-16T08:50:47 UTC (948012647) [ 1.173134] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 1.179

I am configured both the FDCAN interfaces on the STM32MP1 discovery board with the settings below using STM32CubeMX. FDCAN1: PA11 (RX) PA12 (TX)FDCAN2: PB12 (RX) PB13 (TX)But I can't seem to get any data from either interface. I have a logic analyzer connected and have verified that there are packets going to the discovery board but candump doesn't show anything and cansend doesn't seem to be sending out any frames.I also use the following command to turn on each interface. ip link set can0 type can bitrate 500000ifconfig can0 upAm I missing something in the settings?Thanks,

Strange issueused power supply 24v, 5AIf we connect debug 3.5 MM cable on debug port, then only unit boots up and taking to kernel command line prompt else it does not boot upI tried taking out LCD display , USB, battery, still above issue thereits a customized board,help me to diagnose

HelloI built a Yocto based image for my stm32 and made sure that the required packages were installed. When I flashed my Image some packages were not found although before building the image I checked the list of packages to be integrated with bitbake -g st-image-weston && cat pn-buildlist | grep -ve "native" | sort | uniqThe .manifest file also contains the right packages to be installed. Why weren't they included in the image after the build? Thank you.

Hi All,i am have a usb drive enabled in stm32mp1, which works only as a pendrive,but when i connect mouse or keyboard , kernel is not detecting the device.but if i do same procedure in ubuntu machine, the usb port detect pendrive and mouse.what i am missing ?

Hi All,i want to use ES8388 audio coec with STM32MP157. All hardware connections are tested, ad i can see MCLK on scope, also codec is visible on I2C bus.But i'm facing dificulties with Device Tree configuration. snippet from my dts file :sound { compatible = "audio-graph-card"; widgets = "Headphone", "Headphone Jack"; routing = "Headphone Jack", "LOUT1", "Headphone Jack", "ROUT1"; dais = <&sai2a_port>; status = "okay"; }; ........ &sai2 { clocks = <&rcc SAI2>, <&rcc PLL3_Q>, <&rcc PLL3_R>; clock-names = "pclk", "x8k", "x11k"; pinctrl-names = "default", "sleep"; pinctrl-0 = <&sai2a_pins_a>, <&sai2b_pins_b>; pinctrl-1 = <&sai2a_sleep_pins_a>, <&sai2b_sleep_pins_b>; status = "okay";   sai2a: audio-controller@4400b004 { #clock-cells = <0>; dma-names = "tx"; clocks = <&rcc SAI2_K>; clock-names = "sai_ck"; status = "okay";   sai2a_port: port { sai2a_en

Hello, ST CommunityI have successfully implemented dB meter code on my STM32L4 Discovery kit and got SPL in dB, But the code has .a file made by ST.I want to implement dBSPL meter in STM32MP1 using PDM sensor. Can it support same .a file on MP1 board? Can I implement dBmeter on MP1?Thanks,Tarun

Hello,I'm trying to add a python GTK application I created to the startup using systemd.In order to do so I created the following gatewayservice.service file:[Unit] Description=Gateway service Requires=graphical.target After=graphical.target   [Service] Type=idle ExecStart=/bin/bash /usr/bin/gateway_service.sh   [Install] WantedBy=multi-user.targetI am able to manually start the service usingsystemctl start gatewayserviceBut when I try to add it to startup and reboot it doesn't launch automatically.I think I'm getting the requirements wrong in the service file but I'm not sure what to put instead.

Hello , New year 2021 Greetings:party_popper: ! Hope you all are doing great !Looking at the FreeRTOS wiki , there is no support for Cortex - A7?Is there an alternate port available for FreeRTOS for Cortex A7? or some customization for the same?what is the recommendation? Thanks and Regards,Have a great Decade !!D

..

HelloIn many instances (TF-A, U-Boot, Kernel, FlashLayout_emmc.tsv ...) it is assumed that there is an SD card called "mmc0" and optionally an eMMC "mmc1". Now we ONLY have an eMMC and NO SD. This means that the eMMC is called "mmc0" and not "mmc1". As a result, U-Boot does not boot the correct kernel, the kernel cannot find the root partition, the wrong mmc1 is in the flash layout_emmc, etc. I "just" have to look how to get the patches into the Yocto build system. I have another place where I overwrite the "boot_instance" with 0 in the source code. I would prefer a corresponding configuration so that the source code does not have to be patched. It is not yet clear to me who sets the "boot_instance". In boot mode 0xb010, this is 1 and is then translated (incorrectly) into mmc1 in "bootcmd". U-Boot recognizes the eMMC as mmc0, which means that the UBoot environment cannot be read because it is expected on mmc1.Does anyone have a solution?

Hello ST Community,I was following below link,https://wiki.st.com/stm32mpu/wiki/How_to_integrate_AWS_IoT_Greengrass_on_top_of_openSTLinux_distribution#cite_note-3I found that I have to buy STPM4RasPI extension board.The board is not available on mouser and digikey.when I followed the given link https://www.st.com/en/evaluation-tools/stpm4raspi.html#overviewIt shows there is no quantity available and I am also confused which to buy for my STM32MP1-DK2 board.Please help me to find one from Thanhks,Nikunj

Hi STI have a question when setting the ADC Clock on the M4 Core side.The STM32MP151C datasheet states that the ADC Clock can be set up to 36Mhz.When the AHB clock is 200Mhz, what clock will it work with if I set "ADC ClockPrescaler" to "ADC_CLOCK_SYNC_PCLK_DIV4"?When calculated, ADC Clock is 50Mhz.However, the maximum operating clock in the datasheet is 36Mhz.Which ADC clock will it work with?I would be grateful if you could tell me the answer.RegardsMachilus

what does MPU_InitStruct.TypeExtField ? mean only three options available #define MPU_TEX_LEVEL0  ((uint8_t)0x00)#define MPU_TEX_LEVEL1  ((uint8_t)0x01)#define MPU_TEX_LEVEL2  ((uint8_t)0x02)does it mean only 3 set of HAL_MPU_ConfigRegion(&MPU_InitStruct); can be called?is any of many macros can be repeated or if HAL_MPU_ConfigRegion can be called more than three times with multiple regions?

We have own MP157 based module and it sometimes hangs after NRST during debug. It doesn't respond to JTAG DAP, further NRST pulses doesn't help but NRST_CORE helps. It seems as errata "Incorrect reset of glitch-free kernel clock switch". We tried sw workaround (QSPI clk src=per_ck) but it doesn't help. Thus we tried hw workaround - connect NRST+NRST_CORE (as we use simple smps chip to power core). But the MP1 is stuck in reset - NRST(_CORE) are at GND. Both VDD (1V8) and VCORE (1V2) are up. Once I disconnect NRST from NRST_CORE (while still powered) it immediatelly boots. I also scoped the signals - after power is turned on, NRST_CORE goes up, followed by NRST after 10ms. When connected together, they sit at 0 all the time. Chip revision is 0x2000. Any idea ? Thanks, Martin

Hi, I am using stm32F767zi controller board with STONE 15" display. We are having trouble receiving data from the LCD panel. When we try to receive registry entry (8 Bytes) the system works fine, but when we try to read the variable register, the received (9 Bytes) are not being received correctly. we are using 2 different integer arrays for receiving 8 bytes and 9 bytes of data. Following is the sample codeuint8_t read_var[7]= {0xA5, 0x5A, 0x04, 0x83, 0x00, 0x00}; uint8_t read_page[6]= {0xA5, 0x5A, 0x03, 0x81, 0x03, 0x02};  uint8_t read_sc_rcv[8];uint8_t buff[9]; // Register transmit & receiveHAL_UART_Transmit(&huart3, read_page, 6, 100);HAL_UART_Receive_IT(&huart3, read_sc_rcv,8);//Variable transmit & receiveHAL_UART_Transmit(&huart3, read_var, 7, 100);HAL_UART_Receive_IT(&huart3, buff,9);Thank You

dts:in M4:I find the SPI1 doesn't work.

Hi All,i am getting watchdog Device or resource busy in stm32mp1root@mp1som:~# dmesg | grep watchdog[   2.108020] iwdg 5a002000.watchdog: unable to set timeout value, using default[   3.642347] iwdg 5a002000.watchdog: timeout skrinked to 1[   3.647585] systemd[1]: Hardware watchdog 'STM32 Independent Watchdog', version 0[   3.654887] systemd[1]: Set hardware watchdog to 30s.root@mp1som:~# echo V > /dev/watchdog-sh: can't create /dev/watchdog: Device or resource busyroot@mp1som:~#

Hi All,In STM32MP1, i have following two problem related RTC 1. Kernel spaceRTC is working fine for me only when i enter following command at every power up , else the default RTC date show local time.hwclock --localtime --hctosys-- makes RTC works.root@mp1som:~# dateMon Sep 7 06:16:00 UTC 2020root@mp1som:~# hwclock --localtime --hctosysroot@mp1som:~# dateMon May 26 11:22:49 UTC 20142 , Uboot side always shows default RTC time. why this ?following is uboot log:U-Boot SPL 2018.11-stm32mp-r3 (Dec 18 2020 - 10:05:24 +0000)Model: STMicroelectronics STM32MP157A-DK1 Discovery BoardRAM: DDR3-DDR3L 32bits 533000KhzTrying to boot from MMC1U-Boot 2018.11-stm32mp-r3 (Dec 18 2020 - 10:05:24 +0000)CPU: STM32MP157CAA Rev.BModel: STMicroelectronics STM32MP157A-DK1 Discovery BoardBoard: stm32mp1 in basic mode (st,stm32mp157a-dk1)

Hello ST community,I was following the link belowhttps://wiki.st.com/stm32mpu/wiki/How_to_integrate_AWS_IoT_Greengrass_on_top_of_openSTLinux_distributionI had completed PC prerequisites by following, https://wiki.st.com/stm32mpu/wiki/PC_prerequisiteswhen I do bitbake st-image-demo-awsIt stops after 49% with error,ERROR: Task (/home/dnk-051/STM32MPU_workspace/STM32MP15-Ecosystem-v2.1.0/Distribution-Package/openstlinux-5.4-dunfell-mp1-20-11-12/layers/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-extended/mozjs/mozjs_60.9.0.bb:do_compile) failed with exit code '1'How can I solve the error?Thanks,Nikunj

I'm updating a .tsv file, used by the CubeProgramer to program a STM32MP DK1. The file I'm looking at contains:#Opt Id Name Type IP Offset Binary - 0x01 fsbl1-boot Binary none 0x0 arm-trusted-firmware/tf-a-stm32mp157a-dk1-serialboot.stm32 - 0x03 ssbl-boot Binary none 0x0 bootloader/u-boot-stm32mp157a-dk1-trusted.stm32 P 0x04 fsbl1 Binary mmc0 0x00004400 arm-trusted-firmware/tf-a-stm32mp157a-dk1-trusted.stm32 P 0x05 fsbl2 Binary mmc0 0x00044400 arm-trusted-firmware/tf-a-stm32mp157a-dk1-trusted.stm32 PD 0x06 ssbl Binary mmc0 0x00084400 bootloader/u-boot-stm32mp157a-dk1-trusted.stm32 P 0x21 boot System mmc0 0x00284400 st-image-bootfs-openstlinux-weston-stm32mp1.ext4 P 0x22 vendorfs FileSystem mmc0 0x04284400 st-image-vendorfs-openstlinux-weston-stm32mp1.ext4 P 0x23 rootfs FileSystem mmc0 0x05284400 st-image-weston-openstlinux-weston-stm32mp1.ext4 P 0x24 userfs FileSystem mmc0 0x33C84400 st-image-userfs-openstlinux-weston-stm32mp1.ext4I'm trying to understand the file's contents and how to