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 DirectoryUsenet messages - PRISM 802.11 TxExc


    Mike Meeuwsen  wrote
    
    > I've been working on an embedded 802.11 project, similar to some I've
    > seen on this group, interfacing a PCMCIA card to a 16-bit micro. Its
    > been going pretty well, and I am able to read and write to the card (A
    > Linksys WPC11v3, based on PRISM 2/3 chipset).  I've successfully put the
    > card in I/O mode, enabled the MAC port 0, and associated with my AP.  I
    > have evidence of this in the AP log, as well as by checking the
    > connection status in the card.
    >
    > However, when I attempt to transmit a packet on port zero (which should
    > be enabled as per above): in this case, a prebuilt UDP packet to a
    > broadcast MAC address, the card throws a TxExc error of Discon.  The
    > documentation indicates that this means the port is not connected.  This
    > doesn't make sense to me, since the card is still reporting a
    > connection, and unless I've missed them, I haven't recived any info
    > events saying I've diconnected.  I have noticed Rx events, but I haven't
    > implemented the code to process the packets.
    >
    > One other thing I've noticed, in the AP log, there is periodicaly an
    > entry for "association expiration" with the cards MAC addr.  This does
    > not happen consistently.  I am attempting to transmit the packet almost
    > directly after enabling the port (only a few status reads and packet
    > construction in between).
    >
    > I'm out of ideas on this one.  Any advice would be appreciated.
    
    I suspect you've missed out some of the initialisation steps, e.g. system
    scale, basic rate, supported rates, etc... but I can't replicate chunks of
    our PICmicro WLAN source code package here.
    
    Also, if there are errors in your FID/RID handling (e.g. information vs.
    configuration record handling), the PRISM won't necessarily generate an
    error reponse, and may show its displeasure in strange ways.
    
    Jeremy Bentham
    Iosoft Ltd.
    www.iosoft.co.uk
    





    Sponsership

    Connect to anyting, anywhere anytime with yoics.







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