Solved

Hi everybody.I'm currently trying to use the N6 Nucleo for a personal application but am having trouble starting the debugger after initially successes. I am using the Nx_TCP_Echo_Server example, and after a couple of successful iterations my debugger stopped working entirely.I am using the VSCode extension. When I start my debug session with ST-Link GDB server it will connect to the debugger, but an error will follow in the terminal as shown ("target not responding"). After disconnecting and re-initializing the debugger I will get the following error ("error in intializing... please check power"). I get the same issues after power-cycling the board. LED 2 (Red) will then remain off until I power cycle the board after the first error.Previous issues led me to believe I re-wrote the SWD lines so I connected BOOT0 to 3.3V and used the CubeProgrammer to perform a chip erase. Specifically for the external memory since to my knowledge the N6 doesn't maintain internal memory. After the chip

Hello everyone,this is my first time building an STM32 Based Board myself.I am trying to talk to the Chip Using a CP2102 UART Bridge connected to PA9 & 10.For Reset and Boot 0 ive connected Reset (NRST) to RTS of the UART Bridge and Boot0 to its GPIO0 Pin and configured that Pin in the Bridge. I have however also tried just pulling Boot0 High and Jumping NRST to GND and then immediately connecting using STM32CubeProgrammer.Using an Oscilloscope ive found that the Magic Packet is sent to the STM32 (0x7F, 115200 Baud, Even Parity, 1 Stop) but there is no response (Tx of the STM32 stays high all the Time).PB15 is left floating, I am using the VIT6 Variant (The LQFP100 Package), its a Brand new Chip, is there any configuration required before this works?

When using a Zephyr RTOS host with PAwR synchronization response enabled, the STM32WB09 controller (observer role) reports a legacy LE Periodic Advertising Report (subevent 0x0F) while syncing to a PAwR broadcaster.The broadcaster is implemented on EFR32BG42 (SiLabs). Zephyr host reports:[00:00:02.987,453] <dbg> bt_hci_core: hci_event: event 0x3e[00:00:02.987,480] <dbg> bt_hci_core: hci_le_meta_event: subevent 0x0f[00:00:02.987,497] <err> bt_scan: The controller shall raise the latest unmasked version of the eventWhich corresponds to:LE Meta EventLE Periodic Advertising Report (legacy) The Zephyr BLE controller layer is based on stm32wb0x_ble_stack_controller_only.aDoes stm32wb0x_ble_stack_controller_only.a support:BLE 5.4 PAwR (Periodic Advertising with Responses) – Observer role?Periodic Advertising Report v2 (with subevent context)? 

I am looking for an EEPROM device that has the UID but also supports the 256-byte identification page.I was lead to believe that densities less than 1M support either/or, but greaterthan/equal to 1M does support both.However, from what I can tell from the datasheet(s), the -F version (M24M01E-F) says: "The device offers an additional 256-byte page, called the identification page. This page can be used to store sensitive application parameters, which can later be permanently locked in read-only mode."But the -F version does not have section 4.5 so it does not have UID.  datasheet for version -U (M24M01E-U) says "The device also offers an additional 256-byte identification page. This page stores a 128‑bit (16‑byte) unique factory-programmed serial number, locked in read-only mode at factory delivery."And in section 4.4 says "This is an additional 256-byte page, permanently locked in read-only mode. The user can read it by issuing the read identification page instructi

Hello,   in an earlier post it was suggested to reset the FDCAN for full error recovery using RCC_APBRSTR1.FDCANRST Bit This bit seems to be global for all FDCAN instances. Is it correct that full error recovery in one FDCAN instance is not possible without interrupting traffic in the other instance - as all (or both in case of stm32g0b1) instances have to be reset?   t

Hello all, Split from this thread: I'm using an STM32U5G9 and I need to read files from a USB stick. I don't want to use ThreadX because I have to keep this application small. How can I achieve this if UsbX and FileX are supposed to be used only with ThreadX and not in standalone mode?   Thanks for your help. Best regards, Julien

Dear community,I am looking for help to have TFM ported for nucleo_u385rg_q so that I can build the tfm secure and non secure images and do a secure boot on this board. The closest board is b_u585i_iot02a which is a stm32u5 variant. But there are many low level code required for this in trusted-firmware-m repo. Is there a work done by someone that I can use for my work? Any pointers as to how to accomplish this. Thanks in advance for your support.

