Recently active topics

How tp flash the .elf through CAN , i’m using SPC58EC80E5 and working on Autodevkit studio. 

Hi, we are in the initial stage of our project and planning to use STM32H7S7I8T6, we need to have a 128MByte of external RAM as per our requirements but only 64MByte of PSRAM is available in market currently, is it possible to add two 64MByte of PSRAM to the MCU (If any please provide the guidance/design note) or any other options ? 

Dear Sir/Madam,We use STPS20200CG-TR Schottky diode in our unit. This diode has operating junction temperature range -40C...175C and storage temperature range -65...175C. Our unit must start operating at -55C. Will STPS20200CG-TR operate at -55C ambient temperature without being damaged and which parameters may deteriorate?Thank you,Alex  

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

Dear ST Support Team,I am working on a custom BLDC motor controller using STM32G431CBU6 with STM32 Motor Control SDK 6.4.2 and DRV8316CT motor driver.I have created custom Control Board and Power Board JSON files using the Motor Control Board Designer. However, I am facing an issue configuring the current sensing topology for FOC.Hardware ConfigurationMCU: STM32G431CBU6 MCSDK Version: 6.4.2 Motor Driver: DRV8316CT Control Algorithm: FOC PWM Configuration: 3-PWM (TIM1) Current Sensing: Three Shunt Resistors (Amplified)Current sensing connections are:Signal MCU Pin ADC Function CURRENT_AMPL_U PA1 ADC1_IN2 / ADC2_IN2 CURRENT_AMPL_V PA2 ADC1_IN3 CURRENT_AMPL_W PA3 ADC1_IN4 ProblemWhen I configure Three Shunt Resistors, Motor Control Workbench reports the following warnings: CSConnect: ThreeShunt_AmplifiedCurrents DualADCs SharedSignalCSConnect: ThreeShunt_AmplifiedCurrents DualADCs NoSolutionI investigated the ParameterConnection.json file and found that the DualADCs im

Hi community, I have been having trouble with finding the correct steval-mki217v1 motionFX 9axis fusion Sensor orientation: NED, ENU, SEU, NWU. the only resouce I had was from IKS01A1 Nucleo eXpansion board. I had tried several combination and had the best combination shown below.Please feel free to correct what I got wrong here.Could someonr confirm this sensor orientaion I use on the right is correct as well as how can I determine the north east west south from this shield? 

Some applications have the need to use an external interrupt from an GPIO input that is already configured as alternate function. My use case is to use EXTI on a rising edge of SPI_NSS input to detect a terminated SPI transfer on a slave.So I need the combination of MODE_AF and EXTI_IT when configuring the GPIO input pin. Unfortunately, HAL does not support this and asserts on IS_GPIO_MODE(__MODE__) for this combination.However, STM32 MCUs usually support this combination, so it makes sense to support this in HAL.To allow this, I added some definitions in stm32g4xx_hal_gpio.h:#define  GPIO_MODE_AF_IT_RISING                    (MODE_AF | EXTI_IT | TRIGGER_RISING)                     /*!< Alternate Function with External Interrupt Mode with Rising edge trigger detection          */#define  GPIO_MODE_AF_IT_FALLING                   (MODE_AF | EXTI_IT | TRIGGER_FALLING)                    /*!< Alternate Function with External Interrupt Mode with Falling edge trigger detection       

Hi team, Reposting my earlier query as it appears to have been missed.How do I measure the peak RAM and peak Flash usage of an AI model?I need to calculate peak RAM and peak Flash from the IDE, but the model generated by ST Edge AI is in HEX format and is not included in the IDE's reported size. So, I'm adding the HEX file size to the IDE's peak RAM and peak Flash figures — is this approach correct? Details are shared below. KWS cpu+npuIDE  Flash = text + data = 205,404 + 1,616 = 207,020 bytes ≈ 202.17 KBRAM  = data + bss = 1,616 + 102,040 = 103,656 bytes ≈ 101.23 KBFor cpu+npu we flash the model in  hex format, so we need to add the peak ram and peak flash of hex file with IDE peak ram and peak flash. model size - Total Peak Ram and Peak FlashPeak RAM = (103,656 + 22,065 =  122.77 KB) Peak Flash = (207,020 + 22,065 =  223.72 KB)

