Solved

Hey, I am currently trying to get my own hardware to run on STM32 Microcontrollers. In this case, I am using a F103RET6, LQFP64 package. It is being used with very improvised hardware, as a proof of concept only. The layout looks like so, made in Kicad. Please be kind, it's my first rodeo. I am aware of the lacking of decoupling, filtering etc - as said, it's a prototype, I wanted to keep it as simple as possible.I am giving the circuit 9V on the left two solder pads, that are then fed into a 3.3V regulator (500mA max). It works fine up to here.Now there are two goals: I want to have the LED (above the 220Ohms Resistor) blink so I know flashing software (a two line program that toggles PA9) worked, and ultimately test the second circuit, which is a MOSFET driving a load. At this moment, there i no such said load soldered in yet. The planned-for oscillator is currently not in use, I want to try it first with the internal resonator as to not overcomplicate things. For a better view of pi

Hey, I have the ST25DV64KC-DISCO discovery kit, and I want to program it such that whenever an NFC-enabled mobile phone comes in contact, the phone will connect to a Bluetooth address that will be given inside the firmware code. So can somebody please help me with things like which software to download, how I will be able to open the firmware file of the ST25DV64KC-DISCO, name STSW-ST25DV002, and what portion of the code we need to change? Can someone please give me step-by-step instructions?

Hi everyone,I am struggling to understand why the provided example seem not to behave as expected:upon startup, when the gap is detected, the generated Reference_position (TDC) turns out to be localized 1 tooth AFTER the calculated one (angular ticks math), even if the values written to the TBU_CHANNEL1 register are correct. It looks like the match-value is only loaded into the CCU register of the ATOM channel only 1 active edge AFTER (This could be overcome with a one-time only -cold boot- compensation btw).but it's not over: after a lock-loss scenario (take 1 tooth off the crankwheel, e.g.) the resynchronization procedure is carrried out following the same steps as on startup but this time (oddly enough) the Reference_position (TDC) ends up 3 teeth (angular position) BEFORE where it is expected. There must be something with the CPU loading the CCU register values for next matching... Is there anybody running into similar issues on this specific platform? How did you get over (if

The MCWB 6.1.2 doesn't allow the configuration of of both hall sensor and quadrature encoder as speed/position sensors in main/auxiliary speed sensor configurations. It looks like the only conflict is in timer input pin allocation, but it seems like an artificial limitation that is somehow dictated by the project generator's contraints. The current project I refer to is using the NUCLEO-G431RB, but I tried this on many board/CPU platforms, including those that had more timers and many more pins.What is the limitation here? Why aren't the timer peripheral usages more configurable? Is this constraint somehow encoded into template files that would be reasonable to edit?

I am using TouchGFX 4.20.0 library. We are storing all the Fonts and images to the external memory. During the initialization as per the selected language we are caching the respected Fonts and successfully load the fonts and able to see correct text. We also cache all the images upfront. But while our display module is receiving large number of CAN messages on the CAN task sometimes we observed the few texts on the screen becomes garbled. The issue comes only for text we did not see any issue while drawing the images. As we cache both the fonts and images upfront during the initialization though we are seeing the issue with text(fonts).

I have seen the Digital PFC section in MCSDK 6.1.2 but i do not get an option in the project i have selected for the B-G431B-ESC1 project. How can i enable it? How important is this Digital PFC? In my testing i get around 0.6. 

I am struggling to find a good way to identify the two COM ports the STLink-V3PWR provides. One is for direct communication with the power measurement unit and the other is connected to DEBUG for the target device(VCP).We need a easy way to identify the DEBUG UART port of the STLink-V3PWR. When performing the "-l uart" command with the STM32_Programmer_CLI.exe we receive two identical outputs for both ports. This is not the case with the STLINK-V3SET, because we get an easy identifyable description "STMicroelectronics STLink Virtual COM Port". In the example below, how do I distinguish between COM20 and COM21? There must be a better way than opening both ports and checking which one responds to the "version" command.Example Outputs:STLINK-V3SET"C:\\Program Files\\STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin\\STM32_Programmer_CLI.exe" -l uart-------------------------------------------------------------------STM32CubeProgrammer v2.14.0-------------------------------------

