STM32 MCUs

Hello ST,We are using STM32H563RGT6 and want to run at 125℃ environment.We see in the datasheet as below.it seems that for STM32H563RGT6 with suffix 6, if we are using LDO bypass mode (using external 1.2V power supply for MCU Vcore), MCU works at VOS1 mode, it also can run at 125℃ environment.Is it right?Thanks.  

Hi,I have a problem with a custom board, where i can not enter bootloader, on some boards...I had a production where around 10% has this issue. (I did not see it on earlier production of 5pcs).The problem is the cube programmer will not enter bootloader mode.I use a autodirection rs485 tranciever (5V on FT pins) and it is working on many of the boards with no problem, also the in-application code works fine for modbus (also on the bootloader broken devices, after programming with ST-Link)I am using a FTDI USB to RS485 converter.The boot pin is held up by a hall sensor and inverter transistor, i have noticed these sensors has different startup time 50-100ms - therefore the MCU reset pin is controlled by a rather slow RC circuit, to ensure boot is high before reset is released. (this is a litle risky).However, i can see on the current consumption when it goes into application mode or assumed bootloader mode, as in bootloader mode the current stays much lower.I can see on the RX pin of th

Hello!I am using a 32.768 kHz TCXO (TG-3541CE) as the LSE to count the RTC.The MCU is an STM32L452RE.At room temperature, the RTC operates correctly, but at high temperatures (around 50 °C), the RTC stops.Strangely, once it has stopped, touching the MCU by finger causes the RTC to start running again.Suspecting an issue with the TCXO, I tried a different TCXO, but the same behavior occurred. When I added a 200 Ω damping resistor between the TCXO and the MCU, the RTC no longer stopped even when the temperature was raised to 60 °C.This seems to have solved the problem for now, but I am concerned about whether 200 Ω is an appropriate value and whether this is truly a fundamental solution.If you have any ideas about possible root causes or considerations, I would really appreciate your advice.

Hi,I am working with a custom board using an STM32N657X0H3Q and cannot for the life of me bring about a reset via the NRST pin.I have tried applying the workarounds from errata sheet ES0620 - Rev 3, sections 2.2.19 and 2.2.23, but my device still just hangs when any reset is attempted and needs a power cycle to recover.  In our setup:MCUboot and the application are both built as secure firmwarethe application runs from AXISRAM1 after RAM-loadSince it runs from AXISRAM1 which is where the errata recommends to place the First power-on reset flag, I instead decided to set the CORE_RESET_TYPE bit in the SYSCFG_CM55RSTCR register before each reset (in addition to resetting the clock switch control bitfields to their defaults). Does this type of setup have any implications regarding using the SYSRESETREQ bit to generate a software reset?  Thank you/ Silvia

Dear ST Support Team,Thank you for your suggestion to refer to the NX_UDP_Echo_Server example and compare configurations.I have tried to follow your recommendation, but I am still facing issues with Ethernet bring-up. Please find my observations and current status below.1. Current Status (My Application Logs)ETH HAL initialization is successfulPHY link is coming UPHowever, it is negotiating only at 10 Mbps (Full Duplex) instead of 100 MbpsMAC is configured accordingly (10M Full)Transmission is working (ARP packets are being sent successfully)Reception is not working at allKey observations from logs:ARP requests are transmitted:"ETH Tx OK len=42"But:No RX frames receivedRX descriptors remain unused (OWN bit = 0)Frames processed = 0Ping from PC is failing (Destination unreachable / timeout)2. Ping ResultPC Configuration:IP: 10.0.0.100Subnet: 255.255.255.0Result:No successful ping responseBoard keeps sending ARP requests but does not receive any response3. NX_UDP_Echo_Server Exa

