C166/ST10 Cross-Assembler, Linker/Locator, Utilities ... - Tasking

• • • • • • • •
Utilities 10−31
Space
BITA
BIT
non−
segmented
Size Maximum Object Size
segmented
non−
segmented
segmented
RAM ROM RAM ROM RAM ROM RAM ROM
256
(bytes)
2048
(bits)
0 256
(bytes)
0 2048
(bits)
0 256
(bytes)
0 256
(bytes)
0 1 (bit) 0 1 (bit) 0
Table 10−3: Default properties memory spaces that overlap IRAM
These two memory spaces are not used during the automatic allocation
process but overlap the IRAM memory space. So, a reservation or a direct
allocation in one of the memory spaces will influence the available space
in the IRAM memory space.
You can set most of the properties of the above listed memory spaces with
the −m and −T command line options. The −m option controls the
available memory in a particular space. The −T option controls the
maximum object size that can be allocated in a particular memory space.
See section 10.6.8, Options for the details of the options −m and −T.
Each time gso166 generates a .gso file, it will set the $GSO166 directive
in this file. c166 does not accept a file that does not have this directive. A
file that has both the $GSO166 directive and an object allocated in
memory space ’AUTO’, is considered invalid.
10.6.4 PRE−ALLOCATION FILES
With a pre−allocation file gso166 can be forced to allocate a particular
object into a certain memory space. The memory specified in a
pre−allocation file is applied after linking the application. You cannot
overwrite any memory space other than the ’AUTO’ memory space.
You can specify pre−allocation files on the command line with the −a
option. Multiple −a options (pre−allocation files) are allowed.
The format of pre−allocation files is described in section 10.6.10,
Pre−allocation File Format.
0