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

About build error of multirole program

Hello.

The other day, I purchased Nordic's BLE module and started developing a multirole program. The development environment is

・Use project:ble_app_multirole_lesc_s132_pca10040
・ Module used: nRF52832
・ Use IDE: SES
・ Use SDK: nRF5_SDK15.3
・ Soft device used: S132

However, when I tried to build the sample project, a build error occurred. The error content is “nrd_section_x.h: No such file or directory”. (Image1)
I thought that I did not set the path of “nrf_section_x.h” and tried to solve it by the following method.
1. Select a project, right-click and select "Options"
2. Change "Debug" displayed in the upper right to "Common"
3. Select "Preprocessor"
4. Add the path with “nrd_section_x.h” in nRF5_sDK15.3 to the content (Value) of “User Include Directories” (image2 and image3)

However, the same error came out even if it was built by the above method

.
Please let me know if you debug. Thank you.

Image1Image2Image3

Parents
  • Hi,

    Have you done any changes to the project apart from adding the include path and have you tried to build other examples? All projects should build "out-of-the-box" without requiring any changes. I have not managed to replicate the build error here at least.

    Unless you're certain that nothing else has changed I'd suggest you download a new copy of the SDK and try building the example again. You may also try placing the SDK closer to C:\  in order to shorten the absolute paths. There was a path length limit on Windows 7 that could lead to errors like these, but I thought it was fixed for Win 10.    

Reply
  • Hi,

    Have you done any changes to the project apart from adding the include path and have you tried to build other examples? All projects should build "out-of-the-box" without requiring any changes. I have not managed to replicate the build error here at least.

    Unless you're certain that nothing else has changed I'd suggest you download a new copy of the SDK and try building the example again. You may also try placing the SDK closer to C:\  in order to shorten the absolute paths. There was a path length limit on Windows 7 that could lead to errors like these, but I thought it was fixed for Win 10.    

Children
Related