Solved

I can't find Try.SRC or Try.SNK features for DRP devices in ST's USB C Power Delivery Stack (USBPD Core). Did I miss something?If it is not in the stack yet. Is ST planning to integrate this feature? What timeline are we looking at?Is it easy to implement? I guess I would just need to define Rp or Rd values after initial connection, but will that work with the rest of the stack or will it result in a mess?Has anyone tried or even achieved it? Is there a sample implementation?

Hello, I would like to have my account deleted. Please let me know how to do it. Thanks in advance. Regards,

Hello everyone! I'm working on a project using an STM32U575 microcontroller, and I need to manage an SD card (read, write, etc.) via SDIO in 1-bit mode, but without using FreeRTOS. I noticed that FatFs is not natively supported for this MCU in STM32CubeMX, and the recommended alternative is FileX, which is tightly integrated with FreeRTOS. However, due to project constraints, I cannot use an RTOS. So I'm trying to manually integrate FatFs into the project, but I'm running into some difficulties with the integration and compatibility. I was wondering: Has anyone already done this kind of integration? Is it possible to use FileX in standalone mode, without FreeRTOS? Do you have any examples, documentation, or code references for using FatFs or FileX standalone on STM32U5 series? Any help, advice, or shared experience would be greatly appreciated. Thank you in advance and have a great evening! Stefano

Hello everyone,I am working right now in a project involving some of ST products. I have my custom HW board with a STM32G0B1 MCU for a specific functionality. In order to work with it and be able to program and debug my project, I was using two main devices: A NUCLE0-G0B1RE development kit to get familiar with the MCU and make some SW tests, and also a few STLINK-V3MINIE programmers to program and debug my custom HW with the STM32G0B1. The problem comes when the ST-LINK device stopped working with a new version of my HW where the MCU is still the same and the debug circuit also remains the same. With the previous HW version it works well and I am able to program and debug it. I also tried with the ST-LINK integrated in the NUCLEO board with SWD connection and this ones DOES work with my new HW. I am quite confused right know because I don't understand which is exactly the problem here. It's not the first time that the ST-LINK V3MINIE is not working as expected. I also tried t

Hi,Im trying to configure SDMMC 4 wide bus with FATFS for SD card.Im not able to see any DMA options or Platform setting to set SD detect GPIO pin.am I missing something? I have refered through most of the documentation and tutorials online but with this MCU there is no options for DMA or Platform settings menu in .ioc configuration.Could you please help me with a procedure to setup SDMMC and FATFS for this MCU?Thanks    

Hello everyone,I'm new to STM32 and currently working on a USB CDC (Virtual COM Port) project using STM32CubeMX with the following setup:MCUs/Boards: STM32F103C8T6 and Nucleo-F334R8Toolchain / IDE: MDK-ARM (Keil µVision)STM32CubeMX versions tested: 6.14.1 and 6.12.1I configured the USB peripheral in Device Only mode and enabled the Communication Device Class (CDC) in the USB Device middleware settings. I also configured the required USB pins (PA11 as USB_DM and PA12 as USB_DP) and set the USB clock source properly to ensure 48 MHz operation.However, after generating the project, several key USB middleware source files are missing, such as:usbd_core.cusbd_ctlreq.cusbd_ioreq.cusbd_cdc.c(and sometimes also usbd_cdc_if.c)Because of this, the code fails to compile due to missing function references.What I’ve Tried:Verified USB pins (PA11, PA12) are configuredMode is set to Device_OnlyCDC class is selected in middlewareUSB clock is 48 MHz via PLLEnabled code generation options like "Delete p

I would like to make a basic application using BLE (to turn on an LED). I’m using the WB05KN1 shield and my application runs on the U545. I would like to know if it’s possible to carry out this project, if they are compatible, and if you know where I can find example codes because I can only find examples with Zephyr.ephyr.