Hi,I’m working on an STM based UI with multiple dynamic graph widgets on a single screen and running into a hard fault when scaling things up. Right now I have 5 graph widgets, each needing to plot around 700 data points dynamically. However, when I configure all 5 graphs with 700 points each, the screen crashes. The most stable setup I’ve managed so far is about 200 points per graph, anything beyond that consistently leads to a hard fault (which seems memory related).My goal is to reliably support 5 graphs × 700 points on the same screen. I’m trying to understand what could be causing the crash, whether it’s heap or stack limitations, frame buffer constraints, or something else in the graphics pipeline. It would be helpful to know how to narrow this down effectively.

Hello,at the moment i try to read correct accelerometer data with a STM32L010C6 Microcontroller from a accelerometer sensor BMA530. The connection is via I^2C (SDA and SCL) and i programm the Microcontroller with a ST-LINK V2. I took a code from gitHub Platform boschsensortec/BMA530_SensorAPI and changed it because in the common.c data i can´t use the coines commands because the STM32L010C6 needs STM32 HAL-Functions because Bosch use other Hardware as STMicroelectronics. The dev_addr2 = (0x18 << 1) see at https://sourcevu.sysprogs.com/stm32/HAL/symbols/HAL_I2C_Mem_Read#:~:text=SourceVu%20STM32%20Libraries%20and%20Samples,information%20for%20the%20specified%20I2Cand i got it from the BMA530 Datasheet - The default 7 bits I^2C address is 0x18.The Mem_addr = 0x18, i got it from the BMA530 Datasheet. 0x18->ACC_DATA_0 -> Read-only acc_x_7_0. In the BMA530 Datasheet at the Connection Diagram there are two resistors which i don´t have at my board. Could th

Hi, I have an USBPD sink application created with CubeMX that can be found here:https://github.com/ThiRom/H563NucleoUSBPDSink   The project can be build using cmake. If the project is build using Debug configuration, it works. But using Release it shows timeouts on requests. As you can see below during one millisecond the firmware sends 3 retries and a soft reset.  This problem can be seen with -O2 and -O3 option. It seems that the file usbpd_timersserver.c is not working correctly. I found that function: uint32_t USBPD_TIM_IsExpired(TIM_identifier Id) { uint32_t _expired = 1u; switch (Id) { case TIM_PORT0_CRC: _expired = TIMX_CHANNEL1_GETFLAG(TIMX); break; case TIM_PORT0_RETRY: _expired = TIMX_CHANNEL2_GETFLAG(TIMX); break; case TIM_PORT1_CRC: _expired = TIMX_CHANNEL3_GETFLAG(TIMX); break; case TIM_PORT1_RETRY: _expired = TIMX_CHANNEL4_GETFLAG(TIMX); break; default: break; } return _expired; }  When I change it to this: uint32_t USBPD_TIM_Is

Dear ST team.   I am testing UART of NUCLEO-WB09KE with the board [STM32WB09 Nucleo-64 board (MB1801 and MB2032)] I Set UART1 PIN PB4, PB4 with the source attached[100ms period tx send ]. I am checking CN3(23), CN4(35) but no signal shown. Is there anythn        

Hello everyone. I read that V8 will become available for OEM in Q1, but is there any estimations when V8 will become available for independent engineers or maybe even NUCLEO V8 will be released?

Hi all, i search properties for manage showed multinumber counters without not cool moving.For example num 123 121 111 . Align not help here .My idea is mark textarea as number aligned and render calculate widths from font for 0-9 and use it to convert showing as monospaced . Ofcourse font editor can change this , but better is switchable choice. Exist or is this doable in an TGFX version?

I'm back, and working with the stm32g070rb chip. I did prototyping on a nucleo board based on the same chip (split the st link and nucleo board), and wired the ST Link to the microcontroller with the following connections I used open-ocd for flashing code to the nucleo, and it worked flawlessly. Based on the wiring, I made the assumption that this'd translate directly when developing the PCB.   (picture of the PCB and the schematic) When I tried to make the same connections, and tried to flash, I'd get the following issue   ```bash Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWDInfo : clock speed 2000 kHzInfo : STLINK V2J31M21 (API v2) VID:PID 0483:374BInfo : Target voltage: 0.018873Error: target voltage may be too low for reliable debuggingError: init mode failed (unable to connect to