Hi all,I have two STEVAL-MKI220V1 sharing the I2C1.Days ago, I had one kit working with Nucleo-767, so now I added another STEVAL-MKI220V1.After wiring up the kit2, I cloned all the code snippets of kit1 and rename it for kit2 with a number '2' as the suffix of all the variables.Then I added the write config lines as follows: (also changed that the Psense1_ADD = 0x5C (Gnd), Psense2_ADD = 0x5D (VCC))ret_hal = HAL_I2C_Mem_Write_IT(&hi2c1 ,Psense1_ADD,Psense1_REG_CRG1,I2C_MEMADD_SIZE_8BIT,Psense1_CReg1W,1); // 1Hz reading of Pressureret_hal = HAL_I2C_Mem_Write_IT(&hi2c1 ,Psense2_ADD,Psense2_REG_CRG1,I2C_MEMADD_SIZE_8BIT,Psense2_CReg1W,1);With these 2 lines, the kit2 doesn't work. The text box of my HMI shows blank.If I commented either one of it, as follows: (emphasize, "commented either one line")ret_hal = HAL_I2C_Mem_Write_IT(&hi2c1 ,Psense1_ADD,Psense1_REG_CRG1,I2C_MEMADD_SIZE_8BIT,Psense1_CReg1W,1); // 1Hz reading of Pressure//ret_hal = HAL_I2C_Mem_Write_IT(&hi2c1 ,Pse

Hi,I have a STM32G491 based design with three differential shunts, routed to the three Op Amps of the MCU. I would prefer to run the Op Amps in standalone mode. This would allow me to have a low pass filter (cap across negative and output) and I would also be able to fine tune the opamp gain. I understand that this is not possible with 2 ADCs due to limitations in amplified signal routing, but it would be possible with 3 ADCs.It looks like the MCSDK 6.1.1 ships with a promising r3_3_g4xx_pwm_curr_fdbk.c file. How to configure this current measurement topology with the MCSDK 6.x? I have a JSON spec file for my custom inverter board. I am able to generate code for 3 Op Amps + 2 ADCs by using the "ThreeShunt_RawCurrents_Differential_InternalGain" option and STM32G474 as a temporary MCU before importing everything into a STM32G491 project.Additionally, do you have a specification for (differential) PGA shunt measurement network polarization offset and attenuation calculation, or do I have

Hi @ all,what is the difference between VN330SP and VN330SP-E or what does the suffix -E stand for?I have compared both datasheets and found no differences. Thanks a lot for your replies!Phil

Custom STM32MP157AAA3 board with 512MB DDR.[Note: the NOTICE: DEBUG messages in below logs were added to the source code of TF-A]The TF-A DT was compiled with option for SYSRAM with resulting dtb fw-configOP-TEE was compiled for SYSRAM and and enabled with pager as can be seen in  the contents FIP file:The reservation was made in OP-TEE DT:The optee-header_v2.bin: file  generated:Result:NOTICE: Early console setupNOTICE: CPU: STM32MP157AAA Rev.BNOTICE: Model: STMicroelectronics custom STM32CubeMX board - openstlinux-6.1-yocto-mickledore-mp1-v23.06.21NOTICE: DEBUG: stm32_print_boardinfoNOTICE: DEBUG: stm32mp_is_closed_deviceNOTICE: HELLO: fixed_regulator_registerNOTICE: DEBUG: stm32mp1_arch_security_setupNOTICE: DEBUG: print_reset_reasonINFO: Reset reason (0x14):INFO: Pad Reset from NRSTNOTICE: DEBUG: stm32mp1_syscfg_enable_io_compensation_finishNOTICE: DEBUG: fconf_populateINFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe2000INFO: FCONF: Reading firmware con

What way does ST recommend to copy a project without making errors?

I would like to read the unique device ID to check whether the product is good or not.Do you have a unique number?Please tell us.

I am using the 

Hello:I want use ST25R95 to do card emulation. But I can't find any source code in ST25 website.Can you help provide some source code?

Hello. I examined similar questions and answers. Since I'm a newbie, I couldn't find an answer to my problem.In the documentation of the STM32F756ZG development board, it is said that up to 24 channels of ADC measurements can be usable with 3 ADCs. When I want to assign pins in the CubeIDE, warning says that some pins cannot be used due to conflict.There are 2 different conflicts for ADC1, and only one for ADC3. I don't need to use ETH, but even if I set to ETH "disabled", the conflict does not disappear.I wonder if I can make 24 measurements with other available pins. Is it possible?Or does the dev card not allow using all the capabilities of the MCU? 

I saw a TouchGFX music player demo running on stm32f469i-disco development board, very beautiful.Where can I learn the source code

Hi!CMake now seems to be supported for STM32CubeIDE which is great. But how will CMake work with GPIO-configuration and STM32CubeMX when staring a CMake project from sqratch?  

I have an STM32MP157F-DK2. I am wanting to save the original contents of the sd card. How do I save the sd card to a file that I may later put it back unto the sd card? Will dd do this?Thank you!

STM32CubeIDE version is 1.13.0 build 17399_20230707_0829 on Win x64.Create a project for a Nucleo 64 STM32L452RE boardInclude FreeRTOS in your STM32CubeIDE project.In the project manager Check "Enable multi-threaded support", and select the default Thread-safe Locking Strategy.Put a simple printf into the default task:void StartDefaultTask(void *argument){/* USER CODE BEGIN StartDefaultTask *//* Infinite loop */printf("Hello World\n");for(;;) { osDelay(1); }/* USER CODE END StartDefaultTask */}The task will end up in an endless loop in void Error_Handler(void)Stack trace is as follows: void __retarget_lock_acquire_recursive(_LOCK_T lock)is being called with lock = 0, thusentering Error_Handler(), and getting stuck there.I did not observe this kind of behavior with the previous CubeIDE 1.12.x.The firmware package was the same with both CudeIDE version at STM32CubeL4 Firmware packageversion 1.18.0.Obviously newlib is missing something here in the new toolchain which comes

Hi all,I want to start a project with NFC for smart locks. I don't have experience in NFC. Could anyone please help me select NFC IC for the below requirement?1. smart door lock system.2. lock and unlock with only smartwatch and mobile, not with cardsThanks,Aravind

Hello,I am brand new to STM32 parts.I have a STM32F407G-DISC1 eval board and am using STM32CubeIDE version 1.13.1. I am trying to get the FatFs_USBDisk application working with the board. I imported the project and tried to build it.I get the following errors:13:43:30 **** Incremental Build of configuration Debug for project FatFs_USBDisk **** make -j8 all arm-none-eabi-gcc "C:/Users/brentw/STM32CubeIDE/workspace_1.13.1/FatFs_USBDisk/Src/main.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DUSE_HAL_DRIVER -DSTM32F407xx -DUSE_STM32F4_DISCO -c -I../../../Inc -I../../../Drivers/CMSIS/Device/ST/STM32F4xx/Include -I../../../Drivers/STM32F4xx_HAL_Driver/Inc -I../../../Drivers/BSP/STM32F4-Discovery -I../../../Middlewares/ST/STM32_USB_Host_Library/Core/Inc -I../../../Middlewares/ST/STM32_USB_Host_Library/Class/MSC/Inc -I../../../Middlewares/Third_Party/FatFs/src -I../../../Drivers/CMSIS/Include -Os -ffunction-sections -Wall -fstack-usage -fcyclomatic-complexity -MMD -MP -MF"Application/User/main

Unfortunately MCSDK is not available for Linux. So I have installed it on a virtual machine. But the application "Motor Pilot" doesn't work. It even doesn't start.I have tried with MCSDK 6.1.1 and 6.1.0, with Windows 11 and Windows 7, withOracle VM VirtualBox and virt-manager / libvirt. In all cases the application "Motor Profiler" doesn't start.Has anybody got MCSDK working in a virtual machine?Update:Finally I got it working. Motor Profiler and Motor Pilot require 3D Acceleration support. 3D Acceleration from VirtualBox and virt-manager don't work properly with those applications. Some parts of the screens are shown upside down.Solution with VirtualBox:Deactivating VirtualBox 3D Acceleration and selecting Graphic Controller VMSVGA. Installing Mesa3D Windows drivers from https://github.com/pal1000/mesa-dist-win/.Solution with virt-manager:Deactivating virt-manager 3D Acceleration and OpenGL. Installing Mesa3D Windows drivers from https://github.com/pal1000/mesa-dist-win/.

Hey guys and gals!Just received the STM32G031 Discovery Kit with the stm32g031j6m6 chip in the SO8 package. The thing is all my   attempts to program it failed.When the usb cable is plugged in a 'drive' connects where there are two files:1. DETAILS.TXT containing (probably) a result after the ST-LINK firmware update: "Version: V2J42M27Build: Mar 7 2023 17:19:20"2. FAIL.TXT containing "The interface firmware FAILED to reset/halt the target MCU"When attempting to upload a "blinky" code (a new project, just flipping the LED) the process fails with"""Target no device foundError in initializing ST-LINK device.Reason: No device found on target."""Having read through numerous posts even this one did not help: https://community.st.com/t5/stm32-mcu-products/solved-stm32g031j6-disco-can-no-longer-program-the-chip-no/m-p/98007 Jumper IDD (JP1) is in position. The user led (LD2) flashes in regular intervals but with no effect from the user button (as mentioned in the pdf document).I

The TF-A Makefile.sdk creates a small metadata.bin file for each type of boot (USB, SD-cARD, EMMC)1/ How to generates this outside of Makefile.sdk  ? I use this, but is only generates one file and there seems no parameter for the type of the boot device;TF_A_METADATA_JSON=plat/st/stm32mp1/default_metadata.jsontools/fwu_gen_metadata/fwumd_tool.py jsonparse $TF_A_METADATA_JSON -b build/stm32mp1/metadata.bin2/ Is the file the same for each device different or can it be used for SD, EMMC, USB  etc.. ?3/ is there a specification for the format of this file ?4/ is there a tool to enumerate the entries and their values in of this file ?