Solved

I'm planning to use an STM32G0 to make a Type-C to DP controller based on DP Alt Mode, and the high-speed data lines go straight to the DP links, but I'm not really sure how to connect them.Its shape would be something like this.According to the pin assignment of TA0356, item EThis is the Type-C socket definition I found from USB-IFThe mapping in TA0356 is shown in green font.The DPLinks connections are A2  -  A3 = TX1 → ML1B11-B10 = RX1 → ML0B2  -  B3 = TX2 → ML2A11-A10 = RX2 → ML3 Third, this is VESA's PDF,where PDPLinks correspond to shown in blue font.TX1→ ML0RX1→ ML1TX2→ ML2RX2→ ML3Because in the VESA PDF it shows a Type-C cable adapter, we need to swap the TX and RX internally. This is mentioned in the USBIF PDF.So, when the DPLinks in the VESA PDF switch to my design, the following changes will happen, shown in blue font.TX1→ ML1RX1→ ML0TX2→ ML3RX2→ ML2After converting like this, I got a sequence of different DPLinks than in TA0356, where ML0 and ML1 are the same, and ML2 and ML

Hi all,Ive been hand-populating prototype boards around an SPV1050 and for 2 out of 2 boards so far I’ve noticed the SPV1050 being defective right from the beginning. I then replaced the IC  via hot air rework and it worked flawlessly. That makes me wonder if my soldering setup kills the IC.Im using chipquik low temp soldering paste (the syringe is pretty empty, so it is far from fresh) and a Mini Heat plate with the default profile:80 sec rise to 150°C 80 sec rise to 170°C 60 sec rise to 230 90 sec keep at 230°C for soldering slow cooldownAre there any AN’s for this IC regarding soldering? I could nto find any info…Thank you for reading BRDamian 

Hello Team,I am facing RF read and write issues with the M24LR16E‑R EEPROM.The exact problem is as follows:When I take a new EEPROM and write data to it using an RF NFC reader for the first time, the operation is successful. However, during subsequent attempts to read and write: In some EEPROMs, RF read works but write fails but I2C read/Write working. In some devices, both read and write operations fail but I2C read/Write working. A few EEPROMs work correctly without any issues. In our application, we are using Sector 2 and Sector 3 for user data storage.When I read data from the problematic EEPROMs through St25 mobile application, I observe the following:Sector 0 and Sector 1 Security Status is 0x00. And the data read and write is working in these 2 sectors. Sector 2 to Sector 15 Security status: Current Security Status: 0x09 New Security Status: 0x09 Additionally, I receive the warning:“Sector locked. Security Status can only be changed through I2C.”I am not sure why the security

Hi Dear,I connected as picture my SWD pins. What is best solution for SWD Pins? Sould i capasitor, TVS or safety component? Is there any guide for STM32?     

I set PA6 and PA7 to ADC4_INx in CubeMX and ran CODE GENERATE.The generated main.c file implements MX_ADC4_Init(), but it doesn't seem to be called from anywhere.Should I call this somewhere in the main statement?Also, I tried implementing ADC reading within the main loop, but the return value of HAL_ADC_GetValue() is always 0 (even though it's actually around VDD/2).I've attached main.c. Could you please tell me the correct implementation method?

