Country Code settings in iMX8qxpC0mek

[Ram2]

Hi NXP Team

When country code is changed, wlan driver fetch the txpower_xx.bin filr from etc/bt-fwimage
And as per wifi_mod_para.conf initial txpower_xx.bin is read from /lib/firmware/nxp.
which path/folder we need to keep firmware, power.bin and regulatory.db files, does the wlan driver has implementation to fetch from /etc/bt-fwimage.
or there is a macro which defines the path and so can be customised

Requirement is : iMX8qxpC0mek
O.S : Scrathgap [ kernel 6.6.5]

Thanks in Advance 

BR,

Sairam

[weidong_sun]

Dear @Ram2 ,

Could you please tell me Which WiFi module & driver/firmware version you are using?

For WiFi module based on NXP WiFi chip, use the following commands to load it driver.

# modprobe moal mod_para=nxp/wifi_mod_para.conf

or 

# insmod mlan.ko

# insmod moal.ko mod_para=nxp/wifi_mod_para.conf

[Note]

firmware & parameter file, wifi_mod_para.conf are both located in /lib/firmware/nxp

There are 2 kinds of firmware files for WiFi & Bluetooth:  Firmware file name with combo is for Wi-Fi & Bluetooth, which is recommended for uses,  you can also find independent Wi-Fi firmware and Bluetooth firmware. If you want change parameters when loading wifi driver, you can find corresponding node named with WiFi chip part number first in wifi_mod_para.conf, then add one or change existing parameter.

For example, add txpower setting in wifi_mod_para.conf.

......

txpwrlimit_cfg=nxp/txpower_xx.bin

cntry_txpwr=1

......

or place txpower_xx.bin file into /lib/firmware/nxp, and only set cntry_txpwr=1

......

cntry_txpwr=1

......

txpower_xx.bin is just to defined HARDWARE TX POWER capabilities.

Additionally,  etc/bt-fwimage you mentioned should not be firmware of Bluetooth.

If you want to use txpower_xx.bin file, The db.txt/Linux CRDA will be used.

[cntry_txpwr]

2 = the driver uses the regulatory and Txpower Management V2 mechanism. It looks for
rgpower_XX.bin file
1 = the driver uses the legacy mechanism with db.txt/Linux CRDA for regulatory domain
and looks for txpower_XX.bin file
"no value" = The parameter is not in the command. In this case, the driver uses the legacy
mechanism with db.txt/Linux CRDA for regulatory and the firmware default values for
Txpower levels

We have an application note for Tx power settings, 

Regulatory Domain and Tx Power Level Management V2

(AN13384)

It is secure file, which needs two steps to download it.

--NDA is required.

--Applying for access rights from product management team.

Thanks!

Regards,

Weidong