Imagecraft c compiler and development environment for the atmel avr

More documents

Recommendations

Info

ICCV8 for AVR – C Compiler for Atmel AVR.a extension in the edit box. For example, rtos refers to the librtos.a libraryfile. All library files must end with the .a extension.Unused ROM Fill Bytes - fillsthe unused ROM locations with the specified integer pattern.CRC - Specify an address in your device to store the CRC structure. The linkercomputes the CRC for your program and stores it in this structure. You canprogrammatically compute the CRC at run time to check against this value. SeeCRC Generation. The CRC structure looks like:unsigned address;unsigned crc16; must not be used for other purpose. Typically you would specify theaddress at the end of the flash memory.AVR Studio Simulator IO - If selected, use the library functions that interface tothe Terminal IO Window in the AVR Studio (V3.x ONLY). Note that you must copythe file iostudio.s into your source directory.Strings in FLASH - By default, literal strings are allocated in both FLASH ROMand SRAM to allow easy mixing of strings and char pointers. (See Strings.) If youwant to eliminate the overhead of allocating strings in SRAM, you can check thisoption. You must be careful to use the correct library functions. For example, tocopy a literal string allocated this way into a buffer, you must use the cstrcpy()function instead of the standard strcpy() function. (See String Functions.)Return Stack Size - the compiler uses two stacks, one for the return addressesfor the function calls and interrupt handler (known as the hardware stack), andone for parameter passing and local storage (known as the software stack). Thisoption allows you to control the size of the return stack. The size of the softwarestack does not need to be specified. See Program Data and Constant Memory.Each function call or interrupt handler uses two bytes of the return stack and 3bytes if the CPU is a M256x. Therefore, you need to estimate the deepest level ofyour call trees (i.e., the maximum number of nested routines your program maycall, possibly any interrupts), and enter the appropriate size here. Programsusing floating points or longs should specify a hardware stack size of atleast 30 bytes. However, in most cases, a hardware stack size of maximum 50bytes should be sufficient. Since the hardware stack uses SRAM, if you specify astack that is too large, the stack may overflow into the global variables or thesoftware stack and Bad Things Can Happen.Do Not Use R20..R23 - do not use R20 to R23 for code generation. See GlobalRegisters.62
ICCV8 for AVR – C Compiler for Atmel AVRInstruction Set - Select instruction set supported by the device: Classic,Enhanced, Enhanced (no MUL), or XMega. Only changeable if the device is set toCustom.Bootloader Options - Enabled only for devices that support boot loaders such asthe newer ATMega devices. You can specify whether the project is for buildingApplication Code or Bootloader code, and how large the boot size is. SeeBootloader Application.Internal vs. External SRAM - Specify the type of data SRAM on your targetsystem. If you select external SRAM, the correct MCUCR bits will be set.NonDefault Startup - a startup file is always linked with your program (see StartupFile). In some cases, you may have different startup files based on the project.This option allows you to specify the name of the startup file. If the filename is notan absolute pathname, then the startup file must be in one of the librarydirectories.Other Options - this allows you to enter any linker command-line arguments. Forexample,source file:#pragma text:bootloadervoid boot() ... // function definition#pragma text:text // resetUnder “Other Options,” add-bbootloader:0x????where 0x???? is the starting address of the area “bootloader.” This is usefulfor writing a main program with a bootloader in the high memory. If you arewriting a standalone bootloader, then you can simply select the “bootloader”memory configuration in the Build Options - Target dialog box.63
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: ICCV8 for AVR - C Compiler for Atme
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?