Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

The following is a checklist of items that must appear in Config.bib to produce a multiple-XIP image:

  • Define the XIP.

    All XIP regions must be in the order in which they appear in Config.bib.

  • Establish the XIP chain by adding the following lines to the MEMORY section from the sample Config.bib. The reserve section for the chain file must be the first region in the image.

    Copy Code
    #define XIPLOC_PHYSICAL A02C0000; Location of the chain
    RESERVE $(XIPLOC_PHYSICAL) 00002000; CHAIN
    nk.exe: pdwXIPLoc 00000000 $(XIPLOC_PHYSICAL) FIXUPVAR
    
  • Set the following lines in Config.bib in the CONFIG section:

    Copy Code
    XIPSCHAIN = $(XIPLOC_PHYSICAL)
    
  • Define the required fixupvariables in the MEMORY section: nk.exe:pdwXIPLoc.

    This is defined in the sample Config.bib.

  • Reserve a region of RAM for that code, and set the fixup variable to point to it if you are using a RAM region for the flash code as the sample OEM adaptation layer (OAL) does:

    Copy Code
    FLASHFN 8c082000 00001000 RESERVED
    dwFshFnRsvd 00000000 8c082000 FIXUPVAR
    
    Set the dwFshFnRsvdvariable to the same address as the region reserved for the chain file. In the code, add the value of ROM_CHAIN_OFFSET to the variable to dereference the chain location. This should look as follows:

    Copy Code
    dwFshFnRsvd += ROM_CHAIN_OFFSET
    

If you begin with the sample Config.bib, most of the programming is done for you.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.