# HG changeset patch # User Mychaela Falconia # Date 1583098249 0 # Node ID cd031e2501fad4d96e970824f356b7be501342e9 # Parent 44bc757ce2a5a4740ee43a3c844d43d8de1fd068 loadtool.help: dump2bin and dump2srec improvements diff -r 44bc757ce2a5 -r cd031e2501fa loadtools/loadtool.help --- a/loadtools/loadtool.help Sun Mar 01 21:11:52 2020 +0000 +++ b/loadtools/loadtool.help Sun Mar 01 21:30:49 2020 +0000 @@ -107,14 +107,13 @@ argument is the length of the area to dump, also in hex; the third argument is the name of the output file to be created/written. The dump will be saved in binary or S-records as per the chosen command, always in the native byte -order of the Calypso ARM7 target (little-endian). As an implementation limit, -both the starting target memory address and the length of the area to dump need -to be aligned to 128 bytes. +order of the Calypso ARM7 target (little-endian). -dump2srec is deprecated, please use dump2bin instead. If you do use dump2srec, -the S-record image will be written with 128 bytes of payload per record (270 -ASCII characters per line), which is significantly longer records than most -SREC conventions. +The 128 byte alignment requirement of previous versions has been lifted; you +can now dump as little as one byte without any alignment restrictions. In the +case of dump2srec the output file will be written with 32 bytes of payload per +S3 record, with the last record carrying from 1 to 32 bytes of payload as +needed. === exec exec