[Elecraft] K3 problem with logging program after download upgrade

[Dick Dievendorff]

Thanks, Bob.  But I didn't detect the corrupt file problem until after the
K3 Utility had started to load the MCU.  I still think I might need to pass
the file twice, once to verify that it's complete and checksums correctly,
and then again to actually load the firmware into the radio.  

Dick, K6KR
 

-----Original Message-----
From: elecraft-bounces at mailman.qth.net
[mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Bob Cunnings
Sent: Tuesday, December 04, 2007 7:26 AM
To: elecraft
Subject: Re: [Elecraft] K3 problem with logging program after download
upgrade

Well,  From the error message I infer that the file is in Intel Hex
format. This format contains a built in integrity check, namely a
checksum for every line. So it seems the uploader did indeed perform
an integrity check - and detected a problem. Relax, these guys *do*
know what they are doing!

For years, at work, I've been using this format for deployment of
firmware images used to update products in the field, it's plenty
robust, nothing else is required, insofar as verifying the file read
in from disk.

Bob NW8L

On Dec 4, 2007 2:24 AM, Julian G4ILO <julian.g4ilo at gmail.com> wrote:
>
> Surely the uploader should do some kind of integrity check, instead of
> attempting to upload a duff file to the radio? It's not exactly rocket
> science. There's a thing called MD5 that's very good for this...
_______________________________________________
Elecraft mailing list
Post to: Elecraft at mailman.qth.net
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft    

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com