Solved

Hello.I am a college student who is using cortex for the first time.I downloaded stm32cube expansion from stm32 and downloaded format is exe file.I downloaded these exe files and installed them on my computer, but there was a problem from here.I downloaded the programs provided by the stm site, such as stm32cubemx and stm32cubeide.But I don't know how to add and build the folder I downloaded with the exe I mentioned above.It's my first time using the stm program and cortex, so I don't know what to do.I don't think I can share the file because the professor asked me to check it out. To make it simple, there were some pdf and txt files in the folder along with the files Drivers, Middlewares, and Projects. (I've read all the pdf and txt files.)In the projects file, there was a folder called nucleo-h743zi -> Applications -> STL on the board I was using, and inside the STL folder, there were 4 project folders that I needed to check.There are folders called EWARM, Inc, MDK-ARM, Src, SW

Hello There,I'm successfully able to run VL6180 with interrupt functionality. But have some functionality queries.The application is intended to generate interrupt when reading a distance below specific threshold. I found that we need to Clear Interrupt bits every time after interrupt is generated. Actually, I don't want to do that as per the application requirement. With that GPIO1 I would be driving external hardware (mosfet to be more precise) directly without involving MCU.So, how is it possible to make the sensor generating interrupts continuously without clearing interrupt bits?Regards,Keshav Aggarwal

In the Battery Charger circuit in STEVAL-SMARTAG2 version, the bill of materials of the C32 capacitor is not available, can you ask the specific model?

I've been having problems with the CubeMX interface for quite some time now, starting 1-2 years before Windows 11 was released.The problem with the interface can appear both after 10-15 minutes of working in CubeMX and immediately after starting the program.I always use the latest versions of CubeMX.The problem remained after:- updating CubeMX;- reinstalling CubeMX;- updating Java SE JDK 16 to Java SE JDK 20;- Updating Windows 10 to the current Windows 11- Changes to video cards gt250 -> rx450 -> gtx960

I am running LED matrix display from F0 Series MCU. At present whatever I want to display on board, I am putting "Hex code of LED matrix" in the main loop code.  But Now I want to have USB stick containing Hex code of LED matrix. Basically user will upload the Hex code on USB stick from laptop.And controller circuit will have female USB connection, where on inserting the USB stick, "Hex code of LED matrix" will automatically uploaded on  external flash such as AT25SF641B, and MCU reads from that external flash to display on LED matrix display.Please let know any tips to implement this.. I am totally lost. 

I have two of the STM32H747I-DISCO boards. I have used STM32CubeIDE to create a simple project for the boards. I followed AN5361 and am able to debug and see the CM7 and CM4 cores running.I've added code to toggle the board LEDs (port I) but don't see any activity - even with an oscilloscope. The IDE did create the code to enable the GPIO clock (__HAL_RCC_GPIOI_CLK_ENABLE() ).I didn't have any trouble getting blinking LEDs on my STM32F407G-DISC1 boards.The issue seems to be that the four GPIO pins for the LEDs are in a high-impedance state even though Pinout View shows that they're all configured as outputs. The pins are floating at between 1V and 2V (with the scope probe weakly pulling to GND). I can alter the voltage on the pins by connecting a 100k resistor from a pin to either 3.3V or GND, so they're definitely floating.I suspect that there is a clocking issue to GPIO Port I, but I'm new to the STM world and don't know where to start.Can someone please point me in the right directi

I am trying to send data over I2C3 Using STM32F429 Dev Board and Everyting works fine except the HEX Data I want to sendI am Passing this function HAL_I2C_Mem_Write(&hi2c3,0x30<<1,0x09,I2C_MEMADD_SIZE_8BIT,0XFF,1,100); And Getting the Following Output on Logic Analyzer write to 0x30 ack data: 0x09 0x08  Why I am getting 0x08 instead of 0xFF?  

I'm totally new to stm32 and arm development, recently got my stm32-f429(ZIT6) discovery kit . I just following some tutorials, but couldn't properly enable SWO printf() like feature, i followed some ITM register enabling codes and nothing works at all. Please someone provide me some codes , FPU settings and guides which i need to do to trace the printf result from ITM FIFO properly. Im using cube mx latest version( 1.6.0 ) IDE.Thank you.

Hi,I have bought the STM32H747-DISCO kit for testing and I want to test at the max frequency (480MHz). I'm aware of the requirements for the 480MHz, I have followed the user manual:Desoldered and soldered relevant SBs for LDO operation.Updated the code to use the LDO, set the 'VOS 0': if (HAL_PWREx_ConfigSupply(PWR_LDO_SUPPLY) != HAL_OK) { return false; } __HAL_PWR_VOLTAGESCALING_CONFIG(PWR_REGULATOR_VOLTAGE_SCALE0); while (!__HAL_PWR_GET_FLAG(PWR_FLAG_VOSRDY)) { } HAL_RCC_DeInit(); /* Enable HSE Oscillator and activate PLL with HSE as source */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE; RCC_OscInitStruct.HSEState = RCC_HSE_ON; RCC_OscInitStruct.HSIState = RCC_HSI_OFF; RCC_OscInitStruct.CSIState = RCC_CSI_OFF; RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON; RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_HSE; /* PLL1 for System Clock */ RCC_OscInitStruct.PLL.PLLM = 5; RCC_OscInitStruct.PLL.PLLN = 192; RCC_OscInitStruct.PLL.PLLP = 2; RCC_OscInitStruct.PLL.PLLR =

Is there any explanation to how to use production DevEUI, JoinEUI, AppKey and NetwKey, rather than the hardcoded se-identity.h?I have searched all over, application notes, youtube and even studied examples and the actual code, but unable to find out how it is intended to be put together.I tried to populate the LoRaMacNvmData_t passed in OnRestoreContextRequest in lora_app.c, but it is some "BackupContexts" being passed, that seems to be ignored (for this purpose).Am I expected to rely on  FLASH_IF_Read(nvm, LORAWAN_NVM_BASE_ADDRESS, nvm_size);and flash from an external computer, rather than generate it internal to the MCU and report it to external system during test/calibration?

Followed thishttps://wiki.st.com/stm32mpu/wiki/STM32MP1_Developer_Package#Starting_up_the_SDKand thishttps://wiki.st.com/stm32mpu/nsfr_img_auth.php/5/57/U-Boot.README.HOW_TO.txtat:make stm32mp15_trusted_defconfigmake DEVICE_TREE=stm32mp157c-dk2 allbuild goes fine but no .stm32 files in ../build-trustedit shows:-rw-r--r-- 1 user user 932 Sep 28 21:38 Makefiledrwxr-xr-x 4 user user 4096 Sep 28 21:35 scriptslrwxrwxrwx 1 user user 184 Sep 28 21:38 source -> <path>/u-boot-stm32mp-2018.11-r0/build-trustedSame formake stm32mp15_basic_defconfigmake DEVICE_TREE=stm32mp157c-dk2 allnor does this result in any filesmake -f $PWD/../Makefile.sdk allgives an rror:cp: cannot stat <path>/Developer-Package/stm32mp1-openstlinux-4.19-thud-mp1-19-02-20/sources/arm-openstlinux_weston-linux-gnueabi/u-boot-stm32mp-2018.11-r0/build-basic/../build-trusted/u-boot.stm32': No such file or directorycp: cannot stat '<path>/Developer-Package/stm32mp1-openstlinux-4.19-thud-mp1-19-02-20/s

Select a new prject in CibeMX this case STM32Mp157AAA ) Select PZ1 and PZ2 pin. Configure Pz1 output assign PZ2 for EXT IN and assign to Cortex M4Generate MX output fileIssue 1: No GPIO pin initliaziation code is generated !Load project i n AX6 workbench toolAdded manual GPIO and code to main.cIssue 2: When compiling. most errors are related to EXTI (example below) It seems stm32mp1xx_hal.exti.h and .c are not included and compiled into the project. This is probably casued by that CubeMX did not include the GPIO pins How to do add the files to the project to compile ? The "includes" in the project does point to the include folder with the exti files.Also noticed that when adding an I2C port, CubeMX onlu prpvided one set of SCL/SCA pin option (port H) while clicking the pins on the matrix there are many more pins supporting I2C ports. for example ZP5/6 are not shown as a choice but can support I2C.I am able to compile the demo projects from the DK2/MP1 CubeMX package and add GPIO and eX

