|RGBLINK(5)||File Formats Manual||RGBLINK(5)|
A linker script consists on a series of banks followed by a list
of sections and, optionally, commands. They can be lowercase or uppercase,
it is ignored. Any line can contain a comment starting with
;’ that ends at the end of the
ROMX $F ; This is a comment "Functions to read array" ALIGN 8 "Array aligned to 256 bytes" WRAMX 2 "Some variables"
Numbers can be in decimal or hexadecimal format (the prefix is
$’). It is an error if any section
name or command is found before setting a bank.
Files can be included by using the
keyword, followed by a string with the path of the file that has to be
The possible bank types are:
HRAM. Unless there is a single bank, which can occur
WRAMX, it is needed
to specify a bank number after the type.
When a new bank statement is found, sections found after it will be placed right from the beginning of that bank. If the linker script switches to a different bank and then comes back to a previous one, it will continue from the last address that was used.
The only two commands are
ORGsets the address in which new sections will be placed. It can not be lower than the current address.
ALIGNwill increase the address until it is aligned to the specified boundary (it tries to set to 0 the number of bits specified after the command: ‘
ALIGN 8’ will align to $100).
Note: The bank, alignment, address and type of
sections can be specified both in the source code and in the linker script.
For a section to be able to be placed with the linker script, the bank,
address and alignment must be left unassigned in the source code or be
compatible with what is specified in the linker script. For example,
ALIGN’ in the source code is
compatible with ‘
ORG $F00’ in the
rgblinkwas originally written by Carsten Sørensen as part of the ASMotor package, and was later packaged in RGBDS by Justin Lloyd. It is now maintained by a number of contributors at https://github.com/gbdev/rgbds.
|November 26, 2019||Linux|