Solved

I'm looking at Rev 9 of the STM32L412xxx Datasheet, as linked on Digikey, and I'm having a hard time understanding the current consumption figures specified for the Low-power Run & Low-power Sleep modes on the MCU.  Per the table on pg.24 (shown below), the current draw is 83uA/MHz in LPRun mode, which is higher even than the normal Run mode up to 26MHz (range2), which doesn't make sense to me.  Further, the current draw in LPSleep mode is also 83uA/MHz, which suggests there's no power savings putting the MCU to sleep in Low-power mode?  Can somebody tell me what I'm missing here, or is this a typo and one or both of those figures are wrong?

Could I erase rtc backup registers with STM32CubeProgrammer ?

Is there a way to change the Horizontal front and backporch?   This is a addon to this question* https://community.st.com/t5/imaging-sensors/vd56g3-camera-change-the-frame-start-and-frame-end/m-p/888134#M6406@Jean_Poire 

hello,I encountered a problem while developing for stm32u585.I change the iwdg reload value by HAL_IWDG_Init(), and then HAL_PWR_EnterSTANDBYMode(), but the new reload value does not take effect: hiwdg.Instance = IWDG; hiwdg.Init.Prescaler = IWDG_PRESCALER_64; hiwdg.Init.Window = 4095; hiwdg.Init.Reload = 3600; hiwdg.Init.EWI = 0; HAL_IWDG_Init(&hiwdg); HAL_IWDG_Refresh(&hiwdg); HAL_Delay(300); //more than one downcount HAL_PWR_EnterSTANDBYMode();if delay before refresh, it seems work hiwdg.Instance = IWDG; hiwdg.Init.Prescaler = IWDG_PRESCALER_64; hiwdg.Init.Window = 4095; hiwdg.Init.Reload = 3600; hiwdg.Init.EWI = 0; HAL_IWDG_Init(&hiwdg); HAL_Delay(300); //more than one downcount HAL_IWDG_Refresh(&hiwdg); HAL_PWR_EnterSTANDBYMode();Is this the correct process ? If I want to ensure the modification is successful, what should I pay attention to

Label: MC Workbench[PN]: STM32G474RBT6 (Custom Board)[VERSION]: MCSDK 6.3.2[TOOL]: MC Workbench[DETAILS]: I am trying to create a new FOC project for a custom board driving a BLDC motor with Three Isolated Current Sensors (3-ICS). I am constantly getting the following UI error preventing me from creating the project: "It is not possible to create a motor control project with the FOC algorithm using the selected hardware. No proper path for motor control signals was found for the following mandatory features: - Current Sensing"However, when I check the .st_workbench/connectAlgo.log, the solver successfully finds a valid TripleADC route for my pins without any conflicts: DEBUG - CSConnect: ThreeICSCurrents TripleADCs processing start DEBUG - CSConnect: ThreeICSCurrents TripleADCs route: CURRENT_ICS_U PA0 ADC1_IN1 DEBUG - CSConnect: ThreeICSCurrents TripleADCs route: CURRENT_ICS_W PB12 ADC4_IN3 DEBUG - CSConnect: ThreeICSCurrents TripleADCs route: CURRENT_ICS_V PC4 ADC2_IN5 DEBUG - CSConn

ST10F276Z5T3 DC is newer than last shipment date.Last time Delivery 2022-03-11label DC is 23+

Title edited to clarify that this is about accessing a file located on a Host PC hello ST Community, I'm trying to open a binary file with the fopen function for a STM32L5 microcontroller, but it always gives me a null value. The code is like this: char filepath[256]; sprintf(filepath,"%s","C:\\fileBIN.bin"); FILE *file; file = fopen(filepath,"rb"); if(file == NULL) { printf("Error occurred opening file. \r\n"); } else { printf("File opened successfully. \r\n"); }   It always gives me a null value but the path exists and is correct. What's wrong? Thanks for supports  

Hello everyone,I want to share some issues and their fixes when migrating the .ioc file that was created for the Riverdi 10" STM32 display with template 4.1.0 to the newer version of CubeMX ver 1.16.0, STM32Cube FW_H7 V1.13.0.My environment is:Target: Riverdi STM32 10" Display RVT101HVSNWC00-B TouchGFX 4.26.0, CubeMX ver 1.16.0 STM32Cube FW_H7 V1.13.0, CubeIDE ver. 1.19.01. The build in CubeIDE fails with multiple errors searching for the "cmsis_os2.h" file.     Fix: Include paths are missing. Manually add the following include paths in both the Include Paths section of MCU GCC Compiler and MCU G++ Compiler (In CubeIDE)     (Riverdi_101STM32H7_1_6_CM7-->Properties-->C/C++ Build--> Settings-->MCU GCC Compiler-->Include Paths)            The paths to be included are:     " ../../../Drivers/CMSIS/RTOS2/Include" and  "../../../Drivers/CM

