Upgrading to SDK 5.2.0 breaks build

RE: Upgrading to SDK 5.2.0 breaks build

Torsten Robitzki — Fri, 01 Sep 2017 09:14:47 GMT

It's fixed in 14.0! :-)

RE: Upgrading to SDK 5.2.0 breaks build

Torsten Robitzki — Wed, 01 Feb 2017 20:23:53 GMT

And the issue still persists in 12.2 :-)

RE: Upgrading to SDK 5.2.0 breaks build

Susheel Nuguru — Wed, 16 Mar 2016 08:48:07 GMT

Hi David, Yes I noticed it at the time of release. RK also created a support ticket for it. This has been added to the list here

RE: Upgrading to SDK 5.2.0 breaks build

David Robins — Wed, 16 Mar 2016 00:13:44 GMT

Nope. In S132 2.0.0 (no alpha) there is an added GCC_CAST_CPP - but it casts to uin8_t when it should be uint16_t. This produces the following error (GCC 5.2 2015q4 Tools for ARM Embedded, Windows host):

C:\Nordic\s132_nrf52_2.0.0\s132_nrf52_2.0.0_API\include/ble_gap.h:1419:1: note:
in expansion of macro 'SVCALL'
 SVCALL(SD_BLE_GAP_AUTH_KEY_REPLY, uint32_t, sd_ble_gap_auth_key_reply(uint16_t
conn_handle, uint8_t key_type, uint8_t const *p_key));
 ^
C:\Nordic\s132_nrf52_2.0.0\s132_nrf52_2.0.0_API\include/nrf_svc.h:69:6: error: impossible constraint in 'asm'
     );

Replacing uint8_t with uint16_t in nrf_svc.h so the line looks like

#define GCC_CAST_CPP (uint16_t)

fixes the problem.

RE: Upgrading to SDK 5.2.0 breaks build

Susheel Nuguru — Mon, 25 Jan 2016 10:10:46 GMT

This has been fixed and released in s132_nrf52_2.0.0-8.alpha. On S130, it is fixed but will be released in next release.

RE: Upgrading to SDK 5.2.0 breaks build

Jim Credland — Sun, 01 Feb 2015 16:18:26 GMT

Any chance of a fix?

RE: Upgrading to SDK 5.2.0 breaks build

David Robins — Tue, 30 Sep 2014 20:07:34 GMT

This isn't fixed in 6.1.0 - any ETA on a fix?

RE: Upgrading to SDK 5.2.0 breaks build

Torsten Robitzki — Thu, 07 Aug 2014 20:57:30 GMT

I just added a macro definition with your fix and as the SDK header checks whether the macro is already defined or not, this works nice, without the need to change the SDK sources. I'm using CMake too (first project) and currently, the cmake script is looking for a SDK file(GLOB NRF51_SDK_PATH ../nrf51_sdk_${NRF51_SDK_VERSION}*). NRF51_SDK_VERSION is defined as v6_0_0 and I could use this to check for the existens of the bug. `

RE: Upgrading to SDK 5.2.0 breaks build

Anne van Rossum — Thu, 07 Aug 2014 20:10:36 GMT

But would you adjust your code accordingly?

Isn't it easier to allow the user to tell before you start compiling which SDK he/she wants to use? I like cmake, so I use a cmake config file for that in my code: github.com/.../CMakeBuild.config.default, where I introduce a NORDIC_SDK_VERSION variable which I also feed into the code with a -D flag. Maybe it is of use to you.

RE: Upgrading to SDK 5.2.0 breaks build

Torsten Robitzki — Thu, 07 Aug 2014 19:38:21 GMT

And the problem seems to persist in version 6. Does someone of you know some kind of macro to inquire the SDK version, so one would be able to provide a workaround for version where this bug is still present?

RE: Upgrading to SDK 5.2.0 breaks build

Anne van Rossum — Tue, 22 Jul 2014 16:31:07 GMT

There is a bug in the SDK.

Change:

"bx r14" : : "I" (number) : "r0" \

Into:

"bx r14" : : "I" ((uint16_t)number) : "r0" \