Tektronix TDS7104 PPC VXWorks no boot (loop)

[Micha]

Hello all together,
our TDS7104 was not used for several years. Now it did not boot. We followed the TDS7000 repair project https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg292041/#msg292041 and replaced the NVRam battery and chip and checked the output of the debug interface.
Currently we are stuck.
The serial debug output of the VXWorks boot contains some crypred characters and the boot process of VXworks starts again and again:
...
auto-booting...
Error in boot line:
  ™€$>  ª 2`ÂÍ ’, SŠ‚I ”\lC÷ tx  á<C<y­m@×" #K‰v·œ6

Can't load boot file!!


[VxWorks Boot]: Starting at 0xfff00100...
....
We are not able to interrupt the auto-boot by sending a character via serial port.
The link from the TDS7000 repair project containing infos on how to set up the boot parameters (tek forum) is broken (If it would be possible to stop the boot loop via serial port.).
We have a original restore CD.
Will a restore CD work? (May be we can get one from a company nearby.)
Is there someone who can give us some help on how to fix the boot process and boot file?

thanks in advance

The entire boot log file:

Code: [Select]

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.1

Creation date: Apr 20 2000, 08:34:24





Press any key to stop auto-boot...

 7
 6
 5
 4
 3
 2
 1
 0

auto-booting...


Error in boot line:

  ™€$>  ª 2`ÂÍ
’
, SŠ‚I ”\lC÷
tx  á<C<y­m@×" #K‰v·œ6

          ^

Can't load boot file!!


[VxWorks Boot]: Starting at 0xfff00100...


[TiN]

Restore CD useless, as NVRAM has incorrect data.
Try another serial port interface/dongle to interrupt autobooting and set settings.

[macboy]

VxWorks bootloader really should stop by pressing any key (sending a character over serial). Ensure you are sending the char at the correct baud rate, correct polarity, on the correct pin, etc. If you are able to stop the bootloader, then you should be able to use its utilities to set the boot line. What that needs to be in your case, I wouldn't know, but that gobbledygook you have now is not it.

[Micha]

Hi again,
thanks a lot.
Sometimes its really hard to count the pins of a SUB-D9. There should be no gap between pin 2 and 3. But it was.
The serial interface is running and we can interrupt the boot process.
So far so good.
I changed the boot settings via serial port.
Now VxWorks is booting but it hangs on accessing data with an exception.
We've changed the DRAM of the PPC board. But it was not successful.

Code: [Select]

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.1
Creation date: Apr 20 2000, 08:34:24

Press any key to stop auto-boot...
 7
 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\my_script.vsh
other (o)            : nvfs=0x1000

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

Starting at 0x200000...
Initializing backplane net with anchor at 0x1de0000... done.
Backplane anchor at 0x1de0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6003 symbols for standalone.
     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.3.0.
                             WDB: Ready.
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0

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

Was it now?

[Jwalling]

You have this setting which might not be right:
startup script (s)   : c:\vxBoot\my_script.vsh

It's usually this:
startup script (s)   : c:\vxboot\topscript.hw

[Micha]

Thanks a lot for all the helpful hints...

The scope is running now.
summary
1. Replacing NVRAM battery and NVRAM-Chip
2. Use a RS232 cable with correct connection.
3. set the vxWorks boot params
4. use the correct startup script

My second mistake (first was not to count correctly) was to use an incorrect script for the first time after setting the boot parameter. I used tcsTopScript.vsh. After running this script vxWorks crashed every time prior to accessing the script in the boot params.
So I decided to start from the beginning again.

I disconnected the NVRAM battery and reconnected it.
The device started with the known error due to wrong boot parameters.
I set the correct boot params with the correct script "topscript.hw" (thanks for the previous post).
Thats all. The scope started, vxWorks booted and the scope program is running.

Next, the functions and measurements needs to be checked.
Hopefully without any issue.

[Micha]

oh no no no..

Sorry I posted too fast.
(Always check the backseat!)
The scope runs only once after disconnecting the battery and setting boot params.
If I restart the scope again it chrashes in the same way as before. 

Do I have to initialise some memories or checksums after setting boot params?
Do I have to run a special script?
Will it be helpful to post the debug log?

[Micha]

