search

u-blox / evb-ant-1

4 stars 0 forks source link

MAYA-W1 definition #1

Open bkkim007 opened 12 months ago

bkkim007 commented 12 months ago

In the source / app_config.h @ line 22 Wi-Fi module was defined AW AM457 instead of u-blox MAYA-W1 as below

/ @TEST_ANCHOR /

define WIFI_IW416_BOARD_AW_AM457_USD

/ @END_TEST_ANCHOR /

It should be changed as below

define WIFI_IW416_BOARD_UBX_MAYA_W1_USD

//#define WIFI_IW416_BOARD_AW_AM457_USD

Thanks BK

KostasKarouzosUblox commented 10 months ago

Hello @bkkim007,

You are right, the usage of WIFI_IW416_BOARD_AW_AM457_USD was kept in app_config.h file from a version of the SDK where WIFI_IW416_BOARD_UBX_MAYA_W1_USD was not yet available, and then did not change after porting to newer version.

It should be noted that there is no actual difference in the setup of MAYA driver, since both names result in the same configuration:

/* AzureWave AW-AM457-uSD */
#elif defined(WIFI_IW416_BOARD_AW_AM457_USD)
#define WIFI_BT_TX_PWR_LIMITS "wlan_txpwrlimit_cfg_WW.h"
#define SD8978
#define SDMMCHOST_OPERATION_VOLTAGE_1V8
//#define WIFI_BT_USE_USD_INTERFACE
//#define OVERRIDE_CALIBRATION_DATA "WIFI_IW416_BOARD_AW_AM457_CAL_DATA_EXT.h"
#define WLAN_ED_MAC_CTRL                                                               \
    {                                                                                  \
        .ed_ctrl_2g = 0x1, .ed_offset_2g = 0x9, .ed_ctrl_5g = 0x1, .ed_offset_5g = 0xC \
    }
/* u-blox EVK-MAYA-W161/-W166 */
#elif defined(WIFI_IW416_BOARD_UBX_MAYA_W1_USD)
#define WIFI_BT_TX_PWR_LIMITS "wlan_txpwrlimit_cfg_WW.h"
#define SD8978
#define SDMMCHOST_OPERATION_VOLTAGE_1V8
#define WIFI_BT_USE_USD_INTERFACE
#define WLAN_ED_MAC_CTRL                                                               \
    {                                                                                  \
        .ed_ctrl_2g = 0x1, .ed_offset_2g = 0x9, .ed_ctrl_5g = 0x1, .ed_offset_5g = 0xC \
    }

Therefore we decided not to apply a fix at this point, but to include the change in our next release. Please feel free to update this issue with your feedback