Matrix Orbital GLK12232-25-FGW - Manual (Page 48)

font and bitmap files combined up to 16 Kbytes. This section covers uploading, downloading, deleting and
moving files, as well as getting the remaining space or wiping the filesystem.
12.1.1 File Upload Protocol
In order to allow fonts and bitmaps to be uploaded to the on board flash memory Matrix Orbital has
developed a simple protocol that supports RS-232/TTL or I 2 C communications. In order to begin a file
transmission the first step will be to provide the display module with the appropriate command bytes, mean-
ing the command prefix, 0xFE, followed by the command number, 0x24 for a font file, or 0x5E for a bitmap
file. This will begin the file transfer sequence. The next step will be to request a reference identification
number (ref ID) which will allow you to identify the file for future use. Reference ID numbers can be any
byte between 0x01 and 0xFF, however each ID must be unique.
The next part of uploading a font file is to provide the display module with the two byte file size of the
data that you wish to transfer, LSB to MSB. The LSB must be transmitted first followed by the MSB. After
receiving the MSB the display module will send a confirm byte, 0x01, if the file fits and continue, or decline
byte, 0x08, and terminate the session.
Byte Description
0x01 Confirm: Will continue the file transfer.
0x08 Decline: Terminate the session.
The last part of uploading a font file is to upload the file data. After transmitting each byte of the file the
module will echo the byte and wait for a confirmation byte of 0x01 until the file has completed uploading.
Below is an example of uploading the font file which we created in Section 5.1.2 on page 20.
Matrix Orbital GLK12232-25 43