你好，近期我在使用NanoEdge AI Studio实现异常检测功能，基于三轴加速度计的数据实现。我出现了以下问题：1.我使用的最新版本5.0.2，在benchmark界面训练模型后，表格Best Library Result 中异常数据的结果为零，就是在表格的底部。但我生成代码需要的文件后运用到工程中其相似度一直输出为91%，即使我大幅度的改变加速度计的值也仍然时91%。2.在有一次训练时，表格Best Library Result 中异常数据的结果不为零了，大概为68%。我生成需要的额NanoEdge AI.h和library.a以及knowledge.h生成后运用到keil工程中发现能够正常进行学习，并且也可不学习使用knowledge.h的这个数据集进行检测相似度，结果较为明显。只是原本的异常数据其相似度对应的也为68%。3.我的疑惑在于，对应的模型训练不应该异常数据接近为零，正常数据接近一百吗，可我似乎于认为的不一样。并且同样的数据进行第一次训练的结果可能异常数据不为零，但后面几次训练后一直为零。导致的结果就是，训练结果异常数据为零的模型，在使用官方给的先进行学习一段时间，在进行异常检测运行效果是错误的，相似度一直输出为一个固定值，比如91%。并且运行不事先学习，利用knowledge这个数组作为学习数据，运行结果也是不正确的，但是训练结果异常数据不为零的就可正常运行。但这个结果也不是一直会出现的，偶尔出现。我的数据上传使用的是USB串口上传（USB转TTL、或者蓝牙串口） 以下为代码（省略了部分）#include “NanoEdgeAI.h”#include “knowledge.h”#define LEARNING_ITERATIONS 30浮点数 input_user_buffer[DATA_INPUT_USER * AXIS_NUMBER];输入值的缓冲区无效 SystemClock_Config（void）;静态 void MPU_Config（void）;void fill_buffer（float input_buffer[]）{/* 用户开始 */float acc_mg[3]; // 临时存储单个样本的X/Y/Z数据uint16_t samples_collected = 0;uint32_t last_tick = HAL_

Hello, please help, I can’t identify the SMD component in picture.

In HAL_DCMI_Init() of stm32f4xx_hal_dcmi.c, HAL_DCMI_MspInit() gets called twice.  The 2nd call should be deleted from the source.  See lines 216 and 218.

Hi ST membersI am using the ST25R95, following the application note and matching tool to define LC components for EMC filter and matching circuit. the function test is good, but I have a high pulse at 3rd harmonics 40.8MHz and 7th 94.92MHz, do you have similar case happens with emission issue? have any suggestion？ thanks！

Hello forum,i'm working with a custom design where a STM32H743XIH6 is provided on the board along with an USB connection. I'm actually dealing with an issue on USB firmware programming using STM32CubeProgrammer v2.19.0 (up-to-date, but same issue occur with previous versions).When downloading firmware the following error occurs:10:34:53 : STM32CubeProgrammer API v2.19.0 | Windows-64Bits 10:34:59 : UR connection mode is defined with the HWrst reset mode10:34:59 : USB speed : Full Speed (12MBit/s)10:34:59 : Manuf. ID : STMicroelectronics10:34:59 : Product ID : DFU in FS Mode10:34:59 : SN : 20036450000010:34:59 : DFU protocol: 1.110:34:59 : Board : --10:34:59 : Device ID : 0x045010:34:59 : UPLOADING OPTION BYTES DATA ...10:34:59 : Bank : 0x0010:34:59 : Address : 0x5200201c10:34:59 : Size : 308 Bytes10:34:59 : UPLOADING ...10:34:59 : Size : 1024 Bytes10:34:59 : Address : 0x800000010:34:59 : Read progress:10:34:59 : Data read successfully10:34:59 : Time elapsed during the read operation is:

Hi, SPI CR2 is missing from RM (RM0383 Rev 3) table in 20.5.10 SPI register map (page 610). Please update.   Best,Alessandro

I recently installed STM32CubeIDE on a new computer for the first time. Starting out my first project, and I immediately run into an issue that makes the MX portion basically completely un-usable. The problem is that when I want to change the configuration of a pin I simply... can't.For example, if I want to change PA2 (USART2_TX) Maximum output speed from low to high, before I would simply click on "low" and a small menu would pop-up that would let me change it to "high", and now that is just gone.All I can do is change the user label in the pinout view (which will make the configuration refresh and I will see the user label appear) but for example, I cannot simply click on User Label in the configuration window and type something in, it just wont let me do that.I have sure everything is running on the latest version; the IDE and all associated packages, as well as all my drivers and windows itself. I have tried completely uninstalling and re-installing CubeIDE, and when I say complet

I am trying to build a DCDC Converter with following conditionsVin: 400~600VDCVout: 12~15VDC(Isolation is not required)Current Rating: 100mA~300mA(Not really stricted)I can see DC application simple schematic at the first page of the datasheet for ViperPlus Family.However, every examples are AC Inputs with Full bridge Rectifiers.May I just skip the rectifiers use it for DC Application?I guess L,C are for noise filtering.All application notes are for AC DC Converter.  