Board: STM32N6 (Custom board with USB OTG HS)I am trying to create a USB composite device with:  - CDC ACM Instance 0 (LOG port) - Interfaces 0, 1  - CDC ACM Instance 1 (DATA port for GenICam/GenCP) - Interfaces 2, 3  - UVC VIDEO class - Interfaces 4, 5Dual CDC works perfectly. However, when I add CLASS_TYPE_VIDEO to UserClassInstance[], the device fails to enumerate entirely (not visible in lsusb).  ---  Working Configuration (Dual CDC Only)  // ux_device_descriptors.c  uint8_t UserClassInstance[USBD_MAX_CLASS_INTERFACES] = {    CLASS_TYPE_CDC_ACM,   // CDC0 - interfaces 0,1 - endpoints 0x81,0x82,0x03    CLASS_TYPE_CDC_ACM,   // CDC1 - interfaces 2,3 - endpoints 0x84,0x85,0x06  };  Result: Device enumerates as 0483:5710, two /dev/ttyACM ports appear, communication works.  ---  Failing Configuration (Dual CDC + VIDEO)  uint8_t UserClassInstance[USBD_MAX_CLASS_INTERFACES] = {    CLASS_TYPE_CDC_ACM,   // CDC0 - interfaces 0,1    CLASS_TYPE_CDC_ACM,   // CDC1 - interfaces 2,3    CLASS_TYP

Product: STM32CubeProgrammer 2.22.0 (Linux x86-64) Interface: SWD / STLINK-V3 (dual probes) Target: STM32F427 (DEV_ID 0x419)DescriptionRunning --incremental flash against one STLINK-V3 probe while a second STLINK-V3 is physically connected (but not commanded) produces a deterministic SIGSEGV inside ST_LINKInterface::programMemory.Call chain at crash:DebugInterface::programBufferFlashLoader (@ 0x206400) FlashLoaderMng::Loader_WriteRange ST_LINKInterface::programMemory ← SIGSEGV @ 0x727b81Root cause: use-after-free on Target::loadersTarget::loaders is a BSS-global loader table shared across all code in the process. When the second probe is plugged in, the library's internal USB hotplug callback fires, rescans the bus, and rebuilds — freeing — the loader table while the incremental flash write loop holds a pointer into it. There is no lock observed on the table.The sequence at the crash site (DebugInterface::programBufferFlashLoader @ 0x206400):206631: mov 0x40(%rsp),%rdi

I just upgraded to Cube 2.0.0 components. I did my first build in CubeIDE 2.0.0 with a previously working project and I got strange errors.  It appears the HAL objects for the peripherals are getting garbled.  When pointers to the objects are passed to functions, the compiler says that the pointer is of another peripheral type.  In the output below, the pointers to ADCs are treated like they are of the timer typedef.What could cause this? arm-none-eabi-gcc "../Core/Src/main.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DDEBUG -DUSE_HAL_DRIVER -DSTM32G473xx -c -I../Core/Inc -I../Drivers/STM32G4xx_HAL_Driver/Inc -I../Drivers/STM32G4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32G4xx/Include -I../Drivers/CMSIS/Include -I../USB_Device/App -I../USB_Device/Target -I../Middlewares/ST/STM32_USB_Device_Library/Core/Inc -I../Middlewares/ST/STM32_USB_Device_Library/Class/CDC/Inc -O0 -ffunction-sections -fdata-sections -Wall -fstack-usage -fcyclomatic-complexity -MMD -MP -MF"Core/Src/main.d" -MT"

--incremental uses a 32-bit additive byte-sum, not a CRC — sum-preserving content changes are silently skippedProduct: STM32CubeProgrammer 2.22.0 (Linux x86-64) Interface: SWD / STLINK-V3 Target: STM32F427 (DEV_ID 0x419)DescriptionThe --incremental download mode decides whether to skip a flash sector by comparing a 32-bit additive byte-sum of the sector's current chip content against the same sum of the new image.The on-target .stldr CheckSum export (@ 0x200001e9, verified in two loader binaries) uses additive accumulation.Because addition is commutative and linear, any two images whose bytes differ only in ways that cancel (adjacent-byte swap, +1/−1 pair, any permutation within a sector) produce identical sums. Those sectors are silently skipped — old bytes remain on chip and the tool reports success.ReproductionTest images A and B (64 KB, four 16 KB sectors) are constructed so that:Sector 1: bytes at offsets 0x4100/0x4101 are 0x11,0x22 in A and 0x22,0x11 in B — an adjacent swap. Addi

