Recently active topics

HI,I am working on a board using STM32H573V and have a working solution with UCPD detecting an inserted memory stick and running the MSC class. In an other part of the software I am using PC9 as an GPIO push-pull, low speed output and as soon as I set it to high, the voltage at PB14 (UCPD CC2) drops from 3.3V to 1.5V and my UCPD handler signals a device attached and turns VBUS on even though nothing is attached. There is no other electrical connection between PC9 and PB14 on the board. I am using a TCPP03-M20 for VBUS switching. The board is acting as VBUS source.

Hello ST team,In a previous discussion, ​@Jocelyn RICARD confirmed that X-CUBE-CRYPTOLIB V4.x was not reentrant, partly due to its use of the CRC hardware peripheral.I understand that V5.0.0 no longer depends on the CRC peripheral, but I could not find an explicit statement in the documentation regarding thread safety or reentrancy.Could you please clarify the following? Is X-CUBE-CRYPTOLIB V5.0.0 fully reentrant and thread-safe when called concurrently from different RTOS tasks, provided that each task uses independent contexts and buffers? Does this also apply to single-call APIs such as cmox_hash_compute() and cmox_cipher_encrypt(), which do not expose an explicit context? Can ST confirm that V5.0.0 does not use any shared mutable internal state that could prevent concurrent execution? Is any external synchronization (e.g., an RTOS mutex) required when calling CMOX APIs from multiple tasks? We would like to determine whether a global mutex, previously necessary with V4.x, can

I have a hardware where i need to measure the input signal of the AC mains signal 50Hz, the problem is the hardware does not have provision for input capture. Is it possible to measure? I also several other tasks running like RS485, 13 channels ADC measurement etc, the input signal is given to ADC channel. 

Hello,can you identify this component? ST   W7X428CHINABUL 380A Thank you!regardssonic21 

The Audio section of the community was shuttered, so I am posting in the general area. I am looking for information and insight regarding the 2SC5200 (along with 2SCT5200).It’s my understanding that the 2SC5200 was manufactured only in 2009, but possibly into 2010 and was made using the same fab / die process as Toshiba in order to meet JEITA requirements, but the datasheet shows that it was manufactured using the BiT-LA technology. ST had the 2SCT5200 (released in 2007, I believe) which used the BiT-LA technology.Could anyone confirm manufacturing dates for the 2SC5200, please. Could anyone offer insights as to why the parts with what seem to be identical characteristics and manufacturing processes (if that is accurate) had two different registrations / part numbers?The latest 2SC5200 datasheet I found (Doc ID 16310 Rev 1) notes that the datasheet was preliminary, and that the part was already marked as obsolete when the data sheet was released. It looks like a cut and paste from the

Hi Team,I am currently working on integrating the ST25R500 NFC reader using its standalone evaluation board with an external NXP MCU.Could someone please guide me on how to connect the ST25R500 evaluation board to the NXP MCU, including the required hardware connections and interface signals?Your support and guidance would be greatly appreciated.Thanks in advance!

Hello ST team,I am working on a NUCLEO-H533RE board with TrustZone enabled and the following boot chain:STiRoT → OEMuRoT → Secure/Non-secure applicationMy device reports SFSP version 1.2.0 (0x01020000).For a secure-boot timing experiment, I would like to use an LSE-clocked RTC as a time reference across a software/system reset.I found the ES0621 erratum titled “Backup domain erased upon reset when STiRoT boot is active and the clock other than LSI selected.”My understanding is that, on affected SFSP versions, STiRoT selects LSI for RTC/TAMP. If the application subsequently switches the RTC clock to LSE, the backup domain is erased during a subsequent reset. Is there any supported initialization or reset sequence that preserves an LSE-based RTC time reference across reset on SFSP 1.2.0, while retaining the STiRoT boot path?I can use DWT for measurements within OEMuRoT, but I need a continuous reference across reset to include the earlier STiRoT stage. Reference: STM32H523xx/STM32H533xx

