SWRU576 January   2021 WL1801MOD , WL1805MOD , WL1807MOD , WL1831MOD , WL1835MOD , WL1837MOD

 

  1.   Trademarks
  2. 1 Introduction
    1. 1.1 Acronyms Used in This Document
  3. 2 Peer to Peer (P2P) Mode
    1. 2.1 P2P Device
      1. 2.1.1 Searching Phase
      2. 2.1.2 Negotiation
      3. 2.1.3 Group Formation
    2. 2.2 PSP Client
    3. 2.3 P2P GO
    4. 2.4 P2P Commands
      1. 2.4.1 P2P Commands Detailed Information
        1. 2.4.1.1 p2p_find
        2. 2.4.1.2 p2p_connect
        3. 2.4.1.3 p2p_listen
        4. 2.4.1.4 p2p_group_add
        5. 2.4.1.5 p2p_group_remove
        6. 2.4.1.6 p2p_peer
        7. 2.4.1.7 p2p_invite
      2. 2.4.2 P2P Event Details
    5. 2.5 P2P Use Cases
      1. 2.5.1 P2P Connection in PBC (Push Button Control)
      2. 2.5.2 Create Autonomous 1:2 P2P Group (Push button Control)
        1. 2.5.2.1 Assigning IP Address in P2P Mode Using DHCP Method
        2. 2.5.2.2 Create 1:2 P2P Group - Connect With PIN Code
        3. 2.5.2.3 P2P Invitation Procedure - Create Autonomous 1:2 P2P Group, (Push button Control)
  4. 3 Access Point (AP) and Peer-to-Peer (P2P) Multirole
    1. 3.1 Errata/Limitations
  5. 4 Multi BSSID (mBSSID)
    1. 4.1 Setup and Configuration
    2. 4.2 User Guide and Examples
  6. 5 Access Point (AP) Enhanced Low Power (ELP) Mode
    1. 5.1 Setup and Configuration
    2. 5.2 User Guide and Examples
    3. 5.3 Errata/Limitations
  7. 6 WiLink8 Wake on WLAN (WoWLAN) Feature
    1. 6.1 Mode of Operation
    2. 6.2 Adding "Suspend/Resume" WoW Mode to AM335x EVM
      1. 6.2.1 Patch Description
    3. 6.3 WoWLAN (Wake on WLAN) Mode Enable Procedure
      1. 6.3.1 Commands and Expected Output
      2. 6.3.2 Rx Filter Configuration
        1. 6.3.2.1 Rx Filter Configuration Examples
    4. 6.4 WoWLAN - Magic Packet
    5. 6.5 Block Acknowledgement (BA) Filter Setting
    6. 6.6 Hardware Modification Engineering Change Order (ECO) Request for AM335x EVM
  8. 7 WiLink8 Suspend Resume Mode
    1. 7.1 Suspend Resume Example With AM437x SDK
  9. 8 Access Point (AP) Dynamic Frequency Selection (DFS) Master Support
    1. 8.1 Setup and Configuration
    2. 8.2 User Guide & Examples
    3. 8.3 Errata/Limitations
  10. 9 Station Mode - Alternative Method, With iw Commands, Explained
    1. 9.1 Step 1- Check if the wlan0 Interface is Already Running
    2. 9.2 Step 2- Bringup wlan0 Interface if Not Running
    3. 9.3 Step 3 - Connect Device to Available Acces Point
  11. 10References

2.4.2 P2P Event Details

The following events can be received from wpa_supplicant via control interface. The events are specified in hostap/src/common/wpa_ctrl.

