pci-sandpoint

Hi,

We encountered problems with the pci-sandpoint (ppc). It is unable to
allocate PCI memory space. So no single pci bus is operational.

The ‘pci-sandpoint’ command gives as output: Unable to allocate PCI memory
space: Invalid argument
So the ‘pci’ command has all configurations disabled. Setting the
configuration with

pci_write_config32(inf.BusNumber, inf.DevFunc, PCI_COMMAND_MEM_ENABLE ,
1, &j);

Doesn’t give an error but everything stays disabled.
none of the other pci config space commands work either.

This is normal seen that pci-sandpoint can’t do a memory allocation for
the pci. Why doesn’t pci-sandpoint(the equivalent for pci-bios on a x86
platform) work correctly?

Kevin

Thanks in advance

Hi Kevin.

To clear things up, could you tell me the following:

  1. OS version
  2. Sandpoint hardware version
  3. CPU type
  4. What cards you have inserted in which slots

The Sandpoint hardware is fairly ripe with PCI erratas (they should be
available from Motorola’s web site).

As for devices showing up as ‘disabled’ - it will become enabled once
you initialize it (start the driver).

Thanks,
-Jay.

Kevin Renders wrote:

Hi,

We encountered problems with the pci-sandpoint (ppc). It is unable to
allocate PCI memory space. So no single pci bus is operational.

The ‘pci-sandpoint’ command gives as output: Unable to allocate PCI memory
space: Invalid argument
So the ‘pci’ command has all configurations disabled. Setting the
configuration with

pci_write_config32(inf.BusNumber, inf.DevFunc, PCI_COMMAND_MEM_ENABLE ,
1, &j);

Doesn’t give an error but everything stays disabled.
none of the other pci config space commands work either.

This is normal seen that pci-sandpoint can’t do a memory allocation for
the pci. Why doesn’t pci-sandpoint(the equivalent for pci-bios on a x86
platform) work correctly?

Kevin

Thanks in advance

version
-QNX neutrino v6.3 with a windows host

  • board: Motorola Sandpoint X3 evaluation system (PPCEVAL-SP3 rev
    X.3)
  • processor: MPC7410 PowerPC processor ( PPCEVAL_SP3_7410 Altimus X3)

We got the BSP from qnx.

pci slots

slot 1 : nothing (64)
slot 2 : pci bus analyser (64)
slot 3 : pdrive (for interrupt generation and io)
slot 4 : network card

the pci-sandpoint -vvvvv sais : no dll loaded
i try to start the drivers with pci_attach_device ,… but nothing becomes
enabled. (i also don’t forget to call pci_attach) I can write to the pci
config space but this has to be done by the OS normally.!?


Have a nice day,
Kevin

Jay Greig wrote:

Hi Kevin.

To clear things up, could you tell me the following:

  1. OS version
  2. Sandpoint hardware version
  3. CPU type
  4. What cards you have inserted in which slots

The Sandpoint hardware is fairly ripe with PCI erratas (they should be
available from Motorola’s web site).

As for devices showing up as ‘disabled’ - it will become enabled once
you initialize it (start the driver).

Thanks,
-Jay.

Kevin Renders wrote:
Hi,

We encountered problems with the pci-sandpoint (ppc). It is unable to
allocate PCI memory space. So no single pci bus is operational.

The ‘pci-sandpoint’ command gives as output: Unable to allocate PCI memory
space: Invalid argument
So the ‘pci’ command has all configurations disabled. Setting the
configuration with

pci_write_config32(inf.BusNumber, inf.DevFunc, PCI_COMMAND_MEM_ENABLE ,
1, &j);

Doesn’t give an error but everything stays disabled.
none of the other pci config space commands work either.

This is normal seen that pci-sandpoint can’t do a memory allocation for
the pci. Why doesn’t pci-sandpoint(the equivalent for pci-bios on a x86
platform) work correctly?

Kevin

Thanks in advance

Kevin,

What type of network card is it? Can you please post the whole output
of ‘pci -vv’ and ‘sloginfo’ after running ‘pci-sandpoint -vvv’.

Thanks,
-Jay.

Kevin Renders wrote:

version
-QNX neutrino v6.3 with a windows host

  • board: Motorola Sandpoint X3 evaluation system (PPCEVAL-SP3 rev
    X.3)
  • processor: MPC7410 PowerPC processor ( PPCEVAL_SP3_7410 Altimus X3)

