[Elecraft] K3 MCU LD

[Don Wilhelm]

Jim,

This comes up continuously.

If something interrupts a firmware load, you will end up in the 
condition stated.  I could say "RTFM" or read the prior posts that ask 
the same question -- BUT ---

The cure is to read *carefully* the instructions in either the manual or 
the K3 Utility "to force a firmware load".

Shortcuts do not work - follow the instructions carefully from beginning 
to end, and re-boot the computer with each attempt.

If K3 Utility cannot establish communications, you may have a problem 
with your serial port - if you are using a USB to serial adapter, try 
another one.  Some adapters are good, while others are "flaky" - make no 
assumptions, but do try a different adapter if necessary.  The adapters 
that work use the FTDI chipset.  Make certain you have the latest 
drivers loaded. (a real serial port is the best solution)..

73,
Don W3FPR

On 7/8/2012 11:46 PM, Jim Miller KG0KP wrote:
> I had made several JT65 contacts and a phone contact just prior to this
> problem.
>
> K3 hung up (became constant errors appearing to be communications problems)
> during load of new code from non-updated Utility Program.  Went to website
> and downloaded new Utility and re-downloaded code.  K3 was now in MCU LD
> mode.  Utility indicated during port test that the K3 needed a MCU LD.  This
> only happened once.  After that it was just trying different baud rates on
> the comm port.  Disconnected PC to P3 cable at P3 and connected directly to
> K3.  No change.  Removed that cable and used the cable had gone from the P3
> to the K3.  No change.  Used another PC with a real Comm port and downloaded
> the K3 Utility to it and tried it direct.  That did not work either.
> Different PC, different cable, new loads of Utility and K3 code to each PC
> each direct from the Elecreaft site.  The only common piece here is the K3.
>
> The K3 initially had to have power unplugged as it was totally froze up
> after the initial incident.  When powered on, it came up in MCU LD mode on
> its own.  That is the only time the Utility program said it needed MCU LD.
> The PCs had been rebooted numerous times during this procedure to insure
> there wasn't something being assumed by the PC OS or the Utility program.
> All future times it simply could not communicate, repeatedly trying
> descending baud rates.
>
> Looking at the Utility help files on force loading the MCU, it says to leave
> the K3 without power connected for longer than a few seconds.  This was done
> for a 35 minute period, no change.  Power on was done by procedure of
> holding the power switch in until the transmit light starts blinking and the
> darkened panel shows MCU LD.
>
> I also removed the top cover and removed and reinstalled the KIO3 bd and the
> KXV3 bd.  No loose connections.
>
> I CANNOT talk to it.  Anybody with any ideas, please respond.
>
> Thanks es 73, de Jim KG0KP
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>