Elecraft › [K3]

help - firmware hangup

Classic

List

Threaded

15 messages Options

RobertG

help - firmware hangup

I have "lost contact" with my K3. I was trying to load the 4.51 firmware
when I got an error report in the K3 utility program, and the K3 became
unresponsive. Now, the TX light is blinking and MCU LD displays on the
lcd. The computer terminal program keeps trying to establish contact
with no results. In the K3 utility notice window, the program is
continuously cycling through various baud rates with no luck. I tried to
reset the radio using the PWR on - press SHIFT/LO 0 [KE7X p32] but
nothing happens. I have shut everything down and powered back up but
without results. The red TX light and MCU LD is all that I can get. Thanks.

...robert
--
Robert G. Strickland, PhD, ABPH - KE2WY
[hidden email]
Syracuse, New York, USA

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Dick Dievendorff

Re: help - firmware hangup

See K3 Utility Help, Troubleshooting MCU Load failure. It has a step by step
recovery procedure.

73 de Dick, K6KR

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Robert G. Strickland
Sent: Saturday, June 30, 2012 6:43 AM
To: Elecraft
Subject: [Elecraft] help - firmware hangup

I have "lost contact" with my K3. I was trying to load the 4.51 firmware
when I got an error report in the K3 utility program, and the K3 became
unresponsive. Now, the TX light is blinking and MCU LD displays on the lcd.
The computer terminal program keeps trying to establish contact with no
results. In the K3 utility notice window, the program is continuously
cycling through various baud rates with no luck. I tried to reset the radio
using the PWR on - press SHIFT/LO 0 [KE7X p32] but nothing happens. I have
shut everything down and powered back up but without results. The red TX
light and MCU LD is all that I can get. Thanks.

...robert
--
Robert G. Strickland, PhD, ABPH - KE2WY
[hidden email]
Syracuse, New York, USA

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

RobertG

Re: help - firmware hangup

Dick...

Thanks for responding. Still no joy after going through all the HELP
suggestions. The problem seems to be an inability to connect from the
computer to the K3. Note, this whole arrangement has been working
perfectly up to this point. No cable changes, etc. What I get when
trying to establish a connection to the K3 is a steady hunt through
various baud rates with no success. I have cycled everything many times.
I am not using a serial-USB adapter. I am connecting via a microHAM CW
KEYER [which has been working without problems]. I think I'm getting
desperate! Thanks again.

...robert

On 6/30/2012 16:00, Dick Dievendorff wrote:

> See K3 Utility Help, Troubleshooting MCU Load failure. It has a step by step
> recovery procedure.
>
> 73 de Dick, K6KR
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Robert G. Strickland
> Sent: Saturday, June 30, 2012 6:43 AM
> To: Elecraft
> Subject: [Elecraft] help - firmware hangup
>
> I have "lost contact" with my K3. I was trying to load the 4.51 firmware
> when I got an error report in the K3 utility program, and the K3 became
> unresponsive. Now, the TX light is blinking and MCU LD displays on the lcd.
> The computer terminal program keeps trying to establish contact with no
> results. In the K3 utility notice window, the program is continuously
> cycling through various baud rates with no luck. I tried to reset the radio
> using the PWR on - press SHIFT/LO 0 [KE7X p32] but nothing happens. I have
> shut everything down and powered back up but without results. The red TX
> light and MCU LD is all that I can get. Thanks.
>
> ...robert
> --
> Robert G. Strickland, PhD, ABPH - KE2WY
> [hidden email]
> Syracuse, New York, USA
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
>

--
Robert G. Strickland, PhD, ABPH - KE2WY
[hidden email]
Syracuse, New York, USA

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

RobertG

Re: help - firmware hangup

In reply to this post by RobertG

Thanks to all for replying.

Several things... the radio doesn't respond to the PWR switch; it keeps
blinking TX and MDU LD. The only way to cycle on/off is via the power
supply. I installed a Belkin usb-serial adapter which has worked fine
in the past. I disconnected the microHAM interface and ran a K2 serial
cable direct from the adapter to the radio [I have read here that the K2
cable will work, and I have used it with the K3 previously, before
getting the microHAM interface]. I restarted the computer, closed
programs, etc. I get the same problem: no comm between computer and
radio. It seems that the radio's ability to communicate with anything
has been somehow corrupted. There's no way that I can force any software
loading without a connection. Still stumped.

...robert

On 6/30/2012 14:43, Robert G. Strickland wrote:

> I have "lost contact" with my K3. I was trying to load the 4.51 firmware
> when I got an error report in the K3 utility program, and the K3 became
> unresponsive. Now, the TX light is blinking and MCU LD displays on the
> lcd. The computer terminal program keeps trying to establish contact
> with no results. In the K3 utility notice window, the program is
> continuously cycling through various baud rates with no luck. I tried to
> reset the radio using the PWR on - press SHIFT/LO 0 [KE7X p32] but
> nothing happens. I have shut everything down and powered back up but
> without results. The red TX light and MCU LD is all that I can get. Thanks.
>
> ...robert
>

RobertG

Re: help - firmware hangup

In reply to this post by RobertG

I have regained comm with the K3 and load 4.51 successfully.

Going through everything, again, I tried the PWR on/SHIFT LO on p 32 of
the KE7X manual. This time it worked. That enabled comm between computer
and radio, etc. So, I think this is working. Thanks again to everyone
for responding. Aside from specific suggestions - all appreciated - just
having the Elecraft community out there was reassuring which enabled me
to keep plugging along. That's as good as any specific suggestion.
Thanks much to all.

...robert

On 6/30/2012 14:43, Robert G. Strickland wrote:

Bob Cunnings NW8L

Re: help - firmware hangup

In reply to this post by RobertG

In K3 Utility Help, USB to Serial Adapter Troubleshooting topic:

"Before loading K3 firmware through a virtual port associated with a
microHAM microKEYER, microKEYER II, MK2R or MK2R+, change the microHAM
USB Device Router's Radio type to "none". (TU W4TV). If you are unable
to load firmware through a microHAM device, use a USB to Serial
Adapter or a "real" RS-232 cable. Neither microHAM nor Elecraft
recommend loading K3 firmware through the microHAM Router (the PC
software used with microHAM USB devices)."

Maybe this is the problem.

Bob NW8L

------------------------------------------------------------------------------
Dick...

Thanks for responding. Still no joy after going through all the HELP
suggestions. The problem seems to be an inability to connect from the
computer to the K3. Note, this whole arrangement has been working
perfectly up to this point. No cable changes, etc. What I get when
trying to establish a connection to the K3 is a steady hunt through
various baud rates with no success. I have cycled everything many times.
I am not using a serial-USB adapter. I am connecting via a microHAM CW
KEYER [which has been working without problems]. I think I'm getting
desperate! Thanks again.

...robert

On 6/30/2012 16:00, Dick Dievendorff wrote:
> See K3 Utility Help, Troubleshooting MCU Load failure. It has a step by step
> recovery procedure.
>
> 73 de Dick, K6KR
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Dick Dievendorff

Re: help - firmware hangup

In reply to this post by RobertG

Neither microHAM nor Elecraft recommend installing firmware through one of
their devices and the microHAM router (the software in your PC that
implements K3 port sharing for the microHAM CW keyer).

You'll need a USB to Serial adapter or "real" RS-232 cable.

>From the help page I pointed you to earlier:

"If you are using a software sharing program such as N8LP's LP-Bridge or
microHAM's Router between your personal computer and your K3's RS-232 port,
change the cabling so that the PC is connected directly to the K3 without an
intervening software "forwarder". These programs send K3 Programmer's
Reference commands, and a K3 in its bootstrap loader isn't able to process
those commands. Some commands may put the K3 bootstrap loader into an
unresponsive state."

It works fine if you don't start from where you are now.

Dick

-----Original Message-----
From: Robert G. Strickland [mailto:[hidden email]]
Sent: Saturday, June 30, 2012 7:46 AM
To: Dick Dievendorff
Cc: 'Elecraft'
Subject: Re: [Elecraft] help - firmware hangup

Dick...

Thanks for responding. Still no joy after going through all the HELP
suggestions. The problem seems to be an inability to connect from the
computer to the K3. Note, this whole arrangement has been working perfectly
up to this point. No cable changes, etc. What I get when trying to establish
a connection to the K3 is a steady hunt through various baud rates with no
success. I have cycled everything many times.
I am not using a serial-USB adapter. I am connecting via a microHAM CW KEYER
[which has been working without problems]. I think I'm getting desperate!
Thanks again.

...robert

On 6/30/2012 16:00, Dick Dievendorff wrote:

> See K3 Utility Help, Troubleshooting MCU Load failure. It has a step
> by step recovery procedure.
>
> 73 de Dick, K6KR
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Robert G.
> Strickland
> Sent: Saturday, June 30, 2012 6:43 AM
> To: Elecraft
> Subject: [Elecraft] help - firmware hangup
>
> I have "lost contact" with my K3. I was trying to load the 4.51
> firmware when I got an error report in the K3 utility program, and the
> K3 became unresponsive. Now, the TX light is blinking and MCU LD displays

