UBLOX EVK ODIN W2 with LWIP6 ethernet fails on eth.connect() with error -3010

[teetak01]

• Type: Bug
• Priority: Critical

Ublox board reliable fails to get IPv6 address with LWIP6 enabled and using easy-connect.

00:02:42.599 10:59:40.680 | D1 <<< DutThread: [EasyConnect] IPv6 mode
00:02:42.601 10:59:40.683 | D1 <<< DutThread: [EasyConnect] Using Ethernet
00:03:00.554 10:59:58.636 | D1 <<< DutThread: [EasyConnect] Connection to Network Failed -3010!
00:03:00.555 10:59:58.637 | TC     MainThread: Test Case fails because of: Failed to initialize connection

In the same network and with same application, K64F is able to connect with IPv6.

[teetak01]

@MarceloSalazar @bridadan @JanneKiiskila

[0xc0170]

@teetak01 using latest master or what is mbed-os SHA? Is easy-connect public? If yes, please share a repo. anything that helps to reproduce it

@andreaslarssonublox

[JanneKiiskila]

easy-connect is public, of course.
https://github.com/ARMmbed/easy-connect
-> using the tip of the master from there.

mbed-os - 5.4.6 release.

[JanneKiiskila]

Hi,

You can use for example mbed-os-example-client for reproducing this.

https://github.com/ARMmbed/mbed-os-example-client

It has the easy-connect and mbed-os correctly in place already. For the mbed_app.json, use this; https://github.com/ARMmbed/mbed-os-example-client/blob/master/configs/eth_v6.json

[andreaslarssonublox]

@JanneKiiskila
Ok, thanks for the error report we will look at shortly.
Internal ref: TE_OM2-61

Do you know if it works for the NUCLEO_F429ZI target?

[JanneKiiskila]

Nucleo fails as well, see #4433

[teetak01]

This issue seems to be related to #4433 . The Ublox at least makes some effort with the MAC, although its randomization is very weak.

From couple of last runs:

MAC address d4:ca:6e:70:72:0d
MAC address d4:ca:6e:70:72:0d
MAC address d4:ca:6e:70:72:0c
MAC address d4:ca:6e:70:49:a1
MAC address d4:ca:6e:70:49:a1

With high probability there is going to be devices with identical MACs.

[andreaslarssonublox]

@teetak01 The ethernet MAC address for ODIN is stored in OTP during production so it shall always be unique and does not change between reboots. Just to be sure, are you using only one board in the test setup above for the test runs?

[JanneKiiskila]

@andreaslarssonublox - does this also apply for the Ethernet?

[andreaslarssonublox]

@JanneKiiskila Yes, it's stored in OTP for both ethernet and Wi-Fi.

[teetak01]

@andreaslarssonublox you are right. We have multiple boards in CI and I went through the logs. Each device is having correctly unique MAC, which is preserved between jobs.

So, this issue is something else than what we are seeing with the Nucleo-board.

[JanneKiiskila]

We would greatly appreciate any pointers on how to enable the right logs in LWiP that could reveal the true root cause for this problem.

[bridadan]

There's a high probability that the fix for #4433 will also be the fix for this issue. Let's keep the conversation on #4433 for now and we'll update this one after more investigation.