Product forums

Hi, I changed the location of the main.c file in my disk then reimported it in the project explorer as a linked file under the same path (under core/src). When I modify the .ioc file, save it and regerated the code, the changes of the peripheral configuration are not reflected in the linked main.c file. I opended the project directory (on disk) to investigate and saw that a new main.c is generated and the changes are reflected there. What is the solution that makes the generated code from the .ioc be integrated in the linked main.c and not generated a new main.c? 

and how will the information be made available for non-EU residents ? 

STM32CubeMX Version: 6.13.0Chip: STM32WL33CCVxToolchain: MakefileSnippet from startup file startup_stm32wl33ccvx.s: .word MRSUBG_BUSY_IRQHandler /* IRQ20: MR SUBG BUSY interrupt */ .word MRSUBG_IRQHandler /* IRQ21: MR SUBG interrupt */ .word TX_RX_SEQUENCE_IRQHandler /* IRQ22: TX RX SEQUENCE interrupt */ .word CPU_WKUP_IRQHandler /* IRQ23: CPU Wakeup interrupt */ .word SUBG_WKUP_IRQHandler /* IRQ24: SUBG Wakeup interrupt */ Snippet from IT header file stm32wl3x_it.h:void MRSUBG_BUSY_IRQHandler(void); void MRSUBG_IRQHandler(void); void MRSUBGTX_RX_SEQUENCE_IRQHandler(void); void MRSUBG_CPU_WKUP_IRQHandler(void); void MRSUBG_WKUP_IRQHandler(void); Perhaps I'm missing something, but I would assume the function names in the header file need to match the names used for the weak definitions in the assembly file.

HI Sir / Madam,   Is there any documents support for the soldering Reflow temp. ofTS55IDTTR,  reflow soldering profile or curve chart? THanks.   Best Regard, Victor Lai  

Hello ST Community, I am an Engineering Undergraduate, currently working on an academic biomedical project developing a wearable ultrasonic vagus nerve stimulation (uVNS) patch to reduce stress and anxiety levels in my University, which came the guidelines from the Central Projects. We are transitioning from this product to a production-grade wearble system for precise ultrasound signal generation . The system is under the condition of LIFU (Low Intensity Focused Ultrasound Stimulation). Project Main Speciifcations : High-Performance MCU fro real-time MHz-range ultrasound signals.Multiple high-speed DACs/PWM for transducer controlLow-power operation and suitable for wearable patch type deviceCompatibility with DDS Signal generator, RF amplifier and Ultrasound transducersI have been exploring the NUCLEO-H743ZI2 for its excellent Cortex-M7 perfomance, but I have also learnt about the best features of NUCLEO-H75Z3I, STM32L476RG, NUCLEO-F446RE. I have a lot of confused in ch

Hello,   Is there a way to generate code with MX2 by using the CMSIS-RTOS2 API vs the FreeRTOS API? I cannot find a setting in the FreeRTOS configuration to specify that I would like to use the CMSIS-RTOS2 API.   Thank you, -GIl

Hello Team,Believing STM32H5 series is most secure Devices , just doing comparision between H563 and H573 security aspects.Just to know PSA Certified Level 3 and SESIP will also applied to H563 device as well ( being into same Family ) ? We are more concern about firmware protection against Physical and side channel attacks.    

Hi，   vl53L0x goto sleep and wakeup to reduce power.  I used single_mode,program as follow:   I find add          sensor_init(dev,vl53_mode);            //activa  The measurement time was 600 mS. long more than not add  this function？  how  to reduce the time?      

Hi, When performing two measurements per second, how can the power consumption of the VL53L0x be reduced? Is a single measurement or continuous timed measurements preferable? I adopted continuous timed high-speed measurements, setting the measurement duration to 22 ms with a 900 ms interval between measurements, resulting in an average measured current of 19 mA (according to the specification). Based on this, I calculated the average power consumption.(22 mS × 19 mA + 5 μA × 878 mS) / 900 mS = 0.4693 mA. I don't understand why others can achieve 20 μA.