on the lcd.
> The computer terminal program keeps trying to establish contact with
> no results. In the K3 utility notice window, the program is
> continuously cycling through various baud rates with no luck. I tried
> to reset the radio using the PWR on - press SHIFT/LO 0 [KE7X p32] but
> nothing happens. I have shut everything down and powered back up but
> without results. The red TX light and MCU LD is all that I can get.
Thanks.

>
> ...robert
> --
> Robert G. Strickland, PhD, ABPH - KE2WY [hidden email] Syracuse,
> New York, USA
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net Please help support this email
> list: http://www.qsl.net/donate.html
>
>

Bob Cunnings NW8L

Re: help - firmware hangup

In reply to this post by RobertG

I find nothing in the K3 manual or K3 Utility regarding "PWR on/SHIFT
LO". Is this a useful undocumented procedure or just voodoo? Perhaps
the KE7X manual provides a rationale for this action but I don't have
a copy of it, to date the Elecraft manual has been entirely
sufficient.

Bob NW8L

-------------------------------------------------------------------------------------------------------
I have regained comm with the K3 and load 4.51 successfully.

Going through everything, again, I tried the PWR on/SHIFT LO on p 32 of
the KE7X manual. This time it worked. That enabled comm between computer
and radio, etc. So, I think this is working. Thanks again to everyone
for responding. Aside from specific suggestions - all appreciated - just
having the Elecraft community out there was reassuring which enabled me
to keep plugging along. That's as good as any specific suggestion.
Thanks much to all.

...robert
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

RobertG

Re: help - firmware hangup

Bob...

On page 32, KE7X offers that key combination for "initializing
parameters to the default setting." I'm not sure if that applied to my
situation, but I was trying everything. I used that combination to get
the radio to communicate with the Elecraft utility. I had done some
other things, also, like removing a microHAM interface, installing a
usb-serial adapter and running a straight cable. Now, which of these -
including key push/hold - re-established computer-radio comm I can't say
for sure. But, problem is now solved.

Regarding the manual, it's useful. There's a lot of added detail and
discussion of various K3 topics which makes for interesting reading and,
perhaps, better utilization of the radio's capability. YMMV. Have a good
weekend.

...robert

On 6/30/2012 18:32, Bob Cunnings wrote:

> I find nothing in the K3 manual or K3 Utility regarding "PWR on/SHIFT
> LO". Is this a useful undocumented procedure or just voodoo? Perhaps
> the KE7X manual provides a rationale for this action but I don't have
> a copy of it, to date the Elecraft manual has been entirely
> sufficient.
>
> Bob NW8L
>
> -------------------------------------------------------------------------------------------------------
> I have regained comm with the K3 and load 4.51 successfully.
>
> Going through everything, again, I tried the PWR on/SHIFT LO on p 32 of
> the KE7X manual. This time it worked. That enabled comm between computer
> and radio, etc. So, I think this is working. Thanks again to everyone
> for responding. Aside from specific suggestions - all appreciated - just
> having the Elecraft community out there was reassuring which enabled me
> to keep plugging along. That's as good as any specific suggestion.
> Thanks much to all.
>
> ...robert
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>

Iain MacDonnell - N6ML-2

Re: help - firmware hangup

In reply to this post by Bob Cunnings NW8L

Bob,

See the section of the K3 Owner's Manual entitled Troubleshooting /
Parameter Initialization

73,

~iain / N6ML

On Sat, Jun 30, 2012 at 10:32 AM, Bob Cunnings <[hidden email]> wrote:

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Bob Cunnings NW8L

Re: help - firmware hangup

Duh! Parameter Initialization - I see it now (should have searched the
electronic version of the manual).

Thanks, I'm going to make a note of this. It's good to know that it
may help in recovering from a condition where the normal procedure to
force a download doesn't work.

Bob NW8L

On Sat, Jun 30, 2012 at 11:59 AM, iain macdonnell - N6ML <[hidden email]> wrote:

> Bob,
>
> See the section of the K3 Owner's Manual entitled Troubleshooting /
> Parameter Initialization
>
> 73,
>
> ~iain / N6ML
>
>
>
> On Sat, Jun 30, 2012 at 10:32 AM, Bob Cunnings <[hidden email]> wrote:
>> I find nothing in the K3 manual or K3 Utility regarding "PWR on/SHIFT
>> LO". Is this a useful undocumented procedure or just voodoo? Perhaps
>> the KE7X manual provides a rationale for this action but I don't have
>> a copy of it, to date the Elecraft manual has been entirely
>> sufficient.
>>
>> Bob NW8L
>>
>> -------------------------------------------------------------------------------------------------------
>> I have regained comm with the K3 and load 4.51 successfully.
>>
>> Going through everything, again, I tried the PWR on/SHIFT LO on p 32 of
>> the KE7X manual. This time it worked. That enabled comm between computer
>> and radio, etc. So, I think this is working. Thanks again to everyone
>> for responding. Aside from specific suggestions - all appreciated - just
>> having the Elecraft community out there was reassuring which enabled me
>> to keep plugging along. That's as good as any specific suggestion.
>> Thanks much to all.
>>
>> ...robert
>> ______________________________________________________________
>> Elecraft mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:[hidden email]
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html

