Solved

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

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

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

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?

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,

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? 

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!! 

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.

I am trying to interface the EEPROM AT24C04C with STM32G4 series controllers. I have confusion in the function parametersHAL_StatusTypeDef HAL_I2C_Mem_Read_IT(I2C_HandleTypeDef *hi2c, uint16_t DevAddress, uint16_t MemAddress, uint16_t MemAddSize, uint8_t *pData, uint16_t Size)Can you please clarify on the MemAddSize parameter what has to be sent to for the above EEPROM?2nd Question: 1 page is 16 bytes, is it possible for me to write data above 16 bytes as well? 

The BAT30 datasheet shows a storage temperature of -65 to 150C and a maximum junction temperature of 150C.  There is no mention of the minimum operating temperature though.  Can you clarify?

Hi Guys,I am writing a code to measure a pulsating DC voltage. All that I have decided to take 50 samples and take the highest one.  Multiplying the peak value by a factor will give me the approximate RMS value. Please see my code. When built, an error “ Incompatible pointer assignment” shows. #include "stm8s.h"unsigned int max_v;unsigned k;unsigned int val[100];void Clock_Config(void) {CLK->ICKR |= CLK_ICKR_HSIEN; // Enable HSIwhile (!(CLK->ICKR & CLK_ICKR_HSIRDY)); // Wait for stabilizationCLK->CKDIVR = 0x00; // HSI 16MHz / 1 = 16MHzCLK->SWR = 0xE1; // Use HSI as master clock}void adc_init(void) { ADC1 -> CR1 = 0x40;ADC1 -> CR2 = 0x08;ADC1 -> TDRH = 0xFF;ADC1 -> TDRL = 0xFF;ADC1 -> CR1 |= ADC1_CR1_ADON; }uint16_t read_mains_value(void) {unsigned int value;ADC1 -> CSR = 0x05;ADC1_StartConversion(); while(ADC1_GetFlagStatus(ADC1_FLAG_EOC) == FALSE);value = ADC1_GetConversionValue(); ADC1_ClearFlag(ADC1_FLAG_EOC); // return value; }vo

