Product forums

Hello,I am currently experiencing some unusual Ethernet transmission (STM to PC) issues with a few of our custom PCBs. We use the STM32H753II chip and the KSZ8081RNB. The KSZ8081RNB is connected to the MCO2 and the RMII-interface of the STM.The IP/TCP/UDP checksum check primarily fails due to corrupted payloads ranging in size from 1 to 20 bytes, or, more rarely, due to corrupted protocols. It doesn't happen regularly, but it happens too often.This means that, for TCP, two or more retransmissions are sometimes needed.udp bad:udp good:

Hi! I'm working on setting up FDCAN communication using the STM32N6570X0-Q Nucleo Board. However, when I try to modify the bit timing parameters—such as the Nominal Prescaler, Nominal Time Seg1, or Seg2—the baud rate doesn't seem to change regardless of the values I set.On the receiving side, I'm using a STM32H533RE Nucleo Board to echo the messages, but it doesn't receive anything—so I suspect the issue may be with the timing configuration on the N6570X0-Q.Do you have any idea what might be causing this behavior?Thanks in advance! 

So, I was showing some friends in England how to use the Sensor TileBox Pro to measure a building, using the modified CLI_EXAMPLE program.  So starting analysis, the X axis now representing gravity vector in the table, I knew I had the box sitting on its side in a slot in the column, so if I am looking at the box, I was wondering what axis system matched the box and the unit.  Your data sheet showsThe whit dot is important

Hello, stm32h7b3lih6q controller has support ethernet connection give me proper solution I want the Communication in beteen Ethernet and Controller. Thanks.

We had three Sensor TileBox units. In an interesting morning of work, I got the one I have in the USA running, in the hope that the people in the UK who have them could use them.  I got it running, during the reading to get it running, I found a note in one of the PDF files that said the CSV files would be padded to the highest ODR.  First time I had actually seen that other than in a ST reply.  The TileBox recorded nicely once I worked out the boot key, which is one of three buttons and the PDF does not show it that I could find.  I knew I had seen it once, but I could not find it.  I enjoy playing with the combinationsThe CLI_Example program worked nicely.  The sample files json files were challenging. Following the instructions, it proved difficult, I could not do transfer the data to CSV, Unicleo GUI did not help as suggested.  Anyway we are throwing them away, but it was some fun. &nb

