Networking Forums

Networking Forums > Wireless Networking > Wireless Internet > PRISMII - HFA384x - Wlan : Transmit problem

Reply
Thread Tools Display Modes

PRISMII - HFA384x - Wlan : Transmit problem

 
 
Eran
Guest
Posts: n/a

 
      07-16-2003, 02:05 PM
I have succesfulLy initiated and enabled the MAC. I'm able to
associate with the AP: The MAC status (RID FD40) for MAC port #0
reproted as "Connected to ESS"(0x0004), The BSSID (RID FD42) returns
the correct AP mac address and RX packets are recieved correctly. The
problem is with transmit :
1. I'm allocating a buffer for TX with Reclaim bit set.
2. Im getting Alloc event interrupt and reading the FID for TX from
AllocFID register.
3. I'm transmitting a packet using the above FID. The control frame :
TxContrl field = 6 (MAC Port 0, 802.3 format, TxEx + TxOK set); the
Control frame is transmitted using offset=0 and len=14. The 802.3
Header info : destAddr = 0xffffffffffff(broadcast), SrcAddr =
OwnMACAddr value, and length of the data section. The header info+Data
are transmitted using offset 46 and len = DataLen+14.
All is done according to the documentation. When transmitting, I get
TxExc event interrupt, and "Discon"(0x0004) bit is set in the Status
field.
Whats wrong with my TX procedure ?
 
Reply With Quote
 
 
 
 
voldermort
Guest
Posts: n/a

 
      07-16-2003, 02:49 PM
Anyone got a degree in gobbledegook?


"Eran" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> I have succesfulLy initiated and enabled the MAC. I'm able to
> associate with the AP: The MAC status (RID FD40) for MAC port #0
> reproted as "Connected to ESS"(0x0004), The BSSID (RID FD42) returns
> the correct AP mac address and RX packets are recieved correctly. The
> problem is with transmit :
> 1. I'm allocating a buffer for TX with Reclaim bit set.
> 2. Im getting Alloc event interrupt and reading the FID for TX from
> AllocFID register.
> 3. I'm transmitting a packet using the above FID. The control frame :
> TxContrl field = 6 (MAC Port 0, 802.3 format, TxEx + TxOK set); the
> Control frame is transmitted using offset=0 and len=14. The 802.3
> Header info : destAddr = 0xffffffffffff(broadcast), SrcAddr =
> OwnMACAddr value, and length of the data section. The header info+Data
> are transmitted using offset 46 and len = DataLen+14.
> All is done according to the documentation. When transmitting, I get
> TxExc event interrupt, and "Discon"(0x0004) bit is set in the Status
> field.
> Whats wrong with my TX procedure ?



 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem using IAS for WLAN (with WEP) David Windows Networking 2 08-25-2005 10:24 AM
Mandrake Linux on dell laptop with PrismII 2.5 USB 802.11b port cannotjoin the ad-hoc LAN. Steven Wu Linux Networking 0 01-14-2005 03:47 AM
Ad-hoc WLAN-problem Triton Wireless Networks 3 12-24-2004 10:45 PM
WLAN Problem oklier Windows Networking 0 08-05-2003 11:17 PM
Need HFA384x driver for windows Andre Piancastelli Wireless Internet 0 07-09-2003 02:20 AM



1 2 3 4 5 6 7 8 9 10 11