[Elecraft] KX3 bricked by F/W upgrade attempt
Matt Zilmer
mzilmer at roadrunner.com
Sun Nov 16 12:57:26 EST 2014
It doesn't sound stupid at all, Rick. I just went through the same
exercise with a K3 I'm rebuilding. On loading it the first time, the
load failed mid-step. Trying to redo the firmware load, the utility
couldn't even find a K3 attached. But it was because of the state of
the serial port driver (or hardware maybe), not some failure at the K3
or within the K3 Utility program.
In this case, I only had to exit the utility and cycle power on the
USB hub with the serial converter attached. After doing that, the
utility found the K3 in its "waiting for firmware load" state.
This same scenario has played out with the KX3 as well. Rebooting the
computer with nothing attached at the serial port would (should) work
just as well.
73,
matt
W6NIA
On Sun, 16 Nov 2014 09:42:44 -0800, you wrote:
>This may sound stupid, but reboot the computer and try again. It might not be the radio not understanding the data coming in the i/o port, but rather it may be the computer (driver) got hosed and isn't sending proper data streams. Who among us hasn't had an OS go stupid?
>
>Then keep it simple, attach to ONLY the radio directly (you did). I also suggest that you do not have the computer attached to the radio during the (radio or computer) boot process because on occasion, the USB device reader (what is attaching?) may 'read' the device improperly and attach the incorrect driver.
>
>If that doesn't work, then 'prove' that the interface cable is still good (test it).
>
>With all the complexity of attaching various components (OS, firmware, hardware) together, it's a wonder any work at all.
>
>You should be able to get it back to working without EEINT, once the firmware is reloaded.
>
>Rick, WA6NHC
>
>iPad = small keypad = typos = sorry ;-)
>
>> On Nov 16, 2014, at 9:32 AM, Randy Diddel <k5rhd at arrl.net> 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....
>>
>> 73
>>
>> K5RHD
>>
>> /randy
>>
>> On Sun, Nov 16, 2014 at 10:09 AM, Don Palmer <d.palmer at btinternet.com>
>> wrote:
>>
>>> Hi hope this may help you if you go to page 43 of your owners manual.
>>>
>>> Look for Parameter Initialization and see if that will help you.
>>>
>>>
>>>
>>> Don
>>>
>>> G6CMV
>> ______________________________________________________________
>> 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 happymoosephoto at gmail.com
>______________________________________________________________
>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 mzilmer at roadrunner.com
Matt Zilmer, W6NIA
--
"Give me six hours to chop down a tree and I will
spend the first four sharpening the axe." -A. Lincoln
More information about the Elecraft
mailing list