nrf52.h vs nrf52840.h?

RE: nrf52.h vs nrf52840.h?

Mitch996 — Tue, 13 Jun 2017 01:40:02 GMT

Got it, thanks a whole bunch!

RE: nrf52.h vs nrf52840.h?

RK — Mon, 12 Jun 2017 02:25:16 GMT

defined() is very standard C preprocessor syntax, every compiler understands it. It has nothing to do with MDK-ARM. Just define it wherever in your build system you define things. In a makefile it's -D, in every IDE it's somewhere in the IDE. Any of the examples for the NRF52840 for your IDE/build system will have it correctly defined, copy that.

RE: nrf52.h vs nrf52840.h?

Mitch996 — Mon, 12 Jun 2017 02:19:48 GMT

Well the thing is, the original project kind of had all those specific includes, but instead they were about nrf51.

So when migrating to the nrf52 platform, I simply changed them to nrf52/nrf52840 etc.

I'm not exactly sure including nrf.h can get things done, since I've already done it. Either way, inside nrf.h, all you see is macros that dictate inclusion of nrf52.h, nrf52840.h etc.

Anyhow, in nrf.h, there's this line:

#elif defined (NRF52840_XXAA)

"definted" isn't exactly a C99 standard keyword, so I suppose it has something to do with the MDK-ARM, how do I properly activate this line? By putting down "NRF52840_XXAA" in the magic-wand -> C/C++ tab -> define inputbox?

RE: nrf52.h vs nrf52840.h?

RK — Sun, 11 Jun 2017 09:47:05 GMT

must be in a better timezone! It's nice when two people agree on an answer however.

RE: nrf52.h vs nrf52840.h?

endnode — Sun, 11 Jun 2017 09:43:29 GMT

Hey, you were 15 seconds faster';)

RE: nrf52.h vs nrf52840.h?

endnode — Sun, 11 Jun 2017 09:42:50 GMT

I believe you should not manage this manually but instead include simply components\device\nrf.h and just set correct global defines identifying your target. SDK should do the magic for you.

RE: nrf52.h vs nrf52840.h?

RK — Sun, 11 Jun 2017 09:42:35 GMT

Just include nrf.h and make sure you have the correct defines. nrf.h will (as it always has done) include the right things, which in this case is nrf352840.h.