u-blox ODIN driver v1.3 rc2 for mbed OS 5

[andreaslarssonublox]

Description

Bug fixes for the u-blox ODIN-W2 driver:

• GCC reports wrong size mbed-os-example-client size with UBLOX_EVK_ODIN_W2 is massive #3598
• SD card not working with WiFi UBLOX_EVK_ODIN_W2 - SD-card not working if WiFi is used #4257
• Default connection timeout to 20 sec instead of infinite UBLOX_EVK_ODIN_W2 - connect fails unless security is specified #3431
• Removed dependencies to lower RTOS C API
• New/delete works for the OdinWiFiInterface class
• The driver should be compilable with STM32F4 cube v1.16.0 STM32F4 cube update from v1.12.0 to v1.16.0 #4299

The driver has been built with this mbed-os commit:
SHA-1: 8f29517

Status

READY

Migrations

NO

Related PRs

NO

Todos

NO

Deploy notes

None

Steps to test or reproduce

N/A

Test results

mbed_os_test_results_arm.txt
mbed_os_test_results_gcc_arm.txt
mbed_os_test_results_iar.txt

[0xc0170]

/morph test

[0xc0170]

Just to be certain, all is backward compatible, no breaking change here?

What about the new cmsis5 update - will it require a new update?

[andreaslarssonublox]

Yes, there should not be any API changes. We have removed dependencies to lower layer RTOS stuff so it should work with CMSIS5.

[0xc0170]

Yes, there should not be any API changes.

I noticed some code restructure, like removal in the structures, so this should go into 5.5 ?

[andreaslarssonublox]

The OdinWiFiInterface.h has a slight change, the error code is returned for set_timeout , before it was void. Also there is a default timeout on connection setup now, before it was infinite.
The other C API header files have some changes but the end user should use the C++ API.
For us it can go in now but if you think that the set_timeout is a too big change it can also wait I guess.

[mbed-bot]

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 256

Test failed!

[sg-]

@studavekar What version DAPLink is on that board? The version number used to be char 3...7

| K22F           | K22F[0]              | COM9        | I:          | 0231000026334e45003f400d5e0e00294eb1000097969900 |

[studavekar]

The version of DAP link was 0241, have updated to 0243

| K22F          | K22F[0]              | G:          | COM22       | 0231000026334e45003f400d5e0e00294eb1000097969900 | 0243

[studavekar]

/morph test

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 268

All builds and test passed!

[JanneKiiskila]

Please merge this ASAP, so that we can verify the Cloud Client.
@0xc0170 @geky

[JanneKiiskila]

Thank you @0xc0170 and @andreaslarssonublox - I have verified the mbed Cloud Client now works with UBLOX ODIN EVK W2 over WiFi with those changes.

Starting example client
Start simple mbed Cloud Client
Resets storage to an empty state
Start developer flow
[EasyConnect] IPv4 mode
[EasyConnect] Using WiFi (ODIN) 
[EasyConnect] Connecting to WiFi jannek.iki.fi
[EasyConnect] Connected to Network successfully
[EasyConnect] IP address 192.168.1.221
[EasyConnect] MAC address d4:ca:6e:70:88:2d

Client registered

Endpoint Name: 015c20dcb95500000000000100100141
Device Id: 015c20dcb95500000000000100100141
increment resource value, new value of resource is 1
increment resource value, new value of resource is 2