An Arduino core for most 64 and 100-pin AVRs, all running the Urboot bootloader. This core requires at least Arduino IDE v1.8, where v1.8.9 or newer is recommended. IDE 2.x should also work.
From MegaCore version 3 and onwards, the Optiboot bootloader has been replaced by the superior Urboot bootloader. It's smaller, faster, and has automatic baud rate detection, and can read and write to EEPROM. Other cool features the bootloader provides but are not utilized by MegaCore are user program metadata stored in flash (that can easily be viewed by Avrdude -xshowall) and chip-erase functionality. If you already have Optiboot installed and don't want to replace it with Urboot, you can still upload programs without any compatibility issues. However, if you're burning a bootloader to a new chip, Urboot is the way to go.
(All variants - A, L, P, PA, PV, V)
Can't decide what microcontroller to choose? Have a look at the specification table below:
Mega2560 Mega1280 Mega640 Mega2561 Mega1281 Mega128* Pin 70-85 is not broken out on the Arduino Mega. Make sure to check out the AVR style pinout for a more straightforward pinout.
** ATmega165/169/325/329/645/649 has one hardware serial port and four PWM outputs.
Supported clock frequenciesMegaCore supports a variety of different clock frequencies. Select the microcontroller in the boards menu, then select the clock frequency. You will have to hit "Burn bootloader" in order to set the correct fuses and upload the correct bootloader. This also has to be done if you want to change any of the fuse settings (BOD and EEPROM settings) regardless if a bootloader is installed or not.
Make sure you connect an ISP programmer, and select the correct one in the "Programmers" menu. For time-critical operations, an external crystal/oscillator is recommended. The Urboot bootloader has automatic baud rate detection (except when using UART2 and UART3 on ATmega640/1280/2560), so UART uploads should work fine even though the oscillator is a little too fast or too slow.
Frequency Oscillator type Default upload speedMegaCore lets you select which serial port you want to use for uploading. UART0 is the default port for all targets, but any hardware serial port may be used. If your application doesn't need or require a bootloader for uploading you can also choose to disable it by selecting No bootloader. This frees 384 bytes of flash memory on ATmega165/169/325/3250/329/3290 and 512 bytes on ATmega64/128/645/6450/649/6490/1281/2560 and AT90CAN32/64/128.
Note that you need to connect a programmer and hit Burn bootloader if you want to change any of the Bootloader settings.
Since Urboot has automatic baud rate detection, the upload baud rate can be changed without having to re-flash the bootloader. The default baud rate setting will pick a suited baud rate that also works with the legacy Optiboot bootloader used in earlier MegaCore versions. The other baud rate options may or may not work, depending on the clock frequency and accuracy of the clock source. A rule of thumb is that "non-round" baud rates like 230400 works best with "non-round" clock speeds like 18.4320 MHz, while "round" ones like 16 MHz work best with "round" baud rates like 250000.
Brown-out detection, or BOD for short lets the microcontroller sense the input voltage and shut down if the voltage goes below the brown-out setting. To change the BOD settings you'll have to connect an ISP programmer and hit "Burn bootloader". Below is a table that shows the available BOD options:
If you want the EEPROM to be erased every time you burn the bootloader or upload using a programmer, you can turn off this option. You'll have to connect an ISP programmer and hit "Burn bootloader" to enable or disable EEPROM retain. Note that when uploading using a bootloader, the EEPROM will always be retained.
Note that if you're using an ISP programmer or have the Urboot bootloader installed, data specified in the user program using the EEMEM attribute will be uploaded to EEPROM when you upload your program in Arduino IDE. This feature is not available when using the older Optiboot bootloader.
#include <avr/eeprom.h>
volatile const char ee_data EEMEM = {"Data that's loaded straight into EEPROM\n"};
void setup() {
}
void loop() {
} Link time optimization / LTO
Link time optimization (LTO for short) optimizes the code at link time, usually making the code significantly smaller without affecting performance. You don't need to hit "Burn Bootloader" in order to enable or disable LTO. Simply choose your preferred option in the "Tools" menu, and your code is ready for compilation. If you want to read more about LTO and GCC flags in general, head over to the GNU GCC website!
Unlike the official Arduino cores, MegaCore has printf support out of the box. If you're not familiar with printf you should probably read this first. It's added to the Print class and will work with all libraries that inherit Print. Printf is a standard C function that lets you format text much easier than using Arduino's built-in print and println. Note that this implementation of printf will NOT print floats or doubles. This is disabled by default to save space but can be enabled using a build flag if using PlatformIO.
If you're using a serial port, simply use Serial.printf("Milliseconds since start: %ld\n", millis());. You can also use the F() macro if you need to store the string in flash. Other libraries that inherit the Print class (and thus support printf) are the LiquidCrystal LCD library and the U8G2 graphical LCD library.
Note that you don't have to use the digital pin numbers to refer to the pins. You can also use some predefined macros that map "Arduino pins" to the port and port number:
// Use PIN_PE0 macro to refer to pin PE0 (Arduino pin 0) digitalWrite(PIN_PE0, HIGH); // Results in the exact same compiled code digitalWrite(0, HIGH);
MegaCore uses the excellent Urboot bootloader, written by Stefan Rueger. Urboot supports flash writing within the running application, meaning that content from e.g. a sensor can be stored in the flash memory directly without needing external memory. Flash memory is much faster than EEPROM, and can handle at least 10,000 write cycles before wear becomes an issue. For more information on how it works and how you can use this in your own application, check out the Serial_read_write for a simple proof-of-concept demo, and Flash_put_get + Flash_iterate for useful examples on how you can store strings, structs, and variables to flash and retrieve then afterward.
PROGMEM with flash sizes greater than 64kBThe usual PROGMEM attribute stores constant data such as string arrays to flash and is great if you want to preserve the precious RAM. However, PROGMEM will only store content in the lower section, from 0 and up to 64kB. If you want to store data in other sections, you can use PROGMEM1 (64 - 128kB), PROGMEM2 (128 - 192kB), or PROGMEM3 (192 - 256kB), depending on the chip you're using. Accessing this data is not as straightforward as with PROGMEM, but it's still doable:
const char far_away[] PROGMEM1 = "Hello from far away!\n"; // (64 - 128kB)
const char far_far_away[] PROGMEM2 = "Hello from far, far away!\n"; // (128 - 192kB)
const char far_far_far_away[] PROGMEM3 = "Hello from far, far, far away!\n"; // (192 - 256kB)
void print_progmem()
{
uint8_t i;
char c;
// Print out far_away
for(i = 0; i < sizeof(far_away); i++)
{
c = pgm_read_byte_far(pgm_get_far_address(far_away) + i);
Serial.write(c);
}
// Print out far_far_away
for(i = 0; i < sizeof(far_far_away); i++)
{
c = pgm_read_byte_far(pgm_get_far_address(far_far_away) + i);
Serial.write(c);
}
// Print out far_far_far_away
for(i = 0; i < sizeof(far_far_far_away); i++)
{
c = pgm_read_byte_far(pgm_get_far_address(far_far_far_away) + i);
Serial.write(c);
}
}
Select your microcontroller in the boards menu, then select the clock frequency. You'll have to hit "Burn bootloader" in order to set the correct fuses and upload the correct bootloader.
Make sure you connect an ISP programmer, and select the correct one in the "Programmers" menu. For time-critical operations, an external oscillator is recommended.
This installation method requires Arduino IDE version 1.8.0 or greater.
https://mcudude.github.io/MegaCore/package_MCUdude_MegaCore_index.jsonClick on the "Download ZIP" button in the upper right corner. Extract the ZIP file, and move the extracted folder to the location "~/Documents/Arduino/hardware". Create the "hardware" folder if it doesn't exist. Open Arduino IDE, and a new category in the boards menu called "MegaCore" will show up.
Run the following command in a terminal:
arduino-cli core install MegaCore:avr --additional-urls https://mcudude.github.io/MegaCore/package_MCUdude_MegaCore_index.json
PlatformIO is an open-source ecosystem for IoT and embedded systems, and supports MegaCore.
See PlatformIO.md for more information.
Getting started with MegaCoreYour code should now be running on the microcontroller!
To extend this core's functionality a bit further, I've added a few missing Wiring functions to this hardware package. As many of you know Arduino is based on Wiring, but that doesn't mean the Wiring development isn't active. These functions are used as "regular" Arduino functions, and there's no need to include an external library.
I hope you find this useful because they really are!
MegaCore provides a standard, logical pinout for the 64-pin chips. The standard LED pin is assigned to digital pin 13/PIN_PB5.
Click to enlarge:
MegaCore provides a standard, logical pinout for the 64-pin chips. The standard LED pin is assigned to digital pin 13/PIN_PB5. MegaCore includes the original Arduino Mega pinout for the ATmega640/1280/2560, but also a straightforward, "standard" pinout for all 100-pin chips. The standard LED pin is assigned to digital pin 13 on the Arduino MEGA pinout and digital pin 22 on the standard pinout (PIN_PB7 in both cases).
Click to enlarge:
Here are some simple schematics showing a minimal setup using an external crystal. Omit the crystal and the two 22pF capacitors if you're using the internal oscillator.
Click to enlarge:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4