ok,
some additional information:
1. No matter if I set the boot parameters again, it does not start a second time, with battery connected.
2. But I can start the scope without battery and set the boot params every start by hand.

I haved checked the soldering of the NVRAM several times, without any trouble. If I interrupt the boot process the printed out boot params are always correct. That tells me, that the battery and NVRAM are working fine in general. 

But the boot log of vxWorks (the first and successful start) tells a lot of checksum errors.

If there is no solution, I will disconnect the NVRAM battery permanently and connect an arduino to the serial, that sends the boot settings every startup.

The self diagnostic of the scope runs without any issue.

 

Code: [Select]

omPost: 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.1
Creation date: Apr 20 2000, 08:34:24
Press any key to stop auto-boot...
 7
 6
c
[VxWorks Boot]:
[VxWorks Boot]: c
...
...
@

[VxWorks Boot]:
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 interface lo0... done.
PC1 dio device driver installed
Attaching DIO client... done.
Loading c:\vxBoot\vxWorks.st...1773344
Starting at 0x200000...
Initializing backplane net with anchor at 0x1de0000... done.
Backplane anchor at 0x1de0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6003 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.3.0.
                             WDB: Ready.
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: WARNING: Creati0xng new NVRAM file 1fffe08system
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
 (tRootTask): memPartAlloc: block too big - 322897788 in partition 0x3375cc.
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 = 30931936 = 0x1d7fbe0
    ld < TekScopeSM.o
