Solved

Hello,Document: RM0090 Reference Manual for STM32F405/415, STM32F407/417, STM32F427/437 andSTM32F429/439.https://www.st.com/resource/en/reference_manual/rm0090-stm32f405415-stm32f407417-stm32f427437-and-stm32f429439-advanced-armbased-32bit-mcus-stmicroelectronics.pdfRevision: 21, 07-Jun-2024.Location: Pages 847-862 in Section 27. Also, Figure 241, 242, 243, 244, 245, Table 125.This section, figures and table all contain 17 references to ITEVFEN bit, supposedly from I2_CR2 control register.In reality, there is no such bit in this register, the actual name is ITEVTEN (interrupt event enable), and it is located in I2C_CR2, bit 9.Section 27.6.2 has correct name.stm32f405xx.h file, and others related to i2c, use the correct name: #define I2C_CR2_ITEVTEN_Pos (9U) #define I2C_CR2_ITEVTEN_Msk (0x1UL << I2C_CR2_ITEVTEN_Pos) /*!< 0x00000200 */ #define I2C_CR2_ITEVTEN I2C_CR2_ITEVTEN_Msk /*!<Event Interrupt Enable */Therefore, the ITEVFEN in the document should be repla

I am really very new to wireless communication but i need to make the project up and working. I have purchased 2 Wio E5 boards, getting confused how to build and make it working. I have gone through two gitshubs STM Repository and the seed studio repository  seedrepository At present i am looking for point to point communication. I found similarities with both the projects for example BSP folders for nucleo and LoraE5mini, i understand is i have to port the code, i tried hard but it is showing compilation errors. Please recommend me how do i proceed in terms of compilation.

Hi ST,Today I decided to give STM32CubeIDE for VS Code another try.I installed all 15 latest packages (Rev. 3.10).Using the STM32Cube Bundle Manager, I installed all required bundles, including Ninja 1.13.2.After opening in VS Code the folder containing the code generated by STM32CubeMX (CMake option) and trying to configure CMake for the first time (Ctrl+Shift+P → CMake: Configure), I received the error below.What am I missing? The last time I tried this several months ago, the project at least configured correctly and built successfully. Kind regards,Thomas [main] Configuring project: Firmware[driver] NOTE: You are configuring with preset Debug, but there are some overrides being applied from your VS Code settings.[proc] Executing command: "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=C:/Projects/All-purpose-Micro-Controller-2/Firmware/cmake/gcc-arm-none

STM32CubeIDEI have Project Directory (Fully populated from an earlier version of the IDE on a different machine)that I bundled up and then unwrapped on my new build machine.However, when I point my newly installed (up to date) IDE to my unwrapped Project directory,it “sees” the Project is there...but when I click “Finish” to bring it into my IDE, the IDE showsthe project (with the correct name) but devoid of any project properties...and no Source Code Tree(where I normally--and previously--could navigate all the source files).  I can see all the expected source code files in my Project DirectoryWhat is the disconnect?Do I need to manually edit the PROJECT.ioc or .project file (or .cproject or .settings or *something*) ?Is there a known issue with transferring a Project from an earlier version of the IDE?Guidance Appreciated!Paul++ 

Hello,We have designed a custom RF module based on the STM32WL33, and one of ourcustomers is asking us to demonstrate that the RX sensitivity of our modulematches the values published in the datasheet:  - RX sensitivity @ 1% BER:      -132 dBm @ 300 bit/s, 433 MHz, OOK      -128 dBm @ 300 bit/s, 868 MHz, 2(G)FSK      -112 dBm @ 38.4 kbit/s, 868 MHz, 2(G)FSKTo validate this, we would like to reproduce the exact test conditions usingan official ST development board (e.g. NUCLEO-WL33) and theSTM32WL33 GUI, so the result is directly comparable to thedatasheet.In the GUI's "Radio settings" tab we can set: fc, DR (ksps), Fdev (kHz),CHF (channel filter bandwidth, kHz), modulation (OOK/2(G)FSK/4(G)FSK/ASK),Spread Factor, and Pout.Could you please help us with the following:1. What DR / Fdev / CHF / Spread Factor values did ST use internally to   characterize each of the three sensitivity points above? In particular:     - For -132 dBm @ 300 bit/s / 433 MHz / OOK: Under the test conditions of 1

Hello! I installed the extension and configured it to work through a proxy (downloading the compiler, etc.), and everything works fine, but when I try to download devices list via cube pack sync, I get the error: Failed to download with Unsupported `GLOBAL_AGENT.HTTP_PROXY` configuration value: URL protocol must be "http:" I tried adding the proxy via platform environment variables, but that didn't help. Platform: Win11 IDE pluggin: 3.6.4 Pack manager: 0.3.12

Dear Community,I am currently following the official MEMS Studio tutorial "Module 5 - MLC Configuration and Visualization" available on YouTube.I am using the following hardware and software setup:MEMS Studio version: 2.4.0 Board: NUCLEO-F401RE with X-NUCLEO-IKS4A1I was able to successfully complete all tutorial steps up to the Automatic Filter & Feature Selection (AFS) stage. However, whenever I click "Run" in the AFS tool, MEMS Studio displays the following error message:"Unexpected error with code 104 occurred during AFS request processing."The issue occurs consistently, even though I am following the tutorial exactly as shown in the video.Additional information:The PC has internet access. I tested both my company network and a mobile hotspot, but the error persists in both cases. No firewall events indicating blocked connections were detected. The board is correctly recognized by MEMS Studio and all previous steps work as expected.Could you please help me identify the cause of

Hi,I struggled a while to find out why my STM8S I2C was always “Busy”.Even AI had some headaches (except only one put me on the track ...)This device requires to configure the definition of I2C pinout in special FLASH.To do this, compile your project and open ST Visual Programmer.Load your “My_project.s19” file. There are three TABS in the window: PROGRAM MEMORY, DATA MEMRORY and OPTION BYTE. Click on option byte, select AFR6 and change it for “I2C SDA SCK” instead of “AIN4 AIN5”. Save your “My_project.s19” file.When your will burn the device, it will write the new parameters in the FLASH and the device will always be configured for I2C. You do this exercise only once.Hope it will help ….

Hi, I'm seeing a consistent issue where every sensor connected via I²C (as far as I can tell) produces 0 bytes of streamed data over USB:HTS221 (temperature + humidity) LPS22HH (pressure + temperature) STTS751 (temperature) IIS2MDC (magnetometer)At the same time, all SPI-based sensors stream normally:IIS3DWB IIS2DH ISM330DHCX (accelerometer + gyroscope)Both microphones also work correctly.Execution details:Board: STEVAL-STWINKT1BFirmware package: FP-SNS-DATALOG1 v1.5.1 (Utilities/HSDPython_SDK included)Host SDK: HSDPython_SDK (st_hsdatalog 3.0.1, st_dtdl_gui 2.1.0, st_pnpl 2.1.0), Python 3.10, Windows 10Connection: USB (WinUSB), using hsdatalog_cli.pyResult (consistent across multiple runs and after a full USB power-cycle of the board):Name                  Length----                  ------AcquisitionInfo.json     226DeviceConfig.json      28090HTS221_HUM.dat             0HTS221_TEMP.dat            0IIS2DH_ACC.dat         76608IIS2MDC_MAG.dat            0IIS3DWB_ACC.dat      1542000IM

The test conditions of VINCL parameters of VNS3V04DPTR-E chip are: Does light inject 1mA current into the IN pin, and does the SOURCE pin need to be grounded?

The magnetometer doesn’t start over I2C and doesn’t output data via UART. Please help solve the problem; the files are attached.

I recently purchased the STEVAL-LLL001V1 evaluation board, which uses the STLED524 LED driver. According to the user manual (UM2143), the board requires the software STLED524_V1.44.exe (or a later version) for operation. However, I have been unable to locate this software.Could you please let me know where I can download it?

I have a custom design with STM32mp135f + MT41K256M16TW-107 DDR3L @ 533MHz that I want to bring up. I built a Linux image based on OpenSTLinux guides and it boots until my kernel is loaded (uboot logs : “starting kernel”) then its crashes without any logs even with earlycon. By testing the DDR with ST DDR Tool, I realized that byte-masked writes fail (test 9), but halfword & RMW32 work.  I noticed the byte lane swap but it is identical on the dk board. I am a bit lost and don’t know if the issue is timing/config related or due to my hardware design.  

Good morning,I'm working on some new automotive designs and on the current boards i found what are , presumibly, STM components but i can't really identify them with the offerings in the online catalogs, (at least IF they are STM engineering samples)The body is specifically PowerSSO-16 but the marking of the components i found for now present similar but very different top markings2HTS90 D1B1HTS20 D11HTS10 200U2HTS30 D1B1HTS50 D1(these 5 are the ones i classified so far) Can i have some help in documenting them, if they indeed are VND productsBellow a picture of one of the components, there are all the same except the top markings (no logos or such)  

Hello,We are designing a custom board using the STM32MP157FAC1 device. For programming and debugging, we are providing an STDC14 connector on our board and use the STLINK-V3SET debugger/programmer.As per AN5031 (Section 8.3.3), the recommended ESD protection device is ESDALC6V1W5. Snapshot is attached for kind reference.We have the following queries:Query 1:Can we use the HSP053-4M5 device instead of the ESDALC6V1W5 for ESD protection? We are already using the HSP053-4M5 to protect the data, clock, and command lines of the microSD card interface. Using the same device for the STDC14 interface would help us optimize the BOM.Query 2:Can we connect USART1_TX (PA9) and USART1_RX (PB15) of the STM32MP157FAC1 to Pin 14 (T_VCP_TX) and Pin 13 (T_VCP_RX), respectively, on the STDC14 connector for the STLINK-V3SET Virtual COM Port interface? Regards,PS  

Hi, I’m using Nucleo-64 development board with STM32H533RE. On the board,H533:RTC crystal is Crystal, 32.768kHz, 9pF, +/-20ppm, 70KR, 1.6x1mm and load capacitors are 3.9pF each.Crystal 24MHz, 6pF, +-20ppm, 80ohms max, SMD, and load capacitors are 6.8pF each. F723:on the same board, the STM32F723IEK6, it is Crystal, 24MHz, 6pF, +/-20ppm, 80R, 2x1.6mm and load capacitors are 2.7pF each.should the RTC load capacitor value close to 15pF each? should be 24Mhz load capacitors close to 10pF each? why STM32F7 and STM32H5 24MHz have different capacitor values?Thank you for your concerns

​@Pavel A. I am facing a similar issue. Cannot instal STLINK drivers on Windows 11 (STSW-LINK009 | Software - STMicroelectronics)  Here is my system information: Any help would be greatly appretiated!

Heyho,just played with / checked the FPU on a G431.I found that the CubeIDE setting overrides the enable via register SCB->CPACR.So, if source code sets FPU on, but IDE says FPU off, the FPU is off.That a bug or a feature?

Hello everyone,I’m currently working with an STSPIN32G4 MCU on a custom board.Two version of this board exist: version A and version B.When I upload the firmware to the MCU on board A everything works correctly. The exact same firmware on version B doesn’t work.What happens:Board B is powered on and the MCU is still fabric new (no firmware uploaded) The custom fw is uploaded using the “Debug” feature of STM32CUBEIDE via JTAG The code is executed succesfully by the MCU Board B is powered off After repowering on board B the issue starts to present: the firmware gets stuck as soon as any interrupt is calledHere’s an image of where the program points at when I press stop on the debugger after an interrupt callWhat has already been tried:Performing a full chip erase on the MCU and redownloading the firmware, but it still gets stuck on interrupt call Removing the interrupt that was causing the firmware to get stuck (UART1 interrupt), but it still gets stuck as soon as TIM2 interrupt gets cal

STM32CubeProgrammer settingsJust got a NUCLEO-L476RG and connected to my computer. I cannot connect to it with STM32CubeProgrammer or STM32CubeIDE2.0.I had STM32CubeMX generate some code to blink the LED and haven’t changed any code in IDE.How to I actually connect to this board?I have tried changing to hardware reset, holding reset button pushing connect in Cube, then releasing etc. I am able to run Firmware upgrade in Programmer and it says it completes successfully. debug authentication discovery fails also IDE Debug error: (when I connect the board it opens in file explorer automatically) 