I've been working on a board bring up of a STM32U5G7 for a few days following https://support.touchgfx.com/docs/development/board-bring-up/board-introductionWhile the board is able to display the framebuffer and change colours, etc, when I finally complete the bring up process to include TouchGFX generation and TouchGFXDesigner, the project does not run out of the box and it's difficult to debug and tell what's missing.  Instead, since the demos and examples from the STM32U5G9J-DK2 easily compile/run and that there are only a few differences between my board and the kit, would it be possible to modify/copy a DK based application to run on my board? The differences are:- MCU package U5G9 144pin vs U5G7 100pin- external flash not used I'd be happy to make sure the MCU pins are used correct and clock config, etc. but this way at least I know I'm not missing anything. 

I am connecting a TCP/IP stack to the HAL_ETH driver of an STM32F7xx. I am using https://github.com/STMicroelectronics/STM32CubeF7/blob/master/Projects/STM32F767ZI-Nucleo/Applications/LwIP/LwIP_HTTP_Server_Netconn_RTOS/Src/ethernetif.c as a starting point. I see that low_level_output() calls HAL_ETH_ReleaseTxPacket() only if the ethernet driver runs out of DMA descriptors:  do { if(HAL_ETH_Transmit_IT(&EthHandle, &TxConfig) == HAL_OK) { errval = ERR_OK; } else { if(HAL_ETH_GetError(&EthHandle) & HAL_ETH_ERROR_BUSY) { /* Wait for descriptors to become available */ osSemaphoreWait( TxPktSemaphore, ETHIF_TX_TIMEOUT); HAL_ETH_ReleaseTxPacket(&EthHandle); errval = ERR_BUF; } else { /* Other error */ pbuf_free(p); errval = ERR_IF; } } }while(errval == ERR_BUF); It seems like HAL_ETH_ReleaseTxPacket() will then deallocate all completed buffers and block if none of the scheduled buffers has been completed yet. So far so good. But:I

Hi everyone,I'm building a watchdog application on the STM32 NUCLEO-U385RG-Q using the Arduino IDE and the IWatchdog library. Since the library doesn’t support early interrupt callbacks, I modified it by adding some LL code (afterLL_IWDG_SetReloadCounter()) inside IWatchdogClass::set() as shown below. However, the early interrupt doesn’t trigger. Am I missing something, like NVIC config or enabling the interrupt line? LL_IWDG_SetEwiTime(IWDG, (uint32_t)EWITimeout); LL_IWDG_EnableIT_EWI(IWDG); Arduino Code#include <IWatchdog.h> extern "C"{ #include <stm32u3xx_ll_iwdg.h> #include <stm32u3xx.h> } extern "C" void IWDG_IRQHandler (void){ Serial.println("Wake up Interrupt"); } void setup(){ Serial.begin(115200); __enable_irq(); // Enables global interrupts HAL_NVIC_SetPriority(IWDG_IRQn, 0, 0); HAL_NVIC_EnableIRQ(IWDG_IRQn); IWatchdog.begin(10000000); }After further debugging, I found that EWI timeout is not being set if EWI interrupt is enabled and when&nb

Trying to get MD5 hash acceleration working on the Nucleo-H563Zi. I can get SHA1 hash engine to work via bootstrapping a project via CubeMX, but for some reason MD5 is not a selectable option for the hashing algorithm in CubeMX.  All other algorithms can be configured and work, but MD5 is not an option. The Datasheet for the STM32H562/3 says that the Crypto engine offers a MD5 hash, but I can't seem to configure it via CubeMX or by updating the generated code in hash.c to select the MD5 algorithm within MX_Hash_Init(). Is MD5 not supported on the H5?  There are no MD5 examples in the github example repo despite the datasheet claiming the crypto/hash accelerator supports MD5.

Hi!I have an electric scooter that's a few years old, and I'm trying to find out if it's possible to use its charger for LiFePO4 batteries. The scooter's original batteries are two lead-acid units connected in series (24V total)The charger has the reference LT01. I opened the charger and noticed that the charging control IC is from ST. I couldn’t clearly make out the part number, but I believe it reads "324 MZNQ910".The charger specifies that it uses equal voltage charge and floating charge on its case. That is, the IC controls the charging up to a higher voltage level to desulfate the lead-acid batteries. After that, the charger maintains a less more stable floating voltage until it is disconnected from the scooter.LiFePO4 batteries require CC/CV charging, constant current and then constant voltage once the current drops near the end of the cycle. I want to know whether your IC also performs this type of charging so I can determine if it's suitable to use with 2 12.8V LiFePO4 batterie

