Running Edge Impulse on nRF52840 in a custom board.

RE: Running Edge Impulse on nRF52840 in a custom board.

Øyvind — Fri, 10 Sep 2021 07:18:02 GMT

Hello,
Have you tried the answer you got in the other thread?
-Øyvind

RE: Running Edge Impulse on nRF52840 in a custom board.

mr_thomas — Wed, 08 Sep 2021 08:58:20 GMT

Hello Oyvind,

I ran into another issue in importing my Edge Impulse module into nRF52840,

Everything builds fine unless I change the URI in the prj.conf file, with the default URI out of the box, it builds fine.

When I change the project ID to the one I'm trying to import in the URI, it is throwing errors while it tries to download it.

I have created another thread if u want to have a look at the errors.

The documentation mentions we can just set an absolute path to the downloaded module, I tried that too, but it just throws a build error in SES.

Can you please help me out?

RE: Running Edge Impulse on nRF52840 in a custom board.

Øyvind — Thu, 26 Aug 2021 12:24:29 GMT

Thanks for verifying, Thomas. Happy to hear that it works now :)

Sounds like we need to improve the documentation on that part, to make it more clear.

Happy machine learning!

Kind regards,
Øyvind

RE: Running Edge Impulse on nRF52840 in a custom board.

mr_thomas — Thu, 26 Aug 2021 10:07:13 GMT

Got it! you were absolutely right, I didn't realize I was supposed to replace the "x-api-key" part with the actual name under name:api_key tab.

I was following the documentation u linked me in the beginning all along, perhaps it was too brief and ambiguous for me.

Thank you for your patience.

Regards,

Thomas.

RE: Running Edge Impulse on nRF52840 in a custom board.

Øyvind — Thu, 26 Aug 2021 09:42:48 GMT

I'm wondering if there is something off with the API key, and if there is a mismatch with our documentation that needs to be improved.

I was able to build the wrapper sample without issues, and I used name:api_key from Edge Impulse key tab:

-DEI_API_KEY_HEADER=name:api_key

RE: Running Edge Impulse on nRF52840 in a custom board.

mr_thomas — Thu, 26 Aug 2021 08:22:19 GMT

Hey thank you!, I am able to add the Header and was successful at creating the project.

But while building the default wrapper example as it is, I am facing a 401 Unauthorized error along with several others, I have shared my build logs in the previous comment.

RE: Running Edge Impulse on nRF52840 in a custom board.

Øyvind — Thu, 26 Aug 2021 08:14:53 GMT

I suppose converting this ticket to private, this way you can share the whole or more information on the -DEI_API_KEY_HEADER command.

RE: Running Edge Impulse on nRF52840 in a custom board.

mr_thomas — Wed, 25 Aug 2021 15:09:30 GMT

Hey, it worked! I was pulling my hairs trying to figure out what I was doing wrong. Nevermind, these things happen, haha.

Anyway, am I suppose to grant access for including the Impulse project into the NRF connect?

Because I got a few errors while building the project. Here are the logs:

Building ‘D:/Kshitij/ncs/v1.6.1/zephyr/include/dt-bindings/gpio/gpio.h’ from solution ‘build’ in configuration ‘Common’
Building ‘D:/Kshitij/ncs/v1.6.1/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’
  zephyr/misc/generated/syscalls.json does not exist.
  Combining ‘zephyr/misc/generated/syscalls.json’
Building ‘zephyr/misc/generated/struct_tags.json’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/CMakeFiles/parse_syscalls_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/parse_syscalls_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/driver-validation.h’ from solution ‘build’ in configuration ‘Common’
  zephyr/include/generated/driver-validation.h does not exist.
  Combining ‘zephyr/include/generated/driver-validation.h’
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’
  zephyr/include/generated/kobj-types-enum.h does not exist.
  Combining ‘zephyr/include/generated/kobj-types-enum.h’
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/include/generated/otype-to-size.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/kobj_types_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_list.h’ from solution ‘build’ in configuration ‘Common’
  zephyr/include/generated/syscall_dispatch.c does not exist.
  Combining ‘zephyr/include/generated/syscall_list.h’
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’
  zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj does not exist.
  Compiling ‘offsets.c’
Building ‘zephyr/offsets’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/offsets.h’ from solution ‘build’ in configuration ‘Common’
  zephyr/include/generated/offsets.h does not exist.
  Combining ‘zephyr/include/generated/offsets.h’
Building ‘zephyr/CMakeFiles/offsets_h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/offsets_h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/zephyr_generated_headers’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_app’ from solution ‘build’ in configuration ‘Common’
Building ‘app/libapp.a’ from solution ‘build’ in configuration ‘Common’
  CMakeFiles/app.dir/src/main.c.obj does not exist.
  Compiling ‘main.c’
  app\libapp.a does not exist.
  Archiving ‘libapp.a’
