NRF52832: Extend idle thread stack size to 512 bytes.

[pan-]

Description

Fix a crash where the idle thread stack size overflows. This crash
was depending on the compiler and standard library used.

Status

READY

Migrations

NO

[pan-]

@0xc0170 Should resolve #4735 . I would like to have this fix included in 5.5.3.

[0xc0170]

/morph test

[marisabele]

Fix works for TARGET_MCU_NRF52832

[mbed-bot]

Result: SUCCESS

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

/morph test

Output

mbed Build Number: 782

All builds and test passed!

[thinkberg]

I am still having this issue on the NRF52832. Increasing it to 768 works so far. I was wondering, why is there no guard like in mbed_rtx_conf.h?

[0xc0170]

@thinkberg Please create an issue with details how to reproduce the issue.

[thinkberg]

I would like to, but I may have a questions regarding that, like what influences the stack usage of the idle task, so I can try to reproduce without exposing all code.

[pan-]

The compiler, its version and the compilation options are the main cause of idle thread stack size overflows.

Until static analysis is used to determine the maximum depth of the idle thread stack on every build, I'm afraid there is no reliable solution.

[thinkberg]

Then it would make sense to have a guard and be able to set the size in the config, because right now I have to patch mbed-os directly.