It's solved ! Thanks a lot to
Peyton Bland and Raymond Neff (solution) -
It's running fine again after subsequent
power-cycles - Thanks again !
In my case thr ";p " <enter> has done it.
- the original question follows -
Rainer
##############################################################################
Problem 2 - XDELTA Breakpoint after Update -
In this release a new environment variable "xdelta" was added, which
can be set to ON or OFF, to allow a user to enter the debugger on
power-up. This defaults to OFF. However, on some systems on the FIRST
TIME ONLY after power-on following the firmware update to V5.8-3, the
system may go to XDELTA unexpectedly. This is due to an uninitialized
variable bug in the console. What the user will see is as follows :
OpenVMS PALcode V1.82-27, Digital UNIX PALcode V1.76-22
FF.FE.FD.FC.FB.FA.F9.F8.
xdelta startup
Brk 0 at 000FFC08
000FFC08 ! BPT
SOLUTION:
Problem 1 - System Hang after Update -
In order to avoid this problem, the user is advised to follow the
firmware update procedures from CD, as detailed in the XP1000 Firmware
Release Notes. Here is a brief summary of these methods :
The recommended way for a Windows NT customer to update the firmware
is to have the os_type set to "NT" and to power-up the system to
the AlphaBIOS Menus, and to select "Update AlphaBIOS", with the
Alpha Systems Firmware CD inserted. This will result in the NT-variant
being selected by the update program. The correct way for a UNIX or
VMS customer to update the firmware is to have the os_type set to
"UNIX" or "VMS" and boot the Alpha Systems Firmware CD from the SRM
console prompt, and select the default firmware update bootfile
"XP1000_V58_3.EXE" when prompted to type "enter".
If a user wishes to perform a firmware update from Floppy or Network,
they must be careful to obtain the correct update image (NT or Non-NT)
and to make sure the os_type is set appropriately.
Problem 2 - XDELTA Breakpoint after Update -
If the system DOES go to XDELTA, the user simply needs to type
";P ", and the normal console power-up will resume. On
subsequent initializations or power-cycles, the system will NOT
exhibit this bug (it only happens on the first time through, after
which the variable is created and defaulted to OFF).
000FFC08 ! BPT ;P <---user types ";p "
F7.F6.F5.F3.F2.F1.F0.EF.EE.EC.EB.EA.E9.F4.ED.E8.E7.
E6.E5.E4.
COMPAQ Professional Workstation XP1000
Console V5.8-3 Aug 9 2000 17:44:52
>>>
###############################################################################
My original question was:
>
> I have a serious Problem withh an xp1000.
> Never had any problems with a firmware-update i wanted to that
> for on a xp1000 ( first time ).
> Unfortunately I have the Firmware 5.8 CD put in
> and found later that some things were splitted there for the xp1000
> I run the update and confirmed the Version and did a verify
> which passed also - but after a cycle reset i can't get the srm - prompt
> again ...
> Can someone help me - can I somehow reset the console for to do the
> Update again , or do a downgrade ?
>
> Thanks in advance !
> Rainer
>
> _____________________
> thats what I have done
>
> >>> boot dqa0
>
> ...
>
> The default bootfile for this platform is
>
> [XP1000]XP1000_V58_3.EXE
>
> Hit <RETURN> at the prompt to use the default bootfile.
>
> Bootfile:
>
> OpenVMS PALcode V1.82-27, Digital UNIX PALcode V1.76-22
>
> FF.FE.FD.FC.FB.FA.F9.F8.F7.F6.F5.F3.F2.F1.F0.EF.EE.EC.EB.EA.E9.F4.ED.***
No
> keyboard plugged in ***
> E8.E7.E5.E4.
> COMPAQ Professional Workstation XP1000
> Console (UPD) V5.8-3 Aug 9 2000 17:38:07
> >>>Execute Update Sequence
> Update Script Complete
> (boot pmem:180000)
> bootstrap code read in
> base = 180000, image_start = 0, image_bytes = 800000
> initializing HWRPB at 2000
> initializing page table at 7ffee000
> initializing machine state
> setting affinity to the primary CPU
> jumping to bootstrap code
>
> *** COMPAQ Professional Workstation XP1000 -- Firmware Update V5.8_3 ***
>
> Use HELP or ? for help
>
> Update
> VERIfy
> List
> Show
> DUmp
> VERBose
> NVerbose
> DEbug
> NDebug
> ?
>
> Apu-> show
> *** ROM: SRM
> Loaded Image Checksum 0x7b
> Actual Rom Checksum 0xf3
> *** ROM: ARC/AlphaBIOS
> Loaded Image Checksum 0xd5
> Actual Rom Checksum 0xae
>
>
> Apu-> update
> APU-I ARE YOU READY TO PROGRAM (SRM) ROM DEVICE ? (Y/N) y
> APU-I ERASING (SRM) ROM DEVICE
> APU-I PROGRAMMING (SRM) ROM DEVICE
> APU-I VERIFY LOADED (SRM) ROM IMAGE
> APU-I VERIFY LOADED (SRM) ROM IMAGE DONE
> APU-I PROGRAMMING (SRM) ROM COMPLETED
> APU-I ERASING (ARC/AlphaBIOS) ROM DEVICE
> APU-I PROGRAMMING (ARC/AlphaBIOS) ROM DEVICE
> APU-I VERIFY LOADED (ARC/AlphaBIOS) ROM IMAGE
> APU-I VERIFY LOADED (ARC/AlphaBIOS) ROM IMAGE DONE
> APU-I PROGRAMMING (ARC/AlphaBIOS) ROM COMPLETED
> Apu->
> Apu->
> Apu->
> Apu-> verify
> SRM ROM verify successful
> ARC/AlphaBIOS ROM verify successful
> Apu->
> Apu->
> Apu->
>
> ######## here i 've done the cycle reset ########
>
> OpenVMS PALcode V1.82-27, Digital UNIX PALcode V1.76-22
>
> FF.FE.FD.FC.FB.FA.F9.F8.
> xdelta startup
> Brk 0 at 000FFC08
>
> 000FFC08 ! BPT
> ############ that is the point of 'no return' ######
>
--
__________________________________________________________
Rainer Wolf rainer.wolf_at_rz.uni-ulm.de
Tel: 0731-50-22482 Fax: 0731-50-22471
University of Ulm http://www.uni-ulm.de/urz
University Computing Center Albert-Einstein-Allee 11
AG Basissysteme 89069 Ulm
Received on Fri Jul 20 2001 - 06:59:45 NZST