TMP92CZ26A

92CZ26A-65

b. Notes on the user program form at (binary)
1. After receivi ng the checksum of a rec ord, the boot progr am waits for the star t
mark (3AH for “:”) of the next record. If data other than 3AH is received
between records, it is ignored.
2. Since the address pointer is initially set to 00H, the record type to be
transferred first does not have to be an address record.
3. Addresses 3000H to 497FFH (282 Kbytes) are allocated as the user program
download area. Th e user program should be contained within this area.
4. A user pr ogram in Intel Hex format (normall y written in ASCII code) must be
converted into binary data before it can be transferred. See the example
below for how to convert an Intel Hex file into binary format.
When a user program is downloaded via USB , the maximum allowed record
length is 250 bytes.
Example: Transfer data when writing 16-byte data in Intel Hex format from address 3000H
The following shows how an Intel Hex format file is displayed on a text editor.
: 103000000607F100030000F201030000B1F16010B7
: 00000001FF
However, the actual data consists of ASCII codes, as shown below.
3A3130333030303030303630374631303030333030303046323031303330303030
423146313630313042370D0A3A303030303030303146460D0A
Thus, the ASCII codes must be converted into binary data based on the conversion rules shown
in the table below.
ASCII Code Binary Data
3A 3A (Only 3A remains the same.)
30~39 0~9
41 or 61 A
42 or 62 B
43 or 63 C
44 or 64 D
45 or 65 E
46 or 66 F
0D0A Delete
The above Intel Hex file is converted into binary data as follows:
Data record 3A 10 3000 00 0607F100030000F201030000B1F16010 B7
Data Checksum
Record type
Address
Record length
: (Start mark\)
End record 3A 00 0000 01 FF
Checksum
Record type
Address
Record length
: (Start mark)