Compile, link but after flashing, the processor no signs of life

Mbed OS
1

I am offline, using mbed-cli

finally I can compile and link and then flash the chip with .bin file

but the processor is dead in the water…
reflash with the old mbed2.0 online file, the processor is ok

<>
Link: v12
Elf2Bin: v12
±-------------------±-------±------±------+
| Module | .text | .data | .bss |
±-------------------±-------±------±------+
| Misc | 85327 | 861 | 8044 |
| drivers | 3234 | 12 | 212 |
| features/mbedtls | 48 | 0 | 0 |
| hal | 574 | 8 | 0 |
| platform | 1159 | 16 | 92 |
| rtos | 156 | 8 | 0 |
| rtos/rtx | 6114 | 100 | 5036 |
| targets/TARGET_STM | 16122 | 36 | 872 |
| Subtotals | 112734 | 1041 | 14256 |
±-------------------±-------±------±------+
Allocated Heap: unknown
Allocated Stack: unknown
Total Static RAM memory (data + bss): 15297 bytes
Total RAM memory (data + bss + heap + stack): 15297 bytes
Total Flash memory (text + data + misc): 113775 bytes

Object file test_env.o is not unique! It could be made from: C:\workspace\v12\mbed-os\features/unsupported\tests\mbed\env\test_env.cpp .\mbed-os\features\frameworks\greentea-client\source\test_env.cpp
Image: ..build\NUCLEO_F072RB\ARM\v12.bin
<>

How do I set the Stack ? (see error message above)

2

Have you tried to run a debugger? Changing code from mbed 2.0 to mbed OS might have made a difference in execution behavior.

3

Thanks Sarah,

still not running,

Yes, that’s the plan, I am just getting into uV5 now.

I am just starting a new project to see/check how the startup runs in the debugger, then I should be able to swing the rest across…

We are back down to about the same size as mbed2 running MDK522, so that’s not the problem. The Ram size seemed to jump up by 5Kbytes.

Actually the RAM is now close to full. So, MDK522 still does not do as well as online for compression.
my code is full of bool variables, which could compile as 32bit numbers worst case, I guess this is where the RAM is going.

<>
bool stateParameters1,2,3;
>

I dont know how to set the stack in mbed-os the output is complaining about it.

±-------------------±-------±------±------+
| Module | .text | .data | .bss |
±-------------------±-------±------±------+
| Misc | 85327 | 861 | 8044 |
| drivers | 3234 | 12 | 212 |
| features/mbedtls | 48 | 0 | 0 |
| hal | 574 | 8 | 0 |
| platform | 1159 | 16 | 92 |
| rtos | 156 | 8 | 0 |
| rtos/rtx | 6114 | 100 | 5036 |
| targets/TARGET_STM | 16122 | 36 | 872 |
| Subtotals | 112734 | 1041 | 14256 |
±-------------------±-------±------±------+
Allocated Heap: unknown
Allocated Stack: unknown
Total Static RAM memory (data + bss): 15297 bytes
Total RAM memory (data + bss + heap + stack): 15297 bytes // 16 x 1024 - 0xC0 = 16192 bytes available
Total Flash memory (text + data + misc): 113775 bytes

I am not using RTOS on this project.

I would guess my use of the stack would be below 0x200.