Hi,How do I serve request Get Source Capabilities Extended? I'm using STM32G0B1 with a port configured as SRC.When a SINK sends the Get Source Capabilities Extended the STM PD library responds with 'Not Supported' and my code is not aware that this even did happen. Is there way to intercept and serve this request? At least the callback structure does not appear to have direct support for this. USBPD_DPM_ExtendedMessageReceived is never called. /* CAD callback definition */ static const USBPD_PE_Callbacks dpmCallbacks = { USBPD_DPM_SetupNewPower, USBPD_DPM_HardReset, USBPD_DPM_EvaluatePowerRoleSwap, USBPD_DPM_Notification, USBPD_DPM_ExtendedMessageReceived, USBPD_DPM_GetDataInfo, USBPD_DPM_SetDataInfo, USBPD_DPM_EvaluateRequest, USBPD_DPM_SNK_EvaluateCapabilities, USBPD_DPM_PowerRoleSwap, USBPD_PE_TaskWakeUp, #if defined(_VCONN_SUPPORT) USBPD_DPM_EvaluateVconnSwap, USBPD_DPM_PE_VconnPwr, #else NULL, NULL, #endif /* _VCONN_SUPPORT */ USBPD_DPM_EnterErrorR

Hello all,There might be a possible bug in HAL_UART_DeInit(). When calling HAL_UART_DeInit() when it is already initialized could lead to CPU starvation. Assume that an interrupt fires after calling __HAL_UART_DISABLE(huart); and before huart->Instance->CR1 = 0x0U; the interrupt is going to keep firing provided that some conditions are met. I was able to run a debug session and saw that only the interrupt was firing.From the ref. manual -> Note: If TE bit is reset and no transmission is on going, the TC bit is immediately set.This means that the TC bit is always going to be set and the interrupt is constantly going to fire regardless of clearing the TCF in ICR. The reference manual also mentions to ensure TC bit is being set before calling  __HAL_UART_DISABLE(huart).I am running into this issue when TE is reset and TXIE is set after calling  __HAL_UART_DISABLE(huart). This happens extremely rarely but I am able to reproduc

Looking for something to try. I'm want to recover from a failed firmware update of an MLite-880 from Elecevolve after their their 1-click installer. Elecevolve suggested a manual install using the firmware binary and STM32CubeProgrammer. I can put the device in its "DFU FW update mode" and connect to the device from the STM32CubeProgrammer using USB. After connect, the log shows:08:45:07 : STM32CubeProgrammer API v2.22.0 | Windows-64Bits08:45:35 : Disconnected from device.08:46:01 : USB speed : Full Speed (12MBit/s)08:46:01 : Manuf. ID : MALAHITEAM08:46:01 : Product ID : Malahit-Lite DFU08:46:01 : SN : 305B376E313308:46:01 : DFU protocol: 1.108:46:01 : Board : --08:46:01 : IAP08:46:01 : UPLOADING ...08:46:01 : Size : 1024 Bytes08:46:01 : Address : 0x800000008:46:01 : Read progress:08:46:01 : Data read successfully08:46:01 : Time elapsed during the read operation is: 00:00:00.053When I click Start Programming, literally nothing happens except the progress bar at the bottom previous

Hi everybody.I have a problem with my Arduino GIGA R1  + Giga Display shield, configured by CubeMX. I configured the external RAM and flash and it works fine. I also successfully configured TouchGFX.My only remaining problem is the startup of the board. When I power it up, it doesn't boot. Even the ST-Link can't see the MCU. I must start it with BOOT_O at 0 (there is a button on the board) and it enter in bootloader mode and the DFU connection works. I can then connect the programmer, flash the Arduino firmware and after that, I can program/debug via ST-Link, I can reset it it still working. I verified the BOOT_ADDRESS it's on the good memory and not changed by Arduino firmware. As it work under reset, I presume memories are well configured.I can't find what could prevent the core to start. Both core start well on reset (verified with onboard LEDs) but nothing happen on power on. Does anyone have an idea of what could fail  or give me some hints on what to look

I have installed version  13.3.rel1, clean the files and re compile the code :I have a linker error "undefined reference" to a function although the function referenced in the files and declared in the H file who was included.  " C:/ST/STM32CubeIDE_2.0.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3.rel1.win32_1.0.100.202509120712/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe: ./Core/Src/stm32u0xx_hal_msp.o: in function `HAL_PCD_MspInit':C:/Users/../Electronics/../Software/USB_CDC_U0/USB_CDC_U0/Debug/../Core/Src/stm32u0xx_hal_msp.c:102:(.text.HAL_PCD_MspInit+0x4c): undefined reference to `MX_USB_CDC_Init'collect2.exe: error: ld returned 1 exit statusmake: *** [makefile:65: USB_CDC_U0.elf] Error 1"make -j12 all" terminated with exit code 2. Build might be incomplete.15:33:51 Build Failed. 2 errors, 0 warnings. (took 13s.995ms)I have tried the following:1. I have tried changing the file order in "

