Interesting FW Upload issue with K3 (happy ending)

[WB4SON]

Hi:

I am curious if this is an indication of a programmable part wear out, or
perhaps simply a timing issue between my K3 and computer.

I was installing the 5.38 firmware update today in anticipation of
installing the two new synthesizer hardware upgrades.  The K3 utility found
the latest software, connected without issue, and proceeded to do the MCU
update to 5.38.  However when it came time to the Front Panel Firmware, it
failed, complaining that a retry count had been exceeded.  The remainder of
the update went just fine, with both of my existing synthesizers being
successfully updated.

The good news is that a retry of the update (Send All Firmware to K3)
worked the second time around, but it still remarked on one retry being
required.

I have copied the log data that shows the problem, and again wonder if this
was just bad luck, or an indication that the programmable part on my FPF is
wearing out:

K3 responded with revision 05.38
16:23:43 MCU firmware load is complete
16:23:43 Elecraft K3 Utility Revision 1.13.5.9
16:23:43 OS Version 6.2 Build 9200
16:23:43 K3 MCU revision 05.38. RS-232 speed 38400 bit/s.
16:23:48 Sending firmware file C:\Users\Robert\Desktop\K3\hfpf0125.hex to
FPF
16:23:50 Retry 1 successful at address 0x00000450
16:23:51 Retry 1 successful at address 0x00000660
16:24:01 Retry 1 successful at address 0x00001B20
16:24:06 Retry 1 successful at address 0x00002460
16:24:09 Send FPF firmware failed at load address 0x000029E0
16:24:09 Ready
16:24:09 Total number of retries was 14
16:24:09 Highest number of retries for any block was 10
16:24:09 Error code 0xE2000044: Retry limit has been exhausted
16:24:09 FPF verification failed. Reload FPF.
16:24:09 Click "Close" to close this window

Here is the log for the second (successful) attempt:

16:36:36 Sending firmware file C:\Users\Robert\Desktop\K3\hfpf0125.hex to
FPF
16:37:06 Retry 1 successful at address 0x00003960
16:38:07 Waiting 6 seconds for reset to complete
16:38:13 Ready
16:38:13 Total number of retries was 1
16:38:13 Highest number of retries for any block was 1
16:38:13 Loaded FPF firmware revision 01.25
K3 responded with revision 01.25
16:38:13 FPF firmware load is complete


73, Bob, WB4SON
______________________________________________________________
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
Message delivered to [hidden email]

[Dick Dievendorff-4]

This could be an intermittent communication problem. I'd look first at the
serial port and USB to Serial adapter (if there is one).

When the part wears out, my experience is that it continues to fail at the
same address.

My K3 S/N 00018 has had more firmware installs than anyone's with the
exception of N6KR.  Mine is still on its first MCU and FPF.

73 de Dick, K6KR

-----Original Message-----
From: Elecraft [mailto:[hidden email]] On Behalf Of Bob
Sent: Wednesday, May 11, 2016 14:03
To: Elecraft <[hidden email]>
Subject: [Elecraft] Interesting FW Upload issue with K3 (happy ending)

Hi:

I am curious if this is an indication of a programmable part wear out, or
perhaps simply a timing issue between my K3 and computer.

I was installing the 5.38 firmware update today in anticipation of
installing the two new synthesizer hardware upgrades.  The K3 utility found
the latest software, connected without issue, and proceeded to do the MCU
update to 5.38.  However when it came time to the Front Panel Firmware, it
failed, complaining that a retry count had been exceeded.  The remainder of
the update went just fine, with both of my existing synthesizers being
successfully updated.

The good news is that a retry of the update (Send All Firmware to K3) worked
the second time around, but it still remarked on one retry being required.

I have copied the log data that shows the problem, and again wonder if this
was just bad luck, or an indication that the programmable part on my FPF is
wearing out:

K3 responded with revision 05.38
16:23:43 MCU firmware load is complete
16:23:43 Elecraft K3 Utility Revision 1.13.5.9
16:23:43 OS Version 6.2 Build 9200
16:23:43 K3 MCU revision 05.38. RS-232 speed 38400 bit/s.
16:23:48 Sending firmware file C:\Users\Robert\Desktop\K3\hfpf0125.hex to
FPF
16:23:50 Retry 1 successful at address 0x00000450
16:23:51 Retry 1 successful at address 0x00000660
16:24:01 Retry 1 successful at address 0x00001B20
16:24:06 Retry 1 successful at address 0x00002460
16:24:09 Send FPF firmware failed at load address 0x000029E0
16:24:09 Ready
16:24:09 Total number of retries was 14
16:24:09 Highest number of retries for any block was 10
16:24:09 Error code 0xE2000044: Retry limit has been exhausted
16:24:09 FPF verification failed. Reload FPF.
16:24:09 Click "Close" to close this window

Here is the log for the second (successful) attempt:

16:36:36 Sending firmware file C:\Users\Robert\Desktop\K3\hfpf0125.hex to
FPF
16:37:06 Retry 1 successful at address 0x00003960
16:38:07 Waiting 6 seconds for reset to complete
16:38:13 Ready
16:38:13 Total number of retries was 1
16:38:13 Highest number of retries for any block was 1
16:38:13 Loaded FPF firmware revision 01.25
K3 responded with revision 01.25
16:38:13 FPF firmware load is complete


73, Bob, WB4SON
______________________________________________________________
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 Message
delivered to [hidden email]

______________________________________________________________
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
Message delivered to [hidden email]

[WB4SON]

Hi Dick,

Yeah, I'm willing to buy the intermittent comm issue -- I do use the
Elecraft USB cable that came with my K3 #6171.  I found it interesting that
the other updates went just fine, while even the second attempt to update
the FPF had a single retry (all other updates had to be installed again).
Makes me wonder if the timing is a tad more critical for the FPF than the
others.  But as I said, it recovered nicely, so it was a happy ending.

If you haven't worn out your's with all the uploads you do, then I have no
doubt my K3 will outlive me.

Thanks for all you do to make ham radio fun!

73, Bob, WB4SON


On Wed, May 11, 2016 at 5:14 PM, Dick Dievendorff <[hidden email]> wrote:

> This could be an intermittent communication problem. I'd look first at the
> serial port and USB to Serial adapter (if there is one).
>
> When the part wears out, my experience is that it continues to fail at the
> same address.
>
> My K3 S/N 00018 has had more firmware installs than anyone's with the
> exception of N6KR.  Mine is still on its first MCU and FPF.
>
> 73 de Dick, K6KR
>
> -----Original Message-----
> From: Elecraft [mailto:[hidden email]] On Behalf Of Bob
> Sent: Wednesday, May 11, 2016 14:03
> To: Elecraft <[hidden email]>
> Subject: [Elecraft] Interesting FW Upload issue with K3 (happy ending)
>
> Hi:
>
> I am curious if this is an indication of a programmable part wear out, or
> perhaps simply a timing issue between my K3 and computer.
>
> I was installing the 5.38 firmware update today in anticipation of
> installing the two new synthesizer hardware upgrades.  The K3 utility found
> the latest software, connected without issue, and proceeded to do the MCU
> update to 5.38.  However when it came time to the Front Panel Firmware, it
> failed, complaining that a retry count had been exceeded.  The remainder of
> the update went just fine, with both of my existing synthesizers being
> successfully updated.
>
> The good news is that a retry of the update (Send All Firmware to K3)
> worked
> the second time around, but it still remarked on one retry being required.
>
> I have copied the log data that shows the problem, and again wonder if this
> was just bad luck, or an indication that the programmable part on my FPF is
> wearing out:
>
> K3 responded with revision 05.38
> 16:23:43 MCU firmware load is complete
> 16:23:43 Elecraft K3 Utility Revision 1.13.5.9
> 16:23:43 OS Version 6.2 Build 9200
> 16:23:43 K3 MCU revision 05.38. RS-232 speed 38400 bit/s.
> 16:23:48 Sending firmware file C:\Users\Robert\Desktop\K3\hfpf0125.hex to
> FPF
> 16:23:50 Retry 1 successful at address 0x00000450
> 16:23:51 Retry 1 successful at address 0x00000660
> 16:24:01 Retry 1 successful at address 0x00001B20
> 16:24:06 Retry 1 successful at address 0x00002460
> 16:24:09 Send FPF firmware failed at load address 0x000029E0
> 16:24:09 Ready
> 16:24:09 Total number of retries was 14
> 16:24:09 Highest number of retries for any block was 10
> 16:24:09 Error code 0xE2000044: Retry limit has been exhausted
> 16:24:09 FPF verification failed. Reload FPF.
> 16:24:09 Click "Close" to close this window
>
> Here is the log for the second (successful) attempt:
>
> 16:36:36 Sending firmware file C:\Users\Robert\Desktop\K3\hfpf0125.hex to
> FPF
> 16:37:06 Retry 1 successful at address 0x00003960
> 16:38:07 Waiting 6 seconds for reset to complete
> 16:38:13 Ready
> 16:38:13 Total number of retries was 1
> 16:38:13 Highest number of retries for any block was 1
> 16:38:13 Loaded FPF firmware revision 01.25
> K3 responded with revision 01.25
> 16:38:13 FPF firmware load is complete
>
>
> 73, Bob, WB4SON
> ______________________________________________________________
> 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
> Message
> delivered to [hidden email]
>
>

