Author Topic: Keysight 3000T Factory Calibration Failed  (Read 509 times)

0 Members and 1 Guest are viewing this topic.

Offline ElectronManTopic starter

  • Regular Contributor
  • *
  • Posts: 111
  • Country: us
Keysight 3000T Factory Calibration Failed
« on: July 25, 2023, 01:42:10 am »
A while back during some firmware shenanigans with my 3034T (yeah, I know), the firmware nuked my front-panel chip (The little Renesas chip on that circuit board).

I was able to replace the chip with a new one, but didn't have time to put it back together for a while.

Recently I dusted it off, finished the repair, and the front panel is working again. Unfortunately, the calibration wasn't being loaded and I determined that there was a corrupt flash block that was causing \Secure to keep getting recreated.

I was finally able to erase that flash block via JTAG (it was already zeroed out, so no additional data loss) and now \Secure is back and working. However, I no longer have any valid calibration data files.

I found some backups I took a long time ago, but they do not appear to be valid (note the small size, they are mostly zeros):
06/14/24  08:22a                         708 FactoryCal0.dat
06/14/24  08:22a                         704 ServiceCal0.dat
06/14/24  08:22a                       27872 UserCal16.dat
06/14/24  08:22a                          76 SERNUM.DAT

The scope also still reports the factory calibration failed, and as a result, I cannot do a user calibration.

Before I dig in further, I wanted to see if anyone has run into this issue previously. I don't need a precise calibration, for anything I do, but would like to get these errors cleared and be able to user-cal again.
 

Offline ElectronManTopic starter

  • Regular Contributor
  • *
  • Posts: 111
  • Country: us
Re: Keysight 3000T Factory Calibration Failed
« Reply #1 on: July 25, 2023, 05:51:54 am »
UPDATE:

I managed to find the CAL files in a raw NAND dump and restore them to their proper places.

Now I just have to figure out the broken device web page, and the “Firmware is incomplete” message on boot up.

There appears to be other files missing from \Secure on the scope that aren’t getting replaced by the firmware updates.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf