Product forums

Hi, We are using an STM32F103 as a controller for a Half-bridge dc-dc convertor running at 110Khz. We are facing an issue where the microcontroller is resetting every minute when output crosses 12A. We disconnected all peripherals, removed all protections and kept only the PWM and reset problem sustains itself. On further inspection, we found that the PWM duration increases for a few cycles and then the microcontroller resets. It seems to us that the microcontroller clock slows down and then finally stops forcing a reset. We do not have watchdog timer implemented.We are using a 8MHz crystal. Please check attached image (CH1 - reset line, CH2 - Independent PWM, CH3 - Half bridge high side) The fun fact is that if we place the microcontroller on an external PCB and connect to the gate driver with wires, we do not see the microcontroller resetting. (even without the crystal). Sometimes, attaching an oscilloscope probe (1Mohm) also prevents restart. Currently,

Dear Sir or Madam,I require a RoHS declaration of conformity for the following component:STEVAL-MKI208V1KCould you please share it?Thank you very much and kind regards,Thomas

In the past, I have used an LSM330 to wakeup on a gyro z-axis threshold and activate the INT1 pin as shown below:Gyro_WrByte(GYRO_CTRL_REG1, 0x3f); // 95Hz DataRate : 25Hz Cutoff : Normal Mode : Enable All AxesGyro_WrByte(GYRO_CTRL_REG2, 0x07); // HPF Normal Mode : 0.045Hz HPF Cutoff Freq : HPF Normal ModeGyro_WrByte(GYRO_CTRL_REG3, 0x80); // INT on INT1_Gyro PinGyro_WrByte(GYRO_CTRL_REG4, 0x00); // Continuous Update : Little Endian Data : 250 dps FS : 4-Wire SPI IntfcGyro_WrByte(GYRO_CTRL_REG5, 0x04); // Normal Mode Reboot Mem Content : FIFO Disable : HPF Disabled : INT1 Select = 01b : OUT Select = 0 : Use HPF for INT1 to account for any incr gyro bias drift due to incr temperatureGyro_WrByte(GYRO_INT1_CFG, 0x20);      // OR Combination : Z-High EventGyro_WrByte(GYRO_INT1_TSH_ZL, 0x3b);   // Gyro_WrByte(GYRO_INT1_TSH_ZH, 0x02);   // Z-Threshold = 571(0x023b) * 8.75mdps = 5Deg/sGyro_WrByte(GYRO_INT1_DURATION, 0x8a); // WAIT Enable : INT Duration

After reviewing the website, we noticed that the LSM9DS1 is currently listed as obsolete. We would therefore appreciate your guidance on the following points:Is the LSM9DS1 still recommended for new designs, or should it be avoided given its obsolescence status?We understand that the LSM6DSO (https://www.st.com/en/mems-and-sensors/lsm6dso.html) is currently recommended. However, this is a 6-axis IMU. Our application requires a full 9-axis solution including a magnetometer.What is your recommended 9-axis solution today?Do you recommend pairing the LSM6DSO with a specific ST magnetometer device?If we implement a 6-axis IMU together with a separate ST magnetometer, do you provide a 9-DoF (Degrees of Freedom) fusion algorithm that supports such a configuration?Can your fusion algorithms (e.g., MotionFX or equivalent) run on any ARM-based MCU, or are they restricted to STM32 devices?Are there licensing requirements associated with using your fusion libraries?Are there any usage limitations

Hello, I have encountered some issues while developing with the  ASM330LHH. During the initialization sequence of the ASM330LHH interface, I first read the WHO_AM_I  register. After confirming that the value is correct, I proceed to access other registers. In my tests, the WHO_AM_I value read back was correct. After checking the datasheet, it mentions that DEVICE_CONF set 1 to enable configuration. Now, after reading WHO_AM_I and before accessing other registers, I set DEVICE_CONF to 1. When I test again, the value read back from WHO_AM_I becomes incorrect. Could you explain why this happens? I am using SPI for communication in both cases, and the SPI configuration has not be changed at all — I only added the DEVICE_CONF operation.

For STM32H7, if the FMC data lines and SDRAM data lines are cross-connected (not D0 to D0), and address lines are also cross-connected (not A0 to A0), can SDRAM work properly? My PCB is about to be manufactured, but due to the hardware engineer’s design, the SDRAM data lines and the MCU’s FMC data lines, as well as the SDRAM address lines and the MCU’s FMC address lines, are not connected one-to-one according to the CubeMX standard. Instead, the order has been shuffled. The actual wiring relationships are as follows: Data line connections: MCU FMC_D0 is connected to SDRAM_D13MCU FMC_D1 is connected to SDRAM_D14MCU FMC_D13 is connected to SDRAM_D1MCU FMC_D14 is connected to SDRAM_D0MCU FMC_D4 is connected to SDRAM_D7MCU FMC_D5 is connected to SDRAM_D6MCU FMC_D6 is connected to SDRAM_D5MCU FMC_D7 is connected to SDRAM_D4Address line connections: MCU FMC_A0 is connected to SDRAM_A2MCU FMC_A1 is connected to SDRAM_A3MCU FMC_A2 is connected to SDRAM_A0MCU FMC_A3 is connected to SDRAM_A1MCU

Dear All,Could you please provide the HBM and CDM level for the below four products?1. M95320-DRMN3TP/K2. STPS15H100CBY-TR3. STPS3150UY4. STPS1H100AYWe were unable to find this information in the datasheets. For other parts (e.g., MCUs), these values are typically specified, but they do not appear to be listed for these products. I would appreciate your support in sharing this information.Best regards,Rei.

I have the following original debuggers:Stlink V2Stlink V3_SETStlink V3_MINIE (2 pieces)I was recently testing a simple board with an STM32U083 (powered by 3.3V) and found that two Stlink V3 MINIE units could connect to the MCU. Meanwhile, both the V2 and V3_SET work without any issues.I observed that after connecting (SWDIO,SWCLK,VDD,GND) to the powered MCU, both the V2 and V3_SET leave SWDIO at 3.3V (pull-up in the MCU) and SWCLK at 0V (pull-down in the MCU). Whereas the MINIE maintains a 3.3V level on both SWDIO and SWCLK. Out of curiosity, I connected an external 10k pull-down resistor to both SWDIO and SWCLK and observed that SWDIO drops (which is fine), but SWCLK does not, meaning that the Stlink V3 MINIE actively holds SWCLK at 3.3V. Am I doing something wrong, or are both MINIE boards defective?Best regards,Michal Dudka

  Device STM32WLE5 Clock configuration SYSCLK : MSI 16 MHz (MSIPLL mode Enabled)LSE : 32.768 kHz crystalLPTIM2 kernel clock : LSELow power mode : Sleep Observed behavior When configuring LPTIM2 with LSE clock, the following code sometimes blocks because the ARROK flag never sets. __HAL_LPTIM_AUTORELOAD_SET(&hlptim2, Period); while (!__HAL_LPTIM_GET_FLAG(&hlptim2, LPTIM_FLAG_ARROK)); This occurs after waking up from Sleep mode. Workaround Executing the following code before or after wake-up resolves the issue. RCC->BDCR |= RCC_BDCR_LSESYSEN; After writing LSESYSEN, the ARROK flag sets normally. Initialization code SystemClock_Config() already enables LSESYSEN. It is CubeMX provided.  LL_PWR_EnableBkUpAccess(); LL_RCC_LSE_SetDriveCapability(LL_RCC_LSEDRIVE_MEDIUMLOW); LL_RCC_LSE_EnablePropagation(); LL_RCC_LSE_Enable(); while (LL_RCC_LSE_IsReady() != 1) { } LL_RCC_LSE_EnablePropagation() is defined as: __STATIC_INLINE void LL_RCC_LSE_EnablePropagation(void) { S

The SR5E1E7 program written with a trimmed library, Makefile, and blank project file has locked up the chip. After a full chip erase, the demo program can be re-flashed successfully, but flashing my own written file immediately locks the chip again. It has been identified that the DCF address 0x1ff00100 cannot be modified. May I ask what the reason is?

Hi Community, We are exploring the migration of our FreeRTOS-based firmware to Zephyr. Our current design heavily relies on TouchGFX (provided by ST) for controlling an 800×480 touch display. Here are some key details of our setup: TouchGFX with external SDRAM for a double frame buffer using the FMC peripheral Images, fonts, and text stored in external QSPI Flash LTDC controller in use DMA2D accelerator enabled RGB image compression utilized Is there any sample application or detailed documentation available for achieving this on Zephyr? I have already briefly reviewed the following resources: Abstraction Layer Architecture | TouchGFX Documentation and https://support.touchgfx.com/docs/basic-concepts/operating-system#touchgfx-os-wrappers However, I need more guidance, specifically: Examples or reference projects for TouchGFX on Zephyr Detailed documentation on integration steps We have a tig

Hi all,   in the release note of the STM32C5 family it is mentioned that the family will be supported with STM32CubeMX2. May I please ask when is it going to be available?    With best regards, Dmitry

Hi,I’m currently working with an ST4SIM-300M eSIM and testing it for an IoT application.I was able to read the following ICCID from the device:89019990001234567893I wanted to ask if anyone knows which operator or profile this ICCID belongs to. Also, I’m not sure how the activation process should work for the ST4SIM-300M.Does it come with any initial bootstrap profile for network access, or do I need to provision a profile first before it can connect?AT%PINGCMD=0,"8.8.8.8"OKAT+CPINERRORAT+CSQ+CSQ: 99,99OKAT%PDNSET?%PDNSET: 1,,IPV4V6,,,,,0,0,0OKat+cops?+COPS: 0OKat+cops=0At the moment I’m not able to get network connectivity, so any guidance on the correct activation/provisioning steps would be really helpful.Thanks in advance!

Dear ST Support Team, I am seeking technical assistance for two critical issues I am encountering while developing on the STM32MP157F-DK2 (Kernel 5.10.61, Ecosystem v3.1). Issue 1: GLIBC Compatibility When running applications compiled on my host machine, I receive the error: /lib/libc.so.6: version 'GLIBC_2.34' not found. I am attempting to cross-compile using the correct SDK for Ecosystem v3.1, but I am struggling to locate the compatible toolchain/environment for my specific kernel version (5.10.61). Issue 2: Device Tree (.dts) Configuration I am unable to enable additional peripherals (specifically UART7). Despite updating the .dts file to set status = "okay", the peripheral remains disabled on the target board (verified via cat /sys/firmware/devicetree/base/soc/.../status). It appears the system is ignoring my device tree updates and defaulting to the internal bootloader configuration. Attachments:Screenshot showing the GLIBC error on the board.Screenshot of th

How many uart channels are available on STM32H573I-DK Discovery kit.I am Looking for atleast two channels..Thanks in advance...

Run SimulatorGenerateDoneGenerate Assetsmake -f simulator/gcc/Makefile assets -j8generated/simulator/gcc/Makefile:221: recipe for target 'images' failedprocess_begin: CreateProcess(NULL, ../Middlewares/ST/touchgfx/framework/tools/imageconvert/build/win/imageconvert.out -r assets/images -w generated/images, ...) failed.make (e=2): 系统找不到指定的文件。make[1]: *** [images] Error 2simulator/gcc/Makefile:32: recipe for target 'assets' failedmake: *** [assets] Error 2FailedFailed

Hi, just wondering if these constants (specifically NONE and OR both being 0) in the ULD for VL53L8CX are correct#define VL53L8CX_OPERATION_NONE ((uint8_t)0U) #define VL53L8CX_OPERATION_OR ((uint8_t)0U) #define VL53L8CX_OPERATION_AND ((uint8_t)2U) it look like it should be a sequence (0, 1, 2) so the repeated (0, 0, 2) appears out of place. It's hard to tell from the examples if this is intentional though.

Described below method is intended to perform correction of the static ADC’s non-linearity in software using LUT. It requires pure sine-wave source only, that can be generated by any available analog circuitry. Basically, it corrects non linearity induced by signal conversion analog front end all together, that includes ADC and it’s drivers, signal conditioning / amplification stages, inputs protection, etc. There is a way to do the same linearity correction by applying linear ramp voltage and generating error LUT table. New method is using sine-wave, and consequently has a few advantages over “classic” : 1. Linearity of the sine-wave is much more easier to verify down to -140 -160dB (0.1 – 0.01 ppm) using simple tween-T notch filter. 2. Analog front end may include DC blocking capacitors. 3. Calibration test signal could function in the “working band” area, and some complex dynamic distortion of the drivers (due to fall of the AOL over frequency, output stage

According to the PD 3.1 requirements (also PD 3.0), I need to connect UCPD1_CC1 and UCPD1_CC2 to USB-C CC1 and CC2 to communicate and request the desired voltage. But STM32G0B1KBU6  has only UCPD1_CC1 available. Is there any way to connect STM32G0B1KBU6  to USB-C to comply PD 3.1 requirements?

Hi everyone, I have a quick question regarding the upcoming release of CubeMX2 and its backward compatibility. Once CubeMX2 is released, will the older series before C5 (like the F4) support MX2 and HAL2? Also, if they do support it, will we be forced to bundle HAL2 for these older models, or will there be some flexibility? Thanks in advance for any insights or official clarification! Best,Leo

Hello,the SPI does work with NSSP(Negative Slave Select Pulse-Mode), but it does not work if I disable NSSP. As someone pointed out the SPI NSS(P) may only work if the Pulldown of that pin is enabled, but I’m not 100% sure on that one, but it seems to wirk for NSSP-En that way. For NSSP-Disabled I could not get the SPI-Controller to control the NSS(CS).I observed two issues:1) On Reset the NSS(CS) is low and will stay low until the first SPI Transaction. I tried to set it via HAL_GPIO_WritePin( … , GPIO_PIN_SET); but that has no effect, maybe because the Pin is controlles by the SPI-HW.2) Is the serious issue is, if I disable the NSSP, the CS does not work at all.How can I make the Hardware NSS work with NSSP disabled?Thanks a lot, Best Regards, SeppelP.S.This is the Setup and Waverforms for the NSSP-Disabled, I have a 2s delay on startup, which you can see on the scope-pictures.: This is the setup for the NSSP Enabled, the same was used for NSSP-Disabled(only that NSSP was set to

I`m doing project using connection of Pololu VL53L7CX multizone sensor to STM32 NUCLEO-F103RB. It`s my first expirience with that. I would like to ask more experienced developers for help and, if possible, an example of the code. Thank you!

I am trying to implement TFTP file transfer on my STM32 module (Nucleo-H723ZG). I have taken reference from:https://github.com/STMicroelectronics/STM32CubeF4/tree/master/Projects/STM324xG_EVAL/Applications/LwIP/LwIP_IAPhttps://github.com/JoeMerten/Stm32-Tools-Evaluation/tree/master/STM32Cube_FW_F4_V1.9.0/Projects/STM324xG_EVAL/Applications/LwIP/LwIP_TFTP_Server For file transfer I am using tftpd64 software. I used the software for PC-PC file transfer which were on the same local network and it was successful. But when I am trying to send file from PC-STM32 module I am only receiving write request from the client (PC). After that  I am suppose the get a block 0 acknowledgement from the server (STM32 module) which I am not receiving. I tried debugging the code but in the code the acknowledgement is being sent successfully. For more information:- my ethernet is up - I have successfully ping the IP address that I have assigned or configured for the module. - Moreover, I am using

I've read other posts and the relevant app notes about this and tried some testing on my side but still not finding an easy or even effective way to do this.I have a CubeIDE project built on a CubeMX ioc file for STM32G0B1KEU6 and want to change to STM32G0B1KCU6 (smaller flash). Same package, same core, same pinout, just smaller flash size. Should be easy.CubeIDE 2.1.0CubeMX 6.17.0I open the CubeIDE project and then the existing ioc file within that.I click Pinout -> List Pinout Compatible MCU's and select new the MCU. I click Import.It creates a new ioc file (instead of updating the existing file within this project which is what I actually want) and attempts to import all of the existing ioc project settings. It fails to import DAC and USB settings for some reason which I now need to go and manually edit and hope that everything else is correct. It is completely unclear what has and has not ported over successfully so I'll need to very carefully review everything. Now I

Hello, As part of a new project, I'd like to use DFU mode for programming my STM32F303VET6. I have a button that controls BOOT0. If the button is pressed during the microcontroller reset, there's no problem; I successfully enter DFU mode and can reprogram without any issues. I'd like to be able to perform this step without any physical intervention on the board, but rather by creating a 'jump' from my application to the internal ST Bootloader. My board is connected to the PC via a CDC connection. Using HyperTerminal, I send a command that calls a JumptoBootloader function. My function is as follows:   void JumpToBootloader(void) { // 1. Stop USB peripheral RCC->APB1ENR &= ~RCC_APB1ENR_USBEN; // Disable USB clock RCC->APB1RSTR |= RCC_APB1RSTR_USBRST; // Reset USB RCC->APB1RSTR &= ~RCC_APB1RSTR_USBRST; // 2. Put USB pins (PA11/PA12) in analog mode RCC->AHBENR |= RCC_AHBENR_GPIOAEN; GPIOA->MODER |= (3U << (11 * 2)) | (3U << (12 * 2)); // Ana