NavCom Sapphire Rev.J - Manual (Page 59)

Sapphire Technical Reference Manual Rev. J
59
1.19 BOOTLOADB (Binary)
SF-3050 Sapphire SF-3040
GNSS Bootloader1 and Bootloader2 monitor the serial ports for the download of SF-3050 binary
software messages. [BOOTLOADB] is the message ID for the software that is being
downloaded. BOOTLOADB uses the simplified Sapphire binary header format described in
Table 9.
On COM1 of the SF-3050, the maximum PC baud rate to download PIO firmware via a
Serial Connection is 115200 (see Table 24).

On COM2 of the SF-3050, the required PC baud rate to download PIO firmware via
a Serial Connection is 57600.
These requirements do not apply to a USB 2.0 Device or Ethernet connection.
1.19.1 Bootload Input File Format
The input file to the bootload process is the “.s19” file. This file format is generated by
the software build process post-linker tool. It is the standard Motorola s-record file with
special s0 record for Solaris.
The input file for the GNSS board bootload process could be one of the following:
GNSS bootloader1, bootloader2, and NAV program (main application).
For Solaris (Sapphire), the input file for the PowerIO board bootload process could be
one of the following: PIO bootloader and application.
1.19.1.1 Solaris (Sapphire) S0 Record Format
For Solaris, the s19 file includes multiple lines of s0 records, which contain useful
information about the details of the software image, including the version, product type,
product string, build data, time, etc. The information can be used with the bootloading
tool to tell which program it is loading. Some older versions of the s19 file build do not
implement this format of the s0 record.
The first s0 record contains the string “NCT SWINFO VER 001”. This line defines the
version of the software info structure that follows.
The “001” is the current version.
The second, third, and forth lines of the s0 record contain the software_info structure
defined below.
Table 17: Software Info Structure Definition
Field Data Type Value and Description
CRC32 pointer U32 Address of the CRC32 of the whole software image
Major version U08 Software major version
Minor version U08 Software minor version
Build number U08 Software build number
Software type U08 Software type enum defined in Table 22
Data U08[12] ANSI C standard software build date string.
Example: Mar 13 2009