We got the BSP from qnx.

pci slots

slot 1 : nothing (64)
slot 2 : pci bus analyser (64)
slot 3 : pdrive (for interrupt generation and io)
slot 4 : network card

the pci-sandpoint -vvvvv sais : no dll loaded
i try to start the drivers with pci_attach_device ,… but nothing becomes
enabled. (i also don’t forget to call pci_attach) I can write to the pci
config space but this has to be done by the OS normally.!?


Have a nice day,
Kevin

Jay Greig wrote:


Hi Kevin.


To clear things up, could you tell me the following:

\

  1. OS version
  2. Sandpoint hardware version
  3. CPU type
  4. What cards you have inserted in which slots


    The Sandpoint hardware is fairly ripe with PCI erratas (they should be
    available from Motorola’s web site).


    As for devices showing up as ‘disabled’ - it will become enabled once
    you initialize it (start the driver).


    Thanks,
    -Jay.


    Kevin Renders wrote:

Hi,

We encountered problems with the pci-sandpoint (ppc). It is unable to
allocate PCI memory space. So no single pci bus is operational.

The ‘pci-sandpoint’ command gives as output: Unable to allocate PCI memory
space: Invalid argument
So the ‘pci’ command has all configurations disabled. Setting the
configuration with

pci_write_config32(inf.BusNumber, inf.DevFunc, PCI_COMMAND_MEM_ENABLE ,
1, &j);

Doesn’t give an error but everything stays disabled.
none of the other pci config space commands work either.

This is normal seen that pci-sandpoint can’t do a memory allocation for
the pci. Why doesn’t pci-sandpoint(the equivalent for pci-bios on a x86
platform) work correctly?

Kevin

Thanks in advance




\

like you requested:

#sloginfo

Time Sev Major Minor Args

Jan 01 00:00:00 3 17 0 Range check failed (MEM) - Dev 19 - Vend
1011 - Class 20000 - Addr 0 - Size 400
Jan 01 00:01:29 5 17 0 pci_server: Apr 30 2004 18:08:27

Jan 01 00:01:29 2 17 0 pci_server: No dll loaded!


it is actually the pdrive card that needs to work, i don’t care about the
network card but to be complete i will post the whole output of pci -vv so
you can compare. The card that needs to work is the one with vendor 10B5
and device 9060.
Class = Bridge (Host/PCI)
Vendor ID = 1057h, Motorola
Device ID = 4h, MPC107 PCI Bridge/Memory Controller for PPC
PCI index = 0h
Class Codes = 060000h
Revision ID = 12h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 20a0h
Command Reg = 16h
I/O space access disabled
Memory space access enabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate enabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT A
Interrupt line = 0
CPU Interrupt = 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 80 00 00 00 00 20 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 e0 d1 00 fd 40 a3 00 00 00 fc 00 00 00 00
0x80: 00 40 80 c0 00 40 80 c0 00 00 00 00 01 01 01 01
0x90: 3f 7f bf ff 3f 7f bf ff 00 00 00 00 00 00 00 00
0xA0: 03 00 00 32 00 00 00 00 dc 1a 04 ff 00 00 00 04
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 01 00 00 32 00 00 00 00 00 00 03 fd 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: c0 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 e8 75 cc 04 40 04 00 00 40 78 39 32 32 35


Class = Bridge (PCI/ISA)
Vendor ID = 10adh, Symphony Labs
Device ID = 565h, W83C553F/554F ISA Bridge
PCI index = 0h
Class Codes = 060100h
Revision ID = 10h
Bus number = 0
Device number = 1
Function num = 0
Status Reg = 200h
Command Reg = 7h
I/O space access enabled
Memory space access enabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0
CPU Interrupt = 0h
Device Dependent Registers:
0x40: 20 04 00 ef 00 00 78 00 01 00 00 00 00 33 04 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: e0 01 00 80 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 35 0e 01 01 00 00 00 00 00 00 00 00 00 00


