Sign in

username:

password:



Not a member?

Search Comp.Arch.Embedded



Search tips

embedded by Keywords

68HC11 | 68HC12 | 8051 | 8052 | ARM | ARM7 | Asic | AT91 | AT91RM9200 | Atmel | AVR | AVRStudio | Bootloader | CFP | CompactFlash | Cygnal | Cypress | Dataflash | DSP | eCos | EEPROM | Embedded Linux | Emulator | Endian | Ethernet | Firewire | FPGA | Freescale | GCC | GNUARM | GSM | H8 | HDLC | I2C | Infineon | Interrupts | Java | JTAG | LCD | LED | LPC2000 | MCU | Microchip | MMC | MPLAB | MSP430 | PC104 | PCB | PCI | PCMCIA | PowerPC | Rabbit | RS232 | RS485 | RTOS | SBC | SDRAM | Sensor | SPI | STK500 | UART | UML | USART | USB | Verilog | VHDL | VxWorks | Xilinx

Discussion Groups

Discussion Groups | Comp.Arch.Embedded | PCMCIA Problem

There are 2 messages in this thread.

You are currently looking at messages 0 to 2.

PCMCIA Problem - Harry - 01:47 19-10-07



Hi all,

We have interfaced the PCMCIA bus to Intel PXA270  processor.
We have written our own driver for it and runs linux-2.6.15.2.
When i insert the PCMCIA device,WLAN card ,when the system is is
booted up for the first time and card manager application is
running,it shows the details of the card like the manufacturer
details.But if i unplug it and insert it ,with card manager still
running,it shows as anonymous memory.

Does anybody experienced same problem and solved it?

Re: PCMCIA Problem - husterk - 09:24 20-10-07

On Oct 19, 1:47 am, Harry <geharipras...@gmail.com> wrote:
> Hi all,
>
> We have interfaced the PCMCIA bus to Intel PXA270  processor.
> We have written our own driver for it and runs linux-2.6.15.2.
> When i insert the PCMCIA device,WLAN card ,when the system is is
> booted up for the first time and card manager application is
> running,it shows the details of the card like the manufacturer
> details.But if i unplug it and insert it ,with card manager still
> running,it shows as anonymous memory.
>
> Does anybody experienced same problem and solved it?

I have seen something similar to this... We solved this by always
resetting the PCI controller upon disconnect of the PCI device. This
is kind of a crowbar approach but it worked for our system. We were
able to do this because we would only ever have a single PCI device
connected to our system. We were using an ARM9 running the ThreadX OS
with a custom Mini-PCI driver for an 802.11g wireless card.

Hope this helps.

Keith
http://www.doubleblackdesign.com