Technical Support
Support Resources
Product Information
BL51: Absolutely Locating Startup Code BL51: Accessing XDATA Memory at Non-standard Addresses BL51: Avoiding Function Pointer Problems With NOOVERLAY BL51: Batch File for Banked Applications BL51: Burning EPROM from BL51 Files BL51: Call Tree Using Pointers to Functions BL51: Configuration For a Von Neuman Architecture BL51: Configuring XDATA Latch for Code Banking BL51: Creating Data-only Hex Files BL51: Data Memory Overlap When Using PRECEDE Directive BL51: Disable Automatic Bank Switching BL51: DP, DS And DL Directives BL51: Embedding Comments in a Command File BL51: Error 107 (Address Space Overflow) BL51: Error 118 (Erroneous Reference to External Variables) BL51: Error 121 (Improper Fixup) BL51: Error 121 (Improper Fixup) BL51: Error 121 (Improper Fixup) with ROM(Small) BL51: Error L103 (External Attribute Do Not Match Public) BL51: Error L107 (Address Space Overflow) BL51: Error L107 (Address Space Overflow) for ?STACK BL51: Error L107 (Address Space Overflow)with inline ASM BL51: Fatal Error 232 (Application Contains ... Recursions) BL51: Fatal Error 250 (Code Size Limit...) BL51: Fatal Error L210 (I/O Error on L51_bank.Obj) BL51: Function Pointer, Code Banking and NOOVERLAY BL51: Generating User Exception for XDATA Overflow BL51: How Do I Remove AMAKE Records From My OMF File? BL51: How Does Overlay Analysis Work? BL51: How Much Code and Data Are Used? BL51: Ignore Warning 13 (Recursive Call to Segment) BL51: Increasing the Speed of the BL51 Data Overlaying Analysis BL51: Initializing & Locating a Variable to a Fixed Address BL51: Interrupt Generates Warning 16 (Uncalled Segment) BL51: Leaving Holes in CODE Space BL51: Linker Ordering Segments by Size BL51: Linking Programs Larger Than 64K BL51: Listing File Overview BL51: Locating Constant (Code) Variables in a Code Bank BL51: Locating Functions at Ascending Addresses BL51: Locating Functions in Code Banking Programs BL51: Locating Groups of Code Segments Together BL51: Locating Individual Segments While Using Start Address BL51: Long Command Lines BL51: Not Finding Some Functions in Libraries BL51: Obtaining the Memory Map of a Project BL51: Order of Modules in Linking Using In-line Assembly BL51: Overlay Data From Interrupt Routine With Main BL51: Overlaying Bit-addressable Segments BL51: Putting Interrupts in Flash ROM BL51: Setting the Size of Code Space BL51: SFRs Listed for Each Source File BL51: Specifying CODE and XDATA Ranges BL51: Specifying the Order in Which OBJ Files Are Linked BL51: Starting Address for Variables in RAM BL51: SYMBOL vs. PUBLIC Variables BL51: The Code Banking Mechanism BL51: Unresolved External Symbol for Math and FP Routines BL51: Unresolved Symbol ?C_STARTUP BL51: Using Function Pointers With Code Banking BL51: Using Wildcards in Segment Names BL51: Warning 1 (Unresolved External Symbol) Using SBITs BL51: Warning 5 (Code Space Memory Overlap) BL51: Warning 6 (XDATA Memory Space Overlap) Using _AT_ BL51: Warning 7 (Module Name Not Unique) BL51: Warning 15 (Multiple Call To Segment) BL51: Warning 16 (Uncalled Segment, Ignored for Overlay Process) BL51: Warning 16 (Uncalled Segment...) for Called Function BL51: Warning 20 (NBANKS LESS THAN # OF CODE BANKS), PT 2 BL51: Warning L1 (Unresolved External) Using Inline Assembly BL51: Warning L13 (Recursive Call to Segment) with Constants BL51: Warning L16 (Uncalled Segment) ?C_INITSEG BL51: Warning L16 (Uncalled Segment, Ignored for Overlay) BL51: Warning L2: Unresolved External for Functions in C Runtime Lib BL51: Warning L4 (Data Space Memory Overlap) BL51: What Are _DATA_GROUP_ and _BIT_GROUP_? BL51: What Is the _XDATA_GROUP? BL51: Writing Your Own Code Banking System
Cookie Settings | Terms of Use | Privacy | Accessibility | Trademarks | Contact Us | Feedback
Copyright © 2005-2019 Arm Limited (or its affiliates). All rights reserved.
This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.
Change Settings
Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers of your data.