Which IDE should we use for development with nRF5 SDK 12.2.0 ?

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

awneil — Wed, 31 Jul 2019 11:20:12 GMT

Standard first steps whenever any tool tells you it can't find a file:

Does that file actually exist at all?
If it does exist, is it in a location where the tool will find it?
Can you open it using any other tool; eg, Notepad?

The error message shows a relative path - so are you sure that you are starting from the correct point?

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

Jagir — Wed, 31 Jul 2019 11:06:34 GMT

For building i am getting this type errors.

" Build started: Project: experimental_ble_app_lns_pca10040_s132
Build target 'nrf52832_xxaa'
compiling boards.c...
../../../../../../components/boards/boards.c(12): error: fatal error: custom_boards.h: No such file or directory "

Ans this files are available in SDK only, i don't need to change them.

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

awneil — Wed, 31 Jul 2019 10:57:18 GMT

[quote userid="82059" url="~/f/nordic-q-a/50340/which-ide-should-we-use-for-development-with-nrf5-sdk-12-2-0/201509"]because ublox B201 firmware was build on that SDK 12[/quote]

Fair enough.

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

Jagir — Wed, 31 Jul 2019 10:53:16 GMT

I am using older SDK because ublox B201 firmware was build on that SDK 12.

I need to do changes as per my application in that firmware.

SDK from 14 provide SES segger embedded studio out of box, but i have to use SDK 12.

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

awneil — Wed, 31 Jul 2019 09:36:04 GMT

Why are you using such an old SDK version?

Note that any IDE can be used - it's just that Nordic cannot possibly provide detailed support for every single possibility.

In the case of SDK 12, Nordic provided ready-to-go projects for uVision.

However, these will be for whatever version of Keil was current back at that time - so they may no longer "just work" with the current version of Keil.

Which, again, raises the question: Why are you using such an old SDK version?

In later SDKs, Nordic include ready-to-go projects for SES.

But that doesn't stop you from creating your own projects for whatever IDE you like. It just means that you have to do the legwork.

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

awneil — Wed, 31 Jul 2019 09:29:18 GMT

[quote userid="82059" url="~/f/nordic-q-a/50340/which-ide-should-we-use-for-development-with-nrf5-sdk-12-2-0/201235"]Compiling reasons means[/quote]

Jagir: Compelling - not compiling!

https://dictionary.cambridge.org/dictionary/english/compelling

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

Einar Thorsrud — Wed, 31 Jul 2019 07:23:07 GMT

Hi,

The SDK examples should compile correctly out of the box if you have the toolchain correctly installed. Perhaps you are missing the nRF Device family pack? This is just a guess, though. You must provide the error messages if you want more specific advice, as I cannot know what errors you are seeing.

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

Jagir — Wed, 31 Jul 2019 05:58:03 GMT

I have installed Keil & installed MDK provided with SDK for keil,

Now if i am compiling examples given in that SDK it shows me compilation errors of various find not found.

How to solve those errors?

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

Einar Thorsrud — Tue, 30 Jul 2019 13:15:29 GMT

By "compelling reason" I primarily mean if Keil is too expensive for you (provided the application size exceeds the 32 kB limit) or if you have a strong desire to use other supported toolchains, such as GCC or IAR.

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

Jagir — Tue, 30 Jul 2019 12:07:25 GMT

Thanks Einar,

Compiling reasons means ?

RE: Which IDE should we use for development with nRF5 SDK 12.2.0 ?

Einar Thorsrud — Mon, 29 Jul 2019 12:53:54 GMT

Hi,

Keil µVision is the IDE which is best supported in SDK 12.2, so that is what I recommend (unless you have a compelling reason not to use it).