Updated u-blox ODIN-W2 driver binaries to 2.1 rc1

[andreaslarssonublox]

Description

This release contains the following fixes.

• [OOB 5.5.0] ublox_evk_odin_w2 never gets to main see [OOB 5.5.0] ublox_evk_odin_w2 never gets to main mbed-os-example-wifi#36

The release was built and tested with the following commit in mbed-os:
35999be
(this fix was added #4444 in order to pass tests)

Status

READY

Migrations

If this PR changes any APIs or behaviors, give a short description of what API users should do when this PR is merged.

NO

Related PRs

This release depends on the following fixes:

• events: Adopt osEventFlags from RTX 5 #4571
• resolve lwip init twice issue #4444

Todos

Deploy notes

N/A

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]

@andreaslarssonublox CAn youo please rebasE? I believe the latest odin reorganisation in the code that came from the workshop resulted in conflicts here

[andreaslarssonublox]

Rebased it

[0xc0170]

/morph test

[mbed-bot]

Result: SUCCESS

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

/morph test

Output

mbed Build Number: 592

All builds and test passed!

[adbridge]

@andreaslarssonublox does this PR really still depend on #4571 ?

[0xc0170]

@andreaslarssonublox does this PR really still depend on #4571 ?

How does this depend ? I tried this patch, on top of master (does not include referenced PR), and the wifi example builds . But I assume it fails to connect to wifi, correct (havent yet run it on the board).

[andreaslarssonublox]

@0xc0170 For the debug profile it will assert after connection has been setup and after sending some data if #4571 is not fixed. When using the other profiles we have not seen it crashing. See #4500 (comment) for more info.