Table 2-5 Details of P2P Events
P2P Events Details
P2P_EVENT_DEVICE_FOUND Indication of a discovered P2P device with information about that device. For example: P2P-DEVICE-FOUND 02:b5:64:63:30:63 p2p_dev_addr=02:b5:64:63:30:63 pri_dev_type=1-0050f204-1 name='Wireless Client' config_methods=0x84 dev_capab=0x21 group_capab=0x0
P2P_EVENT_GO_NEG_REQUEST A P2P device requested GO negotiation, but we were not ready to start the negotiation. For example: P2P-GO-NEG-REQUEST 02:40:61:c2:f3:b7 dev_passwd_id=4
P2P_EVENT_GO_NEG_SUCCESS Indication of successfully complete group owner negotiation. P2P-GO-NEG-SUCCESS
P2P_EVENT_GO_NEG_FAILURE Indication of failed group owner negotiation. Additional parameter is status. P2P-GO-NEG-FAILURE status=1
P2P_EVENT_GROUP_FORMATION_SUCCESS Indication that P2P group formation has been completed successfully. P2P-GROUP-FORMATION-SUCCESS
P2P_EVENT_GROUP_FORMATION_FAILURE Indication that P2P group formation failed (due to provisioning failure or timeout). P2P-GROUP-FORMATION-FAILURE
P2P_EVENT_GROUP_STARTED Indication of a new P2P group having been started. Additional parameters: network interface name for the group, role (GO/client), SSID, frequency. The pass phrase used in the group is also indicated here if known (on GO) or PSK (on client). If the group is a persistent one, a flag indicating that is included. For example: P2P-GROUP-STARTED p2p0-p2p-0 GO ssid="DIRECT-3F Testing" freq=2412 passphrase="12345678" go_dev_addr=02:40:61:c2:f3:b7 [PERSISTENT]
P2P_EVENT_GROUP_REMOVED Indication of a P2P group having been removed. Additional parameters: network interface name for the group, role (GO/client). For example: P2P-GROUP-REMOVED p2p0-p2p-0 GO
P2P_EVENT_CROSS_CONNECT_ENABLE Indication of allowing of P2P cross connection with uplink network interface. Additional parameters: network interface name for the group, cross connect uplink network interface name. For example: P2P-CROSS-CONNECT-ENABLE p2p0-p2p-0 wan0
P2P_EVENT_CROSS_CONNECT_DISABLE Indication of disabling of P2P cross-connection with uplink network interface. Additional parameters: network interface name for the group, cross connect uplink network interface name. For example: P2P-CROSS-CONNECT- DISABLE p2p0-p2p-0 wan0
P2P_EVENT_PROV_DISC_SHOW_PIN Request from the peer for local p2p device to display a PIN that will be entered on the peer. The following parameters are included after the event prefix: peer_address, PIN. The PIN is a random PIN generated for this connection. P2P_CONNECT command can be used to accept the request with the same PIN configured for the connection. For example: P2P-PROV-DISC-SHOW-PIN 02:40:61:c2:f3:b7 12345670 p2p_dev_addr=02:40:61:c2:f3:b7 pri_dev_type=1-0050F204-1 name='Test' config_methods=0x188 dev_capab=0x21 group_capab=0x0
P2P_EVENT_PROV_DISC_ENTER_PIN Request from the peer for local p2p device to enter a PIN displayed on the peer. The following parameter is included after the event prefix: peer address, device type, name and capabilities. For example: P2P-PROV-DISC-ENTER-PIN 02:40:61:c2:f3:b7 p2p_dev_addr=02:40:61:c2:f3:b7 pri_dev_type=1-0050F204-1 name='Test' config_methods=0x188 dev_capab=0x21 group_capab=0x0
P2P_EVENT_PROV_DISC_PBC_REQ Request from the peer for local p2p device to connect using PBC. The following parameters are included after the event prefix: peer_address, device type, name and capabilities. P2P_CONNECT command can be used to accept the request. For example: P2P-PROV-DISC-PBC-REQ 02:40:61:c2:f3:b7 p2p_dev_addr=02:40:61:c2:f3:b7 pri_dev_type=1-0050F204-1 name='Test' config_methods=0x188 dev_capab=0x21 group_capab=0x0
P2P_EVENT_PROV_DISC_PBC_RESP The peer accepted our provision discovery request to connect using PBC. The following parameters are included after the event prefix: peer_address. P2P_CONNECT command can be used to start GO Negotiation after this. For example: P2P-PROV-DISC-PBC-RESP 02:40:61:c2:f3:b7
P2P_EVENT_SERV_DISC_REQ Indicate reception of a P2P service discovery request. The following parameters are included after the event prefix: frequency in MHz, source address, dialog token, service update indicator, Service Query TLV(s) as hexdump. For example: P2P-SERV-DISC-REQ 2412 02:40:61:c2:f3:b7 0 0 02000001
P2P_EVENT_SERV_DISC_RESP Indicate reception of a P2P service discovery response. The following parameters are included after the event prefix: source address, dialog token, service update indicator, Service Responce TLV(s) as hexdump. For example: P2P-SERV-DISC-RESP 02:40:61:c2:f3:b7 0 0 0300000101
P2P_EVENT_INVITATION_RECEIVED Indicate reception of a P2P Invitation Request. For persistent groups, the parameter after the event prefix indicates which network block includes the persistent group data. For example: P2P-INVITATION-RECEIVED sa=02:40:61:c2:f3:b7 persistent=0
P2P_EVENT_INVITATION_RESULT Indicate result of a P2P invitation that was requested with P2P_INVITE command. The parameter status=<value> shows the status code returned by the peer (or -1 on local failure or timeout). For example: P2P-INVITATION-RESULT status=1