Solved

Hi, two years ago I posted this thread:Solved: How to set "Don't fragment" flag LWIP short TCP pa... - STMicroelectronics CommunityNow I just was reviewing it for another application that truly needed to send more data and was not allowed to wait 50ms for every sent packet.Final root cause explanationThe 415-byte packets were being ACKed after ~40–50 ms because I was only sending one TCP segment at a time and waiting for it to be acknowledged within my application code, before sending the next one.This behavior is due to the TCP Delayed ACK algorithm implemented by Windows. When Windows receives a single TCP segment smaller than the MSS, it does not immediately send an ACK. Instead, it waits approximately 40–50 ms before acknowledging it.This behavior is described in RFC 1122, section 4.2.3.2 ("When to Send an ACK Segment"), which explains that a TCP implementation may delay sending an ACK in order to reduce protocol overhead.If a second TCP segment is received before the delayed ACK t

HelloI have a STM32H7R3V8T6 and want to use a few peripherals and GPIOs. However, I don't manage to see an output with my analyzer. The peripherals themselves seem to work: An XSPI receive for example does receive some dummy bytes and takes exactly the required time for the transfer (measured with the cycle counter), but the pins do not show anything.I reduced my code and came up with this simple demonstration of how I initialize a GPIO:int main(void) { SystemCoreClockUpdate(); HAL_Init(); SystemClock_Config(); __HAL_RCC_GPIOB_CLK_ENABLE(); GPIO_InitTypeDef GPIO_InitStruct = {0}; GPIO_InitStruct.Pin = GPIO_PIN_12; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_LOW; HAL_GPIO_Init(GPIOB, &GPIO_InitStruct); while (1) { HAL_GPIO_TogglePin(GPIOB, 12); HAL_Delay(10); } }The debugger shows that I reach the loop. The registers of the peripheral seem to be correct, but the pin doesn't toggle. This als

I watched the recent webinar about ST25R3916 to ST25DV charging and saw prototype boards in use in the video demo. Is there a reference design available for these boards? I would like to make a custom version for testing. Thank you for any info or link you can provide.

I have created a UI in touchgfx designer, after I opened CubeMX and based .ioc file from touchgfx designer generate codes for stm32n6.Now I want to build these codes in Cube IDE but get this Error .   Errors occurred during the build.Errors running builder 'CDT Builder' on project 'STM32N6570-DK-FreeRTOS_Appli'.Cannot invoke "com.st.stm32cube.common.mx.registry.IIdeHelper.getRootProject(org.eclipse.core.resources.IProject)" because the return value of "com.st.stm32cube.common.mx.registry.MxRegistry.getIdeHelper()" is null  

HI, I am using STM32H745BIT6 ST controller in my custom board.Configured in Direct SMPS mode. When the board is powered on the VCAP voltage is 1.2V and settling at 1V as expected when we try to flash the program to controller the voltage is same, but when we are trying to enter into debug mode the voltage is dipping from 1V to 0.6V and after 5uS its coming back to 1.2V.( Image is attached for reference)Due to this issue, I am not able to enter to debug mode controller is getting disconnected and showing the pop-up as TARGET IS LOST. I have taken all the precautions mentioned in datasheet and reference manual.1) Shorting all three VCAP pins.2) Connected two 2.2uF capacitor near to the pins.3) Even tried with higher capacitor value.4) Checked the shorts in the pins and board with the help of multimeter.5) The PWR_CR3 register is also set to Direct SMPS mode and verified the last 4 bits as 0100.6) Verified in the IOC that it is configured to Direct SMPS

Hi ST Community,I try to write the OTP Memory on NUCLEO-H563ZI Board with STM_Programmer_CLI (Debian Linux).With STM32CubeProgrammer GUI application I can access OTP memory (beginning 0x08FF_F000).When I try to access the otp memory via CLI:./STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -otp displI receive:Error: OTP programming commands are not supported with STLINK interfaces for this device. With lsusb I can see my STLINK-V3:Bus 001 Device 011: ID 0483:xxxx STMicroelectronics STLINK-V3 But also with the command (port=usb1 or usb0):./STM32_Programmer_CLI -c port=usb1 mode=HOTPLUG -otp displI receive:Error: Target device not found.Establishing connection with the device failed. Do you have any ideas/hints what I am mistaking here?Thanks in advance!

