Bring missing stack definitions for various targets.

[pan-]

Those definitions where available in libraries/test/rtos/mbed/* tests but
not in TESTS/mbedmicro-rtos-mbed/* tests.

[pan-]

@0xc0170 @sg-

[0xc0170]

+1

[0xc0170]

@mbed-bot: TEST

HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F,NRF51_DK,NRF51_MICROBIT,NUCLEO_F411RE

[0xc0170]

/morph test

[mbed-bot]

[Build 695]
SUCCESS: Building succeeded and tests were run! Be sure to check the test results

[mbed-bot]

Result: FAILURE

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

/morph test

Output

mbed Build Number: 509

Test failed!

[sg-]

Serial NC TX failure for NRF51_DK but not for 696 or 694 ?? Seems unrelated. morph failures are single threaded mode running rtos tests

[sg-]

/morph test

[bridadan]

I think these changes are fine for now, but in the future should we look at moving these into the targets.json file or perhaps into a test config file (maybe using mbed_app.json)? I think we want to move away from having target specific code in the tests if at all possible.

[pan-]

@bridadan Is it possible to define a configuration based on the pair target and compiler ?

[mbed-bot]

Result: FAILURE

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

/morph test

Output

mbed Build Number: 511

Test failed!