Since a number of applications rely on the existence of the BTN0_PIN definition, the BUTTON0_PIN definition has been renamed to BTN0_PIN to make the ESP32 boards compatible with these applications. However, for compatibility with earlier versions, BUTTON0_PIN is still defined as an alias of BTN0_PIN.
Instead of using the same MCU feature table in every board documentation, it refers to the MCU documentation. This makes it easier to maintain the MCU feature table.
According to the datasheet, SX1278 covers frequencies till 525MHz
and hence, cannot be used for the 868/915 MHz band. So swap both
chips.
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
- No longer include `tools/serial.mk` and `tools/avrdude.mk`, as this is
no done by `boards/common/atmega`
- No longer provide `RESET ?=`, as this is now done in `tools/avrdude.mk` for
all ATmega boards unless they are using a bootloader
- Use the common logic to translate from a bootloader to concrete flasher flags
- Extended documentation on how to use optiboot as alternative bootloader, as
the stock bootloader is affected by a bug preventing the use of RIOT's
pm_reboot() implementation
- including `avrdude.mk` and `serial.mk` is no longer needed
- the avrdude flag -F is dropped
- This allows flashing a board having an MCU different to the one
RIOT was compiled for
- It is better to let the user provide this flag manually if she/he really
wants to turn safety off, knows what she/he is doing, and accepts the
risk associated with this
- the avrdude flag -D is dropped
- This disables issuing an erase command during flashing, however this
erase cycle is strictly required to be able to program the flash
- This is only needed in case of the stk500v2 bootloader, which implicitly
does the erase cycle and fails if explicitly asked to do so
- Only for the stk500v2 bootloader this flag is now added
