RealView Compilation Tools Developer Guide - ARM Information ...

More documents

Recommendations

Info

Embedded Software Development • The stack base location is provided by a semihosting operation during application startup. The value returned by this semihosting operation depends on the debug environment: — RealView ARMulator ISS (RVISS) returns the value set in the configuration file peripherals.ami. The default is 0x08000000. — RealView ICE return the value of the debugger internal variable top_of_memory. The default is 0x00080000. 2-8 Copyright © 2002-2007 ARM Limited. All rights reserved. ARM DUI 0203H Non-Confidential
Embedded Software Development 2.2.4 Linker placement rules The linker observes a set of rules, shown in Figure 2-4, to decide where in memory code and data is located. ZI section A from file2.o RW RO DATA CODE B A section A from file1.o Figure 2-4 Linker placement rules The image is organized first of all by attribute, with RO at the lowest memory address, then RW, then ZI. Within each attribute code precedes the data. From there, the linker places input sections alphabetically by name. Input section names correspond with assembler AREA directives. In input sections, code and data from individual objects are placed according to the order of object files given on the linker command line. ARM does not recommend relying on these rules for precise placement of code and data. Instead, you must use the scatter-loading mechanism for full control of placement of code and data. See Tailoring the image memory map to your target hardware on page 2-15. Note See About scatter-loading on page 5-2 in the Linker and Utilities Guide. ARM DUI 0203H Copyright © 2002-2007 ARM Limited. All rights reserved. 2-9 Non-Confidential
Page 1 and 2: ® RealView Compilation Tools Versi
Page 3 and 4: Product Status The information in t
Page 5 and 6: Contents RealView Compilation Tools
Page 7 and 8: Contents A.2 Semihosting implementa
Page 9 and 10: Preface This preface introduces the
Page 11 and 12: Preface Chapter 6 Handling Processo
Page 13 and 14: Preface • ARM Architecture Refere
Page 15 and 16: Chapter 1 Introduction This chapter
Page 17 and 18: Introduction 1.2 Developing for the
Page 19 and 20: Introduction 1.2.4 Handling process
Page 21 and 22: Introduction 1.2.6 Compatibility wi
Page 23 and 24: Chapter 2 Embedded Software Develop
Page 25 and 26: Embedded Software Development Note
Page 27 and 28: Embedded Software Development 2.2.1
Page 29: Embedded Software Development 2.2.3
Page 33 and 34: Embedded Software Development __rt_
Page 35 and 36: Embedded Software Development Examp
Page 37 and 38: Embedded Software Development 2.4 T
Page 43 and 44: Embedded Software Development SB ST
Page 45 and 46: Embedded Software Development Avoid
Page 47 and 48: Embedded Software Development Table
Page 49 and 50: Embedded Software Development Prote
Page 51 and 52: Embedded Software Development 1 2 3
Page 53 and 54: Embedded Software Development To av
Page 57 and 58: Embedded Software Development 2.6 O
Page 61 and 62: Chapter 3 Writing Position Independ
Page 63 and 64: Writing Position Independent Code a
Page 65 and 66: Writing Position Independent Code a
Page 67 and 68: Chapter 4 Interworking ARM and Thum
Page 69 and 70: Interworking ARM and Thumb 4.1.2 Wh
Page 71 and 72: Interworking ARM and Thumb For exam
Page 73 and 74: Interworking ARM and Thumb 4.2 Asse
Page 75 and 76: Interworking ARM and Thumb 4.2.3 Ex
Page 77 and 78: Interworking ARM and Thumb 4. Run t
Page 79 and 80: Interworking ARM and Thumb 4.3 C an
Page 81 and 82:
Interworking ARM and Thumb 3. To li
Page 83 and 84:
Interworking ARM and Thumb Example
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Chapter 5 Mixing C, C++, and Assemb
Page 91 and 92:
Mixing C, C++, and Assembly Languag
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Chapter 6 Handling Processor Except
Page 109 and 110:
Handling Processor Exceptions 6.1.1
Page 111 and 112:
Page 113 and 114:
Handling Processor Exceptions Examp
Page 115 and 116:
Page 117 and 118:
Handling Processor Exceptions instr
Page 119 and 120:
Handling Processor Exceptions 6.4 H
Page 121 and 122:
Handling Processor Exceptions LDR N
Page 123 and 124:
Page 125 and 126:
Handling Processor Exceptions 6.6 S
Page 127 and 128:
Handling Processor Exceptions The t
Page 129 and 130:
Page 131 and 132:
Handling Processor Exceptions } pri
Page 133 and 134:
Page 135 and 136:
Handling Processor Exceptions • e
Page 137 and 138:
Handling Processor Exceptions In AR
Page 139 and 140:
Page 141 and 142:
Handling Processor Exceptions Byte
Page 143 and 144:
Handling Processor Exceptions Figur
Page 145 and 146:
Handling Processor Exceptions 6.9 U
Page 147 and 148:
Handling Processor Exceptions 6.11
Page 149 and 150:
Chapter 7 Handling Cortex-M3 Proces
Page 151 and 152:
Handling Cortex-M3 Processor Except
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Chapter 8 Debug Communications Chan
Page 173 and 174:
Debug Communications Channel 8.2 Ta
Page 175 and 176:
Debug Communications Channel 8.3.2
Page 177 and 178:
Debug Communications Channel Exampl
Page 179 and 180:
Debug Communications Channel 8.5 Ac
Page 181 and 182:
Appendix A Semihosting This chapter
Page 183 and 184:
Semihosting printf("hello\n"); Appl
Page 185 and 186:
Semihosting Changing the semihostin
Page 187 and 188:
Semihosting A.2.4 RealMonitor RealM
Page 189 and 190:
Semihosting A.3.2 angel_SWIreason_R
Page 191 and 192:
Semihosting A.3.3 SYS_CLOSE (0x02)
Page 193 and 194:
Semihosting Return On exit, r0 cont
Page 195 and 196:
Semihosting Return On exit, r1 cont
Page 197 and 198:
Semihosting The file position is at
Page 199 and 200:
Semihosting A.3.17 SYS_SEEK (0x0A)
Page 201 and 202:
Semihosting Entry There are no para
Page 203 and 204:
Semihosting Return None. Register r
show all

RealView Compilation Tools Developer Guide - ARM Information ...

Create successful ePaper yourself

Delete template?

Save as template?