Hello Team,We are using SensorTile.box Pro, and the board has been successfully flashed with the DataLogExtended.bin firmware.However, we are unable to establish a BLE connection with the board, even after flashing the DataLogExtended firmware. The device does not connect via MEMS Studio / BLE application as expected.Could you please confirm if there are:Any known issues with BLE connectivity when using Data Log Extended on SensorTile.box ProSpecific firmware versions or configuration steps required to enable BLEAny additional setup or reset procedure needed after flashingKindly advise on how to resolve this issue.Thank you for your support.Best regards,Ahilesh

Hi all,to evaluate LIV4F and MAX-M10S, I use Mikroe "GNSS 9" and "MAX" click boards with a passive antenna (Quectel YEGT001W1AM).While the MAX click board with the MAX-M10S gets a fix in less than one minute, the MAX 9 board with the LIV4F doesn't get a fix. Even when starting with an active antenna to get a fix and then switching to the passive antenna, the LIV4F stops operating. Sporadically, the GSV sentence shows then one or two weak (~20) signals while the MAX-M10S has >10 satellites with signals in the range 20..44.From my understanding of the data sheets, both the LIV4F and MAX-M10S should have similar performance without an external LNA, isn't it?Is there any known issue with the Mikroe GNSS 9 click board?Or a possible misconfiguration of the LIV4F I could fix? 

As the title suggests, I need to integrate manually my neural network C code generated for the first time with st edge ai core (version 3.0.0) into my STM32CubeIDE project .ioc based (versionj 2.0.0). I cannot use X-CUBE-AI neither Cube AI Studio because the first one has been made deprecated and the second one has plenty of bugs. In Cube AI studio, when I try to generate a CubeMX template, I don't why the project is duplicated and gets cancelled when I try to modify the project with CubeMX. I've tried to ask for help for the last problem, but nobody has answered for a solution.I don't know how to integrate my neural network C code for the first time in a STM32CubeIDE project .ioc based, because the documentation of ST edge AI core describes how to upgrade a model already integrated and generated with X-CUBE-AI, but everyone here says to not use X-CUBE-AI and I don't know what to do.I need to use the Neural ART Accelerator (so ll aton library is needed).I'm very dissatisfied for ST edg

Hi,Could you please provide more details about the Stop Detection Algorithm referenced in CDB-ID 200? The documentation we have contains very limited information about this feature.Specifically, we would like to understand:- What is the purpose of the Stop Detection Algorithm?- How does it work?- What are the configurable parameters and their recommended values?Thank you in advance for your support.

hiii,Do you plan to support BLE TMAP on this module? 

Hello,Is it possible to power this board with an external 3.3 volt supply while still having the st-link active for debugging purposes? If not, how else can I debug my firmware? I've looked through the UM2592 for the dev board, but can't seem to nail down my answer. Any advice is appreciated. Thank you.

