Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

oberon_backend_chacha_poly_aead.h: No such file or directory error when upgrading from SDK 16.0.0 to SDK 17.1.0 in Segger Embedded Studio

It is properly pointed to in the emProject file, and the SES IDE is able to locate and open it in file explorer.

I upgraded the liboberon to 3.0.8:

When I previously encountered file not found errors it was because my emProject paths were wrong but for this one they seem to be fine. 

Parents
  • Hi,

    It you can find the files in the given paths, and have verified that the project is located in the correct level relative to the files, this could be caused by a too long path.

    If you have placed the project/SDK in a long path, this may cause Keil to not be able to detect the files. If this is the case, please try to move the full SDK closer to the root of the harddrive.

    Best regards,
    Jørgen

Reply
  • Hi,

    It you can find the files in the given paths, and have verified that the project is located in the correct level relative to the files, this could be caused by a too long path.

    If you have placed the project/SDK in a long path, this may cause Keil to not be able to detect the files. If this is the case, please try to move the full SDK closer to the root of the harddrive.

    Best regards,
    Jørgen

Children
Related