I am working with the ISM330DHCX 6-axis IMU and recording accelerometer and gyroscope data.The accelerometer is configured to ±2 g, and the gyroscope is configured to ±250 dps. For reference, here is an example of my recorded data:ACC_X, ACC_Y, ACC_Z, GYRO_X, GYRO_Y, GYRO_Z-248.819, -3.233, -0.732, 0.58751, -0.20601, -0.33572 Processing IMU Data:The accelerometer values are extracted by combining two bytes into a signed 16-bit value and multiplying the result by glAccSensMultThe gyroscope values are processed similarly, using glGyroSensMult.glAccSensMult 0.061 Questions:When the camera is stationary, why might the accelerometer readings have a magnitude significantly different from approximately 1000 mg, and the gyroscope readings be nonzero? Is additional accelerometer and gyroscope calibration required before using this data?

This may be an eclipse limitation. What I wantsingle workspace e.g. $HOME/work/cube a subdirectory for each board. e.g. cube/f303nuc, cube/f401nuc, cube/L100disc multiple projects in each subdir, e.g. f303nuc/blinka, uarta, dacaWhen I try to set up a project, [eclipse] complains about overlapping projects - apparently interpreting the f303nuc directory as a project. Is there a way to organize the way I like, or am I limited to a flat “hierarchy”?Background: Coming off a (gulp) 10 year hiatus. I’ve only used makefile projects in the past. I think I’m pleased that ST now has a linux version of the IDE.

Hello ST team and community,ST Online Support recommended asking here after reviewing the product documentation. I am developing a battery-management hardware-in-the-loop (HIL) prototype and would appreciate authoritative protocol details and guidance on the remaining chip behaviors.Project contextAn Arty Z7-20 FPGA models ten independent 16S battery modules and ten logical L9965A CMUs, split across two VIF endpoints with five CMUs each. An STM32H753 is the external controller, communicating through real L9965T transceivers and a planned external isolated receive/drive front end. The FPGA is not connected directly to the analog ISO pins and does not replace the L9965T. Physical interoperability testing is still pending while hardware is being assembled.Implemented and tested in simulation: NORMAL-mode 40-bit single reads/writes, global/selective broadcasts, enumeration, standard cell-voltage bursts and CRC6 checked against ST's firmware calculator. The CMUs also implement coherent conv

Board: WeAct STM32WB55 Core Board (STM32WB55CGU6, 1MB flash)STM32CubeProgrammer: v2.23.0Connections tested: ST-LINK/V2 clone (SWD, mode=HOTPLUG) and native                     USB DFU bootloader (port=usb1, H3/BOOT0 held                     high to 3.3V)SUMMARYA wireless-stack upgrade (v1.20.0.2 -> v1.24.0 stack, which alsorequired a FUS upgrade from v1.1.1 to a newer FUS) was interruptedpartway through due to the target losing USB connection during thereconnect phase. Since then, the FUS no longer completes any realoperation (fwdelete, fwupgrade all fail with FUS_STATE_ERR_UNKNOWN)on either interface. FUS_GET_STATE itself gives a confirmed,repeatable, interface-dependent result -- see point 10 -- whichdoesn't correspond to operations actually working on either side.STARTING STATE (before anything went wrong)Read via USB bootloader, Read FUS infos:  FUS State   : FUS_IDLE  FUS Status  : FUS_NO_ERROR  FUS Version : v1.1.1.0  STACK Version: v1.20.0.2  STACK Address: 0x80CE000WHAT WAS

Hello,I am trying to configure an STUSB4531 using the STUSB4531 GUI and a NUCLEO-C071RB board as the I²C bridge.Following the application note/documentation, I connected the NUCLEO board to my PC and attempted to drag and drop the provided firmware .bin file onto the board's mass-storage device. However, Windows reports that there is not enough free space available on the drive.Details:Board: NUCLEO-C071RB Target Device: STUSB4531 Method: NUCLEO board used as I²C bridge for the STUSB4531 GUI Firmware file size: ~43 KB Available space on the NUCLEO mass-storage drive: only ~7-8 KBWhen I inspect the drive exposed by the NUCLEO board, it appears almost full, leaving significantly less space than the firmware binary size. As a result, the drag-and-drop operation fails.My questions are:Is the firmware supposed to be copied directly to the mass-storage drive, or should it be programmed using another method such as STM32CubeProgrammer? Is the limited reported drive capacity normal for the NUC

