Subid nb_progcmd message format, Subid nb_eraserep message format, Table 49: subid nb_chkcrcrep message format – NavCom Sapphire Rev.J User Manual
Page 77: Table 50: subid nb_progcmd message format
Sapphire Technical Reference Manual Rev. J
77
Table 49: SubID NB_ChkCrcRep Message Format
Field
Data
Type
Value and Description
Function Type SubID
U08
Enum NB_ChkCrcRep.
Pass or Fail
U08
1= pass, 0 = fail.
Valid count
U16
This is the length for the data field (in bytes).
4 if fail due to CRC error
0 otherwise
Address
U32
If pass, value is 0.
If fail due to maximum address not equal to the value in
NB_SetupCmd, value is error code Err_MaxAddr.
If fail due to CRC error, value is error code Err_BadCrc.
Data
U32
This field only exists if fail due to CRC error. Its value is the
computed CRC32 of the data image.
1.20.2.11
SubID NB_ProgCmd Message Format
SubID NB_ ProgCmd is sent from PC to receiver. It is used to tell the receiver to start
programming the new data into flash. After receiving this command, the receiver starts
erasing the Flash and writing the new data into flash.
The cold bootloader sends the NB_EraseRep, NB_WorkingRep and NB_WriteRep
messages (described below) while programming, then waits for additional commands.
The warm bootloader responds with an NB_WriteFRep response, then automatically
reboots after programming is complete.
The NB_ ProgCmd format is defined in Table 50.
Table 50: SubID NB_ProgCmd Message Format
Field
Data
Type
Value and Description
Function Type SubID
U08
Enum NB_ProgCmd.
Pass or Fail
U08
This field is not used for this command. The value should be 0.
Valid count
U16
0
Address
U32
0
1.20.2.12
SubID NB_EraseRep Message Format
SubID NB_EraseRep is sent from receiver to PC. It is one of the reply messages for
NB_ProgCmd. The receiver sends out this message after it erases Flash, which typically
takes 1 to 3 seconds. Its format is defined in Table 51. This reply is sent by the PIO cold
bootloader, but not the warm bootloader.