time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

Re: [time-nuts] Motorola Oncore UT+ firmware upgrade & backup power questions

HM
Hal Murray
Sat, Jun 20, 2015 11:06 PM

I didnt see this well answered - the device loads firmware at each start
cycle.  If i am not mistaken you can even use ntp.

I just scanned the ntp source code for the Oncore driver.  I didn't see any
hints of loading firmware.  There is code to read the firmware version.

--
These are my opinions.  I hate spam.

gigneil@gmail.com said: > I didnt see this well answered - the device loads firmware at each start > cycle. If i am not mistaken you can even use ntp. I just scanned the ntp source code for the Oncore driver. I didn't see any hints of loading firmware. There is code to read the firmware version. -- These are my opinions. I hate spam.
PS
Pete Stephenson
Sun, Jun 21, 2015 6:24 AM

The Oncore driver can load certain parameters (e.g. the fixed
location, mode of operation, and -- I think -- the current estimated
time) into the Oncore receiver's RAM, but doesn't do anything to the
firmware on flash.

Cheers!
-Pete

On Sun, Jun 21, 2015 at 1:06 AM, Hal Murray hmurray@megapathdsl.net wrote:

I didnt see this well answered - the device loads firmware at each start
cycle.  If i am not mistaken you can even use ntp.

I just scanned the ntp source code for the Oncore driver.  I didn't see any
hints of loading firmware.  There is code to read the firmware version.

--
These are my opinions.  I hate spam.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

--
Pete Stephenson

The Oncore driver can load certain parameters (e.g. the fixed location, mode of operation, and -- I think -- the current estimated time) into the Oncore receiver's RAM, but doesn't do anything to the firmware on flash. Cheers! -Pete On Sun, Jun 21, 2015 at 1:06 AM, Hal Murray <hmurray@megapathdsl.net> wrote: > > gigneil@gmail.com said: >> I didnt see this well answered - the device loads firmware at each start >> cycle. If i am not mistaken you can even use ntp. > > I just scanned the ntp source code for the Oncore driver. I didn't see any > hints of loading firmware. There is code to read the firmware version. > > -- > These are my opinions. I hate spam. > > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. -- Pete Stephenson
BC
Bob Camp
Sun, Jun 21, 2015 11:41 AM

Hi

I think there is some confusion here between the almanacs / ephemeris and the
firmware. The Oncore saves the most recent GPS information (almanac and ephemeris)
in RAM. If that’s battery backed up, it re-loads it at boot. The firmware is in flash memory.
Re-programming the flash is (at best) a “return to vendor” process. Given how long the
parts have been out. There is no guarantee that any given part will have enough silicon to
handle this or that rev of the firmware.

Bob

On Jun 20, 2015, at 7:06 PM, Hal Murray hmurray@megapathdsl.net wrote:

gigneil@gmail.com said:

I didnt see this well answered - the device loads firmware at each start
cycle.  If i am not mistaken you can even use ntp.

I just scanned the ntp source code for the Oncore driver.  I didn't see any
hints of loading firmware.  There is code to read the firmware version.

--
These are my opinions.  I hate spam.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Hi I think there is some confusion here between the almanacs / ephemeris and the firmware. The Oncore saves the most recent GPS information (almanac and ephemeris) in RAM. If that’s battery backed up, it re-loads it at boot. The firmware is in flash memory. Re-programming the flash is (at best) a “return to vendor” process. Given how long the parts have been out. There is no guarantee that any given part will have enough silicon to handle this or that rev of the firmware. Bob > On Jun 20, 2015, at 7:06 PM, Hal Murray <hmurray@megapathdsl.net> wrote: > > > gigneil@gmail.com said: >> I didnt see this well answered - the device loads firmware at each start >> cycle. If i am not mistaken you can even use ntp. > > I just scanned the ntp source code for the Oncore driver. I didn't see any > hints of loading firmware. There is code to read the firmware version. > > -- > These are my opinions. I hate spam. > > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there.
PS
paul swed
Sun, Jun 21, 2015 9:02 PM

Bobs description is accurate. As an example we had a power hit last night.
My gps rcvr came up at some odd time. (normally its all fine in 10-30
seconds) I guessed the battery was bad its been 5 years. Sure enough
sometime later in hours the time is correct. Time to get a screw driver and
battery. :-)
Regards
Paul
WB8TSL

On Sun, Jun 21, 2015 at 7:41 AM, Bob Camp kb8tq@n1k.org wrote:

Hi

I think there is some confusion here between the almanacs / ephemeris and
the
firmware. The Oncore saves the most recent GPS information (almanac and
ephemeris)
in RAM. If that’s battery backed up, it re-loads it at boot. The firmware
is in flash memory.
Re-programming the flash is (at best) a “return to vendor” process. Given
how long the
parts have been out. There is no guarantee that any given part will have
enough silicon to
handle this or that rev of the firmware.

Bob

On Jun 20, 2015, at 7:06 PM, Hal Murray hmurray@megapathdsl.net wrote:

gigneil@gmail.com said:

I didnt see this well answered - the device loads firmware at each start
cycle.  If i am not mistaken you can even use ntp.

I just scanned the ntp source code for the Oncore driver.  I didn't see

any

hints of loading firmware.  There is code to read the firmware version.

--
These are my opinions.  I hate spam.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to

and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Bobs description is accurate. As an example we had a power hit last night. My gps rcvr came up at some odd time. (normally its all fine in 10-30 seconds) I guessed the battery was bad its been 5 years. Sure enough sometime later in hours the time is correct. Time to get a screw driver and battery. :-) Regards Paul WB8TSL On Sun, Jun 21, 2015 at 7:41 AM, Bob Camp <kb8tq@n1k.org> wrote: > Hi > > I think there is some confusion here between the almanacs / ephemeris and > the > firmware. The Oncore saves the most recent GPS information (almanac and > ephemeris) > in RAM. If that’s battery backed up, it re-loads it at boot. The firmware > is in flash memory. > Re-programming the flash is (at best) a “return to vendor” process. Given > how long the > parts have been out. There is no guarantee that any given part will have > enough silicon to > handle this or that rev of the firmware. > > Bob > > > On Jun 20, 2015, at 7:06 PM, Hal Murray <hmurray@megapathdsl.net> wrote: > > > > > > gigneil@gmail.com said: > >> I didnt see this well answered - the device loads firmware at each start > >> cycle. If i am not mistaken you can even use ntp. > > > > I just scanned the ntp source code for the Oncore driver. I didn't see > any > > hints of loading firmware. There is code to read the firmware version. > > > > -- > > These are my opinions. I hate spam. > > > > > > > > _______________________________________________ > > time-nuts mailing list -- time-nuts@febo.com > > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > and follow the instructions there. > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >