Cannot use set_config() API provided by the Ublox driver in the OdinWiFiInterface.cpp to configure wifi parameters such as scan listen interval, remain on channel, etc.
MODULE_UBLOX_ODIN_W2 family
IAR 8.42.1
mbed-os-5.14.2
IAR 8.42.1
In any example using , add the following code
OdinWiFiInterface *network;
network = (OdinWiFiInterface *)(WiFiInterface::get_default_instance());
target_config_params_e cfg = ODIN_CFG_SET_SCAN_LISTEN_INTERVAL;
network->set_config(&cfg, 150);
@se7ensong thank you for raising this issue.Please take a look at the following comments:
Have you correctly specified which version of Mbed OS you are using (tag or sha)? We cannot automatically identify a release based on what you have provided.
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Not sure what should I specify here. The tag shown on the github is indeed mbed-os-5.14.2
Not sure what should I specify here. The tag shown on the github is indeed mbed-os-5.14.2
@se7ensong I'll investigate, that tag is indeed valid and should have been correctly identified by our automation
Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2580
@ARMmbed/team-ublox - probably up your alley?
@se7ensong we've started looking into the issue.
I have run the application and I've seen that application crashes when network->set_config(&cfg, 150); is called. I want to know that, if application is crashing in your case as well or you've encountered a different output? Just to make sure if we are correctly replicating it.. It would be helpful for us if you can provide the application/error logs..
Thanks
@qasim-ublox , yes, that crashes but you should be able to fix this by fixing the fall through here in the switch cases: https://github.com/ARMmbed/mbed-os/blob/4bc491ac30cf58f763c9060ac6fb310d844de890/targets/TARGET_STM/TARGET_STM32F4/TARGET_STM32F439xI/TARGET_MODULE_UBLOX_ODIN_W2/sdk/ublox-odin-w2-drivers/OdinWiFiInterface.cpp#L1999
Then, it should go through without issue but it has no effect I think
@se7ensong yes you are right about the fix. We've already applied the above fix but it still crashes. While debugging the driver I found that, this crash is coming from driver. We are further investigating it and will provide the fix soon.
This issue is fixed in the latest release i.e. v3.7.2. Can we close this issue now?