Boot problem on Tektronix TDS7404 scope? (Solved) - Page 1
Forum section: electronics / repair

author: WORP3
author_rank: Contributor
timestamp: December 16, 2020, 05:20:01 pm
content: First of all, hi to you all, just registered myself after reading so many lovely posts on this EEVblogI 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 logoAfter 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 fileEven 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.QuoteDoes 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.

author: WORP3
author_rank: Contributor
timestamp: December 16, 2020, 05:47:46 pm
content: 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.hwBut unfortunately still getting the same problem, so it's not a timing problem.Code:-> < TopScript.hw################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0pwddbfs:c:/vxBootvalue = 15 = 0xfld < TekScope.o'an't open input 'TekScope.oerrno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)->

author: WORP3
author_rank: Contributor
timestamp: December 16, 2020, 05:58:37 pm
content: This (here below) is really defying all programming logic----Default script loading on startup:Code:################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0pwddbfs:c:/vxBootvalue = 15 = 0xfld < TekScope.o'an't open input 'TekScope.oerrno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)Done executing startup script c:\vxBoot\TopScript.hwKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!----Manual entering the faulty command:Code:-> ld < TekScope.ovalue = 33547168 = 0x1ffe3a0----Rerunning the topscript.hw script again:Code:-> < TopScript.hw################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0pwddbfs:c:/vxBootvalue = 15 = 0xfld < TekScope.o'an't open input 'TekScope.oerrno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)->What the

author: WORP3
author_rank: Contributor
timestamp: December 17, 2020, 04:27:34 pm
content: YesssI 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 errorCode:################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0pwddbfs:c:/vxBootvalue = 15 = 0xfld < TekScope.ovalue = 21167072 = 0x142fbe0ld < TekScopeSM.ovalue = 21166624 = 0x142fa20So, never use the internal windows notepad to change your TopScript.hw fileThen again, for some reason my S/N isn't updated, even after clearing out the NVRAM and rebooting it againDuring boot I keep getting the message that no backup key has been found, shouldn't this message disappear after one reboot?Code:0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...

