STM32 MPUs

These are the steps in chronological order to be able to build the files for a custom board. This seems very convoluted and easily confusing. I this process correct  ? The issues normally are not found with the STM board because all the pre-build files are already in the fip  and other source folders, but for a custom board they are not, hence the issues.Build sequence:=================* Install the SDK* SDK source set to the arm toolchain* Extracted all the sources and applied the patches* Copied the device tree files from CubeMX to the respective folders.* Updated the makefiles.sdk with the the new board name.* Added the device tree file name to the makefiles in fdts and dts sub-folders (TF-A / u-boot)* Set the $FIP_DEPLOYDIR_FIP' and $FIP_DEPLOYDIR_ROOT* Deleted all the custom board files under $FIP_DEPLOYDIR_ROOT that were built before during trial (& error)Steps and issues encountered in chronological order:1. Build u-bootmake -f $PWD/../Makefile.sdk all UBOOT_CONFIG

Quite simple, I try to search for  a variable and when I click search even though I KNOW it's in the project. The window disappears and nothing is done. Is this a bug or Is my search wrong? I'm trying to search the entire project.This is quite frustrating. (See Below)  Thank you

Hi,I am new in STM32MP1 MPU Linux and wish to get the guiding to start developing Linux OS app for my board. The first question:I need to switch GPIO pins.  Any suggestions where to start for single core MPU STM32MP135. Thanks.

My question is what the recommended values are for STM32MP151CAA3T (see image for Altium xsignals creation for the routing).I am currently doing routing and I could not find all this information in the datasheet. 

