Solved

Hello,I am using NUCLEO-H755ZI-Q (STM32H755) and I am observing a reproducible boot issue related to high system clock frequency.1. Hardware / EnvironmentBoard: NUCLEO-H755ZI-QMCU: STM32H755Power supply: USB (on-board)Debugger: ST-LINK (Connect under Reset)Supply configuration: LDOToolchain: STM32CubeIDE 1.19.02. Issue DescriptionWhen the system clock is configured to 480 MHz, the board fails to boot after power-on or reset.Flash programming and verification succeedImmediately after reset release, the target becomes unresponsiveST-LINK connection is lost When the same firmware is configured to 400 MHz, the board boots and runs normally.Interesting behavior:Power-on the boardFlash firmware configured for 400 MHz → boots normallyWithout removing power, rebuild and flash firmware configured for 480 MHzThe board runs normally at 480 MHzIf power is removed and re-applied, 480 MHz boot fails againThis behavior is fully reproducible.3. ObservationsThe issue only occurs after a cold power

I have a custom board with stm32wba65 processor. I also have an RFM95 LoRa module. I need to add LoRaWAN capability. I tried adding I-CUBE-LRWAN into my CubeMX but was not able to load it (not a recognised package).How can I get an ST or Semtech approved LoRaWAN stack into my project?Please do not suggest I use stm32WL processor.

Hello STM Community,I currently have a NUCLEO-U575ZI-Q board and the X-NUCLEO-IKS4A1 motion MEMS and environmental sensor expansion board. I’m looking to add BLE functionality and was considering the X-NUCLEO-WB05KN1.Before proceeding, I’d like to ask:Are the X-NUCLEO-IKS4A1 and X-NUCLEO-WB05KN1 compatible when stacked together on the NUCLEO-U575ZI-Q?If not, is there an alternative BLE expansion board that is known to work well with the IKS4A1 on this Nucleo board?Alternatively, is there an expansion or adapter board that allows both shields to be connected without pin conflicts?Any guidance or shared experience would be greatly appreciated!Thanks in advance.

I'm developing a new secret card project using STM32L476RG and X-NUCLEO-NFC07A1 board, I plan to let the secret card to store private key and do signature related tasks. I'm not sure where can I get blank card which contains the same MCU with STM32L476RG) and the same NFC7 with X-NUCLEO-NFC07A1? I found there are blank card in sale support NFC ISO 14443 protocol. Seem the NFC7 using ISO 15693 protocol. So the NFC blank card support support ISO 15693 protocol can run my image, as showed in image below?ThanksJack Ding.    

This is a continuation from this post, where I erroneously marked the post as solved: https://community.st.com/t5/imaging-sensors/vl53l7cx-distance-data-stratification/td-p/866073Unfortunately I'm still experiencing the issue where range data continue to be unstable, and appear to stratify or cluster into discrete magnitudes.Test setup:2x VL53L7CX sensors on one I2C busCover glass installed on both sensorsRanging enabled on both sensorsThe video is showing data from a single sensorI have a test setup with a sensor looking at the back of a notebook at a fixed distance as shown in this picture. The range data returned from the sensor varies between actual the distance, and shorter distances. You can see this in the video below. In addition, in the video I'm also printing the `target_status` for all 64 zones on the terminal output to the right. Would anyone have insight, or perhaps offer troubleshooting steps?  Thank you EDIT: Added test setup details

The Errata sheet for STM32G030x6/x8, ES0486 - Rev 6, states in chapter 2.2.9:After connecting the debug interface and until the device power-down, the boot source upon reset or wakeup from a low-power mode is determined by the PA14-BOOT0 pin level before connecting the debug interface (stored by the device), as opposed to the actual PA14-BOOT0 pin level. The device power-up restores the operation of the PA14-BOOT0 pin as direct boot source selector.But this also applies to the empty check: if the debug interface is connected, the empty check is only updated on device power-up (reset is not sufficient).So, if you program an empty device with the STM32CubeIDE in order to debug the software, you need to stop the first debugging session, perform a power cycle and start the next debugging session. Otherwise, the µC will keep executing the bootloader and debugging will fail with “Break at address 0x1f… with no debug information available, or outside of program code”.

