C3903U: Argument '-D__MICROLIB' not permitted for option 'cpu'.

[MDF]

My aim is to use a nRF52832 for a Bluetooth peripheral device.

- I just started with a fresh SES V5.44 and downloaded the nRF SDK 17.0.2
- I imported the example "ble_app_hids_keyboard_pca10040_s112" from the SDK
- trying to build the code throws this error : C3903U: Argument '-D__MICROLIB' not permitted for option 'cpu'.

I was asuuming that the examples would compile without any issues - what can I do ?

thanks, matthias

[awneil]

MDF said:

SES V5.44

The release notes say the SDK is tested against v4.50:

https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.2/index.html

MDF said:

the code throws this error : C3903U: Argument '-D__MICROLIB' not permitted for option 'cpu'.

That's not a code error - that's one of the tools complaining about a command-line error.

Please post the full build output transcript - that should show the command line and where, exactly, this error is being thrown

MDF said:

I was asuuming that the examples would compile without any issues

They certainly should

I'd suggest first trying with the recommended SES version: you're using one that's a major version increment - so could be breaking changes ... ?

EDIT

Someone else having problems when using SES v5.something with nRF5 SDK v17.0.2 (ie, later than recommended in the SDK Release Notes) :

devzone.nordicsemi.com/.../314596

[MDF]

I uninstalled the 5.44 and installed the 4.50 - this one comes up with a dialog box "unrecoverable failure : the evaluation period for this release has now expired" ... and then terminates. What now ?

[awneil]

So that's a licensing issue with SES.

Is that when you just start SES  with no project, or when you open a project?

[MDF]

It pops up directly when I start SES - currently I can't do anything !

I assumed the 5.44 installation wrote something to the registry, so I uninstalled and cleaned the registry and the file system manually (removed anything that refers to "Segger"), then rebootet the PC, but after another 4.50 installtion the problem is the same. I even tried this mutliple time, with no success.

[awneil]

Oh dear.

You could try asking Segger: 

https://forum.segger.com/index.php/Board/9-SEGGER-Embedded-Studio-related/

Otherwise it'll have to wait for someone from Nordic to give the official licensing status ...

[MDF]

I was able to create a license via Nordic website, seems to work now
Finally I found out where to find the SES project files "emProject" and this allows me to compile now

I still have no idea how to get around this 'D__MICROLIB' issue - but I guess I wont need it now

Dont get me wrong, but I'm a bit upset because for days it feels like Nordic tells me to get in touch with Segger, Segger tells me its a nordic issue and I played the same game with arm+Keil+Nordic.

thanks, matthias

[awneil]

MDF said:

I still have no idea how to get around this 'D__MICROLIB' issue

Are you still getting that with v4.50 of SES ?

MDF said:

it feels like Nordic tells me to get in touch with Segger, Segger tells me its a nordic issue and I played the same game with arm+Keil+Nordic

Always the trouble when there's multiple independent players involved.

I guess Nordic just don't have the resources to develop their own in-house IDE