I would like to use the Stop3 low-power mode on an STM32U545RE (NUCLEO-U545RE-Q board) and to wake-up the device by the RTC. I have a working example for Stop2 mode for which I largely used the inspiration from the stm32u5 workshop. But when I replace the HAL_PWREx_EnterSTOP2Mode call(s) with HAL_PWREx_EnterSTOP3Mode, the device does not wake up from the stop mode anymore. At least the current consumption drops down to 3uA so I am confident that the Stop3 mode itself is working.The code parts of my main function which I believe are relevant look as follows:HAL_Init();SystemClock_Config();SystemPower_Config();MX_GPIO_Init();MX_ICACHE_Init();MX_RTC_Init();/* The SMPS regulator supplies the Vcore Power Domains */HAL_PWREx_ConfigSupply(PWR_SMPS_SUPPLY);/* Enable ultra low power mode */HAL_PWREx_EnableUltraLowPowerMode();/* Enable the Autonomous Mode for the RTC Stop0/1/2 */__HAL_RCC_RTCAPB_CLKAM_ENABLE();/* Set RTC wakeup timer for 2s */HAL_RTCEx_SetWakeUpTimer_IT(&hrtc,

I have a custom board with G491 and an LED driver (Kinetic KTD2037). MCU is the I2C master. Any attempt to read a register using HAL from the KTD2037 fails, ErrorCode = 0x2 (arb lost). Register writes are OK. I can read/write other devices on the same bus OK. The KTD2037 datasheet has this for an I2C register read:This doesn’t seem consistent with HAL_I2C_Mem_Read() or HAL_I2C_Master_Receive(). On a scope HAL_I2C_Mem_Read() results in  S, 7-bit addr, write, ack, reg addr, ack, Sr, 7-bit addr, read, ack, 0xFF, nackI try setting the internal register pointer (it may not have one) using HAL_I2C_Master_Transmit(), which works OK. Then I follow it with HAL_I2C_Master_Receive() resulting in  S, 7-bit addr, read, ack, 0xFF, nackIt looks like the master says arbitration lost because of unexpected nack from the KtTD037.The KTD2037 datasheet does not mention I2C repeat start.Any way to read this device without writing my own I2C driver?

Hi, I would need FIT or MTTF for M24512-RMN6TP. ThanksBest regardsEnrica

I am using LSM6DSV16X with MLC configured in MEMS Studio v2.3.1. The MLC has an IIR2 high-pass filter on accelerometer XYZ with "store in FIFO" enabled. The UCF was generated by the MLC Tool (internal version 2.4.4 as reported in the output JSON). Expected: IIR filter output values appear in FIFO as tag 0x1B frames, as declared in the mlc_identifiers section of the generated JSON. Observed: Tag 0x1B frames never appear in the FIFO. Firmware drains the FIFO after each 60-sample window and observes exactly 3 MLC words per window — 2x tag 0x1C (features) and 1x tag 0x1A (result). No tag 0x1B words arrive. Verified:- EMB_FUNC_FIFO_EN_B (0x45) = 0x02, MLC_FILTER_FEATURE_FIFO_EN bit is set (confirmed against DS13510 Section 13.18)- mlc.json correctly lists fifo_tag 0x1B identifiers (FILTER_HP_ACC_X/Y/Z) in the metadata- mlc_settings.json has "input": "Acc_XYZ + store in FIFO" for the filter- Firmware FIFO drain handles tag 0x1B explicitly — not dropped in software- No unknown FIFO tag warnin

I have been working with the single core LoRaWAN_End_Node example application on a B-WL5M-SUBG1 board with good success.  With STM32CubeMx v6.16.0, WL Firmware 1.4.0, I see a current draw of under 2uA between transmissions.Last week I upgraded STM32CubeMx to v6.17.0 which in turn upgraded the WL Firmware to 1.5.0, changed the end node example to use the LBM library rather than the LmHandler for managing the radio, and changed the example application name to LoRaWAN_End_Node_LBM.  The application functionality is good but the power consumption jumped to around 80uA between transmissions.In both cases I configured pullups in the USART2 pins (PA2, PA3).I can alternate between these two versions of the application on the same board and the results are very consistent.Has anyone else seen this and does anyone have any suggestions?

I have a discussion in progress, started on 5 June, so it has not been ported to this new forum.I cannot carry on the discussion here, but I can’t seem to log into the old forum - if I use my email address and password it complains about illegal characters but if I use my username, it says “Attempt to sign in to SSO account using a username and password.” I have no idea what and SSO account is!How do I continue my discussion?

Hi everyone,I’m currently working on a design to integrate an ESP32-C6 with the ST85MM PLC modem, and I’m hitting a few roadblocks regarding the best hardware architecture and communication flow.To be honest, I'm also a bit confused about the specific differences between the ST8500 and the ST85MM. I’ve been reading documentation for both, and while they seem very similar (same package, similar pinouts), I'm not clear if the host interface or boot behavior differs significantly between them.Crucially, I haven't been able to find any firmware examples or reference code for either chip. I feel like I'm flying blind regarding the actual host communication implementation. If anyone has a code snippet, a repository, or a specific application note that shows how to initialize the modem or handle the host exchange, that would be appreciated.My main goal is to use the ESP32-C6 as the host controller to manage the ST85MM, specifically for loading firmware

Greetings,I am working on a Hardware-based password manager. When the device is first setup, A 512-Bit key is created which is used to encrypt & decrypt the passwords. This key will be stored on STSAFE-A's Symmetric Key Table and the password can be encrypted/decrypted using this key on the STSAFE-A.Now, I want to be able to set a user specified password on the STSAFE-A and then this password will be used by STSAFE-A to authenticate before performing any encryption/decryption/etc operations. After a set amount of wrong attempts, STSAFE-A should erase the key.Is this achievable?Regards,Aditya M.

Hi there,the VL53L5CX datasheet mentions that RSVD6 is a GPIO and defaults to being an open-drain; my question is:Can I use RSVD6 programmatically? Are there any resources which show it being used? Otherwise, how can I use it? Many thanks in advance

I have read the migration guide (Typical HAL ADC use cases for migration - HAL2 Migrator 1.0.0 documentation) as well as the article How to use ADC with STM32CubeMX2 | CommunityIn the HAL2 code, I found functions such as HAL_ADC_MM_SetConfig(), which suggests that ADC multimode/dual mode is supported by the HAL.However, when using STM32CubeMX2 (not STM32CubeMX), I cannot find any option to configure ADC dual mode (e.g., ADC1 + ADC2).My question is:How can ADC dual mode be configured in STM32CubeMX2?If ADC dual mode configuration is currently not supported by STM32CubeMX2, a short confirmation would be appreciated. Thanks in advance for your help.

I am having trouble connecting to the STM32N6 with SWD.I have implemented a design using the STM32N645X0H3Q (though I have placed the STM32N647X0H3Q) using external VDDCORE. R110 is not mounted (to set VLXSMPS to NC).On startup I have VDDIO (3.3V) and VDDA1V8ON (1.8V) to the MCU, and the MCU activated PWR_ON (I have VDDA1V8ON to the PDR_ON pin, A1 on another page). This activates the reset of the power, including VDDCORE. All voltage measurements are as expected on the board.When I try to connect to the board using SWD in STMProgrammer (v2.20.0), I see the 3.3V, but the STMProgrammer does not connect. I am using a Minnie V3 (v V3J16M8) on Windows. I have tried lower frequencies and all modes and reset modes without success. I should mention that on my prototype board, I have not mounted external crystals, flash or ram. Though I believe that is not necessary for STMProgrammer to see the MCU. Any help is greatly appreciated!

Hello everyone. I am trying to communicate with a VL53L4CD on my PCB, on the same I2C Bus I have a LP LED Matrix Controller and an EEPROM that work just as I hoped they would.  But none of the VL53L4CD seem to be able to communicate over the Bus. I have by now tried to look at everything possibly wrong with it.  Software: The Software gives out the exact I2C Signal I would be expecting (Address 0x52 (derived from 0x29 of course)) but I always get NACK’s,  Hardware: All Sensors are on the same bus, where I Chip Select via the XSHUT Pins, those forms also look correct and only the one is high where I want to talk to the sensor, so there’s not 2 sensors that could respond to the same address having XSHUT on the same niveau. I have tested the connection to the pads, and those are all correct, so is the Power SUpply and GND to the Chip all of those seem correct according to the Datasheet.  My I2C Bus runs on 100kHz which as far as I can tell should work with the Sensor.  Furthermore I have

Hi.For our footprint definition we require a confirmation from you: The letter ‘C’ in the Pin Count ordering information is used for both 48 and 49 pins packages. The WLCSP package is 49 pins.Thanks in advance,Noam