Recently active topics

I have a design with a CR2032 cell connected to VBAT on the STM32WB5MM module. This was set up using CubeMX and there I enabled the LSE.In my code I am able to set the date and time and observe that it increments as expected. However, as soon I power the circuit down and back up the RTC is reset to the default. I have verified that VBAT is 3.1V.I have not yet tried the backup registers.What am I missing?

Hello everyone.I will use my MCU to acquire big amounts of analog data and transfer them to a host using UDP.As DTCM is 128K and SRAM1 is 368K I would like to store those data in SRAM1. As an exercice I’m trying to configure LwIP in SRAM1.I’ve followed many tutorials (MPU is, I beleive, set correctly) :with a cache protected region where all the LwIP data should be (normally it should only matter when I’ll run this program) I’ve also configure ETH to point to this area :And Lwip is also configured with this same areaAnd the flash script is also set :But when I compile the code directly after importing from cubeMX, I get :Data are not in SRAM1, they are in the DTCM.Am I missing something ? Do I have to set some options in the compiler ?Also I’m a bit surprised to see that 4 descriptors x 32 bits = 0xa0 (0d160) ??? Or F777 descriptors are 40 bits ?Thanks to anyone who will take some time to help me.Best regards 

i have a problem regarding the usage of the jpeg codec on a stm32n657x0h-q to decode images. the project also involves the transfer of such images over eth0 but for the sake of isolation of the problem i have bypassed mongoose. the problem seems to relate only to jpeg interrupts since the hpdma channel0, used to feed the periperal, is working.To develop this project i followed this example for the discovery kit.doing some debugging, i noticed that confr0 is being manipulated (i used a watchpoint), both jpeg_cr and jpeg_sr are being set, but confr1 has a strange behaviour: during Init_process, its registers are properly set, then, when manually halting execution in the cycle in main, the confr1 is set to all zeros. During initialization, registers are as follows:Confr1 has DE and HDR set to 0x1, the others to 0x0;cr has JCEN, EOCIE and HPDIE set to 0x1, the others to 0x0sr has IFTF, IFNFF and COF set to 0x1, the Others to 0x0COF in jpg_cr remains 0x1, as does the JCEN, thus the pheriper

Finally was able to test STM32CubeMX2 with a NUCLEO-C562RE board.Simple LED blinking project, and here's what I found out. Project bloat:STM32CubeMX2: 26.2 MB of generated data and when compiled 41.1 MB (NUCLEO-C562RE)STM32CubeMX: 4.6 MB generated and compiled 15.7 MB (NUCLEO-C031C6, same functionality) The old STM32CubeMX included only the HAL libraries actually used.The new one dumps everything in.That's a 5.7x increase for a blink LED. Missing Release configuration:Generated CMake project contains only Debug configuration - No Release.Interesting, because the official "MOOC STM32CubeMX2" video at 4:53 clearly shows both configurations.Either something changed or the video is misleading. Creating Release configuration manually requires editing multiple CMake files, including inside the cmake folder — supposedly overwritten on regeneration (in practice, changed only at project creation).Not trivial if you're not a CMake expert.I did it once manually, but then ended up using Claud

This forum has a new ‘code’ format option - for source code keywords in the middle of plain text:It works fine provided, as above, you type the whole text first, then go back to add formatting.But, if you apply the highlight at the very end of a post, there is no way to “escape” - the whole of the rest of the post will be formatted!

I’m trying to make the example LoRaWAN_End_Node_LBM] work on my nucleo-wl55jc1.For now i’ve just changed the DevEUI and AppKey in se-identity.h to match my chirpstack configuration.I can see the join request from my object and the join accept answer of the server but here is what i see on the log of the nucleo:LoRaWAN End Node LBMAPPLICATION_VERSION: V1.6.0MW_LORAWAN_VERSION: V1.1.0MW_RADIO_VERSION: V1.4.0L2_SPEC_VERSION: V1.0.4RP_SPEC_VERSION: V2-1.0.4Event received: RESET###### AppKEY: 2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C###### NwkKEY: 2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C###### DevEUI: CA:FE:BA:BE:DF:70:70:35###### AppEUI: 00:00:00:00:00:00:00:00###### DevAddr: DF:70:70:358s053:Add JOIN task8s053: TX MNG REQ time=00008053, final_time=000107888s055: Next TX on freq 868100000, DR 3 10s782: Payload: 00 00 00 00 00 00 00 00 00 35 70 70 DF BE BA FE CA 76 01 0A F0 D4 25 size: 23 995: TX DONE11s041: RX1 LoRa at 4957 ms freq:868100000, DR 3,

