Introduction to Programming and Microcontrollers

This is the foundation for everything that follows, so it is worth taking slowly. You will learn what programming actually is, what a microcontroller does, and how code becomes physical action. By the end you will have installed your tools, uploaded your first program to the board, and wired an external LED that blinks on your command. If you have never written a line of code before, this is exactly the right place to start.

What programming is

Programming is the act of writing instructions that a computer or microcontroller can follow to do a specific job. At its core, code is just a list of instructions: if this happens, do that; otherwise, do something else. Every piece of hardware around you depends on it. Your microwave, your fridge, and your phone all contain a controller, and without instructions telling that controller what to do, even the most advanced chip is just an expensive rock. Programming is how you turn that rock into something that acts on the world.

How a machine understands code

You write code in a language that humans can read, but the processor only understands electrical signals that represent on and off, which we write as ones and zeros. A tool called the compiler translates your human-readable code into those machine instructions. You do not need to manage the compiler yourself, but it helps to know it is there: when you press Verify in the editor, the compiler checks your code for errors before anything is sent to the board. If you forget a semicolon, the compiler stops and reports a syntax error, which simply means it could not translate your instructions cleanly.

What a microcontroller is, and the parts in your kit

A microcontroller is a small, self-contained computer on a single board that is built to control hardware directly. The board in your kit is based on the open-source Uno R3 design; the exact color or brand does not matter, because they are interchangeable for our purposes. The board is the brain that gives instructions. The other parts receive those instructions or report back: LEDs light up, resistors limit current, and the breadboard lets you build circuits without soldering. A breadboard is just a grid of metal strips under the surface, with two long rails on the sides for power and ground, so components pushed into the same row are connected.

The structure of a sketch: setup and loop

A program for the board is called a sketch, which is really just a file of code. Every sketch has two required functions. setup runs exactly once, the moment the program starts, and is where you prepare everything, such as declaring which pins you will use and how. loop runs immediately after setup and then repeats forever, over and over, until the board loses power or is reset. Most of your working code lives in loop. Understanding this two-part structure is the key to reading any sketch: configure once in setup, then do the repeating work in loop.

Why the Blink program needs a delay

The Blink sketch turns an LED on, waits, turns it off, waits, and repeats. Setting a pin HIGH sends voltage out of it; setting it LOW stops the voltage. You might think you could just alternate HIGH and LOW to make it blink, but the board executes thousands of instructions per second, so without a pause it would switch on and off far faster than your eye can see and the LED would appear to sit at a dim steady glow. The delay solves this. delay(1000) tells the board to wait 1000 milliseconds, one full second, so the on and off states last long enough to see. That is why there is a delay after both the on and the off step.

Working through it

Install the editor and drivers. Download and install the code editor for your operating system, then install the board drivers from inventr.io/downloads so your computer can talk to the board. If anything misbehaves after installing, a quick restart often clears it up.

Connect the board and select the board and port. Plug the board into your computer with the supplied USB cable. In the editor, open the board selector at the top and choose the Uno board, then choose the correct port. On Windows the port usually looks like COM3 or COM4, often the highest-numbered one; on macOS or Linux it appears with a USB-style name. Selecting the right board and port is the step most first-timers miss.

Open and upload the Blink example. Open the built-in Blink example sketch, then press Upload. The editor compiles the code, checks for errors, and sends it over USB to the board. If it worked, the small onboard LED starts blinking on and off once per second. Getting past this step is the hardest part of the whole month; everything after is smoother.

Experiment with the delay.