We appreciate the example in the STM32Cube repository, located at STM32Cube_FW_H5_V1.1.1\Projects\NUCLEO\H563ZI\Examples\FLASH\FLASH_OBK_EraseProgram. We are looking to modify the product state and write the .obk file directly from the firmware, and we believe your example is a great starting point.STM has detailed a procedure for writing to the alternate OBK sector using the non-secure FLASH_NSOBKCFGR register. The addressing for the OBK sector is set to the base address 0x0BFD0000 (non-secure) rather than 0x0FFD0000 (secure).However, we noticed that the STM32CubeProgrammer employs secure base addressing for the OBK sector, while your example uses non-secure addressing. This difference is essential for our understanding. Could you please explain the reason for using non-secure addressing in your example?According to Figure 32, "Swap Workflow", of the Reference Manual, the role of the current OBK sector and the alternate OBK sector is interchanged after the Swap operation. Thus, w

 Hello ST Community,I'm currently trying to implement a simple function: turning the RF field ON and OFF for a desired duration using the X-NUCLEO-NFC08A1 board.Here is my current setup and progress:I’m using the STM32F401RE Nucleo board as the host MCU.I've referred to UM3007 (Getting Started with X-NUCLEO-NFC08A1) and “Getting started with the X-CUBE-NFC6” documents.I have installed the required X-CUBE-NFC6 software pack in STM32CubeIDE.SPI1 is configured as per the documentation in .ioc .However, after code generation, no SPI-related code is generated (e.g., no MX_SPI1_Init() function).In the .ioc file's System View, the Middleware section shows nothing loaded — I suspect this may be part of the issue.Overall, it feels like the NFC board is not properly interfacing with the MCU, but I can’t identify what’s wrong.Additionally, my goal is only to generate the 13.56 MHz RF field with desired strength and timing — no tag detection or NDEF handling is needed. From the datasheet, I u

Moved from MPUs section - STM32L100 is an MCU, not an MPUI compare this my layout board (with outer st-linkv2 connected), and stm32l100c disco.stm32l100c disco does not have such a question. It will show "Error 57: Illegal Address(0x8000000)".And I disable download to flash, this error is disappeared.However, the program runs in 0x1ffffxxxx,not flash (0x8000000). It won't run my codes (no flash could be found?). I could not run my codes after download, either.But I am totally sure these codes could be executed in stm32l100c disco.And help?   

I've been on an adventure trying to get my first CubeMX/STM32 project off the ground.  Here's as much context as I can give for my debugging process, and hopefully someone can spot what I'm missing. Dev Board: Nucleo-STM32H563ZIT-144 (Arm M33 Core)IDE: VSCode running STM32 V3 (Pre-Release) Toolchain (not using Clang -> using VSCode C/C++ Language Server for Intellisense) on Windows 11Build Tooling: CMake and GCC with code generated from CubeMX using FW/HAL v1.5.0Middlewares Used: ThreadX, NetXDuo, USBX Initial Debugging:First off, the rest of the code base has been working fine, the general ThreadX Application, Netx stack/App, and any additional code I have added hasn't generated unaligned access faults.  I have not been using the MPU, and have explicitly disabled it in the entrypoint using HAL_MPU_Disable() as well as inside Cube MXmain.cint main(void) { /* USER CODE BEGIN 1 */ /* Disable MPU */ HAL_MPU_Disable(); /* USER CODE END

Hello,I use a STM32F103 MCU and I use the RBIT instruction (as an CMSIS inline functinon). The instruction works properly and I can see the rbit instruction in the disassembly window (for this project I have to use an old TrueSTUDIO IDE).According to the ARM documentation this MCU could not execute the RBIT instruction because it is a Cortex-M3 r1p1 core (CPUID: 0x411fc231) which does not have this instruction. In spite of this the instruction seemly works and the "PM0056 Programming manual" (STM32F10xxx/20xxx/21xxx/L1xxxx) mentions too the instruction without making any difference about the revisions.Can someone help clear up this confusion?