mimxrt1050_evk test/kernel/mem_protect/stack_random fails on stack fault

[hakehuang]

Describe the bug
there are many fatal fault when execution on board mimxrt1050

To Reproduce
Steps to reproduce the behavior:

1. mkdir build; cd build
2. cmake -DBOARD=mimxrt1050_evk ..
3. make
4. See error

Expected behavior
test case can return correct result

Impact
looks like the stack size setting for this case is not correct

Screenshots or console output

AASSRRIINNFFII  %]]@@%::dd***** USAGE FAULT *****

  Illegal load of EXC_RETURN into PC

***** Hardware exception *****

Current thread ID = 0x8000030c

Faulting instruction address = 0x72e003f6

Fatal fault in thread 0x8000030c! Aborting.

***** USAGE FAULT *****

  Illegal load of EXC_RETURN into PC

***** Hardware exception *****

Current thread ID = 0x8000030c

Faulting instruction address = 0x72e003f6

Fatal fault in thread 0x8000030c! Aborting.

***** USAGE FAULT *****

  Illegal load of EXC_RETURN into PC

***** Hardware exception *****

Current thread ID = 0x8000030c

Faulting instruction address = 0x72e003f6

Fatal fault in thread 0x8000030c! Aborting.
...

check attached file for more details
serial_2019-02-21-23-42-27.txt

Environment (please complete the following information):

• OS: Linux
• Toolchain Zephyr SDK
• Version v1.14.0_rc1

[hakehuang]

@MaureenHelm

[agansari]

Tested on commit: c2d5e7b

***** Booting Zephyr OS v1.14.0-rc1-445-gc2d5e7b01c *****
Running test suite stack_pointer_randomness
===================================================================
starting test - test_stack_pt_randomization
Test Stack pointer randomization
stack pointer changed 58 times out of 64 tests
PASS - test_stack_pt_randomization
===================================================================
Test suite stack_pointer_randomness succeeded
===================================================================
PROJECT EXECUTION SUCCESSFUL

Test passes.

[dleach02]

not able to reproduce this either...

[hakehuang]

I test RC1 based on 588d7b0, not c2d5e7b

[hakehuang]

and if I run this case for 2 times, then I can reproduce this issue, but I think this is not the only reproduce way. @dleach02 @galak

[ioannisg]

Unfortunately, I do not have hardware to test this on target.

[hakehuang]

after download the application reboot the board can not reproduce this issue, looks like it is related my program method, as I am using the on board cmsis-dap to program a bootloader first. I will check my bootloader fisrt. Thanks. @dleach02 @galak @ioannisg thanks for your checking

[hakehuang]

this is the same root cause as #13655