• State Not Answered
  • Replies 8 replies
  • Subscribers 91 subscribers
  • Views 3337 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 267706
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Nordic SDK & Custom boards

Steven

Hi,


can anyone provide any insight into moving beyond a pca10040 development board and creating a project for a custom board? What are the steps that you have to go through?

I am using a design based on a fanstel bt832. 

I take it that you have to modify "boards.h" and add a header file for your own board.

I am using Segger Embedded Studio and nRF5_SDK_15.2.0_9412b96.

Regards,

Steve.

Parents
  • 0 in reply to Jørgen Holmefjord

    Hi Jorgen,

    the sum total of the wisdom dispensed by nordic on this matter amounts to a single paragraph in the SDK docs at the link you provided:

    Adding support for a custom board

    To add support for a custom board, you must create a custom board support file with the name custom_board.h. This file must be located in a directory in the Include path. You can then select to use the custom board by adding the define statement #define BOARD_CUSTOM.

    The easiest way to create the custom_board.h file is to start with an existing platform definition file (for example pca10040.h) and adapt it to your needs.

    Is that really all there is to say on the matter? Clearly this is not sufficient to inform a user to do something fundamental- to step away from the Nordic dev boards and implement a project for a custom board.

    Sorry, that is not good enough and really very poor customer support, both in the extent of the docs and the care and detail provided in your response - see the previous response from Tim. If it takes a community member to provide detailed support I think that speaks to the attitude of Nordic employees towards their users.

Reply
  • 0 in reply to Jørgen Holmefjord

    Hi Jorgen,

    the sum total of the wisdom dispensed by nordic on this matter amounts to a single paragraph in the SDK docs at the link you provided:

    Adding support for a custom board

    To add support for a custom board, you must create a custom board support file with the name custom_board.h. This file must be located in a directory in the Include path. You can then select to use the custom board by adding the define statement #define BOARD_CUSTOM.

    The easiest way to create the custom_board.h file is to start with an existing platform definition file (for example pca10040.h) and adapt it to your needs.

    Is that really all there is to say on the matter? Clearly this is not sufficient to inform a user to do something fundamental- to step away from the Nordic dev boards and implement a project for a custom board.

    Sorry, that is not good enough and really very poor customer support, both in the extent of the docs and the care and detail provided in your response - see the previous response from Tim. If it takes a community member to provide detailed support I think that speaks to the attitude of Nordic employees towards their users.

Children
No Data
Related