[Elecraft] K3 comatose - sorted, thanks
Stewart Rolfe
gw0etf at btinternet.com
Thu Feb 21 07:58:46 EST 2008
dj7mgq at muenchen-mail.de wrote:
> Hi Stewart,
>
>> I'm sure it's just in a coma and wonder if anyone here knows how to
>> resuscitate prior to Aptos waking up; maybe I should play some music to
>> it, always thought the K3 would be a Frank Zappa sort of radio.....
>> There must be contingency plans for repairing wiped out firmware such
>> as would happen if a power cut occurred mid way through a re-flash so
>> I'm not panicking (yet).
>
>
> Try doing this:
> ================================================
> Forcing a Firmware Download
>
> If you accidentally load an old or incompatible
> firmware version and find the K3 unresponsive, do
> the following:
>
> (1) unplug the K3 from the power supply and wait 5 seconds;
>
> (2) plug the power supply back in;
>
> (3) hold the K3?s POWER switch in; after about 10 seconds, you?ll see
> the TX LED flash (you?ll also see MCU LD on the LCD);
>
> (4) load the correct firmware version.
> ================================================
> From page 42 of K3 Owners Manual C1.pdf
>
> vy 73 de toby
Toby and Ken,
I tried a 'Force Firmware Download' but got the response from the K3
Utility of no response from the K3. Then I remembered I use a virtual
com port via my Microham cw keyer and the usb router; this normally
works fine but I tried a direct hardware comm port connection and the
'forcing' worked....! so all is well now and many thanks for the quick
responses to you both.
Presumably the interruption screwed the virtual com port software
interface while leaving the hardware port unscathed. I've just
reconnected the Microham and reset the port settings and all is back to
normal between the radio and upload utility.
73,
Stewart, GW0ETF
More information about the Elecraft
mailing list