Prev: USB device access via DeviceIoControl and WriteFile / ReadFile
Next: WinXP x64 STREAM.SYS 0x3b Crash
From: "Paul Harrison" <Paul on 17 Aug 2005 07:16
Can anyone confirm whether the PcCardConfig (M) option in the ConfigOverride
section of an inf file for a PCMCIA card running on a cardbus (Texas
Instruments PCI-1510) controller actually does anything under WinXP SP2. I am
trying to enable 16 bit memory access to common memory on the card. I have
checked the memory acess to the device using a logic analyzer, and the 32 bit
memory requests are being broken down into 8 bit accesses. I have tested that
the override section is actually being processed by adding extra resource
requests, which are dully passed in to the driver, and also by adding an
invalid option to the PcCardConfig line which resulted in the driver failing
to install with an invalid inf section error. In clonclusion I know that the
inf file override section is valid and being precessed.
Has anyone managed to get 16 bit memory access to a PCMCIA card to work
succesfully undr Win XP SP2. The hardware has been tested and succesfully
produces 16 bit memory access under WinCE.


From: Pavel A. on 18 Aug 2005 04:51
Try the !exca windbg command to check the socket config registers.
Is the memory width set correctly?

--PA

"Paul Harrison" wrote:
> Can anyone confirm whether the PcCardConfig (M) option in the ConfigOverride
> section of an inf file for a PCMCIA card running on a cardbus (Texas
> Instruments PCI-1510) controller actually does anything under WinXP SP2. I am
> trying to enable 16 bit memory access to common memory on the card. I have
> checked the memory acess to the device using a logic analyzer, and the 32 bit
> memory requests are being broken down into 8 bit accesses. I have tested that
> the override section is actually being processed by adding extra resource
> requests, which are dully passed in to the driver, and also by adding an
> invalid option to the PcCardConfig line which resulted in the driver failing
> to install with an invalid inf section error. In clonclusion I know that the
> inf file override section is valid and being precessed.
> Has anyone managed to get 16 bit memory access to a PCMCIA card to work
> succesfully undr Win XP SP2. The hardware has been tested and succesfully
> produces 16 bit memory access under WinCE.
>
>
From: Paul Harrison on 18 Aug 2005 05:46
Thanks I will look into that.

Paul


"Pavel A." wrote:

> Try the !exca windbg command to check the socket config registers.
> Is the memory width set correctly?
>
> --PA
>
> "Paul Harrison" wrote:
> > Can anyone confirm whether the PcCardConfig (M) option in the ConfigOverride
> > section of an inf file for a PCMCIA card running on a cardbus (Texas
> > Instruments PCI-1510) controller actually does anything under WinXP SP2. I am
> > trying to enable 16 bit memory access to common memory on the card. I have
> > checked the memory acess to the device using a logic analyzer, and the 32 bit
> > memory requests are being broken down into 8 bit accesses. I have tested that
> > the override section is actually being processed by adding extra resource
> > requests, which are dully passed in to the driver, and also by adding an
> > invalid option to the PcCardConfig line which resulted in the driver failing
> > to install with an invalid inf section error. In clonclusion I know that the
> > inf file override section is valid and being precessed.
> > Has anyone managed to get 16 bit memory access to a PCMCIA card to work
> > succesfully undr Win XP SP2. The hardware has been tested and succesfully
> > produces 16 bit memory access under WinCE.
> >
> >
From: Paul Harrison on 18 Aug 2005 11:05

I have examined the ExCA regsiters with a utility supllied by TI for there
controllers, and the ExCA Register 11h is set to 0Bh. If I have read this
correctly we are running with a memory window width of 8 bits as bit 7 of
this regsiter should be set for 16 bit memory accesses. Can anyone help me as
to why we are running in 8 bit memory access mode. Could the CIS
configuartion affect this. I should mention that the PCMCIA card is a
multifunction device.


"Paul Harrison" wrote:

> Thanks I will look into that.
>
> Paul
>
>
> "Pavel A." wrote:
>
> > Try the !exca windbg command to check the socket config registers.
> > Is the memory width set correctly?
> >
> > --PA
> >
> > "Paul Harrison" wrote:
> > > Can anyone confirm whether the PcCardConfig (M) option in the ConfigOverride
> > > section of an inf file for a PCMCIA card running on a cardbus (Texas
> > > Instruments PCI-1510) controller actually does anything under WinXP SP2. I am
> > > trying to enable 16 bit memory access to common memory on the card. I have
> > > checked the memory acess to the device using a logic analyzer, and the 32 bit
> > > memory requests are being broken down into 8 bit accesses. I have tested that
> > > the override section is actually being processed by adding extra resource
> > > requests, which are dully passed in to the driver, and also by adding an
> > > invalid option to the PcCardConfig line which resulted in the driver failing
> > > to install with an invalid inf section error. In clonclusion I know that the
> > > inf file override section is valid and being precessed.
> > > Has anyone managed to get 16 bit memory access to a PCMCIA card to work
> > > succesfully undr Win XP SP2. The hardware has been tested and succesfully
> > > produces 16 bit memory access under WinCE.
> > >
> > >
From: Pavel A. on 18 Aug 2005 15:38
OK. Now, can you flip this bit in a kernel debugger and
see if you get 16-bit cycles?
Set a breakpoint in your driver just before it starts to access the card.

--PA

"Paul Harrison" wrote:
>
> I have examined the ExCA regsiters with a utility supllied by TI for there
> controllers, and the ExCA Register 11h is set to 0Bh. If I have read this
> correctly we are running with a memory window width of 8 bits as bit 7 of
> this regsiter should be set for 16 bit memory accesses. Can anyone help me as
> to why we are running in 8 bit memory access mode. Could the CIS
> configuartion affect this. I should mention that the PCMCIA card is a
> multifunction device.
>
>
> "Paul Harrison" wrote:
>
> > Thanks I will look into that.
> >
> > Paul
> >
> >
> > "Pavel A." wrote:
> >
> > > Try the !exca windbg command to check the socket config registers.
> > > Is the memory width set correctly?
> > >
> > > --PA
> > >
> > > "Paul Harrison" wrote:
> > > > Can anyone confirm whether the PcCardConfig (M) option in the ConfigOverride
> > > > section of an inf file for a PCMCIA card running on a cardbus (Texas
> > > > Instruments PCI-1510) controller actually does anything under WinXP SP2. I am
> > > > trying to enable 16 bit memory access to common memory on the card. I have
> > > > checked the memory acess to the device using a logic analyzer, and the 32 bit
> > > > memory requests are being broken down into 8 bit accesses. I have tested that
> > > > the override section is actually being processed by adding extra resource
> > > > requests, which are dully passed in to the driver, and also by adding an
> > > > invalid option to the PcCardConfig line which resulted in the driver failing
> > > > to install with an invalid inf section error. In clonclusion I know that the
> > > > inf file override section is valid and being precessed.
> > > > Has anyone managed to get 16 bit memory access to a PCMCIA card to work
> > > > succesfully undr Win XP SP2. The hardware has been tested and succesfully
> > > > produces 16 bit memory access under WinCE.
> > > >
> > > >
 |  Next  |  Last
Pages: 1 2
Prev: USB device access via DeviceIoControl and WriteFile / ReadFile
Next: WinXP x64 STREAM.SYS 0x3b Crash