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.

WL1837MOD: modifying INI file for regulatory domain

Part Number: WL1837MOD

Tool/software:

The WL1837MOD is being used in a new design for which the domain regulatory information has to be updated. The customer is utilizing a Python Script to make the changes (https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git). Is this the recommended process? Is this script vetted by TI? 

Additional questions:

  1. The script includes a set of 5GHz channels that doesn’t include all 5 GHz channels.  Does the HW support all 5 GHz channels and should the script be updated to handle them?
  2. Db.txt has an entry for TR that spans multiple frequency bands (5495 – 6425).  How should this be handled by the script for the TI HW?
  3. Are there any changes to the format/information in db.txt that should be handled by the script?

The contents of the input (downloaded) file have changed over time and the script that was originally provided by TI produces output that seems questionable.  For example, there are some channels in the 5GHz range that are included in the input that aren’t supported by the TI script (maybe this is intentional?).  This leads to entries in the output file that have 0 supported channels. Could you please comment on that?

Thank you!

  • looking into this for you

  • Hi Lenio,

    I'm not sure what python script you are referring to, perhaps you could share more details? The link you provided is for the wireless registry database, not any python script provided from TI. 

  • By the way, in linux context, the wireless regdb doesn't have relation to the INI file (wl18xx-conf.bin) that gets downloaded to the wl18xx on boot. Hope that clears up the misconception.

  • Could you please answer one of the main questions which relates to the absence of few 5GHz channels in the database? The Python script was an attempt to adjust the regulatory database to include those missing channels. We have already advised the customer in the past that regulatory databases should not be altered under any circumstances, but the main question remains: does the hardware support all 5-GHz channels? Why are some channels missing? The customer is hesitant to run the script with these pending questions. 

  • Hi Lenio,

    Sorry for the delay. 

    The wireless regdb simply states that for some countries the power of a determined channel must be limited. There is no relation between what the wireless regdb states and the hardware that can be supported. So yes the hardware supports the full 5GHz band, but it may not connect to an AP if the country code mentions that the channel is not supported in that country.