Author Topic: Boot problem on Tektronix TDS7404 scope? (Solved) (Read 5825 times)

WORP3 · « **on:** December 16, 2020, 05:20:01 pm »

First of all, hi to you all, just registered myself after reading so many lovely posts on this EEVblog

I recently purchased an new old Tektronix TDS7404 which was working just great, no problems on start-up what so ever...... Until I noticed that my licence wasn't installed on my scope, even so even my s/n wasn't displaying correctly so entering the option key wasn't going to work.
After reading some repair post on this site, it was clear for me that it's possible to enter your s/n into the .sn file in the vxBoot, also to enter the option key into the .key file. Unfortunately this didn't work as it seems that this sn and key is already in the NVRAM and it won't except an new one without clearing this NVRAM first.

So I removed the #which was before the NvramClearDb = 1 command inside the topscript and rebooted the scope. Afterwards waiting for a while it seems that the scope hangs at the tektronix logo

After connecting a terminal to the debug port it seem's that the vxWorks is booting but when executing the topscript.hw script it can't find the TekScope.o file

Even more strangely, when I enter that same command right after it stopped running the script it's just accepting the command without any errors. Even more strange, if I copy and paste any command inside the topscript.hw to the terminal debug port, the scope even starts up.

Quote

]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997

CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.0 .
WDB: Ready.

usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:\vxBoot\TopScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################

cd "dbfs:c:/vxBoot"
value = 0 = 0x0

ld < TekScope.o
'an't open input 'TekScope.o
errno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)

Done executing startup script c:\vxBoot\TopScript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->

Does any of you have any idea why my powerpc board is not seeing that TekScope.o file during the ld < TekScope.o command?
Second question, is there a way to manually run that topscript.hw again?

Thanks in advance.

WORP3 · « **Reply #1 on:** December 16, 2020, 05:47:46 pm »

Already found one answer, namely how to start a script from the command prompt, you have to use the < sciptname command, so to re-run the topscript.hw just enter:

< TopScript.hw

But unfortunately still getting the same problem, so it's not a timing problem.

Code: [Select]

-> < TopScript.hw
    ################### topScript starts ###############################

    cd "dbfs:c:/vxBoot"
value = 0 = 0x0
    pwd
dbfs:c:/vxBoot
value = 15 = 0xf

    ld < TekScope.o
'an't open input 'TekScope.o
  errno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)
->

WORP3 · « **Reply #2 on:** December 16, 2020, 05:58:37 pm »

This (here below) is really defying all programming logic

----Default script loading on startup:

Code: [Select]

    ################### topScript starts ###############################

    cd "dbfs:c:/vxBoot"
value = 0 = 0x0
    pwd
dbfs:c:/vxBoot
value = 15 = 0xf

    ld < TekScope.o

'an't open input 'TekScope.o
  errno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)

Done executing startup script c:\vxBoot\TopScript.hw
KERNEL:  RUNNING TIME SLICED AT 10 TICKS PER SLICE!

----Manual entering the faulty command:

Code: [Select]

-> ld < TekScope.o
value = 33547168 = 0x1ffe3a0

----Rerunning the topscript.hw script again:

Code: [Select]

-> < TopScript.hw
    ################### topScript starts ###############################

    cd "dbfs:c:/vxBoot"
value = 0 = 0x0
    pwd
dbfs:c:/vxBoot
value = 15 = 0xf

    ld < TekScope.o
'an't open input 'TekScope.o
  errno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)
->

What the

WORP3 · « **Reply #3 on:** December 17, 2020, 04:27:34 pm »

Yesss

I found the problem, it was actually a very stupid one but because it's not visible you don't think about it right away. The problem was that inside my topscript file each line was ending with a CR and LF, something that windows does standard but in Unix there should only be a LF. The CR was added to the filename causing in a not found error

Code: [Select]

    ################### topScript starts ###############################

    cd "dbfs:c:/vxBoot"
value = 0 = 0x0
    pwd
dbfs:c:/vxBoot
value = 15 = 0xf


    ld < TekScope.o
value = 21167072 = 0x142fbe0
    ld < TekScopeSM.o
value = 21166624 = 0x142fa20

So, never use the internal windows notepad to change your TopScript.hw file

Then again, for some reason my S/N isn't updated, even after clearing out the NVRAM and rebooting it again