Hello, In my STM32WBA65 project using FreeRTOS, I tried to create a hot-attach debug configuration.It works OK except for one problem : the RTOS proxy does not know what it is working on, as it seems to rely on the parameter imageFileName in imagesAndSymbols. Since replacing imageFileName with symbolFileName is necessary to get a hot-attach configuration (along with "serverReset": "None"), this is a problem. The problem seems to be that imageFileName has two roles : 1) providing the binary used by the RTOS Proxy and by the loading mechanism and 2) telling the system that we want to load said binary into the target. Is there a way to hot-attach the debugger with RTOS awareness that I missed ?  Below, my launch configuration in launch.json:{ "type": "stlinkgdbtarget", "request": "launch", "name": "Hot Attach", "origin": "snippet", "cwd": "${workspaceFolder}", "serverReset": "None", "imagesAndSymbols": [ { "symbolFileName": "${command:

Hello everyoneI am using a Nucleo H7S3L8 evaluation module am I am trying to get some GPIOs and peripherals to work. I have generated a demo project that toggles a few LEDs and that works. Then I started replacing the GPIO ports (A, B, etc.) and pin numbers in order to get other GPIOs to toggle (I left the rest of the code as-is, really just replaced the letters and numbers). However, I didn't manage to get an output on any of the GPIOs belonging to ports O and P. I tried GPIOO 0 and 4 as well as GPIOP 0-3 and attached the analyzer at CN10 13, 15, 19, 21, 23, 25 with GND at CN10 17 (always one at a time). All these signals do not toggle. Other GPIO banks such as GPIOB and GPIOM work.Are the O and P ports different than the others? Do I miss some special settings? I will later be using the XSPI there, so I will need exactly these pins.I appreciate any help!PS Here are my jumper settings:JP1: not connectedJP2: connectedJP3: only STLK connectedJP5: connected to 3.3 VJP6: not connected

Hello,I am attempting to run a Brushless DC-Flat motor using the STEVAL-PTOOL4A board. However, the system fails right after entering the RUN state, returning an ERROR MC_DP_FAULT (via MC_GetOccurredFaultsMotor1).To resolve this, I tried using the Motor Profiler to identify the exact motor characteristics, but I am unable to establish a connection with the board (see attached screenshot).Motor Characteristics:Nominal Voltage: 12 VDCRated Speed: 10,000 rpmStarting torque: 225 mNmRated Current: 2.18 AWinding Resistance (phase-phase): 0.88 ΩWinding Inductance (phase-phase): 0.331 mHPole Pairs: 7Could you please help me identify the cause of the MC_DP_FAULT error and why the Profiler fails to connect?Best regards,JulesEdit 05/02: I have managed to get the motor running; however, I am still unable to establish a connection to the board via Motor Pilot.

HiWe are developing a product based on the ST25DV-I2C TAG.I noticed that the X-CUBE-NFC4 software module is NRD. Can you suggest any software module that we could use to speed up development?I also tried porting the existing FTM application from ST25NFC_Embedded_Lib_ST25R3911B_1.8.0. I found it very difficult to extract the FTM protocol from this library due to the enormous amount of dependencies. Do you also have a more appropriate FTM sample code to port to our application?BRGilberto

IssueHigher ambient temperatures cause communication malfunctions with XSPI memories.DetailsOur design is heavily adopted from STM32H7S78-DK which also has the same issue described below.The application uses memory-mapped mode for both Flash and RAM as the main operational units. These memories are configured in the bootloader and everything generated using CubeMX. According to the datasheets, all three components (CPU, Flash, and RAM) are specified to operate reliably under the given conditions, and they do function correctly under normal temperatures.The problem arises when the ambient temperature increases from 25°C to 60°C. These temperatures are within the acceptable operating range for all components, as stated in their specifications. Upon reaching higher temperatures, the memories start to exhibit failures. However, further investigation revealed that the issue is not with the memories themselves. When the memories alone are heated, they continue to operate reliably, even at el

Hello,  I am currently looking at the reference designs for STM32WLEx and am interested in board reference STDES-WL5I4IHH. (high band, high power with optimized BOM target for 915MHz/22dBm). As seen on page 6 of:  Data brief - STDES-WL5xxxxx - Reference designs for STM32WL5x and STM32WLEx microcontrollers   When looking at the BOM, the only difference I see between STDES-WL5I4IHH and STDES-WL5I4IHL is the IPD with designator U4. But when looking at the schematics, inductor L3 has no value attached. The BOM states it is 47nH and recommends LQW15AN47NG00. I also checked for STDES-WL5I4ILH which also has 47nH for L3. Is this correct?Do all 3 of these use an L3 inductor with value 47nH?  STDES-WL5I4IHH | Product - STMicroelectronics STDES-WL5I4IHL | Product - STMicroelectronics STDES-WL5I4ILH | Product - STMicroelectronics I am mainly asking this question because when looking at the eval board NUCLEO-WL55JC, there is a switch that changes that i

STM32WL55 BPSK modulation bitrate for transmission and reception. Transmission is mentioned in data sheet is 600 bit/sec, but need to know reception max bit/sec. Is that same 600 bit/sec?

In the documentation on STM32N657X0, it says that the memory must be connected with match length track on the boards.It says:Match length (including BGA package length)- DQS0 with IO0..7 (Byte0), all in 50 mils,- DQS1 with IO8..15 (Byte1), all in 50 mils,- CLK is100 mils from any signal of Byte0 or Byte1- NCS can be CLK +/-700 milsBut I can't find any documentation on "BGA package length".It seems reasonable that the BGA package should be taken into account, since it is 12.8 mm.and a precision of 1.27mm (50 mils) is specified.I hope someone can help me find that documentation.Keld

I'm doing can-bus work with F103 and having a problem I can't figure out.I'm listening for a specific message, it's on a 20ms interval, and then when that message arrives I right away broadcast a new message using the same id but with different data.  To do this I'm setting a flag inside HAL_CAN_RxFifo0MsgPendingCallback and then monitor this flag inside the main loop. If the flag is set I'm calling HAL_CAN_AddTxMessage to send a new message and resetting the flag.  This repeats. Now, everything seems to be working most of the time, but at random times, it can be a minute or several minutes or longer, my messages are not sent for a second or few seconds or randomly sent/not sent for few seconds.  Then everything will go back to normal for a while and then it might get "broken" again.  This will repeat. HAL_CAN_AddTxMessage() is always returning OK. HAL_CAN_TxMailbox[0-2]CompleteCallback() are not being called when I notice the failures. There are 3 other n

Hello,I am working with a custom PCB using STM32H745XI6 (dual core CM7 + CM4).I wanted to boot only the CM4 core.So, in STM32CubeProgrammer --> Option Bytes --> User Configuration:I unchecked BCM7 (CM7 boot disabled)BCM4 remained enabledI clicked ApplyThe operation completed successfullyNo mass erase warningNo security warningNo RDP Level 2 warningRDP was never changed manually.Problem After ApplyingAfter applying the option bytes, I can no longer connect via ST-LINK.STM32CubeProgrammer shows:Error: Unable to read device id from ROM tableError: ST-LINK error (DEV_CONNECT_ERR)Error: Cannot identify the deviceEven in:Under Reset modeHardware reset modeHot Plug mode50 kHz SWD frequencyConnection always fails.What I Have Already TriedConnect under reset (holding NRST manually)BOOT0 high and lowVery low SWD frequency (50 kHz)Hot Plug modeHardware reset modeDifferent USB cableST-LINK V3SET firmware is detected correctlyI also even tried with J-link  Target voltage is ~3.2Vacc

With HPDMA configured for SAI1A, no DMA setup code is generated with CubeMX 6.17.0. See attached IOC file as an example. Possible that I'm missing a required setting, but I can't find anything.Edit: Fully deleting and re-creating project seems to have fixed it :shrug:.

Hello,We have been using CANbus as our form of communication for a system with multiple nodes. Each node was individually tested with CAN and all of them work without issue. However, when we started system integration testing, we noticed significant noise on the CANbus channel that caused data to stop. To give more details, we are running 2 battery packs, a power electronics DC/AC converters (to create a 120Vac signal) and a central supervisory controller, which are all using STM32 MCUs to communicate to each other via CANbus. We are using an STM32H7AGI6, STM32F401RE, STM32F303RE. When we send a CANbus command to start the DC/AC converter, that is when the noise appears and we cannot communicate with the MCUs until the DC/AC converter is turned off. We have termination resistors at the end of the bus and I have verified that the 60 Ohm resistance is seen on the bus. I've also attached a copy of our schematic for the CANbus, which all of the nodes use (except that the 120 Ohm

Hi,Have this working on STM32F302R8 but cannot seem to get my SD Card working on an STM32F446RE. Using hal 0.23.0 with stm32F446 and embedded-sdmm 0.9.0); let sd_mosi = gpiob.pb15.into_alternate::<5>(); let sd_miso = gpiob.pb14.into_alternate::<5>(); let sd_sck = gpiob.pb13.into_alternate::<5>(); let mut sd_spi = Spi::new( dp.SPI2, (Some(sd_sck), Some(sd_miso), Some(sd_mosi)), Mode { polarity: Polarity::IdleLow, phase: Phase::CaptureOnFirstTransition, }, 400.kHz(), &mut rcc, ); let sd_spi_dev = ExclusiveDevice::new_no_delay(sd_spi, sd_cs).unwrap(); rprintln!("Reading file..."); let num_bytes = sdcard.num_bytes().unwrap(); rprintln!("SD Card Size: {} bytes", num_bytes);Which gives[2026-03-01T05:30:04.085Z, +020837ms] panicked at both_test/src/main.rs:184:40: [2026-03-01T05:30:04.085Z, +020837ms] called `Result::unwrap()` on an `Err` value: CardNotFoundVery new to all this but certain of wiring. The SD Adaptor has an Ams117 chip but I have tried in