Figure out why firmware uploading appears to fail

[jverne]

Figure out why firmware uploading appears to fail

[jverne]

Duh. The initial transfer is the "nub" that is sent first, and then it sends the firmware S-record.

It looks like any firmware transfer is getting out of sync. The brick thinks it is updated, and nqc is simply trying to end the conversation, and is retrying until it issues an error:

[...]
.sending 144 bytes
Tx: 55 ff 00 45 ba 00 ff 00 ff 90 6f 00 ff 6d 92 75 8a 6d 92 74 8b 54 ab 70 8f 6d 92 f2 0d 6d 92 f3 0c 6d 92 f4 0b 6d 92 f5 0a 6d 92 f6 09 6e 91 73 8c 00 ff 0d f2 6e 91 7a 85 00 ff 0f f0 aa 55 03 fc 44 bb 16 e9 69 96 76 89 08 f7 ae 51 96 69 00 ff 6e 91 6b 94 00 ff 3b c4 eb 14 e0 1f 12 ed 8b 74 12 ed 8b 74 12 ed 8b 74 eb 14 07 f8 40 bf 04 fb 0c f3 ab 54 8b 74 05 fa 0c f3 3e c1 18 e7 66 99 09 f6 66 99 0c f3 bd 42 18 e7 55 aa 09 f6 55 aa 6f 90 54 ab c3 3c fe 01 6f 90 e4 1b cb 34 82 7d 0c f3 3e c1 18 e7 66 99 09 f6 66 99 0c f3 bd 42 18 e7 55 aa 09 f6 55 aa 6f 90 54 ab c4 3b 1e e1 6f 90 e4 1b cb 34 62 9d 0c f3 3e c1 18 e7 66 99 09 f6 66 99 19 e6 55 aa 6f 90 e5 1a cb 34 f2 0d 0c f3 3e c1 18 e7 66 99 09 f6 66 99 79 86 05 fa 00 ff 0f f0 6f 90 e5 1a cb 34 d2 2d 0c f3 3e c1 18 e7 66 99 09 f6 66 99 19 e6 55 aa 6f 90 e5 1a cc 33 12 ed 0b f4 87 78 6d 92 75 8a 6d 92 74 8b 6d 92 73 8c 6d 92 72 8d 54 ab 70 8f af 50 33 cc
reading 9 bytes, timeout = 300
Rx: 55 ff 00 ba 45 00 ff ba 45
.Tx: 55 ff 00 a5 5a 4c b3 45 ba 47 b8 4f b0 ae 51 7a 85
reading 57 bytes, timeout = 50
Rx:
Retrying...

Tx: 55 ff 00 15 ea 01 fe 03 fc 05 fa 07 f8 0b f4 30 cf
reading 23 bytes, timeout = 50
Rx:
Retrying...
Tx: 55 ff 00 15 ea 01 fe 03 fc 05 fa 07 f8 0b f4 30 cf
reading 23 bytes, timeout = 50
Rx:
Retrying...
Tx: 55 ff 00 15 ea 01 fe 03 fc 05 fa 07 f8 0b f4 30 cf
reading 23 bytes, timeout = 100
reading 1 byte, timeout = 100
Rx: 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17
Retrying...
Tx: 55 ff 00 15 ea 01 fe 03 fc 05 fa 07 f8 0b f4 30 cf
reading 23 bytes, timeout = 200
Rx: 55 ff 00 ea 15 00 ff 03 fc 00 ff 01 fe 00 ff 03 fc 03 fc 02 fd f6 09
No reply from RCX
3458 (253)%
[...]

Even after this error, it works. In fact. I can't reproduce a failed upload in any mode. So, there is a subtle bug here.

[jverne]

So, the top-level nqc DownloadFirmware() is succeeding all the way from unlock to nub to firmware, for both regular and fast.

What is failing is GetVersion() being called immediately after the successful firmware download. It is failing with kRCX_ReplyError (-3).