Hi everyone,I’d like to propose an enhancement for a future TouchGFX update.Currently, the clickable area of a ToggleButton is limited strictly to the dimensions of the button’s image. While this works in simple cases, it can be limiting in more practical UI designs.I suggest giving the ToggleButton a resizable clickable area, similar to the way the FlexButton works. Specifically, this would allow the developer to: Expand the clickable area independently via standard width and height properties. Freely position the toggle image within that area (just like an image placed inside a FlexButton). Use case example:Imagine a screen with multiple toggle options, each accompanied by explanatory text or an icon next to the button. With this feature, users could simply tap on the descriptive text or icon to activate the toggle, instead of having to precisely hit the small button image. This would significantly improve the user experience, especially on smaller screens or touch targets.I believ

 /* * 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

Security:Introduction to STM32H5 security - stm32mcu “Approved version. Approved on: 10:25, 18 May 2026”The following links are broken:In the intro section, the text “For general STM32 security see this article and AN5156.”: The link “this article” is https://wiki.st.com/stm32mcu/wiki/Security:Security_overview which shows a “Page not found” error page. In section 2, in the bullet point about PCROP, the text “Obviously this feature is redundant with the availability of TrustZone® and HDP.”: The link “TrustZone” goes to Security:How to disable TrustZone in STM32L5xx devices during development phase - stm32mcu which is for a different MCU and not very relevant for STM32H5. In section 3, the text “For introduction on these features, refer to this guide.”: The link “this guide” is https://wiki.st.com/stm32mcu/index.php?title=Security:Guide_to_use_specific_security_feature&action=edit&redlink=1 - which does not exist. section 3.2, the text “For broader context follow here.”: The lin

Is there any doco or app note on how to save/restore a STM32H7 CRC calculation (e.g. breaking up long CRC calculation into separate segments that requires re-initialization of CRC HW between segments)?

Dear Forum,I'm using a STM32F401 and implemented the I2C as Target transmitter (Slave) answering a I2C question. I'm programming the I2C CR2 (FREQ Bits) Register as follows with correct speed (42 MHz)I2C1->CR2 = ((DRV_RCC_GetPCLK1Freq() / 1000000u) & I2C_CR2_FREQ_Msk); I've noticed some spikes when the STM32 I2C controller generates the answer, see below (yellow markings)Blue: Clock generated by the controller (the clock speed is about 200kHz)Red: Adrdess Byte generated by the controller, Data Bytes generate by STM32 I2C transmitter (answer) with spikesWhen the FREQ Bits of I2C_CR2 Register are zero, this spikes doesn't occur, see belowThe Reference Manual RM0368 Rev 6 for the I2C CR2 writes:It is noticed that this FREQ bits must be configured to generate I2C compliant Signals. Anyhow from EMC perspective this spikes are bad because the radiate a wide spectrum. I've found nowhere information of correct I2C specifiation/behaviour of the Data Signal the be compliant

Thank you for taking the time to review my question.I migrated the Ux_Device_Audio_2.0_Standalone of STM32WBA6 to STM32H503 and successfully enumerated using USB FS. However, out of 1000 entries into the USBD_AUDIO_PlaybackStreamFrameDone function per second, half are 4 bytes long and half are 384 bytes (audio stream). I monitored the data using USBlyzer and did not see any upload data (EP IN) from STM32H503. I don't know where these 4 bytes come from, and this issue has been bothering me for several days.VOID USBD_AUDIO_PlaybackStreamFrameDone(UX_DEVICE_CLASS_AUDIO_STREAM *audio_play_stream, ULONG length){ /* USER CODE BEGIN USBD_AUDIO_PlaybackStreamFrameDone */ UCHAR *frame_buffer; ULONG frame_length; int32_t ret; UNUSED(ret); /* Get access to first audio input frame. */ ux_device_class_audio_read_frame_get(audio_play_stream, &frame_buffer, &frame_length); if (length) { HAL_GPIO_TogglePin(GPIOA, GPIO_PI

Hello, I have connected a sensor to my nucleo board to send data when sensor detects movement.I have introduced an ISR for that.void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin){ if (GPIO_Pin == GPIO_PIN_0) { pirDetected = true; }} unfortunatelly with that approach everytime the sensor was triggered ( I was able to measure 3.3v on the OUT pin using voltmeter) my stm32 is kind a freezing.  I have introduced some testcode,extern "C" int main(void){ /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init(); /* USER CODE BEGIN Init */ /* USER CODE END Init */ /* Configure the system clock */ SystemClock_Config(); /* USER CODE BEGIN SysInit */ /* USER CODE END SysInit */ /* Initialize all configured peripherals */ MX_GPIO_Init(); while (1) { if(HAL_GPIO_ReadPin(GPIOA, GPIO_PIN_0)) { HAL_GPIO_Write

Hello,I’m using CubeMX 6.18.0. I’m trying to implement a USBX standalone (bare-metal, no RTOS) CDC application. Code within user code sections is overwritten when re-generating the project. As far as I can see this is not a new problem, there are already some older topics about it. @ST: will this ever be fixed?Regards

After updating CubeMX to version 6.16.2, we are seeing HRtimer E and F problems which cause our product to fail.  Reverting back to 6.15 and regenerating the code allows our device to work.  I believe the issue is due to the change in the code database version: MxDb.Version=DB.6.0.161 but I can't be sure as the new version of cubeMX forces values into the HRtimer E and F configurations.Hoping for commiseration and resolution!ThanksRauk

I am using STM32CubeIde version 2.1.1, STM32CubeMX version 6.15.0, Segger JLink, and a STM32G474RB chip.The CubeMX generates a linker file which looks like single bank flash mode, I have uploaded the ioc and ld files.With CubeProgrammer, I set the option bits to DBANK = 0 for single mode or DBANK = 1 for dual mode.In every case the debugger stops flash programming at 0x08010000 (64kB), all beyond 0x08010000 reads 0XFFFFFFFF.That leads to a hard fault right after starting a debugger session.How can I fix this problem?And no, I can’t switch to dual mode as the text section file exceeds 64kB, and I can’t update the CubeMX as all versions 6.16 and 6.17 contain a HRTIM configuration bug.

Hi!I have a custom board with STM32MP257F. I have the same electrical setup for HDMI as STM32MP257-DK board have. Hence, the HDMI output is working. But playing sound through HDMI does not work very well. It sounds like the mono .wav files from /etc/share/sound/alsa are recorded under water.I play these sounds by using instructions from https://wiki.st.com/stm32mpu/wiki/How_to_play_audioHere is my sound card. I can play test sounds like pink noise, PWM and sine waves from speaker-test. Here is my hardware setup. I'm using the same HDMI and I2S Device Tree setup as STM32MP257-DK.(No, in mobile view, I cannot post this as a code block because the button "..." is not available)root@watermelon-wine-1aunknown:/usr/share/sounds/alsa# aplay -l**** List of PLAYBACK Hardware Devices ****card 0: STM32MP25DK [STM32MP25-DK], device 0: 400b0000.audio-controller-i2s-hifi i2s-hifi-0 [400b0000.audio-controller-i2s-hifi i2s-hifi-0]  Subdevices: 1/1  Subdevice #0: subdevice #0root@watermelon-wine-1aunkn

Hello,After updating (and later performing a full uninstall/reinstall) to STM32CubeIDE 2.2.0, the "Instruction Stepping Mode" toggle command has completely disappeared, and it appears the underlying command is no longer registered at all — not just hidden from the toolbar.Version:STM32CubeIDE Version: 2.2.0Build: 29186_20260626_0934 (UTC)OS: WindowsSteps to reproduce:Start a debug session on an STM32H7 target Open the Disassembly view Try to enable "Instruction Stepping Mode" to step at the assembly instruction levelObserved behavior:The icon is no longer present in the Debug toolbar Giving focus to the Disassembly view does not automatically enable instruction-level stepping (F5/F6 still step at C source line level only) Going to Window > Perspective > Customize Perspective > Toolbar Visibility, the command "Instruction Stepping Mode" is listed in the Debug toolbar structure, but checking its checkbox and clicking "Make Item Visible" throws the error: "'Instruction Stepping M

Download firmware option on ST87Mxx GUI 2.4.3.0 does not work on EVKITST87M01-2, module on board is “ST87M01-1301”.If I let it run then it says: “Please reset board” and nothing happens after reset, only way out is “Cancel” after which it says “Download Aborted”.If I try to reset board before message “Please reset board” it says: “A problem occurs : error: error sending “AT+IPR=460800”: device responded with “OK”. 

When using this microcontroller, after entering low-power mode via the HAL_PWREx_EnterSHUTDOWNMode() function, I found that there is a 0.9V voltage on VCAP. But the program indeed did not continue performing the reset operation.Do I need to turn off anything before entering this mode? I have used peripherals such as DMA (linked list in circular mode), SPI, USART, ADC, and GPIO.The following is my function for entering low power mode. static void DevLowerKeyInit(uint8_t *index) {  (void)index;  osDelay(200);       vTaskSuspendAll();  SysTick->CTRL &= ~SysTick_CTRL_TICKINT_Msk;      for (uint32_t i = 0; i < 16; i++) {    NVIC->ICER[i] = 0xFFFFFFFF;    NVIC->ICPR[i] = 0xFFFFFFFF;  }            HAL_DBGMCU_DisableDBGStandbyMode();    HAL_DBGMCU_DisableDBGStopMode();        extern void MX_GPIO_ALL_ANALOG_Init(void);    MX_GPIO_ALL_ANALOG_Init();      __HAL_PWR_CLEAR_FLAG(PWR_WAKEUP_FLAG2);  __HAL_PWR_CLEAR_FLAG(PWR_FLAG_STOPF);  __HAL_PWR_CLEAR_FLAG(PWR_FLAG_SBF);  __DSB(); 

I have been developing an application based on the STEVAL-PTOOL1V1_6S_HL. I have managed to successfully get the motor up and running to the expected RPM using the speed potentiometer functionality. I am now developing my own custom hardware using the STSPIN32F0B and I will not be using the speed potentiometer to control the speed of the motor. Instead my intention is to use the commands such as:MC_ProgramSpeedRampMotor1(2000, 1000);MC_StartMotor1();To set the motor speed and start the motor.I am unsure of how to go about removing the speed potentiometer functionality from the generated code In MC Workbench (V6.4.2) after loading in the STEVAL-PTOOL1V1_6S_HL.ioc the Potentiometer option visible can’t be changed 

Here: In the ‘Best Answer’ shown at the top of the thread (immediately after the OP), it’s on a black background:  But, in its original position within the thread view, it’s on a grey background: Note also that the line spacing is different - so the “ASCII Art” no longer works properly

Sensor is LSM6DSV16X.When I use this .h file in my MCU driver. There is no wrist tilt, but “Wrist tilt detection with accelerometer and gyroscope” can.I don’t know why?

Hi ST Team,Can You pls share the Junction temperature of the following Parts.LSM6DSVTR   M24M01E-FMN6TP

I’m a beginner with the STM32 series and STM32N6570-DK.I’m using ‘TouchGFX 4.26.1 Designer’ and ‘STM32CubeIDE 2.1.1’ and ‘STM32CubeMX’.First, I created a simple project for my STM32N6570-DK using TouchGFX. And, it displayed an image on the LCD normally.Next, to use the SD card, I configured the fileX and SDMMC2 settings using CubeMX.After that, when I regenerated the code using CubeMX, the LCD screen is not displaying properly. Is there a guide on how to use an SD card in a project created with TouchGFX?   

Summary  On a NUCLEO-N657X0-Q I have a custom (non-CubeMX-template) FSBL that copies an "LRUN" application image from external XSPI flash into AXISRAM and jumps to it. The byte-identical signed FSBL runs completely when I stage it with the debugger in Development boot (monitor reset → load → jump Reset_Handler) — the app runs end to end. But in true ROM flash-boot (BOOT pins set for boot-from-flash, power-cycle, no debugger), the FSBL reaches main() (user LEDs light) and then locks up before its first clock-configuration step. The lock-up is invisible to SWD, UART, and even fault handlers, which points at a processor LOCKUP tied to the state the boot ROM leaves at the FSBL entry in flash-boot (security / RIF / clock), which differs from the debugger path. I would like to understand what minimal init my FSBL must do at entry in flash-boot.  Hardware / tools  - Board: NUCLEO-N657X0-Q (MB1940), STM32N657X0H, Cortex-M55 + Neural-ART. Device ID 0x486, Rev Z. Lifecycle state: OPEN (SWD attac