[PN]:  EVSPIN32G06Q2S1[VERSION]: MCSDK 6.4.1[TOOL]: MC WB[DETAILS]:6step and sensorlessabout the BEMF circuit, BJT(Q2/Q5/Q8) the MCWB give me a tip should I keep the BJT and short B-E?wha’s the purpose of these BJT(Q2/Q5/Q8)?

I downloaded X-CUBE-AI, but after clicking it, the Add network button did not appear, and uninstalling and reinstalling the IDE also did not work. 

Right now hardware buttons work the following way:The TouchGFX engine checks if the button value matches the trigger set up in the designer in the generated method of the screen view base handleKeyEvent().In target hardware the method Sample() of your button controller (base class touchgfx::ButtonController) is called by TouchGFX engine. In simulator the vent SDL_TEXTINPUT is used. If you hold a key the event will happen in rising edge of the key press  and then re-occur periodically if you hold it down, because the keyboard event repeats.Using SDL_KEYUP would make more sense as touch button widgets also produce a pressed event on falling edge of button press (button release).You cannot read the values the engine gets from the target hardware or simulator in the model directly. You would have to send them from view to presenter to model and do that for each screen. This is tedious.Alternatively you can retrieve the HAL instance and sample again:uint8_t key

[English was established as the common basis so that everyone in the global community can understand each other (see ST Community Terms and Conditions - STMicroelectronics Community, article 10)]Dear STMicroelectronics Technical Support,Hello,We are a company in the rail transport industry and are currently using your TL084AI operational amplifier. However, during use, we have noticed inconsistencies in the markings on the surface of the devices. I have attached an example in the image below. What does “MZE5303” mean? (Note: we currently have another batch, such as MZE4303. What does this represent?) Which characters indicate the date code (for example, the batch number)? We would appreciate your detailed explanation. Thank you in advance. 尊敬的意法半导体技术支持，您好，我们是一家铁路交通行业的公司，目前正在使用您的TL084AI运算放大器。然而，在使用过程中，我们注意到设备表面的标记存在不一致。我在附图中附上了一个例子。“MZE5303”是什么意思？（注：我们目前还有另一批，比如MZE4303。这代表什么？）哪些字符代表日期代码（例如批号）？我们希望能得到您的详细解释。提前感谢大家。 

The schematic is shown below. I have pulled  down BOOT0 to ground through a jumper ， power supply voltage is normal. Could you please help me check if there is a problem with the MCU configuration。 

I have been chasing a very intermitant issue with some STM32L100 based products.The problem shows itself with the MCU being reset by the WDT part way through the initialisation sequence.This issue only displays itself when the MCU has reset itself using  NVIC_SystemReset();E.G. the program flow is as followsRunning programNVIC_SystemReset(); is calledMCU resets and goes through the init section in main.cpart way through the init section, it locks up and the wdt resets the mcu. Once it has started to do this, it can stay in this reboot loop until you re-power the MCU OR it can recover after only one reboot. There is no pattern to how it recovers without a power cycleThis does not happen when you power up the mcu, it only happens when the mcu has been reset using NVIC_SystemReset();Plugging in a USB cable into the board and a pc stops the reboot cycle. (no app on the pc needs to be using the usb com port) We have several thousand products in the field and we come across this issue once e

I’m about to start a new embedded project that is probably outside my skill set (as usual) and I’m hoping to get some recommendations on what STM MCU might have a reasonable learning curve to build up the MCU part of this system. It’s another autonomous oceanographic observing platform like I’ve built in the past with a lot of help from people on this forum. That system used a STM32H7 MCU. For this case, I need a few more serial ports and an ethernet connection to a new sensor. And I’ll need a file system and lots of Flash and SRAM. Low power matters, but the MCU is pretty low on the power consumption histogram.The STM32H5 looks like a good choice since it has lots of serial ports and the Nucleo STM32H563 has an Ethernet phy and a USB-C connector that theoretically could support a USB Flash driver.. Here are a few specific questionsQ0 Is there a better MCU choice with an easier learning curve that might meet my requirements?Q1. It looks like the H5 and STMCubeMX/IDE now use FileX which