During boot I keep getting the message that no backup key has been found, shouldn't this message disappear after one reboot?

Code: [Select]

0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...
0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...

WORP3 · « **Reply #4 on:** December 17, 2020, 05:21:59 pm »

Now for some reason I can't the scope to accept my sn

I also keep getting a kernel version mismatch during boot, someone any bright idea?

Code: [Select]

0x16936c0 (tShell): >> Kernel version 1.0.8.0  does not match Boot ROM version 1.0.4.0

Here is my last complete boot, if someone has a bright idea why my s/n isn't updating, please let me know. I'm out if idea's at the moment

Code: [Select]

UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

romPost: MPC106  Walking-one passed.

romPost: MPC106 configuration passed.

romPost: First PCI access  passed.

romPost: PC87560 Walking-one passed.

romPost: PC87560 configuration passed.

romPost: DEC21554 configuration passed.


romPost: PERFORMING ROM CHECKSUM TEST...

romPost: ROM checksum passed.


romPost: PERFORMING DRAM CELL TEST...

romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.

romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.

romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...

romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...

romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...

romPost: PERFORMING DRAM WALKING-ONE  TEST...

romPost: DRAM Walking-one test passed.

romPost: PERFORMING NV-MEMORY WALKING-ONE  TEST...

romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.


romPost: POWER-UP DIAGNOSTIC COMPLETE.

Hel










                            VxWorks System Boot


Copyright 1984-1996  Wind River Systems, Inc.





CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.4.0
Creation date: Nov  2 2000, 11:03:34




Press any key to stop auto-boot...
 0
auto-booting...


boot device          : sm
processor number     : 0
host name            : host
file name            : c:\vxBoot\vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h)        : 192.168.0.2
gateway inet (g)     : 192.168.0.1
flags (f)            : 0x1008
target name (tn)     : tds7000
startup script (s)   : c:\vxBoot\TopScript.hw
other (o)            : nvfs=0x1000

Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network intePC1 dio device driver installed
rface lo0... done.
Attaching DIO client... done.
Loading c:\vxBoot\vxWorks.st...1773516
Starting at 0x200000...

User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6008 symbols for standalone.


 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]]
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]]
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks version 5.3.1
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.5
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-1997

                               CPU: Tektronix HPP - PowerPC 740.  Processor #0.
                              Memory Size: 0x2000000.  BSP version 1.0.8.0 .
                             WDB: Ready.

usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:\vxBoot\TopScript.hw ...
dbFsIoctl: invalid code 3
    ################### topScript starts ###############################

    cd "dbfs:c:/vxBoot"
value = 0 = 0x0
    pwd
dbfs:c:/vxBoot
value = 15 = 0xf


    ld < TekScope.o
value = 21167072 = 0x142fbe0
    ld < TekScopeSM.o
value = 21166624 = 0x142fa20

    pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x168d040: value = 23646304 = 0x168d060 = pDbDev + 0x20
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x168ba20: value = 23646048 = 0x168cf60
    copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0

    overrideFPdefaults()
value = 0 = 0x0

    measurePPCtimebase
value = 0 = 0x0


    registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0

    semInitForQueueCheckLogMsg
value = 23652448 = 0x168e860

    initSysWaiter()
value = 0 = 0x0




    raxInit
value = 0 = 0x0
    paiInit
done
value = 16916276 = 0x1021f34 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0






     tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
value = 0 = 0x0
     updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16936c0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - n
o programming needed.
value = 1 = 0x1
     cd "pc:"
value = 0 = 0x0

    raxInitializeDevices
done
0x16936c0 (tShell): (Re)starting Acq Processor
value = 23633928 = 0x168a008

    excHookAdd(stopStressForException)
value = 16703148 = 0xfedeac = stopStressForException


    dsyInit
value = 23625768 = 0x1688028
    dsyWPApplyNextRegs
value = 16906152 = 0x101f7a8 = DsyRegisterTable + 0xab0









    # remove '#' from next line to set powerup scope state to factory default:
    # NvramClearDb = 1

    nvram_initFileSys
0x16936c0 (tShell): >> Kernel version 1.0.8.0  does not match Boot ROM version 1
.0.4.0
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba540c3

    TmgrInit("/db")