I am working with the MDF peripheral and find this to be a great peripheral. However the CubeMX generated code for multiple DMA based filters is not correct.I am using two filters with DMA and CubeMX generates the following descriptors:MDF_HandleTypeDef MdfHandle0;MDF_FilterConfigTypeDef MdfFilterConfig0;MDF_HandleTypeDef MdfHandle1;MDF_FilterConfigTypeDef MdfFilterConfig1;DMA_NodeTypeDef Node_GPDMA1_Channel1;DMA_QListTypeDef List_GPDMA1_Channel1;DMA_HandleTypeDef handle_GPDMA1_Channel1;DMA_NodeTypeDef Node_GPDMA1_Channel0;DMA_QListTypeDef List_GPDMA1_Channel0;DMA_HandleTypeDef handle_GPDMA1_Channel0; When starting the application I found that both MdfHandle0 and MdfHandle1 refer the same DMA handle,  handle_GPDMA1_Channel1. Likewise both handle_GPDMA1_Channel0.Parent and handle_GPDMA1_Channel1.Parent refer the same filter handle,  MdfHandle0.This is caused by generated function HAL_MDF_MspInit which is called when starting a filter using HA

hello ST Community, Is it possible to change the RDP "Read Out Protection" level from level 1 to level 0 without erasing the flash data? I've currently been able to change the level from RDP level 1 to level 0 for Nucleo-H755ZI-Q, but changing the level causes a mass erase of the flash drive. Is it possible to avoid this? If so, is there a code example? Thanks for your support.

Hello,I am working on the boot process and security of the STM32H757.For my tests, I have placed the two boot addresses for the two cores (ADD0 and ADD1 for CM7 and CM4) in the internal flash memory, with an ISR vector at each boot address :ADD0: standard ISR vector calling the standard Reset_Handler, which in turn calls the main function g_pfnVectors: .word __initial_spTop /* Use internal RAM for stack for calling SystemInit. */ .word Reset_Handler .word NMI_Handler .word HardFault_Handler .word MemManage_Handler .word BusFault_Handler .word UsageFault_Handler ... and ADD1: virtually the same ISR vector but calling BootPin_Handler instead of Reset_Handlerg_bootPinVectors: .word __initial_spTop .word BootPin_Handler .word NMI_Handler .word HardFault_Handler .word MemManage_Handler .word BusFault_Handler .word UsageFault_Handler ... Everything seems to be working properly, at least up until the security test.When RDP is set to level 0 or 1, everything is fine and

The issue I am facing when using the STM32U585 microcontroller in the MATLAB and Simulink (M&S) Environment.1. The controller is the STM32U585Allx. Discovery kit. 2.   We  are  working on a project in Simulink (Model-Based Design). As a first stage, we are sensing three-phase AC currents and a PWM generator as a part of our project. For this project the hardware is provided by STM32 U585-based Discovery kit. All  hardware support packages have been installed in the M&S environment.  We are setting up the hardware in STM32CubeMX, configuring ADC1 and Timer1.  All the desired parameters are set and we are generating the code.ioc file.  The ADC is set  for injected signal inputs. TRG0 provides the trigger for the ADC1.   The ADC1 block in Simulink is not getting linked with .ioc file generated in SubeMX. The error is: Index exceeds the number of array elements. So we cannot proceed further.  We would like to get

Thank you @B.Montanari  for the complete guide. Unfortunately on my computer the project is not created as packs can't be downloaded, error is the following (in this case for button pack): Error installing STMicroelectronics.button_part_drivers.2.0.0 pack Could not save pack of pack-URL: https://developer.st.com/st-pack-server/api/v1/pack/STMicroelectronics.button_part_drivers.2.0.0.pack, got: Unsupported `GLOBAL_AGENT.HTTP_PROXY` configuration value: URL protocol must be "http:".   I'm behind a proxy (set at system level), and if I use the URL listed I'm able to download and manually install the pack. I tried setting proxy information on MX2 as IP:port with no result. Is there a way to solve this? BR Edit: moved from How to create a new project with STM32CubeMX2

