Craig and all, Dick has indicated several times that the firmware does have checking data bits, and they are used for validity checks and as an indication that the firmware downloads are successful.
What is happening in the discussion that has ensued is that the MicroHam device is adding (or changing) bits in the stream of firmware data that is being sent to the K3. Yes, when an incorrect write is detected by K3 Utility, it will stop and indicate a failure, Unfortunately, that corrupted data has already scrambled the K3's "brain", and it cannot operate, so you have to follow the "Unplug the power" recovery procedure and try again. I do not know how any additional degree of "robustness" in K3 Utility could correct for that condition. For an analogy of what is happening, I think of a water pipe. There is a clean pump (akin to K3 Utility) that checks and puts clean water (the firmware data bits) in the pipe. Further down that pipe is an opening (akin to the Microham) where dirt and other unwanted stuff is inserted. No way could one expect clean water out of the far end under that situation - and it is not the pump's fault. Bottom line - don't load firmware through a Microham device and expect good results. 73, Don W3FPR On 2/6/2011 2:41 PM, Craig - AE6RR wrote: > > It would be nice if the upgrade installation software was a bit more robust > and didn't just give up if it gets a bad record (the records do have > checksums or some other validity check, I hope). If it would try again > after a bad record, it could probably recover. > > 73, > - Craig, AE6RR > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
