Tektronix VM6000 help

[sprit]

It seems like this is just my own post 


btw, here is update:

It's 5 AM and I'm still messing around with this VM6000.

To confirm that the RAM in demux0 is faulty (U13_0_A), I removed it and swapped its position with U15_0_A, and the debug log reported exactly what I suspected.

Test "114" - Processor-->Memory-->DRAMCal started
See CalDramDump files: U11_0_A(DMX[0])/U12_0_A(DMX_DRAM[0])/U13_0_A(DMX_DRAM[1])/U14_0_A(DMX_DRAM[2])/U15_0_A(DMX_DRAM[3]) ERROR: 10_calDramStep29 GrpAll byte 9: eAll byte 9: exp/act 0x09/0xff (bits: 1 2 4 5 6 7)

*** TEST FAILED ***

The RAM test process ran for a longer period before stopping, and I was certain the RAM I mentioned earlier was faulty. I searched everywhere for a donor board to take the RAM from, but unfortunately, there wasn't one. I'm currently ordering some from Digikey, but I expect it will take quite a while.

My biggest concern right now is the ADG523; it's being misidentified. I tried extracting the ROM from the U170 to see what the U1200 was doing, but it was full of meaningless characters. The misidentification of the ADG523 is causing the SPC process to consume too much time and resources to download.
Test "233" - Registers-->Trigger-->TrigComp started

Invalid U25(ADG523) Trigger System ID reg value 0xdebfdbfa.

*** TEST FAILED ***

Test execution time 0.25188 sec
diagMgr:diagLogFailure: Fri Dec 12 03:53:30 2025 P Pu=1 T=37 "Invalid U25(ADG523) Trigger System ID reg value 0xdebfdbfa."

Test "234" - Registers-->Trigger-->CommTrig started
I'm wondering what's reading this ADG523 address; they gave me the door lock but withheld the key....

I'm wondering if the use of EEPROM files on iAleks' DPO7350 PowerBoard is the cause of this error. The machine still identifies as DPO7104 even though I changed the values ​​in the powerboard's EEPROMs earlier. That's strange. It would be great if someone who owns the original dpo7104 or vm6000 model could share those EEPROM files? Thanks for the help!

Here is the latest log.

[iAleks]

Resistors configurate acqusition board ID, for board like you (DPO7104 4ADC 4DEMUX 1TH)

I attach DUMP, check it, but remember first backup your EEPROM, second backup first backup then continue

[sprit]

Hi iAleks, thanks for your help.

I just backed up the old EEPROMs and tried to flash them using the file ialeks sent, but nothing else came up. The ADG523 continues to report an ID recognition error... I don't know what verified it. Btw, I think I'll pause the game here until the RAM I ordered arrives.

Thank you guys, may the force be with you and i'll see you next...week 

Feng

[sprit]

Hello guys, how's going?


My package arrived today and I'll be back in a few hours. I'm so eager to know the results. I hope everything goes smoothly...

[sprit]

Hi guys, have a great day!

I received my package that day, and while I was happy about the upcoming progress, I discovered that the package I'd been waiting for was the wrong one... The seller sent me the wrong RAM module, so I have to return the old chips and wait for them to send the correct one... The package will arrive in 3-4 days, and I'll update you later. Honestly, I'm really frustrated right now. My DSO80k's motherboard is broken and I can't find a replacement, this VM6000 has tons of errors, and there are several Agilent scope else, but I'm too fed up to touch them anymore. I guess they all hate me now


I think there's an 80% chance the ADG523 is faulty. I've never encountered a VM6000 with these kinds of errors

[sprit]

Good morning everyone.

I just received the DRAM, and after replacing it, the DRAM calibration passed. That's great news.

However, we have a new error, quite different from the previous ones we've encountered: a MIA board detection error. It's causing the scope application to fail to start and freeze.

iAleks, do you have any ideas?

Code: [Select]

***************************************

File opened:  Sat Dec 27 20:55:43 2025

***************************************

Start kernel driver initialization.

Scope.exe RELEASE build.

20:55:43:293[2020] CDriverApi::drvOpen(265) MODERATE:CreateFile fail, Error code=2
setAcqBrdConfig: with board ID is 31
setAcqBrdConfig: with board ID is 31
=======This is an OscarOnStingray RevE board with 4 demuxes=======
=======Version ID: Tekscope 1.2.1d, MIA 0x10011156, ACL 0xAC140707=======