______________________________________________________________
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
Message delivered to [hidden email]

[paulb]

This sounds familiar

A while ago updated a k3 using my laptop and usb to serial. The RS232 won't fit
properly to the K3 so used a linking CAT-5E cable a couple of meters long.
The update failed several times, not sure of exact cause, possible x-talk across the
tx/rx pairs or unused wires. Replaced link cable with a very short CAT5E
all %100

cheers

Paul b
ZL1AJY

[w4sc-2]

I had the same issue with the P3.

Built a P3 kit, and during the upgrading of the f/w, a failure occurred
during FPGA code load.  The 'boot loader' didn't work after that, and I
could not initiate a forced recovery.  Had to send P3 back to factory, under
warranty.  The factory reported the failure was caused an improperly
programmed part.  However, it worked for some of the upgrade.

Ben W4SC

-----Original Message-----
From: Bob
Sent: Wednesday, May 11, 2016 5:03 PM
To: Elecraft
Subject: [Elecraft] Interesting FW Upload issue with K3 (happy ending)

Hi:

I am curious if this is an indication of a programmable part wear out, or
perhaps simply a timing issue between my K3 and computer.

I was installing the 5.38 firmware update today in anticipation of
installing the two new synthesizer hardware upgrades.  The K3 utility found
the latest software, connected without issue, and proceeded to do the MCU
update to 5.38.  However when it came time to the Front Panel Firmware, it
failed, complaining that a retry count had been exceeded.  The remainder of
the update went just fine, with both of my existing synthesizers being
successfully updated.

The good news is that a retry of the update (Send All Firmware to K3)
worked the second time around, but it still remarked on one retry being
required.

I have copied the log data that shows the problem, and again wonder if this
was just bad luck, or an indication that the programmable part on my FPF is
wearing out:

K3 responded with revision 05.38
16:23:43 MCU firmware load is complete
16:23:43 Elecraft K3 Utility Revision 1.13.5.9
16:23:43 OS Version 6.2 Build 9200
16:23:43 K3 MCU revision 05.38. RS-232 speed 38400 bit/s.
16:23:48 Sending firmware file C:\Users\Robert\Desktop\K3\hfpf0125.hex to
FPF
16:23:50 Retry 1 successful at address 0x00000450
16:23:51 Retry 1 successful at address 0x00000660
16:24:01 Retry 1 successful at address 0x00001B20
16:24:06 Retry 1 successful at address 0x00002460
16:24:09 Send FPF firmware failed at load address 0x000029E0
16:24:09 Ready
16:24:09 Total number of retries was 14
16:24:09 Highest number of retries for any block was 10
16:24:09 Error code 0xE2000044: Retry limit has been exhausted
16:24:09 FPF verification failed. Reload FPF.
16:24:09 Click "Close" to close this window

Here is the log for the second (successful) attempt:

16:36:36 Sending firmware file C:\Users\Robert\Desktop\K3\hfpf0125.hex to
FPF
16:37:06 Retry 1 successful at address 0x00003960
16:38:07 Waiting 6 seconds for reset to complete
16:38:13 Ready
16:38:13 Total number of retries was 1
16:38:13 Highest number of retries for any block was 1
16:38:13 Loaded FPF firmware revision 01.25
K3 responded with revision 01.25
16:38:13 FPF firmware load is complete


73, Bob, WB4SON
______________________________________________________________
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
Message delivered to [hidden email]

______________________________________________________________
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
Message delivered to [hidden email]