Join discussions in the Product Forums. Ask questions, learn from your peers, and share insights on ST solutions to accelerate your design journey.
Most recent activity
Hi everyone,I am developing a custom board using an STM32U5 and the LSM6DSV16BX. I am using MEMS Studio to train and configure the Machine Learning Core (MLC), but I noticed that the generated .h configuration file seems to set INT1_MLC1 bit at MLC_INT1 register by default.Even though I haven't explicitly set up physical pin routing in my project, the exported C array includes bank-switching logic that forces this configuration. I see the following sequence in my generated header: { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x01, .data = 0x80 }, // Switch to Embedded Bank // ... [other configs] ... { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x0D, .data = 0x01 }, // MLC_INT1: Route MLC1 to INT1 // ... [other configs] ... { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x01, .data = 0x00 }, // Return to Main Bank Because of this, INT1 pin is firing on MLC state changes. Since this is a custom design, I need strict control over my interrupt routing.My questions are:Can s
Hi,ASM330LHH datasheet states that "compensation for high stability over temperature" are embedded in the device. Could you provide more information about the correction algorithms applied ?In particular, when we measure the bias at 0°/s of the ASM330LHH in a temperature chamber, we get strange non-linear behaviors that we suppose to be a consequence of these algorithms. For instance, in the following figure (filtered bias at 0°/s depending on temperature) some "steps" can be observed. Could you provide a description of the corrections applied / the reason of this behavior ? It would make the device more predictable for us.Furthermore, is there a way to disable these corrections ?Thank you a in advance.
I am currently working with SBSFU on the STM32H743ZIT6 series and have implemented several modifications to its core functionality. I would like to clarify the potential impact of these changes.1. Modification to SBSFU FunctionalityI have altered the default SBSFU behavior by replacing the traditional firmware swapping mechanism with a bank-switching approach to reduce application downtime.Both Bank 1 and Bank 2 will contain the bootloader and the application. Bank selection is managed using the swap option byte.2. Relocation of Swap AreaI plan to relocate the swap area from Sector 8 to Sector 15, considering that Bank 2 spans from Sector 0 to Sector 7.The swap area is used during the decryption process. It requires 128 KB of memory.3. Clarification RequiredI would like to understand whether these modifications will have any impact on the system:Will the transition from a swap-based mechanism to a bank-switching approach affect the core functionality, integrity, or reliability of SBSFU
In the reference manual RM0440 Rev9 of STM32G4 family the bit combination 0b000 for the BLANKSEL setting in the comparator registers COMP_CxCSR is not documented: (Screenshot of page 771 and 773)I assume 0b000 means blanking input disabled, but it should be written in the rm.
When will the NUCLEO-C5A3ZG be available via distributors?The st.com site lists it as available(mass production), but none of the distributors has listed it at all. And the estore lists it as coming soon. Do you have any more concrete dates, will it be available anytime soon? Best
Hello,I’m working on a design using the STM32H750IBTx (LQFP176) running at 400 MHz with FreeRTOS, and I’ve encountered a strange intermittent issue with the display that only appears after long periods of operation.Problem Description:After about 30–40 days of continuous operation, the display starts to flicker and glitch.Once the flicker begins, it persists continuously for around 24 hours and then self-corrects without reboot.Performing a power cycle or reset also immediately clears the issue.No other functional failure is observed (system remains responsive, logs continue, etc.)System Overview:Display: 800×480 RGB LCD connected via LTDC interface (RGB565 format)SDRAM: 32 MB IS42S16160J-6TLI, 8192 rowsQSPI: 64 MB MX25L51245GConnected via FMCFMC clock: 200 MHz, SDRAM clock: 100 MHz (FMC clock divided by 2)Refresh rate: Configured for standard 64 ms / 8192 = ~7.8 µsREFRESH_COUNT and other parameters are set as below#define REFRESH_COUNT ((uint32_t)1539) /* SDRAM refresh counter 200MHz
Hello,I have provisioned two STEVAL-MKBXPRO Rev A boards using the FP-SNS-BLEMESH1 firmware and the ST BLE Mesh mobile application.My goal is to configure one board as a sensor node and the other as a relay/receiver node. Both nodes have been successfully provisioned and added to the same mesh network.However, I am unable to make them communicate correctly using only the ST BLE Mesh application. I cannot get sensor data to be transmitted from the sensor node to the receiver node.Could you please help me
Hi Does anyone know how to stabilize the gyroscope and accelerometer signals. I am getting signals back but I am trying to move a radio button on a bullseye and can't seem to smooth out the signal. I am using I2C communications.
I am currently working on a project using Steval mkboxpro and I would like to implement BLE Mesh communication between them. I am still learning and I was wondering if you could give me some guidance or recommend resources on how to do this Any help or advice would be greatly appreciated.
Hello, I’m having some problems with regression tool configuration for pedometer.I'm having some issues with the regression tool configuration for the pedometer. I’m using the STEVAL-MKI109D and STEVAL-MKI238A with MEMs Studio tool (FW: 2.10.2).First, I set up the sensor using 'Easy Configuration' and changed the Full Scale to ±4g, the Output Data Rate (ODR) to 25 Hz, enabled High-Performance mode, and set the bandwidth to ODR/2.Quick setup configurationFirst, I recorded and saved different walking types (slow, normal, and fast, with 20 steps each) using the 'Save to file' tab. This only saves the Accelerometer data.Next, I opened the Pedometer tab and ran the regression tool using these three files (fast_steps20.txt, normal_steps20.txt, and slow_steps20.txt). I selected the LIS2DUX12 sensor and tested it with the default settings for error type (Mean) and complexity level (50%). The generated results are in the attached zip file.After that, I went to the debug page to test the result
STM32N6570-DK: BOOT0/BOOT1 switches appear to have no effect. In DEV boot (BOOT1=H), external loader MX66UW1G45G_STM32N6570-DK fails with "Init function fail with timeout" via both STM32CubeProgrammer 2.22.0 CLI/GUI and STM32CubeIDE (ST-LINK FW V3J17M10, hot plug and under-reset modes, AP1). In serial boot (BOOT0=H), no USB DFU enumeration on USB1 and no UART acknowledgement on the STLink VCP (115200 8E1). SWD debug access works normally; the board previously booted user firmware from flash. Official STM32N6-OOB readme procedure reproducibly fails at the first sector erase.
I’m using CubeMX to generate the code for the STM32H7S7, more preciously the LTDC code that should be the same for Boot and the AppliFor some reason the HAL_LTDC_MspInit is generating different pins configurations for the Appli and the BootFor instance it generates the code for the PIN PF0 ------> LTDC_R2 in the boot meanwhile in the Appli there’s no PF0I would like to attach my .ico but it seems there’s no attach option in the new community UI
Good afternoon,I am working with the STSW-TTM005 example for a resolver-equipped motor and encountered an issue:Link: STSW-TTM005 | Product - STMicroelectronicsThe motor does not rotate, but instead oscillates between windings.In sensorless mode, the motor rotates correctly.During debugging, the resolver angle appears correct.I tried changing that setting:#define RESOLVER_ANGLE_OFFSET_DEGREE 185.0f // Angular offset in electrical degrees between the resolver and the rotor's magnetic flux, but it didn't workCould you please clarify which resolver-equipped motor was used to validate this solution? My setup is as follows:Control board: NUCLEO-G431RBDriver board: based on DRV8353Resolver board: STEVAL-TTM005AFirmware version: 5.4.8Motor specifications: PMSM with resolver, 20 poles, 24V DC, 67A peakI would appreciate guidance on whether my configuration is compatible and any recommended adjustments.Thank you for your support.Best regards, Anatoliy
Hello STMCommunity,I am a beginner working with the STM32H7B3I-EVAL evaluation board (MCU: STM32H7B3LIH6Q) and I am currently setting up my development environment on Ubuntu 24.04 Linux.I installed STM32CubeIDE using the following installer:st-stm32cubeide_2.1.0_27993_20260219_1630_amd64.deb_bundle.sh. zipHowever I am facing several issues during setup and project creation.Problems I am facinEmbedded Software Package Manager missingI cannot find the option: Help → Manage Embedded Software PackagesThe STM32H7 firmware package does not appear to be installed.Unable to create a proper projectWhen creating a new STM32 project for STM32H7B3I-EVAL, the project builds incorrectly and sometimes shows: make: *** No rule to make target 'all'. Stop.The expected firmware output files (.elf, .hex, .bin) are not generated.CubeMX integration problemIt appears that STM32CubeMX is not properly integrated with STM32CubeIDE on my Linux system..ioc file does not openWhen I double-click the .ioc
I noticed the following in the recent post announcing STM32CubeIDE for Visual Studio Code 3.8.0:CLI tools: A new bundle manager is enabling VS Code to download required CLI tools. This replaces the all-in-one STM32CubeCLT package. ...Now that STM32CubeCLT is no longer required by the VSCode integration, what is the future of STM32CubeCLT? In particular, will it continue to be updated and supported?
Hello.I am building a Thread SED product using the STM32W5MMG. Recently, after upgrading the firmware version to v1.24.0, I encountered a problem with low-power startup.Upon investigation, I discovered that the location of the “Init_Debug();” call within the MX_APPE_Init() method in app_entry.c was different.Previously (in v1.23.0), I had written the following code within the /* USER CODE BEGIN APPE_Init_1 */ block, and this worked correctly. HW_TS_Init(hw_ts_InitMode_Full, &hrtc); /**< Initialize the TimerServer *//* USER CODE BEGIN APPE_Init_1 */#if (CFG_FULL_LOW_POWER != 1) Init_Debug();#endif UTIL_LPM_SetStopMode(1 << CFG_LPM_APP, UTIL_LPM_DISABLE); UTIL_LPM_SetOffMode(1 << CFG_LPM_APP, UTIL_LPM_DISABLE); Led_Init(); Button_Init();/* USER CODE END APPE_Init_1 */ However, with the transition to v1.24.0, the call location of Init_Debug(); was changed as follows. HW_TS_Init(hw_ts_InitMode_Full, &hrtc); /**< Initialize the TimerServer */ Init_Debug();
Hello everyone!I will try to be short here… even though I will probably fail on this task.Hardware: ST-Nucleo-STM32F446REI have a 96kHz loop, which happens inside a callback from TIM3. I also have 4 analog signals to be sampled. Originally, I have set these signals into ADC1 (CH6 and CH7) and ADC2 (CH15 and CH9). Due to the ~10.4us period of time I have inside my callback, considering 168MHz system clock and 21MHz ADC clock (System Clock /2 /4), I need to act quick. I have decided to use DMA for this application: DMA2 Stream 0 assigned to ADC1 and DMA Stream 2 assigned to ADC2. Then, inside the loop, I am simply assigning the buffer values to variables (or, if I need to squeeze a few more cycles, I can use them directly). However, I noticed the variables assigned to ADC2 would not be sampled correctly: the first channel would be sampled just once, at the startup, and the second never, while the two channels on ADC1 would behave well. In my code, var3 and var4, respectively. The most re
We are seeing a very odd data corruption issue which is highly repeatable, and appears to be related to a configuration setting which we haven't yet identified.In our system (running on an STM32H7S7), we're using the STiROT + OEMuROT secure bootloader to load our application. After a minute or two, the application causes a hard fault.The issue comes down to a POP instruction. I can see in the debugger that a value is being copied from the stack to a register, but one of the bits is flipped. Subsequent instructions do some indirection which ultimately causes the hard fault.It's always the same instruction in the same line of code. It always occurs within the first minute or two of execution.Using the debugger, we can see that the value in the stack (stored in DTCM) is correct. The error occurs when it's copied to the register. And although the error always occurs at the same address, it doesn't appear to be a fault with that location, as when I moved the stack to elsewhere in DTCM,
Specific part: ST4SI3M004600HFWAccessed via Quectel modem AT commandshttps://estore.st.com/en/st4si3m004600hfw-cpn.htmlAccording to the product page, it features "Bootstrap connectivity profile provided by a trusted partner".Application note AN5740 says that it applies to ST4SIM-300M (https://www.st.com/resource/en/application_note/an5740-st4sim-with-truphone-connectivity--activation-procedure-stmicroelectronics.pdf).At time of writing ST4SI3M004600HFW, appears to be the only instance of ST4SIM-300M available.So it sounds like the activation instructions in AN5740 should apply to ST4SI3M004600HFW.Those instructions rely on reading the ICCID and feeding it to Truphone.However, the eSIMs that we (and other users) encounter have ICCIDs which are neither unique nor recognised by Truphone (https://community.st.com/interface-and-connectivity-ics-52/st4sim-300m-getting-the-same-iccid-162326).Questions:- Does AN5740 apply to ST4SI3M004600HFW?- Is there a version of the chip that does come with
Hi,I’ve just started a project with a TESEO LIV4F. The processor can communicate with the TESEO LIV4F module through a UART link. NMEA messages are received by the processor. Commands sent to the TESEO LIV4F module are acknowledged by the module (an answer is received by the processor). My problem is that the module do not receive any satellite.The antenna is a passive one which is DC shorted. Due to a BOM error, the serial coupling capacitor have been replaced by a zero ohm resistor. As the antenna is DC shorted, the TESEO LIV4F module input have been sorted to ground. I corrected the problem.Is it possible the module input have been damaged by the short-circuit ? I use a custom code based on the GetPos example. Maybe I missed something.Is there a specific command set to send to activate the reception of satellites ?Best regards,Nicolas
I’m trying to update thestm32WB55 - nucleo Version (MB1355C) SWD stm32wb5x_FUS_fw_for_fus_0_5_3.bin -- latest from STM32CubeWB-1.24.0But it keeps failing every-time i do it. StepsStart FUS check the wireless stack try and flash the first bin fileIt just doesn’t seem to want to work?Error: FUS_STATE_IMG_NOT_AUTHENTIC: It works on the USB sticks when i flash it this way. So i don’t know what it’s doing wrong? Or are these bin files only for the USB stick?
Hello All, I am looking for the CAD design files for the schematic and PCB layout (e.g., Altium, OrCAD, etc.). You are requested to share the design files in the CAD software format used by ST for STEVAL-STWINBX1 eval platform. I am planning use these design files as a base and modify them as per my requirement. Regards, Shailendra.
I was searching for a optimal cristal for my MCU and in the specs of HSE for my MCU (STM32F103) i found this highlighted in yellow Then in the guide shown below I saw and exampe but this doesnt match with the stated in the datasheet because of the following Here the CL1 and CL2 series equivalent is 5pF but the CL of the cristal is 8pF so I dont know if Im missing something or is that this condition is not always true, hope some one can help me to clarify this, thanks!!
Hi,I made a post a few weeks ago but I can’t find it now because I think this forum may have been updated.I have an STM32F779I-EVAL and I’ve managed to get LwIP_HTTP_Server_Raw compiled and running from this repo (STM32CubeF7/Projects/STM32F769I_EVAL/Applications/LwIP/LwIP_HTTP_Server_Raw).The display turns on, and within the debugger, there is no issue. It shows a DHCP timeout and then states its IP is 192.168.0.10, this is fine by me.With a normal ethernet cable connected to a network switch, or even using a crossover ethernet cable, I get nothing when I ping 192.168.0.10. Ethernet is set up correctly within Windows.Does anyone have a clue what’s going on here?I’ve tried basically every tutorial on the internet at this point to ping the device. The most hopeful looks like this one, but still nothing. I’ve also got a Nucleo-H755ZI-Q which doesn’t work with any example.I’m starting to think maybe it is my set up but I’ve tried across multiple computers, all using the correct settings (
Hello again.İ wrote a Python book, but I am new in STM32 boards. I am trying to learn.I bought a "STM32 Nucleo F7 56ZG(216 MHz)" boardand a "STM32 Nucleo H7 53ZI" this week.When I connected the USB socket at the ST-link side to the USB socket of my computer via an USB cable, there was no led light of the board. Both boards behaved like this.There were no led lights on them.What should I do?Should I connect both USB ports on a board to the computer at the same time?Thank you from now on.
ST Community highlights – April to June 2026
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.