HeyI've got great success with the VL53L4CX at sorter ranges, but at longer ranges i seem to get two objects. One closeby between 10 and 30mm away, and one at the distance that it should be.I've done calibration and i cant' get this to go away. I'm assuming it's crosstalk but i've done the crosstalk calibration and so on. What could this be?Example of some of my log output, where you can see the two outputs and some other values from the same measurements.[995156] PerformMeasurement(offset=0, maxdepth=2000, ignoreBelow=10)[995162] Read 388 bytes...[995163] VL53L4CX_SetCalibrationData status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetXTalkCompensationEnable status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetMeasurementTimingBudgetMicroSeconds status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetDistanceMode status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetOffsetCorrectionMode status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SmudgeCorrectionEnable status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetUserROI

Hello ST Community,We are developing an iOS application using the ST25SDK (Swift) to interact with a device equipped with the ST25DV02K-W1 (Dual Interface EEPROM).Our Goal: We need to configure the PWM parameters to control an Adjustable Output Current (AOC). Based on our system design (ported from a working Android implementation), we need to write 4 bytes to Block 62 (Address 0xF8 / 248bytes).The Data Structure: The 4 bytes represent:Bytes 0-1: Period (Little Endian)Bytes 2-3: Pulse Width (Little Endian), where Bit 7 of MSB is set to 1 to indicate "NFC Update".The Issue: The iOS app calculates the correct payload (e.g., [B1 3B 70 AF]) and executes writeSingleBlock without throwing any errors. The console logs confirm the command is sent. However, the value on the device does not change. We suspect the Microcontroller (MCU) on the other side is overwriting the value immediately because it cannot access the I2C bus while the RF field is still active.What we tried:We force presentPasswo

I have installed the stm32 cube ide , after creating the project i am get .ioc file for the configuration , i have done reinstall process but i am unable to clear the issue , the ide is opened as the image attached . 

CubeMX version 6.16.1 I found STM32WBA55CG project with ThreadX,  the  parameter of "TX_LOW_POWER_USER_ENTER" and "TX_LOW_POWER_USER_EXIT" will be reset to default after the ioc re-open.This bug can be 100% reproduce. 

Hello community members, I am using a STM32H5 with acitvated MPU region. I want to check and test dection of nullpointer access.Because of safety reasons. I have configured and activated the mpu so far. When doing a write access to the declared null pointer, the MemManageFault Handler is called as expected. uint32_t *m_pTest = nullptr;*m_pTest = m_value; // -> MemManageHandler is called (as expected)when doing a read access, the BusFaulthandler is calledm_value = *m_pTest; // ->BusFaultHandler is called (not my expectation)//here my mpu configuration and settingsSCB->SHCSR |= SCB_SHCSR_MEMFAULTENA_Msk |SCB_SHCSR_BUSFAULTENA_Msk |SCB_SHCSR_USGFAULTENA_Msk;/* Configure the MPU to prevent NULL-pointer dereferencing ... *///check nullpointer access Region1MPU_InitStruct.Enable = MPU_REGION_ENABLE;MPU_InitStruct.Number = MPU_REGION_NUMBER1;MPU_InitStruct.BaseAddress = 0x00U;MPU_InitStruct.LimitAddress = 0x200U;//512Byte for exampleMPU_InitStruct.AttributesIndex = MPU_ATTR

CubeIDE: v2.0.0CubeMX: v6.16.1Debugger: ST-LINK/V2 V2J46S7Hello,I'm attempting to setup a dual core project using STM32H757XIH MCU on CubeMX. I've generated and imported the project for CubeIDE. I've configured the Trace and Debug -> DEBUG for "Serial Wire" with M7 and M4 selected with Cortex-M7 as the initializer. I've configured one pin (PJ10) to be an output for a user LED.I've attempted to follow AN5361 "Getting started with projects based on dual-core STM32H7 microcontrollers in STM32CubeIDE" when configuring the debug profiles for the M7 project and M4 project while leaving the rest set to default.I've attached the logs to this post. Am I missing something when configuring the processor? Let me know if I need to add anymore information on my configuration.

