WL1837MOD: FM is implemented to detect 4.9GHz band AP?

Hi,
- what region did you set wireless reg to ?
iw reg get

- can you pls run following commands and share the o/p
iw phy<x> info
ex: iw phy0 info

replace x with phy number that lists wlan0 interface ( iw dev)

Saurabh

4.9GHz?

AFAIK wl1837 support 2.4Ghz and 5Ghz bands. Not 4.9Ghz.

BR,

Eyal

According to the following, 11J is supported on wl1837.

Could you confirm if it's supported or not?

 Best regards

HaTa

Hi,

802.11J is not supported.
You can see in the thread that you pointed to that:
"software implementation was not completed to support this requirement, and thus was not tested as part of any release"

See the following document that lists supported features:
www.ti.com/.../swru423a.pdf

Best Regards,
Eyal

Hi,

I also refered the following E2E thread.

But, anyway, I understand that the implementation for 802.11J  are not completed and not supported.

However, I'd like to clarify more details about it because our customer already start prototype development.

I'd like to know more details for status of 11J imprementation.

According to the document which you mentioned above, at least, sccanning is applied also for 11J band. (I referted Table11)

Is that all?

11J cannot be used by change SW by ourselves?

WL1837 STA conncts to WL1837 AP, and have no plan to connects to other products.

Thanks and best regards,

HaTa.

Hi HaTa,

Sorry for the confusion. Actually if you do use wlconf:

www.ti.com/.../swra489.pdf

and run the "First Time System Configuration Script" while selecting "y" for enabling Japanese standard you would be able to use 802.11J
Have you tried this already?

Best Regards,
Eyal

Hi,

At first, I'm very glad to here that 11j can be used by using with wlconf.

However, I'd like to confirm more details about supporting of 11J because I'm very confused about it.

The conclusion is 11J is supported or NOT supported?

Best regards,

HaTa.

Hi,

I confirmed that the problem is happened even if "Japanese Standard" is set as "y".

And also , wireless region is set to Japan with "iw reg set JP".

The result of "iw reg get" is
------------
global
country JP: DFS-JP
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM
(4910 - 4990 @ 40), (N/A, 23), (N/A)
(5030 - 5090 @ 40), (N/A, 23), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW
(5490 - 5710 @ 160), (N/A, 23), (0 ms), DFS
(59000 - 66000 @ 2160), (N/A, 10), (N/A)
------------

The result of "iw phy1 info" is

------------
iphy phy1
max # scan SSIDs: 1
max scan IEs length: 441 bytes
max # sched scan SSIDs: 16
max # match sets: 16
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* WPI-SMS4 (00-14-72:1)
Available Antennas: TX 0 RX 0
Supported interface modes:
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x30
HT20
Static SM Power Save
RX Greenfield
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 16383 bytes (exponent: 0x001)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT Max RX data rate: 72 Mbps
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (20.0 dBm)
Band 2:
Capabilities: 0x30
HT20
Static SM Power Save
RX Greenfield
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 16383 bytes (exponent: 0x001)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT Max RX data rate: 72 Mbps
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5040 MHz [8] (23.0 dBm)
* 5060 MHz [12] (23.0 dBm)
* 5080 MHz [16] (23.0 dBm)
* 5170 MHz [34] (disabled)
* 5180 MHz [36] (20.0 dBm)
* 5190 MHz [38] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm)
* 5210 MHz [42] (20.0 dBm)
* 5220 MHz [44] (20.0 dBm)
* 5230 MHz [46] (20.0 dBm)
* 5240 MHz [48] (20.0 dBm)
* 5260 MHz [52] (20.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5280 MHz [56] (20.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5300 MHz [60] (20.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5320 MHz [64] (20.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5500 MHz [100] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5520 MHz [104] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5540 MHz [108] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5560 MHz [112] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5580 MHz [116] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5600 MHz [120] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5620 MHz [124] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5640 MHz [128] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5660 MHz [132] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5680 MHz [136] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5700 MHz [140] (23.0 dBm) (radar detection)
DFS state: usable (for 107 sec)
DFS CAC time: 60000 ms
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (disabled)
* 4920 MHz [184] (23.0 dBm)
* 4940 MHz [188] (23.0 dBm)
* 4960 MHz [192] (23.0 dBm)
* 4980 MHz [196] (23.0 dBm)
Band 3:
Capabilities: 0x30
HT20
Static SM Power Save
RX Greenfield
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 16383 bytes (exponent: 0x001)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT Max RX data rate: 72 Mbps
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 4920 MHz [184] (23.0 dBm)
* 4940 MHz [188] (23.0 dBm)
* 4960 MHz [192] (23.0 dBm)
* 4980 MHz [196] (23.0 dBm)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* start_sched_scan
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* testmode
* channel_switch
* set_qos_map
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
WoWLAN support:
* wake up on anything (device continues operating normally)
* wake up on pattern match, up to 5 patterns of 1-91 bytes,
maximum packet offset 0 bytes
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 2, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
total <= 3, #channels <= 2
* #{ AP } <= 2, #{ P2P-device } <= 1,
total <= 2, #channels <= 1, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports scan flush.
Device supports per-vif TX power setting
Driver supports a userspace MPM
Device supports configuring vdev MAC-addr on create.
------------

Best regards,
HaTa.