STM32 MCUs

Hi all, I am trying to implement simple USB-FS communication on a BlueCoin board (STEVAL-BCNCS01V1). I am following the official STM tutorial on USB CDC and referencing the official SW package for BlueCoin. So, for USB I need PLL source from HSE clock: BlueCoin schematic shows that there is a crystal oscillator @16Mhz (NDK NX2520SA) installed directly on the board, so I configured RCC HSE as Crystal/Ceramic Resonator; the problem is that the function HAL_RCC_OscConfig(&RCC_OscInitStruct) in SystemClock_Config retrieves HAL_TIMEOUT as a result. Timeout value is default at 100ms. Clock configuration in STM32CubeMX is as suggested in the official USB tutorial: My current debug configuration has BlueCoin connected via SWD to a NUCLEO-G0B1RE, as suggested in UM2240 (see page 14). Could you please help me? Am I missing something? Thanks to anybody who can help!

I'm trying to compile a basic blinky application for the N6 and failing. I open the latest CubeIDE, import the GPIO_Toggle project (or any other one for that matter) and try to build. I get an error about no rule to make target. Please provide guidance on how to build the basic examples 13:47:52 **** Build of configuration Debug for project GPIO_InfiniteLedToggling_Init_FSBL **** make -j11 all make: *** No rule to make target '/Users/workspace/STM32CubeN6-git/Drivers/STM32N6xx_HAL_Driver/Src/stm32n6xx_ll_exti.c', needed by 'Drivers/STM32N6xx_HAL_Driver/stm32n6xx_ll_exti.o'. Stop. "make -j11 all" terminated with exit code 2. Build might be incomplete. 13:47:52 Build Failed. 1 errors, 0 warnings. (took 83ms) 

HelloCurrently I am working with NUCLEO-N657X0-Q by using STM32CubeIDE_2.1.1 STM32Cube_FW_N6_V1.3.0MxCube v6.17.0Trying to investigate and migrate CDC ACM feature in to the my own project. As basis I am using Ux_Device_CDC_ACM Example provided by ST as reference.It was discovered that Ux_Device_CDC_ACM example would not work properly after MxCube project regeneration -- it goes to the HardFault_Handler() at some point (not defined currently at which point)The investigation showed that the issue is connected with the Optimization level (MxCube updated STM32CubeIDE project files) just only for the one single source file: "stm32n6xx_hal_rcc_ex.c". If optimization level is set to "-O0" for the mentioned file -- HardFault_Handler() is observed. By changing it to the "-O3" -- the application works successfully.Could you please explain this "hidden" dependency, and what is the reason of this?

Hi all,I designed a custom STM32 board that powers up, but the firmware starts only after I manually press the reset button. Once reset is pressed, everything works normally.The clock source is an external crystal, and BOOT pins are configured with resistors.Questions:Should I suspect reset timing, clock startup, or BOOT pin state first?Would increasing reset delay with an RC network help?On the PCB, how close should crystal traces and load capacitors be placed to the MCU pins?

Hi ST Support Team,  #1 Demo provided by ST for STM32H7B3I-EVAL board is working on Windows Simulator.   But it is not working for Target (STM32H7B3I-EVAL board.)  #2 Does code generated by TouchGFX designer will run on Target board without any code changes on target (STM32H7B3I-EVAL).Please help me to resolve this issue.  Regards,Tejas

Hi,we are using the internal SMPS for core voltage generation.VDD, VBAT and VDD18AON are on 1.8V. My question is if I can also power up the other 1.8V lines (VDDSMPS, VDDA18USB, VDDA18CSI, VDDCSI,VDDA18ADC and VREF+) simulteanously with VDD, VBAT and VDD18AON or does this harm the device?So I would like to power up the 1.8V lines all together to get rid of an additional load switch on the PCB (for delaying the "late" 1.8V lines) due to space constraints. Is it possible? Thanks a lot!

Left commented out SFU_NO_SWAP and defined ENABLE_IMAGE_STATE_HANDLING in app_sfu.h, but when trying to build SECoreBin and SBSFU errors appear:/Middlewares/ST/STM32_Secure_Engine/Core/se_fwimg.h:47:61: error: unknown type name 'SE_FwStateTypeDef'Is there something I am missing? I selected AES-GCM crypto schemeI have followed https://www.st.com/resource/en/application_note/an5056-integration-guide-for-the-xcubesbsfu-stm32cube-expansion-package-stmicroelectronics.pdf (Chapter 8.5)  

HiI am trying to setup the NUCLEO-G491RE along with a X-NUCLEO-SNK1M1 to communicate with a USBC PD source.I have tried to follow the STM32StepByStep - Getting started with USB-Power Delivery Sink.STM32StepByStep:Getting started with USB-Power Delivery Sink - stm32mcuAfter generating the code and trying to build the project I get the following error:fatal error: gui_os_port.h: No such file or directorymake: *** [Utilities/GUI_INTERFACE/subdir.mk:25: Utilities/GUI_INTERFACE/gui_api.o] Error 1make: *** Waiting for unfinished jobs....I am unsure how to make this error go away, because as far as I understand it, the CubeMX code generator should give me all the necessary output files to make this simple sink project functional.I would like to get the GUI to work, such that I can verify the ability to change the power output of the USBC Source.I attached the generated files along with the CubeMX file.Thanks in advance.

