??? 07/28/05 14:11 Read: times |
#98359 - error detection Responding to: ???'s previous message |
Craig Steiner said:
I don't remember if it's the Dallas or the TI part, but one of them acknowledges each HEX line with a pass/fail flag immediately based on the HEX file's line checksum. ALL of them do. See my table, row entitled "command confirmation". It is also a way to let the PC know that the command is accomplished (data programmed) - but usually a small constant delay at the end of the line is enough, see datasheet (or the table) for how long programming of a byte/a row takes. The problem is that the echoed data plus the confirmation scrolls too fast. Some terminals have "screen buffers" sop you can scroll back many lines, other allow data capturing; yet another is able to count occurence of certain character - so probably one can find his way. And if not, it is always possible to read back the content (or a checksum - LPC9xx) and compare. Jan Waclawek |
Topic | Author | Date |
UART-ISP | 01/01/70 00:00 | |
Corrections ?? | 01/01/70 00:00 | |
Clairvoyants wanted :-) | 01/01/70 00:00 | |
and so what | 01/01/70 00:00 | |
ADuC8xx | 01/01/70 00:00 | |
benefits of readable protocol | 01/01/70 00:00 | |
comments | 01/01/70 00:00 | |
Error reporting | 01/01/70 00:00 | |
expanding | 01/01/70 00:00 | |
Not sure, but... | 01/01/70 00:00 | |
error detection | 01/01/70 00:00 | |
tedious | 01/01/70 00:00 | |
Probably, not sure | 01/01/70 00:00 | |
option, yes - solution, no | 01/01/70 00:00 | |
When did he do that? | 01/01/70 00:00 | |
not Jan, but Ian, not Gates but Linux | 01/01/70 00:00 | |
Linux is a good reason why | 01/01/70 00:00 | |
flip for linux | 01/01/70 00:00 | |
Excellent! | 01/01/70 00:00 | |
Main benefit IMHO | 01/01/70 00:00 | |
readable or not | 01/01/70 00:00 | |
caveats of using terminal | 01/01/70 00:00 | |
DOS | 01/01/70 00:00 | |
DOS is DOS | 01/01/70 00:00 | |
DOS version of Download for ADuC8X![]() | 01/01/70 00:00 |