Can't build Release, no hints on error.

Trying to build release but its failing with the only message being the screenshot above. Building debug works, but release has an issue

nrf52833 Segger embedded studio

  • They're all pretty much the same saying the .o file does not exist, the Debug build shows the same notes

  • I used nRF5 a long time ago, so I'm not native on how to solve that problem, but from what I remember, it usually can be easily solved by reinstallation of the SDK. I hope some nordic engineers will help you out soon, but try to reinstall the environment, and maybe it will do the trick Slight smile

  • Hi BMW,

    It is difficult to tell what is wrong with only this much information. Could you please give more details?

    - What SES version are you using? Please try to use the version of SES that your SDK was released with.
    - Is there any difference between the Release and Debug build configurations for the source file that are having issue?
    - Can you reproduce the issue in an example? Or can you give us some steps to reproduce it?
    - Can you, on your file system, delete the Output folder and retry the build?
    - Could there be any concerns with file path length?

    I tried to build ble_app_hrs_c_pca10100_s122, which uses the Oberon library and targets the nRF52833, but I don't have any problem.

    Hieu

  • - What SES version are you using? Please try to use the version of SES that your SDK was released with.

    Using 7.12 and 6.34 both are experiencing the issue
    - Is there any difference between the Release and Debug build configurations for the source file that are having issue?

    Release modified: 
    Debug modified: 
    - Can you reproduce the issue in an example? Or can you give us some steps to reproduce it?
    - Can you, on your file system, delete the Output folder and retry the build?

    Tested this and it seems to fail on first attempt but builds on second attempt? At lease the output file seems to work
    - Could there be any concerns with file path length? 

    No this shouldn't be the issue.

Related