Dear STMicroelectronics Community / Support Team,I hope you are doing well.I am currently working with the STM32N6 Discovery Kit and noticed that it uses an external Octal NOR flash device with the part number MX66UW1G45G. However, I have been unable to locate a public datasheet for this exact component.I was able to find datasheets for similar parts such as MX66U1G45G and MX66UM1G45G, but not for the “UW” variant used on the board. This has led to some confusion regarding the exact specifications, supported features, and command set of the device.I would appreciate your guidance on the following points:Is MX66UW1G45G a custom or internal part number used specifically for STM32 evaluation boards?Is there a publicly available datasheet for this device, or can it be shared upon request?Can MX66UM1G45G (or another publicly documented part) be considered a fully compatible equivalent for development purposes?Are there any specific differences (e.g., command set, timing, interface behavior)

Hi everyone,I am developing a project on the STM32N657X0H3Q where I need to implement a Dual CDC ACM composite device.I am following the "Standalone" implementation to avoid a full ThreadX dependency, as I plan to integrate this with a FreeRTOS project (using X-CUBE-FREERTOS).While looking at the USBX configuration in CubeMX and the ST Wiki (Introduction to USBX), I noticed the option USBD_COMPOSITE_USE_IAD ( As seen in the picture).If I enable USBD_COMPOSITE_USE_IAD , can I simply increase the number of CDC ACM class instances in CubeMX to 2?Does CubeMX automatically handle the IAD grouping for the second CDC instance, or do I need to manually adjust the interface descriptors in the generated ux_device_descriptors.c ?Can you provide an approach to configure this using MX? Which are all the files that should be edited to configure this.

During the initialization of STM32 UHS-I, it has an IO output of 3.3V. After initialization, it outputs at 1.8V. However, I noticed that the external voltage switch transceiver is powered at 1.8V on the host side. I'm afraid it might burn out the external voltage switch transceiver. Before initializing the SD card, can the SDMMC internally switch to a 1.8V control signal and directly input it to the external voltage switch transceiver? I noticed that the voltage switch transceiver A side recommended in <RM0433> is also powered at a fixed 1.8V. Is there another way to use the SDMMC

error updating STM32CubeIDE 2.1.1 see attachment.

 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?

Looking to add a 4 mic pdm array setup to livetune environment. Had questions on how deep into the environment we need to go for the changes. Is it just a matter of changing the # of channels for the sysIn, # of slots and active slots on the pdm interface? or do we need to drive deep as address the audio buffer as well. At one point I thought I read the audio buffer was allocated dynamically. We are just looking for a little guidance before we start changing things as there might be a simple way to achieve our goal vs us guessing and creating issues.

Hello ST Community,I’m working with the STM32 Nucleo-N657 board and need a way to execute my application after flashing to external memory without manually toggling the BOOT1 jumper on the board.What I’m Doing Now:BOOT1 jumper is set to HIGH for development (DEV boot mode)I have a simple LED blink application built with GPIO configured in the FSBL context The code runs as expected in DEV mode (debug mode of STM32CubeIDE)I then flashed the signed binary in external memory using STM32CubeProgrammer and External Memory loader for Nucleo-N6 board at address 0x70000000. Then, I switched BOOT-1 jumper to LOW and reset the board. The code runs as expected from external memory.Problem:I have N6 board connected to a remote PC and won’t always have physical access to toggle the BOOT1 jumper and press reset.I would like to know:Is there a programmatic or configuration-based way to run the program automatically after flashing, without needing to change the BOOT1 jumper man

Hello,I am using a STM32WL55 UFQFPN48 in an application. I am only using the high power output (up to +22 dBm) and only plan on transmitting with this device.I want to transmit in the 420-440 MHz range, but there does not seem to be any load-pull analysis data from within AN5457 which would give output impedance at this frequency. I can only find data for higher bands. Is this data found somewhere else? I would like to use it for simulation and calculation.Best

In CubeMX Version 6.17.0, for STM32G474RET6, HRTIM1, TIMA output2 configuration, set sources is forced to 0 cannot be changed to 1 and it is showing "Set Sources: nothing to set as Dead Time is enabled, Output2 signal is defined based on Output1 Configuration Set Sources" even if Dead time is kept disabled. This issue was not present on previous versions of CubeMX.

Hi,We were attempting to control a high-voltage BLDC motor using the EVSPIN32G06Q2S1 evaluation board. While following the Getting Started procedure described in UM3394, the board got  damaged during the power-up stage.Below are the steps we followed and the observations we made.Steps performedGenerated firmware using Motor Control Workbench.Flashed the firmware to the evaluation kit using the Nucleo board’s ST-Link.The digital section was powered using the 3.3 V supply from the ST-Link.Power-up observationsWhen only AC power was applied, the power stage turned ON, but the logic section was not powered.When VDD was supplied via ST-Link (3.3 V) and AC power was applied, the board was damaged:The 5 A fuse (F1) blew.The 0 Ω resistor (R29) burned.VDD and GND are now shorted.QuestionsCould someone clarify the correct power-up sequence for this board when using ST-Link for programming?What is the purpose of R29 shorting the logic ground and power ground ReferencesUser Manual: UM3394Eval

