custom_board.h for sdk v12.2 and v13.0

RE: custom_board.h for sdk v12.2 and v13.0

Artem Efremov — Thu, 06 Jul 2017 19:13:22 GMT

If your custom board does not have any buttons, then the problem could be resolved by setting LEDS_NUMBER to 0 in custom_board.h and wrapping content of bsp_btn_ble.c with

#if BUTTONS_NUMBER > 0
  // content of bsp_btn_ble.c
#endif // BUTTONS_NUMBER > 0

It seems to be a bug because functions in bsp_btn_ble.c always try to call functions from bsp.c which are not defined when BUTTONS_NUMBER is 0.

RE: custom_board.h for sdk v12.2 and v13.0

ogura — Sat, 22 Apr 2017 22:31:35 GMT

thanks. both works fine.

RE: custom_board.h for sdk v12.2 and v13.0

butch — Sat, 22 Apr 2017 15:57:18 GMT

Or have you tried in pca10040.h changing LEDS_NUMBER 4 to LEDS_NUMBER 0 ? (and similarly for BUTTONS_NUMBER)

RE: custom_board.h for sdk v12.2 and v13.0

butch — Sat, 22 Apr 2017 13:12:54 GMT

Can you get around the problem by keeping BOARD_PCA10040 and not trying to define a new custom_board.h? In other words, if your app knows there is no LED or button, and does not call any functions to use LED or button, then your app should compile and work. I don't think it will even link in any of the board support functions, since you don't call them.