Get bytes

Transfer of core dumps, files and raw flash from the watch to the phone. More...

Modules
	Get bytes protocol
	Get bytes endpoint messages.
	Get bytes storage
	Backends reading the transferred objects.

Enumerations
enum	GetBytesObjectType { GetBytesObjectUnknown = 0x00 , GetBytesObjectCoredump = 0x01 , GetBytesObjectFile = 0x02 , GetBytesObjectFlash = 0x03 }
	Object types transferred over get bytes. More...
enum	GetBytesInfoErrorCode {   GET_BYTES_OK = 0 , GET_BYTES_MALFORMED_COMMAND = 1 , GET_BYTES_ALREADY_IN_PROGRESS = 2 , GET_BYTES_DOESNT_EXIST = 3 ,   GET_BYTES_CORRUPTED = 4 }
	Error codes of the GET_BYTES_CMD_OBJECT_INFO response. More...

Detailed Description

Transfer of core dumps, files and raw flash from the watch to the phone.

A Pebble Protocol endpoint. The phone sends a request (see GetBytesCmd), and the watch answers with a GET_BYTES_CMD_OBJECT_INFO message holding an error code and the object size, followed on success by GET_BYTES_CMD_OBJECT_DATA chunks until the whole object is sent. Multi-byte fields are big-endian. Only one transfer runs at a time. File and flash reads are not available in release builds.

Objects are read through a Get bytes storage backend.

Enumeration Type Documentation

GetBytesInfoErrorCode

enum GetBytesInfoErrorCode

Error codes of the GET_BYTES_CMD_OBJECT_INFO response.

Enumerator
GET_BYTES_OK	Success, data follows.
GET_BYTES_MALFORMED_COMMAND	Invalid or unsupported request.
GET_BYTES_ALREADY_IN_PROGRESS	Another transfer is in progress.
GET_BYTES_DOESNT_EXIST	The object does not exist, e.g. no (new) core dump.
GET_BYTES_CORRUPTED	The object is corrupted.

GetBytesObjectType

enum GetBytesObjectType

Object types transferred over get bytes.

Enumerator
GetBytesObjectUnknown	Unknown.
GetBytesObjectCoredump	Core dump.
GetBytesObjectFile	PFS file.
GetBytesObjectFlash	Raw flash region.