• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 40 subscribers
  • Views 2088 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

INI File Country based?

Sesh Padm
Intellectual 380 points
Other Parts Discussed in Thread: WL1837

Hello all,

I downloaded WL1837MOD_INI_FCC_CE.ini and WL1837MOD_INI_FCC_CE_JP.ini. Not sure if gforge is the right place to get these. On comparing these files they turned out to be exactly the same.

1) Can you please point me to what differences are needed for FCC_CE ini vs Japan ini file.

2) We use QNX operating system.I do not have wlconf package available in MCP 8.5 release. Are these parameters typically set at manufacturing by editing ini files or usage of some other command line tools?

Regards,

Sesh

  • 0
    TI__Prodigy 730 points

    Sesh,

    1) Differences are needed for FCC_CE ini vs Japan are in the PerChanPwrLimitArr11ABG values.

    You can take those file from git.ti.com/.../official_inis

    2) For QNX no need to use wlconf package. You should edit the tiwlan.ini file with the changes you require (according to the ini files mentioned above) and

    run the tiwlan_cfg_ti18xx tool (the tool runs automatically if you use our load_dtv script). This will generate a valid bin file.

    Guy

  • 0 in reply to Guy Mishol
    Intellectual 380 points

    Hi Guy,

    We wish to launch our product with WL1837 across several countries in the world. With MCP 8.5 release i see a regulatory domain file.

    1) Where do we provision country code for the driver to pick up the right power levels? 

    2) Will WL8_1837_TI_module_INI file be required for all countries except Japan? Does Regulatory domain file override this file depending on country code?

    WPA supplicant.conf has a country code field. Not sure if this field has any affect on the drivers.We use calibrator tool to do most of our testing with WPA supplicant turned off. This requires some other option to set country code as well.

    Thanks,

    Sesh

  • 0 in reply to Sesh Padm
    TI__Prodigy 730 points

    Sesh,

    1) All the countries data base is in the regulatory domain file.

    2) No. The Regulatory domain file has data on all countries and it is not used to determine which country will be in use (only holds the data base).

    AP: Country is taken form the hostapd.conf file

    STA: Country taken from the beacons (in MCP8.5 we do not have support in country code settings from wpa_supplicant.conf).

    Guy

  • 0 in reply to Guy Mishol
    Intellectual 380 points

    Thanks Guy. Had a few follow up question to your responses

    1) [Guy] - AP: Country is taken form the hostapd.conf file

     [Sesh] - We do not plan to use hostapd and instead would use p2p_ti18xx.conf to create WiFi Direct Group Owners. Can we program country code into this file to ensure compliance with 802.11h for GO?

    2) [Guy] STA: Country taken from the beacons (in MCP8.5 we do not have support in country code settings from wpa_supplicant.conf).

    [Sesh] According to https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/t/392916 TI driver supports static and dynamic provisioning of country code. We do not wish to only rely on the AP after Jan 1 2015 FCC ban.

    I have the following questions related to MCP 8.5 code               

                   a) Which config file should i use for static provisioning?

                   b) How do i provision dynamically?

                  c) Is their a default  hardcoded in driver software?

                  d) Will current driver software not associate if it cannot find country information in AP beacons?

    Thanks,

    Sesh

  • 0 in reply to Sesh Padm
    TI__Prodigy 730 points

    I have the following questions related to MCP 8.5 code               

                   a) Which config file should i use for static provisioning?

    [GuyM] Again, This is not supported in MCP8.5 code (It will in MCP8.5SP1 which may be ready until the end of the year).

                   b) How do i provision dynamically?

    [GuyM] Setting the country dynamically is done automatically from every received beacon with country code.

                  c) Is their a default  hardcoded in driver software?

    [GuyM] Yes. The driver is loaded with country code = "WW" (world wide).

                  d) Will current driver software not associate if it cannot find country information in AP beacons?

    [GuyM] No. As mentioned the WW country code allows association even if it cannot find country information in AP beacons.

  • 0 in reply to Guy Mishol
    Intellectual 380 points

    Hi Guy,

    Thanks for the responses. Also wish to confirm country code behavior for P2P GO ( See question below )

    1) [Guy] - AP: Country is taken form the hostapd.conf file

     [   Sesh] - We do not plan to use hostapd and instead would use p2p_ti18xx.conf to create WiFi Direct Group Owners. Can we program country code into this file to ensure compliance with 802.11h for GO?

    Thanks,

    Sesh

  • 0 in reply to Guy Mishol
    Intellectual 380 points

    Hi Guy,

    With respect to following QA i need some clarification

     a) Which config file should i use for static provisioning?

    [GuyM] Again, This is not supported in MCP8.5 code (It will in MCP8.5SP1 which may be ready until the end of the year).

    We wish to better understand how upcoming patch will behave under following scenarios

    A) Station statically provisioned with US. Station sees country code JP broadcasted in beacons on channel 14.

    Expectations -> Station will not connect.

                                 Driver will notify application software

    B) Station statically provisioned with US. Station sees country code JP broadcasted in beacons on channel 6.

    Expectations -> Station will not connect.

                                 Driver will notify application software

    Wonder if station will connect for same region ( Eg: Belgium and Austria in EU with same power tables for 2.4 GHZ )

    C) Station statically provisioned with WW ( Worldwide ) and sees country code JP broadcasted in beacons.

    Expectation - Stations will connect