Hello ST Community,I am working on a BLDC motor control project and would like to use STM32 Motor Control SDK (MCSDK) Workbench to generate firmware.My Hardware ConfigurationMotor Type: BLDCMotor Voltage: 48VMCU: STM32F405RGT6IssueWhen creating a new project in MCSDK Workbench, I cannot find my exact board/MCU configuration in the board selection list. Since the STM32F405RGT6 board is not available in the predefined options, I am unable to proceed with the standard project generation workflow.QuestionsIs STM32F405RGT6 officially supported by MCSDK Workbench?If yes, how can I create a project for this MCU when it is not listed in the board selection menu?Is there a way to add a custom board definition?Where can I obtain the required board configuration/JSON file (if available)?Can an existing board configuration be modified to support STM32F405RGT6?If MCSDK does support this MCU, what is the recommended procedure for configuring:PWM generationCurrent sensingHall sensors / Sensorless con

Hello,I’m working on STM32U5 flash with tfm application using script “regression.sh” and “TFM_UPDATE.sh” of MB1551 example project in SBSFU. I lost the connection with the chip when I unchecked nSWBOOT0 in option bytes.Trust Zone : activatednBoot0 : checkednSWBOOT0 : uncheckedRDP : 0 So when we try a JTAG connection, we have this error.STM32CubeProgrammer Error connection Do you know a solution to regain connection with the STM32U5 ?Thanks for your attention,Kind regards,

System: STM32CubeIDE 2.2.0, Win11 Hi there,I am using the STM32WB09 and I am running the BLE Heartrate OTA Example via debugger.There is only one thing I don’t understand:When I create a release version of this example (= hex file) and execute a “run” command in STM32CubeIDE, the program is running until I powercycle the device. Then suddenly there seems to be an old application in Flash?But when I create a new project, execute the same “run” command the program remains also after powercycle.Here’s a log of my run command with the application which will be reverted back after power cycle: ST-LINK SN : 0044004E3137510E33333639ST-LINK FW : V3J17M11Board : STLINK-V3MINIVoltage : 3.30VSWD freq : 8000 KHzConnect mode: hwRstPulseReset mode : Software resetDevice ID : 0x032Revision ID : Rev ADevice name : STM32WB09NVM size : 512 KBytes (default)Device type : MCUDevice CPU : Cortex-M0BL Version : --Opening and parsing file: ST-LINK_GDB_server_a16044.srecMemory Programming ...File : ST-LINK_GDB

Dear Support Team, Kindly help to download the  EB Tresos Studio  basic version (the configurator), which is distributed free of charge by ST . Thanks,Madhav.

I have the STM32U595QJI6 installed on a custom PCB sharing its VDD supply line with other components, when the PCB is to go into standby, the command HAL_PWREx_EnterSHUTDOWNMode()  is used to put the STM32U595QJI6 into shutdown mode.The PCBs standby current is as expected, however, when the VDD supply line is at 3.3V, and the STM32U595QJI6 gets colder (locally cooling just the STM32U595QJI6 to 0℃) the standby current starts to increase roughly 3 times higher.When the VDD supply line is at 3V, this does not occur, and the standby current decreases as the temperature decreases as expected.When the PCB is running, the running current also decreases when it is cooled to 0℃ as expected, regardless of if the VDD supply line is 3V or 3.3VAll the pins are in an analog state, except the PWR_PUCRx and PWR_PDCRx , which are in a default state.What could be the cause of this current increase in shutdown mode, under the specific conditions of a 3.3V VDD supply line, and a temperature decrease to 0℃

Hello, I have been using the NUCLEO-C562RE for my evaluation and due to a mistake I fried the MCU that came with the board, I replaced the MCU with an MCU from the same series. The dev board came with C562RE and I replaced it with C552RE, but after that I am not able to use JLink to connect to the MCU.am I right in assuming that since the pinout of the two MCU’s are same, the MCU’s can be swapped and used ? 

Hello,We are designing a custom board using the STM32MP157FAC1 device and need to provide one USB 2.0 High-Speed port.Kindly refer to the attached block diagram snapshot and review the proposed USB interface architecture of our custom board.Please verify whether the implementation is correct and let us know if any modifications or additional recommendations are required for reliable USB 2.0 High-Speed operation.Regards,PS 

I encountered a potential bug in CubeMXs Configuration Checks for USBX.I am trying to configure USBX in standalone mode. When i try to increase the value of “USBX System Stack Size” to be higher than 1024 i get a warning that it needs to be lower than the USBX memory pool size, even when this is the case.Attached is a screenshot with example settings. To reproduce the error set USBX System Stack Size to 1025.The used MCU is a STM32U385CGTxBest regards, Cecil  

