AVR Drivers: Difference between revisions
Jump to navigation
Jump to search
Binary size
(Binary size) |
|||
| Line 201: | Line 201: | ||
See [[Modifying BLF-VLD]] for programming notes. | See [[Modifying BLF-VLD]] for programming notes. | ||
=== Checking program size === | |||
AVR Eclipse and Atmel studio can show you size of the program after compilation. If you want to check it otherwise, use avr-size as shown below. | |||
<pre>C:\BLF-VLD\Programmable\avr-size -C --mcu=attiny13a BLF-VLD.elf | |||
AVR Memory Usage | |||
---------------- | |||
Device: attiny13a | |||
Program: 968 bytes (94.5% Full) | |||
(.text + .data + .bootloader) | |||
Data: 26 bytes (40.6% Full) | |||
(.data + .bss + .noinit) | |||
EEPROM: 64 bytes (100.0% Full) | |||
(.eeprom)</pre> | |||
<blockquote>The ATtiny13A provides the following features: 1K byte of In-System Programmable Flash, 64 bytes EEPROM, 64 bytes SRAM.</blockquote> | |||
Maximum: | |||
* Program: 1024 bytes | |||
* Data: 64 bytes | |||
* EEPROM: 64 bytes | |||
And yes, the same source program will have different machine code size and slightly different machine code when compiled with different options and different versions of AVR-GCC. Original Tido's programmable ELF has a size of Program: 1004 bytes (98.0% Full). | |||
=== Optimizations === | === Optimizations === | ||