STM32 MCUs Boards and hardware tools

Im using i2c on stm32 nucleo and the slave is a cheap imu (mpu6500). Sometimes the bus just gets stuck and doesnt work. And the weird thing is if i plug everything out, flash code again and run it it will not work. Until it randomly works again until the next random fail. I tried with various setups, with pull ups from stm32, with external 5k pull ups.Initially i was running bare metal code but i thought something is worng with the code and switched to HAL to do simple read or write. Everything is the same, randomly works and doesn't work.Did anyone experience and solve something similar? 

Is there a board schematic for STM32L432KC somewhere?I want to acces pin PA13. But I can find no connector or easy acces point.Thanks

i am quite new for stm32n6, i am working with STM32N6570-DK with Arduino IMX335 . i just wanna make a simple snaphort using the project SnapshotDecimationMode (used with mb1854)as my reference. i can configured the camera via I2C and start the pipe. but the frame event did not interrupt. i think the causes of issue arepower sequence: arducam has only power en pins unlike mb1854 which has reset and power enable pins.i configured something wrong about interrupt.anyone can teach me the true way to config the camera with dcmipp interrupt?

While designing Electronic speed controllers for a 6s battery, an stm32 was decided to use as the MCU.    After receiving our first PCBs, we were unable to successfully program them with the stlinkv3 minie. Attached is an image of the schematic of where the STM lies on the board as well as the attached components. When the boards first came in the stm32 was able to be flashed with a program, but after the first flash they could not be connected to any more. This is with using an external power supply as the stlink v3 didn't seem to provide power as the prg tool was unable to detect the chip.   After continued testing (and changing out the mcu) the issue persisted although with a slight deviation, it would allow us to program it once or twice but when we clear the flash, it would lose connection and throw an error of dev_target_held_under_reset. In case it is relevant, the only connection type that can even read the flash of the chip is hot plug but that is unable to chan

hi, ive noticed that hand landmarks pre built binarys uvc output does not work on the C02 revision NUCLEO-N657X0-Q but does work on the c01 rev, could anyone guide me on how to get this demo up and running ont he c02?

Dear all, I would like to connect a camera to my Nucleo F756ZG board, with the goal to send images via the ethernet port. However, this board doesn't feature a 30-pin ZIF connector nor a 22‑pin FFC connector....Apparently, the STM32 F756ZG has a "DCMI". Is this accessible on the Nucleo board as well?Which module/camera do you recommend for the Nucleo F756ZG?Would you recommend Arducam? They seem suspiciously cheapThe B-CAMS-IMX is not compatible, right?Many thanks

So as the title suggests, I have been trying to get the LCD screen to work on the STM32F469i-DISCO board. Currently I just want it to turn on at all. I found the BSP drivers in this link as well as the OTM8009A drivers in this other link  When I run the code however, it gives me the following error:../Drivers/BSP/STM32469I-Discovery/stm32469i_discovery_lcd.c:402:5: error: too few arguments to function 'OTM8009A_Init'402 | OTM8009A_Init(OTM8009A_FORMAT_RGB565, orientation); I noticed that the function prototype for that function is int32_t OTM8009A_Init(OTM8009A_Object_t *pObj, uint32_t ColorCoding, uint32_t Orientation);so I am not sure why the lcd drivers call the function in that way. Are there better/newer drivers that I should be using instead?

Dear Sir/Mam, As LCD, i.e., RK043FN48H-CT672B Rocktech of STM32F746 Discovery Board is obselete hence can we change to RK043FN66HS-CTG Rocktech without any implication in the firmware of Discovery board? Please respond me as soon as possible. Best Regards Sushant Verma

Moved from STM32 MCU products forum board to MCU embedded software as the main question is about how to run the demo vs LCD versions. I got STM32U5G9J-DK2 and this Discovery is still assembled with LCD board MB1860A version. But the documentation suggesting this DK have LCD board MB1860B version and share only B version scheme. I taked damage of my LCD board MB1860A and replaced it to MB1860B LCD board version from my next Discovery Kit STM32H7S78-DK. And here arising some problems: For example the BSP demo from example pack working flawlesly, but the main demo embedded from factory doesn't work with STM32U5G9J-DK2  and MB1860B version of LCD board. The LCD is dark and look as dead.   So my questions  which could be provide the answer about incorrectly work of LCD sounds like: 1. Why doesn't the main demo work, despite of the docimentation suggestion that this kit is assembled with the MB1860B LCD version board? 2. How I can obtain the scheme for M

Hello,We have procured a STM32U5G9J-DK1 discovery kit. We are in need of the default pre-loaded program that comes with the kit as this will help us to understand how to use Touch display and its other features. We see that this pre-loaded program is not available in the repository downloaded for STM32U5G. Therefore, request you to kindly share it here.With regard,Sudarshan Chaudhary

