Solved

Hi, I’m working on an STM32G491 MCU and facing an issue with GPIO PB9.In my project, I initialize PB9 as a digital output and try to set it HIGH, but the pin always stays LOW on the board.However, if I configure PB9 as input and toggle the pin externally in the same circuit, I can read HIGH and LOW correctly.Why would PB9 not go HIGH when configured as output? What could be the possible reasons or things to check?

I want to make a project on stm32f103, I write some code. When I want to add sd card support, I need to use spi interrrupt enable.But after I enable the global irq then the code is hang. Besides I debug the code with gdb, then I do ctrl + c , then I found the code hang in some nvic irq handler like WWDG_IRQHandler, UsageFault_Handler, USB_LP_CAN1_RX0_IRQHandler randomly.I try to disable all nvic irq and clear the pendings , But I found it's useless, the code as below int ret; LL_SPI_InitTypeDef spi_init; LL_GPIO_InitTypeDef gpio_instance = {0}; LL_GPIO_AF_Remap_SWJ_NOJTAG(); __HAL_RCC_SPI3_CLK_ENABLE(); __HAL_RCC_GPIOB_CLK_ENABLE(); __HAL_RCC_GPIOA_CLK_ENABLE(); /**SPI GPIO Configuration PA15 ------> SPI3_NSS PB3 ------> SPI3_CLK PB4 ------> SPI3_MISO PB5 ------> SPI3_MOSI */ gpio_instance.Pin = LL_GPIO_PIN_15; gpio_instance.Mode = LL_GPIO_MODE_ALTERNATE; gpio_instance.Speed = LL_GPIO_SPEED_FREQ_HIGH; LL_GPIO_Init(GPIOA, &gpio_instance); gpio_insta

Please help finding what diode is this, picture attached, the marking looks like 6BD, Thank you for any help provided.

Hello colleagues.My first post here...I have seen somewhere in youtube tha it is possible to provide URL to the specific Github location and use code from there as a library or some sort of included component. It has to be special file in Github serving as a "link" or index. Unfortunately, I forgot where I hve seen that and cannot find way to do that.  Any pointers ? Thanks.  

[VERSION]: MCWB v6.3.2[TOOL]: STM32CubeMX v6.13.0, STM32CubeIDE v1.11.5[BOARD]: STEVAL-PTOOL1V1[PROJECT]: STEVAL-PTOOL1V1_6S_SL and STEVAL-PTOOL1V1_6S_HLWhen I run the STEVAL-PTOOL1V1_6S_SL project generated by STM32CubeMX, the program loads and runs as expected.   When I run the STEVAL-PTOOL1V1_6S_HL (which is just the Hall-effect version instead of the sensorless SL version), the program loads and runs when the debugger is connected, but would not run properly after a power cycle, unless I reset the chip using NRST.  Both were tested on the same PCB.I thought the program wasn't booting, but determined that it actually was, but it just wasn't getting past some of the init functions (I think the MX_MotorControl_Init call).  If I add a delay (~1s) after the HAL_Init() and SystemClock_Config() calls, before the other peripheral init calls are made, the program runs normally after a reboot for the most part.  I still see som

I don't know what happened recently (or perhaps longer) with the ST website, but where can I find the ST products?

I want to change the selected toolchain for a project by clicking on "Setup STM32Cube project(s)" and selecting the desired toolchain and clicking save.I want to change from clang to gcc to test a few things.It keeps using the old toolchain (clang). Even if I delete the build folder.If I delete CMakePresets.json I get an error that the project requires a preset.If I modify CMakePresets.json I get the following warning message when building:[cmake] Manually-specified variables were not used by the project:[cmake] [cmake] CMAKE_TOOLCHAIN_FILE [cmake]In STM32CubeMX the toolchain option is greyed out.What's the proper way to change the tool chain?

