
It does not appear to be necessary for these devices but might result in more appropriate libraries to be linked in. It is best to _not_ specify the exact MCU because otherwise a few other settings (such as startfiles and some linker script configs) also get set, which we do manually anyway and should not be interfered with. I discovered this while working on support for the atmega1284.
18 строки
386 Б
JSON
18 строки
386 Б
JSON
{
|
|
"inherits": ["avr"],
|
|
"llvm-target": "avr-atmel-none",
|
|
"cpu": "atmega328p",
|
|
"build-tags": ["atmega328p", "atmega", "avr5"],
|
|
"cflags": [
|
|
"-mmcu=atmega328p"
|
|
],
|
|
"ldflags": [
|
|
"-mmcu=avr5"
|
|
],
|
|
"linkerscript": "src/device/avr/atmega328p.ld",
|
|
"extra-files": [
|
|
"targets/avr.S",
|
|
"src/device/avr/atmega328p.s"
|
|
],
|
|
"emulator": ["simavr", "-m", "atmega328p", "-f", "16000000"]
|
|
}
|