0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...
0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...
value = 0 = 0x0
    PhxProxyInit
value = 21175904 = 0x1431e60
    rtlInit
value = 0 = 0x0


    sysExtMemAddToPool memSysPartId,0x02000000,0x0e000000
value = 0 = 0x0

    hwAccount_init
sysEnetAddrGet: 45:00:cc:ba:44:00
value = 0 = 0x0

    GpibInit
value = 267500128 = 0xff1ba60

    wfmMemInit(1)
value = 57781984 = 0x371aee0

    vertInstall
value = 57774948 = 0x3719364

    calConStatus = cc_init(2)
0x16936c0 (tShell): Reading 300 bytes of service cal data from EEPROM[0] into 0x
3719220
0x16936c0 (tShell): nvMem_read succeeded
0x16936c0 (tShell): Reading 82 bytes of service cal data from EEPROM[300] into 0
x3719300
0x16936c0 (tShell): nvMem_read succeeded
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x16936c0 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/1
0x16936c0 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/2
0x16936c0 (tShell): cc_init: bank 2 chksum failed, NOT reset to factory
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/3
0x16936c0 (tShell): cc_init: bank 3 chksum failed, NOT reset to factory
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/5
0x16936c0 (tShell): cc_init: bank 5 chksum failed, NOT reset to factory
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/6
0x16936c0 (tShell): cc_init: bank 6 chksum failed, NOT reset to factory
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/7
0x16936c0 (tShell): cc_init: bank 7 chksum failed, NOT reset to factory
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/8
0x16936c0 (tShell): cc_init: bank 8 chksum failed, NOT reset to factory
0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/15
0x16936c0 (tShell): cc_init: bank 15 chksum failed, NOT reset to factory
0x16936c0 (tShell): Optical hardware is not present.
calConStatus = 0x1324d08: value = 33263 = 0x81ef

    vertPostCalRestoreInstall
value = 0 = 0x0

    MathMeasCreateTheMathandMeasurementLibraries
value = 57602368 = 0x36ef140
    initAcqMapper
0x16936c0 (tShell): initAcqMapper: Enter
value = 0 = 0x0
    trigMapInit
value = 0 = 0x0
    dsyMapInit
value = 0 = 0x0
    mathMapperInit
value = 0 = 0x0
    utilMapInit
value = 57599712 = 0x36ee6e0

    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 20007032 = 0x1314878 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 23671784 = 0x16933e8
    dsyMapHookup
value = 23671888 = 0x1693450
    utilMapHookup
value = 23671920 = 0x1693470

    rtlHookup
value = 0 = 0x0
    horizMapHookup
value = 23671880 = 0x1693448
    fastFrameMapHookup
value = 23671904 = 0x1693460
    trigMapHookup
value = 23671912 = 0x1693468
    vertMapHookup
value = 23671904 = 0x1693460
    spcMapHookup
value = 23671904 = 0x1693460
    autosetMapHookup
value = 23671944 = 0x1693488
    timeSyncMapHookup
value = 23671936 = 0x1693480
    auxTrigMapHookup
value = 23671920 = 0x1693470
    dpoMapHookup
value = 23671912 = 0x1693468


    TmgrStartup
value = 56649296 = 0x3606650
    PhxProxyStartup
value = 56598752 = 0x35fa0e0
    taskDelay(2)
0x3681ec0 (tmgr): >> optNewOptKey: Bad instru Id
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 56072928 = 0x3579ae0

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 55861056 = 0x3545f40

    enablePowerupDiags = 0
enablePowerupDiags = 0x12ea4e8: value = 0 = 0x0
    EnableHorizInterpolation=1
new symbol "EnableHorizInterpolation" added to symbol table.
EnableHorizInterpolation = 0x14593c0: 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!
->

m k · « **Reply #5 on:** December 19, 2020, 12:16:17 pm »

(I know nothing about your specific device)

Since you did that nvram_initFileSys with NvramClearDb of wrong value it may have done something differently.
Though the parameter seems to be boolean with default value 0, usually the definition goes something like false = 0; true = not false, so no problems there.
On the other hand, if it's something not boolean the result can be different, like "1\cr" but that's a far cry.

Later it says that 300 bytes of service cal data from EEPROM and then nvMem_read succeeded.
Then some file chksum errors, no idea how those should be but my understanding goes so that you have not cleared the whole EEPROM.
Should it give a chksum error of EEPROM if that NvramClear have failed, guite likely.

Is the internal Windows before w2k?

Can't remember when excactly notepad changed its coding between txt and other types but that is one possibility.
Means that when you saved that file, if its save type was different, all those special characters changed corresponding the codepage in use.
That's also a far cry since script hardly uses any of those characters.
Use of tab character is also one possible difference but that goes one way only, from tab to spaces and surely the interpreter can handle them both.

WORP3 · « **Reply #6 on:** December 19, 2020, 04:49:13 pm »

De windows installed on that scope is Windows 2000 and yes the notepad did write an CR and LF at the end of each line, seen it in a hex editor. But that's fixed now, all CR are gone and scope is booting. Just have to find a way to get the S/N back in there.
Probably I will remove the battery clip attached on the NVRAM and solder some leads to it so I can install a seperat battery cell holder which I can access more easily. Just waiting for some parts at the moment.

m k · « **Reply #7 on:** December 19, 2020, 06:54:45 pm »

If the altered file has nothing above 0x7F I think you can be sure that everything is ok.

Version difference can obviously mean something but does that mean that you have to downgrade I also obviously have no idea but I'm sure someone around here has already been there.

WORP3 · « **Reply #8 on:** December 25, 2020, 10:35:30 am »

After more fidling with the scope and it's VxWorks I did a retry on the clear NVRAM inside the topscript.hw, unfortunately it didn't trigger a SN reset so it will use the .sn file which is on the HDD. I've tried several reboots with the protections switch in both positions.

Code: [Select]

    # remove '#' from next line to set powerup scope state to factory default:
     NvramClearDb = 1
NvramClearDb = 0x131484c: value = 1 = 0x1

    nvram_initFileSys

For some reason the clear NVRAM is only triggering the option key from resetting, not the actual serial number

Any of you got some idea's on how to trigger a sn reset?

Code: [Select]

    TmgrInit("/db")
0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...
0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...

WORP3 · « **Reply #9 on:** December 25, 2020, 10:50:25 am »

Looking at the bootup log, I also noticed that it keep telling me that the boot rom wasn't matching the kernel version.

Code: [Select]

    nvram_initFileSys
0x16936c0 (tShell): >> Kernel version 1.0.8.0  does not match Boot ROM version 1.0.4.0
value = -1 = 0xffffffff = pDbDev + 0xfe972fbf

Looking more specific to the boot.bin that was on my harddrive, I noticed using a hex monitor that this boot.bin was actually version 1.0.8.0 while during boot it was telling me that it was booting 1.0.4.0.

Code: [Select]

CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.4.0
Creation date: Nov  2 2000, 11:03:34

After some more research I stumbled on a script that was actually ment to update the boot rom flash, zie script below:

Code: [Select]

    #################### topScript starts ###############################
    #
    #  This script is for standalone prototypes that want to update
    #   their bootROMs to the newest version in the 
    #   scope's c:/vxBoot directory.
    
    sysFlashUpdate ("dbfs:c:/vxBoot/boot.bin")
    setLED 0x40
    #
    # hopefully you get this message at the end:
    # sysFlashUpdate: SUCCESS: flash written
    # sysFlashUpdate: TESTING: comparing region
    # value = 0 = 0x0

I removed the topscript.hw out of the boot options so I will not start all of the scope applications. A bit reluctance to do this I waited for a new reboot and started the theflash update script using the following command:

< topScript.vxw

Even more nerve wracking I watched the script doing it's job, hoping nothing is going wrong during this update:

Code: [Select]

-> < topScript.vxw
    #################### topScript starts ###############################
    #
    #  This script is for standalone prototypes that want to update
    #   their bootROMs to the newest version in the
    #   scope's c:/vxBoot directory.

    sysFlashUpdate ("dbfs:c:/vxBoot/boot.bin")
sysFlashUpdate: TESTING: comparing region
sysFlashUpdate: Erasing flash...done
sysFlashUpdate: Writing flash sectors
s0@0xff800000................
s1@0xff810000................
s2@0xff820000................
s3@0xff830000................
s4@0xff840000................
s5@0xff850000................
s6@0xff860000................
s7@0xff870000................
sysFlashUpdate: SUCCESS: flash written
sysFlashUpdate: TESTING: comparing region
value = 0 = 0x0
    setLED 0x40