This is a big problem for me, as I have thousands of products out there using the older BLE_OTA bootloaders, bootloaders which themselves are not updatable by OTA.   I have a custom phone app for iOS and Android that interfaces with these products and provides OTA updates.I was about to release an update to the product firmware via my phone app that incorporates several important fixes, but in regression testing this firmware, I found that older units could not successfully perform OTA updates using my new firmware (though units programmed with the updated bootloader could).   I tried many combinations to see what worked and what doesn't work, before narrowing the problem down: FUSBootloaderStackStack locationFirmware Git hashResult + notes01.23 plus  b87d60Worked like normal the second time.1.2.0.01.20.01.20.0.20x805A000b87d60No STM_OTA when commanded1.2.0.01.20.01.22.0.20x805C000b87d60No STM_OTA when commanded1.2.0.01.23 plus1.22.0.20x805C000b87d60W

Now I've been sitting here for 2 long day's and still haven't been able to solve the BUS-error problem. I'm logging with Kvaser USB CAN card so what I want to see right now is some healthy frames coming out from it, but no, only bus-errors, so I thought it was time to ask the community about it. I'm not a newbie in CAN and I've made an earlier project with STM32F302R8 which worked fine, but with this processor I seem to be stuck. The main.c attached is only me trying to get the interfaces up and running. What is strange is also the FDCAN Protocol status which doesn't seem to give me correct info, for example the "Activity status" which seems to be 8. Are there a friendly soul somewhere that could help me out? Intention is to get the classic CAN working and then Move over to CANFD. (With a different PC CAN interface of course) Thank you in advance, Johan [FDCAN] Classic 125 kbit/s up (PCLK1=64000000 Hz) [FDCAN] LEC=7, DLE=7, ACT=8, EP=0, Warn=0, BO=0, RxESI=0, RxBRS=0, RxFD=0, PE=0, TDC

Hello,I can not start STM32CubeIDE_2.0.0.I have the following error:D:\ProgramFiles\STMicroelectronics\STM32CubeIDE_2.0.0\STM32CubeIDE;;.C:\Users\Mich\.swt\lib\win32\x86_64\swt-win32-4966r5.dll: La procedure specifiee est introuvableCan't load library: C:\Users\Mich\.swt\lib\win32\x86_64\swt-win32.dllCan't load library: C:\Users\Mich\.swt\lib\win32\x86_64\swt.dllC:\Users\Mich\.swt\lib\win32\x86_64\swt-win32-4966r5.dll: La procedure specifiee est introuvableIn directory .swt\lib\win32\x86_64 there is only swt-win32-4966r5.dll file.Why the installer does not put these files?Do you have any correction please?Best regardsMichel

Hello ST Community,I am trying to run the ST67W6X_HTTPS_Client example project for the STM32-U575ZITX-Q Board, but with a U5A5ZJ-Q board instead (The .ioc file was changed to suit the board difference). I am getting a successfull initialization as well as a good scan and connection to the Wi-Fi network, however when trying to fetch data from the Openweather API i am getting a Socket connection error. I had suspicions that the failure was due to the GPDMA being configured differently if between the board im using and the one made for the project, however when in debug mode in never seems to go into a fault. Below is the serial output of the logs i am getting as well as the ioc file i have changed to suit the different board. Any help would be much appreciated!#### Welcome to ST67W6X Wi-Fi HTTPS Client Application ##### # build: 12:57:02 Nov 25 2025 --------------- Host info --------------- Host FW Version: 1.1.0 --------------- ST67W6X info ------------ ST67W6X MW Version: 1.1.1 AT Vers

I recently purchased some STMF303 boards for implementing a free pre-compiled HEX file.I received the boards with the STM32F303CCT6 chip, but the pre-compiled file was for the STM32F303CBT6 chip. The HEX loads but does not run on any 303CCT6.Are there significant compatibility differences between the CCT6 and CBT6 chips that would justify this?Could I have lost the purchased boards?Thank you.

