Imagecraft c compiler and development environment for the atmel avr

More documents

Recommendations

Info

ICCV8 for AVR – C Compiler for Atmel AVRGenerating Production ELF FileSome of the current AVR flash programming tools accept a “production ELF” file asinput. Prior to using the production ELF file, the binary code for flash and EEPROMare stored in different files and other special control bytes (such as “lock bits”, and“fuses”) must be handled specially using the flash programming tool. This is acumbersome and error-prone process. In contrast, a production ELF file contains allthe binary code needed to program an AVR device; including flash, EEPROM, fuses,etc.One example of an AVR tool that uses production ELF file is Atmel Studio 6, under the"Device Programming/Production file" dialog.ICCV8 for AVR generates additional .bin files, and in a post-linker step, combinesthem into a single production ELF file. This process is transparent to the users. Notethat this is for production use only and the ELF file does not contain debug symbols.To debug using Atmel Studio, continue to use the .cof COFF output file.In addition to the .bin output, contents of flash and EEPROM continue to be availablein the respective .hex and .eep output files as before. (See Initializing EEPROM onhow to define EEPROM data.) Use the following #pragma to specify content for otherspecial AVR areas. Each pragma must appear in only one source file (i.e. do not put itin a header file where it will be included by multiple source files).Note that the compiler does not check the content specified in these pragmas. Youmust ensure that the correct values are used. #pragma avr_signature (signature0, signature1, signature2)AVR signature is always three bytes. Signature0 is always the Atmelmanufacturer code of 0x1E. The other two bytes are device dependent. This is fordevice verification - if Studio cannot verify that the device has the right signaturebytes, no other programming will be performed.We have defined the macros SIGNATURE0, SIGNATURE1 and SIGNATURE2 inthe common iccioavr.h header file so if you use that header file, you can writethe following for any AVR device:#include ...#pragma avr_signature(SIGNATURE0, SIGNATURE1, SIGNATURE2)114
ICCV8 for AVR – C Compiler for Atmel AVR#pragma avr_fuse (fuses0, fuses1, fuses2, fuses3, fuses4, fuses5)Depending on device, there are different numbers of fuse bytes. This pragmastarts with LOW FUSE byte, followed by HIGH and EXTENDED FUSE bytes.For XMEGA, fuses3 byte is not used (yet) and must be set to 0xFF.#pragma avr_lockbits (lockbits)Currently, all AVR devices have just one byte for lock bits and the value 0xFCdisallows reading out the memories and changing the fuses by a hardwareprogrammer.#pragma data:user_signaturesexample:#pragma data:user_signaturesunsigned char a[] = {“Copyright (C) 2013 ImageCraft” };#pragma data:dataXMEGA only: “user signatures” is an extra page of flash memory in the xmegadevices, fully accessable by software and not deleted by chip erase. Since youcan place a large amount of data, it uses the same syntax as the #pragmadata:eeprom for initialized EEPROM data. Therefore, you must also end thedefinition with #pragma data:data.115
Page 2 and 3:
ICCV8 for AVR - C Compiler for Atme
Page 4:
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65: ICCV8 for AVR - C Compiler for Atme
Page 165 and 166:
TOOL REFERENCESMISRA / Lint Code Ch
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204:
show all

Imagecraft c compiler and development environment for the atmel avr

Create successful ePaper yourself

Delete template?

Save as template?