[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 49.910::kav30

Title:VAX on VMEbus: KAV30
Notice:Could have been as fast as 68K but its a VAX!
Moderator:CSSVMS::KAV30_SUPP
Created:Thu Apr 18 1991
Last Modified:Fri Aug 02 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:159
Total number of notes:645

155.0. "KAV30-AD/AC REV C04/C03 PROM boot problems" by ZYDECO::REDDY () Mon Aug 07 1995 17:12


Steve Rodkey, of Texas Insturments, is having problems with his PROMed 
applications.  

They did not have any problems when they were using KAV30 Rev B board with 
RTVAX module REV C.  

Since those boards are not available, they had to buy KAV30-AD Rev C03 and
KAV30-AC Rev C03 boards.  The RTVAX on these is Rev D01.  When they use either
of the boards, prom their application, and boot PRB1, they see ".. 84 fail" on
the console.  They reset the board and boot again and this time on the console
they see, "e...4" and then it hangs.  On the LED display, they see a 4 on the
top and F on the bootom display.  The PROM chips on the board has 23-264-E800A02
and 23-263-E800A02.  The prom chips they ae using is a TI 27C240-10.  Steve
feels that the CPU is not reading the correct data.  He used the console to
examine the boot blocks and said that they are different on the board that
works and the new rev board that does not work.  After the failure, when he
ran the self test, whenhe issued, T B, he got back ? 30 UNXINT and for T D, he
got a ?40 no such device.

Are there any problems with using the boards that the customer is using?  They
are planning to use the KAV30s for another two years.  Since they cannot buy
earlier rev level boards, it is very important for them to get the appliations
PROMed on the newer KAV30s.

Thanks,

Sumithra
T.RTitleUserPersonal
Name		DateLines
155.1no known problems ...EICMFG::KAV30_SUPPMon Aug 07 1995 18:1616
    Hi,
    
    the customer has to use the new EPROM's for building theire own 'new'
    EPROM's, that is: copy the 'standard' content of the EPROM set 263/264
    to the new EPROM and then add theire own code as described in the docu.
    Booting a rev Cxx KAV30 with an old EPROM will not work...
    
    There are no known problems with the new boards, nevertheless several
    customers reported problems when doing new EPROM's - the solution:
    strictly keep to the procedures outlined in the HW manual & Release
    Notes.
    
    rgds,
    
    	Thomas
155.2Followed the instructions in the docsZYDECO::REDDYMon Aug 07 1995 19:1316
    
    Thomas,
    
    The customer says that he is following the instructions given in the
    docs exactly.  They are using 1 meg prom chips.  They have connected
    jumpers J1 and J3.  What is J2 used for?  He also said that when
    he examines the boot block address 20098000 from the console, he
    sees E7000018.  He said that it should be E7880118 (which is what he
    sees when he takes the prom back and checks it and it is also the value
    on the proms that are working with the earlier rev).
    
    They found out the hard way that booting a rev Cxx KAV30 with an old
    EPROM will not work.
    
    Sumithra
155.3... ask the customer to read ...EICMFG::KAV30_SUPPTue Aug 08 1995 12:1324
    Sumithra,
    
    >> What is J2 used for ?
    
    KAV30 Hardware Installation and User's Information (delivered with
    every single board..), p 2-6:
    "The KAV30 also contains jumper posts that are reserved for Digital.
    These jumper posts are J2 (sic!), J4 and J40."
    
    >> They found out the hard way ...
    
    KAV30 Hardware release notes (delivered with every single board),
    Section "Important information about the Eproms"
    " If for any circumstances you have different revisions of the T6010-XX
    module at your site, do not interchange the EPROM set's, always check
    for compliance as shown above (EPROM comparison table)."
    
    I'll check for the code in the boot block and will come back to you
    with my findings ...
    
    rgds,
    
    	Thomas
155.4strange numbers...EICMFG::KAV30_SUPPSun Aug 13 1995 18:4523
    Hi Sumithra,
    
    we do not understand your customers problem ...
    
    Here are the facts:
    
    EPROM starts at 2020 0000, the lowest 512k are 'double mapped' to the
    rtVAX300 ROM space, which starts at 2008 0000. Adding 96k to that you
    get 2021 8000 for the 'legal' start address and 2009 8000 if you look
    at the 'copy'. The content of 2021 8000 is 'E700 0018' for all EPROM's
    of KAV30 rev Bx and Cx. If you examine this address on a 'promer' you
    have to calculate the offset again, since these EPROMs are accessed in
    bytes you need to divide the 96k address by 4 (4 bytes per longword)
    which gives you C000 Hex. At this address you can see E700 for the odd
    and 0018 for the even EPROM... anything else is garbage ...
    
    I'm sorry, but the only explanation we have is that something is wrong
    with the customers EPROM's.
    
    best regards,
    
    Thomas
155.5ZYDECO::REDDYTue Aug 15 1995 19:328
    
    Thomas,
    
    I will check with the customer.  He is very sure, he has EPROMed it
    correctly.
    
    Sumithra
155.6Can't explain, but it is working nowZYDECO::REDDYTue Aug 22 1995 22:5114
    
    Thomas,
    
    The information provided in .4 was helpful.  The customer blasted some
    new EPROMS and this time it worked.  He said that he did not do
    anything different.  He feels that the EPROMs that he used might have
    been defective.  He said that in a few months they will be blasting a
    new batch of EPROMS and if at that time they run into any problems, we
    will look into this again.
    
    Thanks for the help.
    
    Sumithra