• State Not Answered
  • Replies 22 replies
  • Subscribers 25 subscribers
  • Views 1576 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 282294
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

asset_tracker_v2 build error in NRF Connect SDK V1.8

user112518

Hi, 

Trying to build the asset_tracker_v2 application I finally get the following error:


Rebuilding ‘zephyr / zephyr.elf’ from solution ‘build’ in configuration ‘Common’
Compiling ‘dev_handles.c’
Compiling ‘isr_tables.c’
Linking ‘zephyr.elf’
Post-link command
[WinError 2] The system cannot find the specified file

The software packages used are:
NRF Connect SDK V1.8
SES Nordic Edition V5.68

Trying to compile the same application from NRF Connect V1.71 is successful.

Thank You!

Neculai

  • 0

    Hello Neculai,

    are you able to successfully build the Asset Tracker V2 application in NCS v1.8.0 outside of SES, via a command line build?

    Regards,

    Markus

  • 0 in reply to user100109

    Hi,

    I did what you said and got the following result:

    Culi@Culi-TOSH-I5 MINGW64 ~/ncs/v1.8.0/nrf/applications/asset_tracker_v2 ((v1.8.0))
    $ west build -b nrf9160dk_nrf9160ns
    -- west build: generating a build system

    ...........

    ...........

    [300/314] Generating linker.cmd
    [301/314] Generating isr_tables.c, isrList.bin
    [302/314] Generating dev_handles.c
    [303/314] Building C object zephyr/CMakeFiles/zephyr_final.dir/misc/empty_file.c.obj
    [304/314] Building C object zephyr/CMakeFiles/zephyr_final.dir/isr_tables.c.obj
    [305/314] Building C object zephyr/CMakeFiles/zephyr_final.dir/dev_handles.c.obj
    [306/314] Linking C executable zephyr\zephyr.elf
    Memory region Used Size Region Size %age Used
    FLASH: 223708 B 392704 B 56.97%
    SRAM: 112104 B 178968 B 62.64%
    IDT_LIST: 0 GB 2 KB 0.00%
    [307/314] Generating zephyr/mcuboot_primary_app.hex
    [308/314] Generating zephyr/mcuboot_primary.hex
    [309/314] Generating ../../zephyr/app_update.bin
    [310/314] Generating ../../zephyr/dfu_application.zip
    [311/314] Generating ../../zephyr/app_test_update.hex
    [312/314] Generating ../../zephyr/app_signed.hex
    [313/314] Generating ../../zephyr/app_moved_test_update.hex
    [314/314] Generating zephyr/merged.hex

    Culi@Culi-TOSH-I5 MINGW64 ~/ncs/v1.8.0/nrf/applications/asset_tracker_v2 ((v1.8.0))
    $

    Looks like something is going on with SES.

    The error in SES persists as follows:

    Checking ‘mcuboot/zephyr/zephyr.hex’

    modules/mcuboot/mcuboot_subimage-prefix/src/mcuboot_subimage-stamp/mcuboot_subimage-build does not exist.

    Combining ‘mcuboot/zephyr/zephyr.hex’

    [WinError 2] The system cannot find the file specified

    What do you think?

    Regards,

    Neculai

  • 0

    Thanks a lot for your feedback, Neculai.

    Neculai said:
    Looks like something is going on with SES.

    Yes, your toolchain setup appears to be correct at least, which is good. How does your nRF Connect Options window in SES look like? Can you share a print screen?

    Regards,

    Markus

  • 0
    Neculai said:
    I'm attaching two screenshots ...

    Thank you, Neculai!

    Your GNU ARM Embedded Toolchain Directory appears to be incorrect. It should be something like C:/gnuarmemb/version-folder.

    Regards,

    Markus

Related
Terms of service