Product forums

I am struggling with the keys in the new V1.5.0 LBM stack. Keys are read from NFC EEPROM and device is joining. After joining, I expect the stack to save the join and session keys in secure memory so the keys are deleted in EEPROM for security. After reset, the device does not join. How must this be handled.

I've noticed, that the new STM32C5xx family is not present in the STM32_open_pin_data repo. I know why (MX2 vs MX), but ST, please, keep updating this repo with the new families' data. It's a valuable database for third party tools used to allocate pins in various STM32 designs. Thanks, JW

Hi everyone,For my current project, I am working with an STM32WB55RGV. I am using all 256 KB of its RAM and running the ADC1 at a sample rate of 5.8 MSPS with 8-bit resolution.I am looking to migrate to a newer STM32 family that provides equivalent (or more) RAM and supports this high ADC performance. I plan to order some standalone chips and devkits for prototyping. Compact devkits would be a huge plus.During my research, I found the STM32H523CCT6 chip and the NUCLEO-H533RE devkit at a good price. Do you think this is the best choice for my needs? Also, are there other "mini" devkit options (like the Nucleo-32) that come with a large amount of RAM?Thanks in advance!

Hello,   I may have found a bug related to the STM32C092GCU6 MCU and the FDCAN peripheral.   I created a new project and experienced issues with FDCAN reception: no RX messages were received, and the callback HAL_FDCAN_RxFifo0Callback() was never triggered.  After several days of troubleshooting, I discovered a possible mismatch between the startup file and the generated interrupt handler names.  In startup_stm32c092gcux.s, the following interrupt vectors are defined:  .word FDCAN_IT0_IRQHandler /* FDCAN global interrupt 0 */ .word FDCAN_IT1_IRQHandler /* FDCAN global interrupt 1 */   Howeve

Hello. I'm working on a BLE  application that uses an STM WBA55 board and ThreadX. It was based on the St Threadx p2pServer example, The Sequencer is disabled. I'm using stmCubeIDE 1.19 and st_fw1.7 and i cannot migrate to new versions due to compatibility reasons.The main idea for the application is that the board initializes, advertizes 10-20 seconds for a connection, connects to a device like a phone pc, gets data from a sensor and transfers the data to the connected device. If no connection occurs or if the device is disconnected it should go into sleep/stop/standby mode until an EXTI interrupt from the user button is triggered. As of now the application is structured as follows:-- A main thread is in charge of initializing the rest of the threads (one thread for each type of sensor eg temp adc etc) and handle events like ble connection/disconnection and sleep/wake up requests.--Upon a sleep request a flag is set into an

Hi I am trying to figure out these VCAP conections.From the datasheet I could look like they are internally connected together, for this reason could avoid routing these three pads together on my board.Can anybody confirm that is the case?Thank you.

My code is as follows. volatile uint8_t d_deadcode = 0U; void sleepManagement(void) { if ((isIgnActive(IGN_1, getGpioInput(GPIO_IN_IGN_1))) || (isIgnActive(IGN_2, getGpioInput(GPIO_IN_IGN_2)))) { return; /* ign sig exist */ } if (isSleepSync()) { sleepEntryHandler(); d_deadcode = 1U; } else { updateDateOld(); requestSleepSync(); } } static void sleepEntryHandler(void) { uint32_t rtcWakeup; irqIsrDisable(); deinitApp(); if (ignOff1hrElapsed.state == OFF) { rtcWakeup = TIME_IGN_OFF_LOAD_60MIN - ignOff1hrElapsed.onTimer; startRtc(rtcWakeup); } startWkpu(); enterStandby0(); } void enterStandby0(void) { /* * PD0(8KB): always retained, not programmable * PD1(32KB): always lost in STANDBY0, not programmable * PD2(56KB): retain in STANDBY0 */ MC_PCU.PCONF2.B.STBY0 = ON; if (SPCSetRunMode(SPC5_RUNMODE_STANDBY0) == CLOCK_FAILED) { SPC5_CLOCK_FAILURE_HOOK(); } }​

Hi,ASM330LHH datasheet states that "compensation for high stability over temperature" are embedded in the device. Could you provide more information about the correction algorithms applied ?In particular, when we measure the bias at 0°/s of the ASM330LHH in a temperature chamber, we get strange non-linear behaviors that we suppose to be a consequence of these algorithms. For instance, in the following figure (filtered bias at 0°/s depending on temperature) some "steps" can be observed. Could you provide a description of the corrections applied / the reason of this behavior ? It would make the device more predictable for us.Furthermore, is there a way to disable these corrections ?Thank you a in advance. 

 The following object detection models are not appearing on the STM32 Model ZooSSD_Mobilenet_V2(192x192)ST_YOLO_X_NANO(192x192)Have these models been removed or renamed?  

