INS401 User’s Manual
_____________________________________________________________________________________
Doc# 7430-3305-08
Page 32
The sent JA command needs to include the CRC values of rtk.bin and ins.bin. After receiving the
JA command, the MCU will calculate the CRC of the written rtk.bin and ins.bin. Only when the
calculated CRC values are correct , It will jump to the APP, otherwise it will stay under
BootLoader.
Table 18 Set Update Core and Bin Size (CS)
Send:
Header
Msg_Type
Length
Data
CRC
0x5555
0xaa04
9
Update
core
2 bytes
Bin size
4 bytes
AppInfo
3Bytes
2 bytes
Receive:
Header
Msg_Type
Length
Data
CRC
0x5555
0xaa04
2
Update
core
2 bytes
‘
S
’
– Set Succ
‘
F
’
-- Set Failed
2 bytes
Update core = “C0” or “C1”. “C0” corresponds to rtk_app, and “C1” corresponds to ins_app.
Bin size is the length of the actual rtk or ins bin file. This value should be sent with the high
order first.
*bin_size = (ptrUcbPacket->payload[2] << 24) |
(ptrUcbPacket->payload[3] << 16) |
(ptrUcbPacket->payload[4] << 8) |
(ptrUcbPacket->payload[5] );
It should be noted that when the host computer reads All.bin, it confirms the burned bin.
For example, when burning rtk.bin, in addition to identifying the rtkstart information in all.bin,
the host computer should also identify the information in Bin to ensure that it is the real rtk.bin.
When it is confirmed as rtk.bin, fill in "rtk" in the AppInfo section. When the MCU receives the
correct CS command, it returns'S', otherwise, it returns'F'.
At the same time, when the Update core in the CS command is not "C0" or "C1", the MsgType
of the returned frame = 0x1515.
Table 19 Write APP Bin (WA)
Send:
Header Msg_Type Length
Data
CRC
0x5555 0xaa03
Nu
8
start Addr 4 bytes
Numbytes 4 bytes BinData 2 bytes