Electronics > Repair
Tek TDS7404 tips about log welcome
charlyd:
picking up where i left last time i took the best position for the airflow over the chips by turning the unit upside down. and connect my W98 monitor pc with Hyperterm to the console port.
starting the fan and booting up the scope again to see if my option key was in because the last log also gave a bad instrument ID.
so i went throught the menus ans saw empty spaces as for the serial and for the key. so next step was to look in the vxboot for .sn and .key and it they were empty or not.
and from what i saw the were ok. |O
ok next step CLEARDB and see what happens. so i swap out a prepared topscript.hw file with the original one. and told the unit to fully reboot.
After that it stop at the bootsettings. and i think my Nvram batterij had been disconnected for a short while while the scope went upside down for the ACQ board to be build out and in and so on... so i turned the unit on the side with the fan all over the ACQ board after i reassemble the Cpu board to check the NVram.
time to boot up and put in so Tekconnect adapter to see where i was with the triggering of the channels. i did the simple test for each channel for the first impression. default setup -> autosetup and the trigger source on the channel under test. that look quit ok.
and before the 20 minutes warm up were past i ran the diagnose which end like it always did alle passed except for MISC 531 (calibration needed). i disconnected all inputs and ran SPC after the unit was warmed up and this time with succes.
i had seen in the SManual to rerun diagnose after SPC was passed so i did and all errors were gone now so that part was fixed.
also from what i saw was that
- If the trigger chips are failed only 12 & 16 calcon are modified in date after SPC run.
- If the trigger chips are working ok calcon files 9 & 12 & 16 are modified with still SPC fail.
- If the trigger chips are working ok and the right procedure has been followed all files in between and incl. 9-15 has been modified in date.
( as a side note: the Diagnose and SPC only give output in the console like (not tested option not installed ) for the rest no errors. if there is more visible this is pointing to a problem)
so now i end up with 2 errors still in my log:
- the EEprom error:
extd chksum failed, stored = 0xffffffff calc = 0xdb766060
0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory
- and an error i have since i disconnected the NVram and batterij that the
TmgrInit("/db")
0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
the last error can not be a big one it was never there before so..
but the eeprom checksum error.
does anybody know the adress where to peek for the content or maybe already did this and can give me more info.
charlyd:
....bump.....
any tips on resolving the error 0xdb766060
0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory.
what points to the nvram checksum fail.
[ editted 04-2022 ]: i flashed the eeprom and that solved the problem : extended bank17 chksum failed ].
charlyd:
i added a series of available options to the scope by generating the right option key.
now i have a lot of available option numbers. ST and SM is also enabled but the diagnositics error trigger 463 and misc 451 are back again.
From reading on the forum i had to rerun the calibration and after that the diagnostics again.
- my SPC is passes but my diagnostics still shows both errors, do i miss a procedure or adjustment in the scope?
another point for now i which available option number i link to which option i am afraid i have to build a option list?
charlyd:
the message about restoring serial and option key from disk can be easy fixed. i had to swap my protection switch to get the serial written ito the NVRAM ( FRAM)
still left over with last errors, which i see in many debug logs appear:
>> 0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory
has anybody performed the following action with succes on a non -B version like TDS7404 >> calConStatus = cc_init(1) and what can i expect ?
Erasing sector 3 of the M25P20 FLASH
Storing 358 bytes of service cal #1 data from 0x1ffe500 into NV[3:0]
NV service cal data verified.
i took this from an other post:
-------------------------------------- https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg2764508/#msg2764508 ----------------------------
Maybe I found out how to re-do SPC for a new ACQ board. There is a need to execute this command(calConStatus = cc_init(1)), which will completely erase the SPC calibration data of your previous ACQ board, and then rewrite the original factory CAL data when re-executing After SPC, all user CAL data in the directory c:\vxBoot\CalCons will be regenerated, but it is recommended that you back up all the files under c:\vxBoot\CalCons before running this command.
--- Code: ----> calConStatus = cc_init(2)
0x167bce0 (tShell): Reading 358 bytes of service cal #1 data from NV[3:0] into 0x164d7e0
0x167bce0 (tShell): nvMem_read succeeded
0x167bce0 (tShell): Optical hardware is not present.
calConStatus = 0x127d1dc: value = 0 = 0x0
-> calConStatus = cc_init(1)
0x167bce0 (tShell): Erasing sector 3 of the M25P20 FLASH
0x167bce0 (tShell): Storing 358 bytes of service cal #1 data from 0x1ffe500 into NV[3:0]
0x167bce0 (tShell): NV service cal data verified.
0x167bce0 (tShell): Optical hardware is not present.
calConStatus = 0x127d1dc: value = 131071 = 0x1ffff
--- End code ---
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
i am curious to the results or maybe somebody is willing to try on a non repairable scope.
charlyd:
i have just this question can anybody help me out with this problem:
--- Code: ----------------------------------Problem 2 ------------------------------------
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
ET cal failure (SLOW FAST)
--- End code ---
i ask this because when i was looking into my logs from last year with the NVRAM installed. i saw i had this output too in three logs. (and the 4th and last log that same it was gone. see bottom log here below.)
--- Code: --- runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
ET cal failure (SLOW FAST)
value = 0 = 0x0
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
DIAGNOSTIC EXECUTION begin
OptionST not tested. (option not enabled)
BK2 not tested (option not enabled)
DIAGNOSTIC EXECUTION finished
--- End code ---
and 4th and last run my SPC passed and my log was like this:
--- Code: --- enablePowerupDiags = 0
enablePowerupDiags = 0x12fad08: value = 0 = 0x0
EnableHorizInterpolation=1
new symbol "EnableHorizInterpolation" added to symbol table.
EnableHorizInterpolation = 0x36466e0: value = 1 = 0x1
runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
value = 0 = 0x0
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
--- End code ---
why am i getting this "minMain-maxMain" part?
lots of questions raise here:
- anybody had this and knows the right way to fix this.
- it was gone last year after SPC PASS. with a NVRAM installed, now i have a FRAM can that be the reason?
- does this mean i have to clearDB or re-init something else?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version