BLOGS

In Part 7, we saw how the main loop checks for UART input every millisecond. When a character is received, the command processing begins. Let’s dive deep into how this interactive command system works and how it controls our task scheduler and power management. The Command Processing Structure When UART_IsDataAvailable() returns true, we enter the

Previously in Part 6, we initialized the task scheduler and registered six tasks. All tasks are now marked as READY. The initialization phase is complete. Now we enter the main loop where actual task execution begins. Where We Are in Code Execution We’re at line 158 in main.c. All initialization functions have returned, all tasks

Previously in Part 5, we initialized the power management system, giving our STM32F429ZI the ability to sleep and wake up efficiently. Now we’re ready to initialize the task scheduler – the system that will orchestrate multiple tasks running at different rates. Where We Are in the Code PowerMgmt_Configure() has just returned to main(), and execution

Previously in Part 4, we gave our STM32F429ZI the ability to communicate through UART. Now our microcontroller can speak, and the first thing it does is announce itself to the world. Where We Are in the Code UART_Init() has just returned to main(), and the very next lines are: These five UART_SendString() calls are our

Previously in Part 3, we gave our STM32F429ZI microcontroller a heartbeat using SysTick – a timer that ticks every millisecond. Now that SysTick_Init() has completed and returned to main(), our microcontroller knows how to keep time. But it still can’t communicate with the outside world. It’s like having a computer with no monitor or keyboard

Previously in Part 2, we traced the boot sequence and verified our interrupt vector table. Now, let’s dive deep into the first critical function call in our main() – SysTick_Init(). Furthermore, after our interrupt vector table verification block completes successfully, execution immediately moves to the next line: Think of this moment as pressing the “setup”

Previously in Part 1, we explored our project structure. Now, let’s uncover what actually happens when you power on your STM32F429ZI microcontroller. Before Your Code Runs Furthermore, while our application code begins at the main() function, several critical initialization steps occur before this point. Understanding this hidden journey is essential for debugging boot issues and

Welcome to my STM32 IoT framework series! I’m building a complete IoT system from scratch without using STM32 HAL libraries. Let’s start by understanding the project structure. Project Overview This is a baremetal implementation featuring: GitHub Repository: github.com/umanggulati/iotmoduleProject Name in IDE: embeddedc_gpio1234 Complete File Structure Directory Explanations Inc/ – Header Files Contains all the public