value = -65 = 0xffffffbf = ppp_parms + 0xffc4f02f
    #
    # hopefully you get this message at the end:
    # sysFlashUpdate: SUCCESS: flash written
    # sysFlashUpdate: TESTING: comparing region
    # value = 0 = 0x0
->

Luckily the update went just fine and during a next reboot the scope was telling me it is loading BSP version: 1.0.8.0, also the matching warning was gone

For those interested, the actually boot prom on the bord is an: AM29LV040B-90JC

WORP3 · « **Reply #10 on:** December 25, 2020, 11:17:45 am »

In the meantime, as someone was pointing this out to me, I did something to prevent my trigger chips from over heating, just to prevent my chips looking like this:

Boot problem on Tektronix TDS7404 scope? (Solved)

I opened my scope and did a quick peek on my own trigger chips and luckily they where looking just fine:

I adjusted a heatsink that I had lying around:

And glued them on my chips, after some cleaning of the chips off-coarse:

Hopefully they will stay cool now and last a lifetime

WORP3 · « **Reply #11 on:** December 25, 2020, 11:20:24 am »

Can anyone tell me why the inline tumbnail or full image attachment options isn't working?

Tantratron · « **Reply #12 on:** January 15, 2021, 06:40:48 am »

Quote from: WORP3 on December 25, 2020, 11:17:45 am

In the meantime, as someone was pointing this out to me, I did something to prevent my trigger chips from over heating,
And glued them on my chips, after some cleaning of the chips off-coarse:
Hopefully they will stay cool now and last a lifetime

Hello, could you provide a reference of what specific glue product you have use to attach the heatsinks ?

On a side note, I do have spare old tektronix partially failed acquisition board with heatsinks, what safe method can be used to detach or de-glued these heatsink form the IC's ?

Thanks, Albert

WORP3 · « **Reply #13 on:** January 15, 2021, 01:17:07 pm »

Quote from: Tantratron on January 15, 2021, 06:40:48 am

Quote from: WORP3 on December 25, 2020, 11:17:45 am
In the meantime, as someone was pointing this out to me, I did something to prevent my trigger chips from over heating,
And glued them on my chips, after some cleaning of the chips off-coarse:
Hopefully they will stay cool now and last a lifetime
Hello, could you provide a reference of what specific glue product you have use to attach the heatsinks ?

On a side note, I do have spare old tektronix partially failed acquisition board with heatsinks, what safe method can be used to detach or de-glued these heatsink form the IC's ?

Thanks, Albert

Yhea,sure. I always use the 3M 2216 B/A glue for this kind of work.

https://nl.farnell.com/3m/2216-b-a-gray/epoxy-2-part-high-peel-sheer/dp/1702757

WORP3 · « **Reply #14 on:** January 15, 2021, 05:23:51 pm »

Quote

On a side note, I do have spare old tektronix partially failed acquisition board with heatsinks, what safe method can be used to detach or de-glued these heatsink form the IC's ?

It all depends on the type of glue that is used. In most cases heating it up will loosen the glue so you can take it off.

Quote

Organic adhesives such as cyanoacrylate, epoxy, acrylic, anaerobic, and UV curable acrylates will break down around 250, and 300 °C. Where inorganic based adhesives such as ceramic threadlockers can resist up to 650 °C and silicone based can exceed 350 °C.

WORP3 · « **Reply #15 on:** January 15, 2021, 05:58:26 pm »

I finally found a way to get my S/N back inside my scope

After the failed attempt to use the clear command inside the topscript, I tried to just remove the battery from my nvram. Unfortunately after I opened my scope it seems that my powerpc bord has a Dallas block with integrated battery instead of this clip on thing, so no removing battery quickly

I searched a lot for a different solution to get rid of my nvram data, I found out that VxWorks is having a lot more capability then I would have suggested. It even seems possible to use commands to write actually something in your nvram, or get something out off-course. The big question was, at which address is that nvram located

Luckily there is a debugger inside VxWorks with even a hex monitor, so after a lot of searching trough it's memory space, I finally found out where the nvram is located:

0xfd0c0000-0xfd0dffff NVRAM
0xfd0e0000-0xfd0fffff NVRAM mirror

