FreeCalypso > hg > freecalypso-tools
comparison CHANGES @ 679:be641fa7b68d
CHANGES: fc-loadtool flash e-program-* addition
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Sun, 08 Mar 2020 23:06:03 +0000 |
| parents | 2772cf8435b4 |
| children | 7de96d468c47 |
comparison
equal
deleted
inserted
replaced
| 678:f2a023c20653 | 679:be641fa7b68d |
|---|---|
| 1 Changes in the current code since fc-host-tools-r12: | 1 Changes in the current code since fc-host-tools-r12: |
| 2 | 2 |
| 3 * fc-loadtool memory dump commands (dump2bin and dump2srec) have been | 3 * fc-loadtool changes: |
| 4 reimplemented using loadagent's new BINDUMP command, sending the dump stream | 4 |
| 5 from the target to the host in binary format instead of hex. This change | 5 + Memory dump commands (dump2bin and dump2srec) have been reimplemented using |
| 6 speeds up the dump transfer time by a little over 2x. | 6 loadagent's new BINDUMP command, sending the dump stream from the target to |
| 7 | 7 the host in binary format instead of hex. This change speeds up the dump |
| 8 * fc-loadtool flash programming commands (flash program-bin, program-m0 and | 8 transfer time by a little over 2x. |
| 9 program-srec) have likewise been changed to use a new binary protocol, | 9 |
| 10 producing some improvement in flash programming times, particularly when a | 10 + Flash programming commands flash program-bin, program-m0 and program-srec |
| 11 slow 115200 baud serial link has to be used. | 11 have likewise been changed to use a new binary protocol, producing some |
| 12 improvement in flash programming times - see the updated | |
| 13 doc/Loadtools-performance article. | |
| 14 | |
| 15 + New combined erase+program commands have been implemented: flash | |
| 16 e-program-bin, e-program-m0 and e-program-srec. See the new | |
| 17 doc/Flash-programming article for explanation of the intended usage. | |
| 12 | 18 |
| 13 * fc-xram uses the new binary protocol to transfer the user's XRAM image to the | 19 * fc-xram uses the new binary protocol to transfer the user's XRAM image to the |
| 14 target, producing a speed increase of 3.5x to 5x for the most common use | 20 target, producing a speed increase of 3.5x to 5x for the most common use |
| 15 cases. Also added CRC-32 verification of the downloaded RAM regions before | 21 cases. Also added CRC-32 verification of the downloaded RAM regions before |
| 16 jumping to the downloaded image. | 22 jumping to the downloaded image. |