Products > Test Equipment
Agilent E7495 linux root account
<< < (47/91) > >>
ke6iyc:
@kr5j

You also need to "install" the options, done on the unit itself.

They do not automatically appear...

Brian
kr5j:
I started with A.06.25 FW then did the GPS patch. I rebooted and the GPS patch appears to have worked, now the GPS info has the current UTC time. Also the GPS icon turns green! Then I did the license patch and it appears to have worked but cannot access the screen to see installed options. Also cannot get to the GPS adjustment screen. The problem that is once the unit boots up, I select System then press More 2 of 2 to get to Page 2. Unit takes a few seconds then all the button labels on the left side of the screen disappear. Unit stays in this condition and does not respond to any button presses. I have to reboot to get the unit operational again. Why would either patch affect it this way?
DogP:
I had that same problem: https://www.eevblog.com/forum/testgear/agilent-e7495-linux-root-account/msg1053888/#msg1053888 .  You need to modify the /flash/egServer/license/elgato.lic file and add a SIGN value (like SIGN=000000000000 ) to any that don't already have a SIGN.

Pat
ve7xen:

--- Quote from: kirill_ka on April 27, 2017, 09:30:43 am ---
--- Quote from: ve7xen on March 18, 2017, 04:05:15 am ---So this is quite odd, since Linux itself has no trouble with the current date, but the egServer process seems to be rolling it over zero to 'less than the minimum'. I guess egServer must be internally representing the time in a nonstandard way. Maybe just patching the comparison would make it work again?

--- End quote ---

No. What we see here is "GPS week rollover" problem.
http://www.npl.co.uk/reference/faqs/when-and-what-is-the-gps-week-rollover-problem-(faq-time)
The message doesn't show the time which is "less than minimum". I verified that it's current time minus 1024 weeks.
So GPS subsystem adjusts system clock and then it's immediately reset to "minimum time".

--- End quote ---

Curious, because rollover last happened in 1999 and doesn't happen again until 2019. The instrument was released sometime around 2002-3. So I kind of thought of that but wrote it off as something else. It's definitely this though, probably the firmware is checking some arbitrary date in the past to decide what GPS epoch it is in, and how many weeks to add. We went past that boundary date, so it think it's pre-1999 again. If anyone's curious, the disassembly of the patched region is:

--- Code: ---old
---
0x2122880: 4b 25 85 e2   r2 = r5 + 314572800                                                                                                                                                                   
0x2122884: 15 28 82 e2   r2 = r2 + 1376256
0x2122888: f6 2d 82 e2   r2 = r2 + 15744

new
---
0x2122880: de 25 85 e2   r2 = r5 + 931135488                                                                                                                                                                   
0x2122884: 3f 28 82 e2   r2 = r2 + 4128768
0x2122888: f6 2d 82 e2   r2 = r2 + 15744

--- End code ---

Which adds exactly 1024 weeks to the constant.

Nice work on the patch and thanks! I couldn't crack it.
kr5j:
I copied the legato.lic file to mnt but it does not appear on the CF card. There were also 2 screen shots in the mnt folder and they are not on the CF card. I did a screenshot and when I opened the CF card on my PC the screenshot was there but nothing else. How do I put the legato.lic file on the CF card? I tried the mount /devf/hdc1/ /mnt command and it said it failed: not a directory.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod