electro
/
avr-c-boilerplate
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Basic boilerplate for programming AVR (arduino) in C.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13 Commits
1 Branch
0 Tags
110 KiB
 
 
 
 
 
Tag: Branch: Tree: 225d295675
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '225d295675'
${ noResults }
avr-c-boilerplate/README.md

1.9 KiB
Raw Blame History

AVR C Boilerplate

This is a basic boilerplate for programming AVRs in C.

The project aims to make programming Arduinos in C fun by providing support for basic functionality like GPIO and USART, so you can start developing without having the datasheet open all the time.

It is intended for ATmega328P (the chip in Arduinos), but can be easily adapted to other parts.

Requirements

Before you can start coding, you need to install a few software packages:

  • avrdude - the flash tool
  • avr-gcc - compiler
  • avr-libc - libc implementation for AVR
  • avr-binutils - utils for manipulating AVR binaries
  • make - to run the Makefile

There's a good chance you already have make, the rest should be in your distribution's repos.

If you're on Arch:

# pacman -S base-devel avr-gcc avr-binutils avr-libc avrdude

If you're on Mac, you should be able to pull the stuff with brew.

Getting started

The provided main.c is a good starting point - it contains some simple demo code.

You can compile it with make and flash with make flash.

"It doesn't work"

Before you can flash, check that the avrdude options in the file are correct for your system - especially the device (/dev/ttyUSB0). It can differ if you're on Mac or Windows (/dev/cu.xxx, resp. COMx).

You may also adjust the baudrate (-b 57600). Some boards need 115200 or a different value.

You can look what the Arduino IDE is using - it's running avrdude too.

adjusting the Makefile

  • If you add a new C file to the project, add an entry for it's .o (object file, created by the compiler before linking) to the OBJS list in the Makefile.
  • Similarly, if you add a new folder with header files, add it to INCL_DIRS.
  • In case you need printf (or printf with floats), enable the appropriate LD_FLAGS in the Makefile (it's well commented). Code size will - obviously - grow quite a bit.