Product forums

Hello,I need to build a USB headset(mic+speaker) using STM32H742VIT6 for a project. I want the stm32h7 to be recognized as a audio device when connected to a PC/android device. Is this possible?This is my first time using a STM Board with cubeMX and cubeIDE, so I want to build the microphone part first. I am having trouble programming the board, specially what middleware to use, how the structure of the project works in the ide, what would be the setup e.g. clock config, dma, adc, timer configuration. It would be nice if I could get some resources/guide on how to start, because I am lost inside the mx and ide!Hardware: WeAct Studion STM32H742VIT6MAX4466 mic

Hi, Was wondering if there is any info on when the VL53L9CX is expected to be released? Regards 

Hi everyone,My company recently purchased a new ST-Link/v2 programmer. The problem is that after the firmware update, the device stopped working, and when I press the Connect button on the STM32CubeProgrammer, the following error appears:Error: ST-LINK error (DEV_USB_COMM_ERR)I tried using an ST-Link/V2 programmer I bought a few months ago, and everything works fine (I only replaced the programmer, same USB cable, same programming cable).The programmer is original, I'm sure of it. I purchased the programmer from DigiKey.Even the serial number I see appears to be genuine. When I try to update the firmware, I get the following result:Can anyone help me solve my problem?Thanks  

The bootrom of STM32N6 can drive winbond nor flash memory?Such as W25Q? 

PART NO: STM32H743IIT6CUBE_IDE VER: 1.19.0SDK : STM32Cube FW_H7 V1.12.1LSE PART NO. : CM9V-T1A-32.768kHz-12.5pF-20PPM-TA-QCHello everyone,I am trying to use RTC on mentioned STM part number. I have enable LSE and configured the RTC.Currently i am not using any battery, i am using a power supply with 3V to VBAT.After boot up inside HAL_RCC_OscConfig, i am getting timeout while checking RCC_FLAG_LSERDY flag.   while (__HAL_RCC_GET_FLAG(RCC_FLAG_LSERDY) == 0U) { if ((HAL_GetTick() - tickstart) > RCC_LSE_TIMEOUT_VALUE) { return HAL_TIMEOUT; } }   The sequence is, once i have provided VDD then VBAT, everything works fine.Next i just turn off the VDD, VBAT is still present.Then i turn on the VDD and facing this issue.Another thing to note is, i am not facing this issue with LSI. So i changed the crystal but facing the same issue.Also the PDR_ON pin is connected to VDD according to specifications.Is it possible to provide any insight of why this is happe

We have a bit of an issue with a batch of STR731FV2T7 microcontrollers (oldschool, I know) not being able to be flashed properly. Any help would be appreciated. We've verified all the usual suspects are not a problem (signal integrity, crystal oscillation, power supply rails all OK). We've also x-ray inspected the packages and the dies, bond wire and package all look the same as known working batches. Anyway, when we try to flash the board with a SEGGER Flasher, we get the following: SEGGER J-Link Commander V6.44h (Compiled May 3 2019 17:37:48)DLL version V6.44h, compiled May 3 2019 17:37:09Connecting to J-Link via USB...O.K.Firmware: J-Link ARM / Flasher ARM V4 compiled Apr 18 2019 16:17:53Hardware version: V4.02S/N: 164215152License(s): JFlash, GDBIP-Addr: 10.0.0.156 (DHCP)VTref=5.019VType "connect" to establish a target connection, '?' for helpJ-Link>Please specify device / core. <Default>: STR731FV2Type '?' for selection dialogDevice>Please specify target interface:J) J

Hi everyone,I am trying to generate a professional SBOM for my project.I have a few questions regarding the best workflow:Tooling & Detection: What the best tool to generate the SBOM.I tried using ScanCode, but it didn't find any component in my project (e.g., FreeRTOS). I had to manually add .about files to the folder to get results. Is there a better tool that can generate the SBOM with minimal manual intervention?ST Cube SBOM : The Cube MCU packages contain dozens of libraries (FatFS, FreeRTOS, USB_Host, etc.). If my project only uses FatFS, the package JSON still lists everything. Do I have to manually extract the components I use from the ST JSON? how to get use of the ST SBOM?I’d love to hear if anyone has a script or a specific toolchain that automates this without the manual "copy-paste" from the ST manifests Thank you!Yahya  