HelloI am using a Mac. There is software support for stm32cude ide on Mac. But I would like to ask if there is support for Touchgfx application on a Mac.On the website https://www.st.com/en/embedded-software/x-cube-touchgfx.htmlI can not find a link to download the software for Mac.Is there software support for Mac or any other way to run this application? Thank you 

Hi, I'm following the "Programming guidelines for IEEE 1588 timestamping" from page 2792 of the RM0481. I've been working on this specifically for quite a while and I cannot even get the timestamp nanosecond or second registers to move. It feels to me like a clock issue, but unless I'm mistaken, the PTP clock (clk_ptp_ref_i from the manual(p.456)) is the same as the ETH clock (PLL1Q), which I've verified is running because I'm successfully using NetXDuo to negotiate DHCP and send/receive UDP packets successfully. I've also tried initializing the PTP Timestamp without NetXDuo just in case there was some conflict there, but that was also unsuccessful.  Here is my initialization code: /*1. Mask the Timestamp Trigger interrupt by clearing bit 12 of Interrupt enable register(ETH_MACIER).*/ ETH->MACIER &= ~(ETH_MACIER_TSIE); PRINT_U32_BINARY(ETH->MACIER); // 2. Set bit 0 of Timestamp control Register (ETH_MACTSCR) to enable // timestamping. ETH->MACTSCR |= ETH_MACT

Unable to install on Linux Mint 22.3 xfce

Hello all,I’m building a prototype of simple digital clock that shows the current time in 24 hour format with 29 LEDs. The schematic also shows a 10-LED bar, but it is not implemented at the moment. The LEDs are divided into four banks: minutes, tens of minutes, hours and tens of hours. LED cathodes are controlled via two 8-bit shift registers driven via SPI2 & two GPIO pins.I’m prototyping with a Nucleo-F410RB board which uses the STM32F410 chip. I’m using the STM32Cube and STM32CubeIDE for development.I would like to know if it’s possible/feasible to use a 4-channel timer (such as TIM1) in PWM mode for driving the four multiplex signals (MPX0..3 in the schematic below)? Or is GPIO pins with software control the best choice for this application?Thank you for your advice!LED display schematicSTM32 I/O pinsMy messy prototype setup showing the time “07:18” and one bi-LED showing the status “green”. 

I received VND5160JTR-65-E instead of VND5160JTR-E. Which are the differences between them? What do the additional characters ‘-65’ mean?  

I'm currently working on an amplifier stage for a COHO Driver. I'm posting with a general question on the characterization for this transistor. The PD55003-E came up as a candidate for my coherent oscillator amplifier stage. Since the FET's datasheet specifies higher frequencies I was wondering if there were any tests done rated around 55-59 MHz with a Class A amplifier. The design includes a 17 dBm input and a 27 dBm output. The general worry is that with the lower frequency requirement that these dBm specs won't work in the testing stage. This is only the second amplifier I have designed so bare with me if I missed any crucial information on the datasheet.

 Hello,This is a fairly obvious bug with CubeMX configuration of the ‘Block Size’ for TouchGFX Hybrid Double Buffering.  Normal values are reported as errors but if I change the byte size to <-1, the errors disappear.  The parameter description also reflects this wrong OK case.  See screenshot for picture of bug being described. CubeMX ScreenshotContext:Recently migrated touchGFX from v4.22.1 to v4.27.0 for this project Using CubeMX v6.18.1 Configuring project for STM32U5 series (specifically STM32U5A9NJHxQ) Let me know if further information is required about my project configuration. Thanks

Title: STM32L431 debug launch fails every other time depending on odd/even number of Flash pagesHello,I would like to report a reproducible issue with STM32CubeIDE and an STM32L431 device.Environment MCU: STM32L431CBT6 STM32CubeIDE: Version 2.2.0 Build: 29186_20260626_0934 Debugger: ST-LINK / SWD Flash page size: 2 KB SymptomFor a long time, I had an intermittent problem when starting a debug session.Approximately every second debug launch failed.Depending on the failed attempt, I observed one of the following: The program appeared not to be loaded correctly. The CPU ended up somewhere in System Memory, for example at an address around 0x1FFFxxxx. The program started, but did not stop at the configured breakpoint. In some failed sessions, peripheral registers could no longer be read from the debugger. Initially, I suspected BOOT0, reset timing, SWD speed, or hardware noise.However, the same physical PCB worked reliably when I programmed another firmware project into exact

