r/stm32

I want to use stm32N6 as it has csi for a camera and a npu for computer vision and it would be cool to test out its CV capabilities on a drone. Since its based on a new architecture a lot of vendor support is broken/buggy and I am wondering if I should use zephyr instead of hal, right now I just have motor control working, I plan to implement CSI camera next (imx219), then NPU, after that will be standard flight control additions like imu and wireless module ect. but the main complexity will be CSI and NPU. I heard Zephyr has better N6 support but its NPU is undercooked so I may have to do a hybrid approach for the NPU specifically.

Hi internet people!

I'm an old dude who used to be an electronics engineer 30 years ago. I only know about analog electronics, but now I decided to finally figure out microcontrollers. I have plenty of time for this task. Well at least until I'm alive. In order to learn things I came up with a task for myself. An electronic device project. I always learn stuff that way.

But I'm kinda lost because of huge range of options.

So here it is. I am a moonshiner (and an alcoholic of course) so I couldn't think of anything better than to make a thermal controller for my distillation setup. So I am asking this community for help - please tell me where to start?

This device must compare the temperature from two temperature sensors. And based on their readings clicks 8 relays open/closed. In addition, it must have LCD with temperature readings and some kind of settings menu to well... set some settings. Also 4-5 buttons for setting temperature threshold values based on which the contacts are closed or opened. All of this must be recorded in some memory and stored there even after a power outage. I don't need networking features or anything else. That kind of device. Sounds simple but like everything in the world I know it's not.

Here are specific questions:

- There are lots of STM32 MCUs. Which one is suitable for this task?

- Or maybe I should use something else?

- Can you recommend me good dev boards. I know only about official Nucleo ones?

- Is it really necessary to know C++ or Rust for coding that type of device firmware?

Thanks everybody!

Hey everyone,

I'm posting this out of pure frustration after spending an entire day trying to wrap my head around a hardware/debug lockout on my Nucleo-L476RG board while learning bare-metal STM32 development. I'm hoping someone can explain what actually happened under the hood, because I feel like I'm losing my mind.

Here is the timeline of what went down:

I was experimenting with pure bare-metal code (no HAL). At one point, my code included a low-power instruction (wfi - Wait For Interrupt) or initialized early on a routine that locked the core or stopped it from servicing the debug interface. Immediately after flashing that build, OpenOCD completely lost connection.

OpenOCD / CubeProgrammer throws "Error: Unable to get core ID" and "No STM32 target found", even when trying connect under reset. The board is not fully dead. The bootloader in system memory is completely fine, and I can still successfully flash the chip via UART (stm32flash with BOOT0 pulled high). So, the MCU itself runs code fine when booted via system memory, but the onboard ST-LINK debug interface/firmware bridge completely refuses to communicate with the target MCU over the SWD lines.

Did some chatting with gemini, tried some things to get it back. 1: Flashing a clean binary / wiping flash via UART. 2: Connect under reset and Hot Plug modes in STM32CubeProgrammer. 3: Hard-resetting the board manually while plugging in USB to catch the core during boot. 4: Checking the physical jumpers (CN2 jumpers are intact, JP5 is on U5V).

Nothing brings the SWD channel back to life. The onboard ST-LINK detects via USB on the PC, but it throws a brick wall the second it tries to talk to the main STM32 chip.

Since I'm sick of jumping through hoops with a broken onboard debugger, I've sort of decided to order an independent external ST-LINK V2 clone for a few bucks, pull the CN2 jumpers on the Nucleo, and hook up SWCLK/SWDIO directly to bypass the onboard.

1. How on earth can a standard bare-metal program permanently break the debug circuitry of a Nucleo board if I didn't explicitly remap PA13/PA14 (SWDIO/SWCLK)? Did I trigger a hardware latch-up or ESD/voltage spike?
2. Has anyone else experienced an onboard ST-LINK effectively "commiting suicide" while keeping the main MCU functional via UART?

Any insights are appreciated. I'm ready to move on to an external programmer, but I'd love to know what actually went wrong technically.

So I created a project using cubemx and made it for uvision5 but then I wanted to see if I can make one for stm IDE using the same ioc file but it just doesn’t work it won’t let me use it to create a new project like it will create the new project but I just can’t open it
And even using uVision I can’t simulate it like I try to blink LED to simulate it but that doesn’t work at all
Help me it’s for a project

Wanted to start working with stm32 bluepill but could only find the reference manual

Please share the user manual if you guys have it

I am learning STM32 using the F446RET6 board. I'm facing an issue while connecting a W25Q64 NOR FLASH memory via SPI1 to the board. The JEDEC ID should be 20 70 17, but the STM32 consistently receives incorrect data: 3F FF FF.

The connections are VCC to 3.3V, GND to GND, SCLK to PA5 (SPI1_SCK), D0/DO to PA6 (SPI1_MISO), D1/DI to PA7 (SPI1_MOSI), and CS to PC7 as a GPIO output.

SPI1 is configured as Master, Full Duplex, 8-bit, CPOL Low, CPHA 1st Edge, MSB First, Software NSS, with a prescaler of 32. CS is manually controlled using PC7.

The HAL SPI transaction completes successfully, but the returned JEDEC ID is incorrect. The same W25Q64 module works perfectly with an ESP8266, where I get the expected 20 70 17, so the flash itself appears to be working.

I also tested PA5, PA6, PA7 and PB6 separately as GPIO outputs using a multimeter. All of them can correctly output both HIGH (~3.3V) and LOW (~0V). PC7 also switches correctly between ~3.3V and 0V when used as CS.

I initially used a breadboard for the SPI connections and noticed some inconsistent behavior, so I also tried connecting the SPI lines directly to different sections of the PCB, but the problem remained.

I have ordered an 8-channel logic analyzer to inspect CS, SCLK, MOSI and MISO. Before it arrives, I would like to know if there is anything obvious I am missing in the STM32 SPI configuration, wiring, or HAL implementation, and whether this could indicate a problem with SPI1 itself.

https://preview.redd.it/brbh92iyzwhh1.png?width=1916&format=png&auto=webp&s=ed7ea14865f849e151191cc143fabcb56e42349c

First of all, complete beginner, first day of tinkering with it and following tutorials.
In desperate need of help, long story short I have tried to blink a led for a first on my Blue Pill board and succeeded on my first time. Any future attempts on changing the code on the cubeide has gone into errors such as target no device found (see image).
Since then I have tried so much stuff the internet search results has told me to.
For more information, in CubeProgrammer the serial number is 0 and pressing connect doesnt do anything, which makes me believe the st link is faulty, but in st-link utility the serial number shows fine.
The Chatgpt suggests that wiring can be the problem, but I'm positive the wires connect to the same labels on the board and the st link, also the same way it worked the first time, but still "no target found".
Don't know if I bricked my card / st link, or did something completely wrong
Any help would be appreciated, will provide more info if needed. Thank you.