You can replace the CMOS RAM and battery with a NVRAM
(or FRAM) with a little work.
You have to remove the battery, cover it over with a label
describing the modification (because you are nice).
You also have to provide a voltage to the CPU's battery
detect circuit to fool it into thinking it has a good battery.
After doing that, you program the new NVRAM with the old
NVRAM's contents, and plug it in.
However, your calibration will be wrong for your scope, as
the NVRAM's files are unique to the scope that created it.
I wouldn't do the above, as the battery/cmos RAM combination
lasts a lot longer than an NVRAM, and cribbed calibration data
is worse than no calibration data at all.
When you plug a new NVRAM into your scope, and turn the power
on for the first time, the firmware installs a default set of
calibration constants into the constant area, and sets the
uncalibrated flag so that the screen has a row of dots along
the bottom, to announce to the world the scope is uncalibrated.
The only logical reason to program the NVRAM with someone else's
data is if you want to fool a buyer into thinking the scope is
calibrated.
-Chuck Harris
Max Vlasov via Groups.Io wrote:
toggle quoted message
Show quoted text
Hi,
Also have anyone transferred the 2445B NVRAM content into the 2445A SRAM?
There is a 2445B NVRAM file kindly uploaded by Mitchell Kobierowski in this forum. Technically it's possible to upload it into the 2445A SRAM (connect the voltage source via the current limiter while being in the ROM programmer tester and then bring it back to the A5 board). I hope it should fix the FAIL04 prompt and restore the calibration data integrity. Since my 2445a has option 05 (video triggering), I would have to recalibrate it later on together with CAL01, CAL02, CAL03.... but one at a time.
I wonder if doing CAL one at a time is possible at all..
Thank you,
All the Best,
Maxim
