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

Cannot build projects in SES; 'entropy.c' & ctr_drgb.c' fatal errors

Hi Devzone,

I am struggling to build projects in SES. I am getting "fatal errors" when I try to build applications and samples. See following output from SES (asset_tracker build):

1> Compiling ‘entropy.c’
2> Compiling ‘ctr_drbg.c’
1> C:/Users/jesp374b.NEXT/AppData/Local/Programs/Python/Python37/Lib/site-packages/west/ncs/nrfxlib/nrf_security/src/backend/cc310/replacements/entropy.c:441:1: fatal error: opening dependency file C:/Users/jesp374b.NEXT/AppData/Local/Programs/Python/Python37/Lib/site-packages/west/ncs/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/spm\zephyr\modules\nrfxlib\nrf_security\src\mbedtls\CMakeFiles\spm_mbeddrbg.dir\__\backend\cc310\replacements\entropy.c.obj.d: No such file or directory
1> compilation terminated.
2> C:/Users/jesp374b.NEXT/AppData/Local/Programs/Python/Python37/Lib/site-packages/west/ncs/mbedtls/library/ctr_drbg.c:471:1: fatal error: opening dependency file C:/Users/jesp374b.NEXT/AppData/Local/Programs/Python/Python37/Lib/site-packages/west/ncs/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/spm\zephyr\modules\nrfxlib\nrf_security\src\mbedtls\CMakeFiles\spm_mbeddrbg.dir\C_\Users\jesp374b.NEXT\AppData\Local\Programs\Python\Python37\Lib\site-packages\west\ncs\mbedtls\library\ctr_drbg.c.obj.d: No such file or directory
2> compilation terminated.
Build failed


I am using the Nordic Semi. version of SES.
I have used the "Getting Started Assistant" to set up my toolchain. I have re-cloned the nRF Connect SDK using the commands mentioned in the Getting Started Assistant. I have also installed the modules mentioned in the assistant.
I am using "ncs_tag" = v1.0.0

Thanks in advance.

Regards, 
Jesper.

Parents
  • Hi, 

    Just to make sure, did you also run "west update" after changing the tag?

    Please run these commands and build the code again.

    git checkout v1.0.0
    west update

    -Amanda H.

  • Hi,

    Yes, I did run "west update".
    I just tried to run the commands again, but with no luck. I am still getting the same errors when I build. 

  • Hi,

    I deleted the nsc folder, and performed the commands as per instructions in Section 2. 
    I had no issues cloning the nRF Connect SDK, nor any when using a tagged version (v1.0.0).
    But when I tried to install the required modules for Zephyr, I get the following error:

    Collecting hub==2.0 (from -r zephyr\scripts\requirements.txt (line 10))
      ERROR: Could not find a version that satisfies the requirement hub==2.0 (from -r zephyr\scripts\requirements.txt (line 10)) (from versions: 0.0.1, 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.2, 0.2.0.1, 0.2.0.3, 0.2.0.4)
    ERROR: No matching distribution found for hub==2.0 (from -r zephyr\scripts\requirements.txt (line 10))
    When trying to install hub==2.0 manually, I get the same error. 
    By the looks of it, there seems to be no version "2.0" for hub. The "closest" version is "0.2".
    Should I try to install this version (v0.2) manually?

    The requirements for "nrf" and "mcuboot" installed with no errors.


    Jesper

    Edit: I have not tried the tutorial mentioned. Will do so soon.

  • Hi Jesper, 

    Please see Bjørn Kvaale's suggestion in this post:

    changing hub == 2.0 to git-spindle == 2.0

    -Amanda H.

  • Hi Amanda,

    I am able to build the project now, which is great :)
    I did as suggested, and changed the "requirements.txt" file. I was then able to complete the installation with no further issues. 

    I also didn't have any issues flashing my merged.hex to the DK. However, I don't seem to be able to get a connection. I am running asset_tracker, in an attempt to add the DK to my nRF Cloud, but only LED 3 blinks. Should I open a new thread on this topic? 

    Nevertheless, thank you for your help :)
    Jesper 

  • Oh no... I am getting new errors when trying to build the at_client sample, see below...

    3> C:/Users/jesp374b.NEXT/AppData/Local/Programs/Python/Python37/Lib/site-packages/west/ncs/mbedtls/library/asn1parse.c:387:1: fatal error: opening dependency file C:/Users/jesp374b.NEXT/AppData/Local/Programs/Python/Python37/Lib/site-packages/west/ncs/nrf/builds/newAt_client/spm\zephyr\modules\nrfxlib\nrf_security\src\mbedtls\CMakeFiles\spm_mbedcrypto_vanilla.dir\C_\Users\jesp374b.NEXT\AppData\Local\Programs\Python\Python37\Lib\site-packages\west\ncs\mbedtls\library\asn1parse.c.obj.d: No such file or directory
    3> compilation terminated.
    2> C:/Users/jesp374b.NEXT/AppData/Local/Programs/Python/Python37/Lib/site-packages/west/ncs/mbedtls/library/asn1write.c:389:1: fatal error: opening dependency file C:/Users/jesp374b.NEXT/AppData/Local/Programs/Python/Python37/Lib/site-packages/west/ncs/nrf/builds/newAt_client/spm\zephyr\modules\nrfxlib\nrf_security\src\mbedtls\CMakeFiles\spm_mbedcrypto_vanilla.dir\C_\Users\jesp374b.NEXT\AppData\Local\Programs\Python\Python37\Lib\site-packages\west\ncs\mbedtls\library\asn1write.c.obj.d: No such file or directory
    2> compilation terminated.
    Build failed

    What could be the cause this time?

    Jesper

  • I performed a reboot of my pc, and I have also changed the location of my build folder (shortening the path to the build folder). I am now able to successfully build both asset_tracker and at_client.

    I hope that was it, and that I can continue to build in the future.

    Jesper

Reply Children
No Data
Related