The file is called hello.ftdi.44.echo.c.make so you can download it and rename it to Makefile, so that make will automatically load it. Let's say that the program is ok for your board (and that your board is ok), so we can learn from its Makefile in order to understand how to modify it or create our own Makefile. On the lecture page there is already a C program that can be compiled and uploaded to the Hello Board (with an Attiny44). Let's look at a ready-made example for the Fab Academy. The structure of a Makefile is very simple, and more tutorials about it can be found here, here or here. Otherwise, you can specify it with make -f filename, especially if you have more Makefiles with different names. Make reads automatically a Makefile file in the folder where you launch it (it should be the folder where your project can be found). Furthermore, you can distribute it to other people that can therefore use it for compiling your software easily. When you need to deal with multiple configurations and commands when compiling a software, you can use the make command on Mac/Linux for automatizing this task. All the instructions on the Makefile for this exercises basically deals with almost only these two commands. Since we normally use AVR microcontrollers in the Fab Academy, we need write a C code for them, compile it with avr-gcc and send it to the microcontroller with avrdude. The AVR is a modified Harvard architecture 8-bit RISC single-chip microcontroller, which was developed by Atmel in 1996. Back to tutorial index Makefile for Embedded Programming

How to create a makefile for c program