I am using the VL53L7CX to measure a black object. When the object is placed at a distance beyond 200 mm, the readings become very unstable and a large number of erroneous points appear. Additionally, when a highly reflective object enters the sensor’s field of view, the points that were previously showing valid data for the black object also start returning errors. Once I remove the highly reflective object, those points recover and start reporting correctly again. In the error state, the affected points return no data at all — it seems as if the sensor does not detect any object. However, the black object is still present in the scene. The only change is the removal of the white object, which causes the sensor data to change significantly. Has anyone encountered a similar issue? Could this be related to crosstalk, or are there specific configuration settings recommended for black targets at longer distances? Any advice would be greatly appreciated.

I cannot get USB DFU serial boot to work correctly with STM32CubeProgrammer.I keep getting the error "Please specify Binaries path" but there is no area to specify the binary path.Does anyone have any experience with USB serial boot on the STM32N6.

Hello. I need to find this component. Thank you 

Hi, I'm Dheeraj Sudan from the UK. I'm a software developer and also run a business with my wife Meenu Hinduja. I’m trying to create a new project in STM32CubeIDE, but I want to make sure I’m following the best approach. RegardsDheeraj Sudan and Meenu Hinduja 

When i try to add breakpoint, there is a cross sign on breakpoint symbol. So even if the code works, breakpoint never works.I try to add __asm("BKPT 0"); but it also did not work. I am not sure what is the problem.My CubeID version is: Version: 2.1.1Build: 28236_20260312_0043 (UTC)

 Hi,  I've implemented the antenna selection circuit as per AN6121 but I'm getting some strange behaviour. Background- I have designed and manfactured a test pcb using the ST25R3916.   On it I have 2 ST25R3916 chips, one with a single antenna connected and the other with 6 antennae and a multiplexer circuit as described in AN6121- Each has a header where I can connect it to my MCU host board so I can use the same software on both to compare- I have the single antenna chip working - it can detect tags correctly.  The chip connected to the multiplexer is not doing so well. I have attached the circuit diagram which i'm pretty sure matches the diagram in AN6121, paying careful attention to which way round the FETs are.  Note I've used the same fets as in the AN.  I'm assuming SW must be low to select the antenna?What i see, which i'm not expecting, is a large voltage drop across R1 in my diagram,  12v incoming drops to 7.6 vo

Hello everyone! I'm new to the NUCLEO-H743ZI2 board. I need help with two questions: 1) I can't find a description of the STLK backup port -CN2 anywhere. Can you tell me if I can use it to program other STM32 devices on other boards, and how? 2) Can anyone share the schematic for the H743ZI2 board?  

Hi,I would like to inquire whether the STM32C5 series supports ITTIA DB. Additionally, is it possible to use this library directly within CubeMX for development?

I would like to enable spread spectrum on the STM32H573RIT6.We are currently running on 250Mhz and at that frequency we have big peak which is 15dB above the limit, that's why I would be able to enable the spread spectrum. I looked into the STM32H7 example, so I am already aware and able to modify the PLL realtime. Now my question is how do I connect the DMA of the STM32H5 properly to a timer and a buffer to load the PLL. And also a question I have, what are good values for the PLL.  

Hi friends, Again I have come with a problem. Please see my code. PWM works as usual. But it is made to stop by resetting PC3 bit, PWM does not stop rather, it behaves randomly. Sometimes the PWM channels are driven high, driven low or PWM pulse is there. Many modifications has turned futile. Hence I seek your support. Regards ankhola Main,c /* MAIN.C file * * Copyright (c) 2002-2005 STMicroelectronics */ #include "stm8s.h" #include "ccp.h" void inv_on(void); void inv_off(void); void sw_state(void); unsigned int pwm_duty1 = 40; unsigned int pwm_duty2 = 50; unsigned int i=0; unsigned int duty; unsigned char toggle=0; unsigned char off_state; unsigned char on_state; unsigned const int table []= {0, 16, 32, 48, 64, 80, 96, 112, 127, 143, 159, 174, 190, 205, 220, 235, 250, 264, 279, 293, 307, 321, 335, 349, 362, 375, 388, 400, 413, 425, 437, 448, 460, 471, 481, 492, 502, 511, 521, 530, 539, 547, 555, 563, 570, 577, 584, 590, 596, 602, 607, 612, 616, 620, 623, 627, 630, 632, 634

We are designing a lens cover to be used with VL53L9CX. Can you share any more data on the FoV of the time of flight sensor? The attached data sheet on the part page is for a different sensor "VL53L7CX" is there a data sheet for the "...9CX" version? In "Description of the fields of view of STMicroelectronics' Time-of-Flight sensors" Sections 3.2 & 3.3 reference exclusion cones which are given in a product data sheet. Could you please share this file? Also, 3.3 references keep-out cones which can be shared by contacting support. Any additional information would be helpful to ensure our lens does not interfere with the required FoV. Thank you! 

