Inrease thread stack size to 1024 bytes in NVStore test for NRF52

[marcuschangarm]

Description

On the NRF52, the NVStore test is running at the stack boundary so on certain compiler versions the test will fail due to stack overflow. This PR increases the stack size for the NRF52 target.

Pull request type

[x] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change

[marcuschangarm]

@davidsaada @geky

[davidsaada]

@marcuschangarm I was really trying to avoid these target specific ifdefs in my code, working pretty hard in the NVStore tests to achieve it (I do remember the NRF52 board giving me hard time doing so).
Perhaps the best way to achieve this goal would be to inquire how much free heap size we have, and tune the test code accordingly. However, I don't know if such an API (for inquiring free heap size) even exists, do you?

[marcuschangarm]

There might be with the mem stats functions but I'm not sure.

Do you mind solving this in a later PR? This is really blocking my work and our deliverable to several companies.

[davidsaada]

Do you mind solving this in a later PR? This is really blocking my work and our deliverable to several companies.

No problem. Will probably handle it after I'm back from my vacation in a week or so.
Would just like the understand the reason for this failure., as this test previously passed successfully. I see you added many changes, and wonder if they were all related to this board only. If they are not, I suspect the test may fail for other boards as well.

[marcuschangarm]

Thank you! Hope you have a great vacation!

The whole SDK has been upgraded for the NRF52 so I'm not surprised that the behavior has changed a lot!

[cmonr]

@marcuschangarm Is there a reason that this PR is targeting master instead of your feature branch?

[0xc0170]

@marcuschangarm Is there a reason that this PR is targeting master instead of your feature branch?

Shall this be targeting your feature nrf branch rather? That would unblock feature progress, and meantime @davidsaada will look review this and propose a correct fix?

[marcuschangarm]

I'm targeting master so that I can use the CI to test the rebase branches.

Also, I'm not comfortable changing a test inside the same PR the test would have failed for.

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 1645
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/6518/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[0xc0170]

Approving with the future investigation (fix) for the proper thread stack value in this test

[mbed-ci]

Exporter Build : SUCCESS

Build number : 1277
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6518/

[mbed-ci]

Test : SUCCESS

Build number : 1434
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/6518/1434