Peer manager leading to hard fault with -Os flag with GCC 5

RE: Peer manager leading to hard fault with -Os flag with GCC 5

tesc — Mon, 25 Apr 2016 14:41:29 GMT

Hi,

I have no problems building and running the ble_app_proximity example of SDK 11 when using -Os optimisation. It uses peer manager. Do you get the same or similar issues when trying with the ble_app_proximity example?

There has been some linker script problems but these should have been fixed from SDK 11. The linker scripts still must be patched when migrating from previous versions, though.

Regards, Terje

RE: Peer manager leading to hard fault with -Os flag with GCC 5

FormerMember — Mon, 25 Apr 2016 13:24:54 GMT

Thanks for the quick reply RK. I think where we are differing is what our expectations are from Nordic. A Free tool doesn't mean that it should be kind of untested and dependent on the community to iron out the bugs, especially when a company like Nordic say that they support GCC. I can do the debugging to figure out what is happening and do less "guessing", especially if I've to work with a pre-release SDK. But I don't expect to do hours of debugging when moving to a new "stable" SDK. I am using the code from 11.0.0_89a8197 which I think is the latest.

So if anyone is able to use peer manager in SDK 11.0.0 with Os optimization with GCC, please let me know.

RE: Peer manager leading to hard fault with -Os flag with GCC 5

RK — Mon, 25 Apr 2016 00:51:08 GMT

"I'm guessing some memory isn't allocated in an aligned manner. Please help me solve this as we prefer using Os as its lighter on the OTA update."

Guessing doesn't help. How can someone solve a random hardfault you have without proper details? Hardfaults are possible to track back, so get the stack trace and work out where the hardfault occurred and why, then someone may be able to suggest something.

As to your general complaints about GCC support, Nordic at least provides support for GCC, but internally they're really a Keil shop so it's going to get less testing and it's going to have some issues. A lot of those get resolved by the community here and are rolled back into the SDK. That's the cost of using free tools.

The fix for the linker script was put into the released SDK11.0, are you sure you're using the right SDK?