Bootloadb message body general format, Function type, Table 18: bootloadb binary message – NavCom Sapphire Rev.J User Manual
Page 60

Sapphire Technical Reference Manual Rev. J
60
Table continued on next page
…
Field
Data Type
Value and Description
Time
U08[9]
ANSI C standard software build time string; example: 17:17:11
Reserved1
U08[3]
Reserved field
Product type
U08
Spin number
U08
Software spin number
Reserved2
U08
Reserved field
Swinfo_ver
U08
Software Info structure (this structure) version
Product string
U08[28]
Descriptive text string for the product. See Table 22 for the list.
The data portion of those s0 records contains a maximum of 44 hex characters
(representing 22 bytes of data). The total size of the software_info structure is 64 bytes,
so the second and third s0 record contain 22 bytes of data, and the forth s0 record
contains 20 bytes of data.
Example s0 records for bootloader1 “.s19” file:
S01600004E4354205357494E464F20564552203030310050
S0190000FFF12AA0010201004A756C203234203230303900313724
S01900003A32313A33380000000003000001534F4C415249532063
S0170000474E535320424F4F54310000000000000000000028
Decoding of the first s0 record:
S0 16 0000 4E4354205357494E464F2056455220303031 00 50
length | N C T S W I N F O V E R 0 0 1 | checksum
address terminating null character
1.19.2 BOOTLOADB Message Body General Format
The BOOTLOADB message general format is defined in the following table:
Table 18: BOOTLOADB Binary Message
Data Item (8 Bytes + data)
Data Type
Function Type SubID (enum)
U08
Pass or Fail (1 = pass, 0 = fail)
U08
Valid count
U16
Address
U32
Data
U08
1.19.2.1 Function Type
Function Type provides a Function/SubID of the command. The following function type
subIDs are defined as enum: (Enums ending
with “Cmd” are commands sent from a PC
tool to the receiver. Enums ending
with “Rep” are replies sent from the receiver to a PC
tool).