Dear ST Community,I recently bought the SPC582B-DIS board in order to test the EV-VNF1248F board. I installed the VNF1248 Evaluation board GUI and the UDE STK 2021 by following VNF user guide.I downloaded the Chorus1M_VNF1248_discovery.elf in order to test the board, I flashed it with this elf file (flash success) but communication is not possible in the GUI with the good COM port  and good serial configuration (error "Cannot found Demo Board! Check USB cable"  in USB FTDI, and no Rx trame in Serial Port)I tried with another computer, same results. I looked in the forum, I have the good PLS driver (Driver USB PLS\JtagUsbDriver), and I installed the stsw-link009, but still not working.I also found another elf file on st community website --> Chorus1M_M09SpiDriver.elf, and with this .elf, I'm able to communicate, I get Rx trame and uC is active, but I get the error "firmware is not fitting with HW type", which seems logica

Hi Community, I am using STM32H745I-DISCO board and generated a TouchGFX project and attempted to flash/debug from CubeIDE. The flashing process fails during the erase stage. Observed Errors Initially: “Error: failed to erase memory” After enabling external loader (without initialization): Erase still fails After enabling external loader with Initialize = true: “Failed to initialize external memory” “Error in initializing ST-LINK device” In CubeProgrammer: External flash is detected when selecting loader MT25TL01_STM32H745I-DISCO

Hello, I am working with the ST67W61 WiFi module and NCP firmware provided in X-CUBE-ST67W61. The firmware flashing process works correctly when using the reference setup: NUCLEO-U575ZI-Q X-NUCLEO-67W61M1 expansion board However, the same flashing procedure fails on our custom board, which is designed based on the X-NUCLEO-67W61M1 schematics. Issue observed:During NCP flashing over UART, the process fails at handshake stage with the following error: "ack is b''" "CHIP IMG LOAD SHAKEHAND FAIL" Observations: UART communication appears inactive (no response from module) Same firmware and flashing tool used Same COM port configuration verified

Hi all !I'm trying to write a driver for a LevelX system to talk to a QSPI chip over the OCTOSPI1 peripheral (STM32H563). I got the chip to respond to most commands, set it up in reading / protected mode.But, later, I've spotted an issue : I cannot sent over DMA two buffer, one after the other (as I did, two call to the Transmit_DMA function). Or, the LevelX API provide me two buffer, that may not be contigous. That's the issue, how to do ?I reminded that this chip has Linked List functionnality, which does match what I want (two DMA transfer from / to two different memory space, but, within one frame (Only one NCS being low).And, I cannot find a way to make them work...From a general perspective, the code is build like that :    if (xfer_size > GD25_DMA_THRESHOLD) {         /*          * Clean the semaphore, to ensure we restart from 0.          */  

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? 

Hello,I'm sorry to bother again, but it seems there is another issue in the latest update of VSCode STM32IDE extension. While trying to Start Debugging with GDB Server (STM32Cube Debug STLink GDB Server v1.3.0), with launch.json as: "version": "0.2.0", "configurations": [ { "type": "stlinkgdbtarget", "request": "launch", "name": "STM32Cube: STM32 Launch ST-Link GDB Server", "origin": "snippet", "cwd": "${workspaceFolder}", "serverReset": "Connect under reset", "preBuild": "${command:st-stm32-ide-debug-launch.build}", "runEntry": "main", "imagesAndSymbols": [ { "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}" } ], "faultUnalignedAccess": false, "liveWatch": { "enabled": true, "samplesPerSecond": "4" }, "preRunCommands": [ "set output 16" ] } ] } The Debug starts and I get an error message as:

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.

HelloI have my own board with STM32G071KBT6 microcontroller. I successfully comunicate with charger by PD protocol and I receive up to 21 V (PPS). But I need above 21V. I have power bank with AVS up to 28V and USB cable with e-marker (up to 240W). How to configure the stack to receive EPR parameters? I have no TCPP IC, but I use my own protection circuit. In the trace the EPR commands isn't present. I use STM32CubeIDE 2.1.1 and STM32CubeMX 6.17.0.Thanks a lot and best regards

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  

Dear all, I found an interesting effect using the CubeL4 and CubeMX generated files for a STM32L496 and use ADC1 and ADC3 (not simultaneously): What we do: We turn the ADCs on only when we sample data, otherwise they are turned off.  To turn the ADC off, we use HAL_ADC_DeInit which calls HAL_ADC_MspDeInit. Issue: HAL_ADC_MspInit and HAL_ADC_MspDeInit keep track of active ADCs through static variable HAL_RCC_ADC_CLK_ENABLED. Init increases the count, deinit decreases it. If, however, init and fails but we still call deinit the count wraps around to 0xFFFF FFFF - upon next init it wraps around to 0, but then the ADC clock is not turned on and initialization fails again. See the code snippets below: HAL_ADC_MspInit HAL_RCC_ADC_CLK_ENABLED++; if(HAL_RCC_ADC_CLK_ENABLED==1){ __HAL_RCC_ADC_CLK_ENABLE(); }   HAL_ADC_MspDeInit

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

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.