Hi everyone,I am currently trying to use the ADC with DMA on my STM32H7S78-DK. To do so, I am following this guide: https://community.st.com/t5/stm32-mcus/stm32h7r-s-how-to-configure-an-adc-dma-transfer-in-circular-mode/ta-p/737149. I've made little changes to the code compared to the guide. I am attaching my project. The problem is that the program ends up in the Error_Handler() when the HAL_ADC_Start_DMA() (or the HAL_ADCEx_Calibration_Start()) function is executed.During the execution of the HAL_ADC_Start_DMA(), the ADC_Enable() function returns HAL_ERROR: /* Enable the ADC peripheral */ tmp_hal_status = ADC_Enable(hadc); /* Start conversion if ADC is effectively enabled */ if (tmp_hal_status == HAL_OK)Inside the ADC_Enable() function, the execution lead to this part (ADC_ENABLE_TIMEOUT limit reached): if ((HAL_GetTick() - tickstart) > ADC_ENABLE_TIMEOUT) { /* New check to avoid false timeout detection in case of preemption */ if (__

Hi,I’m trying to generate code for a dual-BLDC FOC setup using an STEVAL-IHM039V1 together with two X-NUCLEO-IHM08M1 boards in MC Workbench 6.4.1.For this combination you need an adapter board to go from the motor-control connector to the Morpho connector.As far as I understand, there is no dedicated adapter board for this configuration, but it looks like the X-NUCLEO-IHM09M2 could be used when using double-sided equal length male headers and stacking the IHM08M1 on top of it.However, MC Workbench doesn’t allow me to insert the adapter board between the two boards. When I click “Add adapter”, the page stays empty.Is there any straightforward way to still define this connection inside MC Workbench? Maybe by editing the adapter JSON file or another configuration file? Or will there still be compatibility issues later on when generating the code?Thanks.

