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

nrfx.h: No such file or directory

Hi,

I am coming accoss an issue while running the LLPM Sample example from http://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.2.0/nrf/samples/bluetooth/llpm/README.html on nRF52. The issue being "nrfx.h: No such file or directory". Any help would be appreciated. I have attached screenshot below and output transcript. 

Output is as follows:

Building ‘zephyr/include/generated/driver-validation.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/CMakeFiles/driver_validation_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/driver_validation_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/kobj-types-enum.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/otype-to-str.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/CMakeFiles/kobj_types_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/kobj_types_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘C:/Users/production/ncs/v1.2.0/zephyr/include/dt-bindings/gpio/gpio.h’ from solution ‘build’ in configuration ‘Common’
Building ‘C:/Users/production/ncs/v1.2.0/zephyr/include/dt-bindings/i2c/i2c.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/misc/generated/syscalls.json’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_list.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/CMakeFiles/syscall_list_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_dispatch.c’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/syscall_list_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_offsets’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj’ from solution ‘build’ in configuration ‘Common’
1> Compiling ‘offsets.c’
1> In file included from C:/Users/production/ncs/v1.2.0/zephyr/include/arch/arm/aarch32/cortex_m/cmsis.h:17,
1> from C:/Users/production/ncs/v1.2.0/zephyr/include/arch/arm/aarch32/cortex_m/mpu/arm_mpu_v7m.h:10,
1> from C:/Users/production/ncs/v1.2.0/zephyr/include/arch/arm/aarch32/cortex_m/mpu/arm_mpu.h:13,
1> from C:/Users/production/ncs/v1.2.0/zephyr/include/arch/arm/aarch32/arch.h:248,
1> from C:/Users/production/ncs/v1.2.0/zephyr/include/arch/cpu.h:17,
1> from C:/Users/production/ncs/v1.2.0/zephyr/include/kernel_includes.h:34,
1> from C:/Users/production/ncs/v1.2.0/zephyr/include/kernel.h:17,
1> from C:/Users/production/ncs/v1.2.0/zephyr/arch/arm/core/offsets/offsets.c:25:
1> C:/Users/production/ncs/v1.2.0/zephyr/soc/arm/nordic_nrf/nrf52/soc.h:16:10: fatal error: nrfx.h: No such file or directory
1> compilation terminated.
Build failed

Parents Reply
  • Hi,

     

    I tried with both the "toolchain manager" (in nRF connect for desktop), and manually with tag v1.2.0, and I am unfortunately unable to reproduce the error you're seeing.

    Are you using the toolchain manager, or have you manually checked out using west? If using the manual way, could you ensure that "west update" is called from the ncs/nrf directory (just in case some repos have not been updated properly)?

     

    Kind regards,

    Håkon

Children
Related