Keysight Technologies U3810A, Getting Started Manual

Page: 86 / 134

Keysight U3810 Series Getting Started Guide 86
3
Login to the BeagleBone via PuTTY using either the RNDIS or serial connection.
4
To update the Lab Code to the latest revision, use the command ./LabCodeReset.sh -u .
This will refresh the code and set the environmental variables to reflect the new revision code.
5
To ensure the code is authentic, check the signature. This will use the public.key, checksum.sig
and LabCode.tar.gz to verify authenticity.
6
For the update process, the script will ask for the sudo password. This is to update the system
parameters.
7
After the update is complete, a reboot is suggested. This will load in all the latest system
parameters into the running sessions.
debian@beaglebone:~$ ./LabCodeReset.sh -u
The LabCode.tar.gz has been signed.
Checking on the signature
gpg: key 7C92DD7F05C4BDAE: "Copyright Keysight Technologies 2020" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
gpg: assuming signed data in 'checksum'
gpg: Signature made Mon 27 Apr 2020 05:20:54 AM UTC
gpg: using RSA key 011F5B903A1BFE765E4EDC4F7C92DD7F05C4BDAE
gpg: Good signature from "Copyright Keysight Technologies 2020" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 011F 5B90 3A1B FE76 5E4E DC4F 7C92 DD7F 05C4 BDAE
Checking on SHA256 hash ...
LabCode.tar.gz: OK
Do you want to proceed to refresh the code? (y/n)
…
Updating Keysight Revisions
[sudo] password for debian:
Reboot is suggested