Post Edited by ST moderator to apply source code formatting Hello, To need to disable external read/write access to flash in stm32c071 i have changed the RDP from level 0(0xAA) to level 1(0xBB) and was successful in doing so. But when I try to change from level 1 to level 0 i am unable to change it.  code to change from level 1  to level 0. eFLASH_ErrorType_t FlashReadWriteEnable(void) { eFLASH_ErrorType_t err_code = e_SUCCESS; // Check if flash is busy err_code = CheckFlashBusy(); if(err_code == e_SUCCESS) { // Unlock flash err_code = flashUnlock(); if(err_code == e_FLASH_UNLOCKED) { // user options unlock err_code = flashOptUnlock(); if(err_code == e_FLASH_OPT_UNLOCKED) { FLASH->OPTR &= (~FLASH_OPTR_RDP_Msk); FLASH->OPTR |= (0xAA << FLASH_OPTR_RDP_Pos); FLASH->CR |= FLASH_CR_OPTSTRT; // Check if flash is busy err_code = CheckFlashBusy(); if(err_code == e_SUCCESS) { FLASH->CR |= FLASH_CR_OBL_LAUNCH; } } } } return err_code;

I want to try the multi antena design mentioned in AN6121. where can I either download the gerber files for the PCB or order a PCB?

Hi all,I really hope someone can shed some light on this...I am trying to find any information regarding the accuracy of the internal temperature sensor of the STM32H7 family, more specifically the STM32H743XIH6.I understand that each device is factory calibrated to improve the accuracy, however I cannot find what the accuracy actually is, I mean, I cannot find any official source of information, I've seen some saying that it is ±1.5C, but nothing in the ST documentation.Any help is appreciated.Thanks  

STM32CubeIDE 1.15.1 login error, although Check Connection shows "green" in the "Firmware Updater". Because of the Login error I cannot Install "STM32CubeU0 Firmware Package V1.0.0 / 12-February-2024". I have seen in the Forum, that this kind of error has been around for a while, and even with this (for the time being) latest version of STM32CubeIDE. If some of you fellows have working ideas, please let me know!

Hi tech supoort reps, According to the documentation for the NUCLEO-563ZI (MB1404C), the board is expected to support I3C mode. However, during our evaluation, we were unable to successfully issue I3C shell and CCC (Common Command Code) commands.At this stage, it is unclear which configuration or setting does not meet the expected requirements. Could you please provide:The correct steps to enable and use the I3C interface on this boardAny required software, firmware, or device-tree configurationsA simple example or reference demonstrating successful I3C shell and CCC command execution Thank you for your support. [00:00:00.000,000] <inf> i3c_hub_init: I3C Hub I2C init start[00:00:00.004,000] <inf> i3c_hub_init: Hub I2C init done[00:00:00.104,000] <inf> i3c_bus_mgr: I3C bus re-enumeration start[00:00:00.104,000] <inf> i3c_bus_mgr: I3C CCC: RSTDAA[00:00:00.204,000] <err> i3c_bus_mgr: RSTDAA failed (-116)*** Booting Zephyr OS build v4.3.0-6019-gef798176ad4c

Dear ST colleagues,I tried recently the package X-CUBE-NFC12.First I tested on NUCLEO-L476RG board the delivered example and it was working out of the box, then I tried on NUCLEO-C071RB but it was not working, first I noticed that the Pins configuration are not correct it was fixed, but still not working, did anyone ever test this example, because I assume it needs to work without any modification.Thank you in advance for your support.Best regardsBassem Taamallah

Regarding the Schottky diode 1N5711, could you please tell me what the reverse resistance value of this diode is? Our factory's designer believes that the reverse resistance value of this diode can be greater than 200 megohms. Could you please confirm if there is a product of this model with a reverse resistance value greater than 200 megohms? Also, under what conditions is this reverse resistance value tested and is there a testing specification? Please give us some suggestions. Thank you!

I am trying to debug a project I have created in STM32CubeMX and edited in STM32CubeIDE with the STM32MP257F-DK. I am seeing an intermittent error which is mentioned in the troubleshooting grid, but it's not clear to me how to fix it.  After it builds with no errors, I get a familiar message:Error in final launch sequence:Failed pre launchFailed pre launchFirmware remoteproc load failed, please:1. make sure that /lib/firmware on your target has space2. make sure that /lib/firmware has write access> you can open a Console View for this..When I check dmesg on the board, I see the lines[ 58.546876] remoteproc remoteproc0: powering up m0[ 58.628708] remoteproc remoteproc0: Booting fw image Project_Name_CM33.elf, size 3097880[ 58.631958] remoteproc remoteproc0: bad phdr da 0x80100000 mem 0x540[ 58.638236] remoteproc remoteproc0: Failed to load program segments: -22[ 58.645251] remoteproc remoteproc0: Boot failed: -22This "bad phdr" line is mentioned in Table 1 of the troublesho