On a garage floor a small limestone block 150 mm by 50 mm by 20 mm on a fixed roller support XXXXXXXXXXXXXAF              RSensor at A, the F and R are small wooden blocks and a roller.  I pick up the electrical signal to 420 Hz.  The limestone is vibrating at 460 Hz quite nicely as it is a heavily degraded block so the Sensor TileBox Pro is quite good, but should I normally see electrical signals this high, the CX1 stops at about 180.  

Hello All,We are adding the IIS2MDCTR magnetic sensor in our existing product.The concern we share is that this is a magnetic sensor and will it affect the MRI machine or its results when installed in the MRI Room.Our product is an Emergency Exit Light a manadatory product but as of now without the magnetic sensor. Please share your feedback. 

 /* * Stl_Scheduler.c * * Created on: Jun 25, 2026 * Author: User */#include <stl_user_api.h>#include "stl_scheduler.h"#include "main.h"#include "app_threadx.h"#include "APP_Log.h"extern TIM_HandleTypeDef htim15;/* RAM & FLASH Tests definitions */#define FLASH_SECTION_SIZE 1024U#define RAM_SECTION_SIZE 128U#ifdef STL_DISABLE_RAM_BCKUP_BUF#define RAM_BACKUP_BUFFER_SIZE 0#else#define RAM_BACKUP_BUFFER_SIZE 32#endif// STM32H523#define TEST_RAM_START_ADDR (0x20000000U + RAM_BACKUP_BUFFER_SIZE)#define TEST_ROM_START_ADDR 0x08000000U//#define TEST_ROM_END_ADDR 0x0801A3FF//#define TEST_ROM_END_ADDR 0x0801A00FU#define TEST_ROM_END_ADDR 0x0801A3FFU//#define TEST_ROM_END_ADDR 0x0807F7FFU/*#if (defined (__GNUC__) && !defined (__CC_ARM) && !defined (__ARMCC_VERSION))extern void *_edata_load;#define TEST_ROM_END_ADDR ( (uint32_t)&_edata_load + 3)#endif*/// Runtime RAM test: 8 sections x 128 bytes = 1024 bytes#define TEST_RAM_SECTION_NB_RUN 8 /* only 8 RAM

Summary This article presents a step-by-step tutorial on how to develop a USB device with dual CDC ACM in the STM32F7 microcontroller using the classic USB library. The tutorial is based on NUCLEO-F767 and can be easily tailored to any other STM32.   Introduction If you are developing a USB device composite application for the STM32, this article is for you! Here we show you how to implement the classical USB device middleware to use more than one class in the same application. For this tutorial, we use the F767 Nucleo board, which has a USB connector to open two CDC (Communications Device Class) class through the USB communication. The CDC is used to open a virtual COM port communication. This board has an STM32F767 microcontroller, and for further details about the board, refer to its user manual. The steps shown here can be easily adapted to any other STM32. The IAR IDE, the STM32CubeF7 were used to build this tutorial. To get access to the code developed for this articl

I want the motor to run at 4000pps with 38 V power supply and full step with 17HS 8401!In this case, which is superior, L6470 (voltage control) or L6472 (current control)? Also, if you have any points to keep in mind, please let me know.

I am trying to make the ADC channels sample the current through some motor channels synchronised to the center of the center aligned PWM waveform to avoid switching noise.The microcontroller I am using is the STM32F411 series, and I am using the first 3 channels of Timer 2 for PWM. The 4th channel is set to "Output compare no output", and I also set the timer trigger output event selection to Output compare (OC4REF). I set the pulse of channel 4 to the TOP value of the timer so it triggers when the counter counts to the TOP (midpoint of PWM). For the ADC, i am trying to sample 4 inputs (2 phases for 2 motors) and shift the data into a buffer using DMA. I enabled scan conversion mode as well as DMA continuous requests, and set the trigger source to Timer 2 capture compare 4 event, triggered on the rising edge. The ADC global interrupt is also enabled.In code, I started timer 2 using:HAL_TIM_Base_Start(&htim2); HAL_TIM_OC_Start(&htim2, TIM_CHANNEL_4);Then, I start the ADC us