In MogdSharp, select "Filesystem" followed by "Upload to device" and then click on "Upload". Select any BIN file. MogdSharp will send the following ascii characters to the display: 254 176 0 64 0 0
This command 254 176 can NOT be found in any PDF file found on the Web site. Does someone know what this command does (probably "Upload file system") and even more important: how it works?
B.t.w. I'm using a GLK24064-25 display.
Cheers!
MogdSharp sends undocumented command
Hello,
Thanks for posting on the forum.
Yes, command 176 is the File System Upload command which is not documented as of the current technical manuals since it is a command we were working on and were not fully tested hence it was not advertised.
As you may see, this command is pretty powerful and it can really make the module break if the user is not well versed with the product.
Here's a quick description of the command:
File System Upload: 254/176/<4 byte length, LSB to MSB>/<data>
This command uploads an image of a filesystem (16KB max) to the display.
The history behind this command is that so large quantity users maybe able to clone modules, bitmaps and fonts are copied exactly to another module.
Please let me know if this helps.
Thanks for posting on the forum.
Yes, command 176 is the File System Upload command which is not documented as of the current technical manuals since it is a command we were working on and were not fully tested hence it was not advertised.
As you may see, this command is pretty powerful and it can really make the module break if the user is not well versed with the product.
Here's a quick description of the command:
File System Upload: 254/176/<4 byte length, LSB to MSB>/<data>
This command uploads an image of a filesystem (16KB max) to the display.
The history behind this command is that so large quantity users maybe able to clone modules, bitmaps and fonts are copied exactly to another module.
Please let me know if this helps.
Raquel Malinis
Design and Development
Matrix Orbital
Design and Development
Matrix Orbital
-
Ray
- Matrix Orbital
- Posts: 745
- Joined: Thu Dec 13, 2001 4:00 pm
- Location: Earth.... I think..
- Contact:
While raquels quick rundown of the command is correct the protocol has a little robustness build in so you can be sure the 16k you send actually gets into the module without any communication errors.
Here's a typical conversation for the fs upload command:
1 ) Send (File System Upload) 254/176/<4 byte length, LSB to MSB>
2 ) Recieve (1 byte status) 1 = Yes, I can handle this go on, anything else error terminating command
3 ) Send first byte of data
4 ) Recieve Echo of the first byte
5 ) Send 1 if echo was correct, send 0 to terminate command
6 ) Send second byte of data
7 ) Recieve echo of second byte
8 ) Send 1 if echo was correct, send 0 to terminate command
Repeat as needed until you send the whole image file.
This command goes hand in hand with the FileSystem Download command which goes like this:
1 ) Send (File System Download) 254/48
2 ) Recieve 2 byte length (LSB -> MSB)
3 ) Recieve data with the specified length.
Here's a typical conversation for the fs upload command:
1 ) Send (File System Upload) 254/176/<4 byte length, LSB to MSB>
2 ) Recieve (1 byte status) 1 = Yes, I can handle this go on, anything else error terminating command
3 ) Send first byte of data
4 ) Recieve Echo of the first byte
5 ) Send 1 if echo was correct, send 0 to terminate command
6 ) Send second byte of data
7 ) Recieve echo of second byte
8 ) Send 1 if echo was correct, send 0 to terminate command
Repeat as needed until you send the whole image file.
This command goes hand in hand with the FileSystem Download command which goes like this:
1 ) Send (File System Download) 254/48
2 ) Recieve 2 byte length (LSB -> MSB)
3 ) Recieve data with the specified length.