#stm32

Every embedded systems student starts with curiosity. At first, terms like microcontrollers, GPIO, UART, SPI, I2C, and RTOS may seem confusing. But with consistent learning and hands-on practice, those complex topics gradually become exciting challenges.

The journey usually begins with learning programming languages like C and Embedded C, followed by understanding how microcontrollers interact with hardware. Soon, blinking an LED isn't just a simple project—it's the first step toward building real-world embedded applications.

As students progress, they start working with sensors, communication protocols, debugging tools, and development boards such as Arduino, STM32, and ESP32. Every project teaches something new, whether it's fixing a bug, improving code efficiency, or understanding how hardware and software work together.

One important lesson every embedded systems student learns is that mistakes are part of the learning process. Debugging can take hours, but solving a problem brings confidence and valuable experience.

Eventually, classroom concepts turn into practical skills. Students build projects, prepare for technical interviews, complete internships, and gain the confidence to work on real-time embedded applications in industries like automotive, IoT, consumer electronics, healthcare, and industrial automation.

The life cycle of an embedded systems student isn't just about learning technology—it's about developing problem-solving skills, patience, creativity, and the confidence to build innovative solutions.

STMicroelectronics has begun volume production of China-manufactured STM32 microcontrollers, marking a major milestone in building a resilient and localized semiconductor ecosystem. The initiative starts with the high-performance STM32H7 series, with additional STM32 families set to follow.

Recently i managed to make my way into the store and buy an actual modern SD card from a reputable source (Phillips)

Not only does it respond the same way every time, it also responds with "illegal command" set to false and also ON BYTE BOUNDARY (detected bitshift is 0 every time).

I guess working with legacy hardware made me more experienced and tougher but i am glad to be dealing with something more predictable this time. Maybe next time i sit down at this (which is probably not today cause i have other things coming) i will be able to write/read a block which would be fantastic and a moment i am looking forward to the most.

I wrote some code, the way i usually like by making references to datasheet chapters etc. Everything was going well but the card did not work. I knew it was ok since it worked when plugged to my PC, but it was not responding to my init commands over SPI.

I googled and googled but nothing seemed to work. I tried my no-name logic analyzer but for some reason linux didnt recognise it - it used to work a few years ago but no more i guess.

Eventually i decided to check all the data that is being transmitted to the STM32 chip by changing all the writes into read/writes. Turns out MISO line was high all the time, non stop. This activated some alarm bell in me since it looked like an electrical error.

Eventually i found some random thread about arduino with what seemed to be a similar problem. What i did not mention is that SD cards work with 3.3v (afaik) which is not a big deal since stm32 also works on 3.3v. Sometimes one might want to plug them into a 5v circuit though and to accommodate that, the board i bought contained a voltage level regulator type of chip forgot the name. Essentially converter between 3.3. and 5v signals.

Apparently, in some cheaper no name modules like mine, this type of chip bugs out and keeps on holding the MISO line high despite the fact that SD card has let it go long time ago. This sounds like exactly what is happening to me.

Solution? Glorious:

Bypass the voltage converter. 3.3v should still be considered high state even by 5v circuits, so it should work.

I appreciate the random person who just bumped into a random thread after 2 years of inactivity and just dropped this knowledge. These folks are the backbone of the internet and im glad to have been in his position once or twice myself.

I myself did not feel like soldering that wire, especially since the pad on the socket is super small and these modules are very cheap. Since STM32 works on 3.3v anyways, and atmegas also have low voltage versions nowadays i decided to just buy another module which has no additional ICs on it - no voltage regulators, converters etc, just plain SD card socket and routed connections, maybe a resistor or two.

Funny thing in the end, but also kind of irritating, since it took me long enough to finally sit down and start tinkering with this stuff. Also it might turn out there's a different problem at play and i just bought some more electrojunk for no reason. But then again, i put some more sensors and SPI fun stuff into the basket when i was orderign the new module, so there's always new stuff to look forward to.