Hex File ReferenceThe postlocator is responsible for generating the hex file needed for the ROM flow. It can also be used by emulator and simulator for testing purposes. Due to the data structure of Intel hex files, it is not possible to handle virtual and physical addresses as data structures within the same file nor virtual addresses for multiple levels. Therefore, SLE 79 specific information is provided within comment lines. Such information are comments to be is played in the ROM generator GUI, date and time of creation, segment descriptors, virtual addresses and so on.Note: The Intel hex file is an ASCII text file with lines of text that follow the Intel hex file format. Each data line in an Intel hex file contains one hex record. These records are made up of hexadecimal numbers that represent machine language code and/or constant data. Intel hex files are often used to transfer program and data to be stored in ROM or NVM.1.1 Hex File StructureThe SLE 70 hex file is divided into three parts which have to occur in the described order:• Comment part containing the following information:–As first line “; TYPE=SLE70_MASK_IHEX” as identifier for the SLE 70 hex file format.– Five sections in arbitrary order- COMMENT (optional)- INFO- MEMORY_ADDRESSES- CONFIG- DESCRIPTOR– The keywords inside these sections may contain- Letters “a –z” and ”A –Z” (not case sensitive)- Digits “0 –9” but not as first character- “-” or “_” but not as the first character-Leading and trailing spaces are ignored• Data part which data lines (records) start always with a colon “:”. The only comments allowed in this part are the definitions of the virtual addresses “V_ADDR = 0x...”. These comments are allowed at the beginning of a line and define the virtual address for the following data lines until another definition of the virtual address. The virtual address must contain the level information in the upper byte. The offsetin an extended linear address record affects both the physical and the virtual address. Gaps in the data record section also affect the virtual address.• Optional comment part which is situated after the “end-record” line.General Rules• The indicator for a comment line is t he semicolon “;”.• The indicator for a data line is the colon “:”.• Every character to the right of the equal sign will be assigned to the value of the keyword, except leading and trailing spaces. Quoting of strings containing spaces is not required.• E mpty lines may occur anywhere in the file.1.1.1Body of a SLE 70 HEX FileThe basic structure of a SLE 70 hex file is given below. Optional parts are shown in green.Please note that only within the green marked parts user comments are allowed and may be freely edited. All other parts (red, blue and magenta) must not be changed by the user.Please keep also in mind that within the INFO_SECTION some tool components may appear more than once and in different versions. That is not a fault (is a feature?) because large projects developed over a long time may include modules formerly developed with older tool component versions.1.1.2 Syntax of INFO_SECTION1.1.3 Syntax of MEMORY_ADDRESSES_SECTION1.1.4 Syntax of CONFIG_SECTION1.1.5 Syntax of FILL_MEMORY_SECTION1.1.6 Syntax of SYMBOL_SECTION1.1.7 Syntax of DESCRIPTOR_SECTION1.2 Record FormatAn Intel HEX file is composed of any number of HEX records. Each record is made up of five fields that are arranged in the following format:Each group of letters corresponds to a different field, and each letter represents a single hexadecimal digit. Each field is composed of at least two hexadecimal digits, which make up a byte, as described below:1.2.1 Data RecordThe Intel HEX file is made up of any number of data records that are terminated with a carriage return and a linefeed. Data records appear as follows:1.2.2 End-of-File RecordAn Intel HEX file must end with an end-of-file (EOF) record. This record must have the value 01 in the record type field. Any HEX records following this record will be ignored. An EOF record always appears as follows:1.2.3 Extended Linear Address RecordThe Intel HEX contains extended linear address records when the H386 directive is used. This record is used to specify the two most significant bytes (bits 16 - 31) of the absolute address. This address offset is used for all following data records. Extended linear address records appear as follows:1.3 ExampleHex文件是可以烧录到MCU中，被MCU执行的一种文件格式。