Solved

I  have already submitted the case in ST Online Support, but have had no reply for over two weeks.

In the debug mode of JLink, the usage method of LiveWatch cannot be found. Only STLink has this function. How long will it take for the relevant functions of jLink to be updated?I really enjoy using this extension plugin provided by your official side. I hope you can let me know! thank you{ // 使用 IntelliSense 了解相关属性。 // 悬停以查看现有属性的描述。 // 欲了解更多信息，请访问: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "jlinkgdbtarget", "request": "launch", "name": "STM32Cube: Launch JLink GDB Server", "origin": "snippet", "cwd": "${workspaceFolder}", "preBuild": "${command:st-stm32-ide-debug-launch.build}", "runEntry": "main", "imagesAndSymbols": [ { "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}" } ] } ] 

Hello! Recently I discovered that my program (STM32 TCP client) gets stuck in netconn_connect() function for about 5 minutes if server to which I want to connect to is not available when this function is called. Only after that time program would go intoif ((tcp_rexmit_rto_prepare(pcb) == ERR_OK) || ((pcb->unacked == NULL) && (pcb->unsent != NULL))) {statement (which is present in tcp_slowtmr() function). Once it happens, the debugger shows that:TCP PCB shown in debuggerIt's the tcp_rexmit_rto_prepare(pcb) condition that allows program to go into the if statement. Also, as debugger shows, nrtx is equal to 0, which means there were no retransmissions in the last 5 minutes (rtime=575, which is 287 seconds).Interesting thing is it's possible to "unfreeze" the program way sooner by pinging the client device or by replugging Ethernet cable. netconn_connect() would finally finish and device could try to connect to server once again. By the way, the netconn I used was

Hello ST Community,We are using LIS2DW12 in single data conversion on-demand mode.Configuration:- MODE[1:0] = 10, single data conversion on-demand mode- SLP_MODE_SEL = 0, output data generation triggered by INT2 external signal- INT2 is used for Data update trigger- INT2 is driven by an MCU GPIOAccording to the LIS2DW12 datasheet, INT2 is described as a clock input when selected in single data conversion on-demand mode, and INT2 clock input supports up to 200 Hz.However, we could not find the AC timing specification for the INT2 input trigger.Could you please clarify the following points?1. What is the minimum HIGH pulse width required on INT2 to guarantee a trigger?2. What is the minimum LOW pulse width required before the next trigger?3. Is the trigger detected on the rising edge, falling edge, or by the HIGH level?4. Is it required to keep INT2 HIGH until DRDY is asserted, or is a one-shot pulse acceptable?5. Are these timing values guaranteed over process, voltage, and temperature?

Hi everyone!I'm writing my first bare-metal driver for STM32 in C (CMSIS, no HAL). The driver controls a TMC2209 stepper motor driver over half-duplex UART.The basic functionality is currently working: initialization, frame assembly, CRC calculation, and movement control via VACTUAL. To keep it hardware-agnostic, the UART send function is decoupled using a function pointer (handler->send). Registers are defined using union and bitfields (struct).Since this is my first driver, I'd love to get feedback from experienced embedded developers on the following questions: API Design & User Access: What level of API access should I expose to the user, and how should it be structured? Is it better to hide register manipulation behind high-level functions (e.g., set_speed, set_current), or keep direct register access accessible? Bitfields vs. Shifts/Masks: Is using union + struct (bitfields) acceptable for production-ready embedded code, or is it better to switch to explicit bit shifts a

As the title describes, the conversion tool to convert Stm32CubeIDE projects over to Visual Studio Code seems to work. Apart from the fact that, at least in my case, it failed to copy over the assembly files, .s files, in the project. Which led to build errors, specifically thumb mode errors.Just posting this here so that it may help others. Not quite sure how best else to let others know.

Hi, I was making a demo project so needed a really straightforward way to use the ADC of my STM32F446RE.I configured the ADC1 with only channel. Default parameter everywhere except I enabled ‘Continuous Conversion Mode’ as I understood it, all I had to do with it was to start the ADC (HAL_ADC_Start(&hadc1)) and pick the values every time my loop needed it. I was surprised to notice that ‘HAL_ADC_PollForConversion(&hadc1, 100)’ worked only the first call then always yield HAL_TIMEOUT as I was expecting the ‘Continuous Conversion’ mode to allow me to not call HAL_ADC_Start and stop every time.After finding the linked post, I found the solution was to change the ADC setting from hadc1.Init.EOCSelection = ADC_EOC_SINGLE_CONV Into hadc1.Init.EOCSelection = DISABLE The thing is this option is not available in STM32CubeMX (V6.17.0) so I have to pick either ADC_EOC_SINGLE_CONV or ADC_EOC_SEQ_CONV.I have the behavior I wanted but I wonder if this can be improved in STM32CUBEMX or is the

We are considering using IIS2ICLX for product development.I would like to know the following specifications for this product. ① “stability” of “bias” with respect to a fixed calibration value over a period of one year② “stability” of “scale factor” with respect to a fixed calibration value over a period of one year 

Regarding the behavior of temperature drift of the IIS2ICLX, I would like to ask for your guidance.- When the temperature increases, how does the zero-point temperature drift behave?- Does the amount of zero-point drift change depending on the rate of temperature increase?For example, after heating rapidly to 80°C and then allowing the temperature to stabilize sufficiently, compared with slowly heating to 80°C and allowing the temperature to stabilize sufficiently.

Hello,I am currently working with the IIS2ICLX MEMS inclinometer sensor, and I am unable to find the noise spectral density curve as a function of frequency.Would it be possible for you to provide it, in particular for the low-frequency range (0.1 Hz, 1 Hz, 10 Hz, etc.)?Thank you very much in advance for your help.Best regards,

Hi,I'm currently encountering an issue with USB CDC on the STM32F466: the device is not being recognized as a USB CDC device.I'm using the USB_OTG_FS peripheral, with the USB_DEVICE middleware configured as CDC. However, in the Parameter Settings for USB_OTG_FS, I don't see an option for Internal PHY.I then tried using USB_OTG_HS with Internal FS PHY instead, and in that configuration, the Internal PHY option is available in the parameter settings.So I'd like to confirm the following:Is the Internal PHY option only available when using Internal FS PHY (i.e., only through USB_OTG_HS configured for FS mode), and not available for USB_OTG_FS directly?If I need to use CDC with USB_OTG_FS, do I need to add external pull-up resistors (since there's no internal PHY option to handle this automatically)?Thanks in advance for your help.

Hello,I’m using an Karo SOM module (MP257) on a custom board with SFP module.The SFP module is powered with the main 3.3V regulator. It has a TX_DISABLE input (0=ON, 1=OFF). This input :Is TTL Has an internal pull-up R (around 10k) Has an external pull-down R (10k) In connected to PE2This makes a voltage divider : without driving the TX_DISABLE line, the voltage is something like 3.3V / 2 (1.8V to be precise)Some simple tests to confirm that :SFP module unplugged => voltage is driven only by the pull down R => 0V A source meter on the TX_DISABLE confirms the presence and value of the internal RPU. Now let’s play with the MP2. Is this processor able to blink a led ? Don’t laugh, nothing could be further from the truth. After linux boot : gpioinfo shows PE2 is input. It should logically be driven by the driver, but for an obscure reason, this is not the case. At least we can do things manually… Set it to 0 ?gpioset -b disabled -d push-pull PE2=0=> Voltage is still 1.8V Ok, bad.

Hello,I am integrating the VD5943 image sensor with a Lattice FPGA acting as a MIPI CSI-2 receiver.I have reviewed both the VD5943 Datasheet (DS14968) and the Reference Manual (RM0532), but I could not find any information about the operating mode of the MIPI CSI-2 clock lane.Could someone from ST please clarify the following?Does the VD5943 transmit the MIPI CSI-2 clock in Continuous Clock mode or Non-Continuous Clock mode? If this behavior is configurable, which register controls it? If it is fixed, which mode is implemented by default?This information is important to ensure compatibility with our FPGA CSI-2 receiver and downstream processing.Thank you for your support.

Hi ST team,I am working with an STM32MP257 where Linux runs on the Cortex-A35 and a FreeRTOS application runs on the Cortex-M33. The M33 firmware is loaded and started by Linux using remoteproc.The application is running correctly, but I would like to understand the recommended workflow for debugging the M33 application.I have read the "Debug support" section of RM0457 and understand that the M33 can be accessed through the shared SWD/JTAG interface by selecting the appropriate Access Port. However, I'm still not clear on the recommended debug workflow when the M33 is managed by remoteproc.My questions are:Can STM32CubeIDE/ST-LINK attach to an already running M33 started by remoteproc, or should the M33 be stopped first? If Linux has already loaded the firmware, should the debugger load only the ELF symbols instead of downloading the application again? Is there any special OpenOCD/ST-LINK or CubeIDE configuration required for this use case? Is there an ST application note or example de

Dear STM Support Team,I am working on a custom hardware platform based on the STM32N6570-DK.We have replaced the default MX66UW1G45G Octal SPI NOR Flash on the evaluation board with an Infineon S25FS512S Quad SPI NOR Flash. Since the default external loader is designed for the Macronix Octal flash, STM32CubeProgrammer is unable to program the new flash device.We would like to develop a custom External Loader (.stldr) for the S25FS512S. However, we are unable to find the source code or documentation specific to the STM32N6570-DK external loader.Could you please clarify the following?Is the source code for the STM32N6570-DK External Loader (MX66UW1G45G_STM32N6570-DK.stldr) publicly available? If yes, where can it be obtained? Is there any application note or documentation describing the API and project structure required to develop an External Loader for the STM32N6 series? Are there any reference projects or examples for creating a custom .stldr for STM32N6 devices? If the source is not

Hello,In the reference schematic of the STM32MP157F-DK2, the HSE clock is generated using the NDK NZ2016SH 24 MHz END4869F oscillator. However, this part is not readily available, and we are therefore looking for a suitable alternative.Could you please confirm whether the Abracon’s part ASE-24.000MHZ-LR-T can be used as a replacement to provide the HSE clock for the STM32MP157FAC1 device ? If this part is not recommended, kindly suggest a suitable alternative that is compatible with the STM32MP157FAC1.Regards

Hello,We are designing a custom board using the STM32MP157FAC1 device. In our design, we are not using the DSI interface or the ADC peripheral.We would like your guidance on the recommended handling of the corresponding unused pins.(1.) DSI Interface:Since the DSI interface is not used, how should the following differential signals be terminated ?(a.) DSI_CKP / DSI_CKN(b.) DSI_D0P / DSI_D0N(c.) DSI_D1P / DSI_D1N(2.) Analog Inputs:As the ADC is not being used, what is the recommended way to connect or terminate the ANA0 and ANA1 pins ?Could you please advise the recommended hardware implementation for these unused pins?Regards,

I’m using VSC with the STM32 extensions.When running debug sessions at leat 50% of the time I get this error message:Error in initializing ST-LINK device.Reason: USB communication error. Please reconnect the ST-LINK USB cable and try again.cube has exited with code 3 I have a good quality USB lead and I’m running on macOS on a Mac Mini M2

Hello,I am using the STM32G031F4P6 (TSSOP20) and have a question regarding the PA11[PA9] and PA12[PA10] remapping.According to RM0444, PA11_RMP and PA12_RMP remap PA11→PA9 and PA12→PA10. However, in STM32CubeMX, the shared pins PA11[PA9] and PA12[PA10] only expose the Alternate Functions of PA11/PA12 (e.g., USART1_CTS, USART1_RTS/DE/CK), and USART1_TX/RX are not available.Could you please clarify:Is this a limitation of STM32CubeMX? Or is it not possible to use the PA9/PA10 Alternate Functions (e.g., USART1_TX/RX) on the physical PA11/PA12 pins after enabling PA11_RMP/PA12_RMP?If it is supported in hardware, what is the recommended way to configure it?Thank you.

hi all, I am trying to flash + run a relocatable / runtime loadable model. The problem is that the inference results are wrong (they never change, no matter what the buffer contains when I start the inference). If I use the stai_model files from the AI Cube Studio, the model works correctly, but is not relocatable… Am aware of matching the address where I flash the network_rel.bin and generating the model. (← see URL) I am using these docs. (← see URL) I am enabling all AXISRAM3...6 I generate the model as follows:stedgeai.exe generate -m "path/to/model.tflite" --input-data-type uint8 --no-inputs-allocation --no-outputs-allocation --target stm32n6 --st-neural-art --reloc# final output something like this:+--------------------------+-------------------------------+------+------------+--------+| name (addr) | flags | foff | dst | size |+--------------------------+-------------------------------+------+------------+--------+| xSPI2 (0x20009332

I’m trying to convert an ONNX model which has a Conv layer that takes weights as input (has 2 inputs). Edge AI gives me:NOT IMPLEMENTED: Convolution with multiple not constant inputs not supportedAre there any short-term plans to support such layers in ST Edge AI?I also tried to change the name of the layer to some custom name (DynConv). The error in ST Edge AI changed to:NOT IMPLEMENTED: Unsupported layer types: DynConvI thought that I could bypass this error by using --custom with a JSON definition, but the JSON format is poorly documented. Also, many attempts at different formats seem to indicate that --custom only works for Keras. Is this correct?

Hi ST Community,I am working on the STM32N6570-DK board and need guidance on running two AI models together in a single pipeline:YOLO-FastestV2 for object detection (this is my custom train model) MediaPipe Face Landmark for facial landmark detectionMy GoalI want to:Run YOLO-FastestV2 to detect objects/faces from camera input Then run MediaPipe Face Landmark on detected face regions (ROI) Process both models efficiently on STM32N6570-DK Display final output with bounding boxes + face landmarksCurrent StatusI can run object detection examples on STM32N6570-DK. I have AI models available in ONNX/TFLite format. I am exploring deployment using STM32Cube.AI / ST AI tools. I am not sure about the best architecture for running both models together.QuestionsI need help with the following:Is it possible to run two AI models in parallel on STM32N6570-DK? What is the recommended pipeline? Camera → YOLO-FastestV2 → ROI extraction → Face Landmark → Display Output Should both models be merged into

Hi ST Community,I need help regarding a version mismatch issue while deploying my AI model on STM32N6570-DK.Current EnvironmentI am currently using:ST Edge AI Core: v2.2.0-20266 (2adc00962) STM32Cube.AI: 10.2.0-RC1ProblemWhen I convert/generate my model using the current tools, the generated model version becomes:Generated model version: 1.1.3dev14But my board/application runtime is using:Runtime version: 1.1.3dev8Because of this version mismatch, I am unable to run the model properly.My UnderstandingI think I currently have two possible options:Option 1Install an older ST Edge AI version / STM32CubeAI version that generates a model compatible with:1.1.3dev8Option 2Upgrade my runtime/environment on the board so that runtime version becomes:1.1.3dev14QuestionsI need guidance on the following:Which option is recommended by ST? Where can I find the correct ST Edge AI / STM32CubeAI version that generates models for runtime 1.1.3dev8? How can I upgrade the runtime on STM32N6570-DK from 1.1.

I am working on STM32N6570-DK. If I want to deploy random forest model on this MCU, what is the procedure. As most of the time I was using STM32 Cube AI studio to generate IDE project and work on it . But , AI studio doesn’t support tree based models. So, what is the standard procedure for deploying random forest or tree based models on this MCU for real time detection ?  Kindly guideThanks & RegardsChanchal 

Trained Yolov8n on the coco text dataset, trying to import into STCube AI Studio and receive the following error message.Run failed: Error: analyze error: INTERNAL ERROR: 0 vs. 11. Please check the report for more details. Output: ST Edge AI Core v4.0.0-20500 359356bb0