Solved

Hi ST community,I create a simple application using USART1 baudrate 9600 TX pin - PB6 & Rx pin - PB7. I send uart frame each 1 second. J22 connects to CP210x. I see that the RX led of CP210x toggle each 1 second but when I open terminal screen on the laptop with same baudrate, nothing is shown. HAL_transmit return HAL_OK. Tx pin and Rx GPIO pin is configured as default, no pull up and pull down. What is problem here?  void SystemClock_Config(void) { RCC_OscInitTypeDef RCC_OscInitStruct = {0}; RCC_ClkInitTypeDef RCC_ClkInitStruct = {0}; /** Configure the main internal regulator output voltage */ if (HAL_PWREx_ControlVoltageScaling(PWR_REGULATOR_VOLTAGE_SCALE3) != HAL_OK) { Error_Handler(); } /** Configure LSE Drive Capability */ HAL_PWR_EnableBkUpAccess(); __HAL_RCC_LSEDRIVE_CONFIG(RCC_LSEDRIVE_MEDIUMHIGH); /** Initializes the CPU, AHB and APB buses clocks */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI48|RCC_OSCILLATORTYPE_HSI |RCC_OSCI

The data sheet for the G474RE says it has a Memory Protection Unit. The article on how to enable/configure it in STM32CubeMX shows a CORTEX_M# node under "System Core". I don't see that node. Thank you.

JW 

I am using sr6p3e and I tried to access Gicr registers but I got aport exception, I tried several things like check if clock control the module and if there is a protection registers but I didn't find anything, I know that it use axim for interface so I tried to write on another module GTM registers after making necessary configuration but I got sameh issue I check the startup code coming with mcal and found it configure mpu for Gicr and prephiral section and when I apply it in my code it solve the issueI don't need to use mpu, is there another way to access Gicr and gtm ?

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 fo

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.

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

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 the "Firmware Upgrade" button, it says Device 066AFF485671664867215448 not found. No device connected.So I downloaded th

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>(X11FontManager.java:57) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62

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. Critical Section / Interrupts kurz maskieren __disable_irq(); // 4. EEPROM Init mit Retry EE_Status status = EE_WRITE_ERROR; const uint8_t max_retries = 3; uint8_t attempt = 0; while(((status != EE_OK) && (status != EE_PAGE_FULL)) && (attempt &l

There are 4 external events that can be chosen to trigger and reset individual counters of each HRTIM timer unit in STM32H743 MCU. CubeMX shows those events once the Event Configuration is chosen "Enabled" . Yet only Source 1 is active (allowed to be chosen) but the Source 3 that I need to connect internally to the TIM2 TRGO output is inactive (cannot be chosen) . Why? My attempts to use AI got strange results - after searching the STM documents AI concluded that CubeMX is limited , it allows only external on-pin connections and any internal connections must be manually coded in addition to the generated code. If it is so then why does CubeMX show those other options yet does not allow to choose them? Or is there way to activate those options ?Please anybody give me suggestion.Note: the STM32CubeMX is the latest downloaded and installed yesterday. The MCU library pack is also current. 

Hello,I recently made a custom PCB with the teseo-liv4ftr for an avionic and i have trouble making it work. The module responds to the nmea commands via I2C, but I couldn't get a fix whatsoever and not even a signal on the PPS pin.The Teseo is soldered correctly and with a proper LDO power supply. Also, I am using a Taoglas active antenna (AP.25M.07.0080A).Can anybody please help me?Schematic of the design attached below.

Hi,when selecting the STM32C051K8 in Cube MX it seems that CubeMX has wrong configs/specs about it?As you can see from the screenshot below it shows it is a LQFP package but - unless I missed something - it is supposed to be a UFQFPN32 package.The main issues are...1) when searching for micros with that package, that micro does not appear2) not sure if the entire CubeMX generated code is somehow affected? Firth thought is that it is just a package difference but the pin count is the same so perhaps it is ok, but perhaps not? Point #2 is the most important at the moment. Could someone form ST please guarantee we can use CubeMX to configure the part?Many thanks  

