No best answer

Hi,I'm struggling to get the CAN working on a project I'm working on with the STM32F446ZET6. With the project below (CastletRestart) i just get a flat line of 3.3V high on the TX line for CAN1, this is being tested in loop back mode, with the TUT_CAN_F446 project the can works (downloaded from a tutorial) in loopback mode, as far as i can see ive replicated everything across but it still isnt working.Its likely to be something silly and i do apologise for this being the case but i cannot see what ive missed having reviewed the code countless times.P.s. i am aware the Tutorial project is targeted at a different micro, but the CAN1 ports are the same.Any advice welcomed, thank you for your timeChris

According to the reference manual, enabling USB requires APB2 to operate at a minimum clock of 12MHz. Cubemx2, however, does not validate this constraint and will proceed even if an invalid clock is configured

Hello,I am attempting to communicate between my STM32H7B3I-EVAL and a Vector CANalyzer (VN1630A). I previously reached out to figure out why my CAN messages from the CANalyzer are not being received by the STM32 MCU. There was a belief that it was the filters causing the issue, so I did not initialize the filters and tried to see if any message was being received. There are still no messages being received, but I can send them from the STM32 to the CANalyzer without issue. I would like to find out why my code is not working, but I have some specific questions to try and assist my thought process:If the FDCAN_FilterTypeDef is a defined variable but not initialized, it will not filter, correct?Is the function correct for receiving data from the RXBUFFER?if(HAL_FDCAN_GetRxMessage(&hfdcan1, FDCAN_RX_BUFFER0, &RxHeader, RxData) != HAL_OK){ Error_Handler(); }Setup Picture: #include "main.h"   /** @addtogroup STM32H7xx_HAL_Examples * @{ */   /** @addtogroup T

I am tried to send a simple message over CAN, but I got the broken Frame when transmitting, I capture it on a Logic Analyzer(Pic Below), it seems that it is Transmitting but not Correctly.Did I did somting wrong or Did I miss Someting?And here is my Code:int main(void) { /* USER CODE BEGIN 1 */     /* USER CODE END 1 */   /* MCU Configuration--------------------------------------------------------*/   /* Reset of all peripherals, Initializes the Flash interface and the Systick. */   LL_APB2_GRP1_EnableClock(LL_APB2_GRP1_PERIPH_AFIO); LL_APB1_GRP1_EnableClock(LL_APB1_GRP1_PERIPH_PWR);   NVIC_SetPriorityGrouping(NVIC_PRIORITYGROUP_4);   /* System interrupt init*/ /* SysTick_IRQn interrupt configuration */ NVIC_SetPriority(SysTick_IRQn, NVIC_EncodePriority(NVIC_GetPriorityGrouping(),15, 0));   /** DISABLE: JTAG-DP Disabled and SW-DP Disabled */ LL_GPIO_AF_DisableRemap_SWJ();   /* USER CODE BEGIN Init */   /* USER CODE END In

This is a weird one :) I'm using the STM32F769 device, and I have the LTDC peripheral running at low speed (8MHz PCLK). When I send a CAN message to the unit, the CAN RX interrupt is invoked, and only when the ISR exits,  an LTDC error interrupt is raised, which indicates FIFO underrun. Here is a code snippet below:void conv_u32_to_buf(uint32_t num, uint8_t buf[]){   memcpy(buf, (void*)&num, 4);}void CAN1_RX0_IRQHandler(void){   CAN_TypeDef* can = CAN1;   // If CAN message available in the FIFO   if ((can->RF0R & CAN_RF0R_FMP0) != 0U)   {      uint8_t data[8];      // Get pointer to mailbox      CAN_FIFOMailBox_TypeDef* mailbox = &can->sFIFOMailBox[CAN_FILTER_FIFO0];        // This does not work      uint32_t tmp = mailbox->RDLR;      conv_u32_to_buf(tmp, &data[0]);      tmp = mailbox->RDHR;

Here is the software setting:​For STM32H735(STM32H745 is the same but with different ID):-Defines:/* USER CODE BEGIN PV */FDCAN_TxHeaderTypeDef TxHeader;FDCAN_RxHeaderTypeDef RxHeader;uint8_t TxData_Node1_To_Node2[] = {0x10, 0x32, 0x54, 0x76, 0x98, 0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66};uint8_t RxData_From_Node2[12];/* USER CODE END PV */ -FDCAN:  ​ hfdcan1.Instance = FDCAN1; hfdcan1.Init.FrameFormat = FDCAN_FRAME_FD_BRS; hfdcan1.Init.Mode = FDCAN_MODE_NORMAL; hfdcan1.Init.AutoRetransmission = ENABLE; hfdcan1.Init.TransmitPause = DISABLE; hfdcan1.Init.ProtocolException = DISABLE; hfdcan1.Init.NominalPrescaler = 1; hfdcan1.Init.NominalSyncJumpWidth = 13; hfdcan1.Init.NominalTimeSeg1 = 86; hfdcan1.Init.NominalTimeSeg2 = 13; hfdcan1.Init.DataPrescaler = 2; hfdcan1.Init.DataSyncJumpWidth = 12; hfdcan1.Init.DataTimeSeg1 = 12; hfdcan1.Init.DataTimeSeg2 = 12; hfdcan1.Init.MessageRAMOffset = 0; hfdcan1.Init.StdFiltersNbr = 1; hfdcan1.Init.ExtFiltersNbr = 0; hfdcan1.Init.RxFifo0ElmtsNbr = 1;

I would be interested in implementing a FDCAN communication between two STM32H747 MCU boards. I have implemented communication on a single board in External LoopBack mode. However, I am having problems understanding how to connect the two boards. Do any of you know how to do this, or do you know a good guide?

Is there a way to detect a CAN message loss in a RX Fifo when in the overwrite mode (so an overwrite?)

I’m trying to make the example LoRaWAN_End_Node_LBM] work on my nucleo-wl55jc1.For now i’ve just changed the DevEUI and AppKey in se-identity.h to match my chirpstack configuration.I can see the join request from my object and the join accept answer of the server but here is what i see on the log of the nucleo:LoRaWAN End Node LBMAPPLICATION_VERSION: V1.6.0MW_LORAWAN_VERSION: V1.1.0MW_RADIO_VERSION: V1.4.0L2_SPEC_VERSION: V1.0.4RP_SPEC_VERSION: V2-1.0.4Event received: RESET###### AppKEY: 2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C###### NwkKEY: 2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C###### DevEUI: CA:FE:BA:BE:DF:70:70:35###### AppEUI: 00:00:00:00:00:00:00:00###### DevAddr: DF:70:70:358s053:Add JOIN task8s053: TX MNG REQ time=00008053, final_time=000107888s055: Next TX on freq 868100000, DR 3 10s782: Payload: 00 00 00 00 00 00 00 00 00 35 70 70 DF BE BA FE CA 76 01 0A F0 D4 25 size: 23 995: TX DONE11s041: RX1 LoRa at 4957 ms freq:868100000, DR 3,

