RE: nRF51822 "target folder" in mbed? (Really, how to live with the mbed API)

Mike Wirth — Tue, 03 Mar 2015 01:15:58 GMT

Philip, thanks for being a trail blazer with the mbed environment. I'll undoubtedly have more mbed IDE questions for you :-) Mike

RE: nRF51822 "target folder" in mbed? (Really, how to live with the mbed API)

Philip Freidin — Tue, 03 Mar 2015 00:01:57 GMT

Hi Mike,

If you hover over the "A" in the multiple popups, one of them includes "TARGET_NRF51_DK".

In the program workspace pane (left side of the screen) select the "mbed" library in your project.

On the right side of the screen, the "Library Build Details" pane should show up. Click on the "Open Build Page". Find "TARGET_NRF51_DK" , and click on it, followed by "TARGET_NORDIC", "TARGET_MCU_NRF51822" , "TARGET_NRF51_DK", and finally "PinNames.h"

(all of which was shown when you hovered over the "A" that had TARGET_NRF51_DK in the path)

At line 100 (also shown while hovering over the "A") is the definition for LED1 for the DK board. And all the other pin definitions for _DK.

If you instead navigate to /TARGET_NRF51_DK/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/nrf-sdk/app_common

you will find the Nordic headers that you should be familiar with in the Keil environment.

Sounds like you are doing development with the DK board, but are planning to use a different board later. I think the following might be a way to support both:

// change next line to 0 for Mikes target board

#define TESTING_WITH_DK    (1)

#if TESTING_WITH_DK
#define MIKES_LED1             LED1
#else
#define MIKES_LED1             P25
#endif

I haven't actually tested the above snippet, I leave that for you.

I don't have answers for the rest of your questions.