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

[MDF]

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

[awneil]

Sorry - not used nRF-Connect SDK yet

[MDF]

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

[awneil]

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.

awneil said:

Or just download direct from SES

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

[MDF]

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

[awneil]

MDF said:

Can you please explain what's the difference between "nRF Connect SDK" and "nRF5 SDK"

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

MDF said:

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

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