Today got an update message in SW4 Eclipse to update Did that. Now when trying to start "Debug" on an STM32MP1 board Exclipse just exits. The error is as follows. Debug files atttched.Getting frustrated with the AC6/STM32MP1/Eclipse solution as a development environment ...Will go evaluate other platforms if the STM32MP1 environment and experience does not get stable soon.OpenSTM32/plugins/com.st.stm32ide.mpu.externaltools.openocd.linux64_1.0.0.201902141520/resources/openocd-mpu/bin/openocd -d1 -f skeleton Debug (1).cfg -s /media/user/H3D1P2/Personal/2019/Projects/OpenSTM/Pangu/skeleton -s /media/user/H3D1P2/Tools/OpenSTM32/plugins/com.st.stm32ide.mpu.debug_1.1.0.201904120827/resources/openocd/st_scripts -c gdb_port 3333 -c tcl_port 6666 -c telnet_port 4444 ## A fatal error has been detected by the Java Runtime Environment:## SIGSEGV (0xb) at pc=0x00007f4b99aa973d, pid=19624, tid=0x00007f4bdd45a700## JRE version: Java(TM) SE Runtime Environment (8.0_151-b12) (build 1.8.0_151-b12)#

As in a different post, The TF-A build did not create the FIP binaries after deleting the FIP build folder.This article does not describe how to create a new FIP binary. only how to update. very confusing !The fiptool does provide a create function but its not listed as one the options in this page: very confusing !How to configure TF-AHow to use the "Create" option ?

