Could this account for the "Intel Hex file ran out of bytes before Intel
End file record was read" -and- "Intel Hex Read error: Expected start
characher ":" not found" messages when attempting (unsuccessfully)
to load the new upgrade into my K3?
73! Ken Kopp - K0PP
[EMAIL PROTECTED]
----- Original Message -----
From: Don Rasmussen
To: [email protected]
Sent: Tuesday, 04 December, 2007 05:40
Subject: [Elecraft] K3 problem with logging program after download
upgrade
Hi, Buck.
The K3 Utility attempts to communicate with the MCU initially to
establish its baud rate. This is done by sending a small command
at each of the supported speeds. <snip>
Soapbox ON.
IMO - This is a tragic WASTE of BITS.
And this happens every time there is an update?
Calculate the number of updates over the life of the
radio, now how big is the bit bucket - remembering
ASCII is 7 bits per character plus parity plus start
bits and stop bit.
Could be some major overflow problems when folks least
expect it...
_______________________________________________
Elecraft mailing list
Post to: [email protected]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
