Author Topic: non-booting / defectiveTDS7054  (Read 2487 times)

0 Members and 1 Guest are viewing this topic.

Offline blacknoise

  • Contributor
  • Posts: 31
  • Country: de
non-booting / defectiveTDS7054
« on: June 16, 2014, 12:08:03 pm »
Hello,

after longer reading this is my very first posting here - so for the first:

MANY, many thanks for this outstanding community and forum!


Currently i am trying to repair a TDS7054.

As the PowerCAP of the NVRAM was empty, i had to replace that and to restore the data needed  to boot the PPC board.

Therefore i used similar data as shown here https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/ or here http://dev.xdevs.com/projects/csa7404/wiki/Wiki.

Instead of the startup script file "c:\vxBoot\dio_rst.vsh" - which i could not find on my hard drives - i used "c:\vxBoot\topScript.hw". I found a hint referencing this file as the script anywhere in the internet, without knowing if this is ok...

But i think, my TDS does not execute this script anyway, as soon after the big VxWorks ASCII logo and just below the "usrNvFsInit"-line it does not show the correct:

"nvfs: WARNING: Creating new NVRAM file system"  (as shown in the CSA7404 repair project),

but it stops immediately with an exception:

Code: [Select]
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0

data access
Exception current instruction address: 0x00223f98
Machine Status Register: 0x0000b030
Data Access Register: 0xf9f8f416
Condition Register: 0x20000042
Data storage interrupt Register: 0x40000000
Task: 0x1fffe08 "tRootTask"

So my questions are:

1) What is the correct content of the "c:\vxBoot\dio_rst.vsh" file  -  and/or: is "c:\vxBoot\topScript.hw" really a suitable supplement for this file?

2) What is the meaning of the exception message above? Does it indicate a hardware failure on the PPC-Board?

As i used two different hard disks for trying the TDS7054 to boot from (one with a Win95-Installation, and one with a WinXP-Installation - and both working perfectly on other TDS7054 hardware), i currently do not think that a defective "vxWorks.st" file is the reason for the error...

Thanks to everybody for reading so far - and i will be very happy with any hint or help...

Kind regards
Norbert

 

Offline TiN

  • Super Contributor
  • ***
  • Posts: 3955
  • Country: tw
  • xDevs.com/live - 24/7 lab feed
    • xDevs.com
Re: non-booting / defectiveTDS7054
« Reply #1 on: June 16, 2014, 02:40:52 pm »
Post your .vsh file, i'll take a look :)
YouTube | Chat room | Live-cam | Have documentation to share? Upload here! No size limit, firmware dumps, photos.
 

Offline blacknoise

  • Contributor
  • Posts: 31
  • Country: de
Re: non-booting / defectiveTDS7054
« Reply #2 on: June 16, 2014, 03:21:44 pm »
Many thanks for your reply TiN!

The only ".vsh" file in my vxBoot folder is "tcsTopScript.vsh":

Code: [Select]
    #################### topScript starts ###############################
    #
    #  This script was initially constructed by running
    # make scripts/topScript
    #  in the nextGen directory.
    #
    #  This script is for standalone prototypes that want to update
    #   their bootROMs to the newest version in the
    #   scope's c:/vxBoot directory.
   
    cd "pc:c:/vxboot"
    tcsLoadTableToNVRAM "setup.tcs"

    #
    # hopefully you get this message at the end:
    # 'value = 0 = 0x0'
    # REBOOT!!!

...and the "breaking news": the TDS7054 is running!

Until now only "close" to perfect - only via an external Display at the VGA on the PPC board - the internal TFT is not working.

But what did i do to let the PPC boot? I only changed the last line in the PPC boot script from "nvfs=0x1000" to "nvfs=0x0000":

Code: [Select]
boot device          : sm
processor number     : 0
host name            : host
file name            : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00
host inet (h)        : 192.168.0.1
gateway inet (g)     : 192.168.0.2
user (u)             : anonymous
ftp password (pw)    : anonymous
flags (f)            : 0x1008
target name (tn)     : TDS
startup script (s)   : c:\vxBoot\topScript.hw
other (o)            : nvfs=0x0000

To be honest - i fiddled around without really knowing what this line specifies.  Is this possibly the offset/address to store the script in the NVRAM? And - if this is true - is the size of the NVRAM in a TDS7404 bigger than the one in a TDS7054? Was possibly accessing the NVRAM out of bounds the reason for the exception?

Another "mystery": At first i changed the nvfs value down to 0x800 - with the funny effect that the TDS sometimes started perfect, and sometimes annoyed me with the exception????

And for completeness - that is the content of the "topScript.hw":

Code: [Select]
    ################### topScript starts ###############################

     cd "dbfs:c:/vxBoot"
   
    ld < TekScope.o
    ld < TekScopeSM.o

    pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
    pDBfs  = dosFsMkfs("/db", pDbDev)
    copy ("TekScope.DBF", "/db/TekScope.DBF")
   
    overrideFPdefaults()

    measurePPCtimebase

    registerMemPartitionSizes ( 0x00000000 )

    semInitForQueueCheckLogMsg

    initSysWaiter()
   
    raxInit
    paiInit

    verifyAcqBoardID

     updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
     cd "pc:"

    raxInitializeDevices
   
    excHookAdd(stopStressForException)
   
   
    dsyInit
    dsyWPApplyNextRegs
   
    # remove '#' from next line to set powerup scope state to factory default:
    # NvramClearDb = 1
   
    nvram_initFileSys
   
    TmgrInit("/db")
    PhxProxyInit
    rtlInit

    sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
   
    hwAccount_init
   
    GpibInit

    wfmMemInit(1)
   
    vertInstall
 
    calConStatus = cc_init(2)

    updateTrigCal

    MathMeasCreateTheMathandMeasurementLibraries
    initAcqMapper
    trigMapInit
    dsyMapInit
    mathMapperInit
    utilMapInit
   
    TmgrHookup
    PhxProxyHookup
    hookupAcqMapper
    MathMeasMapHookup
    dsyMapHookup
    utilMapHookup
   
    rtlHookup
    horizMapHookup
    fastFrameMapHookup
    trigMapHookup
    vertMapHookup
    spcMapHookup
    autosetMapHookup
    timeSyncMapHookup
    auxTrigMapHookup
    dpoMapHookup
   
   
    TmgrStartup
    PhxProxyStartup
    taskDelay(2)

    gpibHwInitC
    gpibTaskSpawn

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"   

    enablePowerupDiags = 0
 
    runPowerupDiags
 
    rtlStartup
   
    tsComp

    ################### topScript ends ###############################

So, before i investigate what could be wrong with the internal TFT, i need some sleep - here in Germany it's already 7:15. AM. ;-)
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf