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

SEGGER EMBEDDED STUDIO, ERROR offsets.c.obj

Hi!

I'm currently setting up the nRF9160 dev kit for development and are having some trouble with "building" the asset tracking application.

Building ‘zephyr/include/generated/driver-validation.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/driver-validation.h’
Building ‘zephyr/include/generated/kobj-types-enum.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/kobj-types-enum.h’
Building ‘zephyr/include/generated/otype-to-str.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/misc/generated/syscalls.json’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/misc/generated/syscalls.json’
Building ‘zephyr/include/generated/syscall_list.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/syscall_list.h’
Building ‘zephyr/include/generated/syscall_dispatch.c’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_macros.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/syscall_macros.h’
Building ‘zephyr/include/generated/offsets.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/offsets.h’
1> Traceback (most recent call last):
1> File "C:/programvare/nrfsemi/ncs/zephyr/scripts/gen_offset_header.py", line 72, in <module>
1> input_file = open(args.input, 'rb')
1> FileNotFoundError: [Errno 2] No such file or directory: 'C:/programvare/nrfsemi/ncs/nrf/applications/asset_tracker/build/zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj'
Build failed

Any clues on what can cause this error message?

I'm using master branch.

Regards,

David

  • Hi, and sorry for the very late reply, but when a question has a "verified answer" it no longer appears in my queue.

    The nRF9160 can be in both secure and non-secure state. To communicate with the modem, it has to be non-secure, so you always* want to build the application as non-secure.

    When you build your application, the "Secure Partition Manager" (SPM) also gets built. To do its job, it needs to be running in the secure domain. That is why it changes the board.

    Regarding your missing options and failure to build in SES, I recommend you open a new case, so that we get notified about updates.

    Best regards,

    Didrik

    *There are some situations where you might want your application to be in the secure domain, but these are mostly related to peripherals not configured by the SPM. If you want to use the modem or are unsure, use non-secure.

Related