Class = Mass Storage (IDE)
Vendor ID = 10adh, Symphony Labs
Device ID = 105h, W83789F Sonata bus master PCI-IDE controlle
PCI index = 0h
Class Codes = 01018fh
Revision ID = 5h
Bus number = 0
Device number = 1
Function num = 1
Status Reg = 280h
Command Reg = 1h
I/O space access enabled
Memory space access disabled
Bus Master disabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 8h un-cacheable
PCI IO Address = 1f0h length 8 enabled
CPU IO Address = fe0001f0h
PCI IO Address = 3f4h length 4 enabled
CPU IO Address = fe0003f4h
PCI IO Address = 170h length 8 enabled
CPU IO Address = fe000170h
PCI IO Address = 374h length 4 enabled
CPU IO Address = fe000374h
PCI IO Address = 8f0400h length 16 enabled
CPU IO Address = fe8f0400h
PCI IO Address = 0h length 16 enabled
Max Lat = 40ns
Min Gnt = 2ns
PCI Int Pin = INT A
Interrupt line = 14
CPU Interrupt = eh
Device Dependent Registers:
0x40: b3 00 ff 00 09 09 00 00 09 09 00 00 09 09 00 00
0x50: 09 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


Class = Bridge (Unknown)
Vendor ID = 10b5h, PLX Technology
Device ID = 9060h, PCI9060 PCI Bus Master Interface Chip
PCI index = 0h
Class Codes = 068000h
Revision ID = 3h
Bus number = 0
Device number = 5
Function num = 0
Status Reg = 280h
Command Reg = 0h
I/O space access disabled
Memory space access disabled
Bus Master disabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT A
Interrupt line = 0
CPU Interrupt = 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


Class = Network (Ethernet)
Vendor ID = 1011h, Digital Equipment Corporation
Device ID = 19h, DC21142/3 PCI/CardBus 10/100 Mbit Ethernet Ctlr
PCI index = 0h
Class Codes = 020000h
Revision ID = 41h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 280h
Command Reg = 0h
I/O space access disabled
Memory space access disabled
Bus Master disabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
PCI IO Address = 0h length 128 disabled
Max Lat = 40ns
Min Gnt = 20ns
PCI Int Pin = INT A
Interrupt line = 80
CPU Interrupt = 50h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


Thanks

Kevin Renders
Dedicated-systems
Jay Greig wrote:

Kevin,

What type of network card is it? Can you please post the whole output
of ‘pci -vv’ and ‘sloginfo’ after running ‘pci-sandpoint -vvv’.

Thanks,
-Jay.

Kevin Renders wrote:
version
-QNX neutrino v6.3 with a windows host

  • board: Motorola Sandpoint X3 evaluation system (PPCEVAL-SP3 rev
    X.3)
  • processor: MPC7410 PowerPC processor ( PPCEVAL_SP3_7410 Altimus X3)

We got the BSP from qnx.

pci slots

slot 1 : nothing (64)
slot 2 : pci bus analyser (64)
slot 3 : pdrive (for interrupt generation and io)
slot 4 : network card

the pci-sandpoint -vvvvv sais : no dll loaded
i try to start the drivers with pci_attach_device ,… but nothing becomes
enabled. (i also don’t forget to call pci_attach) I can write to the pci
config space but this has to be done by the OS normally.!?


Have a nice day,
Kevin

Jay Greig wrote:


Hi Kevin.


To clear things up, could you tell me the following:

\

  1. OS version
  2. Sandpoint hardware version
  3. CPU type
  4. What cards you have inserted in which slots


    The Sandpoint hardware is fairly ripe with PCI erratas (they should be
    available from Motorola’s web site).


    As for devices showing up as ‘disabled’ - it will become enabled once
    you initialize it (start the driver).


    Thanks,
    -Jay.


    Kevin Renders wrote:

Hi,

We encountered problems with the pci-sandpoint (ppc). It is unable to
allocate PCI memory space. So no single pci bus is operational.

The ‘pci-sandpoint’ command gives as output: Unable to allocate PCI memory
space: Invalid argument
So the ‘pci’ command has all configurations disabled. Setting the
configuration with

pci_write_config32(inf.BusNumber, inf.DevFunc, PCI_COMMAND_MEM_ENABLE ,
1, &j);

Doesn’t give an error but everything stays disabled.
none of the other pci config space commands work either.

This is normal seen that pci-sandpoint can’t do a memory allocation for
the pci. Why doesn’t pci-sandpoint(the equivalent for pci-bios on a x86
platform) work correctly?

Kevin

Thanks in advance




\