In stm32f0xx_hal.c:/** * @brief Initialize the MSP. * @retval None */__weak void HAL_MspInit(void){ /* NOTE : This function should not be modified, when the callback is needed, the HAL_MspInit could be implemented in the user file */} But this must not be implemented in a User file, because there is already an implementation generated by CubeMX in stm32f0xx_hal_msp.c:/** * Initializes the Global MSP. */void HAL_MspInit(void){ /* USER CODE BEGIN MspInit 0 */ /* USER CODE END MspInit 0 */ __HAL_RCC_SYSCFG_CLK_ENABLE(); __HAL_RCC_PWR_CLK_ENABLE(); /* System interrupt init*/ /* USER CODE BEGIN MspInit 1 */ /* USER CODE END MspInit 1 */} So implementing a HAL_MspInit() in a User file - as the comment in stm32f0xx_hal.c suggests - will cause a “multiple definition” Linker error!

Embedded veteran here, been involved in all manner of MCUs and MPUs professionally (especially safety-critical) but for personal use most of my prior experience has been with PIC16F and 18F (to save money obviously), of course those are only 8-bitters. I’m very interested in learning STM32 MCUs (gee they look ALMOST like DSPs except it’s single-cycle multiply not MAC and no simultaneous pointer adjustments etc.). Thing is my PIC experience has given me a pretty decent collection of chip initialization routines that I can adapt as necessary for small differences with peripheral features and such. My “inherent bias” is bare metal, no FreeRTOS, I understand I may be “going against the grain” a little but I want to get my hands on every nanosecond I may have coming. I don’t necessarily need this in C language, but I would like to get my hands on at least a very detailed list of all the HW registers that COULD need to be set, and the EXACT order in which this is “most safely accomplished”.

The RTC is connected by a switch to either VDD or VBAT.Voltage monitoring controls this switch to ensure that the transition occurs before VDD drops below the minimum voltage that the RTC circuitry requires.However, among several products such as STM32L4 and STM32G4, the reference manual states in the shutdown mode section:“The brownout reset (BOR) is not available in shutdown mode. No power voltage monitoring is possible in this mode, therefore the switch to the backup domain is not supported."It may appear that this voltage monitoring is disabled to reduce power consumption.But, when using the real-time clock (RTC) in shutdown mode, users may observe that the RTC that is powered from VDD continues to operate correctly after VDD is removed and restored, regardless of whether the microcontroller was placed in shutdown mode.This behavior can be reproduced by performing a test shared by our Super User ​@waclawek.jan in this product forum thread.Remove the 0R resistor R90 connecting VDD t

Hi all,I'm working on the STM32H747I-DISCO (CM7 core, bare-metal LwIP without RTOS, polling mode via MX_LWIP_Process()). Goal is simply to get the board to respond to ping from my PC over Ethernet.Hardware done:Solder bridge rework completed per UM2411 Table 5: SB8 closed / SB21 open (PC1 → ETH_MDC instead of mic DOUT), R87 open / SB17 closed (PE2 → ETH_nINT instead of mic CLK)Software config:ETH set to RMII mode in CubeMX, all 9 RMII pins showing green in Pinout view (PA1, PA2, PA7, PC1, PC4, PC5, PG11, PG12, PG13) LWIP middleware enabled, static IP configured (matching my PC's subnet), no DHCP USART3 used for debug output via Putty Everything runs on CM7 only; CM4 isn't touching ETH/LWIPSymptom:The code intermittently jumps into HardFault_Handler(void) — not on every run, which points to a timing/cache-related issue rather than a hard config error. When it doesn't crash, ping still doesn't get a reply./* Private user code ---------------------------------------------------------*//*

hi all, I am trying to flash + run a relocatable / runtime loadable model. The problem is that the inference results are wrong (they never change, no matter what the buffer contains when I start the inference). If I use the stai_model files from the AI Cube Studio, the model works correctly, but is not relocatable… Am aware of matching the address where I flash the network_rel.bin and generating the model. (← see URL) I am using these docs. (← see URL) I am enabling all AXISRAM3...6 I generate the model as follows:stedgeai.exe generate -m "path/to/model.tflite" --input-data-type uint8 --no-inputs-allocation --no-outputs-allocation --target stm32n6 --st-neural-art --reloc# final output something like this:+--------------------------+-------------------------------+------+------------+--------+| name (addr) | flags | foff | dst | size |+--------------------------+-------------------------------+------+------------+--------+| xSPI2 (0x20009332

I am using the STM32H7B3I-EVAL board. According to the user manual, both the ST-LINK Virtual COM Port and the RS-232 connector (CN9) use USART1 on PB14/PB15 in the default configuration.I have configured USART1 in asynchronous mode with:TX: PB14 RX: PB15 Baud rate: 115200 Hardware flow control: NoneThe ST-LINK VCP works correctly, and I can see the transmitted data on the PC. However, the RS-232 port on CN9 does not work.I am using a DTECH USB-to-RS232 cable connected to CN9.My questions are:Is any jumper or solder bridge configuration required to enable the RS-232 port, even when using PB14/PB15? Since both ST-LINK VCP and RS-232 share USART1, should the transmitted data appear on both interfaces simultaneously? Does CN9 require a straight-through RS-232 cable or a null-modem cable? Has anyone successfully used the RS-232 port on STM32H7B3I-EVAL with a USB-to-RS232 adapter?Any suggestions on what else I should check would be appreciated.

