Nanostack update for mbed-os-5.6

[artokin]

Notes:

• Pull requests will not be accepted until the submitter has agreed to the contributer agreement.
• This is just a template, so feel free to use/remove the unnecessary things

Description

Update nanostack for mbed-os-5.6 release:

• Update Nanostack to v6.2.1 (was: v6.2.0).
• Update coap-service as a subtree
• Update eventloop as a subtree
• Update mbed-trace as a subtree

Status

IN DEVELOPMENT

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

This Nanostack release is backwards compatible.

Related PRs

List related PRs against other branches:

branch	PR
other_pr_production	link
other_pr_master	link

Todos

• [x ] Tests
• Documentation

Deploy notes

Notes regarding the deployment of this PR. These should note any
required changes in the build environment, tools, compilers, etc.

Steps to test or reproduce

Outline the steps to test or reproduce the PR here.

[SeppoTakalo]

@0xc0170 Please start tests for this.

[0xc0170]

/morph test-nightly

[adbridge]

@artokin PRs should not contain squashes or merge commits, these break our patch releases. If you wish this to be backported to 5.5.6 then please instead use rebase for your commits. If it is targeted for 5.6 then it is less of an issue...

[artokin]

@adbridge , this PR is targeted to mbed-os-5.6.

[SeppoTakalo]

@adbridge Good point.

PR should specify:
Target: mbed OS 5.6

This is not to be backported to 5.5.x

[mbed-bot]

Result: FAILURE

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

/morph test-nightly

Output

mbed Build Number: 1096

Example Build failed!

[SeppoTakalo]

Can somebody explain the build failure:

Compile [ 68.7%]: irq_cm4f.S
[DEBUG] Compile: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\bin\iasmarm --cpu Cortex-M7 --fpu VFPv5 -DTRANSACTION_QUEUE_SIZE_SPI=2 -D__CORTEX_M7 -DARM_MATH_CM7 -D__FPU_PRESENT=1 -DUSBHOST_OTHER -D__MBED_CMSIS_RTOS_CM -D__CMSIS_RTOS -f .\BUILD\NUCLEO_F767ZI\IAR\.includes_741ae50a4fb9e68fa715ca0da6ea3a3a.txt -o .\BUILD\NUCLEO_F767ZI\IAR\mbed-os\rtos\rtx5\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\irq_cm4f.o .\mbed-os\rtos\rtx5\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\irq_cm4f.S
[DEBUG] Return: 3
Traceback (most recent call last):
  File "C:\mj\workspace\bm_wrap\1189\examples\mbed-os-example-mesh-minimal\mbed-os\tools\make.py", line 296, in <module>
    stats_depth=options.stats_depth)
  File "C:\mj\workspace\bm_wrap\1189\examples\mbed-os-example-mesh-minimal\mbed-os\tools\build_api.py", line 539, in build_project
    objects = toolchain.compile_sources(resources, resources.inc_dirs)
  File "C:\mj\workspace\bm_wrap\1189\examples\mbed-os-example-mesh-minimal\mbed-os\tools\toolchains\__init__.py", line 922, in compile_sources
    return self.compile_queue(queue, objects)
  File "C:\mj\workspace\bm_wrap\1189\examples\mbed-os-example-mesh-minimal\mbed-os\tools\toolchains\__init__.py", line 985, in compile_queue
    raise ToolException(err)
ToolException
[mbed] Working path "C:\mj\workspace\bm_wrap\1189\examples\mbed-os-example-mesh-minimal" (program)

[theotherjimmy]

@SeppoTakalo That's an internal IAR error that we are trying to root cause ATM: #4879.

[studavekar]

/morph test-nightly

[mbed-bot]

Result: SUCCESS

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

/morph test-nightly

Output

mbed Build Number: 1128

All builds and test passed!