Hello, I use STM32WB05KZ. Could you give me an example about how to store configuration data to NVM by aci_hal_write_config_data() function? - When I tried to store to 0x00 (I used static randow MAC address), it returns 0 but the data is lost when the chip is rebooted; - When I save to any other address (such as, 0x40), it always returns to 0x12. Thanks a lot.  

I have questions regarding estimated_reflectance and range_sigma in VL53L5 and L8The reflectance: how is it calculated? Is it R=signal_rate_per_spads*depth^2/K? the number_of sapds_enabled seems a useless parameter for a user? Can we know this calibrated constant K?The ambient_light has nothing to do with the R calculation?For these multi zone TOF, if we place a flat target in front of TOF, it shall give the same R. ST’ already does the internal compensation for the depth and for the angle of incidence. Right??  I can not find this kind of info in ST’s doc. Can only guess. If it has, please point out the Docs sourceThe range_sigma: for L5, if the resolution is 4 x 4, the readout is zero. I can read out  this parameter if it is 8 x8What is the default sigma_threshold for distance in L5? Is it the same for resolution  8x8 and 4 x4? Also, when I change this threshold, it is unclear if this threshold, e.g.,100mm shall multiply with a scale factor 128. Please confirm thatThan

I'm using the library here: https://github.com/stm32duino/VL53L1, and it seems to stop measuring around 3.2-3.5 meters. I may be wrong, but think that means that it is not using the histogram? I set it to long distance ranging mode.Here is my code:bool Sensor::ConfigureSensor(TOF &tofSensor) { Log.noticeln("Configuring [%s]", tofSensor.name); if (tofSensor.sensor_object == nullptr) { Log.fatal("No TOF sensor object initialized."); return false; } VL53L1_Error status; status = tofSensor.sensor_object->InitSensor(tofSensor.address); delay(10); if (status != VL53L1_ERROR_NONE) { Log.fatal("Failed to initialize %s. Status: %d. Halting.", tofSensor.name, status); while (1){;} return false; } Log.noticeln("%s address set to 0x%x", tofSensor.name, tofSensor.address); status = tofSensor.sensor_object->VL53L1_SetPresetMode(VL53L1_PRESETMODE_RANGING); delay(10); if (status != VL53L1_ERROR_NONE) { Log.errorln("Failed to set preset mode for %s", tofSen

Hello, I am using this sensor for a project where it is mounted on a cane to detect overhanging objects that could hit visually impaired people. This works fine indoors, but outdoors, when the ambient light is around or greater than 10k Lux—and keeping in mind the sensor is pointed upwards and hit directly by sunlight—it only catches obstacles when they are very close. I am currently using a 4x4 resolution with continuous ranging at 30Hz. My question is: is there a way to increase its efficiency? By efficiency, I mean increasing the detection distance through hardware, structural, or software solutions.

Hello, I have started evaluation of X-NUCLEO-ESE02A1 shield with NUCLEO-F401RE board, and used STM32CubeMX for project generation according to PDF inside X-CUBE-SAFEA1 package. However, I can't get any demo running, and both these generated demos, as well as my attempt, fail with error code 0x01 which maps to STSAFEA_COMMUNICATION_ERROR. I have tried putting jumpers for I2C lines pullup on the shield, jumpers P4 and P5, but it did not help. Then I read in the product User manual UM3579 about additional RST PIN so I tried also putting a jumper on P3 connector but still nothing. However then I traced it to PB5/D4 PIN which is actually not used and not advised to be initialized in the Getting started document. So my question is: Do I need to use this pin, and if so, how exactly should it be used, to enable communication with STSAFEA110? Everything other, related to I2C, USART, expansion package itself is enabled, project compiles and app shows logs after flashing to Nucleo,

Hello everyone,I'm working with an STM32L562E-DK board and testing the "TrustZoneEnabled" template included in the "STM32Cube_FW_L5_V1.6.0" package. The goal is to run the basic example that transitions from the secure to the unsecured zone, but I'm finding that, after following all the instructions in "README.txt" and compiling the project, the code gets stuck in the next function:static void NonSecure_Init(void) { funcptr_NS NonSecure_ResetHandler; SCB_NS->VTOR = VTOR_TABLE_NS_START_ADDR; /* Set non-secure main stack (MSP_NS) */ __TZ_set_MSP_NS((*(uint32_t *)VTOR_TABLE_NS_START_ADDR)); /* Get non-secure reset handler */ NonSecure_ResetHandler = (funcptr_NS)(*((uint32_t *)((VTOR_TABLE_NS_START_ADDR) + 4U))); /* Start non-secure state software application */ NonSecure_ResetHandler(); } Specifically on the "NonSecure_ResetHandler()"; or it doesn't even execute the no-secure part.Current option bytes configuration (verified with STM32CubeProgrammer):DBANK => Checke