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

AES example in SDK version 17.0.0 does not compile out of the box

Hello.

Trying to compile the AES CBC MAC example out of the box, we get the ferror below.

Your help would be appreciated.

Many thanks,

Andrew

Building ‘nrf_crypto_aes_cbc_mac_pca10040’ from solution ‘nrf_crypto_aes_cbc_mac_pca10040’ in configuration ‘Release’

....

Linking nrf_crypto_aes_cbc_mac_pca10040.elf
    cannot find ../../../../../../../../external/micro-ecc/nrf52hf_armgcc/armgcc/micro_ecc_lib_nrf52.a: No such file or directory
Build failed

  • Hello.

    The micro-ecc problem has resurfaced at linker level now.

    What I didn't realise when I got the clean compile above was that mcro-ecc was disabled. When I enable it and disable all the other backends, it runs trhough to the linking stage but I get the error below which from what I can see means there is a  floating point clash between the snRF2K target (supporting VFP register usage) and the library .a file you provided (the one I have been unable to compile) which does not.

    Can you please advise how to resolve this ?

    Regards,

    Andrew

    ++++++++++++++++++++++++

    Here is the error:

    Building ‘nrf_crypto_aes_cbc_mac_pca10040’ from solution ‘nrf_crypto_aes_cbc_mac_pca10040’ in configuration ‘Release’
      Linking nrf_crypto_aes_cbc_mac_pca10040.elf
        Output/Release/Exe/nrf_crypto_aes_cbc_mac_pca10040.elf uses VFP register arguments, ../../../../../../../../external/micro-ecc/nrf52nf_armgcc/armgcc/micro_ecc_lib_nrf52.a(uECC.c.o) does not
        failed to merge target specific data of file ../../../../../../../../external/micro-ecc/nrf52nf_armgcc/armgcc/micro_ecc_lib_nrf52.a(uECC.c.o)
    Build failed

  • Did you ever get this issue resolved?

    FWIW, I think it is due to inconsistent use of the floating point ABI between the library build and your project build.

Related