• State Verified Answer
  • Replies 11 replies
  • Subscribers 89 subscribers
  • Views 2777 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 268496
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Error when adding MCUBOOT to project

CktDesigner

I'm using nRF Connect v1.5.0, Zephyr, and Segger Embedded Studio (SES) to develop an application I'm testing on nRF5340-DK.

I have a project that compiles and runs.    But now I want to include MCUBOOT so I can eventually add in FOTA updates.

My understanding is that I only need to add "CONFIG_BOOTLOADER_MCUBOOT=y" to prj.conf and rebuild the solution to include MCUBOOT in the project.

I added the statement to prj.conf, ran Cmake in SES, then attempted to rebuild the project/solution, but the build fails.

The error message seems to indicate that it can't find a file, but it looks like the path listed in the error message may be malformed.   The first part of the path looks like it proceeds down through the build directory hierarchy, but then the "relative back-a-directory" attempts to traverse a directory that doesn't exist.  The path ends with the install directory where nRF_Connect SDK is installed (E:/AdditionalWindowsTools/Nordic/nRF_Connect_SDK).

Is there some other parameter I need to set to get MCUBOOT included in my project?

Here is a screen capture showing the error:

Thanks!

Parents
  • 0

    As an aside... 

    While waiting to see what is happening when including "CONFIG_BOOTLOADER_MCUBOOT=y" in the prj.conf file, I decided to comment this line out and continue developing the underlying code.

    I performed the edit on prj.conf, then ran Cmake through SES.   I cleaned the Solution, then rebuilt.    

    The result is an error:

    I expected to get back to the clean build I had prior to adding the statement in prj.conf.

    It appears that the error is flagged on a statement that is not currently active...    And perhaps part of the MCUBOOT code.   Shouldn't removing the statement from prj.conf eliminate this?

    Thanks...

  • 0 in reply to CktDesigner

    I got the second part of this to compile.   This was accomplished by creating a new build target directory.   So evidently, commenting out the CONFIG statement for MCUBOOT, then running CMake, Cleaning the existing build directory must not completely clean the build target directory.    Starting with a "fresh one" works.

    So now I can continue development of my code until I get an answer to the MCUBOOT issue...

Reply
  • 0 in reply to CktDesigner

    I got the second part of this to compile.   This was accomplished by creating a new build target directory.   So evidently, commenting out the CONFIG statement for MCUBOOT, then running CMake, Cleaning the existing build directory must not completely clean the build target directory.    Starting with a "fresh one" works.

    So now I can continue development of my code until I get an answer to the MCUBOOT issue...

Children
No Data
Related