Hello,I am currently working with the STM32WBA65RI for BLE Direction Finding using connectionless mode. I would like to know if it is possible to use a low-power mode such as Standby with RTC, allowing the board to consume only a few nanoamps, then wake up periodically via the RTC, perform advertising for a defined period, and return to Standby mode.Could anyone provide guidance or share experience with this approach?Best regards.

Hello to whom this might concern,I was recently experimenting with STM32C011J4M for a small hobby project (I am trying to fit into a about coin size) and want to comunnicate with other chip over I2C. Due the size of the package I cannot use debugging to find core of the issue, so I used multimeter and legs 4 to 7 as signal outputs. I let CubeMx to generate signal configuration and try to use PA8 as output signal (overlaping with PA11[PA9]). The resulting behavior is that the physical leg 4 is stuck on 1.2V and output is not detectable. If I leave PA11 set as analog-nopull, but remove PA11 from 'HAL_SYSCFG_SetPinBinding' the output becomes readable. From rading on the other pins, I can see, that the communication doesn't work. The I2C is also on overlaping pins (default generation put the pins on PC14[leg 1] and PB6[leg8], which also overlaps with programming connections). I try to communicate with lp5817 and am wondering, if I should also remove pins PB7, PA14 and PC15 f

Hello, we have designed different boards with STM32G0B1.With our latest board we find that bootloader is not activated at power on, even when Boot0 is high roughly 1ms before MCU power rises (I can provide oscillogram), instead of bootloader, application is started.Of course nBOOT_SEL option is zero. After giving a reset, bootloader is correctly starting.The only difference to other boards might be MCU revision. We have that problem with MCUs marked 'Z'. With 'A' marking every board is working.Are there differences between MCU revisions regarding this?Is there a minimum time Boot0 has to be high before power on?Is reset required to activate bootloader (i.e. is it not guaranteed to start after power on? if yes, what are the differences between reset and power on, respectively where are they documented)?I did not find answers to the above in your documentation.Thank you in advance 

Hi,On a custom board I get the following message: Unable to detect DBGMCU Mailbox STwhen i run regression.bat.I did several test (provisionning, regression) before and i didn't notice any issuesDA with password and TZ disabledA program is running on my custom board but i cannot come back to OPEN state with the regression script.I tried with HRST wired to my STLINK with no success ...Any ideas ?Regards

The FSBL → Application jump is working fine, and the application is running properly from external flash.However, I am facing the following issues:Ethernet IssueEthernet initialization is successfulPHY link is UP, but speed is 10 Mbps (Full Duplex)Ping is not workingEthernet TX is failing continuouslyNo UDP data transmissionCamera IssueCamera (IMX335) is detected over I2CInitialization is successfulStreaming is startedBut no frame data is received (first frame timeout)Support RequiredHow to fix Ethernet bring-up (speed, ping, TX issue)Any example/project for Ethernet + UDP communicationGuidance for CSI/DCMIPP camera interface and how to read frame dataThe suggested VENC_RTSP_Server example contains only initialization; full configuration and setup details are not clear & .ioc also missingThese issues are blocking further progress. Kindly provide guidance or reference examples.

I am struggling with the keys in the new V1.5.0 LBM stack. Keys are read from NFC EEPROM and device is joining. After joining, I expect the stack to save the join and session keys in secure memory so the keys are deleted in EEPROM for security. After reset, the device does not join. How must this be handled.

