MCUs SCAFFOLDs

Collection of Rakefiles to start of and avoid IDEs.

Or graphically:

AVR + ~~IDE~~ Ruby = FUN

ESP + ~~IDE~~ Ruby = FUN

ARM + ~~IDE~~ Ruby = FUN

Just clone:

git clone git://github.com/nofxx/mcu_scaffold.git

or download:

https://github.com/nofxx/mcu_scaffold/zipball/master    # .zip

https://github.com/nofxx/mcu_scaffold/tarball/master    # .tar.gz

And choose a MCU:

AVR

ATmega Family. The 8bit father of all. From ATMEL, you know it from Arduino. The CPU, the famous ATmega328.

ARM

Linux Boards -> Rpi/BBB Cortex M? STM32... Up to 64 bits of linux fun. Lots of CPUs here, and nevermind if you have a kernel to worry about that.

ESP

ESP32/ESP8266/NodeMCU/WeMos Xtensa CPU. The cheap answer to ARM's 32bits reign. With wifi!

Getting Started

The following are instructions for getting up and running under different operating systems. This will take you through installing mcu-gcc, mcu-libc, mcudude, and the MCU GNU Binutils.

Building and Running the Sample Project

Each scaffold is driven by a Rakefile. If you're not familiar with Rake, you'll want to take some time to familiarize yourself with it. It's integral to the operation of this scaffolding.

The different stages of the build process are broken down into different rake tasks. These can be viewed by running the command rake -T in the scaffold directory. You'll see something like this:

$ rake -T
rake clean                       # Remove any temporary products.
rake clobber                     # Remove any generated file.
...

The name of the serial port used by the programmer may be passed as an environment variable to the rake. If you do not know how to identify the name of the serial port used by the programmer, consult with the section corresponding with your operating system under the 'Identifying the Name of the Programmer Serial Port' later in this document.