MPLAB C Compiler for PIC24 MCUs and dsPIC DSCs ... - Microchip

More documents

Recommendations

Info

16-Bit C Compiler User’s Guide a previous version if the original publisher of that version gives permission. b) List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. c) State on the Title page the name of the publisher of the Modified Version, as the publisher. d) Preserve all the copyright notices of the Document. e) Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. f) Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. g) Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. h) Include an unaltered copy of this License. i) Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. j) Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. k) For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. l) Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. m) Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version. n) Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section. o) Preserve any Warranty Disclaimers. If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles. You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already DS51284H-page 218 © 2008 Microchip Technology Inc.
GNU Free Documentation License includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. G.6 COMBINING DOCUMENTS You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements”. G.7 COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. G.8 AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. © 2008 Microchip Technology Inc. DS51284H-page 219
Page 1 and 2:
MPLAB ® C COMPILER FOR PIC24 MCUs
Page 3 and 4:
Page 5 and 6:
Table of Contents A.5 Identifiers .
Page 7 and 8:
INTRODUCTION MPLAB ® C COMPILER FO
Page 9 and 10:
CONVENTIONS USED IN THIS GUIDE The
Page 11 and 12:
THE MICROCHIP WEB SITE Preface C Re
Page 13 and 14:
1.1 INTRODUCTION 1.2 HIGHLIGHTS MPL
Page 15 and 16:
1.5 COMPILER FEATURE SET Compiler O
Page 17 and 18:
Page 19 and 20:
Differences Between 16-Bit Device C
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Using the Compiler on the Command L
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
3.6 ENVIRONMENT VARIABLES Using the
Page 67 and 68:
Page 69 and 70:
4.1 INTRODUCTION 4.2 HIGHLIGHTS 4.3
Page 71 and 72:
4.5 MEMORY SPACES Run Time Environm
Page 73 and 74:
Run Time Environment 1. It is possi
Page 75 and 76:
4.8 SOFTWARE STACK Run Time Environ
Page 77 and 78:
FIGURE 4-2: CALL OR RCALL Stack gro
Page 79 and 80:
4.11 FUNCTION CALL CONVENTIONS Run
Page 81 and 82:
Run Time Environment The compiler a
Page 83 and 84:
4.14.2 String Literals as Arguments
Page 85 and 86:
Page 87 and 88:
6.1 INTRODUCTION MPLAB ® C COMPILE
Page 89 and 90:
6.3 PMP POINTERS Additional C Point
Page 91 and 92:
6.4 EXTERNAL POINTERS 6.3.3 Define
Page 93 and 94:
ead_external16 Additional C Pointer
Page 95 and 96:
Additional C Pointer Types } else {
Page 97 and 98:
Page 99 and 100:
7.5 USING SFRS Device Support Files
Page 101 and 102:
7.6 USING MACROS Device Support Fil
Page 103 and 104:
EXAMPLE 7-2: EEDATA ACCESS VIA PSV
Page 105 and 106:
Page 107 and 108:
Interrupts When using the interrupt
Page 109 and 110:
8.4.1 dsPIC30F DSCs (Non-SMPS) Inte
Page 111 and 112:
8.4.3 PIC24F MCUs Interrupt Vectors
Page 113 and 114:
Interrupts TABLE 8-3: INTERRUPT VEC
Page 115 and 116:
Interrupts TABLE 8-4: INTERRUPT VEC
Page 117 and 118:
85 _Interrupt85 _AltInterrupt85 Res
Page 119 and 120:
8.8 ENABLING/DISABLING INTERRUPTS I
Page 121 and 122:
Interrupts 2. Unsafe: read bar inte
Page 123 and 124:
LATGbits.LATG2 = 0; /* No problem l
Page 125 and 126:
Page 127 and 128:
Mixing Assembly Language and C Modu
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
A.5 IDENTIFIERS A.6 CHARACTERS Impl
Page 139 and 140:
Implementation-Defined Behavior The
Page 141 and 142:
A.15 PREPROCESSING DIRECTIVES Imple
Page 143 and 144:
A.17 SIGNALS A.18 STREAMS AND FILES
Page 145 and 146:
A.24 GETENV A.25 SYSTEM A.26 STRERR
Page 147 and 148:
B.1 INTRODUCTION MPLAB ® C COMPILE
Page 149 and 150:
__builtin_btg Built-in Functions De
Page 151 and 152:
__builtin_clr_prefetch Argument: xp
Page 153 and 154:
__builtin_dmaoffset Built-in Functi
Page 155 and 156:
__builtin_fbcl Built-in Functions A
Page 157 and 158:
__builtin_modsd Argument: dividend
Page 159 and 160:
__builtin_mpy Error Messages An err
Page 161 and 162:
__builtin_mulss Built-in Functions
Page 163 and 164:
__builtin_psvoffset Built-in Functi
Page 165 and 166:
__builtin_subab Built-in Functions
Page 167 and 168:
__builtin_tblwth Built-in Functions
Page 169 and 170:
C.1 INTRODUCTION C.2 ERRORS MPLAB
Page 171 and 172:
Diagnostics ambiguous abbreviation
Page 173 and 174: Diagnostics cast specifies function
Page 175 and 176: F Diagnostics ‘identifier’ fail
Page 177 and 178: Diagnostics initializer for static
Page 179 and 180: Diagnostics invalid use of undefine
Page 181 and 182: N Diagnostics negative width in bit
Page 183 and 184: R Diagnostics redeclaration of ‘i
Page 185 and 186: Diagnostics symbol ‘symbol’ not
Page 187 and 188: Diagnostics void expression between
Page 189 and 190: Diagnostics anonymous union declare
Page 191 and 192: Diagnostics comparison between sign
Page 193 and 194: duplicate ‘const’ The ‘const
Page 195 and 196: Diagnostics function might be possi
Page 197 and 198: Diagnostics ‘identifier’ is nar
Page 199 and 200: Diagnostics library function ‘ide
Page 201 and 202: P Diagnostics parameter has incompl
Page 203 and 204: Diagnostics shift count >= width of
Page 205 and 206: Diagnostics too many arguments for
Page 207 and 208: V Diagnostics __VA_ARGS__ can only
Page 209 and 210: MPLAB ® C COMPILER FOR PIC24 MCUs
Page 211 and 212: MPLAB C Compiler for PIC18 MCUs vs.
Page 217 and 218: E.1 INTRODUCTION E.2 HIGHLIGHTS MPL
Page 221 and 222: G.1 PREAMBLE MPLAB ® C COMPILER FO
Page 223: G.3 VERBATIM COPYING G.4 COPYING IN
Page 229 and 230: Glossary File Registers On-chip dat
Page 231 and 232: Glossary Machine Language A set of
Page 233 and 234: Glossary Stack, Software Memory use
Page 235 and 236: Symbols __builtin_add..............
Page 237 and 238: -fpack-struct .....................
Page 239 and 240: -idirafter.........................
Page 241 and 242: Peephole Optimization..............
Page 243 and 244: -Wsequence-point...................
show all

MPLAB C Compiler for PIC24 MCUs and dsPIC DSCs ... - Microchip

Create successful ePaper yourself

Delete template?

Save as template?