[Elecraft] [K3] Possible bad file in 4.67 ZIP archive

Tom H Childers n5ge at n5ge.com
Sun May 5 18:03:48 EDT 2013


Downloaded and installed this morning.

I see no problems, and yes I saw the hmcu0467b.hex, but I'm not a bit
worried about it.  My machine and rig working great on my wonderful
Win 7.0 Pro SP1 machine.

73,
Tom
Amateur Radio Operator N5GE
ARRL Lifetime Member
QCWA Lifetime Member

Let's start giving Mr. Uda his due.
The Yagi antenna was designed by 
Mr. Yagi AND Mr. Uda.  It should 
be called the "Yagi-Uda" antenna.

On Sun, 5 May 2013 10:20:48 -0500, Nate Bargmann <n0nb at n0nb.us>
wrote:

>Checking on the available K3 firmware this morning, I saw that a Beta
>4.67 is available.  After downloading and attempting the update, the MCU
>load failed (first time for me).  After a few more tries and failures I
>successfully loaded MCU 4.61, FPF 1.15, and DSP1 2.81 so I knew the K3
>was fine.  :-)
>
>Watching the K3 Utility dialog boxes I saw that file 'hmcu0467b.hex' was
>being loaded.  Looking in the directory, I saw that file 'hmcu0467.hex'
>also was present and 17 minutes newer.  "Hmmmm", sez I, so after
>deleting 'hmcu0467b.hex', MCU 4.67, FPF 1.15, and DSP1 2.81 firmware
>files all loaded correctly.
>
>I am using the "Elecraft K3 Utility for Linux Version 1.12.9.22", if
>that matters.
>
>As the file size between 'hmcu0467b.hex' and 'hmcu0467.hex' is the same
>(but the "diff" utility shows a lot of differences), the utility
>apparently chooses 'hmcu0467b.hex' by determining that the extra
>character makes it a later file.  In this particular case, it happens to
>be earlier and this K3, S/N 4762, didn't like it at all.
>
>On the plus side, I now know how to recover from a bad MCU load, the
>first time this has happened to me in over 2 1/2 years of owning my K3.
>;-)
>
>73, de Nate, N0NB >>



More information about the Elecraft mailing list