[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] pcmcia and 802.11 cards
Since I'm doing this project in my spare time, I was concentrating on the
ease of implementation. I have not experienced difficulty in obtaining 16bit
cards, but Im sure that their availability will decrease over the next 5
years. This gives me plenty of time.
As I am doing this for fun, the 16bit interface is quick to implement. I
have the design on paper, and plan to enter it tonight as a schematic in
ise. I plan to stick on a codec and usb, so I have a bit more work to do.
Maybe I'll do a 32bit interface next.
You are correct about the timeout. I have timeouts suppressed. Anyway, my
opb clock is 50mhz, leaving a 320ns max access time if bus timeouts we left
on. Since its all just code, its easily changed as needed.
Im using Protel for schematic and PCB (do to the need to use it at my last
job). I do have a copy of Orcad, but have not learned it yet. I thing I can
import/export to/from orcad.
Rich
-----Original Message-----
From: owner-microblaze-uclinux@itee.uq.edu.au
[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of aurash
Sent: Sunday, October 24, 2004 1:49 AM
To: microblaze-uclinux@itee.uq.edu.au
Subject: Re: [microblaze-uclinux] pcmcia and 802.11 cards
Hi Rich,
Richard Klosinski wrote:
>I have converted my design to a ise project, and am now working out of xps.
>I have created a basic opb interface that ports the address, data, rnw,
>and cs lines.
>
are you familiar with the OPB? you need to ack each transfer in 16 opb clks
maximum, or assert timeout supress (if I remember correctly) it not only a
matter of bringing the signals outside (the opb_gpio is a good starting
point) or the ipif (in EDK)
>
>Im using the cirrus 6710 as a model for controls that are needed. I don't
>plan to reproduce the timing, addressing, chip info, and other mapping
>registers. It will have interrupt and power control.
>
>I assume that a custom pcmcia driver will be needed for linux, but
hopefully
>I can hack an existing one to achieve my results.
>
I think is not a big issue to modify an existing driver
>
>Most of the signals are brain-dead to reproduce, except for a few: CE1n,
>CE2n, REGn. I plan to always transfer 16bit data, so CE1 and CE2 will
follow
>each other. The REGn signal is harder to understand. I don't understand
>(yet) about how the bus gets into 'Memory Card' and 'I/O card' modes. Is it
>set by the driver through a register in the interface chip?
>
>
No clue.
>Anyway, nearly done with my interface, except for the Reg pin. Researching
>PCMCIA ethernet chip, I found most don't use any address line above A10.
>
Because most of them are working in I/O mode
>This is also true for the prism 2,2.5,3 wlan chipsets as well as smcs
>chipsets. This will save me IO pins.
>
Correct.
>
>As I have outgrown my spartan 3 demo pcb, I might do a quick board with a
>sp3x1000 in the 256pin bga package. It will leave me with 700k gates free
>and 40i/o pins. I think I'll stick on a ac97 codec and usb chip (i/o pins
>free going to 0!).
>
Just a quick note, I was strugling to find PCMCIA wlan cards (old legacy
16bit mode) and are quite hard to find ...
why not going dirrectly for 32bit mode and 802.11g (if anyway you plan a
sp3-1000 256pin)
btw what PCB program are you using ? I'm using Orcad maybe we can share
some libraries ...
Aurash
>
>Rich
>
>-----Original Message-----
>From: owner-microblaze-uclinux@itee.uq.edu.au
>[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of aurash
>Sent: Saturday, October 23, 2004 2:06 AM
>To: microblaze-uclinux@itee.uq.edu.au
>Subject: Re: [microblaze-uclinux] pcmcia and 802.11 cards
>
>Rich,
>
>Se my comments inline
>
>Richard Klosinski wrote:
>
>
>
>>I'd like to start designing a pcmcia interface for my
>>microblaze/ucLinux system, and would like to know if anyone has had
>>experience making this connection. I have a few questions:
>>
>>
>>
>
>
>
>>1) I noticed that most pcmcia card side chipsets do now use address
>>lines a11:24. Can someone confirm this?
>>
>>
>>
>>
>I'm not an expert in PCs but ont the legacy PC you can have only 1024 I/O
>ports (10 bit address) which means that the card will work in memory
adresss
>space (memory like interface) - it will be interesting to find out if the
>PCMCIA doesn't have a "dedicated" or recomanded address space, anyway on a
>fpga doesn't really matter (you can play as you want) but will be nice to
>try to stay in the same range for driver compatibility perspective
>
>
>
>>2) Obviously, the microblaze is 32 bits, so I plan to steer the 16bit
>>data to the upper/lower words depending on the lsb (a31 in the microblaze
>>
>>
>world).
>
>
>>Does this sound like it would work?
>>
>>
>>
>>
>yes will work nice, the only think is when you read you need muxes dor the
>data (to steer 16 bits) exactly as you described, and you need to keep the
>data lines in ZERO when the card is not selected (the opb bus has a ORed
>tree structure on the incoming data path) and another thing is that you
need
>to generate an acknoledge on the OPB for each transaction request (simple
>state machine) - it will be nice to be capable to setup the latency for
this
>ACK in order to deal with low speed peripherals.
>
>
>
>>Anyone have words of en/dis-couragement before I start...
>>
>>
>>
>Go for it. WILL WORK.
>I will publish on my website next week, a simple OPB_2_ISA attacment that
>I'm using right now for my 10Mb ethernet chip (CS8900) this can be a good
>start to develop your attachment. I'm very interested to attach pcmcia card
>(802.11b) to my system as well, so we can share the pain
>
>Aurash
>
>
>
>>Thanks
>>Rich.
>>
>>PS. If anyone is interested in the port to the nuhorizon sp3 demo
>>board, I can tar the new files with instructions on how to re-assemble
>>them. Sorry, Im not to savvy in the linux world of patches. The card is
>>now 100% functional (sdram, flash, 2 comm ports, and led to blink a
>>
>>
>heartbeat).
>
>
>>___________________________
>>microblaze-uclinux mailing list
>>microblaze-uclinux@itee.uq.edu.au
>>Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>>Mailing List Archive :
>>http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>>
>>
>>
>>
>>
>>
>
>
>___________________________
>microblaze-uclinux mailing list
>microblaze-uclinux@itee.uq.edu.au
>Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>Mailing List Archive :
>http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
>___________________________
>microblaze-uclinux mailing list
>microblaze-uclinux@itee.uq.edu.au
>Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
>
>
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/