Example 2: Mvme3600 Series Board Acts Differently - Motorola MVME2600 Series Reference Manual

Universe (VMEbus to PCI) Chip

Example 2: MVME3600 Series Board Acts Differently

4
4-18
Repeat portions of the earlier example on an MVME3600 series board.
This board had not previously been seen to hang upon PCI reset. This
particular board had customized values for the LSI0 setup parameters.
The Universe register init code is still disabled, and must be manually
called. The PCI init code is enabled, so the Universe PCI memory space
requirement defined by its Configuration Space register at offset 0x10 is
being accommodated and enabled during PCI probing. PCI probe list
d,c,e,f,10
1. After a P/U reset, before the init code has written the registers, the
LSI0 register settings are:
CTL BS
800000
2. Run the init code and the LSI0 registers become:
CTL BS
80821000 3000000 300a000 4d000000
3. After a bye, before the init code has run:
CTL BS
80820000
Therefore the PCI reset caused the following changes in the LSI0
image:
from supervisor to user
from PCI space base address 300.0000 to 0
from PCI space size of a000 to size of 0
from a VME base address of 5000.0000 to 0
This explains why it has never been a problem on this particular
MVME360x. The fact that the PCI base and PCI bound registers are
both 0 makes the effective size of the image 0 bytes. Therefore this
"enabled" image will never utilize any PCI address space.
BD
0 0
BD
BD
0 0
TO
0
TO
TO
0