value = 30947136 = 0x1d83740
    pDbDev = ramDevCreate(0, 512, 1024, 1024, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1d839e0: value = 30947840 = 0x1d83a00 = pDbDev + 0x20
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1d83580: value = 30947584 = 0x1d83900 = pDBfs + 0x380
    copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
   
    overrideFPdefaults()
value = 0 = 0x0
    measurePPCtimebase
value = 0 = 0x0
    registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
    semInitForQueueCheckLogMsg
value = 30946528 = 0x1d834e0
    initSysWaiter()
value = 0 = 0x0
   
   
   
    raxInit
value = 0 = 0x0
    paiInit
done
value = 22542592 = 0x157f900 = PaiBaseRegisterTable + 0x948
    verifyAcqBoardID
value = 0 = 0x0
   
     updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")   
0x1d8a060 (tShell): 1340 bytes successfully verified.
AVR processor FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.
value = 0 = 0x0
     cd "pc:"
value = 0 = 0x0
    raxInitializeDevices
done
0x1d8a060 (tShell): (Re)starting Acq Processor
value = 30973488 = 0x1d89e30
   
    excHookAdd(stopStressForException)
value = 22295856 = 0x1543530 = stopStressForException
   
   
    dsyInit
value = 29147656 = 0x1bcc208
    dsyWPApplyNextRegs
value = 22532472 = 0x157d178 = DsyRegisterTable + 0xab0
   
   
   
    # remove '#' from next line to set powerup scope state to factory default:
    # NvramClearDb = 1
   
    nvram_initFileSys
0x1d8a060 (tShell): >> Restoring exisiting filesystem in NVRAM...
0x1d8a060 (tShell): >> bd_bytesPerBlk 512 / bd_nBlocks 254 / bd_blksPerTrack 254, pNvRamDiskVolDesc 0x0
0x1d8a060 (tShell): >> Creating new /nvram device...
0x1d8a060 (tShell): >> iosDevFind Status 0x1d9a520
0x1d8a060 (tShell): >> Creating filesystem in NVRAM...
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfb35d723
   
    TmgrInit("/db")
0x1d8a060 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x1d8a060 (tShell): >> Reading config values from files on hard disk....
0x1d8a060 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...
0x1d8a060 (tShell): >> Reading config values from files on hard disk....
0x1d8a060 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x1d8a060 (tShell): >> Reading config values from files on hard disk....
0x1d8a060 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...
0x1d8a060 (tShell): >> Reading config values from files on hard disk....
value = 0 = 0x0
    PhxProxyInit
value = 27785888 = 0x1a7faa0 = invertY + 0x250
    rtlInit
value = 0 = 0x0
    sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0
   
    hwAccount_init
sysEnetAddrGet: 66:c5:23:fa:77:09
value = 0 = 0x0
   
    GpibInit
value = 0 = 0x0
    wfmMemInit(1)
value = 47693536 = 0x2d7bee0
   
    vertInstall
value = 47687652 = 0x2d7a7e4
 
    calConStatus = cc_init(2)
0x1d8a060 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x2d7a6c0
0x1d8a060 (tShell): x24165_read succeeded
0x1d8a060 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0x2d7a780
0x1d8a060 (tShell): x24165_read succeeded
0x1d8a060 (tShell): extd chksum failed, stored = 0xffffffff calc = 0x28d5a0ee
0x1d8a060 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory
0x1d8a060 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x1d8a060 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x1d8a060 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/1
0x1d8a060 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
0x1d8a060 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/2
0x1d8a060 (tShellcalConStatus): cc_init: bank  = 2 chksum failed, NOT reset to factory
0x0x1d8a06017c8f10 (tShell): : value = cc_restoreBank: can't open file 164335C:/vxBoot/calCons/ = 0x3
0x1d8a060281ef (tShell): cc_init: bank
3 chksum failed, NOT reset to factory
0x1d8a060    updateTrigCal (
tShell): cc_restoreBank: can't open file value = C:/vxBoot/calCons/05
0x1d8a060 = 0x (tShell): cc_init: bank 05 chksum failed, NOT reset to factory
0x1d8a060 (
tShell): cc_restoreBank: can't open file     MathMeasCreaC:/vxBoot/calCons/te6TheMathandMeasureme
ntLibraries0x1d8a060
 (tShell): cc_init: bank 6 chksum failed, NOT reset to factory
0x1d8a060 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/7
0x1d8a060 (tShell): cc_init: bank 7 chksum failed, NOT reset to factory
0x1d8a060 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/8
value = 0x1d8a060 (tShell47514752): cc_init: bank  = 0x8 chksum failed, NOT reset to factory
2d50480x01d8a060 (tShell):
cc_restoreBank: can't open file     inC:/vxBoot/calCons/it15AcqMapper
0x1d8a060
 (tShell): cc_init: bank value = 15 chksum failed, NOT reset to factory
00x1d8a060 = 0x (tShell): initAcqMapper: Enter
0
    trigMapInit
value = 0 = 0x0
    dsyMapInit
value = 0 = 0x0
    mathMapperInit
value = 0 = 0x0
    utilMapInit
value = 47512096 = 0x2d4fa20
   
    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 24911840 = 0x17c1fe0 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 30973336 = 0x1d89d98
    dsyMapHookup
value = 30973432 = 0x1d89df8
    utilMapHookup
value = 30973456 = 0x1d89e10
   
    rtlHookup
value = 0 = 0x0
    horizMapHookup
value = 30973424 = 0x1d89df0
    fastFrameMapHookup
value = 30973440 = 0x1d89e00
    trigMapHookup
value = 30973448 = 0x1d89e08
    vertMapHookup
value = 30973440 = 0x1d89e00
    spcMapHookup
value = 30973440 = 0x1d89e00
    autosetMapHookup
value = 30973480 = 0x1d89e28
    timeSyncMapHookup
value = 30973472 = 0x1d89e20
    auxTrigMapHookup
value = 30973456 = 0x1d89e10
    dpoMapHookup
value = 30973448 = 0x1d89e08
   
   
    TmgrStartup
value = 47021648 = 0x2cd7e50
    PhxProxyStartup
value = 46971104 = 0x2ccb8e0
    taskDelay(2)
value = 0 = 0x0
    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 46858832 = 0x2cb0250
    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"   
value = 46828304 = 0x2ca8b10
    enablePowerupDiags = 0
enablePowerupDiags = 0x17a028c: value = 0 = 0x0
 
    runPowerupDiags
0x2d19b20 (tmgr): >> Commit opt_currOptKey string[64] <4YXSS-LFHHJ-TZUNS-ABI8P>
0x2d19b20 (tmgr): >> Writing new checksum 0x69e0 to nvram....
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
done
value = 22552812 = 0x15820ec = SoftSwitchesRegisterTable + 0x48
 
    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!
->


[GastonBA]

Did you found out what was the reason for the boot problem with the battery?