Hello everyone,I am working on my bachelor thesis about sensorless Field-Oriented Control (FOC) for a three-phase BLDC motor.At the moment, I have a NUCLEO-F303RE board, a small BLDC motor, an ESC, and a power supply. I have already generated and measured PWM/SPWM signals from TIM1 channels on the STM32, but I understand that using an ESC with a 50 Hz throttle signal is not the same as directly generating three-phase PWM for FOC.For this reason, I am considering using an X-NUCLEO-IHM07M1 motor driver expansion board with my NUCLEO-F303RE board.My question is:Can the NUCLEO-F303RE + X-NUCLEO-IHM07M1 combination be used for a sensorless FOC thesis project? More specifically, can this board act as the required three-phase motor driver/inverter stage so that I can implement or test sensorless FOC with STM32 Motor Control SDK or my own code?I would also like to know whether this combination is supported by STM32 Motor Control Workbench / MCSDK, or whether I should use another Nucleo board o

Hi everybody.I'm currently trying to use the N6 Nucleo for a personal application but am having trouble starting the debugger after initially successes. I am using the Nx_TCP_Echo_Server example, and after a couple of successful iterations my debugger stopped working entirely.I am using the VSCode extension. When I start my debug session with ST-Link GDB server it will connect to the debugger, but an error will follow in the terminal as shown ("target not responding"). After disconnecting and re-initializing the debugger I will get the following error ("error in intializing... please check power"). I get the same issues after power-cycling the board. LED 2 (Red) will then remain off until I power cycle the board after the first error.Previous issues led me to believe I re-wrote the SWD lines so I connected BOOT0 to 3.3V and used the CubeProgrammer to perform a chip erase. Specifically for the external memory since to my knowledge the N6 doesn't maintain internal memory. After the chip

Due to absence of a security forum for MPU's (while there is for MCU's) posting this here.The CRA prohibits products with known CVE to be placed or made available on the EU market.The ST Yocto ECO 6. Scrarthgap currently has 632C CVEs. The latetst Yocto master has 13.As such,1. how to place a product on the market while a distro without known CVE's does not exist ? A company may have great documentation and processes but if the actual supplied software has known CVE's there isn't a to place it on the market2 Many devices may use even older  ECO systems (5.10) images which may have even more CVE. How will there get patched ?3. Where can information about the known CVE's in ST kernel , U-Boot, OPTEE and TF-A (dev packages) be found ? 