Hi ST community I'm working on a simple application to get USB Device CDC ACM up and running. My goal is to make my STM32N6 Nucleo board detectable by my laptop so that it appears as a Virtual COM Port under Windows Device Manager.Here are my STM32CubeIDE settings:Step#1:  Clock Configuration.    Step#2: Set SYS clock : HSE -? DIGBYPASS Clock Source   Step#3:  Select TIM6, check off : Application   Step#4:  Select TIM6 as Timebase Source, check off : Application    Step#5:  Select USB1_OTG_HS, and select Internal HS Phy: Device, check off : Application  Step#6:  Select Threadx  and check off Core and Mode: Application  Step#7:  Select USBx with the following setting :1. Mode: Application mode 2. Check off  Core system3. UX Device:  Device CoreStack HS and Controllers HS4. Device Class HS: CDC_ACM  And here is my main.c file : ​​​Here is my project folder structure.To program the board, I've set the boot switches to DEV mode and compiled only the application code. I don't build or progr

Embedded veteran here, been involved in all manner of MCUs and MPUs professionally (especially safety-critical) but for personal use most of my prior experience has been with PIC16F and 18F (to save money obviously), of course those are only 8-bitters. I’m very interested in learning STM32 MCUs (gee they look ALMOST like DSPs except it’s single-cycle multiply not MAC and no simultaneous pointer adjustments etc.). Thing is my PIC experience has given me a pretty decent collection of chip initialization routines that I can adapt as necessary for small differences with peripheral features and such. My “inherent bias” is bare metal, no FreeRTOS, I understand I may be “going against the grain” a little but I want to get my hands on every nanosecond I may have coming. I don’t necessarily need this in C language, but I would like to get my hands on at least a very detailed list of all the HW registers that COULD need to be set, and the EXACT order in which this is “most safely accomplished”.

Hello,another day, another N6 "issue" :)I want to do RAM to RAM copy by HPDMA, but the data never get copied from Src to Dest, Dest always stays unmodified. I have checked the 'DMA_RAMToRAM' example for N6 and went from there, but with no success.DMA Init:__HAL_RCC_HPDMA1_CLK_ENABLE(); HAL_NVIC_SetPriority(HPDMA1_Channel1_IRQn, 0, 0); HAL_NVIC_EnableIRQ(HPDMA1_Channel1_IRQn); handle_HPDMA1.Instance = HPDMA1_Channel1; handle_HPDMA1.Init.Request = DMA_REQUEST_SW; handle_HPDMA1.Init.BlkHWRequest = DMA_BREQ_SINGLE_BURST; handle_HPDMA1.Init.Direction = DMA_MEMORY_TO_MEMORY; handle_HPDMA1.Init.SrcInc = DMA_SINC_INCREMENTED; handle_HPDMA1.Init.DestInc = DMA_DINC_INCREMENTED; handle_HPDMA1.Init.SrcDataWidth = DMA_SRC_DATAWIDTH_HALFWORD; handle_HPDMA1.Init.DestDataWidth = DMA_DEST_DATAWIDTH_HALFWORD; handle_HPDMA1.Init.Priority = DMA_LOW_PRIORITY_HIGH_WEIGHT; handle_HPDMA1.Init.SrcBurstLength = 2; handle_HPDMA1.Init.DestBurstLength = 2; handle_HPDMA1.Init.TransferAllocatedPort = DMA_SRC_ALLOC

Could you share ST60A3H1 IBIS model?Due to ST60A3H1 include eUSB signal, we would like to simulate the eUSB signal integrity on our design layout.ThanksHank

Hi ST Team,I am facing an issue while building an OpenSTLinux project for STM32MP255.EnvironmentBoard: STM32MP255 OpenSTLinux: 5.0.8 Yocto Distribution: openstlinux-weston Ubuntu: 22.04 LTS Kernel: 6.8.0-124-generic pseudo version: 1.9.0+git pseudo SRCREV: 28dcefb809ce95db997811b5662f0b893b9923e0  ProblemThe build fails during:build-info-openstlinux.bb:do_packageThe failure occurs inside Yocto's standard perform_packagecopy() while executing:tar --exclude=./sysroot-only \-cf - \-C image \-p -S . |tar -xf - \-C packageThe error is:got *at() syscall for unknown directory, fd 4unknown base path for fd 4, path buildcouldn't allocate absolute path for 'build'tar: ./etc/build: Cannot open: Bad addresstar: Exiting with failure status due to previous errors Investigation PerformedI verified the following:1. RecipeThe build-info-openstlinux.bb recipe is unchanged and only creates the /etc directory.The /etc/build file is generated by image-buildinfo.bbclass.2. Generated fileVerified that:ima