SummaryThis article explains the STM32C5 boot modes and how they are selected using the BOOT0 pin, BOOT_SEL and BOOT0 option bits, BOOTADD, BOOT_LOCK, and the EMPTY flag. It is based on the STM32C55x/C56x reference manual.IntroductionThe STM32C5 microcontroller series offers a flexible boot architecture that lets developers choose, secure, and update the firmware boot source with fine control. This flexibility is key to supporting reliable in-field firmware updates, secure production programming, and safe recovery during development and large-scale deployment. To design a robust system, it is important to understand how the device selects its boot source at reset. This article is based on the STM32C55x/C56x reference manual (RM0522), the STM32C56x datasheet, and application note AN2606.Summary Introduction 1. Boot sources and the BOOTADD option 2. Boot selection logic 3. EMPTY check mechanism 4. Securing the boot configuration 5. Embedded bootloader 5.1 Prerequisites 5.2 Connect to th

Hello,We have designed a custom RF module based on the STM32WL33, and one of ourcustomers is asking us to demonstrate that the RX sensitivity of our modulematches the values published in the datasheet:  - RX sensitivity @ 1% BER:      -132 dBm @ 300 bit/s, 433 MHz, OOK      -128 dBm @ 300 bit/s, 868 MHz, 2(G)FSK      -112 dBm @ 38.4 kbit/s, 868 MHz, 2(G)FSKTo validate this, we would like to reproduce the exact test conditions usingan official ST development board (e.g. NUCLEO-WL33) and theSTM32WL33 GUI, so the result is directly comparable to thedatasheet.In the GUI's "Radio settings" tab we can set: fc, DR (ksps), Fdev (kHz),CHF (channel filter bandwidth, kHz), modulation (OOK/2(G)FSK/4(G)FSK/ASK),Spread Factor, and Pout.Could you please help us with the following:1. What DR / Fdev / CHF / Spread Factor values did ST use internally to   characterize each of the three sensitivity points above? In particular:     - For -132 dBm @ 300 bit/s / 433 MHz / OOK: Under the test conditions of 1

Hello,We are using STM32 Motor Profiler to identify the parameters of an IPMSM motor, but the profiling process always stops at approximately 7% and reports a “Driver Protection” fault.Hardware configuration: - MCU board: NUCLEO-F446RE - Motor-control expansion board: X-NUCLEO-IHM09M2 - Power board: STEVAL-IPMM15B -Motor type: IPMSM  Thank you. 

Hello Experts,I am working on the STM32MP257F-EV1 board (MB1936 Var1.0 Rev.C-01) and following the official OpenSTDroid provisioning guide. I have successfully used flash-device(STM32CubeProgrammer v2.22.0 ) to flash the full eMMC starter image via DFU mode (FlashLayout_emmc_cm33tdcid.tsv). After that, I switched the boot mode from DFU to eMMC (M33-TD) and pressed USER2 + RESET to enter fastboot mode, as described in the documentation. However, instead of entering fastboot, the board goes into an infinite reboot loop.Observed behavior: Serial console (minicom) shows the following repeated sequence: iac exceptions: [159:128]=0x000001IAC exception ID: 128Ooops...[INF] System reset[INF] Reset reason: System reset (SYSRST) (0x94)[INF] init:pmic@33 STPMIC:20 V1.1[INF] welcome to MCUboot: TF-Mv2.1.3-4-g0a94de886[INF] cpu: STM32MP257FAI Rev.?[INF] board: stm32mp257f eval1[INF] board ID: MB1936 Var1.0 Rev.C-01[INF] dts: stm32mp257f-ev1-cm33tdcid-ostl-emmc-bl2.dts[INF] boot device: sdmmc2[INF]

The code I’ve written in main.c for a program on NUCLEO H7S3L8 works perfectly fine, but on NUCLEO F767ZI goes into hardfault mode when reaching line 455 “mfcc_compute(mfcc_left, audio_buffer_16bit_left, mfcc_feature_left);” (more precisely, inside this function, at line 263 “float last = (float)audio_data[0] / (1 << 15);”). Can someone tell me how to solve the problem? I’ve declared arrays static to not go into stack overflow. Can someone tell me how to solve the problem? (Int_mic_F7 is the project for NUCLEO F767ZI while audio.zip is the project for NUCLEO H7S3L8)