With this information I wrote some scripts that make it possible to backup and restore your nvram data, and to clear it by filling it with an empty file. I've attached the necessary files, it's best to place them all inside your c:/vxBoot directory. At least I presume that they are at that location in my description below.

Before using any of those scripts it's probably better to rename your topscript.hw and reboot your powerpc, just to be sure that no Tek software is intervening. After the reboot first go to your vxBoot dir by using the following command:

Code: [Select]

cd "pc:c:/vxBoot"
!!Very important, use any of these scripts At Your Own Risk! Don't use them if you not sure what you are doing!!

After that u can just use one of the following commands:

To make a backup of your nvram, use:

Code: [Select]

< NVRAMToFile.txt

To restore a backup file back inside your nvram, use:

Code: [Select]

< FileToNVRAM.txt

To clear the whole content of your nvram, use:

Code: [Select]

< EmptyNVRAM.txt

Code: [Select]

cd "pc:c:/vxBoot" to go to the vxBoot dir and execute your topscript using the < with your topscript_name

After my topscript was ready, my scope had it's original serial number and the matching options back, finally

WORP3 · « **Reply #16 on:** January 15, 2021, 06:09:16 pm »

Ohh one more thing. It can happen that your scope reboots just fine and that it seems that your boot settings are still there, this is probably not the case after a clear. It's best to enter your settings and use the following command to check if your boot settings are actually inside the nvram:

Code: [Select]

d 0xfd0c0100
U can also check if your serial number is actually inside the nvram if you use this command:

Code: [Select]

d 0xfd0c1000
You are looking directly inside the memory so it's not lined up correctly. But you should be able to just look and see if it's there.
Also use as a target name inside your boot settings the string "tds7000" or it probably will not keep your current control settings when rebooting your scope!

charlyd · « **Reply #17 on:** January 15, 2021, 10:51:18 pm »

Hi WORP3 very nice post and very helpfull thanks.
Keep up the good work

WORP3 · « **Reply #18 on:** February 07, 2021, 02:28:36 pm »

In the meantime I replaced my NVRAM as it was constantly strewing up my settings. Here are some pictures I took during the replacement of the NVRAM. The one that came off the board had a date code from 2001 so it's no more then logical that it was screwing up my data.
I first wanted to just use hot air to remove the Dallas chip but after a while I noticed that I had really needed to turn up the heat to get it loose, so I stopped at mechanically separated the pins out of the Dallas chip. This way I could just remove the pins one at the time. The new chip is placed on a socket so it will be a lot easier to replace it the next time

Johnny10 · « **Reply #19 on:** February 07, 2021, 02:56:49 pm »

Why the Zip tie on the Dallas chip?

WORP3 · « **Reply #20 on:** February 07, 2021, 03:12:33 pm »

Quote from: Johnny10 on February 07, 2021, 02:56:49 pm

Why the Zip tie on the Dallas chip?

To prevent the chip from falling out of the socket during transport/vibration, the chip is quite heavy. It's just a precaution

WORP3 · « **Reply #21 on:** February 01, 2022, 05:35:29 pm »

Quote from: WORP3 on January 15, 2021, 06:09:16 pm

Ohh one more thing. It can happen that your scope reboots just fine and that it seems that your boot settings are still there, this is probably not the case after a clear. It's best to enter your settings and use the following command to check if your boot settings are actually inside the nvram:

Code: [Select]
d 0xfd0c0100
U can also check if your serial number is actually inside the nvram if you use this command:

Code: [Select]
d 0xfd0c1000
You are looking directly inside the memory so it's not lined up correctly. But you should be able to just look and see if it's there.
Also use as a target name inside your boot settings the string "tds7000" or it probably will not keep your current control settings when rebooting your scope!

I had to come back on these addresses where the serial number is located inside the NVRAM. As the most of the NVRAM is in fact a ram drive, the actual serial number is inside some kind of database file and can therefore change location inside this ram drive. Probably right after a complete clear it will be at the above location.

xiang_zhen · « **Reply #22 on:** November 21, 2022, 03:52:20 am »

hi, Thanks for your detail comments about the tds7104/7404 issue fixed experience, I have same issue with this device, but the log is a little different, please could you help to check what happen? thanks

UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

romPost: MPC106 Walking-one passed.

romPost: MPC106 configuration passed.

