Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!haven!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcrware!kim
From: kim@mcrware.UUCP (Kim Kempf)
Newsgroups: comp.os.os9
Subject: Re: Ethernet Support Package .. hardware incompatabilities!
Keywords: alarms, signal number
Message-ID: <948@mcrware.UUCP>
Date: 5 Feb 89 16:44:29 GMT
References: <429@infovax.lan.informatik.tu-muenchen.dbp.de> <1233@mmm.UUCP>
Reply-To: kim@mcrware.UUCP (Kim Kempf)
Distribution: usa
Organization: Microware Systems Corp., Des Moines, Iowa
Lines: 23

In article <1233@mmm.UUCP> manning@mmm.UUCP (Arthur T. Manning) writes:
>I finally got Mizar's 8210 RAM board to at least allow the system to boot
>with Os9 2.2 after replacing the rb7400 module.  Now the system starts
>getting CRC  errors (232) when  I start using the extra memory!  This does
>not happen when the ethernet software is not running, so I  would  suspect
>it has some problem   with  the 8210.
>
There are a number of likely causes of this problem:

	- Multiple boards responding to the same address.  The *entire* address
	range of the memory the new board is providing must not overlap anything
	else.  Otherwise just this sort of problem will occur as both the RAM
	and something respond causing sporadic operation and random data values.

	- One should get from the mfgr. of the hardware the local and VMEbus
	maps of the hardware supplied so valid spare address ranges can be
	identified.

	- Custom user-written drivers are always suspect.

Microware has tested this exact configuration in house and we have a number
of other customers who have no problems with Unibridge on off the shelf
Mizar configurations.