Solved

New programmer and new to the STM32 ecosystem as well.I am working with a STM32F401 as it has 5v tolerant inputs and 2 32bit clocks.I have a simple program that reads the 2 32bit TIMs (2&5) in encoder mode, sums the results and then outputs a quadrature signal to a device. I have the GPIO outputs set to "low" speed, which according to my reading should give them a max of 2Mhz output.Even this appears to be too fast with the HCLK set to the maximum of 84Mhz. On a scope the signal looks pretty bad and my device (cheap DRO) cannot read the signal at that speed. If I drop the HCLK down to 4Mhz everything works as expected and I get real nice square waves on the scope but this feels "kludgy"My question is, is there something else I should be looking at to adjust the output rate? HAL_Delay etc feel even more kludgy than stepping the clock down.Any help would be greatly appreciated; Code follows while (1) { /* USER CODE END WHILE */ /* USER CODE BEGIN 3 */ int32_t cnt1 = __HAL_

HI, I'm using stm32h7s78-dk, and setup the external flash following this tutorial The "appli" project is in external flash and runs with no issue. Now I want to write some config data such as display brightness to the external flash according to user input but I can't find a way to do that. I tried HAL_FLASH_Program(), but it seems can only modify the internal flash. Then I tried to enable EXTMEM_MANAGER_APPLI in CubeMX to use EXTMEM_WriteInMappedMode(). However, I can't reinitialize the xspi in "appli" project..What is the appropriate way to do this? Any input is much appreciated!

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 

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

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'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.

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

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: 

Hello, I am experiencing a problem with ADC1 and ADC2. I configured them in Dual Regular Simultaneous Mode, where ADC1 acts as the master and ADC2 acts as the slave. The ADC channel connections are as follows: ADC1 Channel 1: 24V_Sense ADC1 Channel 2: 5V_Sense ADC2 Channel 14: IOut_Sense ADC2 Channel Vrefint: Internal reference voltage However, I noticed that IOut_Sense always has a value, while 24V_Sense is unstable and fluctuating. OUTPUT:V24:24011 mV | V5:3 mV | I:23653 mA V24:8807 mV | V5:3 mV | I:8675 mA V24:8726 mV | V5:1 mV | I:8675 mA V24:8844 mV | V5:3 mV | I:8675 mA V24:23767 mV | V5:1 mV | I:23528 mA V24:23853 mV | V5:0 mV | I:23590 mA V24:23727 mV | V5:0 mV | I:23435 mA V24:23968 mV | V5:0 mV | I:23481 mA V24:8832 mV | V5:3 mV | I:8675 mA V24:23541 mV | V5:0 mV | I:23388 mA uint32_t adc_dual_buffer[4]; int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_ADC1_Init(); MX_ADC2_Init(); MX_USART1_UART_Init(); MX_I2C1_Init();

Split from STM32CubeIDE version 2.1.0 won't generate IOC project file as this is a new question.Please keep to one question per thread.Thanks both Ghofrane GSOURI & Andrew Neil for pointers. Adopting the method shown in the presentation. I have selected a nucleo development board to create an STM32MX project. I have then created a STM32CubeIDE projecfrom the MX project. Having not written any code yet, I'm getting compilation errors but have no idea why? The errors are relating to files marked with a red x below: 

I'm trying to set up FSMC in muxed mode to read_write external NOR flash devices. Muxed pins goes through 2 8-bit latches 74HC574D.The problem is that currently i can barely read from external NOR and it's not accepting commands.Firstly HAL_NOR_Init(&hnor1, &Timing, NULL) returns HALL_ERR  since it fails to read CommandSet from NOR. It should read address 0x13 from CFI and get 0x02 or 0x01 as a result, but write commad makes no effect and as a result driver reads at 0x13 from memopry start.After analyzing what's going on on the FSMC bus I still cand fing any clues. Here is an example how it performs ReadID sequence, using standard HAL_NOR_ReadID Everything looks correct, 3 sequences 0x555 - >0xAA, 0x2AA -> 0x55 and 0x555 -> 0x90, but reading 0x00 and 0x01 right after returns data from NOR not the deviceID I've also tried bitbang mode with same pins and code below successfully reads deviceID. So after all it's not a witing problem, but maby timings or so

Hello,When generating a basic Bluetooth project for NUCLEO‑WBA55CG using STM32CubeMx 6.17 (and 6.16) with Cmake as the toolchain, the project compilation fails to a missing symbol during the link stage.Here is the error message:le_ctrl.c:(.text.HCI_READ_LOCAL_VERSION_INFORMATION+0x20): undefined reference to `ll_sys_get_brief_fw_version'After investigation, it turns out the issue is caused by the incorrect order of linked static BLE libraries in the generated CMake file "cmake/stm32cubemx/CMakeLists.txt". CubeMX places the Link Layer and BLE Stack libraries in an order that prevents the linker from resolving symbols correctly. Reordering the libraries fixes the issue.Here is the corrected order that resolves the error:# Project static libraries set(MX_LINK_LIBS :stm32wba_ble_stack_basic.a :WBA5_LinkLayer_BLE_Basic_lib.a STM32_Drivers ${TOOLCHAIN_LINK_LIBRARIES} Utilities STM32_WPAN Common ) Best regards

Hi Together,I am currently trying to use the FMAC hardware accelerator. Normal usage already works. Now for numerical stability I want to implement the filter as second order sections (sos). According to RM0481:Cascaded filters must either be combined into a single stage, or implemented asseparate filters. In the latter case, multiple sets of filter coefficients can be pre-loadedinto the memory, one set per stage, and only the X2_BASE address changed to selectwhich set is used.To do this I currently:Concatenate all the stage coeffs into one vector:static int16_t const b_Coeffs_0[b_Coeff_len_0] = { 55, 111, 55 }; static int16_t const a_Coeffs_0[a_Coeff_len_0] = { -3745, -258 }; static int16_t const b_Coeffs_1[b_Coeff_len_1] = { 16384, 32767, 16384 }; ...static int16_t all_coeffs[sos_Coeff_Count] = { b_Coeffs_0[0], b_Coeffs_0[1], b_Coeffs_0[2], a_Coeffs_0[0], ...On setup input the vector as b coefficients:filter_Config.Clip = FMAC_CLIP_ENABLED; filter_Config.Filter = FMAC_FUNC_IIR_DIRECT

Having some issues trying to debug a FreeRTOS project using JLink, using an STM32U5G9 (Riverdi 5" Display Board) If I enable "serverRtos" in the launch configuration:"configurations": [ { "type": "jlinkgdbtarget", "request": "launch", "name": "STM32Cube: STM32 Launch JLink GDB Server", "origin": "snippet", "cwd": "${workspaceFolder}", "preBuild": "${command:st-stm32-ide-debug-launch.build}", "runEntry": "main", "serverSpeed": "12000", "serverRtos": { "enabled": true, "port": "60000", "driver": "freertos", "driverPort": "ARM_CM33_NTZ" }, "preRunCommands": [ "monitor exec SetRTTSearchRanges 0x200bb800 0x234800" ], "imagesAndSymbols": [ { "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}" } ] } ]And then try to start a debug session, i get a disconnect error:Reading 20 bytes @ address 0x200C2A5C Read 4 bytes @ address 0x200C2A28 (Data = 0x200C2970) Read 4 bytes @ address 0x200C2A58 (Data = 0x200BEA20) Read 4 bytes @ add