author: WORP3
author_rank: Contributor
timestamp: December 17, 2020, 05:21:59 pm
content: Now for some reason I can't the scope to accept my snI also keep getting a kernel version mismatch during boot, someone any bright idea?Code:0x16936c0 (tShell): >> Kernel version 1.0.8.0 does not match Boot ROM version 1.0.4.0Here 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 momentCode:UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUromPost: 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.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.4.0Creation date: Nov 2 2000, 11:03:34Press any key to stop auto-boot...0auto-booting...boot device : smprocessor number : 0host name : hostfile name : c:\vxBoot\vxWorks.stinet on backplane (b): 192.168.0.1:ffffff00host inet (h) : 192.168.0.2gateway inet (g) : 192.168.0.1flags (f) : 0x1008target name (tn) : tds7000startup script (s) : c:\vxBoot\TopScript.hwother (o) : nvfs=0x1000Initializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching network intePC1 dio device driver installedrface lo0... done.Attaching DIO client... done.Loading c:\vxBoot\vxWorks.st...1773516Starting at 0x200000...User: targetInitializing backplane net with anchor at 0x16e0000... done.Backplane anchor at 0x16e0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching 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-1997CPU: 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=0nvfs: STATUS: Mounting existing NVRAM file systemKERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:\vxBoot\TopScript.hw ...dbFsIoctl: invalid code 3################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0pwddbfs:c:/vxBootvalue = 15 = 0xfld < TekScope.ovalue = 21167072 = 0x142fbe0ld < TekScopeSM.ovalue = 21166624 = 0x142fa20pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)new symbol "pDbDev" added to symbol table.pDbDev = 0x168d040: value = 23646304 = 0x168d060 = pDbDev + 0x20pDBfs = dosFsMkfs("/db", pDbDev)new symbol "pDBfs" added to symbol table.pDBfs = 0x168ba20: value = 23646048 = 0x168cf60copy ("TekScope.DBF", "/db/TekScope.DBF")value = 0 = 0x0overrideFPdefaults()value = 0 = 0x0measurePPCtimebasevalue = 0 = 0x0registerMemPartitionSizes ( 0x00000000 )value = 0 = 0x0semInitForQueueCheckLogMsgvalue = 23652448 = 0x168e860initSysWaiter()value = 0 = 0x0raxInitvalue = 0 = 0x0paiInitdonevalue = 16916276 = 0x1021f34 = PaiBaseRegisterTable + 0x948verifyAcqBoardIDvalue = 0 = 0x0tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"value = 0 = 0x0updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")0x16936c0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.value = 1 = 0x1cd "pc:"value = 0 = 0x0raxInitializeDevicesdone0x16936c0 (tShell): (Re)starting Acq Processorvalue = 23633928 = 0x168a008excHookAdd(stopStressForException)value = 16703148 = 0xfedeac = stopStressForExceptiondsyInitvalue = 23625768 = 0x1688028dsyWPApplyNextRegsvalue = 16906152 = 0x101f7a8 = DsyRegisterTable + 0xab0# remove '#' from next line to set powerup scope state to factory default:# NvramClearDb = 1nvram_initFileSys0x16936c0 (tShell): >> Kernel version 1.0.8.0 does not match Boot ROM version 1.0.4.0value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba540c3TmgrInit("/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 = 0x0PhxProxyInitvalue = 21175904 = 0x1431e60rtlInitvalue = 0 = 0x0sysExtMemAddToPool memSysPartId,0x02000000,0x0e000000value = 0 = 0x0hwAccount_initsysEnetAddrGet: 45:00:cc:ba:44:00value = 0 = 0x0GpibInitvalue = 267500128 = 0xff1ba60wfmMemInit(1)value = 57781984 = 0x371aee0vertInstallvalue = 57774948 = 0x3719364calConStatus = cc_init(2)0x16936c0 (tShell): Reading 300 bytes of service cal data from EEPROM into 0x37192200x16936c0 (tShell): nvMem_read succeeded0x16936c0 (tShell): Reading 82 bytes of service cal data from EEPROM into 0x37193000x16936c0 (tShell): nvMem_read succeeded0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/00x16936c0 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/10x16936c0 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/20x16936c0 (tShell): cc_init: bank 2 chksum failed, NOT reset to factory0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/30x16936c0 (tShell): cc_init: bank 3 chksum failed, NOT reset to factory0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/50x16936c0 (tShell): cc_init: bank 5 chksum failed, NOT reset to factory0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/60x16936c0 (tShell): cc_init: bank 6 chksum failed, NOT reset to factory0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/70x16936c0 (tShell): cc_init: bank 7 chksum failed, NOT reset to factory0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/80x16936c0 (tShell): cc_init: bank 8 chksum failed, NOT reset to factory0x16936c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/150x16936c0 (tShell): cc_init: bank 15 chksum failed, NOT reset to factory0x16936c0 (tShell): Optical hardware is not present.calConStatus = 0x1324d08: value = 33263 = 0x81efvertPostCalRestoreInstallvalue = 0 = 0x0MathMeasCreateTheMathandMeasurementLibrariesvalue = 57602368 = 0x36ef140initAcqMapper0x16936c0 (tShell): initAcqMapper: Entervalue = 0 = 0x0trigMapInitvalue = 0 = 0x0dsyMapInitvalue = 0 = 0x0mathMapperInitvalue = 0 = 0x0utilMapInitvalue = 57599712 = 0x36ee6e0TmgrHookupvalue = 0 = 0x0PhxProxyHookupvalue = 0 = 0x0hookupAcqMappervalue = 20007032 = 0x1314878 = AcqMapperRtlDataListMathMeasMapHookupvalue = 23671784 = 0x16933e8dsyMapHookupvalue = 23671888 = 0x1693450utilMapHookupvalue = 23671920 = 0x1693470rtlHookupvalue = 0 = 0x0horizMapHookupvalue = 23671880 = 0x1693448fastFrameMapHookupvalue = 23671904 = 0x1693460trigMapHookupvalue = 23671912 = 0x1693468vertMapHookupvalue = 23671904 = 0x1693460spcMapHookupvalue = 23671904 = 0x1693460autosetMapHookupvalue = 23671944 = 0x1693488timeSyncMapHookupvalue = 23671936 = 0x1693480auxTrigMapHookupvalue = 23671920 = 0x1693470dpoMapHookupvalue = 23671912 = 0x1693468TmgrStartupvalue = 56649296 = 0x3606650PhxProxyStartupvalue = 56598752 = 0x35fa0e0taskDelay(2)0x3681ec0 (tmgr): >> optNewOptKey: Bad instru Idvalue = 0 = 0x0gpibHwInitCvalue = 0 = 0x0gpibTaskSpawnvalue = 56072928 = 0x3579ae0gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"value = 55861056 = 0x3545f40enablePowerupDiags = 0enablePowerupDiags = 0x12ea4e8: value = 0 = 0x0EnableHorizInterpolation=1new symbol "EnableHorizInterpolation" added to symbol table.EnableHorizInterpolation = 0x14593c0: value = 1 = 0x1runPowerupDiagsdonedipSwitch = 0x0, enablePowerupDiags = 0, puMode=0CalDiagPowerUpDiagsEnabled = 0!! SKIPPING POWERUP DIAGNOSTICS !!value = 0 = 0x0rtlStartupvalue = 0 = 0x0tsCompvalue = 0 = 0x0################### topScript ends ###############################Done executing startup script c:\vxBoot\TopScript.hwKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!->