Howard Stephenson

Parameter Initialization (EE INIT)

In reply to this post by Iain MacDonnell - N6ML-2

At K3 Support we very rarely ask someone to do the Parameter
Initialization (EE INIT)
If you did not have a good CONFIG file saved you could spend a good hour
turning options back on, redoing calibrations and filter set up.
If the K3 has a problem or a small glitch trying to reload the firmware
can make it lock up in the MCU LD.
If your not sure of what's wrong before you reload the firmware or do a
EE INIT please don't hesitate drop us an e-mail at <[hidden email]>
We are there to help you!

--
------
73's Howard Stephenson K6IA
Customer Support
------

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Don Wilhelm-4

Re: Parameter Initialization (EE INIT)

Let me add my recommendation *against* doing Parameter Initialization
(EE INIT) for the K3 or the KX3 - the same also applies to a "Master
Reset" for the K2. It is to be used only as a last resort - if you have
saved the configuration at a time when all was working just fine, it is
not a big deal to reload that configuration file.

It will be of no benefit to do a configuration save just before doing
the EE INIT because restoring that configuration is quite likely to
repeat the error.

In the case of the K2, there is a nice chart for recording your menu
settings in the K2 A to B mod instructions. You could record the K3
menu settings in a similar manner, but there is no convenient form for that.

Yes, when doing a K2 repair, I may do a Master Reset "just because" -- I
will be going through all the alignment and calibration procedures
anyway, and it is easy for me - I have had a lot of practice with over
700 repairs - it is not as easy for the unpracticed owner.

73,
Don W3FPR

On 6/30/2012 3:31 PM, Howard Stephenson wrote:

> At K3 Support we very rarely ask someone to do the Parameter
> Initialization (EE INIT)
> If you did not have a good CONFIG file saved you could spend a good hour
> turning options back on, redoing calibrations and filter set up.
> If the K3 has a problem or a small glitch trying to reload the firmware
> can make it lock up in the MCU LD.
> If your not sure of what's wrong before you reload the firmware or do a
> EE INIT please don't hesitate drop us an e-mail at <[hidden email]>
> We are there to help you!
>

Jeff Herr

Re: Parameter Initialization (EE INIT)

Configuration data, housed in non-volatile memory, is usually only cleared
and reloaded in either of two situations:

1. when a program revision alters the layout of the data.
2. when the stored data, due to defect, causes functional problems that
necessitate return to a known good baseline.

In general is this not the case with the elecraft products?

During init is ALL the variable storage written? Or just a portion?

WW6L

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Matt Zilmer

Re: Parameter Initialization (EE INIT)

EE INIT restores factory default settings. You should only use it if
the K3 is misbehaving due to corruption of its stored data structures.

Wayne never mentioned it, but I'd bet even money that the initial data
structure locations (from the original design) are the same today, and
that he's added some as needed, or when the expandability of the K3
changed. For example when the Ref Lock accessory was designed in, it
may have required some added memory and storage space. I've had to do
firmware designs like this a few times, to maintain backward
compatiblity with downrev hardware.

It's a really good idea to save the Config prior to EE INIT, and
probably periodically is a good recommendation. Then you can restore
your own settings after an EE INIT or if you (the user, general) dorks
some set up or parameter and can't figure it out easily enough.

AFAIK, only the K3 has an EE INIT function by that name. There are
various front or back doors in all recent Elecraft transceivers for
functions like this.

73,
matt W6NIA

On Sun, 01 Jul 2012 10:34:34 -0700, you wrote:

>Configuration data, housed in non-volatile memory, is usually only cleared
>and reloaded in either of two situations:
>
>1. when a program revision alters the layout of the data.
>2. when the stored data, due to defect, causes functional problems that
>necessitate return to a known good baseline.
>
>In general is this not the case with the elecraft products?
>
>During init is ALL the variable storage written? Or just a portion?
>
>
>WW6L
>
>
>______________________________________________________________
>Elecraft mailing list
>Home: http://mailman.qth.net/mailman/listinfo/elecraft
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:[hidden email]
>
>This list hosted by: http://www.qsl.net
>Please help support this email list: http://www.qsl.net/donate.html