Document number
205065
Version
Rev. N
Issue date
2019-02-04
Sirius OBC and TCM User Manual
Page
152
of
174
Table 9.1 Telecommand acceptance failure error types
Error code Data type
Error description
0
UINT8
Illegal APID (PAC error)
1
UINT8
Incomplete or invalid length packet
2
UINT8
Incorrect checksum
3
UINT8
Illegal packet type
4
UINT8
Illegal packet subtype
5
UINT8
Illegal or inconsistent application
data
(unused)
9.3.1. Subtype 1
–
Image transfer start
A telecommand using this subtype has to be sent first before sending any image data and
will set up for a new image upload. It can also be used to abort an existing upload
transaction during the data transfer phase, by simply initializing a new one. The data format
is specified in Table 9.2 below.
Minimum image size is currently 272 bytes including header, and maximum image size is 16
Mbyte.
Table 9.2 Image transfer start command data structure
Total number of bytes in image
Reserved (zero)
Reserved (zero)
UINT32
UINT32
UINT32
A telecommand execution complete report (if requested in the PUS header) will return the
values listed in
in case of a failure
.
Table 9.3 Image transfer start telecommand execution failure codes
Error code
Data type
Error description
EINVAL
UINT8
Imvalid image size
EBUSY
UINT8
Unable to open System Flash for
writing
9.3.2. Subtype 2
–
Image data
This subtype transports data segments of the actual flight software image. Each segment
can be maximum 1000 bytes long (to avoid splitting packets over several frames), and all
segments except the last shall be of maximum length. The data format is specified in Table
9.4 below, with the data length given in the PUS header.
Table 9.4 Image data command structure
Segment number
Segment length
Segment data
UINT16
UINT16
UINT8 UINT8 UINT8
…