mbed-os-example-client does not work on STM Nucleo F401RE

[markus-becker-tridonic-com]

I am trying to get the mbed-os-example-client to run on an STM Nucleo F401RE with the 6LoWPAN shield and the configuration.

In order to do so, I modified

diff --git a/mbed_app.json b/mbed_app.json
index 48fbd8d..f4f737b 100644
--- a/mbed_app.json
+++ b/mbed_app.json
@@ -2,7 +2,7 @@
     "config": {
         "network-interface":{
             "help": "options are ETHERNET,WIFI,MESH_LOWPAN_ND,MESH_THREAD",
-            "value": "ETHERNET"
+            "value": "MESH_LOWPAN_ND"
         },
         "wifi-ssid": {
             "help": "WiFi SSID",
@@ -15,9 +15,10 @@
     },
     "target_overrides": {
         "*": {
-            "target.features_add": ["IPV6", "CLIENT", "IPV4"],
+            "target.features_add": ["IPV6", "CLIENT"],
             "mbed-client.reconnection-count": 3,
-            "mbed-client.reconnection-interval": 5
+            "mbed-client.reconnection-interval": 5,
+            "nanostack.configuration": "lowpan_router"
         }
     }
-}
+}

and

diff --git a/tools/toolchains/gcc.py b/tools/toolchains/gcc.py
index 027a956..27dc11f 100644
--- a/tools/toolchains/gcc.py
+++ b/tools/toolchains/gcc.py
@@ -86,7 +86,7 @@ class GCC(mbedToolchain):
             self.flags["common"].append("-g")
             self.flags["common"].append("-O0")
         else:
-            self.flags["common"].append("-O2")
+            self.flags["common"].append("-Os")

         main_cc = join(tool_path, "arm-none-eabi-gcc")
         main_cppc = join(tool_path, "arm-none-eabi-g++")

so that it actually fits into ROM.

On the K64:
mbed compile -c -t GCC_ARM -m K64F -j 4

Starting mbed Client example...
Using Mesh
Connecting to Mesh..
Connected to Network successfully
IP address ....
SOCKET_MODE : UDP
Connecting to coap://[...
Registered object successfully!

On the F401RE:
mbed compile -c -t GCC_ARM -m NUCLEO_F401RE

Starting mbed Client example...
Using Mesh
Connecting to Mesh..
Connection to Network Failed -3009! Exiting application....

[markus-becker-tridonic-com]

@mlnx @bcostm

[yogpan01]

@SeppoTakalo @kjbracey-arm Can you please check this ?

[kjbracey]

Can we enable some trace?

[MarceloSalazar]

It seems tracing is not working as expected (ticket here ARMmbed/mbed-os#449)
Could we please help to investigate the issue?

[markus-becker-tridonic-com]

For which module should I enable tracing?

[kjbracey]

Simplest thing to do is add mbed-trace.enable to your mbed_app.json, in this section:

"target_overrides": {
    "*": {
        "mbed-trace.enable": 1
    }
}

[markus-becker-tridonic-com]

Debug output on F401RE:

<\n>
<\r>Connection to Network Failed -3009! Exiting application....<\r><\n>
<\0>Starting mbed Client example...<\r><\n>
Using Mesh<\r><\n>
<\n>
<\r>Connecting to Mesh..<\r><\n>
<\r><27>[2K<27>[90m[DBG ][core]: Allocate Root Tasklet<27>[0m<\r><\n>
<\r><27>[2K<27>[90m[DBG ][6lo ]: P.Init<\n>
<27>[0m<\r><\n>
<\r><27>[2K<27>[90m[DBG ][m6La]: init()<27>[0m<\r><\n>
<\r><27>[2K<27>[90m[DBG ][m6La]: connect()<27>[0m<\r><\n>
<\n>
<\r>Connection to Network Failed -3009! Exiting application....<\r><\n>

[kjbracey]

Did you clean after changing the config? (There's no autodependency on it). I'm expecting trace from the network stack.

[markus-becker-tridonic-com]

I assume so. My commandline was mbed compile -c -t GCC_ARM -m NUCLEO_F401RE -j 4.

[markus-becker-tridonic-com]

Somehow I suspect that the nd_tasklet_main does not start.

[kjbracey]

Seems likely, as you cleaned. It didn't manage to start the stack at all.

[markus-becker-tridonic-com]

Any hint on what could be going wrong?

[kjbracey]

Got to go now, but perhaps lack of memory for the Nanostack (nsdynmemlib) pool? Insufficent threads configured in RTX (I don't think error returns from thread creation are checked)?

[markus-becker-tridonic-com]

Any hints on what one can tweak and where?

[SeppoTakalo]

Way back, I recall seeing timing problems with atmel-rf-driver.
I don't think we have tested with ST board for a while.

In order to verify actually what happened, we need to check with RF sniffer if the device is able to send anything at all.

There is also assumption on the driver that 'CS' release required specific timeouts, not sure if these are true on every platform.
Please see: https://github.com/ARMmbed/atmel-rf-driver/blob/master/source/driverAtmelRFInterface.cpp#L175