Hi Team, Greetings! Mems studio is used and LSM6DSV320X is kept on the sensor tile box pro, We are currently performing drop tests using the SensorTile Box pro platform mounted on a flat board casing. The tests are conducted from the same height under two configurations: Wired mode with an ODR of ~7.6 kHzWireless mode with an ODR limited to ~1 kHzWhile analyzing the accelerometer (high-g) data, we observe a variation in peak acceleration values of approximately ~20 g between different runs, even though the drop conditions are kept identical.We would like to understand the following:Is such a variation (~20 g) in peak acceleration expected under these conditions?Could the difference in ODR (7.6 kHz vs 1 kHz) significantly impact the captured peak values for short-duration impact events?Are there any known limitations in wireless mode (e.g., filtering, bandwidth constr

Hello ST Community,I am working on the NUCLEO-N657X0-Q board with a TrustZone project configured in STM32CubeMX with three contexts: FSBL, AppSecure (AppS), and AppNonSecure (AppNS). The FSBL is working correctly and jumping to AppS successfully. I followed the wiki article "How to start with RIF on STM32N6 MCUs" as reference. https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_RIF_on_STM32N6_MCUs The secure LED (configured as output push-pull, pulled low initially) turns ON but never toggles. I have tried both HAL_Delay() and a pure software loop  for (volatile uint32_t i = 0; i < 800000; i++);  inside the

I am working with the STM32L4S5VIT6 and currently facing an issue while trying to communicate with the system bootloader over USART. I am using the B-L4S5I-IOT01A Discovery board, on which I am attempting this setup. I have configured BOOT0 correctly and verified that the MCU enters boot mode (the application stops running as expected). I connected USART2 on PA2 (TX) and PA3 (RX), tried swapping TX/RX lines, and also interfaced through a MAX3223 level shifter to a MOXA device, but the STM32CubeProgrammer still reports a “KO – device not responding” error. I have confirmed that the MCU runs user code correctly (LED blink test), so basic functionality is intact. At this point, I suspect either a configuration misunderstanding from AN2606, incorrect peripheral mapping for this specific MCU, or a hardware-level issue with the UART path. Has anyone faced a similar issue with STM32L4 series bootloader communication, or can help clarify the exact USART instances/pins supported in boot mode

Hi everyone,I am working with the NUCLEO-U385RG-Q (MB1841) and I've noticed an inconsistency in the UM3062 user manual, specifically in Table 18 (ST Morpho connector pin assignment).The documentation states that PB7 is available on the Morpho connector at pin 5 of CN10. However, in the standard factory configuration, this does not seem to be the case. It appears that the connection depends on the solder bridge (SB) configuration, but the manual is not explicitly clear about the default state for this specific board variant.This makes the pinout tables quite confusing at a glance.Could you please tell me where I made a mistake and are there any other reliable sources of information about the pinout connections for this Nucleo board?Thank you in advance for information.

Hi, I was trying to create a small 8x8 / 4x4 point cloud using a VL53L5CX sensor, and I can get the depth data for each zone, but I was wondering if there was a way to get x,y,z from this information? Like if there was a way to know the vertical and horizontal angle for every zone on the VL53L5CX and then calculate the x,y,z location of the points using that and the depth data. Any help would be appreciated!

Dear community, I've used yocto as my workhorse in the past a lot for other processor manufacturers. Now as I'm happily joining the STM world for linux I'm stuck. Maybe it is a too easy to miss question, but which steps I have to take for putting all the needed images to the sd-card? I have followed the rules to go for using the create_sdcard_from_flashlayout.sh script with FlashLayout_sdcard_stm32mp257f-dk-optee.tsv as the parameter. After that I've used dd to flash the .raw to the designated sdcard but the board does not start at all. From the provided sdcard it starts without any issue.Where is my mistake? Regards KS

I am currently working with the X-NUCLEO-NFC10A1 board and interfacing it with an ESP32 DevKit V1. While attempting to establish communication between the two, I have tried all SPI modes as well as different reset logic configurations, but I am still unable to get them to communicate properly.I have included my Arduino test code below for reference, which I am using to verify the communication:Please check in attachment section there is code file

Hi everyone, I am developing an application for the NUCLEO-H7S3L8 kit using VS Code with the STM32 VS Code Extension. I have successfully built both the 'Boot' and 'App' projects.Currently, I am struggling with flashing the 'App' project firmware into the external Flash memory. In STM32CubeIDE, selecting an External Loader (.stldr) is very intuitive within the Debug Configuration, but I haven't found the equivalent setting in VS Code for the STM32H7RS series.Could you please guide me on how to configure VS Code to recognize the External Loader and the proper workflow for flashing code to external memory for this specific MCU?PS: On STM32cubeIDE, I'm referring to this example: https://github.com/ST-TOMAS-Examples-ExtMem/stm32h7rs_ospi/tree/main. Now

Hello,I've been struggling with this issue for a couple days, I have a Nucleo-L476RG board that I am trying to run and debug in VS Code. I'm using the STM32CubeMX + STM32 VS Code Extension tool chain to create cmake files, build, and then debug, but I cannot run and debug code due to an error:Error in initializing ST-LINK device.Reason: ST-LINK firmware upgrade required. Please upgrade the ST-LINK firmware using the upgrade tool.I have tried using the "Upgrade ST-Link Firmware" button in the VS Code Extension "STM32Cube Devices and Boards Menu" and I get the following error:Fatal error while trying to update STLink Firmware. Source: STM32Cube Debug CoreSo I installed STM32CubeProgrammer and tried to upgrade firmware from there. I get the following information about my device:Serial Number: 066AFF485671664867215448Firmware Version: V2J43M28When I select

On Kubuntu 24.04 when double clicking onSetupSTM32CubeProgrammer-2.19.0.linuxan empty window appears and then closes again. If I runSetupSTM32CubeProgrammer-2.19.0.linuxvia the terminal (as admin or as user), I get this error:Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at sun.awt.X11FontManager.getFileNameFromPlatformName(X11FontManager.java:174) at sun.font.SunFontManager.initCompositeFonts(SunFontManager.java:3506) at sun.font.SunFontManager.access$800(SunFontManager.java:65) at sun.font.SunFontManager$2.run(SunFontManager.java:555) at java.security.AccessController.doPrivileged(Native Method) at sun.font.SunFontManager.<init>(SunFontManager.java:386) at sun.awt.FcFontManager.<init>(FcFontManager.java:35) at sun.awt.X11FontManager.<init>(X11FontMan

Is it possible to get pretty-print support for data-structures and custom types? It seems that not even STL types (e.g. std::vector) can be inspected easily by default: std::_Vector_base<int, std::allocator<int> > = {...} std::_Vector_base<int, std::allocator<int> > = Variable object not foundThis is all that is shown for a std::vector<int>.Looking into this, it seems that GDB can do this via python-based pretty printers, which even seem to be available for for the libstdc++ bundled with the IDE, e.g. "/opt/st/stm32cubeide_1.19.0/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.14.3.rel1.linux64_1.0.0.202510151430/tools/arm-none-eabi/lib/thumb/v7e-m+fp/hard/libstdc++.a-gdb.py"However, Python support seems t

Hi everyone,I am currently facing a very frustrating issue while trying to interface an AP Memory APS51208N (Octal PSRAM) with an STM32H723 via the OctoSPI peripheral.To avoid reinventing the wheel, I recently refactored my initialization code to use the official ST aps512xx library (https://github.com/STMicroelectronics/stm32-aps512). I'm using read and write latency set to 7.Unfortunately, the peripheral is still not working properly, and I am experiencing three distinct, highly erratic behaviors:1. Weird Register Read Pattern When I try to read the memory control registers using the BSP functions, the returned values are incorrect and seem to form a repeating sequence rather than actual register data. Here is what I get for MR0 to MR8:Array[0] (MR0) = 0x08

Hello everyone, I recently encountered a strange BUG.I use DMA to transfer ADC data. Previously, this program was configured this way without any problem, but it suddenly doesn't work these two days. What's even stranger is that I used STlink in the IT file to HAL_DMA_IRQHandler(&hdma_adc1); Break point. The value can be read out during debugging, but the serial port still doesn't work.The development environment is CubeIDE1.18.1

I created an independent task to run the TCP client and send.[424] local 192.168.10.188 port 5001 connected with 192.168.3.100 port 57804 [ ID] Interval Transfer Bandwidth [424] 0.0- 1.0 sec 5660 KBytes 46368 Kbits/sec [424] 1.0- 2.0 sec 5500 KBytes 45055 Kbits/sec [424] 2.0- 3.0 sec 5389 KBytes 44149 Kbits/sec [424] 3.0- 4.0 sec 5191 KBytes 42526 Kbits/sec [424] 4.0- 5.0 sec 5088 KBytes 41681 Kbits/sec [424] 5.0- 6.0 sec 4936 KBytes 40436 Kbits/sec [424] 6.0- 7.0 sec 4832 KBytes 39583 Kbits/sec [424] 7.0- 8.0 sec 3816 KBytes 31258 Kbits/secThe above is the data volume and status received by my iperf server. After that, my client task no longer sends any messages. I use my computer to ping the IP address of my STM32, and then the client will resume sending.I observed that the gState of my heth variable is HAL_ETH_STATE_STARTED, and the ErrorCode is

Dear ST Team,I use multiple versions of CubeIDE and would appreciate it if the currently running IDE version could be displayed in the following screens (somewhere).Thank you

Good morning,I currently have my final design ready but I am struggling to understand the meter calibration setup in AN4470. Below are images of how to setup to meter a load as per UM2066 and also how to setup the meter for calibration as per AN4470.My main source of confusion is where a load will be applied during the calibration process. If my device is currently setup as Figure 16, do I simply replace the isolated source with the precision current and voltage source (Gen) and leave my load as is?Then I calibrate based on what the readings on the source are (assuming it is precise and I am not using a higher class precision energy meter - HPM). Thanks in advance!-J 

The output of TIMX_CH1 and TIMx_CH1N is decided by previous value before bits 6:4 changed to Frozen mode? 

Dear all I was setting up the RISAF4 for STM32MP257, however, the partition with name "linuxkernel2" has a glitch where its size shows as givenWhich is beyond the size of my LDDR4 set to 8Gb.How to solve it? A quick reply will be appreciated.Thanking you!With regardsAmit 

HiInitial situationMCU = STM32U599VJTxQSTM32CubeIDE = v1.19.0TouchGFX = v4.26.0EEPROM Emulator = x-cube-eeprom-v8-0-0 (downloaded direct from STM website)I use the eeprom emulator to save an array of 251 bytes permant on the flash. To save the data into the flash I use the EE_WriteVariable32bits functionThis are my function to init the EEPROM emulator, write data to EEPROM and read data from EEPROMvoid Datastore::EEPROM_Init() { HAL_FLASH_Unlock(); // 1. Flash freigeben // 2. Sicherstellen, dass Flash idle ist uint32_t timeout = 1000000; while(__HAL_FLASH_GET_FLAG(FLASH_FLAG_BSY)) { if(timeout-- == 0) { HAL_FLASH_Lock(); this->m_errorHdl_p->Add(ERR_ID_EEPROM_INIT_FAILURE); return; } } // 3. C

Hi friends, Does have processors from this family a dedicated input pin as the the input for inner LDO? It will be in the future to supply the inner LDO with the voltage Vcc/2 from the splitter like LM2665 or other. best regards zbynoB