Building ‘cmake_object_order_depends_target_zephyr’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/libzephyr.a’ from solution ‘build’ in configuration ‘Common’
  zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf.c.obj does not exist.
  zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf_packaged.c.obj does not exist.
  zephyr/CMakeFiles/zephyr.dir/lib/os/crc32c_sw.c.obj does not exist.
  zephyr/CMakeFiles/zephyr.dir/lib/os/crc32_sw.c.obj does not exist.
  Compiling ‘cbprintf.c’
  Compiling ‘cbprintf_packaged.c’
  Compiling ‘crc32c_sw.c’
  Compiling ‘crc32_sw.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/crc16_sw.c.obj does not exist.
  zephyr/CMakeFiles/zephyr.dir/lib/os/crc8_sw.c.obj does not exist.
  zephyr/CMakeFiles/zephyr.dir/lib/os/crc7_sw.c.obj does not exist.
  zephyr/CMakeFiles/zephyr.dir/lib/os/dec.c.obj does not exist.
  Compiling ‘crc16_sw.c’
  Compiling ‘crc8_sw.c’
  Compiling ‘crc7_sw.c’
  Compiling ‘dec.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/fdtable.c.obj does not exist.
  Compiling ‘fdtable.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/hex.c.obj does not exist.
  Compiling ‘hex.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/notify.c.obj does not exist.
  Compiling ‘notify.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/printk.c.obj does not exist.
  Compiling ‘printk.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/onoff.c.obj does not exist.
  Compiling ‘onoff.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/rb.c.obj does not exist.
  Compiling ‘rb.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/sem.c.obj does not exist.
  Compiling ‘sem.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/thread_entry.c.obj does not exist.
  Compiling ‘thread_entry.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/timeutil.c.obj does not exist.
  Compiling ‘timeutil.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/heap.c.obj does not exist.
  Compiling ‘heap.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/heap-validate.c.obj does not exist.
  Compiling ‘heap-validate.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/bitarray.c.obj does not exist.
  Compiling ‘bitarray.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf_complete.c.obj does not exist.
  Compiling ‘cbprintf_complete.c’
  zephyr/CMakeFiles/zephyr.dir/lib/os/reboot.c.obj does not exist.
  Compiling ‘reboot.c’
  zephyr/CMakeFiles/zephyr.dir/misc/generated/configs.c.obj does not exist.
  Compiling ‘configs.c’
  zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/validate_base_addresses.c.obj does not exist.
  Compiling ‘validate_base_addresses.c’
  zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/validate_enabled_instances.c.obj does not exist.
  Compiling ‘validate_enabled_instances.c’
  zephyr/CMakeFiles/zephyr.dir/subsys/cpp/cpp_init_array.c.obj does not exist.
  Compiling ‘cpp_init_array.c’
  zephyr/CMakeFiles/zephyr.dir/subsys/cpp/cpp_ctors.c.obj does not exist.
  Compiling ‘cpp_ctors.c’
  zephyr/CMakeFiles/zephyr.dir/subsys/cpp/cpp_dtors.c.obj does not exist.
  Compiling ‘cpp_dtors.c’
  zephyr/CMakeFiles/zephyr.dir/subsys/pm/power.c.obj does not exist.
  Compiling ‘power.c’
  zephyr/CMakeFiles/zephyr.dir/subsys/pm/pm_ctrl.c.obj does not exist.
  Compiling ‘pm_ctrl.c’
  zephyr/CMakeFiles/zephyr.dir/subsys/pm/policy/policy_residency.c.obj does not exist.
  Compiling ‘policy_residency.c’
  zephyr/CMakeFiles/zephyr.dir/drivers/console/uart_console.c.obj does not exist.
  Compiling ‘uart_console.c’
  zephyr/CMakeFiles/zephyr.dir/drivers/clock_control/clock_control_nrf.c.obj does not exist.
  Compiling ‘clock_control_nrf.c’
  zephyr/CMakeFiles/zephyr.dir/drivers/timer/sys_clock_init.c.obj does not exist.
  Compiling ‘sys_clock_init.c’
  zephyr/CMakeFiles/zephyr.dir/drivers/timer/nrf_rtc_timer.c.obj does not exist.
  zephyr/CMakeFiles/zephyr.dir/D_/Kshitij/ncs/v1.6.1/nrfxlib/crypto/nrf_cc310_platform/src/nrf_cc3xx_platform_abort_zephyr.c.obj does not exist.
  Compiling ‘nrf_rtc_timer.c’
  Compiling ‘nrf_cc3xx_platform_abort_zephyr.c’
  zephyr/CMakeFiles/zephyr.dir/D_/Kshitij/ncs/v1.6.1/nrfxlib/crypto/nrf_cc310_platform/src/nrf_cc3xx_platform_mutex_zephyr.c.obj does not exist.
  Compiling ‘nrf_cc3xx_platform_mutex_zephyr.c’
  zephyr\libzephyr.a does not exist.
  Archiving ‘libzephyr.a’