I'd like to clone an existing STM32 C project with CMake that I've previously setup. I've seen posts about how to do this on STM32CubeIDE but none using the VSCode extension.Currently, I'm aware of 2 methods:Cloning `.ioc` fileClone the `.ioc` file into new folder with <New Project Name>.Find and replace any <Old Project Name> references with <New Project Name> in the `.ioc` file.Open the updated `.ioc` file in CubeMX and generate code.Copy over any user code from the original `main.c`.(a bit tedious depending on how much user code there is)Copy over any libraries and recreate any symlinks.Build projectCopying the whole project folder and renamingCopy entire project folder and rename it.Find and replace all occurrences of <Old Project Name> with <New Project Name>.Try building and fix any errors that pop up.Method 1 feels safer but is more tedious than method 2.Is there a neater way to do this that doesn't involve manually replacing values? (i.e. with

Hi! I am trying to muddle my way through a design that revolves around an STM32U5 MCU, and am specifically trying to think about ESD protection. I have been referencing AN5612, which quite helpfully provides lots of specific examples for various applications (though it seems to perhaps be falling out of date, as a handful of the devices mentioned seem to now be marked NRND). One thing that I can't quite wrap my head around, though, is ESD protection as it relates to running some or all of the power domains of the MCU at 1.8V. For example, the datasheet for the stm32u59xx has an Absolute Maximum Ratings table that shows most FT (5V tolerant) pins have a max rating of either 5.5V or min(Vxx+4.0, 6) - so 5.8V in this case - with other pins having a max rating of 4.0. I know these are DC voltages, but I think I understand that it's these values I should use when trying to parametrically search for ESD protective devices, such that they have forward voltages above 1.8V and clamping vol

HiIn this EVAL-SCS001V1 BoardI want to connect this board to my STM32F767ZI, BUT Data lines D+/D- on Its USB-C Connector are not connected to any test point. Is there any workaround this? I can solder wires to for example A side of this connector(D+/D-) but then B side will be left unconnected. I can live with the fact that USB CABLE will work in only 1 orientation when inserted in USB-C Receptable but i am unsure of any other consequences that it will cause? Power delivery contracts/CC1/2, etc.. I know ST offers another Development board STEVAL-ISC005V1 where these signals are available but don't need so many Voltage Outputs and EVAL-SCS001V1 fits perfectly.

We are considering using ST TRISIL (TSS)  devices for crowbar protection . We have been using an alternative type of protection device from LITTELFUSE (SIDACTOR) in an application where we require the TSS to fail as a short circuit. In our application we require the TSS to be a single use device that fails to a very low impedance in a current limited circuit (~3A) . The LITTELFUSE devices have been tested extensively in our circuit and do fail safe to a very low impedance of ~0.1 ohms however some other brands (not ST) have a percentage that fail with impedance of say 5-7 ohms which is too high a resistance  with 3A flowing and this creates excessive power and fire risk. The ST data for the SMP100LC series of TSS device says that it will fail safe and our testing on 10pcs so far shows this to be correct. Can anyone confirm that the design of the TRISIL device will never fail in a higher impedance manner therefore minimizing fire risk?

Hello,first let me start this post by mentioning that I'm still very much a beginner.I'm writing my own abstraction layer functions for the N657X0.While running my clock_config() function, I ran into an issue that I don't know how to fix. The function works as follows:- reset RCC->CR, CRGR1, CFGR2- enable MSI and wait for MSI ready bit- set CPU & SYS clock source to MSI and wait for clock source confirmation bits- disable all other oscillators and all PLL- reset RCC->HSICFGR- configure HSI- enable HSI and wait for HSI ready bit- set CPU & SYS clock source to HSI and wait for clock source confirmation bits- disable MSI- reset RCC->MSICFGR- configure MSI- enable/disable oscillators (if HSIEN=0 then MSIEN=1 and vice-versa)- reset RCC->ICxCFGR- configure ICx- reset RCC->PLLxCFGRx- configure PLLx- enable PLLx and wait for PLLx lock ready bit- check CPU and SYS clock source selection- check if source is actually active by checking the corresponding ready bit again- sel

