PAGETBL / PAGETBLV2

Note: in ginmake 2.19+. page tables can be avoided through using a combination of SEGMENT and SEGMENT_ADDRESS definitions.

A file containing a page table may be referenced in a header file using either PAGETBL or PAGETBLV2:

[PAGETBL=COMS.ASM]
[PAGETBLV2=COMS.ASM]

PAGETBL indicates an old-style page table and is present in most existing code. This is now restricted to 32 entries (to catch errors when upgrading to the extended comms protocol) and should have contiguous a EEROM segment. This version of page table allows ROMBS to be used as EEROM in ASM code if it directly follows the EEROM data.

PAGETBLV2 indicates that the page table should be handled differently by Ginmake and is intended for use with the extended comms protocol. PAGETBLV2 does NOT allow ROMBS to be used for calibration data. With PAGETBLV2 it is possible to have breaks in the EEROM data so that parameters and/or ROMBS may be inserted in the middle of the EEROM data without being a part of the calibration. This is generally required when using the extended protocol because the header information must still reside in page 0x1F (i.e. a read of 0xDF 00 using the 13 bit protocol). If splits exist in EEROM, multiple regions will be added to the calibration data with a single checksum added at the location of CHKLOC or CRCLOC. All regions are summed up to the location of the checksum.

Objects such as maps and tables are not allowed to span region boundaries. Ginmake will emit errors in such situations and suggest padding values.

Also see section on SEGMENT definitions for multi-region calibrations / parameter spaces.