Proxim Harmony 802.11b

Colin Worth cworth at buphy.bu.edu
Sun Jul 4 17:41:43 EDT 2004


Hello,

   I am trying to set up a Proxim Harmony 802.11b PCMCIA card.  There was 
a previous message about this card, saying to flash it with a new 
PDA and a new CIS.  But I am not sure this is correct for my case, because 
the card identifies itself with MANFID

0x126,0x8000,

instead of 0x126,0x0002, as it listed in the previous message.  

Maybe this is just part of the screwed up CIS (?).  What is the correct 
MANFID?  Does it matter?

Also, the back of the card has a sticker on it that says:
Vcc=3.3, MAC=xxxxxx-xxxxxx, but hostap seems to identify it as a 5.0 volt 
card.

Here is the output with options: ignore_cis_vcc=1:

(I also tried no_primary=1 and that did not change the output):

Jul  4 16:58:30 debian kernel: hostap_crypt: registered algorithm 'NULL'
Jul  4 16:58:30 debian kernel: hostap_cs: 0.2.2 - 2004-05-31 (Jouni 
Malinen <jkm
aline at cc.hut.fi>)
Jul  4 16:58:31 debian kernel: hostap_cs: setting Vcc=33 (constant)
Jul  4 16:58:31 debian kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Jul  4 16:58:31 debian kernel: hostap_cs: ignoring Vcc=50 (from config)
*** I put in a few extra messages about tuples ***
Jul  4 16:58:31 debian kernel: About to get first tuple for 
CISTPL_CFTABLE_ENTRY
Jul  4 16:58:31 debian kernel: Got it
Jul  4 16:58:31 debian kernel: Executing CISTPL_CFTABLE_ENTRY tuple loop 
in host
ap_cs
Jul  4 16:58:31 debian kernel: it's the default tuple
Jul  4 16:58:31 debian kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Jul  4 16:58:31 debian kernel: vcc.present, may ignore
Jul  4 16:58:31 debian kernel: enabled conf.attributes |=CONF_ENABLE_IRQ
Jul  4 16:58:31 debian kernel: IO window settings: cfg->io.nwin=1 
dflt.io.nwin=1
Jul  4 16:58:31 debian kernel: io->flags = 0x0046, io.base=0x0000, len=64
Jul  4 16:58:31 debian kernel: IO space reserved
Jul  4 16:58:31 debian kernel: hostap_cs: Registered netdevice wifi0
Jul  4 16:58:31 debian kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io 
0x0100-
0x013f
Jul  4 16:58:31 debian kernel: prism2_hw_init: initialized in 90 ms
*** Attempts to get PDA: ***
Jul  4 16:58:31 debian kernel: wifi0: trying to read PDA from 0x007f0002
Jul  4 16:58:31 debian kernel: About to unenable_aux_port
Jul  4 16:58:31 debian kernel: prism2_enable_aux_port: was not enabled!?
Jul  4 16:58:31 debian kernel: prism2_enable_aux_port(0) timed out
Jul  4 16:58:31 debian kernel: wifi0: trying to read PDA from 0x007f0000
Jul  4 16:58:31 debian kernel: prism2_enable_aux_port: was not enabled!?
Jul  4 16:58:31 debian kernel: prism2_enable_aux_port(0) timed out
Jul  4 16:58:31 debian kernel: wifi0: trying to read PDA from 0x003f0000
Jul  4 16:58:31 debian kernel: prism2_enable_aux_port: was not enabled!?
Jul  4 16:58:31 debian kernel: prism2_enable_aux_port(0) timed out
Jul  4 16:58:31 debian kernel: wifi0: trying to read PDA from 0x00390000
Jul  4 16:58:31 debian kernel: prism2_enable_aux_port: was not enabled!?
Jul  4 16:58:31 debian kernel: prism2_enable_aux_port(0) timed out
Jul  4 16:58:31 debian kernel: Valid PDA not found, buf=NULL
Jul  4 16:58:31 debian kernel: wifi0: valid PDA not found
*** Messages I put in code, the following 3 commands don't cause errors: 
***
Jul  4 16:58:31 debian kernel: hfa384x_disable_interrupts
Jul  4 16:58:31 debian kernel: hfa384x_outw, then inw
Jul  4 16:58:31 debian kernel: hfa384x_events_only_cmd
*** This one does: ***
Jul  4 16:58:31 debian kernel: about to prism2_get_version_info NIC, PRI
Jul  4 16:58:33 debian kernel: wifi0: hfa384x_cmd: entry still in list? 
(entry=c
111f160, type=0, res=0)
Jul  4 16:58:33 debian kernel: wifi0: hfa384x_cmd: command was not 
completed (re
s=0, entry=c111f160, type=0, cmd=0x0021, param0=0xfd02, EVSTAT=0000 
INTEN=0010)
Jul  4 16:58:33 debian kernel: wifi0: hfa384x_get_rid: CMDCODE_ACCESS 
failed (re
s=-110, rid=fd02, len=8)
Jul  4 16:58:33 debian kernel: Could not get RID for component PRI
Jul  4 16:58:33 debian kernel: hostap_cs: Initialization failed
Jul  4 16:58:33 debian kernel: Registered client in prism2_attach


cardctl ident:
Socket 0:
  product info: "PROXIM", "Harmony 802.11b/LAN PC CARD", ""
  manfid: 0x0126, 0x8000
  function: 6 (network)
Socket 1:
  no product info available


cardctl config:
Socket 0:
  Vcc 5.0V  Vpp1 0.0V  Vpp2 0.0V
  interface type is "memory and I/O"
  irq 3 [exclusive] [level]
  function 0:
    config base 0x03e0
      option 0x41
    io 0x0100-0x013f [16bit]
Socket 1:
  not configured


dump_cis:
Socket 0:
  dev_info
    NULL 0ns, 512b
  attr_dev_info
    SRAM 500ns, 1kb
  vers_1 5.0, "PROXIM", "Harmony 802.11b/LAN PC CARD", ""
  manfid 0x0126, 0x8000
  funcid network_adapter
  lan_technology wireless
  lan_speed 1 mb/sec
  lan_speed 2 mb/sec
  lan_media 2.4_GHz
  lan_connector Closed connector standard
  config base 0x03e0 mask 0x0001 last_index 0x02
  cftable_entry 0x01 [default]
    Vcc Vnom 3300mV Vmin 3V Vmax 3600mV Iavg 300mA
    Ipeak 300mA Idown 10mA
    io 0x0000-0x003f [lines=6] [16bit]
    irq mask 0xffff [level] [pulse]

Socket 1:
  no CIS present


cardctl info:
PRODID_1="PROXIM"
PRODID_2="Harmony 802.11b/LAN PC CARD"
PRODID_3=""
PRODID_4=""
MANFID=0126,8000
FUNCID=6
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
cardctl status:
Socket 0:
  5V 16-bit PC Card
  function 0: [ready]
Socket 1:
  no card


Here is what happens if you try to flash a new primary firmware (not sure 
if this is the right hex file):

prism2_srec wifi0 -sg pm010101.hex
srec summary for pm010101.hex
Included file name: pm010101.hex
Component: 0x0015 1.1.1 (primary firmware)


Verifying update compatibility and combining data:
Failed to open '/proc/net/hostap/wifi0/debug' for reading.
Incompatible update data.


If the problem is that I need new PDA and CIS, I would appreciate someone 
on the list sending me the necessary PDA and CIS data from your card or 
from some other source.  
The previous message said that such data from most types of prism2 cards 
should be okay (doesn't have to be proxim harmony).

Thanks,
Colin W







More information about the HostAP mailing list