# HG changeset patch # User Mychaela Falconia # Date 1583020413 0 # Node ID ae4330d86029c0dbe78d52d15e89b48dff43675d # Parent bdb69847c809b83b4b0b97d428200ebe71b879f0 loadtool.help: description of program-m0 updated diff -r bdb69847c809 -r ae4330d86029 loadtools/loadtool.help --- a/loadtools/loadtool.help Sat Feb 29 21:34:03 2020 +0000 +++ b/loadtools/loadtool.help Sat Feb 29 23:53:33 2020 +0000 @@ -276,17 +276,11 @@ === flash:program-m0 flash[2] program-m0 image.m0 -*.m0 is the format that has been used by companies like TI and Closedmoko for -their proprietary firmware images. It is emitted by TI's hex470 tool, and in -the proprietary environment it is fed as an input to FLUID. (The latter is -TI's Flash Loader Utility Independent of Device, and fc-loadtool can be seen as -an independent reimplementation thereof - although it doesn't have the same -level of device-independence.) The *.m0 format is actually a variant of -Motorola's SREC, but with a different byte order: each 16-bit word is -byte-reversed relative to the native byte order of the ARM7 processor. -(This strange byte order actually makes some sense if one views the image as a -long array of 16-bit hex values; 16 bits is the width of the flash memory on -Calypso GSM devices and thus the natural unit size for flash programming.) +Calypso firmware images built with TI's TMS470 toolchain in TI's canonical +manner come out in a hex format that is a variant of Motorola's SREC, in files +ending with the .m0 suffix. We have nicknamed this format "moko-style m0" +after its most famous user; this command programs the flash with an image in +this moko-style m0 format. Because each S-record contains an address, no addresses or offsets need to be specified in the flash[2] program-m0 command, only the image file.