flashAccessInit MiaNV; Flash ID = 0x00ffffff; size = 0x040000
flashAccessInit AcqNV; Flash ID = 0x00208012; size = 0x040000
Start hardware account initialization.
Event log has 0 entries
20:55:53:598[2020] nvPublic.cpp:nvFlashGet(574) MODERATE:nvFlashGet: there is no entry in the MiaNV flash
20:55:53:598[2020] hwAccount.cpp:hwAccount_init(1991) MODERATE:failed to read flash memory, will use factory default values.
20:55:53:598[2020] hwAccount.cpp:hwAccount_init(2017) MODERATE:hDigital acq board ID not supported
20:55:58:965[2020] nvPublic.cpp:nvFlashGetMinimal(629) MODERATE:nvFlashGet: there is no entry in the MiaNV flash
20:55:58:965[2020] flMgr.cpp:flMgrInit(228) MODERATE:failed to read floating licenses
20:56:09:020[2020] nvPublic.cpp:nvFlashGet(574) MODERATE:nvFlashGet: there is no entry in the MiaNV flash
20:56:09:020[2020] flMgr.cpp:readRuntimePersistent(257) MODERATE:read failed
Start hardware access initialization.
Atmel clock src has been programmed successfully
Signature of acq processor firmware is 7EA0
Acq processor code successfully verified
20:56:09:941[2020] hwConnect.cpp:hwAccessInit(1266) U7(LMX2326PLL) was detected successfully (re)locked 1 times after waiting 0.01ms.
CH2 signal not safe with 11.947122 volts RMS
CH3 signal is not safe with less then -20.000000 volts

***************************************

File opened:  Sat Dec 27 21:09:43 2025

***************************************

Start kernel driver initialization.

Scope.exe RELEASE build.

21:09:43:370[636] CDriverApi::drvOpen(265) MODERATE:CreateFile fail, Error code=2
setAcqBrdConfig: with board ID is 31
setAcqBrdConfig: with board ID is 31
=======This is an OscarOnStingray RevE board with 4 demuxes=======
=======Version ID: Tekscope 1.2.1d, MIA 0x10011156, ACL 0xAC140707=======

flashAccessInit MiaNV; Flash ID = 0x00ffffff; size = 0x040000
flashAccessInit AcqNV; Flash ID = 0x00208012; size = 0x040000
Start hardware account initialization.
Event log has 0 entries
21:09:55:697[636] nvPublic.cpp:nvFlashGet(574) MODERATE:nvFlashGet: there is no entry in the MiaNV flash
21:09:55:697[636] hwAccount.cpp:hwAccount_init(1991) MODERATE:failed to read flash memory, will use factory default values.
21:09:55:697[636] hwAccount.cpp:hwAccount_init(2017) MODERATE:hDigital acq board ID not supported
21:10:01:706[636] nvPublic.cpp:nvFlashGetMinimal(629) MODERATE:nvFlashGet: there is no entry in the MiaNV flash
21:10:01:706[636] flMgr.cpp:flMgrInit(228) MODERATE:failed to read floating licenses
21:10:12:552[636] nvPublic.cpp:nvFlashGet(574) MODERATE:nvFlashGet: there is no entry in the MiaNV flash
21:10:12:552[636] flMgr.cpp:readRuntimePersistent(257) MODERATE:read failed
Start hardware access initialization.
Atmel clock src has been programmed successfully
Signature of acq processor firmware is 7EA0
Acq processor code successfully verified
21:10:13:473[636] hwConnect.cpp:hwAccessInit(1266) U7(LMX2326PLL) was detected successfully (re)locked 1 times after waiting 0.01ms.
CH2 signal not safe with 11.948467 volts RMS
CH3 signal is not safe with less then -20.000000 volts
21:10:18:420[636] CDmxPublic::powerUpCal(123) Starting analog demux pll/dll and memory calibration
DRAM is Mt_ddr2_512M_667
21:10:18:680[636] CDmxPublic::powerUpCal(226) ADG387 demuxs have been calibrated at 166MHz sysClk

Dram Calibration results:
-------------------------
DramCal has PASSED on all Demuxs

21:10:18:730[636] CDmxPublic::powerUpCal(123) Starting analog demux pll/dll and memory calibration
DRAM is Mt_ddr2_512M_667
21:10:18:981[636] CDmxPublic::powerUpCal(226) ADG387 demuxs have been calibrated at 166MHz sysClk

