[Elecraft] KX3 bricked by F/W upgrade attempt

[Phil Wheeler]

Randy,

Re "On a side note, I wish I could use a Mac in 
the shack for everything natively (not in a VM 
like Parallels or VMWare, etc).", you can. Just 
use Bootcamp and install Windows as an alternate 
boot option. I do that with my MBAir and my MBPro. 
Both have solid-state drives, so re-boot is fast. 
I got tired of dealing with Parallels!

73, Phil W7OX

On 11/16/14 11:08 AM, Randy Diddel wrote:
> Don,
>
> You are correct.  I tried it on a Mac with a brand new cable (I have many
> extras as I have bought a lot of Elecraft toys).  See my notes on the post
> that just went to the reflector.  Good ideas and I got to a solution just
> before reading this.  Thanks for the help.
>
> On a side note, I wish I could use a Mac in the shack for everything
> natively (not in a VM like Parallels or VMWare, etc).
>
> Thanks for the input and 73,
>
> K5RHD
>
> /randy
>
> On Sun, Nov 16, 2014 at 11:58 AM, Don Wilhelm <w3fpr at embarqmail.com> wrote:
>
>> Randy,
>>
>> MCU LD is a normal display by the KX3 when waiting for firmware to be
>> loaded.
>> It may be that the KX3 is just sitting there waiting for the computer to
>> feed it some data.
>>
>> Because this all started during a firmware update that stopped midstream
>> for some unknown reason, I would suggest you be suspicious of the computer,
>> the adapter cable and anything else associated with the serial connection.
>> You may even want to try reloading the driver for the USB to serial adapter.
>>
>> It would be a shame to send the KX3 back to Elecraft only to discover that
>> there was a problem at the computer end.  If you have another computer (or
>> can borrow one) try loading the USB cable adapter driver and KX3 Utility on
>> that computer.  If you have an XG3 signal generator, try using the same
>> cable and the XG3 Utility - the cable for the XG3 and the KX3 are the same.
>>
>> 73,
>> Don W3FPR
>>
>>
>> On 11/16/2014 12:32 PM, Randy Diddel wrote:
>>
>>> As I stated. I have read the manua (RTFM)l and tried the EEINT proceedure
>>> stated there. It will NOT respond to a Parameter INIT.  It still says "MCU
>>> LD." I have tried all documented solutions to get it back right.  I
>>> realize
>>> that I would have to recalibrate or load original config file after but I
>>> cannot even get there....
>>>
>>>
>>>
> ______________________________________________________________
> 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
> Message delivered to w7ox at socal.rr.com
>