Hello, I'm trying to use TouchGFX. I created a new project and clicked on Generate code. Afterwards I get the following error message, which I do not know how to handle. Do you have any suggestions?Generate CodeCopy FrameworkCopying TouchGFX framework version 4.24.1 to C:\temp\testgfx\MyApplication\touchgfxDoneGenerateWrote config/gcc/app.mkWrote config/msvs/Application.propsWrote generated/gui_generated/include/gui_generated/common/FrontendApplicationBase.hppWrote generated/gui_generated/include/gui_generated/common/FrontendHeapBase.hppWrote generated/gui_generated/include/gui_generated/common/SimConstants.hppWrote generated/gui_generated/include/gui_generated/screen1_screen/Screen1ViewBase.hppWrote generated/gui_generated/src/common/FrontendApplicationBase.cppWrote generated/gui_generated/src/screen1_screen/Screen1ViewBase.cppWrote generated/simulator/gcc/MakefileWrote generated/simulator/include/simulator/mainBase.hppWrote generated/simulator/include/simulator/video/D

 Hi Partners,hope I can find you well through this mail,I need X-NUCLEO-IHM08M1 3D model(step), if you have the resource, please help me! thanks.  best regards,Crispian Liu 

Hi, I'm a bit stuck.   I'm trying to program watermarks for BANK2 (to make the entire bank secure so I can read the whole area using secure alias) for a custom boot-loader.   The code below is executing in secure context from BANK1 (and no bank swap).  It runs without error, but after a reset, the option bytes are still unchanged.   Im calling it with (FLASH_BANK_2, 0, 63, 0) as arguments. (63 being the last flash page of a 512KB bank - device is 1MB)   I am pretty sure I misunderstand something.   Kind Regards, Nick /**  * @brief Configures or Disables Secure Watermark for a specific bank.  * @PArambank: FLASH_BANK_1 or FLASH_BANK_2  * @PAramstart_page: Start page (Set > end_page to disable)  * @PAramend_page: End page  * @PAramlaunch: If SET, triggers a System Reset immediately to apply changes.  * @return true if the operation was successful, false otherwise  * @note to disable WM, set start_page > end_

Hello,I dug deeper into PSSI behavior, and and I observed unwanted behavior. From my point of view it is a bug.PSSI is configured as:OUTEN = 1 (transmit mode)CKPOL = 0 (outputs driven on rising edge, inputs sampled on falling edge)RDYPOL = 0 (0 at input indicates that the receiver is ready to receive)DEPOL = 0 (0 at output indicates that data is valid)DERDYCFG = 0b11 (Both PSSI_RDY and PSSI_DE alternate functions enabled)EDM = 0b00 (Interface captures 8-bit data on every parallel data clock)Chip STM32H7R3Z8T6, clocked at 600MHz from HSI, placed at PCB, powered by 3.3VPSSI kernel clocked by 150MHz and 300MHz (PLL from HSI)Transmitted data is rising numbers from 0 to 15, stored in array in AHBSRAM1, manualy written by core to PSSI->DR as 32bit values (four data bytes at one write). See source code:while (1){ if(PSSI->SR & PSSI_SR_RTT4B){ // wait until space in PSSI buffer PSSI->DR = arr[idxx]; // place data to buffer idxx++; // index to next data if(idxx >= BLOCK_SIZE

IntroWhen I'm using the "STM32CubeIDE for Visual Studio Code" extension, I often want to edit C source files outside of my workspace, which are listed in my CMakeLists.txt and get compiled into the firmware just like any other C file.  Unfortunately, with the default setup, the language server (clangd) cannot find some of the headers I include, and it doesn't know the right compilation options, so intelligent features like inlay hints (red squiqqlies) and the "Go to definition" command do not work properly.  The ST extension attempts to communicate this kind of information to the language server by putting a ".clangd" file at the root of my workspace folder which has a line in it like "CompilationDatabase: build_release".  But clangd won't consider that file when looking at source files outside of the workspace.MotivationI have multiple STM32 projects that share some common libraries, so my folder structure looks like:lib/lib1/lib1.clib/lib1/lib1.hlib/lib2/lib2.clib

Hello,I designed a custom PCB using the STM32F401RE (LQFP64), but I cannot connect to the MCU through SWD. I am using an ST-Link probe and the st-probe command-line tool.When I run the probe command, the ST-Link probe itself is detected, but the target MCU is not properly identified. The tool reports the flash size as 0x00.MCU: STM32F401REDebugger: ST-Link probeTool: st-probeObserved behavior:ST-Link probe is detected correctly.The MCU is not detected.Flash size reported as 0x00.Power measurements:VDD = 3.3 VVDDA = 3.3 V (through ferrite bead BLM18AG601SN1D)VCAP ≈ 1.2 V (2.2 µF capacitor connected directly, ~8 mm trace, no vias)NRST = 3.3 VTotal board current ≈ 18 mA (two LEDs also present)The MCU does not heat up, and current consumption appears normal.Power architecture:12 V input → buck converter → 5 V → LDO → 3.3 V (MCU supply)Analog supply filtering:VDD → ferrite bead → VDDADecoupling capacitors are placed near the MCU.Debug connections:SWDIO → PA13SWCLK → PA14NRST connected to th

I started learning embedded systems recently, and have been using the Nucleo-F303RE board with the STM32CubeIDE toolchain. Recently, I compiled a program and started stepping through it in the debugger. Everything worked fine as always. I started to modify a single line of code, but decided not to make any changes as I wanted to run the debugger again first. Despite being the exact same program, it took much longer to reach the breakpoint in main from the startup ... maybe 10 seconds instead of 1.5 seconds. Single stepping through a line or a single instruction worked, but was clearly must slower than before. Stepping over a function that writes maybe 10 registers took about 10 seconds. When I let the program run freely, it was no longer reaching a breakpoint in my SysTick handler, even though it was before. How can I get the debugger to work?I tried cleaning the project and rebuilding, but that didn't work. I tried another simple program to make sure the board or ST_Link wasn't someho

Following the ST sample : STM32CubeH5\Projects\NUCLEO-H563ZII regenerated OEMiRoT_Config.obk with the STM32TrustedPackageCreator.then, rebuild the OEMiRot application and the applications OEMiROT_Appli_TrustZone_Secure & OEMiROT_Appli_TrustZone_NonSecureI ran the script : \ROT_Provisioning\OEMiROT\provisioning.batusing the 'PROVISIONED' choice.The script returns No error. But When I check the PRODUCT_STATE with STM32CubeProgrammer, the state came back to OPEN instead of PROVISIONED.But, I had to use the DA to connect to the device with the STM32CubeProgrammer. So, OBK files seems to be applied.I has already checked that the PROVISIONING state has been correct before the OBK provisioning sequence.So it's the action "set state PROVISIONED" that fails (or maybe an issue with the OBK files ???,  but no way to check if they are OK).Someone has already meet this issue ? How to fix it ?  

Title edited to state the issue being discussed.Really? After all these years? Padawan

I'm getting the "elf has a LOAD segment with RWX permissions" warning, and a quick search here reveals a couple of ways to get around this: Disable the warning, or edit the .ld file.However, in my case, I'm using the upper half of the STM32's flash area to emulate non-volatile memory.  So I want my flash to be writeable.Can anyone suggest some magic to put in my linker file that will make the warning go away, but also allow me to write to flash?Also: I'm using STM32CubeIDE, so my linker file is auto-generated.  Is there a user-override mechanism (like there is in the source code)?Thanks.

Hi, I am seeking some guidance.With the new release STM32CubeIDE for Visual Studio Code 3.8.0, it says it comes with new features including " Serial terminal: Enabling developers to easily setup serial communication for example leveraging the ST-LINK virtual com port."In the docs, there is not much explanation on how to get this working. I only see:"If the serverPort attribute is defined, two ports are used by the ST-LINK GDB server: one for the debug session and serverPort + 1 for the SWO connection.These ports are reserved even if SWO is not activated in the debug configuration."How would one activate the SWO in the launch.json? I went through all the options with completition and none seem to activate or configure the SWO.I know that with the extension "Cortex-Debug" provided by marus25 we could configure the SWO as so:"swoConfig": { "enabled": true, "cpuFrequency": 275000000, // must match -a (Hz) :contentReference[oaicite:4]{index=4} "swoFrequency"

Hi, I'm trying to measure X-Nucleo-nfc03a1 with VNA: i got completely different values for C11 C22 and C2 as is on nucleo board. I understood something wrong? and when I remove Resistors 330ohm, inductor and 4 100pF capacitors I got like: 

We are developing a STiROT/OEMuROT bootloader for a customer using the above chip. This is based on the STM32H7S78-DK sample. The customer has developed the main application and have added support to download a new firmware image over Ethernet. This image is stored in external RAM and once downloaded an md5 checksum of the image is stored and a flag is set to indicate that new firmware is available. At this point the device is restarted to switch to the bootloader. We've added code to the bootloader that checks if a new firmware image is available in external RAM. If a new image is available the bootloader validates that the image is OK by recalculating the md5 checksum. The validation passes and at this point a section in external FLASH is erased. After the erase completes, the image in external RAM is copied into the external FLASH and the copied image is validated via md5 checksum - which fails. On further investigation it is the data being read from external RAM that is incorrect (