I have connected and an external HS PHY to STM32F427VGT6 through ULPI pins.Configured USB_OTG_HS in Host Only mode for external Phy with parameter Settings asSpeed: High Speed 480MBits/s Enable internal IP DMA: DisabledPhysical Interface: External PhyUse External VBUS: EnabledSignal Start of Frame: DisabledIn NVIC settings for USB_OTG_HS all three available interrupts are enabled.  USB On The Go HS End Point 1 Out global interrupt true 0 0 USB On The Go HS End Point 1 In global interrupt true 0 0 USB On The Go HS global interrupt true 0 0 In Middleware Packages USB_ Host, FATFS is configured according to attached image.MCU schematic and USB-PHY schematic is also attached.The problem i am facing is STM32 is not detecting USB and gstate of USB always remain to HOST_IDLE, even if i connect or disconnect pendrive.

Im an engineering student and wanted to dive into PCB designs, so I started off with a PCB design for a vibration monitor system that i first built on arduino. This is my first ever PCB design which I made using reference/data sheets and whatever resources I could find online. Before I started routing I was wondering if could get some feedback on my current design especially for the power supply and decoupling placement, crystal and NRST implementation and general PCB placement issues before routing. Any advice is much appreciated. I am usingSTM32F103C8T for my MCUMPU6050 for the sensor.Screenshots of the Schematic, PCB and pinout are below.

Does the STM32N6570-DK board support XSPI/OSPI interfaces for communication with external peripherals, or are these interfaces limited only to internal or external memory devices?For example, if there is a Device that supports OSPI/XSPI for communication, is it possible to connect the STM32N6570-DK board to such a device to enable data exchange?Could you please provide a clear explanation of the capabilities and practical use cases of the OSPI/XSPI interface on the STM32N6570-DK board?

Hello Everyone,I am currently using LPUART2 for communication between an MCU (STM32U031) and an MPU (Application Processor).Configuration parameters:Baud rate: 9600Stop bits: 1Parity: NoneData bits: 8Description:Data exchange between MCU and MPU works perfectly when both devices are operating in normal power mode (i.e., not in sleep or stop modes). However, I am facing an issue when both MCU and MPU wake up from sleep/stop mode. After wake-up ,The MCU is unable to receive data from the MPU, even though the MPU continues transmitting data. No IRQ handler is triggered on the MCU side.Additional Details:I deinitialize the LPUART before entering sleep/stop mode.I reinitialize it immediately after wake-up.Scenarios Tested:Only MPU enters sleep (MCU remains active): After MPU wake-up, communication works perfectly.Both MPU and MCU enter sleep: After wake-up, communication fails (MCU doesn’t receive data).Observation:It seems that the issue is related to LPUART behavior du

So far, in all my projects, the MCU has been powered via USB attached to computer. I would like to make a project in which the MCU is powered by a portable power supply. However, I don't know which equipment I need to use for this purpose. I have a power supply module from ELEGOO kit (ELEGOO Upgraded Electronics Fun Kit w/Power Supply Module, Jumper Wire, Precision Potentiometer, 830 tie-Points Breadboard for Arduino, STM32 : Amazon.com.au: Computers), which can output 5/3.3V electricity. Can I connect a powerbank to the supply module, and use the supply module to power the board, or should I look for other options? The board I use is stm32f407g-disc1, and the datasheet (DS8626_STM32F40xxx.book) says that the voltage should be in 1.8-3.6V range and the power of electrical current should be less than 240 mA (p79).

Hello,   I’m starting a new design with the STM32H755. I also have the dev board (Nucleo-H755ZI-Q), but I do not have its schematic. So far, the closest schematic/design reference I’ve found is Figure 18 in AN4938 (“Getting started with STM32H755”).   Could you please share more schematic references?   I was thinking about the following: The complete NUCLEO-H755ZI-Q schematic and the BOM Any additional pages/details related to the Figure 18 schematic (it appears to reference a multi-page schematic, but we only have the first page in this document) Any other official schematic/reference design examples for STM32H755 that I could use as a starting point   Thank you for your time and help!  

I get no message if i send some bytes about my terminal tool. Because i have no schematic i dont know waht going wrong. Do i need an external supply( target ) or do i need pullup resistor or someone else? A target board isnt still connected.

Hi everyone,I’m feeling a bit defeated by a task that should be "Hello World" level simple. I’m trying to get a basic printf to show up in PuTTY using a NUCLEO-G474RE, but I’m getting absolutely nothing in the terminal.I do this all the time with my NUCLEO-H723ZG using USART3 and it works like a charm. For the G4, I’ve switched over to USART2, but no luck.Here is my setup:Toolchain: CubeMX + CMake.The Logic: I've overwritten __io_putchar() with a HAL_UART_Transmit call.The Config: USART2 is enabled, baud rate matches PuTTY (115200), and the clocks seem fine.I even had a friend who uses G4 boards regularly take a look, and even he couldn't figure out why the data isn't hitting the ST-Link. It feels like I'm missing one tiny, G4-specific checkbox or jumper setting.I've put together a bare-bones repository with just the code for the printf here: https://github.com/mpek29/nucleoG4Has anyone else run into similar issues ?Thanks in advance for any pointers, I'm sure it's something silly I've

