Currently comment on runout sensor configuration says:

• By default the firmware assumes HIGH=FILAMENT PRESENT.

which is quite confusing and not very informative for regular user. As we test filament sensor status by M119 command It should clearly say when filament present on M119 we should see either "open" or "TRIGGERED" status and we can flip FIL_RUNOUT_INVERTING otherwise. Nobody really

There are a few flags that currently don't have proper error checking. The ones I found are -gc, -scheduler and -size. Using the wrong value will lead to no or unexpected errors.

I think the best way to handle it is to add a new method to compileopts.Config that checks whether there are any faulty flags, which is then called from the main function.

Solutions

1. Convert INO files to CPP

2. Manual prototype declaration

#ifdef DO_NOT_USE
typedef int32_t delaytype;
void thisShouldNotAppearInTheBinary(delaytype timer); // aded manually
void thisShouldNotAppearInTheBinary(delaytype timer) {
  delay(timer);
}
#endif

Readme.txt includes the following:

t84_default - ATtiny84A default configuration - 1534 bytes
t841_default - ATtiny841 default configuration - 1586 bytes
t45_default - ATtiny85 default configuration - 1588 bytes
t85_default - ATtiny85 default configuration - 1588 bytes
t85_aggressive - ATtiny85 smaller size - critical - 1418 bytes
t1

We should really have a page (in extras, with the other docs like this) that lists popular libraries that are known to work or not work with these parts (and in the latter case, alternatives if any, and information on any plans by myself or others to work over said libraries). Also needs some info on what a library compatibility issue will look like in the error output.

This is a great issue fo

EasyAVR has very poor developer documentation. We should at least comment the code.

I am trying to evaluate adapting ArduinoMenu to run under Mongoose OS, and am looking at a two stage implementation plan:

1. get it running on Linux (with a very generic serial input and output device, similar to the Blink or Button examples). I want to do this so I can quickly get the menus going, and make sure I really understand what's going on.

2. move it to Mongoose OS (with an ILI9341

uint16_t readChannel(Channel channel)

According to docs.modm.io

typedef uint8_t 	Channel
// this type may also be an enum or enum class 

the call readChannel(1) should be legal, but: error: cannot convert 'int' to 'modm::platform::Adc1::Channel'.

We should up

The introduction of the platform.txt gave us lots of under the hood settings to play with. Sadly the documentation isn't the best..

I was thinking about implementing an additional flag in the boards.txt file; {programmer.speed}.
If a slow internal clock is selected like 128 kHz, the programmer.speed flag will hold "-B32". if the speed is 9.6 MHz it will hold "-B1". By doing this I can get rid of