Unkown hardfault when running C++ on B-L072Z-LRWAN1 about sub-iot-stack HOT 2 OPEN

I have never tried running a C++ application on the stack for embedded, but I would expect name mangling difference between C and C++ being the issue here. I saw that you added an extern "C" block around the code, but I wonder if the bootstrap function itself would need to be declared with extern "C" as wel? A long time ago we where able to run the stack as part of an OMNET++ based simulation, which meant it was useable from within a C++ program, but this was on the PC host not on the embedded target. You can still see the __LINK_C define from link_c.h being used in function definitions. My guess is that it would need to be added for bootstrap() and probably others as well. If you comment to call to bootstrap() do you still crash? Can you break in __framework_bootstrap() ?

from sub-iot-stack.

I looked a bit further into the problem and the code seems to crash on assembly code. The code crashed in the init_clock() function of stm32_common_mcu.c file when initialising the RCC structs. The debugger would go into memset assembly code where the program would throw a hardfault. The structs can be seen in the image below. I did put the = {0) in comments so the code would continue.

Later the code would crash in stm32l0xx_hal_rcc.h line 1201 that line of code would also lead to an assembly file because of calculation with unsigned 32 bit integers. It would lead to __aeabi_dadd.csdasm and would crash on the line of code which can be seen in the figure below.

So when compiling C++ for the B-L072Z-LRWAN1 the code does crash before the main loop is even called.

from sub-iot-stack.