Product forums

I've developed my own PCB using an STM32H723ZGT6 microcontroller.  I'd like to store data to a microSD card that's onboard, and I've designed it to use SDMMC2 for the better transmission rate.  I have no external pullup resistors, but I have enabled the internal pullup resistors (found to be 38kOhms using a multimeter) on each of the data lines and the CMD line.  I have ESD protection inline using the EMIF04-1005M8.  The bus is configured in 1-bit mode until successful connection is made.  Additionally, I've tried two different micro SD cards, a 32GB SanDisk, and an 8GB Gigastone micro SD card.  I run into issues in HAL_SD_Init, which is called in the MX_SDMMC2_SD_Init.  I've stepped through the code using the ST-Link and have found the issue to be in this loop: while (!__HAL_SD_GET_FLAG(hsd, SDMMC_FLAG_RXOVERR | SDMMC_FLAG_DCRCFAIL | SDMMC_FLAG_DTIMEOUT | SDMMC_FLAG_DATAEND)) { if (__HAL_SD_GET_FLAG(hsd, SDMMC_FLAG_RXFIFOHF)) { for (count = 0U;

Cross to Diodes Inc PN: SDM40E20LC-7 with long life cycle for new design.  

I get the build warning (which is treated as an error):```CompressedUnmappedFontCache.cpp:146:66: error: unused parameter 'glyphNode' [-Werror=unused-parameter] [build]   146 | void CompressedUnmappedFontCache::unableToCache(const GlyphNode* glyphNode, int byteSize)```This is easily fixed withvoid CompressedUnmappedFontCache::unableToCache(const GlyphNode* /*glyphNode*/, int /*byteSize*/) { while(1); }​But, it's generated code, so I have to make this fix every time a regenerate. This warning happens in both `CompressedUnmappedFontCache` and `CompressedFontCache`.

I am using the EVLSPIN32G0B1 demo board and the MC Workbench v6.4.1 software, and I would like to use the FOC control algorithm.More specifically, I would like to use the Hall sensors when the motor starts and operates at low speeds, and then switch to sensorless control at higher speeds.I have read that the library does not support automatic switching, so I will need to implement it manually in the code.How should I proceed?Thank you for your support.

Hi everyone!I have generated a code from CubeMX for USB-PD in bare-metal configuration like this:  Then I started testing the code and the function USBPD_PE_Init at this line: /* PE SET UP : Port 0 */ CHECK_PE_FUNCTION_CALL(USBPD_PE_Init(_port_index, (USBPD_SettingsTypeDef *)&DPM_Settings[_port_index], &DPM_Params[_port_index], &dpmCallbacks));returned false.I have looked in the assembler window and found out that some members of static const USBPD_PE_Callbacks dpmCallbacks = { USBPD_DPM_SetupNewPower, USBPD_DPM_HardReset, NULL, USBPD_DPM_Notification, USBPD_DPM_ExtendedMessageReceived, USBPD_DPM_GetDataInfo, USBPD_DPM_SetDataInfo, USBPD_DPM_EvaluateRequest, NULL, NULL, // Like this one!!! USBPD_PE_TaskWakeUp, #if defined(_VCONN_SUPPORT) USBPD_DPM_EvaluateVconnSwap, USBPD_DPM_PE_VconnPwr, #else NULL, NULL, #endif /* _VCONN_SUPPORT */ USBPD_DPM_EnterErrorRecovery, USBPD_DPM_EvaluateDataRoleSwap, USBPD_DPM_IsPowerReady };are not a

Hello,As a lot of people here, i'm trying to implement USB in standalone mode (bare metal, no OS used).I'm using NUCLEO-STM32WBA65RI board.CubeDE 1.19CubeMX 6.15.0 still can't make it work. I'm looking for help. I checked a lot of forum posts, a lot of github pages.I based myself on :https://github.com/STMicroelectronics/x-cube-azrtos-h7/blob/dev/usbx/Projects/NUCLEO-H723ZG/Applications/USBX/Ux_Device_CDC_ACM_Standalone/USBX/App/app_usbx_device.cand tried to implement the AzureRTOS USBX standalone versionHere is my Cube MX configuration :Clock USB :I only used X-CUBE-AZRTOS-WB and desactivated USBX : Using buffer <10*1024 would rise a memory error flag in ux_device_stack_initialize() : The rest is default configuration. Then USB_OTG_HS : Device_Only and :Then i generated the code,I added : if(MX_USBX_Device_Init() != HAL_OK) { for(;;); }And inside of it : /* USER CODE BEGIN MX_USBX_Device_Init1 */ USBX_APP_Device_Init(); /* USER CODE END MX_USBX_Device_Init1 */A

What could be the reason that configuring in CubeIDE SWV as enabled the MCU on debug flashes and stops responding? Flashing works fine both ways, SWO is connected. Time elapsed during verifying operation: 00:00:00.082Download verified successfullyTarget is not responding, retrying...Shutting down... Failed to read registers from targetError: Failed to set breakpoint at address: 0x80005c0.Error: Failed to set more breakpointsFailed to read all registers from targetExternal target MCU is STM32L412. STLink is upgraded to the latest version.Since flashing works, SWD is connected properly.MCU is configured as trace asynchronous Sw and there are no reconfiguration of SWD pins.  

I'm trying to create an empty project for the NUCLEO-U3C5ZI-Q using STM32CubeIDE v2.1.1 under MacOS. All available updates have been applied.I've used File/STM32 Project Create to create an STM32CubeIDE Empty Project for the NUCLEO-U3C5ZI-Q board (all settings at the defaults offered).The project is created, along with the startup and linker files, but there is no .ioc file.

Hello, I am using a firmware package with the System Workbench for STM32 IDE and would like to ask how I can configure a peripheral and integrate it into my code. Additionally, does it support code generation similar to STM32CubeMX? Thank you in advance!      

Trying to flash F1 and F0 series boards (not a clone, resoldered the MCU with a genuine from mouser) with L4 ST link V2.1, but having no success. Doing the basic CN2  headers out, CN3 VDD(with or without), SWCLK, GND, SWDIO. Spamming every option in CubeProgrammer to talk to the MCU with changing boot settings, doing resets before, while and after connecting, but nothing. L4 talks normally with the internal MCU. I measured MCU - STLink pin to pin resistances, everything seems ok with 22 ohm termination, the only problem i see is when connecting the 3.3V sense to the AIN_1 (CN3 1st pin), then i read in programmer 5.98V (VDD is not 5V, measured, stable 3.3V). In the schematic there is a voltage divider and when 3.3V ST_LINK is there, AIN is 1.65, which goes directly to MCU and shows in Programmer double of that. But by the same meaning, when connecting VDD i bypass with 3V (- schottky diode) and in the programmer get the double. Since its only sense voltage, it shouldnt be neccesary

The CubeMX suddenly can't generate some .h files such as stm32f103xb.h, core_cm3.h, stm32f1xx_hal_rcc.h ..., I tried to use legacy CubeMX to generate but still the same.How to fix it?Left picture is what it should look like ,and the right one is the wrong one.

Hello,Is this M93C46-A125 EEPROM available in WFDFPN8 (MF) package? Because according to the datasheet, the M93Cx6-A125 series exists in 3 packages (SO8, TSSOP8,WFDFPN8). but i founded just SO8, TSSOP8.     

Hi,I´m trying to migrate the example Application p2pServer (BLE) from the Nucleo board to a custom board with an STM32U575CI, but it fails initializing:#### Welcome to ST67W6X BLE P2P Server Application #####<\n># build: 17:52:14 Mar 18 2026<\n>--------------- Host info ---------------<\n>Host FW Version: 1.2.0<\n>[ERROR] [4000] [ST67W6XTask] (w61_at_sys.c:340) sem_if_ready not received<\n>[ERROR] [4000] [ST67W6XTask] (w61_at_common.c:375) sem_if_ready not received<\n>[ERROR] [4000] [ST67W6XTask] (w61_at_sys.c:312) Could not init Modem handler<\n>[ERROR] [4000] [ST67W6XTask] (main_app.c:975) [ERROR] in W6X_Init API<\n>[ERROR] [4000] [ST67W6XTask] (w6x_sys.c:115) W61 Init failed<\n>[ERROR] [4000] [ST67W6XTask] (main_app.c:401) Failed to initialize ST67W6X DriverAny idea what could be the problem?BestAchim

I have same error since days on differnt machines in different networks.While this is working:cube bundle list-online PS C:\git\nucleo-h753zi-canfd> cube bundle list-online Name : Platform Version --------------------------------------------------------------------- adoptium-jre : x86_64-windows ["21.0.8+9.st.2", "17.0.16+8.st.1", "17.0.15+6.st.1", "17.0.14+7.st.6", "17.0.14+7.st.5"] cmake : x86_64-windows ["4.2.3+st.1", "4.0.1+st.3"] cube-cmsis-scanner : x86_64-windows ["2.4.2", "2.2.1", "1.1.3", "1.1.0", "1.0.1"] cube-code-doc : all ["0.0.7+st.2", "0.0.6+st.2", "0.0.5+st.1", "0.0.3+st.1", "0.0.2+st.1"] cube-code-manifest : x86_64-windows ["1.1.3+st.1", "1.0.9+st.2", "1.0.6+st.1", "1.0.3+st.1", "1.0.1+st.1", "1.0.0+st.1"] cube-wrapper : x86_64-windows ["0.10.2", "0.8.3", "0.7.3"] gnu-gdb-for-stm32 : x86_64-windows ["14.3.1+st.2", "13.3.1+st.10", "13.3.1+st.9"] gnu-tools-for-stm32 : x86_64-windows ["14.3.1+st.2", "13.3.1+st.9", "13.3.1+st.8"] gnu-tools-for-stm32-13_3_1-d

Hello everyone!I am using stm32n6570-dk. My project has only FSBL and was generated using STM32CubeMX. I was able to run it in debug mode without issues. The code does not execute when flashed to external flash memory. I had to comment out "MX_ICACHE_Init();" for the code to run from external memory. I thought there may be a configuration issue from my side. So I ran the "Starter project" provided by STM located at "STM32CubeN6\Projects\STM32N6570-DK\Templates_Board". This code also runs fine in debug mode. It does not work when flashed to external memory without commenting out "MX_ICACHE_Init();".I expect the example code to work without modifications.  I figured out that the program does not reach the error handler and gets stuck in HAL_ICACHE_ConfigAssociativityMode(). This is when flashed to external memory.if (HAL_ICACHE_ConfigAssociativityMode(ICACHE_1WAY) != HAL_OK){Error_Handler();}Within HAL_ICACHE_ConfigAssociativityMode() it gets stuck in READ_B

Hi Community,Today you will provide the answers, and I will ask the questions!Looking at the statistics gathered by our tools (assuming customer consent given), we can see the huge popularity of designing software relying on an RTOS. FreeRTOS is widely used, and we assume that the adoption Azure ThreadX will also spread quickly.As CubeIDE tools guys, we have invested some effort in RTOS debug features. To quickly summarize the RTOS debug offer, let's make a list:Window > Show > View > Other > FreeRTOS / ThreadXProvides views to visualize kernel objects for the 2 RTOSesDebug config > Debugger > Enable RTOS ProxyWill allow the debugger to unwind and display the full call stack for ALL threads in the RTOS, not only the one currently in context!For Azure ThreadX CubeIDE 1.8.0 can also conveniently export trace logs to be visualized "offline" in Microsoft TraceX toolIn our view the RTOS support is now quite decent! ;)What is puzzling is the lack of feedback and bug reports

I am not able to view stm32N6 PSRAM @ 0x90000000 with IAR Memory view, it only shows --. And after I tried to access 0x90000000, the debugger seemed to hang up.I tried with STM32N6570-DK XPI_PSRAM_MemoryMapped project. I set a breakpoint at line 197 -- if (errorBuffer == 0) after it read/wrote PSRAM successfully. When it stopped at the breakpoint, I opened the memory view to check memory @0x90000000. It failed.If I did the similar with stm32CubeIDE, it worked fine.  Any idea why the IAR was not working?

Hi, I am tring to write data by the FDCAN bootloader of system memory, my target is STM32H563. Now, I can read the device ID, perform the mass erase command, but I can't write data to SRAM/Flash, the FDCAN bootloader doesn't response any CAN message after the Write_Memory command. Below picture is the CAN message log when I try to write 64 bytes data to flash at 0x0802_0000. I also check the 'Write_Unprotect' command, so the MCU is not write protect.Do I miss something have to do?Thank you.

I’m using a NUCLEO-H533RE and CLion as my development environment. Configuring and building my STM32 project works fine, but I haven’t been able to get debugging to work. I receive the following error:Error in initializing ST-LINK device.Reason: Unknown. Please check power and cabling to target.Using STM3CubeProgrammer I can connect with the board and did the full chip erase.The attached images show the current settings.Does anyone have any idea?

Hi,I’m working with a MYIR MYD-YA157C (STM32MP157AAC) board and I’m trying to restore a board using STM32CubeProgrammer (USB / DFU mode) with a FlashLayout TSV.The board is custom made , but the HW should not be a problemBut i am running into erorr: 16:47:55 : Download in Progress:16:47:56 : Error: failed to download Sector[0]16:47:56 : Error: failed to download the File16:47:56 : Error: Download partition 0x21 failed16:47:56 : Error: TSV flashing service failed16:47:56 : Disconnected from device. Little bit of a backgroundThe chip comes with preloaded yocto , and after trying to flash our distro we get this erorr  I tried the following thingsRemove everything from the EMMC - Nothing helpsChaning offsets - Did not helpUse UDF tool - Did not helpTried on different computer - Did not helpTried different cable  - Did not help It is very strange I attached logs from Cube programmer @Aimen1  Could somebody help us with some suggestions

Hello,I am using MEMS Studio (latest version) with the LSM6DSV320X to configure the Machine Learning Core with 2 decision trees.Steps I follow:Open MLC tool, set workspace via BrowseImport mlc_settings.json — data patterns load correctlyARFF Generation tab — add features, click Generate ARFF File — generates features.arff successfullyDecision Tree Generation tab — set 2 trees, assign labels to each treeClick Generate Decision TreeError:Unable to open features_DT0.arffI notice two problems happening:MEMS Studio generates features.arff but then looks for features_DT0.arff when generating 2 trees. With 1 tree it works fine.When the error occurs, the file features_DT0.arff (which I manually copied/created) gets deleted from the workspace folder.After the error, mlc_settings.json gets reset — the dectrees[].filename fields are cleared back to empty strings, and sensor settings revert to defaults.What works:1 decision tree generates successfully every timeWhat fails:2 decision trees — always

I am working with the STM32MP257F-DK using the official Starter Package. Suddenly, the board entered a state where several power rails are disabled. The ST-LINK LED (LD5) is blinking red slowly, and there is no HDMI output (0V on the rail) I have SSH access via USB OTG (usb0), but the system is in a "degraded" state.The ST-LINK is not recognized by the PC.HDMI monitor detects no signal. Diagnostic Data (Output of grep "" /sys/class/regulator/*/state): I have attached a screenshot, but here are the critical regulators currently in disabled state:regulator.11 (vdd3v3_usb) -> disabledregulator.12 (v5v_hdmi) -> disabledregulator.3 (vddio3) & regulator.4 (vddio4) -> disabledregulator.7 (vddcore) -> disabled (Surprisingly, since the CPU is running).Attempts to fix: Tried to enable them via sysfs: echo enabled > /sys/class/regulator/regulator.12/state -> Result: Permission denied.Tried to force it via I2C: i2cset -f -y 0 0x33 0x93 0x01 -> Result: Write

经我这三两天的多次调试，我终于找到了问题所在先说segger rtt viewer的工作方式首先，我将segger rtt的源码编译烧录到stm32mp257d_m33那里去。这时m33核的暂存会持有一个_segger_rtt结构体。然后我将这个结构体地址提供给segger rtt viewer，这时就会成功建立起通讯现在我通过segger rtt viewer向stm32mp257d_m33发送数据，这时jlink这个硬件工具就会通过swd直接操作暂存将数据写入到_segger_rtt结构体的下行缓冲区，按理会同时更新_segger_rtt结构体下行缓冲区的写位置WrOff而我在stm32mp257d_m33的用户代码逻辑是，将从swd收到的数据即刻原封不动的发还回去下面是我实际使用segger rtt viewer时的输入输出窗口的内容00> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=0< 55600> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=0< 5645600> WrOff=557, RdOff=557, HasData=000> WrOff=557, RdOff=557, HasData=0< 546546500> WrOff=557, RdOff=5

On an STM32H563, I am trying to write the OBkey1 data.I have successfully set the product state to provisioning (0x17) with: FLASH_OBProgramInitTypeDef optionBytes; HAL_FLASHEx_OBGetConfig(&optionBytes); HAL_FLASH_Unlock(); HAL_FLASH_OB_Unlock(); optionBytes.OptionType = OPTIONBYTE_PROD_STATE; optionBytes.ProductState = OB_PROD_STATE_PROVISIONING; HAL_FLASHEx_OBProgram(&optionBytes); HAL_FLASH_OB_Launch(); HAL_FLASH_OB_Lock();Now, when I try to write too OBKey1 with: uint32_t dataAddr = 0x20050000; memcpy ((void*)dataAddr, source, 0x60); RSSLIB_DataProvisioningConf_t * pConfig = (RSSLIB_DataProvisioningConf_t *)0x20050100; pConfig->pSource = (uint32_t*)dataAddr; pConfig->pDestination = (uint32_t*)0xffd0100; pConfig->Size = 0x60; pConfig->DoEncryption = 0xCACA0AA0U; pConfig->Crc = 0; HAL_FLASHEx_OBK_Unlock(); provisioningResult = RSSLIB_PFUNC->NSC.DataProvisioning(pConfig); HAL_FLASHEx_OBK_Lock();The call to DataProvisioning() causes

Hello,I am writing to seek advice on connecting an APMemory APS12808 OSPI memory to the STM32H723ZGT6 microcontroller.Initially, I attempted to adapt the code from this thread ( https://community.st.com/t5/stm32-mcus-products/stm32h7-octospi-mode-hyperbus-hyperram-access-and-delay-block/td-p/143237/page/2 )  from @Alex - APMemory  to the STM32H723ZGT6. You can find the result in the attached file `main_1.c`. With this configuration, read and write operations do work, but I am encountering issues with data mismatches/corruption.Subsequently, I tried to enable the Memory Mapped mode based on Application Note AN5050. This is where significant problems began I cannot get this mode to activate. The relevant code is in the attached file `main_2.c`.My specific questions are:1. Is there a known working example for enabling the Memory Mapped mode for this type of memory?2. Why does AN5050 not cover the MR (Mode Register) configuration and memory initialization sequence?