Hello,I have a question about vscode with STM32 extension. I have setup a project with vscode and stm32 extension, and after compiler, it can do debug, and I can see the Global Variables on the VARIABLES window. as belowbut when I use vscode to do another design not with stm32 extension. I do the debug, but I cannot see the Global Variables on the VARIABLES window. as below, only Locals and Registers.Why no Global Variables? what is the difference among the 2 vscode?Thanks. 

On the STM32N6, half the ram is attached to this NPU RAM on it's own bus.  Are there any downsides to using this ram for non neural net applications. Use case     I would like to use the NPU ram for just frame buffers.   From what i can tell the memory is continues so i could put a memory buffer across potentially 2 different AXISRam sections.   Just asking if i would be able to use DMA operations with the DMA2d or the GPU2.5D engine.  Or if i could DMA peripheral like SPI or LTDC from these buffers Related posthttps://community.st.com/t5/stm32-mcus-products/npu-sram/m-p/808103#M279969   

In our project I use STM32H573VIT6 LDO uC. We have a problem with the PB14 pin. We use 3 pins for LED control (PB10, PB13 and PB14, see photo). The problem with the PB14 is that the LED lights up dimly without code initialization. If PB14 is initialized as Output, Open Drain, No Pullup-Pulldown, it lights up dimly in the OFF state and normally in the ON state. With Output Push-Pull initialization it works normally, i.e. in the OFF state the LED does not light up and in the ON state it lights up normally.  1. What could be the problem? 2. Should I use PB14 at all and is there a potential risk of later problems?

Hello everyone,I am trying to implement SBSFU (Secure Boot Secure Firmware Update) on NUCLEO-G474RE using STM32CubeExpansion_SBSFU_V2.7.0.Initially, everything was working fine and I was able to program the board normally.What I didI followed the SBSFU documentation and examples.While configuring SBSFU, I modified Option Bytes, specifically Write Protection (WRP) addresses to match the SBSFU memory layout.After applying the option bytes, the problem started.Current problemNow I cannot program or erase the MCU anymore.I get the following errors:1.In STM32CubeIDE'Launching SBSFU (1)' has encountered a problem.Failed to execute MI command:load ...\SBSFU.elfError finishing flash operation2. In STM32CubeProgrammerFull chip erase failsMass erase fails with error:Error: Mass erase operation failed. Please verify flash protection3.I also tried:Full chip eraseErase selected sectorsHardware reset / power cycle“Under reset” connection modeFactory reset via STM32CubeProgrammer→ All fail with

Hello, Happy new year !I create my custom board with STM32MP153C I try to boot but I have an issue. Starting systemd-udevd version 255.17^ root '/dev/disk/by-partuuid/e91c4e10-16e6-4c0e-bd0e-77becf4a3582' doesn't exist or does not contain a /dev. [ 14.557600] platform 5a006000.usbphyc: deferred probe pending [ 14.561992] platform 5800c000.usb: deferred probe pending [ 14.567427] platform 50001000.pwr: deferred probe pending [ 14.572778] platform 49000000.usb-otg: deferred probe pending [ 14.578559] amba 58005000.mmc: deferred probe pending [ 14.583629] platform 5800d000.usb: deferred probe pendingI change SD card I change some settings in device tree of kernel vqmmc-supply but I don't undestand in UBOOT I can explore my sd card Hit any key to stop autoboot: 0 STM32MP> mmc list STM32 SD/MMC: 0 (SD) STM32MP> mmc dev 0 switch to partitions #0, OK mmc0 is current device STM32MP> part list mmc 0 Partition Map for MMC device 0 -- Partition Type: EFI Part Start

