This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

new custom board.h file causes build error: expected '=', ',', ';', 'asm' or '__attribute__' before '_Bool'

Hi, I have followed the steps of generating a new .h file for my custom board (save as of the PCA10056.h board, modify the file, then generate a new macro in preprocessor definitions).  However, the updates result in the following build error.  Is there a simple explanation?  All other files in the project are identical, and the original PCA100056.h file in the project builds and runs just fine. I'm using SDK 15.2 with SES 3.40 since they were verified to work together.  I don't see any syntax issues in the cusom .h file.   I appreciate the help.

Rebuilding ‘MyProject’ from solution ‘MyProject’ in configuration ‘nrf52840_xxaa’
1> Assembling ‘thumb_crt0.s’
2> Compiling ‘system_nrf52840.c’
3> Assembling ‘ses_startup_nrf_common.s’
4> Assembling ‘ses_startup_nrf52840.s’
1> Compiling ‘patch_ble.c’
4> Compiling ‘data_comm.c’
2> Compiling ‘main.c’
3> Compiling ‘external_flash_fake.c’
2> In file included from ../components/ble/common/ble_advdata.h:53:0,
2> from C:\nRF_BLE_FPCB\MyProject\test\main.c:56:
2> ../components/boards/boards.h:109:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '_Bool'
Build failed

Parents
  • Hi,

    Can you show us your board file? It is not easy to say what the problem is just from the error message without seeing the code that has the error. Without knowing more, I suspect you are missing something at the end of a statement or block (";", "}" , "#endif" or similar).

  • Yes, I can share my board file, but I would prefer to temporarily take the ticket private before publicly sharing anything that could be considered sensitive information.  I'm happy to have it returned to public once the solution is found.

Reply
  • Yes, I can share my board file, but I would prefer to temporarily take the ticket private before publicly sharing anything that could be considered sensitive information.  I'm happy to have it returned to public once the solution is found.

Children
  • Sounds good. Can you make a new private case with the board file and refer to this thread? That way we can keep the confidential information there and update this public thread with the solution.

  • Nevermind, I think it was an idiotic single character in front of a commented line.  Regardless, it builds now.  Thanks for your time.