I am unable to change the project name in STM32CubeIde, if i change it and try to open it i get error windows cannot find the file. They are all linked files, may be that is causing the issue, what changes i have to do avoid this error. The project is generated using MCSDK and after generation i am trying to change the project name in CubeIde. 

Hii’m triyng to use USBX audio class on nucleo-h563zi. i have succed to make PC to recognise the board like a controller audio but windows have problem to start the device (error code 10), problem 0xA status:  0xC0440027i’m stuck at this fase unfortunately also i think there are some missing files in the middleware directory, in the example provided by ST UX_Device_Audio2.0_Playback (not sure is related to the error to start device)there is this code: VOID USBD_AUDIO_PlaybackStreamChange(UX_DEVICE_CLASS_AUDIO_STREAM *audio_play_stream, ULONG alternate_setting){ /* USER CODE BEGIN USBD_AUDIO_PlaybackStreamChange */ /* Do nothing if alternate setting is 0 (stream closed). */ if (alternate_setting == 0) { return; } BufferCtl.state = PLAY_BUFFER_OFFSET_UNKNOWN; /* Start reception (stream opened). */ ux_device_class_audio_reception_start(audio_play_stream); /* USER CODE END USBD_AUDIO_PlaybackStreamChange */ return;}the function ux_device_c

I have a bunch of following warnings:c:/programs/ARMtools/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32F1xxxx/STM32F1xx_HAL_Driver/Inc/stm32f1xx_ll_gpio.h: In function 'void LL_GPIO_SetPinMode(GPIO_TypeDef*, uint32_t, uint32_t)': c:/programs/ARMtools/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32F1xxxx/STM32F1xx_HAL_Driver/Inc/stm32f1xx_ll_gpio.h:343:22: warning: ISO C++17 does not allow 'register' storage class specifier [-Wregister] 343 | register uint32_t *pReg = (uint32_t *)((uint32_t)((uint32_t)(&GPIOx->CRL) + (Pin >> 24))); |in several LL headers.Can this please be fixed in some suitable way? One way to do that might be to replace the 'register' specifier by a macro, which would be defined based on the __cplusplus  standard preprocessor macro and its value. A simple version would be to add#if __cplusplus >= 201703L #define register #endifto each header where this occurs, but I am not a C++/build-environment specialist so don't know whether thi

I am running STM32CubeMX2 (1.1.1) on a Mac (Tahoe 26.6.2) and I did (with some difficulty) get it installed and running. I configured a MCU (STM32C552CEUx) and generated an STM32CubeIDE project. No problem.I went back and copied the .ioc2 file, renamed it, and went to configure a different system. Everything was going fine until I tried to configure some new pins after adding middle ware (FreeRTOS and basic_stdio). I could not select pin functions in the graphic mode, table mode, or through activating the associated peripheral (I2C2) and updating the GPIO there. So, I closed CubeMX2 and restarted. Now I get the splash screens showing fine, but when they go away, I just get the spinning timer in the upper-left of an empty screen. In file, I can click Close Window which it will dutifully do, but then I have nothing. In view, Reload and Force Feload do not seem to do anything.   Any thoughts as to how to debug this would be greatly appreciated.

I am struggling with creating USB CDC_ACM standalone using only USBX. In my project my only aim is using my PCB as COM port using with USB connection. With that later on i will upload some settings etc. with usb connection. I cannot pass first step: Windows can not see my device successfully. Often throwing Code43 and Code10 errors. And rarely successfull connection established with the same code pattern. I am not sure if i do the things correctly. In LAB videos and official documents, they achieve USB standalone only using USBX with STM32U0 family. BUt i am not sure if this concept covers the CDC_ACM Standalone. Because i am new at USB communication, terminologies messing in my mind. To sum up, i want to be sure that if i can achieve USB standalone(bare-metal) applicaiton using only with USBX for CDC_ACM (virtual COM port)?