Hi everyone,For my current project, I am working with an STM32WB55RGV. I am using all 256 KB of its RAM and running the ADC1 at a sample rate of 5.8 MSPS with 8-bit resolution.I am looking to migrate to a newer STM32 family that provides equivalent (or more) RAM and supports this high ADC performance. I plan to order some standalone chips and devkits for prototyping. Compact devkits would be a huge plus.During my research, I found the STM32H523CCT6 chip and the NUCLEO-H533RE devkit at a good price. Do you think this is the best choice for my needs? Also, are there other "mini" devkit options (like the Nucleo-32) that come with a large amount of RAM?Thanks in advance!

Hello. I'm working on a BLE  application that uses an STM WBA55 board and ThreadX. It was based on the St Threadx p2pServer example, The Sequencer is disabled. I'm using stmCubeIDE 1.19 and st_fw1.7 and i cannot migrate to new versions due to compatibility reasons.The main idea for the application is that the board initializes, advertizes 10-20 seconds for a connection, connects to a device like a phone pc, gets data from a sensor and transfers the data to the connected device. If no connection occurs or if the device is disconnected it should go into sleep/stop/standby mode until an EXTI interrupt from the user button is triggered. As of now the application is structured as follows:-- A main thread is in charge of initializing the rest of the threads (one thread for each type of sensor eg temp adc etc) and handle events like ble connection/disconnection and sleep/wake up requests.--Upon a sleep request a flag is set into an appropriate value. The rest of the threads inc

Hi I am trying to figure out these VCAP conections.From the datasheet I could look like they are internally connected together, for this reason could avoid routing these three pads together on my board.Can anybody confirm that is the case?Thank you.

Hi Community, I am using STM32H745I-DISCO board and generated a TouchGFX project and attempted to flash/debug from CubeIDE. The flashing process fails during the erase stage. Observed Errors Initially: “Error: failed to erase memory” After enabling external loader (without initialization): Erase still fails After enabling external loader with Initialize = true: “Failed to initialize external memory” “Error in initializing ST-LINK device” In CubeProgrammer: External flash is detected when selecting loader MT25TL01_STM32H745I-DISCO However: Mass erase fails Sector erase also fails Error message: “Sector erase operation has failed… please verify flash protection”  I am using STM32CubeIDE v1.18.1 and STM32CubeProgrammer: v2.16.x I have attached screenshots. Can someone help what could be the issue? Thanks.  

Hi all !I'm trying to write a driver for a LevelX system to talk to a QSPI chip over the OCTOSPI1 peripheral (STM32H563). I got the chip to respond to most commands, set it up in reading / protected mode.But, later, I've spotted an issue : I cannot sent over DMA two buffer, one after the other (as I did, two call to the Transmit_DMA function). Or, the LevelX API provide me two buffer, that may not be contigous. That's the issue, how to do ?I reminded that this chip has Linked List functionnality, which does match what I want (two DMA transfer from / to two different memory space, but, within one frame (Only one NCS being low).And, I cannot find a way to make them work...From a general perspective, the code is build like that :    if (xfer_size > GD25_DMA_THRESHOLD) {         /*          * Clean the semaphore, to ensure we restart from 0.          */         while (tx_semaphore_get(&

and how will the information be made available for non-EU residents ? 

Hello ST Community, I am an Engineering Undergraduate, currently working on an academic biomedical project developing a wearable ultrasonic vagus nerve stimulation (uVNS) patch to reduce stress and anxiety levels in my University, which came the guidelines from the Central Projects. We are transitioning from this product to a production-grade wearble system for precise ultrasound signal generation . The system is under the condition of LIFU (Low Intensity Focused Ultrasound Stimulation). Project Main Speciifcations : High-Performance MCU fro real-time MHz-range ultrasound signals.Multiple high-speed DACs/PWM for transducer controlLow-power operation and suitable for wearable patch type deviceCompatibility with DDS Signal generator, RF amplifier and Ultrasound transducersI have been exploring the NUCLEO-H743ZI2 for its excellent Cortex-M7 perfomance, but I have also learnt about the best features of NUCLEO-H75Z3I, STM32L476RG, NUCLEO-F446RE. I have a lot of confused in ch