AVR Freaks

Where did you find it?

<br> is HTML for "new line" - so, as  MattRW said, you need to replace each <br> with a new line:

avr-gcc     -g -Os -mmcu=“microcontroller” -c “filename”.c
avr-gcc     -g -mmcu=“microcontroller” -o “filename”.elf “filename”.o
avr-objcopy -j .text -j .data -O ihex “filename”.elf “filename”.hex
avr-size    --format=avr --mcu=“microcontroller” “filename”.elf 

​Here the filename that we want to compile is: led.c and the microcontroller is: atmega32​ So the code becomes

avr-gcc     -g -Os -mmcu=atmega32 -c led.c
avr-gcc     -g -mmcu=atmega32 -o led.elf led.o
avr-objcopy -j .text -j .data -O ihex led.elf led.hex
avr-size    --format=avr --mcu=atmega32 led.elf 

 

EDIT

On the HTML <br> tag: 

https://www.w3schools.com/tags/tag_br.asp

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/br

+1

The Microchip one says it works on linux: 

https://www.microchip.com/en-us/development-tools-tools-and-software/mplab-x-ide

Yes because the program reads the template - you make some menu selections to customize it and then it writes out a new Makefile based on your selections.

You started this thread on Jan 28. It is now Feb 18. If you had simply installed an IDE for AVR you would now have been writing you AVR code rather than worrying about makefiles/mfile since Jan 29.

I simply suggested Mfile as it makes a good makefile but you do need to get the TCL to work. The alternative is simply to manually copy makefile_template to your own project then hand edited it. (which is what the TCL GUI would have done automatically)

If you manually edited it the lines you probably need to change are:

# MCU name
MCU = atmega128

unless you really do happen to be using a mega128 you need to change this to the model of AVR you want to build for.

Also look at:

# Target file name (without extension).
TARGET = main


# List C source files here. (C dependencies are automatically generated.)
SRC = $(TARGET).c

Well "TARGET" is the name of the project. So you might want to use something like:

# Target file name (without extension).
TARGET = LED_flasher

or whatever describes the overall intent of the project. When it finally builds the output ELF (and HEX) file they will be called whatever you put here so LED_flasher.elf, LED_flasher.hex and so on.

On the line:

# List C source files here. (C dependencies are automatically generated.)
SRC = $(TARGET).c

this is going to take the TARGET name and assume you have a .c file of that name (in my example LED_flasher.c) but perhaps this is not the case. Perhaps you just have files called main.c uart.c, timer.c and adc.c in which case you list them all on this line:

SRC = main.c adc.c timer.c uart.c

or perhaps it is as simple as one file?

SRC = main.c

In the unlikely case that the project includes some assembler code in .S file then edit that onto the:

# List Assembler source files here.
#     Make them always end in a capital .S.  Files ending in a lowercase .s
#     will not be considered source files but generated files (assembler
#     output from the compiler), and will be deleted upon "make clean"!
#     Even though the DOS/Win* filesystem matches both .s and .S the same,
#     it will preserve the spelling of the filenames, and gcc itself does
#     care about how the name is spelled on its command-line.
ASRC = 

but you probably don't need to do anything there.

One more that you might need to edit is:

# List any extra directories to look for include files here.
#     Each directory must be seperated by a space.
#     Use forward slashes for directory separators.
#     For a directory that has spaces, enclose it in quotes.
EXTRAINCDIRS = 

If you have "library code" that has .h files that are not in the main project directory then you need to tell the preprocessor where to look by adding the other directory names on this line.

Other than this you don't really need to change anything (at least at first). Also note that every important "XXX =" line in that file that you might need to change has a few lines of comment before it saying what it is for and how to set the value.

But you really would be better off using an IDE - have you looked at MPLABX ?

(also when I go to the main Mfile site and download the makefile_template currently there has 506 lines).

Eh? All professional engineers use IDEs these days. Sure it's an idea to understand what they generate in the makefile but the days of creating Makefile from scratch are long since passed. If you do want to learn about "command line scripting" learn about CMake or Scons.