Quantcast

Mycal's Experimental Homepage Software

Menu
Home
Login

Jump To
  • My Projects
  • Basic Archive
  • Clearlake
  • Archive
  • Articles
  • Links
  • Sandbox
    Search
  • You are at /Projects/Embedded_Enternet/802.11/

    Parent DirectoryMore Usenet Posts


    news:22iapuo8gsi4oa3rnlpebo04o25vo1nv82@4ax.com...
    > Jeremy,
    >
    > I really appreciate your replying to this topic.
    > I've got the tuples decoded, so the easy part is done :)
    >
    > I have one last question, and it goes more to my understanding of the
    > way the book I'm reading explains things
    > (PCMCIA Developers Guide, 3rd Edition)
    >
    > My understanding of what the book says,
    >
    > "To switch to I/O Mode from Attribute Mode:"
    >
    > De-assert REG#, OE#  & WR#  (Make them outputs and set them high)
    > Place 0x3E0 on the Address Lines
    > Place 0x01 on the Data Lines
    > Strobe IOWR
    > Wait 500ms
    > Check -Ready#-      (If asserted, wait more)
    >
    > "...The card is now in I/O mode. "
    >
    >
    > Does this sound basically correct?
    
    No, using IOWR implies you're already in I/O mode. Use WR (i.e. do a write
    to attribute memory at  address 3E0), assuming you've checked the tuples to
    make sure the config reg is at 3E0 (bytes 4-7 of CISTPL_CONFIG, which has
    code 1Ah).
    
    Jeremy Bentham
    Iosoft Ltd.


    Thanks Jeremy, I re-read it and now it makes sence. Now if I could only get it to actualy work... I remember reading an eariler post from you regarding level converters and that you didn't think they were needed. I take it the the mico you used is 5 volt ? The one I'm trying is 3.3 volt and it looks like it can read from the card, but cannot write to it. Using WE# as a write strobe, I cannot get it to accept the 01 at 0x3E0 and switch modes. The card I'm trying is based on the Prisim 2.5 chipset. I thought it was 3.3/5.0, but it doesn't seem to wite at 3.3 But, on the brighter side, as least I can read from the card ! Steve [Samples from my card] 0=1 2=3 4=0 6=0 8=ff a=17 c=4 e=67 10=5a 12=8 14=ff ...... 3dc=ff 3de=ff 3e0=0 3e2=80 [Sample of Decoded Tuples] 0=1a #1A CISTPL_CONFIG 2=7 Link to next Tuple 4=3 Size of field bytes 6=1 Index To Last Entry In Table 8=e0 Configuration Register Base (0x03e0) a=3 c=0 e=0 0=1 0=1d #1D CISTPL_DEVICE_0A (For Attribute Memory) 2=5 Link to next Tuple 4=1 Other Conditions info field 6=67 1100111 (My book does not explain this tuple) 8=5a 1011010 A=8 0001000 C=ff End of Tuple On Sun, 29 Sep 2002 12:25:33 +0100, "Jeremy Bentham" wrote: >No, using IOWR implies you're already in I/O mode. Use WR (i.e. do a write >to attribute memory at address 3E0), assuming you've checked the tuples to >make sure the config reg is at 3E0 (bytes 4-7 of CISTPL_CONFIG, which has >code 1Ah). > >Jeremy Bentham >Iosoft Ltd. >





    Sponsership

    Connect to anyting, anywhere anytime with yoics.







    Last Update at 04-29-2025 1:16 pm
    Copyright 1994-2006 mycal, All Rights Reserved