The Device Tree configuration link . https://wiki.st.com/stm32mpu/wiki/STM32_MPU_device_tree does not include scmi.dstiAfter a rough time lot to wade through trial an errors, we were able to reduce the SCMI errors. First we added #include "stm32mp15-scmi.dtsi" and then stm32mp157a-<board>-scmi.dtsi copied from the ev1-scmi.dts but removed i2C4 because this board if quite the same as EV1 but does not use PMIC/I2C4 .  if this is correct change is our biggest guess but it reduced most of the scmi error less one., as follows:The U-boot build failed with:/soc/usbphyc@5a006000/usb-phy@0: Reference to non-existent node or label "scmi_vdd_usb"However, the workshop for STM32MP15 documentation shows the following to be added/* USER CODE BEGIN usbphyc_port0 */phy-supply = <&scmi_vdd_usb>;/* USER CODE END usbphyc_port0 */After searching the whole ecosystem with grep -Rnw . -e 'scmi_vdd_usb'for this definition, only the following 3 files, besides our file,  in the whole EC

For a custom board configured in CubeMX   usingSTM32MP157AAA3 , UART4, 512MB DDR3L, (4Gx16)  external crystal (HSE, LSE), and discrete power regulator, no PMIC,  device trees were generated with CubeMXwhen compiling optree errors and warnings occur.[1] Wrong CFG_DRAM_SIZE 1024MBytes, in device-tree: 512MBytes.  The TF-A and U-boot .dts files contain the same setting for memory and do not fail.memory@c0000000 {device_type = "memory";reg = <0xc0000000 0x20000000>;When setting memory to 0x40000000 instead of 0x20000000 it passes. Why is this ?[2] Warnings in files (not changed, default provided by ECO system). Audio/I2S is not even configured in CubeMX.core/arch/arm/dts/stm32mp157.dtsi:20.21-35.5: Warning (avoid_unnecessary_addr_size): /soc/dsi@5a000000: unnecessary #address-cells/#size-cells without "ranges", "dma-ranges" or child "reg" propertycore/arch/arm/dts/stm32mp151.dtsi:416.22-428.5: Warning (unique_unit_address): /soc/spi@4000b000: duplicate u

After compiling TF-A, uboot and optee, the flashing of the first mage xxx-usb.stm2 using the CLI tool ends with a wait for completion of the download this fails. The UART report a panic. Any idea how to look further. is this a problems with TF-A device tree or could it be from uboot or optee as the binaries in and output pf those build depend on each other ? Any way to reduce or isolate where it it going wrong to reduce the effort for looking around and trial and errors ? Could it just  be .dtb file TF-A generated  ?This board ran fine with a previous ECO system.CubeProgrammer:File download completeTime elapsed during download operation: 00:00:03.039RUNNING Program ...Address: : 0x1DFU status = 0DFU State = 5bwPollTimeout = 1sending a dfu end of download requestDFU status = 0DFU State = 7bwPollTimeout = 1libusb get status error [-7] : LIBUSB_ERROR_TIMEOUTlibusb get status error [-7] : LIBUSB_ERROR_TIMEOUTlibusb control transfer error [-7] : LIBUSB_ERROR_TIMEOUTReconnecting...

For the MP15 the workshop informs to include, for TF-A  vdd_sd for sdmmc1 in the USER section of sdmmc1.. This particular board uses discrete legacy regulator power. when commenting these the lines,  the build goes trough. Could this causes issues ? Should thes vdd_sd labels be included in the device tree ? if, yes,  how and where ?  There was a patch for vdd i uboot and kernel but not for tf-a where vddd move to scmi:./arm-ostl-linux-gnueabi/linux-stm32mp-6.1.28-stm32mp-r1-r0/0023-v6.1-stm32mp-r1-DEVICETREE.patch:4398:- vdd_sd: vdd-sd {./arm-ostl-linux-gnueabi/linux-stm32mp-6.1.28-stm32mp-r1-r0/0023-v6.1-stm32mp-r1-DEVICETREE.patch:4759:+ scmi_vdd_sd: voltd-vdd-sd {./arm-ostl-linux-gnueabi/u-boot-stm32mp-v2022.10-stm32mp-r1-r0/0004-v2022.10-stm32mp-r1-DEVICETREE.patch:3828:- vdd_sd: vdd-sd {./arm-ostl-linux-gnueabi/u-boot-stm32mp-v2022.10-stm32mp-r1-r0/0004-v2022.10-stm32mp-r1-DEVICETREE.patch:4200:+ scmi_vdd_sd: voltd-vdd-sd {and vdd_sd is only defined in./arm-ost

$ make stm32mp15_trusted_defconfig$ make menuconfig# disable PMIC power and enable legacy power in device drivers => power$ savemake DEVICETREE=stm32mp157a-board-mx cleanmake DEVICETREE=stm32mp157a-board-mx allWhy the code needs pmic when pmic is disabled ?LD u-bootarm-ostl-linux-gnueabi-ld.bfd: drivers/power/power_core.o: in function `pmic_dump':/media/user/H3D2P1/Tools/STM32MP1/STM_ECO_5.0.0/Developer-Package/stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21/sources/arm-ostl-linux-gnueabi/u-boot-stm32mp-v2022.10-stm32mp-r1-r0/u-boot-tm32mp-v2022.10-stm32mp-r1/drivers/power/power_core.c:95: undefined reference to `pmic_reg_read'arm-ostl-linux-gnueabi-ld.bfd: drivers/power/power_core.o: in function `do_pmic':/media/user/H3D2P1/Tools/STM32MP1/STM_ECO_5.0.0/Developer-Package/stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21/sources/arm-ostl-linux-gnueabi/u-boot-stm32mp-v2022.10-stm32mp-r1-r0/u-boot-stm32mp-v2022.10-stm32mp-r1/drivers/power/power_core.c:163: undefined refer

Example for optee:make -f $PWD/../Makefile.sdk all DEVICETREE=stm32mp157a-board-mxAn  error occurs but it stlll generates message with outpfolder and a message that the output files was completed.This happens when the device tree is not found it with errors in the device tree. It still generated the bin files in optee/deploy folder letting the user with the impression that everything went fine.what we would like is to have a makefile just to build for a one board that stops and gives a clear message that something went wrong, with a return value for non zero so that it also can be integrated in a build script.There was one was to easy check on error by adding > <output>to the make command. it then just shows a the error and stop message.make -f $PWD/../Makefile.sdk DEVICETREE=stm32mp157a-board-mx allmake[1]: Entering directory '/media/user/H3D2P1/Tools/STM32MP1/STM_ECO_5.0.0/Developer-Package/stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21/sources/arm-ostl-linux-g

STM32MP157AAA3 with discrete powerERROR (phandle_references): /soc/pwr@50001000: Reference to non-existent node or label "vdd"ERROR (phandle_references): /soc/pwr@50001000: Reference to non-existent node or label "vdd_usb"ERROR (phandle_references): /soc/mmc@58005000: Reference to non-existent node or label "v3v3"ERROR (phandle_references): /soc/usbphyc@5a006000/usb-phy@1: Reference to non-existent node or label "vdd_usb"ERROR (phandle_references): /soc/usbphyc@5a006000/usb-phy@1: Reference to non-existent node or label "scmi_vdd_usb"The first 3 were resolved by adding these definitions as regulators, but scmi error could not be resolved. also added the "stm32mp15-scmi.dtsi  in includes but did not work. Besides , scmi_vdd_sub is only defined in mp135f dsti files and reference the PMIC resources which this board does not have. only way to fix it was changing the reference from scmi to usb_vdd . Is this correct?     

https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/plat/stm32mp1.rstmentions to build u-boot and optee first before TF-A:Building u-boot raises an error:Missing stm32mp157a-board-mx-fw-config-optee.dtb file in folder: $FIP_DEPLOYDIR_FWCONF or '$FIP_DEPLOYDIR_ROOT/arm-trusted-firmware/fwconfig'When building TF-A it fails but it does generated this dtb. After copying the dtb to the FIP_artifact folder, and then running u-boot again , the TF-A builds as well.Is this how it's supposed to be ? 

No matter what is in the following line of the Makefile.sdk (even it is empty)UBOOT_DEVICETREE_stm32mp15_defconfig ?= stm32mp157c-ed1 stm32mp157f-ed1 stm32mp157a-ev1 stm32mp157c-ev1 stm32mp157d-ev1 stm32mp157f-ev1 stm32mp157a-dk1 stm32mp157d-dk1 stm32mp157c-dk2 stm32mp157f-dk2  <custom board>make -f $PWD/../Makefile.sdk allOnly create optee files for the st boards as can be seen form the output from the build:fiptool-stm32mp config:optee:bl32 config value: opteedevicetree config: stm32mp157c-ed1 stm32mp157f-ed1 stm32mp157a-ev1 stm32mp157c-ev1 stm32mp157d-ev1 stm32mp157f-ev1 stm32mp135f-dk stm32mp157a-dk1 stm32mp157d-dk1 stm32mp157c-dk2 stm32mp157f-dk2Make clean does not have affect.while.....make -f $PWD/../Makefile.sdk UBOOT_CONFIG=trusted UBOOT_DEFCONFIG=stm32mp15_defconfig UBOOT_BINARY=u-boot.dtb DEVICETREE=stm32mp157a-<custon board> alldoes output the optee file.[fiptool] Create fip-stm32mp157a-<custom board>-optee.bin fip binary into 'FIP_DEPLOYDIR_FIP' fold

Please comments whether STM32cube IDE software is free or licensed? We will use it for checksum verification, programming or re-programming.Thanks You.

Hello, all.I am using STM32CubeIDE with an STM32G030 micro. I attempted to implement a simple interrupt - based timeout timer on Timer17 using the HAL driver. See attached file “Screenshot1”for the TIM7configuration info. Here’s the Init Code generated from the setup in the .ioc file:/* USER CODE END TIM17_Init 1 */htim17.Instance = TIM17;htim17.Init.Prescaler = 64 - 1;htim17.Init.CounterMode = TIM_COUNTERMODE_UP;htim17.Init.Period = 10000 - 1;htim17.Init.ClockDivision = TIM_CLOCKDIVISION_DIV1;htim17.Init.RepetitionCounter = 0;htim17.Init.AutoReloadPreload = TIM_AUTORELOAD_PRELOAD_DISABLE;if (HAL_TIM_Base_Init(&htim17) != HAL_OK){Error_Handler();}My micro is running a 64 MHz clock, so the prescaler setting has it running at 1 MHz (counting microseconds). I ran the htim17.Init.Period in the .ioc out to 65536 - 1 to handle a 50 millisecond interval and tested to see if it was running correctly with this simple, no - interrupt code from Sean Hymel’s Digi-Key instruction