Empathy List Archives

time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

RE: [time-nuts] Difference between HP 5370A and 5370B

jim_johnson@agilent.com

Wed, Apr 27, 2005 3:04 PM

Hi Daun,

Not sure if you could do that or not. The
EPROMS are old technology compared to what we
have today so I'm not sure just how you'd "read
'em and clone 'em". I'll try to see if there's
a way ...

Jim

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On
Behalf Of Daun Yeagley
Sent: Tuesday, April 26, 2005 9:26 AM
To: Discussion of precise time and frequency measurement
Subject: RE: [time-nuts] Difference between HP 5370A and 5370B

Hi Jim

I'm wondering that if we were to find an example of a known
"good" unit as well
as a bad one, that we could look at the EPROMS to determine
any defenses and
then clone the good ones. That would be one way to save David
if he gets a
"bad" one.

Daun

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On
Behalf Of jim_johnson@agilent.com
Sent: Tuesday, April 26, 2005 12:18 PM
To: time-nuts@febo.com
Subject: RE: [time-nuts] Difference between HP 5370A and 5370B

Hi David,

Apparently the GPIB fix occurred in the
5370B models only and as far as he knows, there
could be some units out there with "bad" firmware
in them and some with the GPIB fix. The problem
still remains where they didn't change the firmware
revision number so there's no way to confirm it
one way or the other, besides having your GPIB hang
up on you. Sorry, but that's about the best that
can be done on this issue. I hope your 5370B is
a later model that has the fix in it!

Regards,
Jim

-----Original Message-----
From: time-nuts-bounces@febo.com

[mailto:time-nuts-bounces@febo.com]On

Behalf Of David Kirkby
Sent: Friday, April 15, 2005 1:52 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Difference between HP 5370A and 5370B

jim_johnson@agilent.com wrote:

Hi again David,

I talked to xxxxx this morning and here's what

he said:

Thanks.

The 5370B has a different processor board than the
"A" model, with on-board RAM (the "A" had a separate
RAM board). The "B" has had an upgrade to its DAC
board. The "B" has a different input module that is
more stable than in the "A". The firmware has had an
upgrade in the "B", as the HPIB (GPIB) would occasionally
hang up in the "A" model. The bad news is that the
newer firmware carries the same rev. number as the old one
so you can't easily tell which one you have installed.

I'm slightly lost there. You seem to be implying the B's have newer
firmware than the A's, but then saying its not easy to tell if
you have
the new firmware, since the revision is the same. If the newer
firmware
was installed only in B's, then all you would need to do is
look at the
model number. Clearly then I assume either some B's have the old
firmware, or some A's have the new firmware, or perhaps HP
would update
an A to a B firmware.

time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

Hi Daun, Not sure if you could do that or not. The EPROMS are old technology compared to what we have today so I'm not sure just how you'd "read 'em and clone 'em". I'll try to see if there's a way ... Jim >-----Original Message----- >From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On >Behalf Of Daun Yeagley >Sent: Tuesday, April 26, 2005 9:26 AM >To: Discussion of precise time and frequency measurement >Subject: RE: [time-nuts] Difference between HP 5370A and 5370B > > >Hi Jim > >I'm wondering that if we were to find an example of a known >"good" unit as well >as a bad one, that we could look at the EPROMS to determine >any defenses and >then clone the good ones. That would be one way to save David >if he gets a >"bad" one. > >Daun > > >-----Original Message----- >From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On >Behalf Of jim_johnson@agilent.com >Sent: Tuesday, April 26, 2005 12:18 PM >To: time-nuts@febo.com >Subject: RE: [time-nuts] Difference between HP 5370A and 5370B > > >Hi David, > > Apparently the GPIB fix occurred in the >5370B models only and as far as he knows, there >could be some units out there with "bad" firmware >in them and some with the GPIB fix. The problem >still remains where they didn't change the firmware >revision number so there's no way to confirm it >one way or the other, besides having your GPIB hang >up on you. Sorry, but that's about the best that >can be done on this issue. I hope your 5370B is >a later model that has the fix in it! > >Regards, >Jim > > >> >>>-----Original Message----- >>>From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On >>Behalf Of David Kirkby >>Sent: Friday, April 15, 2005 1:52 PM >>To: Discussion of precise time and frequency measurement >>Subject: Re: [time-nuts] Difference between HP 5370A and 5370B >> >> >>jim_johnson@agilent.com wrote: >>> Hi again David, >>> >>> I talked to xxxxx this morning and here's what >>> he said: >> >>Thanks. >> >>> The 5370B has a different processor board than the >>> "A" model, with on-board RAM (the "A" had a separate >>> RAM board). The "B" has had an upgrade to its DAC >>> board. The "B" has a different input module that is >>> more stable than in the "A". The firmware has had an >>> upgrade in the "B", as the HPIB (GPIB) would occasionally >>> hang up in the "A" model. The bad news is that the >>> newer firmware carries the same rev. number as the old one >>> so you can't easily tell which one you have installed. >> >>I'm slightly lost there. You seem to be implying the B's have newer >>firmware than the A's, but then saying its not easy to tell if >>you have >>the new firmware, since the revision is the same. If the newer >>firmware >>was installed only in B's, then all you would need to do is >>look at the >>model number. Clearly then I assume either some B's have the old >>firmware, or some A's have the new firmware, or perhaps HP >>would update >>an A to a B firmware. >> > >_______________________________________________ >time-nuts mailing list >time-nuts@febo.com >https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > _______________________________________________ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts _______________________________________________ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

Poul-Henning Kamp

Wed, Apr 27, 2005 6:13 PM

In message 65213341217E8D458E7C78E6640C74950405CBDE@waglmb01.labs.agilent.com
, jim_johnson@agilent.com writes:

Hi Daun,

Not sure if you could do that or not. The
EPROMS are old technology compared to what we
have today so I'm not sure just how you'd "read
'em and clone 'em". I'll try to see if there's
a way ...

Depending on the size, you can read them on most old PC's by plugging
them into the net-boot socket on a network card.

Programming them is slightly more involved.

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

In message <65213341217E8D458E7C78E6640C74950405CBDE@waglmb01.labs.agilent.com> , jim_johnson@agilent.com writes: >Hi Daun, > > Not sure if you could do that or not. The >EPROMS are old technology compared to what we >have today so I'm not sure just how you'd "read >'em and clone 'em". I'll try to see if there's >a way ... Depending on the size, you can read them on most old PC's by plugging them into the net-boot socket on a network card. Programming them is slightly more involved. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.