Dear, @halfhalf Post Edited by ST moderator to apply source code formatting and translate from Chinese to English to comply with the community rule:Best regards,Gyessine------------------------------------------------------------------------------------------------------------The STM32G474R datasheet does not mention the BOOT1 pin.If the BOOT0 pin of STM32G474R is set to high, where does the program start?If the BOOT0 pin is set to high and the BOOT1 pin is set to high, the program starts from SRAM. Is the program size limited by the size of SRAM? If a bootloader program and a main program are written, with the bootloader starting at address 0x20000000 and the main program starting at address 0x08000000, can this solve the issue of jumping from SRAM at 0x20000000 to flash memory at 0x08000000, so that the main program size is only limited by the size of flash memory?----------------------------------------------------------------------------------------------------------

Hi, everyone.I'm trying to configure I2S in a STM32H523CET. I'd like to activate MCLK signal, but I can't find how. I'd also like activate external clock input for I2s (AUDIOCLK signal). The CubeMX says:"Audio Clock Input is not available.To enable it, one of the following RCC Mode(s) or IP(s) have to be configured from the Pinout TAb:-EnableExtClockForSAI1"But again, I can't find where to activate that. 

For users having / wanting / needing their own VSCode C++ setup it would be very beneficial to have the STM32 debugging VSCode extensions not rely on the rest of the STM32 Cube extensions.Neither do I want nor do I need all of the bundle management, CMake replacement, code analysis and what not stuff the VSCode extensions are doing.Currently, st-cube-ide-stlink-gdbserver, st-cube-ide-debug-generic-gdbserver, st-cube-ide-debug-core (whatever I would really need) pull in the Core and, especially annoying and not really understandable for me, the CMake Support extension.I'd appreciate to have a debugging support extension that works well with any build + edit setup, just like cortex-debug. 

Hello, I am developing a project using the TCPP03 (X-NUCLEO-DRP1M1) and the ST USB-PD stack on an STM32G0 with FreeRTOS. I am concerned about the thread safety of the FLGn interrupt handling. In the standard BSP examples, the EXTI interrupt calls BSP_USBPD_PWR_EventCallback(). I2C Contention: Since BSP_USBPD_PWR_EventCallback() performs blocking I2C reads (ReadFlagRegister), what prevents the PE_Task or CAD_Task from attempting an I2C transaction at the same time? ISR Safety: In an RTOS environment, is it considered safe to perform blocking I2C calls inside the FLGn ISR, given the risk of HAL_BUSY or kernel priority issues? Best Practice: Does ST recommend a Deferred Interrupt pattern (e.g., using USBPD_DPM_CADTaskWakeUp) to move the I2C diagnostic logic out of the ISR and into a thread context?

Hi all! Thank you for taking time to assist me. I am attempting to make a composite USB Device on the NUCLEO-C562RE. I found the Middleware USBX examples and the core drivers exist in my toolchain at: STM32CubeC5/middleware/usbx However, I cannot seem to find the middleware configuration for USBX in STM32CubeMX2. My pack manager in the STM32CubeMX2 is set to this default value: "cube.packManager.cmsisPackRepositories": ["https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx"] Please let me know if I have missed anything or if you need further information from me to figure out the root issue. The examples, linked above, clearly auto generated the USBX files using the MX2 software, but I could not find the documentation that allowed me to generate those files. I would greatly appreciate it if someone could assist me with this.   EDIT: I saw this forum that says support isn't out until Q3. Does that mean I have to write the generated cod

Hello.I'm trying to work with the B-G431B-ESC1 board.I've assembled a prototype consisting of the specified board, a T-Motor MN3510-13 KV700 motor, a 13*4.4L propeller, and a 4S battery. I'm using MC SDK v6.4.1.At first glance, everything seems to be working fine. The motor starts with the specified propeller and runs fine up to about 7500 RPM.Then problems begin as the RPM increases. Depending on the battery's discharge level, i.e., the bus voltage, at certain RPMs the program seems to lose control of the motor. The motor revs up, and RPM, current, and power fluctuate. I understand that at such RPMs and under such a load, the modulation index is high and approaches 100%. I'm essentially starting to hit the limit. But this response doesn't satisfy me. Previously, I tested this motor with the same propeller and battery using the STEVAL-ESC001V1 board. I approached the same limit, but there were no oscillations. The motor simply stopped accelerating when it reached a certain RPM. For exa

I'm faced with connecting a (piano) keyboard to an MCU using a number of columns and a number of rows.The principle is shown in the attached photo.  I've read approaches where the coulmns are pulled to low while the rows are inputs that are sensed.Am I right that with the given arrangement it would be appropriate to set the columns to "HIGH" and sense the rows whether they are "HIGH"?  Excuses, forgot to say which MCU: it's an STM32F103C8T6 here.The diodes are common  practice to avoid so called "ghost hits" when multiple contacts are actuated.