Hello,I have no CAN experience, but I have to decide soon if we can use the STM32 (prob. H7) with its CAN-FD interface.To me with my limited CAN knowledge it looks like it supports all hardware necessities, like "old & slow" CAN and the newer, faster version with bitrate change.But to make sure that I am not missing something important :What are the limitations of the STM32 CAN-FD ? What's your experience?Thanks in advance! Edit: I have checked / am reading AN5348 and the STM32 CAN-FD "presentation"

Hello ST Community,I’m developing a custom external loader for a GD25Q64E flash device and cannot get STM32CubeProgrammer to read/write/erase the external flash. I’ve attached a screenshot of the error reported by the programmer.What I’ve doneFollowed the ST tutorial “External QSPI loader how to” External QSPI loader how to - STMicroelectronics. Verified read/write/erase work when exercised from main.c — no errors there. When running the loader, I see a hardfault reported in the CubeProgrammer “HardFault” tab. There is a hardfault at the end of loader_src.c in init(); I’m not sure whether that is expected. Project uses SPI3 with DMA and interrupts to talk to the external flash. I have also tested this with just polling and verified read/writing/erase work when exercised from main.c Device and external flash infoFlash: GD25Q64E SPI instance: SPI3 (Polling)Questions:  Any troubleshooting tips for getting the custom loader working with STM32CubeProgrammer (and diagnosing the hardfault sho

Hello, I initialized CAN on STM32F429ZIT6 on registers. I would like to tranmitt and receive messages. But on transmission lines is silence. In my opinion I forgot about any register, but I don't know which. So could you help me what i sholud change in my code?

Hello,I'm running the BLE_DataThroughput_Server Application on a NUCLEO-WBA65RI (server, notifying) connected to a NUCLEO-WBA55CG (client, receiving notifications), and I'm seeing a significant throughput regression between STM32CubeWBA v1.7.0 and upper versions, with strictly identical configuration. Setup (identical in both cases):Server: NUCLEO-WBA65RI, BLE_DataThroughput_Server Application, from STM32CubeWBA v1.7.0, v1.8.0, and v1.10.0 Client: NUCLEO-WBA55CG,  BLE_DataThroughput_Client Application, from STM32CubeWBA v1.10.0 Connection interval: 11.25 ms PHY: 2M MTU size : 244 Build configuration: Release I added :const uint8_t a_BLE_rx_pckt_count_and_rx_pckt_len[2] = { 0x07, 0x00 }; /* rx_pckt_count , rx_pckt_len */ aci_hal_write_config_data(CONFIG_DATA_LL_RX_ACL_CTRL_OFFSET, 2, a_BLE_rx_pckt_count_and_rx_pckt_len);as described in the "How to get the best throughput" section of the wiki (rx_pckt_count=7, rx_pckt_len=0) Results:BLE_DataThroughput_Server Application from STM32CubeW

I am not getting any IO expansion Module which can support these feature as32UI (Universal Input), 16 AO (Analog Output) and 16 DO (Digital Output) over RS485 communication in a Daisy chainUniversal Inputs0-5V DC 0-10V DC 0-20mA / 4-20mA 5kΩ Thermistor 10kΩ Thermistor RTD (100Ω / PT100/PT1000) Dry Contact / Binary Input Pulse Count InputUniversal Outputs0-10V Analog Output 0-20mA / 4-20mA Analog Output Relay / Binary OutputsPlease suggest

OverviewDebug Authentication Discovery occasionally succeeds in CLOSED state, but Full Regression fails (“Unable to boot on RSS_DA” / “Unable to detect DBGMCU Mailbox”)Get ready for the stm32 safari! Product / Environment- Board: Custom based off of STM32H7S78-DK (MB1736)- MCU: STM32H7S7L8H6H- Debugger(s) used: STLINK-V3SET- Tool: STM32CubeProgrammer v2.19.0- ST-LINK FW: V3J17M10B6S1- Board setup used during recovery attempts:- tried altering Boot0 (boot from RSS/system flash)- tried manual reset- tried low SWD speed and hardware reset modes Summary of the issueI was attempting to recover the board after secure configuration experiments. The board was originally reachable over SWD, but after running the **`ROT_Provisioning/DA/provisioning.sh`** flow from the STM32CubeH7RS package, normal SWD access stopped working. The board is now in **CLOSED** state, and **Debug Authentication Discovery** can occasionally succeed if I hit a very narrow timing window at power-up, but an

I’m trying to implement USB mass storage class device standalone(no RTOS) on nucleo board STM32U575ZI-Q, using RAM for memory.I mostly followed these steps :, but skipped the  eMMC parts (I’m using RAM). Instead i did  like here: https://embetronicx.com/tutorials/microcontrollers/stm32/stm32-usb-device-msc/ , in ux_device_msc.c I  defined  STORAGE_BLK_NBR,  STORAGE_BLK_SIZ, and then used memcpy() inside functions like STORAGE_Read_FS().Someone has done seemingly the same thing already(combining these two things) and it worked: https://github.com/ST-TOMAS-Examples-USB/STM32U385RG_Ux_Device_MSC_Standalone . Are there any adittional steps i’ve missed?Right now, after plugging the USB into my PC, it appears in Device Menager with code 10( device cannot start ). I’ve put a breakpoint on STORAGE_Read_FS() line while debugging, but it never stops there.   

Hi,I am using my own board based on an STM32F207ZG with STM32F2 HAL v1.9.4. I implemented a USB HID Host using STM32CubeIDE (v1.19.0), simply enabling USB Host and HID Class support in CubeMX and generating the code.I was able to read keys correctly from a standard USB desktop keyboard. However, I was not able to read from a USB HID RF reader. While debugging the problem, I noticed the following code in `usbh_hid.c`, inside `USBH_HID_Process()`:case HID_IDLE:  status = USBH_HID_GetReport(phost, 0x01U, 0U,                              HID_Handle->pData,                              (uint8_t)HID_Handle->length);  if (status == USBH_OK)  {    HID_Handle->state = HID_SYNC;  }This initial `USBH_HID_GetReport()` therefore has to complete successfully before the state machine proceeds to `HID_SYNC` and eventually reaches `HID_GET_DATA`, where `USBH_InterruptReceiveData()` starts polling the HID interrupt IN endpoint EP1. My question is: What is the intended purpose of this initial `G

Dear team,We are using in our Solar charge controller with STM32G030C8T6 mcu with internal Vref calibration. We are getting mostly Input voltage sensing ADC pin PB0, PB1 and PB2 failure either while power on time or after few days of normal working. Due to that we are getting many fields issue for battery charging. request your advice and suggestion to sort it asap.

Here on Opensuse Tumbleweed with fvwm2 the installation starts with a small window where the "Continue" button is not visible on startup. The window is can only be resized a little smaller but not larher. Only by scrolling the "Continue" button gets visible.This is unexpected.The follwing stages the presented window still can not be sized to a sensible size. MX2 was installed before on that PC and was still accessible. I do not know how the window size behaved during the first installation.Screen size is  3840x2160.

Environment:STM32CubeMX version: 6.18.1  STM32CubeIDE version: 2.2.0 STM32 MCU: SMT32H7R3Z8J6 OS: Windows 11Project configuration:Code Generator option: "Generate peripheral and middleware initialization as a pair of .c/.h files per peripheral (optional)" = [Enabled / Disabled] Relevant peripherals already enabled before: xSPI, USART1 New peripheral added that triggers the issue: USB_FS/HS, SPIx, UART/USARTx, and others. Description:When I add a new peripheral or middleware in STM32CubeMX and generate code, CubeMX creates an empty folder or generates incomplete peripheral and/or middleware output.The issue appears repeatedly with the same pattern and is not random. In the first case: Create or open project in CubeMX. In Project Manager / Code Generator, set: "Generate peripheral initialization as a pair of .c/.h files per peripheral" = Disabled (default).  Generate code.  Add a new peripheral: USB_FS (and/or others).  Generate code again. Open CubeIDE, then build. In the current situat

Hi all,When I create a TouchGFX application starting from CubeMX, the following folder and its subfolders are not generated:{ProjectName}\Appli\Middlewares\ST\touchgfx_componentsGPU2D is enabled, and “Use GPU2D acceleration” is set to True under the X-CUBE-TOUCHGFX package settings.However, when I create a TouchGFX project using TouchGFX Designer and select the STM32N6570-DK, these folders are generated correctly.Am I missing a configuration step in CubeMX?Thanks so much!

According to the STM32MP257 datasheet:"1× USB 2.0/3.0 high-speed/SuperSpeed dual role data with embedded 480 Mbits/s and 5 Gbits/s PHY" "1× PCI Express with embedded 5 Gbits/s PHY (PHY shared with USB 3.0 SuperSpeed)"I would like to clarify:Can the USB3DR peripheral be used as a USB 3.0 SuperSpeed port while simultaneously supporting USB 2.0 High-Speed operation on the same connector? Is the embedded USB 2.0 PHY always available when the USB3DR interface is enabled? When PCIe is not used, can the USB3DR interface provide both the 480 Mbit/s USB 2.0 and 5 Gbit/s USB 3.0 links together as a standard USB 3.x port? Is the PHY sharing limitation only between PCIe and USB 3.0 SuperSpeed, or does it also affect USB 2.0 functionality?Any clarification on the USB/PCIe PHY sharing architecture would be appreciated.

Hello, I’m trying to initially build the Distribution-Package 6.2.0 (v26.02.18) as stated in the Wiki (https://wiki.st.com/stm32mpu/wiki/STM32MPU_Distribution_Package#Initializing_the_OpenEmbedded_build_environment)I am using a VM in Virtual Box running Ubuntu 24.04.5 LTS.I attached the log file.Any help is appreciated :)Thanks in advance.Ben

Hi all, hoping some of the veterans here or an ST engineer can help. Long debug session, board-level causes systematically ruled out, looking for input on what's left.Setup: SPC58NH92E7RMI0X (eLQFP176), custom board, internal-regulator-with-external-ballast configuration (BC868ballast transistor).Core symptom: VDD_HV_IO_MAIN, fed from a confirmed-clean 3.3V LDO, never reaches 3.3V once connected to the MCU — plateaus around 1.3–1.8V regardless of available current (tested to 800mA–1A limit, current settles 500mA–1.5A depending on config). VDD_LV never stabilizes at 1.2V as a direct consequence. MCU runs very hot; the ballast transistor does not.Ruled out:Wrong part (physically confirmed) Wrong pinout: every power/config/Ethernet pin checked against the official IO definition workbook Passive short on VDD_HV_IO_MAIN (~2.9kΩ unpowered, not a short, higher than an unrelated rail on the same board measured the same way) Wrong component values/orientation on the ballast circuit A real power

I am currently evaluating the following ST platform for an IO-Link Device application: MCU Board: NUCLEO-G071RB IO-Link Expansion Board: X-NUCLEO-IOD02A1 IO-Link Transceiver: L6364Q Software Package: X-CUBE-IOD02 Development Environment: STM32CubeIDE The STM32G071RB example project included in X-CUBE-IOD02 builds and runs successfully.However, based on the documentation and the provided ministack library, the current software package appears to be based on IO-Link Interface and System Specification V1.1.2.For a new product development, I would like to use a newer or the latest available IO-Link Device Stack.I would appreciate any information on the following: Is there a newer version of X-CUBE-IOD02 that supports an IO-Link specification later than V1.1.2? Is there an updated version of the following ministack library that supports a newer or latest IO-Link specification? iol_device_ministack_stm32g0_wc32_ot.a If an updated library is available, where can the corresponding li