Hello, I am currently evaluating the STM32N6570-DK and am seeking clarification regarding a discrepancy I’ve encountered. I can confirm that there is a 48MHz crystal on board for the HSE. However, the default CubeMX projects generated by the board selector, as well as other example projects I have reviewed, all configure the input frequency to 24MHz. Could you please clarify what the correct input frequency for the HSE should be on this discovery kit? Thank you for your assistance.

Hello STM Community,I currently have a NUCLEO-U575ZI-Q board and the X-NUCLEO-IKS4A1 motion MEMS and environmental sensor expansion board. I’m looking to add BLE functionality and was considering the X-NUCLEO-WB05KN1.Before proceeding, I’d like to ask:Are the X-NUCLEO-IKS4A1 and X-NUCLEO-WB05KN1 compatible when stacked together on the NUCLEO-U575ZI-Q?If not, is there an alternative BLE expansion board that is known to work well with the IKS4A1 on this Nucleo board?Alternatively, is there an expansion or adapter board that allows both shields to be connected without pin conflicts?Any guidance or shared experience would be greatly appreciated!Thanks in advance.

I have designed a STM32H723 board with LAN8742A PHY IC and its connected to a Hanrun HR911105A Magjack. I am running the Ethernet stack on mongoose network library. The stack is working perfectly on a STM32H7 Nucleo Board, the link auto-negotiates to 100Mbps Full duplex speed. Unfortunately, on the custom board, the link auto negotiates to 100M full-Duplex but ARP resolution fails(the link works fine at 10M speed). The schematic and layout are highly inspired by the STM32H723 Nucleo and the LAN-8742A evaluation board. I am attaching the schematic(PHY side, cannot show the STM side due to NDA reasons) and debug messages from LAN8742A registers for the same. Some Notes on the Layout: The Board is a 8 layer PCB. Majority of the routing has been done on the top and bottom layers. Layer 2 is the reference layer for the 100ohm differential TX and RX lines. The TX and RX digital lines ( from PHY to STM) are roughly matched to 50 ohm impedance. I can't show more than this unfortunately, b

Hello, I have a Nucleuo-F767ZIT6 board on which I verified a Ethernet code using FreeRTOS in Netconn API, there the code works fine without any issues. So, I moved on to designing a custom board for the same controller the first board worked without any issues but when I designed another iteration of the same board the ethernet stopped working in it, I've checked if other peripherals work fine and they work flawlessly, the ethernet part of the board is same as I had previously designed but still it does not work. The code that I run on both the boards is the same as there were no changes in the controller side. This the connections on the first board : Below is my design of the second board: Both the design are similar to the design of Nucleuo-F767ZIT6, but don't understand why one design works where as the other doesn't, I have done all the proper clock configurations and set the correct HSE crystal values too. Any suggestion in debugging the above mentioned issue will be gre

Hi STM Community, I’m currently working with the NUCLEO-G491RE board and need some guidance regarding DFU (Device Firmware Update) mode. According to the documentation, CN2 is marked as the DFU connector. Based on that, I have soldered 4 pins on CN2. I also have a USB Type-C female breakout board, and I’d like to connect it properly to CN2. USB Type-C Female Breakout Board. However, I’m a bit confused about the following points: CN2 pin mapping Which pin on CN2 corresponds to GND, D+, D-, and 3.3V / VBUS? Entering DFU mode What are the exact steps to put the NUCLEO-G491RE into DFU (Device Firmware Update) mode? Do I need to configure BOOT0, jumpers, or any CubeMX settings for this? At the moment, when I connect the board to my PC using the USB breakout, the device is detected as an “Unknown USB Device”, so I assume I’m missing something in either the wiring or configuration. I would really appreciate it if someone could: Clarify the CN2 pinout, and Explain the cor

I am using an STM32H755ZQ device and unable to start a debug session using STM32CubeIDE + ST-LINK (SWD).The system uses two STM32 controllers, where firmware is flashed to one controller and data is shared/communicated to the second controller.Debug fails with errors like DEV_TARGET_HELD_UNDER_RESET and GDB connection timeout (localhost:61234).Even with Connect under reset, low SWD frequency, and full chip erase via STM32CubeProgrammer, the issue persists.Looking for guidance on whether inter-controller communication, reset interaction, or H755-specific debug/security settings could block debugging.

Hello,I’m working on a project with the NUCLEO-H753ZI board and need to connect multiple devices. I’d like to know:1. How many GPIO pins are 5 V-tolerant for digital input?2. How many GPIO pins are available for general use, both 3.3 V-only and 5 V-tolerant, considering the board’s default peripherals?I want to make sure I safely use the MCU’s GPIOs for my inputs and outputs. Any guidance or reference resources would be appreciated.Thank You!