author: m k
author_rank: Super Contributor
timestamp: December 19, 2020, 12:16:17 pm
content: (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.

author: WORP3
author_rank: Contributor
timestamp: December 19, 2020, 04:49:13 pm
content: 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.

author: m k
author_rank: Super Contributor
timestamp: December 19, 2020, 06:54:45 pm
content: 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.

author: WORP3
author_rank: Contributor
timestamp: December 25, 2020, 10:35:30 am
content: 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:# remove '#' from next line to set powerup scope state to factory default:NvramClearDb = 1NvramClearDb = 0x131484c: value = 1 = 0x1nvram_initFileSysFor some reason the clear NVRAM is only triggering the option key from resetting, not the actual serial numberAny of you got some idea's on how to trigger a sn reset?Code:TmgrInit("/db")0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...0x16936c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...

author: WORP3
author_rank: Contributor
timestamp: December 25, 2020, 10:50:25 am
content: Looking at the bootup log, I also noticed that it keep telling me that the boot rom wasn't matching the kernel version.Code:nvram_initFileSys0x16936c0 (tShell): >> Kernel version 1.0.8.0 does not match Boot ROM version 1.0.4.0value = -1 = 0xffffffff = pDbDev + 0xfe972fbfLooking 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:CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.4.0Creation date: Nov 2 2000, 11:03:34After some more research I stumbled on a script that was actually ment to update the boot rom flash, zie script below:Code:#################### 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 = 0x0I 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.vxwEven more nerve wracking I watched the script doing it's job, hoping nothing is going wrong during this update:Code:-> < 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 regionsysFlashUpdate: Erasing flash...donesysFlashUpdate: Writing flash sectorss0@0xff800000................s1@0xff810000................s2@0xff820000................s3@0xff830000................s4@0xff840000................s5@0xff850000................s6@0xff860000................s7@0xff870000................sysFlashUpdate: SUCCESS: flash writtensysFlashUpdate: TESTING: comparing regionvalue = 0 = 0x0setLED 0x40value = -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 goneFor those interested, the actually boot prom on the bord is an: AM29LV040B-90JC

author: WORP3
author_rank: Contributor
timestamp: December 25, 2020, 11:17:45 am
content: 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: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

author: WORP3
author_rank: Contributor
timestamp: December 25, 2020, 11:20:24 am
content: Can anyone tell me why the inline tumbnail or full image attachment options isn't working?

author: Tantratron
author_rank: Frequent Contributor
timestamp: January 15, 2021, 06:40:48 am
content: Quote from: WORP3 on December 25, 2020, 11:17:45 amHello, 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

author: WORP3
author_rank: Contributor
timestamp: January 15, 2021, 01:17:07 pm
content: Quote from: Tantratron on January 15, 2021, 06:40:48 amYhea,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

author: WORP3
author_rank: Contributor
timestamp: January 15, 2021, 05:23:51 pm
content: QuoteIt 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

author: WORP3
author_rank: Contributor
timestamp: January 15, 2021, 05:58:26 pm
content: I finally found a way to get my S/N back inside my scopeAfter 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 quicklyI 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 locatedLuckily 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 NVRAM0xfd0e0000-0xfd0fffff NVRAM mirrorWith 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: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:< NVRAMToFile.txtTo restore a backup file back inside your nvram, use:Code:< FileToNVRAM.txtTo clear the whole content of your nvram, use:Code:< EmptyNVRAM.txtAfter clearing your nvram just reboot your powerpc.Don't forget using the clear script will wipe your nvram data, so also your boot settings, your serial number and your option key. Make sure you have the correct .sn and .key files inside your vxBoot directory so it will get restored after the first execution of the topscript.After reboot just useCode:cd "pc:c:/vxBoot"to go to the vxBoot dir and execute your topscript using the < with your topscript_nameAfter my topscript was ready, my scope had it's original serial number and the matching options back, finally

author: WORP3
author_rank: Contributor
timestamp: January 15, 2021, 06:09:16 pm
content: 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:d 0xfd0c0100U can also check if your serial number is actually inside the nvram if you use this command:Code:d 0xfd0c1000You 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 yourcurrent control settingswhen rebooting your scope!

author: charlyd
author_rank: Frequent Contributor
timestamp: January 15, 2021, 10:51:18 pm
content: Hi WORP3 very nice post and very helpfull thanks.Keep up the good work

author: WORP3
author_rank: Contributor
timestamp: February 07, 2021, 02:28:36 pm
content: 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

author: Johnny10
author_rank: Frequent Contributor
timestamp: February 07, 2021, 02:56:49 pm
content: Why the Zip tie on the Dallas chip?

author: WORP3
author_rank: Contributor
timestamp: February 07, 2021, 03:12:33 pm
content: Quote from: Johnny10 on February 07, 2021, 02:56:49 pmTo prevent the chip from falling out of the socket during transport/vibration, the chip is quite heavy. It's just a precaution

author: WORP3
author_rank: Contributor
timestamp: February 01, 2022, 05:35:29 pm
content: Quote from: WORP3 on January 15, 2021, 06:09:16 pmI 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.

author: xiang_zhen
author_rank: Newbie
timestamp: November 21, 2022, 03:52:20 am
content: 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? thanksUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUromPost: 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.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.8.1Creation date: Jun 27 2003, 09:52:39Press 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 = quitboot device : smprocessor number : 0host name :file name : c:/vxboot/vxWorks.stinet on ethernet (e) :inet on backplane (b): 192.168.0.1:ffffff00host inet (h) : 192.168.0.2gateway inet (g) : 192.168.0.1user (u) :ftp password (pw) (blank = use rsh):flags (f) : 0x1008target name (tn) : tds7000startup script (s) : c:/vxboot/topscript.hw c:/vxBoot/topScript.hwother (o) : nvfs=0x1000[VxWorks Boot]:[VxWorks Boot]: @boot device : smprocessor number : 0file name : c:/vxboot/vxWorks.stinet on backplane (b): 192.168.0.1:ffffff00host inet (h) : 192.168.0.2gateway inet (g) : 192.168.0.1flags (f) : 0x1008target name (tn) : tds7000startup script (s) : c:/vxBoot/topScript.hwother (o) : nvfs=0x1000Initializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching network intPC1 dio device driver installederface lo0... done.Attaching DIO client... done.Loading c:/vxboot/vxWorks.st...1773516Starting at 0x200000...Host Name: bootHostUser: targetInitializing backplane net with anchor at 0x16e0000... done.Backplane anchor at 0x16e0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching 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-1997CPU: 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=0nvfs: STATUS: Mounting existing NVRAM file systemtcsTableUnpack: checksum failed on buffertcsTableLoadFromNVRAM: tcsTableUnpack failedKERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:/vxBoot/topScript.hw ...dbFsIoctl: invalid code 3################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0ld < TekScope.ovalue = 23662048 = 0x1690de0ld < TekScopeSM.ovalue = 23661408 = 0x1690b60pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)new symbol "pDbDev" added to symbol table.pDbDev = 0x1692720: value = 23668544 = 0x1692740 = pDbDev + 0x20pDBfs = dosFsMkfs("/db", pDbDev)new symbol "pDBfs" added to symbol table.pDBfs = 0x16909a0: value = 23661056 = 0x1690a00 = pDBfs + 0x60copy ("TekScope.DBF", "/db/TekScope.DBF")value = 0 = 0x0overrideFPdefaults()value = 0 = 0x0measurePPCtimebasevalue = 0 = 0x0registerMemPartitionSizes ( 0x00000000 )value = 0 = 0x0semInitForQueueCheckLogMsgvalue = 21818112 = 0x14ceb00initSysWaiter()value = 0 = 0x0raxInitvalue = 0 = 0x0paiInitdonevalue = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948verifyAcqBoardIDvalue = 0 = 0x0#xiangzhe addtcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"value = 0 = 0x0updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")0x16975c0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.value = 1 = 0x1cd "pc:"value = 0 = 0x0raxInitializeDevices0x16975c0 (tShell): >> Setting PLL to 1.25e+09 Hz.done0x16975c0 (tShell): (Re)starting Acq Processorvalue = 23688080 = 0x1697390excHookAdd(stopStressForException)value = 17557980 = 0x10be9dc = stopStressForExceptiondsyInitvalue = 21806216 = 0x14cbc88dsyWPApplyNextRegsvalue = 17760428 = 0x10f00ac = DsyRegisterTable + 0xab0# remove '#' from next line to set powerup scope state to factory default:# NvramClearDb = 1nvram_initFileSysvalue = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4e9e3TmgrInit("/db")0x16975c0 (tShell): Assertion failed: status == EXIT_SUCCESS, file ../src/dbmsInterfaceLibrary.cpp, line 14916from here, the PPC board is halt and no print message any more, if we press Ctrl+X, PPC board reset.

author: charlyd
author_rank: Frequent Contributor
timestamp: November 21, 2022, 08:26:43 pm
content: i would start to swap out your NVram dallas DS1245. that a much better starting point for your debug log

author: xiang_zhen
author_rank: Newbie
timestamp: November 25, 2022, 08:24:19 am
content: Hi, thanks for your reply, I have swaped out the DS1245, but the issue is still open, there are two issue, one isnvfs: STATUS: Mounting existing NVRAM file systemtcsTableUnpack: checksum failed on buffertcsTableLoadFromNVRAM: tcsTableUnpack failedthe other is:TmgrInit("/db")0x16975c0 (tShell): Assertion failed: status == EXIT_SUCCESS, file ../src/dbmsInterfaceLibrary.cpp, line 149which 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 logoAfter 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

author: xiang_zhen
author_rank: Newbie
timestamp: November 29, 2022, 03:51:31 am
content: Hi, I have swaped out the DS1245, but the issue is still open, there are two issue, one isnvfs: STATUS: Mounting existing NVRAM file systemtcsTableUnpack: checksum failed on buffertcsTableLoadFromNVRAM: tcsTableUnpack failedthe other is:TmgrInit("/db")0x16975c0 (tShell): Assertion failed: status == EXIT_SUCCESS, file ../src/dbmsInterfaceLibrary.cpp, line 149which 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 logoAfter 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 149please could you help to check and advise, I really have no idea, thanks very much.

author: Elevon
author_rank: Newbie
timestamp: January 27, 2023, 05:35:25 am
content: Hello everyone,I'm trying to dump the contents of my NVRAM so that I can save whatever is on there in case I need it going forward. Unfortunately, my TDS 7404 came without a HDD, so I don't have a backup copy of the NVRAM contents.I'm trying to run @WORP3's code, but it doesn't seem to be working. I do have the files copied to the correct directory, and I made sure not to open them with Notepad. The 7404's terminal doesn't seem to be accepting my commands -- it just spits them back out at me. Maybe someone can give me insight as to what's happening here and if it's fixable without resetting the NVRAM.QuoteI attached a picture as well, so you can see that I'm entering the commands and they're being returned. Apologies if I'm doing something really stupid -- I'm an analog electronics guy with very little understanding of this type of thing.

author: charlyd
author_rank: Frequent Contributor
timestamp: August 05, 2023, 02:46:34 pm
content: hi yes it works great look in your vxboot for a nvrdump.bini guees you created a custom topscript.hw like:Code:################### topScript starts ###############################cd "pc:c:/vxBoot"after booted type the commandline < NVRAMToFile.txt