Building ‘D:/Kshitij/ncs/v1.6.1/zephyr/misc/empty_file.c’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_..__nrf__drivers__hw_cc310’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_..__nrf__lib__fatal_error’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_arch__arm__core__aarch32’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_arch__arm__core__aarch32__cortex_m’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_arch__arm__core__aarch32__mpu’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_isr_tables’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_arch__common’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_drivers__gpio’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_drivers__serial’ from solution ‘build’ in configuration ‘Common’
Building ‘edge_impulse/src/edge_impulse_project-stamp/edge_impulse_project-mkdir’ from solution ‘build’ in configuration ‘Common’
  edge_impulse/src/edge_impulse_project-stamp/edge_impulse_project-mkdir does not exist.
  Combining ‘edge_impulse/src/edge_impulse_project-stamp/edge_impulse_project-mkdir’
Building ‘edge_impulse/src/edge_impulse_project-stamp/edge_impulse_project-download’ from solution ‘build’ in configuration ‘Common’
  edge_impulse/src/edge_impulse_project-stamp/edge_impulse_project-download does not exist.
  Combining ‘edge_impulse/src/edge_impulse_project-stamp/edge_impulse_project-download’
    downloading 'http://studio.edgeimpulse.com/v1/api/33126/deployment/download?type=zip&modelType=int8' failed
    401 Unauthorized
    downloading 'http://studio.edgeimpulse.com/v1/api/33126/deployment/download?type=zip&modelType=int8' failed
    401 Unauthorized
    downloading 'http://studio.edgeimpulse.com/v1/api/33126/deployment/download?type=zip&modelType=int8' failed
    401 Unauthorized
    downloading 'http://studio.edgeimpulse.com/v1/api/33126/deployment/download?type=zip&modelType=int8' failed
    401 Unauthorized
    downloading 'http://studio.edgeimpulse.com/v1/api/33126/deployment/download?type=zip&modelType=int8' failed
    401 Unauthorized
    downloading 'http://studio.edgeimpulse.com/v1/api/33126/deployment/download?type=zip&modelType=int8' failed
    401 Unauthorized
Build failed

RE: Running Edge Impulse on nRF52840 in a custom board.

Øyvind — Wed, 25 Aug 2021 13:15:09 GMT

My sincerest apologies for causing this issue for you, I see now that I was missing one small part: -DEI_API_KEY_HEADER

Please retry and let me know how that works for you.

RE: Running Edge Impulse on nRF52840 in a custom board.

mr_thomas — Wed, 25 Aug 2021 09:21:41 GMT

Hey! I did try this.

But I get this error:

CMake Error: The source directory "D:/Kshitij/v1.6.1/nrf/samples/edge_impulse/wrapper/build_nrf52840dk_nrf52840/-EI_API_KEY_HEADER=x-api-key:xxxxxxx<my-apikey>xxxxxxx" does not exist.

I did follow the documentation line by line and did as instructed.

RE: Running Edge Impulse on nRF52840 in a custom board.

Øyvind — Fri, 20 Aug 2021 12:17:54 GMT

Hello,

Make sure that you have Segger Embedded Studio Nordic Edition, which can download from here. Then click on File -> Open nRF Connect SDK.

Hope this helps.

Kind regards,
Øyvind

RE: Running Edge Impulse on nRF52840 in a custom board.

mr_thomas — Fri, 20 Aug 2021 09:11:21 GMT

Hey, yes I did find my API keys, my question is how do I add the key to the Cmake option 'EI_API_KEY_HEADER '.

I mean should I define it as:

"EI_API_KEY_HEADER=x-api-key:aaaabbbbccccdddd" in the global Cmake option as per instructions in here.

I'm just confused on where and how to add it in Segger Embedded Studio.

RE: Running Edge Impulse on nRF52840 in a custom board.

Øyvind — Fri, 20 Aug 2021 06:53:50 GMT

Hello, have a look at step two of Downloading model directly from Edge Impulse Studio. It states:
You can access your API keys under the Keys tab in the Edge Impulse project dashboard.

RE: Running Edge Impulse on nRF52840 in a custom board.

mr_thomas — Thu, 19 Aug 2021 13:40:08 GMT

Hey, Thank you for your response! This is really helpful.

Another doubt I am having following the steps in documentation you linked is adding the API key to the project.

After I add an additional cmake option 'EI_API_KEY_HEADER ' as per instructions.

How do I define it with my own API key?

RE: Running Edge Impulse on nRF52840 in a custom board.

Øyvind — Wed, 18 Aug 2021 11:47:28 GMT

Hello,

Please see our nRF Connect SDK documentation on Using Edge Impulse.

Kind regards,
Øyvind