Hi everyone, I’d like to ask for your expertise. I’m working with a custom board based on the STM32H755ZIT, configured in LDO mode. My issue is that when I connect the board to my PC via USB to use the Virtual COM Port (VCP), the computer does not detect the device. I haven’t encountered this problem on other boards I’ve used, such as those with STM32L4 or STM32WB, where USB VCP works as expected. Is there a particular difference in the USB VCP implementation between the STM32H7 series and the STM32L4/WB series that I should be aware of? Here is the noteworthy configuration of my project in CubeMX RCC, HSE=Crystal/Ceramic Resonator SupplySource = PWR_LDO_Supply (This is in line with my hardware design) Power Regulator Voltage Scale = Scale 2 USB_OTG_FS,Mode=Device_Only USB_DEVICE_M7, Class For FS IP = Communication Device Class (Virtual Port Com)   For the code: usbd_cdc_if.c /* USER CODE BEGIN PRIVATE_VARIABLES */ USBD_CDC_LineCodingTypeDef LineCoding = { 115200, /* baud

Hello,I am working with the B-L4S5I-IOT-01A board (MCU: STM32L4S5VIT6) and attempting to load a .hex file using the UART bootloader via USART1 (PB6, PB7).Since this USART is connected by default to the ST-LINK interface, I removed the necessary resistors (R42, R43) to isolate the ST-LINK connection. I then provided direct RX/TX connections from the MCU side through the corresponding pads.However, I am unable to detect the MCU UART in the STM32 Programmer IDE. The device does not appear or respond during the bootloader communication attempt.Could you please guide me on the correct procedure to:Properly enable UART boot mode on this boardEnsure USART1 is usable for bootloader communicationIdentify any additional hardware or configuration requirementsAny reference or clarification would be greatly appreciated.Thank you.

i created a project with the MCSDK for controlling my 3-phase motor,i used it to create a new project with the ioc file with the cubemx, but got many compilation errors, i manage to solve lots of them but got 1 error i cant solve:error: #error "Please select first the target STM32G0xx device used in your application (in stm32g0xx.h file)"133 | #error "Please select first the target STM32G0xx device used in your application (in stm32g0xx.h file)" but the macro STM32G031xx is defined on my PREPROCESSOR definitations. There are lots of issues with the last third-part parties software lately (MCSDK and GFX as well), the projects are lucking some folders, like the include folder in which the main.h exist or the h files of the drivers and are not part of the project when doing searches 

Hello everyone,this is my first time building an STM32 Based Board myself.I am trying to talk to the Chip Using a CP2102 UART Bridge connected to PA9 & 10.For Reset and Boot 0 ive connected Reset (NRST) to RTS of the UART Bridge and Boot0 to its GPIO0 Pin and configured that Pin in the Bridge. I have however also tried just pulling Boot0 High and Jumping NRST to GND and then immediately connecting using STM32CubeProgrammer.Using an Oscilloscope ive found that the Magic Packet is sent to the STM32 (0x7F, 115200 Baud, Even Parity, 1 Stop) but there is no response (Tx of the STM32 stays high all the Time).PB15 is left floating, I am using the VIT6 Variant (The LQFP100 Package), its a Brand new Chip, is there any configuration required before this works?

Dear Sir or Madam,  We would like to use NUCLEO-WL33CC2 to verify DMR RSSI reliable detection(compulsory requirement) and demodulation(optional requirement).  We only need rx chain for scanning purpose.  As per ETSI TS 102 361-1, DMR TDMA frame has sync word in the middle of 30ms frame and does not have preamble. And in Chapter 10.2.2.2 (Physical layer), an RRC filter is designed for 4FSK.  It seems these settings may not have corresponding option in STMWiseCube, so that we would like double check with you if there is any better setting for detect 30ms packet RSSI at least.  We do know the sync word content for DMR, which is 48 bit long. The modulation is 4FSK, nomial channel width is 12.5kHz, and data rate is 9.6kbps. And deviation is +/-0.648kHz and +/- 1.944kHz for 4FSK, shall we use 1.944kHz in the setting of deviation in STMWiseCube?   Our requirement is RSSI at room temperature for this TDMA frame detection in RF conducted test mode and without

When using a Zephyr RTOS host with PAwR synchronization response enabled, the STM32WB09 controller (observer role) reports a legacy LE Periodic Advertising Report (subevent 0x0F) while syncing to a PAwR broadcaster.The broadcaster is implemented on EFR32BG42 (SiLabs). Zephyr host reports:[00:00:02.987,453] <dbg> bt_hci_core: hci_event: event 0x3e[00:00:02.987,480] <dbg> bt_hci_core: hci_le_meta_event: subevent 0x0f[00:00:02.987,497] <err> bt_scan: The controller shall raise the latest unmasked version of the eventWhich corresponds to:LE Meta EventLE Periodic Advertising Report (legacy) The Zephyr BLE controller layer is based on stm32wb0x_ble_stack_controller_only.aDoes stm32wb0x_ble_stack_controller_only.a support:BLE 5.4 PAwR (Periodic Advertising with Responses) – Observer role?Periodic Advertising Report v2 (with subevent context)? 

I am looking for an EEPROM device that has the UID but also supports the 256-byte identification page.I was lead to believe that densities less than 1M support either/or, but greaterthan/equal to 1M does support both.However, from what I can tell from the datasheet(s), the -F version (M24M01E-F) says: "The device offers an additional 256-byte page, called the identification page. This page can be used to store sensitive application parameters, which can later be permanently locked in read-only mode."But the -F version does not have section 4.5 so it does not have UID.  datasheet for version -U (M24M01E-U) says "The device also offers an additional 256-byte identification page. This page stores a 128‑bit (16‑byte) unique factory-programmed serial number, locked in read-only mode at factory delivery."And in section 4.4 says "This is an additional 256-byte page, permanently locked in read-only mode. The user can read it by issuing the read identification page instructi

Hello,   in an earlier post it was suggested to reset the FDCAN for full error recovery using RCC_APBRSTR1.FDCANRST Bit This bit seems to be global for all FDCAN instances. Is it correct that full error recovery in one FDCAN instance is not possible without interrupting traffic in the other instance - as all (or both in case of stm32g0b1) instances have to be reset?   t

Hello,I'm having an issue for a few latest versions of clangd. I was hoping this issue would be resolved in newest update of VS Code extension - clangd v1.0.5., but still with no success. Issue: I'm using two Configurations in CMake -> Configure. Configurations are defined in CMakePresets.json like this:I'm using define as this: I'm switching configuration via CMake->Configure->Select Configure Preset.Now, switching Configuration on clangd v1.0.2 will highlight/fade non-used define correctly. Switching to clangd version v1.0.4, it's no longer working correctly.I have set the setting on v1.0.4 as such:Opacity is 0.5. If I change the Configuration, the Opacity no longer works on the code segment:But, if I go to settings and just enter the value 0.5, it starts working again, untill the next Configure change.This issue in not on v1.0.2, only at v1.0.4 and v1.0.5.

Hello all, Split from this thread: I'm using an STM32U5G9 and I need to read files from a USB stick. I don't want to use ThreadX because I have to keep this application small. How can I achieve this if UsbX and FileX are supposed to be used only with ThreadX and not in standalone mode?   Thanks for your help. Best regards, Julien

Dear community,I am looking for help to have TFM ported for nucleo_u385rg_q so that I can build the tfm secure and non secure images and do a secure boot on this board. The closest board is b_u585i_iot02a which is a stm32u5 variant. But there are many low level code required for this in trusted-firmware-m repo. Is there a work done by someone that I can use for my work? Any pointers as to how to accomplish this. Thanks in advance for your support.

In an Edge AI audio project that I'm working on, there is SAI2 peripheral that stops audio transmission after a while when the AI algorithm in the while loop of the main.c has done some inferences.The AI algorithm code was generated with Cube AI Studio and, when STM32CubeAI_Studio_AI_Process() is commented, the SAI peripheral works normally without interruptions.The board used is a NUCLEO-N657X0-Q.The version of software used is:-ST Edge AI Core: version 4.0.0-STM32CubeIDE: version 2.0.0-Cube AI Studio: version 1.1.0I've tried to search on internet for a solution and there is no material concerning it! I've tried to ask for help in other posts, but nobody helped me. Can somebody try to explain why and find a solution? I'm desperate and I don't know what to do for my project but withdraw. 

Hi,How do I serve request Get Source Capabilities Extended? I'm using STM32G0B1 with a port configured as SRC.When a SINK sends the Get Source Capabilities Extended the STM PD library responds with 'Not Supported' and my code is not aware that this even did happen. Is there way to intercept and serve this request? At least the callback structure does not appear to have direct support for this. USBPD_DPM_ExtendedMessageReceived is never called. /* CAD callback definition */ static const USBPD_PE_Callbacks dpmCallbacks = { USBPD_DPM_SetupNewPower, USBPD_DPM_HardReset, USBPD_DPM_EvaluatePowerRoleSwap, USBPD_DPM_Notification, USBPD_DPM_ExtendedMessageReceived, USBPD_DPM_GetDataInfo, USBPD_DPM_SetDataInfo, USBPD_DPM_EvaluateRequest, USBPD_DPM_SNK_EvaluateCapabilities, USBPD_DPM_PowerRoleSwap, USBPD_PE_TaskWakeUp, #if defined(_VCONN_SUPPORT) USBPD_DPM_EvaluateVconnSwap, USBPD_DPM_PE_VconnPwr, #else NULL, NULL, #endif /* _VCONN_SUPPORT */ USBPD_DPM_EnterErrorR