Hi!I accedently used STPMIC25A instead of STPMIC25D when I want to boot A35 from SD card.According to AN5727 page 13, topic 4.1.8. it says that if the MP257 is going to boot from SD card, then the STPMIC25D must be used instead of STPMIC25A due to LDO7 and LDO8 are dedicated for 1.8/3.3V at initial boot.My question is: is there any soldering fix I could use to borrow voltage from another Buck/LDO output from STPMIC25A?My goal is just to boot TF-A. Suggestion:I use LDO2 for VDD_SD and VDDIO_SD. LDO2 boots at 3.3V. My SD-card might be UHS-I, but I'm guessing that it can run at low speed as well (3.3V pull-up). Edit 1:I cut of the traces from VDD_SD and VDDIO_SD and connected them to LDO2. Now I have 3.3V on the SD Card and its pull-up. But no signs of output of the USART6. The CLK of SDMMC1 has been started. I guess that the BootROM understand its purpose when telling 0b0001.

Hi,based on the ST example where the 640kB RAM is splitted into 2 * 320kB for secure/non-secure application, I want to change this to 32kB/608kB for secure/non-secure app. After modification of the linker files for the secure/non-secure app, the non-secure app runs into an hardfault right at the start. The error is that some ns access is done in secure area in SRAM1 (at address 0x2001f840).I first started the project on the STM32H563 eval board and simply copied the settings of MPU and GTZC over to the STM32H562. These settings are working on the STM32H563, so I can properly jump there into the non-secure app.Are there any difference in setting the memory areas for secure/non-secure/priviledged feature?Here are the settings.linkerfile non-secure:define symbol __ICFEDIT_region_RAM_start__ = 0x20008000;define symbol __ICFEDIT_region_RAM_end__ = 0x2009FFFF;linkerfile secure:define symbol __ICFEDIT_region_RAM_start__ = 0x30000000;define symbol __ICFEDIT_region_RAM_end__ = 0x30007FFF;v

Hello.How can we enable brown out for this processor and the brown out voltage?Thank you.

Hi, I'm checking the flammability specifications for MJD31CT4. I need to know if the molding material of this part is rated UL94 V-0. If it's not V-0, could you tell me what the official rating is? Any link to a supporting document would be much appreciated. Thanks!

Hi,I've tried to use high-pass filter in MLC in MEMS Studio, but the results are incorrect for first windows in each data file. I found that result is different from the one from Unico, but probably because Unico just drops first 2 windows from each file (which is an error itself). Signal is a quite constant noise (sample data and project is attached). These are F2_MEAN_ACC_Z_FILTER_1 & F3_MEAN_ACC_V_FILTER_2 from MEMS Studio and Unico. Decision tree generated based on these filters makes no sense. Values of these features read from FIFO looks ok. Looks like a bug in the app. Best regardsTomasz  

Hello everyone, I am currently working on a project using the STM32U5G9ZJT6Q mcu with USB UVC. For my setup, I am providing:  32 MHZ external clock to phy  144 MHZ system clock  In the documentation(TRM and CubeMX), the maximum external phy clock specified is 32 MHZ. However I need to achieve a 60 MHZ PHY Clock, which seems to be supported by the hardware but isn't explicitly listed in CubeMX or the reference manual. My questions are:  Is it possible to configure the external PHY Clock to run at 60 MHZ?  If so, does anyone have an example configuration or code snippet to achieve this? Any insights or suggestions would be greatly appreciated! Thank you in advance.

I'm trying to understand how the HDPL1 is calculated based on an OBK file.I have dumped the contents of HDPL1 / 0x0BDF0100 and can see that for a 16 length password, I have 96 bytes written, as follows0x0BFD0100 to 0x0BFD0120, unknown calc, how is this calculated?0x0BFD0120 to 0x0BFD0140 SHA-256 of password0x0BFD0140 to 0x0BFD0160 zeros

Hello, I would like to know the H264 VENC performance for the STM32N6 using the ST example: STM32Cube_FW_N6_V1.1.1/Projects/STM32N6570-DK/Applications/VENC/VENC_RTSP_ServerI have a hardware setup with a nucleo-n657x0-q + a ST B-CAMS-IMX camera module.Question 1: The example provided by the STM32CUBE_FW is for STM32N6570-DK. Will it also work for the nucleo-n657x0-q  Thank you.