Hello STM32 Community,I am currently developing a USB Type-C Active Cable application using an STM32 with the official USB-PD Middleware.My Goal: The MCU needs to behave as an EMarker/Active Cable. Therefore, it should:Ignore all SOP messages on the CC line (no response and no GoodCRC ).Only respond to SOP' and SOP'' messages.Able to monitor (Snoop) SOP messages exchanged between the Source and Sink to maintain state awareness.The Problem: In the current X-CUBE-USB-PD middleware and STM32CubeMX configuration, there is no explicit option to disable SOP handling while keeping SOP'/SOP'' active. Since GoodCRC is typically handled by the UCPD hardware autonomous logic to meet the strict tTransmitSOP timeout, the hardware automatically sends a GoodCRC when it detects a valid SOP message CRC, even if the firmware isn't intended to process it.Technical Details & Questions: I am looking for a way to bypass or disable the hardware-level auto-response for SOP only.Register Control: Is there

In ds H5E5 is given:  3x 12b ADCbut on selector is shown:...so secret 3 x 16b ADC there - or error in table ?  

Hello,I am planning to use the TLV320AIC23B audio codec with the STM32H7B3LIH6Q controller.Kindly confirm:Is TLV320AIC23B compatible with STM32H7 (using SAI/I2S for audio and I2C for control)?Any specific requirements for clock (MCLK) or configuration to ensure proper operation?Thanks.

Hello everyone,   i want to build a CAN FD network with three NUCLEO-C092RC boards. So far i can transmit frames, as i can see on an oscilloscope. But the moment i connect TWO boards, the interrupt is not triggered. My code should activate user LED2 if it receives a frame with one specific id: Board 1 (0x101) triggers LED when receiving message 0x344 or 0x234 Board 2 (0x234) triggers LED when receiving message 0x344 or 0x101 Board 3 (0x344) triggers LED when receiving message 0x101 or 0x234   i use a nom. baudrate of around 500 kbit/s and data baudrate of 1 Mbit/s with a clock of 40 MHz (HSE). The Boards are connected with two short (10cm) twisted jumper cables and the jumpers for the 120 Ohm resistor are also plugged in on both baords. when i test it in external loopback mode, it works (with ident. change) Could this just be a problem with my wires (reflexion , parasi. C ,etc.)?   thanks a lot for the help

In STM32CubeMX, here is the orientation for a chip with a red dot marking pin 1 at the top left when text reads from left to right.In real life, here is the orientation for a chip with a red dot marking pin 1. As far as I'm aware, all STM32 chips are oriented like this, with pin 1 at the bottom left when text reads from left to right. Why is the text rotated 90 degrees differently? Is this intentional? If there is a reasonable explanation, I'm interested in hearing it. It seems to only add confusion. Wouldn't it make more sense if the default orientation (or at least the text orientation) to match between the two? In STM32CubeMX, you can rotate the part for convenience. This is useful. However, the text also rotates, so if you put pin 1 in the bottom left like in reality, the text is now rotated. (This is the same story in STM32CubeMX2.) 

Hello,I am using X-CUBE-EEPROM as a mean to store variable in internal FLASH memory on STM32U5G9-DK2 board. Here is my function where a variable in flash:static FLASH_STATUS flash_slot_write_shared_key(const FLASH_INDEX *index, uint8_t slot, uint8_t *shared_key) { if (slot > FLASH_SLOTS_NUMBER) return FLASH_WRONG_PARAM; if (shared_key == NULL) return FLASH_NULL_PARAM; EE_Status ee_status = EE_WRITE_ERROR; HAL_FLASH_Unlock(); taskENTER_CRITICAL(); ee_status = EE_WriteVariable96bits((uint16_t)index->entries[slot].addr, (uint64_t *)(shared_key)); if (ee_status != EE_OK) return FLASH_ERROR; ee_status = EE_WriteVariable96bits((uint16_t)index->entries[slot].addr + 1, (uint64_t *)(shared_key + 12)); if (ee_status != EE_OK) return FLASH_ERROR; ee_status = EE_WriteVariable32bits((uint16_t)index->entries[slot].addr + 2, *(uint32_t *)(shared_key + 24)); if (ee_status != EE_OK) return FLASH__ERROR; ee_status = EE_WriteVariable32bits((uint16_t)index->entries[

The STM32MP135 is powered by PMIC1A. After initial power-up, the voltage at BUCK4 is normal at 3.3V, but during U-Boot flashing, the output voltage at VOUT4 drops to only 2.4V, causing the flashing to fail. The VDD and VDDQ pins of the eMMC are powered by the same power rail, VOUT4.

I am trying to understand one point in the official VL53L8CX datasheet.In the pin description table, pin C5 (MISO) is described for SPI as:“SPI: Main input secondary output. Push-pull output, driven to IOVDD level.”But in Figure 6 (“Typical application schematic for SPI”), the MISO line seems to have a 47 kΩ pull-down resistor to GND.I attached two screenshots:1. the table entry for C5 / MISO2. the SPI typical schematic with the suspected 47 kΩ pull-down highlightedMy question is: how should this be interpretedcorrectly?Does ST mean that MISO is a push-pull output, but an external weak pull-down is still recommended as a default line state? Or is this schematic being misread, and that 47 kΩ resistor actually belongs to another signal?I would appreciate clarification from anyone who has used VL53L8CX in SPI mode or has already resolved this ambiguity.

Hello,I think I have interesting case, but from the beginningI use STM32F446ZEJx and HAL Drivers from STM32Cube_FW_F4_V1.28.3.When I use HAL_StatusTypeDef HAL_SPI_TransmitReceive_DMA(SPI_HandleTypeDef *hspi, const uint8_t *pTxData, uint8_t *pRxData, uint16_t Size)with Size=5 it internally checks the argumentif ((pTxData == NULL) || (pRxData == NULL) || (Size == 0U)) return HAL_ERROR;and passes the Size to/* Set the transaction information */ hspi->ErrorCode = HAL_SPI_ERROR_NONE; hspi->pTxBuffPtr = (const uint8_t *)pTxData; hspi->TxXferSize = Size; hspi->TxXferCount = Size; hspi->pRxBuffPtr = (uint8_t *)pRxData; hspi->RxXferSize = Size; hspi->RxXferCount = Size;later it configures the DMA channels,Rx/* Enable the Rx DMA Stream/Channel */ HAL_DMA_Start_IT(hspi->hdmarx, (uint32_t)&hspi->Instance->DR, (uint32_t)hspi->pRxBuffPtr, hspi->RxXferCount)Tx/* Enable the Tx DMA Stream/Channel */ HAL_DMA_Start_IT(hspi->hdmatx, (uint32_t

Is there a guide that shows how to set up a CDC USB device on the STM32N6 without using ThreadX in baremetal mode?   I've tried following both, but it seems to hardfault on both examples crash at __lib_init_array(). I've tried increasing the stack and heap sizes to no success:https://community.st.com/t5/stm32-mcus/how-to-use-stmicroelectronics-classic-usb-device-middleware-with/ta-p/599274    https://community.st.com/t5/stm32-mcus/how-to-implement-usbx-in-standalone-mode/ta-p/614435    It's frustrating that the old USB_Device middleware got removed. We shouldn't be forced to use an RTOS where it is not needed...

Hello,I am using STM32H7B3LIH6Q and planning to interface a TFT display via LTDC (RGB interface). I am considering the following options:NHD-4.3-800480CF-ASXP (4.3", 800×480, RGB)NHD-4.3-480272EF-ASXP (4.3", 480×272, RGB)NHD-3.5-320240JF-ASXP (3.5", 320×240, RGB)Kindly suggest:Which TFT is most suitable for STM32H7 in terms of performance and ease of integration?Is 800×480 the preferred resolution for LTDC + TouchGFX applications?Do these RGB TFT displays support HDMI interface directly?If HDMI output is required, is using an external RGB-to-HDMI bridge (e.g., ADV7511) the correct approach?Thanks.