romPost: First PCI access passed.

romPost: PC87560 Walking-one passed.

romPost: PC87560 configuration passed.

romPost: DEC21554 configuration passed.

romPost: PERFORMING ROM CHECKSUM TEST...

romPost: ROM checksum passed.

romPost: PERFORMING DRAM CELL TEST...

romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.

romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.

romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...

romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...

romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...

romPost: PERFORMING DRAM WALKING-ONE TEST...

romPost: DRAM Walking-one test passed.

romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...

romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.

romPost: POWER-UP DIAGNOSTIC COMPLETE.

Hel

VxWorks System Boot

Copyright 1984-1996 Wind River Systems, Inc.

CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.8.1
Creation date: Jun 27 2003, 09:52:39

Press any key to stop auto-boot...
1

[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]: c

'.' = clear field; '-' = go to previous field; ^D = quit

boot device : sm
processor number : 0
host name :
file name : c:/vxboot/vxWorks.st
inet on ethernet (e) :
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
user (u) :
ftp password (pw) (blank = use rsh):
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw c:/vxBoot/topScript.hw
other (o) : nvfs=0x1000

[VxWorks Boot]:
[VxWorks Boot]: @

boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxBoot/topScript.hw
other (o) : nvfs=0x1000

Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network intPC1 dio device driver installed
erface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773516
Starting at 0x200000...

Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6008 symbols for standalone.

]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997

CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.1 .
WDB: Ready.

usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxBoot/topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################

cd "dbfs:c:/vxBoot"
value = 0 = 0x0

ld < TekScope.o
value = 23662048 = 0x1690de0
ld < TekScopeSM.o
value = 23661408 = 0x1690b60

pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1692720: value = 23668544 = 0x1692740 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x16909a0: value = 23661056 = 0x1690a00 = pDBfs + 0x60
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0

overrideFPdefaults()
value = 0 = 0x0

measurePPCtimebase
value = 0 = 0x0

registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0

semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00

initSysWaiter()
value = 0 = 0x0

raxInit
value = 0 = 0x0
paiInit
done
value = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948

verifyAcqBoardID
value = 0 = 0x0

#xiangzhe add
tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
value = 0 = 0x0

updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16975c0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0

raxInitializeDevices
0x16975c0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x16975c0 (tShell): (Re)starting Acq Processor
value = 23688080 = 0x1697390

excHookAdd(stopStressForException)
value = 17557980 = 0x10be9dc = stopStressForException

dsyInit
value = 21806216 = 0x14cbc88
dsyWPApplyNextRegs
value = 17760428 = 0x10f00ac = DsyRegisterTable + 0xab0

# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1

nvram_initFileSys
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4e9e3

TmgrInit("/db")
0x16975c0 (tShell): Assertion failed: status == EXIT_SUCCESS, file ../src/dbmsInterfaceLibrary.cpp, line 14916

from here, the PPC board is halt and no print message any more, if we press Ctrl+X, PPC board reset.

charlyd · « **Reply #23 on:** November 21, 2022, 08:26:43 pm »

i would start to swap out your NVram dallas DS1245. that a much better starting point for your debug log

xiang_zhen · « **Reply #24 on:** November 25, 2022, 08:24:19 am »

Hi, thanks for your reply, I have swaped out the DS1245, but the issue is still open, there are two issue, one is

nvfs: STATUS: Mounting existing NVRAM file system
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed

the other is:

TmgrInit("/db")
0x16975c0 (tShell): Assertion failed: status == EXIT_SUCCESS, file ../src/dbmsInterfaceLibrary.cpp, line 149

which should be s.w issue, h.w should be ok, but we don't know how to fix it.

I removed the # which was before the NvramClearDb = 1 command inside the topscript and rebooted the scope. Afterwards waiting for a while it seems that the scope hangs at the tektronix logo

After connecting a terminal to the debug port it seem's that the vxWorks is booting but when executing the topscript.hw script,it halt on command "TmgrInit("/db")", same as below.

TmgrInit("/db")
0x16975c0 (tShell): Assertion failed: status == EXIT_SUCCESS, file ../src/dbmsInterfaceLibrary.cpp, line 149


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Boot problem on Tektronix TDS7404 scope? (Solved) (Read 5825 times)

Share me