Hello,I hope this is not a duplicate but I didn't find a similar issue.I'm developing for my company an Android app using the STSW-ST25SDK001 - Software Development Kit for ST25 Tags and Dynamic Tags (https://www.st.com/en/embedded-software/stsw-st25sdk001.html).To use your SDK i have to include two artifacts:st25sdk-1.13.0.jarst25_android_reader_interface-1.0.12-release.aar, specific for AndroidI see that the AAR includes an "application" tag in its AndroidManifest.xml, even if it's only a library and does not provide an Application class:<application android:allowBackup="true" android:label="@string/app_name" android:supportsRtl="true" ></application>This cause Gradle to complain and fail build with the following error: Manifest merger failed : Attribute application@allowBackup value=(false) from AndroidManifest.xml:7:9-36is also present at [st25_android_reader_interface-1.0.12-release.aar] AndroidManifest.xml:10:9-35 value=(true).Suggestion: add 'tools:replace="andr

stack:Zephyr on stm32n6 (nucleo_n657x0_q)When sending a buffer over sai via i2s_write data is written into the buffer.I expected the TX buffer to be treated as read-only and remain unchanged by the driver.It's only ever the first 2 numbers.Why is that?  Example code:int16_t tx_block_test[96] = {0}; In attachment a minimal version of a project that displays this issue.

I need clarification regarding the correct pinout for the specific part number I am designing with: STM32H7R7A8I6.I've noticed a discrepancy between the datasheet and the STM32CubeMX tool:Datasheet: The document shows two options for the UFBGA169 package: Figure 8 (UFBGA169 SMPS pinout) and Figure 10 (UFBGA169 GFx with SMPS pinout).STM32CubeMX: When I select the exact part number STM32H7R7A8I6 in Cube MX, it only displays the pin configuration that matches Figure 10 (UFBGA169 GFx with SMPS pinout).Can you please confirm if the ordering code STM32H7R7A8I6 guarantees the GFX pin configuration (Figure 10)? I need this confirmation to ensure my PCB design is correct before finalizing my purchase and manufacturing.

I am using STM32U083 MCU in a project that runs on a 3.6v Li-SOCL2 lithium thionyl chloride battery (OC voltage 3.65V / Nominal voltage at 1mA 3.6V).Currently I have used a LDO of 2.5v to power the MCU, but I was thinking if we can eliminate the LDO and directly power the MCU from the battery.Going through the datasheet I have found that the recommended input supply voltage is 1.55v-3.6v, and max is 4.0v, I have seen a mass produced device using the same battery directly on a STM32L053 MCU. I am expecting the same might be possible with U083 as well.Please suggest if this is okay or is there can be any potential issues that can happen. 

So i'm following along with this video* https://www.youtube.com/watch?v=usQ_f6Swpok&list=PLTJzs51NlEICI7ARAHOyUqMhTgJE0UFv0&index=5 I have the same* STM32N6-DK board This is my build command for the GPIO_IO_Toggle application.* /opt/st/stm32cubeide_1.18.1/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.linux64_2.2.100.202412061334/tools/bin/STM32_SigningTool_CLI -bin GPIO_IOToggle_FSBL.bin -nk -of 0x80000000 -t fsbl -o GPIO_IOToggle_FSBL-Trusted.bin -hv 2.3 -dump GPIO_IOToggle_FSBL-Trusted.bin I tried this on 2 different boards and the same thing happened Bellow is the results from trying to program it. My output from generating the signed bin

The correct declaration should be:void initialise_monitor_handles( void )This is not very important... but it generates warnings

Nucleo-WB55RGThe docs mention that it can be run off a button cell & also mention that the 3V3 pin can be used to power the board. Is it possible to run the board off a 3.7V LiPo battery? My application is pulling 7ms & using BLE 

I'm trying to find the cause of a hard fault in my code. The problem repeatedly appears after a few or more minutes after starting the  code, sometimes not at all, sometimes every time at close startup after enabling interrupts, and somethimes after a few seconds, as if it were dependent on the compilation. Somethimes watchdog re-runs code.CubeIDE, STM32G0 I tried debugger IDE and here apears something like this:   What does mean signal handler FFFFFFF1 and FFFFFF9 ? Maybe it helps me to find the problem.I dont use freertos, I dont use dynamic memory allocations. Only interrupts with 4 priority levels_Min_Heap_Size = 0x1000 ; /* required amount of heap */_Min_Stack_Size = 0x2000 ; /* required amount of stack */   

Hello AutoDevKit Support Team,I’m setting up an AEK-MCU-C4MINI1 board and I’m unable to get a working debug session through the board’s mini-USB (P2). I’ve read the user manual, followed the bring-up steps, and tried several configurations, but OpenOCD never manages to see the device over JTAG.SummaryExpected: OpenOCD starts, identifies the SPC58 device, and GDB halts at main().Actual: OpenOCD starts but repeatedly reports JTAG scan/IDCODE errors (“all ones”; IR capture 0x3F). GDB then disconnects.HardwareBoard: AEK-MCU-C4MINI1 (power to J2 = 12 V, S1 ON; D10 LED on)Connection: single mini-USB to P2 (no external probe connected to J3)Windows Device Manager shows:Ports (COM & LPT): AEK-MCU-C4MINI1 (Interface 1) (COMx)USB devices: AEK-MCU-C4MINI1 (Interface 0)USB IDs seen via Zadig: 0483:049A for both interfacesHost / ToolsWindows 11 x64AutoDevKit Studio 2.6.1OpenOCD bundled with AutoDevKit: 0.12.0+dev-00318-g0e98d766eGDB: ppc-freevle-eabi-gdb.exe (AutoDevKit toolchain)ProjectNew SPC

Hi ST Team,I am working on the STM32F746G-DISCO board.I have ported ThreadX with TouchGFX to this board, and I want to use the ThreadX + TouchGFX sources generated by STM32CubeIDE.However, I am facing build errors during compilation.Please find the attached photos/screenshots of the errors.I request your support in resolving this issue.If possible, please share any relevant documentation, guides, or reference links that explain how to properly integrate ThreadX with TouchGFX on this board.Thank you,

I am logged into my STM user account.I get to the download page for STM32CubeCLT (https://www.st.com/en/development-tools/stm32cubeclt.html#get-software) and I try to download the latest version for Windows.A dialog pops up with 'Log in to MyST', 'Create a MyST Account' and down in the corner 'Download as a Guest'.I click 'Log in to MyST' and the dialog just closes and no download starts.