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

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

awneil — Tue, 18 May 2021 20:08:07 GMT

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu/310235#310235"]Can you please explain what's the difference between "nRF Connect SDK" and "nRF5 SDK" [/quote]

"nRF5 SDK" is the one that's been around for years - currently at v17.something.

It is creaking from having to support all the new features & options.

It only supports the 2.4GHz protocols (BLE, ANT, Thread, Zigbee).

"nRF Connect SDK" is "the future" - they're not going to doing any more updates to the old SDK.

It takes a whole new approach to configuring stuff, includes an RTOS (Zephyr), etc

https://webinars.nordicsemi.com/understand-the-nrf-connect-sdk-2

As I said, I've not tried it yet.

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu/310235#310235"]is there any cross-reference list that explains which "nRF5 SDK" version supports which SoftDevice-Versions [/quote]

That's in the Release Notes:

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

Also, for each chip, there's a "Compatibility matrix":

https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52832/COMP/nrf52832/nrf52832_comp_matrix.html

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

MDF — Tue, 18 May 2021 16:02:32 GMT

...Thanks for clarifying this. Can you please explain what's the difference between "nRF Connect SDK" and "nRF5 SDK" - I browsed through the online documentation, but I found no clear explanation.

Also, is there any cross-reference list that explains which "nRF5 SDK" version supports which SoftDevice-Versions ?

thanks, matthias

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

awneil — Mon, 17 May 2021 16:39:08 GMT

Sorry - The naming is confusing. 😞

There's "nRF Connect" as the tool for downloading, etc - replacing nRF GO Studio.

Then there's "nRF Connect SDK" as a completely new SDK - as opposed to the nRF5 SDK.

It's the SDK I've not used - sorry, I thought that's what you meant.

But I don't use nRF Connect for programming - I use SES or Segger's own utilities for that.

[quote userid="6462" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu/309576#309576"]Or just download direct from SES[/quote]

Do SES and/or Keil and/or Segger's own utilities see your J-Link?

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

MDF — Mon, 17 May 2021 15:57:47 GMT

you are joking - you told me 5 days ago to use nRF connect ...

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

awneil — Mon, 17 May 2021 15:10:51 GMT

Sorry - not used nRF-Connect SDK yet

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

MDF — Mon, 17 May 2021 14:32:20 GMT

I downloaded+installed "nRF connect" - the installer updated some files and found my existing Keil and SES environment ... but it won't see my Segger USB j-link. Is this maybe because I have a "j-link edu" ? Windows device Manager (USB devices) says the J-Link is properly installed.

My target hardware contains the nRF52832 and a MSP430, so I have also a MSP programmer installed+connected (using virtual com5 and com6). nRF connect finds this device, but of course its not valid.

any ideas ? - thanks

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

awneil — Wed, 12 May 2021 16:38:32 GMT

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu/309564#309564"]nRFgo Studio[/quote]

nRF GO Studio is ancient - does it even support nRF52832 ?

You should be using nRF Connect:

further down that page:

Or just download direct from SES.

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu/309564#309564"]possible to have two versions of SES installed in parallel ?[/quote]

It was certainly possible with v4.50 and earlier versions

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

MDF — Wed, 12 May 2021 15:31:47 GMT

I found out, that this issue seems to be related to nRFgo Studio and/or my hex file. I used NRFgo Studio to download the hex file from the segger compilation into the nrf52, and after this, SES reports the cortex-m0. When I erase all memory and download another hex-file (which I know that works), the device reports as Cortex-M4

I guess that the hex binary from SES is somehow not ok - but how can I find this out ? Its just the example from SDK 17.0.2 with no modification

Do you know whether its possible to have two versions of SES installed in parallel ? I mean 4.50 and 5.44

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

MDF — Wed, 12 May 2021 15:11:42 GMT

Segger suggests to continue using 5.44 - and I was able to successfully compile the code from the HID_keyboard example, so why not using 5.44 ...

It seems I can load the code (hex-file) into the nrf52 chip using nrf-go studio - but it won't work with SES. My hardware setup is compatible with pca10040, so I'm using this path.

When connecting the J-link target I see an error "Identified core does not match configuration. (Found: Cortex-M0, Configured: Cortex-M4)" - here is the complete output:

Connecting ‘J-Link’ using ‘USB’
Connecting to target using SWD
Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 5.44/bin/JLink_x64.dll
Firmware Version: J-Link V11 compiled Apr 27 2021 16:36:21
DLL Version: 7.20`
Hardware Version: V11.00
Target Voltage: 3.335
Device "NRF52832_XXAA" selected.
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x5BA01477
SWD speed too high. Reduced from 4000 kHz to 2700 kHz for stability
DPIDR: 0x2BA01477
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC041. Implementer code: 0x41 (ARM)
Unknown core, assuming Cortex-M0
Found Cortex-M0 r0p1, Little endian.
Identified core does not match configuration. (Found: Cortex-M0, Configured: Cortex-M4)
FPUnit: 6 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB000 SCS
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM

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

awneil — Wed, 12 May 2021 14:54:52 GMT

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu/309548#309548"]I still have no idea how to get around this 'D__MICROLIB' issue[/quote]

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

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu/309548#309548"]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[/quote]

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

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

MDF — Wed, 12 May 2021 14:48:47 GMT

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

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

awneil — Wed, 12 May 2021 11:43:37 GMT

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 ...

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

MDF — Wed, 12 May 2021 08:53:12 GMT

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.

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

awneil — Wed, 12 May 2021 08:44:25 GMT

So that's a licensing issue with SES.

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

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

MDF — Wed, 12 May 2021 07:56:01 GMT

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 ?

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

awneil — Tue, 11 May 2021 16:39:10 GMT

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu"]SES V5.44[/quote]

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

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

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu"]

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

[/quote]

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

[quote userid="104149" url="~/f/nordic-q-a/75018/c3903u-argument--d__microlib-not-permitted-for-option-cpu"]I was asuuming that the examples would compile without any issues[/quote]

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