Tektronix TDS 7404 stuck on booting VxWorks

[geshka]

Hello team. 
I posted this already to the older thread but it is not getting any hits, so I am hoping to get some answers in a new one.

I am restoring TDS 7404  which had general boot problems.  I re-imaged HDD and scope started to boot into Windows 2000 no problems. When it is starting scope SW, however, it is stuck.  As per recommendations here I connected serial terminal and recreated boot config for the PPC board. It is starting to boot into VxWorks and even showed me scope picture once.  After that I tried to reboot it and VxWorks is having exception   - see below.  I renamed startup script to see if it is something there - VxWorls still "hangs"  , i guess it not even coming to execute startup script.
Here my questions:
Is there way to understand what is causing to VxWorks to "hang" ?
Is there possibility  to re-init NVRAM completely ?
Is there debugging options for VxWorks to understand what is causing it to "hang" ?

Any other bright ideas ?

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 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)            : 0x1000
target name (tn)     : target
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 inPC1 dio device driver installed
terface lo0... done.
Attaching DIO client... done.
Loading c:\vxBoot\vxWorks.st...1773516
Starting at 0x200000...

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

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

This is what I see after pressing Ctrl-C into terminal - looks like a strack trace

Code: [Select]

2f1588 vxTaskEntry    +60 : 223d6c ()
223d6c usrRoot        +458: usrNvFsInit ()
206abc usrNvFsInit    +18c: dosFsDevInit ()
2a1838 dosFsDevInit   +260: 2a6170 ()
2a6230 dosFsTimeSet   +2ac: 2a6a84 ()
2a6de8 dosFsTimeSet   +e64: 2a210c ()
2a23c8 dosFsDevInitOptionsSet+aec: 2a210c ()
2a21e8 dosFsDevInitOptionsSet+90c: 2a0b50 ()
2a0b78 symSRemove     +c8c: 2a5cdc ()
293c34 ramDevCreate   +1f0: bcopy ()

[cruff]

Typing a control-C in the VxWorks interpreter will interrupt the current task and produce a stack back trace like you see. At the point you interrupted it it was copying some data, possibly into the RAM disk.

In the first capture you showed, was that before or after you typed the control-C? That appears to show a data access exception for the tRootTask task.

I'm not familiar with VxWorks 5.3, so I don't know what tRootTask is responsible for on your device.

You could enter the "i" command to see what the state of the tasks are. Maybe there will be some clue from the names or if some of them are in the STOPPED state.

[geshka]

Cruff.

First capture was produced before Crtl-C .  At that  point PPC board was not responding at any command or letter I was pressing.  What was working is only Ctrl-C that was generating stack trace  - (second capture)  or Ctrl-X causing VxWorks to restart.   

[cruff]

Sounds like the initialization process didn't make it to the point where the VxWorks C interpreter shell is running, or the scope's kernel build doesn't enable the shell on the serial port (either is possible).

Since you've seen variable behavior on multiple boot attempts, there may be something wrong with the hardware associated with the PPC chip. It looks like the PPC hardware is working well enough to boot from the Windows side of things.

Does the Windows side have a prototype file system image that is used to populate the NVRAM file system the PPC is using? I'm just guessing from the stack back trace, but the NVRAM might be formatted as a DOS FAT file system. Is there anything in the PPC boot configuration that gives a possible clue?

[coromonadalix]

you have a dedicated thread here about the tds7000 / tds7k  series  you should have posted there

starting many thread to get some hits ......

you killed an sell buy thread, and was locked by admin, you posted other threads about this same equipement ...

[geshka]

you have a dedicated thread here about the tds7000 / tds7k  series  you should have posted there

starting many thread to get some hits ......

you killed an sell buy thread, and was locked by admin, you posted other threads about this same equipement ...

Guilty on all counts 

[geshka]

Does the Windows side have a prototype file system image that is used to populate the NVRAM file system the PPC is using? I'm just guessing from the stack back trace, but the NVRAM might be formatted as a DOS FAT file system. Is there anything in the PPC boot configuration that gives a possible clue?

Cruff. I am not sure.  I was looking into hidden Windows folder - c:\VxBoot and did not find anything that might be giving a hint. 

[Simon]

Hello team. 
I posted this already to the older thread but it is not getting any hits, so I am hoping to get some answers in a new one.

You may be happy but many people do not appreciate duplicate threads.