Dear All, I have followed the instruction as per Intro to Embedded Linux Part 2 - Yocto Project.The compilation for layer kirkstone. When i run the command "bitbake core-image-minimal" it give error after 4 hours of work.The error is pasted below./home/mypc/Projects/yocto/build-mp1/tmp/work/stm32mp1-poky-linux-gnueabi/m4projects-stm32mp1/1.6.0-r0/git/Projects/STM32MP157C-EV1/Demonstrations/AI_Character_Recognition/Src/app_x-cube-ai.c:91:3: internal compiler error: Illegal instruction | 91 | if(imax >= 0 && max > 0.5F) | | ^~ | 0x1521b50 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char const*, __va_list_tag (*) [1], diagnostic_t) | ???:0 | 0x15227d6 internal_error(char const*, ...) | ???:0 | 0xb7838f crash_signal(int) | ???:0 | 0x1721239 __gmpn_tdiv_qr | ???:0 | 0x17036ed parsed_string_to_mpfr | ???:0 | 0x1704497 mpfr_strtofr | ???:0 | 0xae57ec real_from_string(real_value*, char const*) | ???:0 | 0xae61cb real_from_string3(real_value*, char c

Hello. I need to integrate a TI SN65DSI83 bridge with a DK2 board and one of the requirements of that bridge is to drive the data lanes to LP-11 state. What is the procedure to make that happen? I am assuming I need to make changes to dw-mipi-dsi / dw-mipi-dsi-stm drivers but that is not obvious to me at the moment. Thanks.

Hello,we have developed a project in STM32CubeIDE which already works.the the project is generated  "Under Root"  like this: Now we want to implement the compilation in a yocto layer instead of use .elf directly.we have take into account the extended recipe of example project (recipes/extended/M4projects) and we have adapted it to compile our project. However the .elf files are not same size as the ones generated in CubeIDE and  doesnt work.is there any solution to implement the compilation of CM4 firmware in yocto ?thank you

Hello ST community,I am designing a board with STM32MP135 CPU and DDR3L based from STM32MP135F-DK.DDR stress test passed successfully and tf-a files are adjusted to have I2C4 on pins used in my design (SCL on PB13 and SDA on PB7).When I flash board there is the following message in console (debug mode enabled):NOTICE: CPU: STM32MP135F Rev.Y NOTICE: Model: STMicroelectronics custom STM32CubeMX board - openstlinux-5.15-y octo-kirkstone-mp1-v22.11.23 ERROR: nvmem node board_id not found INFO: PMIC version = 0x21 INFO: Reset reason (0x35): INFO: Power-on Reset (rst_por) INFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe0000 INFO: FCONF: Reading firmware configuration information for: stm32mp_io INFO: Using USB INFO: Instance 2 INFO: Boot used partition fsbl1 NOTICE: BL2: v2.6-stm32mp1-r2.0(debug):v2.6-dirty(a1f02f4f) NOTICE: BL2: Built : 13:14:26, Nov 23 2021 INFO: BL2: Doing platform setup INFO: RAM: DDR3-DDR3L 16bits 400000kHz ERROR: DDR expected freq 400000 kHz, current

how we can putt our video in the stm32mpu video playback folder  and how we can play this video ?

Hi all,   I work on a STM32MP153 device and I used the command echo mem > /sys/power/state to put CPU A7 in Cstop mode, but I still have MCU running.I am wondering if a message via IPCC from MCU to MPU (that is stopped at WFI) can wakeup the A7 CPU.I tried but it seams not working, so I would like to understand if it is feasible (in the AN5109 low-power application note I don't find IPCC as a wakeup source)Looking forward  Andrea

 STM32MP157AAA  custom board with DRAM, SD- EMMC, USB and UART , Discrete power( no PMIC) . The board uses discrete oscillators for HSE and RTC, so they are set as Crystal OSC for both in CubeMX USB, UART are correctly configured (same as the default peripheral settings). DRAM is correctly setup based on the used DRAM chip. In .config the PMIC options is disabled and legacy power enabledThe CubemX settings were verified by the SOM manufacturer as being correct. This board has run a previous version of the ECO system without problems.TF-A uses SCMI but if the file #include "stm32mp15-scmi-u-boot.dtsi" is included, errors occur.To fix some other CubeMX generated dts file errors:a. Add a file stm32mp157a-<board>.dsti file in the main dts file. (which CubeMX did not add as an include). This fle is empty.b.. Add a binman entry to the stm32mp157a-<board>.dsti. Thee definition was found in stm32mp15-scmi-u-boot.dts and if not included u-boot fails with a message tha

I'm trying to use the TIM internal peripheral as an events counter on an STM32MP15. I have the ETR pin connected to a line generating pulses. When I tried to configure the trigger in STM32CubeMX,I was unable to select the ETR trigger when TIM1 was connected to Linux, only when connected to the M4 core.Is there no linux driver capable of running the TIM internal peripheral in this mode?https://wiki.st.com/stm32mpu/wiki/TIM_device_tree_configuration seems to indicate that `st,stm32-timer-counter` can be used as an external events counter. Do I simply need to manually create the device tree setup? If so, what do I need to do to set it up? 

Many thanks for your help!I have a custom STM32MP157c boards that works OK when the galcore.ko module is not deployed.When the galcore,ko module is deployed, the screen doesn't show up the usual image and after the boot image has been displayed, it stays black.From cat /home/weston/weston.log, it seems that something foes wrong with a signal 15 ([11:24:37.793] caught signal 15:([11:24:17.605] Output 'DPI-1' enabled with head(s) DPI-1   [11:24:17.605] Compositor capabilities:   arbitrary surface rotation: yes   screen capture uses y-flip: no   cursor planes: yes   arbitrary resolutions: no   view mask clipping: yes   explicit sync: no   color operations: no   presentation clock: CLOCK_MONOTONIC, id 1   presentation clock resolution: 0.000000001 s   [11:24:17.606] Loading module '/usr/lib/weston/desktop-shell.so'   [11:24:17.609] launching '/usr/libexec/weston-keyboard'   [11:24:17.612] Warning: support for depreca

Hi ST experts,I'd like to build a bare metal ARM cortex-A7 driver for my MIPI DSI display module. Because there is no HAL driver for LTDC and DSI host then I decided to build it from scratch. I followed the procedures from the STM32MP RM document to configure the parameters and initialize the HW. However, I couldn't read the display ID from DCS read command, checking bit 4 PRDFE (in register DSI_GPSR) is always 1. I tried to configure u-boot to support my display module, compiled the u-boot then I could execute DCS commands without any problem. It took a few weeks to compare my driver implementation line by line with the u-boot driver, even dumping out all the register values. Finally, I noticed there is a different register setting in the u-boot driver:#define WRPCR_REGEN BIT(24) /* REGulator ENable */#define WRPCR_BGREN BIT(28) /* BandGap Reference ENable *//* Enable the regulator */dsi_set(dsi, DSI_WRPCR, WRPCR_REGEN | WRPCR_BGREN);There is no bit 28 in the RM document. Interestingl

I am making a board using STM32mp151a.I want to make Linux OS for this machine.I refered to the web page below.https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machineHowever, Error happened on bitbake process.Please tell me the cause and countermeasures.Error message************************************************** *************| ERROR: Input tree has errors, aborting (use -f to force output)| make[1]: *** [/home/chino/STM32MPU_workspace/yct/build-openstlinuxweston-stm32mp1-led_g_test2/tmp-glibc/work-shared/stm32mp1-led_g_test2/kernel-source/scripts/Makefile.lib:414 : arch/arm/boot/dts/stm32mp157f-led_g_test2-mx.dtb] Error 2| make: *** [/home/chino/STM32MPU_workspace/yct/build-openstlinuxweston-stm32mp1-led_g_test2/tmp-glibc/work-shared/stm32mp1-led_g_test2/kernel-source/Makefile:1471: stm32mp157f-led_g_test2-mx. dtb] Error 2| ERROR: oe_runmake failed| WARNING: exit code 1 from a shell command.ERROR: Task (/home/chino/STM32MPU_workspace/yct/layers/meta-st/meta-st-stm32mp/reci

Hello,I'm trying to configure an externall interrupt (for a digital signal) to be handle from the User Space. I have configured the following node in the device tree on the root node:/ {... exti_gpio_node { compatible = "test,button"; input-gpios = <&gpiod 15 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>; interrupts-extended = <&gpiod 15 IRQ_TYPE_EDGE_FALLING>; interrupt-names = "qwerty"; status = "okay"; }; ...}; I have read this STM documment about interrupts overview, but I'm not clear about how it's supose to be the handling of this interruption from the userSpace. My goal is to make a script that have some "callback()" function to be able to do something with the interrupt signal.I appreciate any information that can make me understand how the workflow should be, or even if you could give me an example about it.Juan P.@Tesla DeLorean @waclawek.jan @TDK @Peter BENSCH @Eleon BORLINI @Imen.D  @Brian TIDAL @PatrickF @Olivier G

Hi all,I am designing a custom board using the STM32MP157CAD. But I haven't been able to get a lock on HSE crystal.Still on tf-a, I removed st,bypass to use the internal oscillator, also used the DTS generated by STM32CubeMX, following my PCB design. But was only able to boot the board using HSI.Enabling TF-A debug messages I was able to see that software was enabling HSE crystal and hanging on HSERDY flag until timeout. I tried to increase the timeout value but not even after 10s software was able to achieve a lock.My crystal specs:Freq: 24MHz;Load capacitance: 20pF;Freq. stability: +-30ppmESR: 40rI have attached schematics and PCB connections with the crystal below (HCLK_IN goes to PH0 and HCLK_OUT to PH1)What could be causing the HSE not to lock?

https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-DK2/Develop_on_Arm%C2%AE_Cortex%C2%AE-A7/Install_the_SDKIt should be more clear the en.xxxx file is under the x86 Yocto package. not the first item development package which are sources. then should use gzip -f to extract the tar from the gz file. then cd the stm32* folder, then cd the sdk  folder and then change the permission.. then the chmod filename is wrong, should be using sudo with filename st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.sh https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-DK2/Develop_on_Arm%C2%AE_Cortex%C2%AE-A7/Modify,_rebuild_and_reload_the_Linux%C2%AE_kernelSays to download the developer package. This should be the BSP package. and also here first gzip to unzip the tar, then tar the .tar file. and the file should be LOWER case SOURCES.In the starter package, the actual tar filena

We are using STM32MP135-DK and we connect to SPI5 an SD Card Adapter.We modified the device tree as follows to use the mmc-spi-slot driver: &spi5{    pinctrl-names = "default", "sleep";    pinctrl-0 = <&spi5_pins_mx>;    pinctrl-1 = <&spi5_sleep_pins_mx>;    status = "okay";    /* USER CODE BEGIN spi5 */     spisdcard@0 {        compatible = "mmc-spi-slot";        reg = <0>;        gpios = <&gpiog 1 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;        voltage-ranges = <3300 3300>;        spi-max-frequency = <2400000>;        status = "okay";        disable-wp;      };  &nb

Hello,according to drivers/gpu/drm/stm/ltdc.c stm hardware supports these pixel formats:enum ltdc_pix_fmt {PF_NONE,/* RGB formats */PF_ARGB8888, /* ARGB [32 bits] */PF_RGBA8888, /* RGBA [32 bits] */PF_RGB888, /* RGB [24 bits] */PF_RGB565, /* RGB [16 bits] */PF_ARGB1555, /* ARGB A:1 bit RGB:15 bits [16 bits] */PF_ARGB4444, /* ARGB A:4 bits R/G/B: 4 bits each [16 bits] *//* Indexed formats */PF_L8, /* Indexed 8 bits [8 bits] */PF_AL44, /* Alpha:4 bits + indexed 4 bits [8 bits] */PF_AL88 /* Alpha:8 bits + indexed 8 bits [16 bits] */};which corresponds to list of pixel format that I get from modetest -M stm | grep format:formats: AR24 XR24 RG24 RG16 AR15 XR15 AR12 XR12 C8 My question is : does STM hardware support RGB666 pixel format ?  If yes, how should I patch stm driver to handle this pixel format ?

To workaround path issue with depmod -a /lib/modules# cp -r 5.15.67 5.15.67-g8d25ddcc4f56# /sbin/depmod -adepmod: ERROR: could not open directory /lib/modules/5.15.67-g8d25ddcc4f56: No such file or directorydepmod: FATAL: could not search modules: No such file or directorythis error is because after compiling some kernel changes, mostly device tree changes, Makefile populates lib/modules/5.15.67 however, how to fix where the modules path is, or what the kernel version is ?# uname -r5.15.67-g8d25ddcc4f56

Dear All, en.flash-stm32mp1-openstlinux-6-1-yocto-mickledore-mp1-v23-06-21.tar.gzan  en.FLASH-stm32mp1-openstlinux-5.15-yocto-kirkstone-mp1-v22.11.23.tar.gz look corrupted. I can't extract them. I need your help. Danke you, Sir. 

Hello all,We have a custom board with STM32MP157FAC1.Kernel version is 5.10.153.I know that Murata 1DX is used on STM32MP157C-DK2 board and that's why we choose it to use in our product.But in our case, module is waiting in loading state.The command for probe the module: modprobe brcmfmac debug=0x1FFFFE  The output: [ 422.736902] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 422.771509] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 422.922159] brcmfmac: brcmfmac_module_init No platform data available. [ 422.927641] brcmfmac: brcmf_ops_sdio_probe Enter [ 422.927671] brcmfmac: brcmf_ops_sdio_probe Class=0 [ 422.927689] brcmfmac: brcmf_ops_sdio_probe sdio vendor ID: 0x02d0 [ 422.927706] brcmfmac: brcmf_ops_sdio_probe sdio device ID: 0xa9a6 [ 422.927722] brcmfmac: brcmf_ops_sdio_probe Function#: 1 [ 422.934208] brcmfmac: brcmf_ops_sdio_probe Enter [ 422.934236] brcmfmac: brcmf_ops_sdio_probe Class=0 [

When generating u-boot an error occurs: stm32mp15-scmi-u-boot.dtsi:135.1-6 Label or path scmi not found. Following the steps in the OpenSTLinux 5.0 workshop document to update the device tree files.  It mentions to include an scmi.dtsi file for u-boot for the specific board. Is there any more information how to do this? This is a custom board with an STM32MP157AAA3 using legacy power. (regulators not PMIC) and this board worked fine with a previous ECO system but in ECO 5.0.0 SCMI was introduced.  

Hi all,I have been trying to boot a custom ST32MP15 board, I get through TF-A and U-boot, but boot fails while Starting Kernel.I had some issues with external 24MHz crystal so I am using HSI to provide CPU clocks. On TF-A and U-Boot device trees I was able to find the nodes to fix that and used STM32CubeMX to help me calculate the PLL multipliers. Although, couldn't find similar nodes for kernel device tree.After U-Boot is loaded I can see that MPU and peripheral clocks have the values I set up (U-boot has some troubles reading values from STPMIC1 but TF-A was able to configure the PMIC)I am able to load zImage and dtb from SD Card and call boot command, but after that the device would hang on "Starting Kernel...". I followed the tutorial at https://wiki.st.com/stm32mpu/wiki/Dmesg_and_Linux_kernel_log# to enable earlyprintk, trying to boot after that gets past the "Starting Kernel..." message, but kernel just prints some garbled lines and reboots the device. I have copied the mess