[OOB 5.6 r2] DISCO_F429ZI crashed at runtime by Makefile exported binary

[toyowata]

Description

• Type: Bug
• Priority: Major

---

Bug

Target
DISCO_F429ZI

Toolchain:
GCC_ARM

Toolchain version:
arm-none-eabi-gcc.exe (GNU Tools for ARM Embedded Processors 6-2017-q1-update) 6.3.1 20170215 (release) [ARM/embedded-6-branch revision 245512]
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

mbed-cli version:
1.2.0

mbed-os sha:
mbed-os-example-uvisor-number-store (363c109)
`- mbed-os (6e087488e101)

DAPLink version:
0221

Expected behavior
The example run on the target without error.

Actual behavior
I got following error at runtime.

Semaphore 0x0 error -9

Steps to reproduce

$ mbed import mbed-os-example-uvisor-number-store
$ cd mbed-os-example-uvisor-number-store
$ mbed update mbed-os-5.6-oob2
$ mbed export -m DISCO_F429ZI -i make_gcc_arm
$ make

Flash the binary from BUILD/mbed-os-example-uvisor-number-store.bin to the target drive.

Note that the binary created by mbed compile -m DISCO_F429ZI -t GCC_ARM -f works fine (no runtime error). And also, binary file size is slightly different between GCC_ARM build and make_gcc_arm build (see below).

Toolchain	binary file size
GCC_ARM	71KB
make_gcc_arm	124KB

Misc. info

Build log file
Makefile

[ciarmcom]

ARM Internal Ref: IOTSEC-456

[Patater]

@toyowata Please try using the --profile develop option with the exporter.

The exporter defaults to using a different profile that mbed compile, so you'll get different results from mbed compile unless you specify the --profile.

[toyowata]

The runtime result is same. Please see below:
ARMmbed/mbed-os-example-uvisor#60 (comment)