Mbed Cloud Client Example with Mbed OS6 hardfaults

[esajaa]

Description of defect

When using the RC1 for the Mbed OS 6.0.0 for the Mbed Cloud Client Example, the device hardfaults. This does seem to happen when the device starts to connect with ethernet.

Target(s) affected by this defect ?

K64F

Toolchain(s) (name and version) displaying this defect ?

GCC_ARM 7.3.1

What version of Mbed-os are you using (tag or sha) ?

9a8c9e2

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

Mbed CLI: 1.10.1

How is this defect reproduced ?

Change the Mbed OS version of the Mbed Cloud Client Example to point to the first release candidate of Mbed OS 6.0.0. Link to Mbed Cloud Client Example https://github.com/ARMmbed/mbed-cloud-client-example

[yogpan01]

@adbridge @0xc0170 FYI.

[evedon]

@hugueskamba could you investigate

[ciarmcom]

@esajaa thank you for raising this issue.Please take a look at the following comments:

We cannot automatically identify a release based on the version of Mbed OS that you have provided.
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de
or a single valid release tag of the form mbed-os-x.y.z .

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[esajaa]

Seems like this configuration change causes the issues:
https://github.com/ARMmbed/mbed-os/pull/12761/files

When reverting it, the example works with the 6.0.0 RC1

[ithinuel]

Hello.
I am unable to reproduce the crash. using :

git clone https://github.com/ARMmbed/mbed-cloud-client-example.git
cd mbed-cloud-client-example
mbed deploy
cd mbed-os
git checkout mbed-os-6.0.0-rc1
cd ..
mbed dm init -d arm.com --model-name oob
mbed compile -t GCC_ARM -m K64F -f

using gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599] (GNU Tools for Arm Embedded Processors 9-2019-q4-major)

confirmed with gcc version 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907] (GNU Tools for Arm Embedded Processors 7-2018-q2-update)

tracked it down to :

#0  0x0004614a in mstd::impl::INVOKE<Kinetis_EMAC, void (), Kinetis_EMAC* const&>(void (Kinetis_EMAC::*)(), Kinetis_EMAC* const&) (
    target=<optimized out>, fn=<optimized out>) at ./mbed-os/platform/cxxsupport/mstd_type_traits:350

[adbridge]

@esajaa what version of GCC are you using ?

[esajaa]

GCC_ARM 7.3.1. I tried it with the newer one, 9.2.1, and the example works fine with that one. Thank you for the quick support.

[kjbracey]

Duplicate of #12910? Need a release note that we're serious about needing GCC 9.

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2682

[adbridge]

Duplicate of #12910? Need a release note that we're serious about needing GCC 9.

We can add it as a requirement for mbed-os-6.0 that both GCC 9 and ARMC 6 are required...

[adbridge]

GCC_ARM 7.3.1. I tried it with the newer one, 9.2.1, and the example works fine with that one. Thank you for the quick support.

@esajaa can we close this now then ?

[kjbracey]

We can add it as a requirement for mbed-os-6.0 that both GCC 9 and ARMC 6 are required...

It is already there in the usual "supported toolchain" section, the difference is just that it's not just that we haven't tested it (but it may well work) as in the past, we know for a fact that GCC 7 will fail this time.

Anything we can do to try to pre-empt people hitting this and wasting time figuring it out would be good.

Don't think compiler version has ever really mattered that much in the past, particularly for GCC. Failures due to old versions have been rare. I reckon people are out of the habit of looking at "supported toolchains" on updates.