Dram Calibration results:
-------------------------
DramCal has PASSED on all Demuxs

MFG Console disabled because COM1 is used.
Calling tcpipInit...
21:10:19:201[636] consoleTcpip.cpp:getNoneTekLinkNicIpAddress(336) MODERATE:Error: Ethernet adapter MS TCP Loopback interface
 has a bad MAC addr = FF-FF-FF-FF-FF-FF !!!
Is the TekLink MAC addr unprogrammed?
21:10:19:201[636] systemPublic.cpp:sysInitTcpDebugInterface(231) Debug console listening on port 1072
21:10:19:201[636] systemPublic.cpp:systemInitOnCreate(573) MODERATE:DEBUG OUTPUT IS ENABLED BY DIAG MODE = FACTORY
Connecting trace interface to Error Log.
21:10:19:201[636] genHorzConstraints.cpp:generateHorizConstraintTables(956) Generating horz constraint tables.

5.56 ... 11.11 ... 21:10:19:241[636] genHorzConstraints.cpp:generateHorizConstraintTables(959)
Done generating tables.
21:10:19:241[636] acqUpStatsTimer.cpp:acqDsyUpStatsCreateTimer(79) acqDsyUpStatsTimerHandler
Calling appInterface.init
21:10:19:391[636] mathNetMgr::Init(141) mathNetMgrHandler
21:10:19:462[636] gpibControlLayer.cpp:GpibInitialize(4482) MODERATE:GpibInitialize: Initializing 6 parsers
Factory date: Thu Feb 27 17:21:32 2020

CH2 signal not safe with 11.910786 volts RMS
CH3 signal is not safe with less then -20.000000 volts
SPC date: Thu Feb 27 17:27:55 2020

, checksum mismatch, expected 43546 found 2576921:10:20:092[636] tmgrclass.cpp:TmgrStartup(1903) tmgrTaskInit
21:10:58:608[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:11:31:145[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:12:03:671[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:12:36:439[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:13:12:390[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:13:51:286[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:14:26:477[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:14:59:354[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:15:32:041[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts
21:16:04:638[636] CFlashMemory::disableFlashWr(696) MODERATE:MiaNV failed to become write-disabled even after five attempts

***************************************

File opened:  Sat Dec 27 21:21:37 2025

***************************************

Start kernel driver initialization.

Scope.exe RELEASE build.

21:21:37:340[672] CDriverApi::drvOpen(265) MODERATE:CreateFile fail, Error code=2
setAcqBrdConfig: with board ID is 31
setAcqBrdConfig: with board ID is 31
=======This is an OscarOnStingray RevE board with 4 demuxes=======
=======Version ID: Tekscope 1.2.1d, MIA 0x10011156, ACL 0xAC140707=======

flashAccessInit MiaNV; Flash ID = 0x00ffffff; size = 0x040000
flashAccessInit AcqNV; Flash ID = 0x00208012; size = 0x040000
Start hardware account initialization.
Event log has 0 entries
21:21:50:999[672] nvPublic.cpp:nvFlashGet(574) MODERATE:nvFlashGet: there is no entry in the MiaNV flash
21:21:50:999[672] hwAccount.cpp:hwAccount_init(1991) MODERATE:failed to read flash memory, will use factory default values.
21:21:50:999[672] hwAccount.cpp:hwAccount_init(2017) MODERATE:hDigital acq board ID not supported
21:21:57:288[672] nvPublic.cpp:nvFlashGetMinimal(629) MODERATE:nvFlashGet: there is no entry in the MiaNV flash
21:21:57:288[672] flMgr.cpp:flMgrInit(228) MODERATE:failed to read floating licenses

Could some EEPROM files be corrupted? But I don't think so because I've never seen this error before. ADG523 still hasn't appeared in the logs, probably because that test procedure hasn't been performed yet.
This adventure is quite challenging . By the way, could the admin please rename this thread to "The Tektronix VM6000 Adventure"? Thank you very much everyone.

Sincerely,

Feng.

[sprit]

I think this is just a monologue!

Btw, In case the ADG523 fails, where can I find replacements? Is this a custom component from Tektronix, or just internal Tektronix code customized by National Semiconductor?I would be very happy if someone could share this IC with me. My guess was probably right , the ADG523 is broken. I restored all the EEPROM files on the powerboard, but the error persists. Haizzzzzz

The best things will come to you.

Feng