How to resolve a build error in Zephyr while building the Edge Impulse precompiled sample for Thingy 53.

Hi

I was working on an application sample for some days named "Machine learning" which is located at nrf/application, but facing a huge amount of issues connecting the board to edge impulse studio.

So while searching for the answer I found  https://devzone.nordicsemi.com/f/nordic-q-a/93706/nrf-edge-impulse/394830 this ticket, and in this ticket, they have given "edge impulse precompiled for thingy53", link of that is https://github.com/edgeimpulse/firmware-nordic-thingy53 

1. Should I need to use this sample instead of a machine learning sample for working with edge impulse?

I have downloaded and tried to create a build using this sample, but I am facing a build error 

D:/firmware/zephyr/drivers/ipm/ipm_nrfx_ipc.c: In function 'vipm_nrf_0_set_enabled':
D:\firmware\zephyr\include\devicetree.h:305:40: error: 'DT_N_INST_0_nordic_nrf_ipc_IRQ_IDX_0_VAL_irq' undeclared (first use in this function)

D:/firmware/zephyr/drivers/ipm/ipm_nrfx_ipc.c: In function 'gipm_init':
D:\firmware\zephyr\include\devicetree.h:305:40: error: 'DT_N_INST_0_nordic_nrf_ipc_IRQ_IDX_0_VAL_priority' undeclared (first use in this function)

I have not made any changes to the sample and I am unsure why this error is occurring in the default sample.

Can you help me resolve this issue?

Parents Reply Children
  • When I tried to fire the command "edge-impulse-daemon", the following messages and errors came up.

    Microsoft Windows [Version 10.0.22621.1105]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\Users\sachi>edge-impulse-daemon
    Edge Impulse serial daemon v1.17.0
    Endpoints:
        Websocket: wss://remote-mgmt.edgeimpulse.com
        API:       https://studio.edgeimpulse.com
        Ingestion: https://ingestion.edgeimpulse.com
    
    ? Which device do you want to connect to? COM17 (Microsoft)
    [SER] Connecting to COM17
    [SER] Serial is connected, trying to read config...
    [SER] Retrieved configuration
    [SER] Device is running AT command version 1.0.0
    
    Setting upload host in device...Error while setting up device Error: Failed to set upload host: p
        at EiSerialProtocol.setUploadHost (C:\Users\sachi\AppData\Roaming\npm\node_modules\edge-impulse-cli\build\shared\daemon\ei-serial-protocol.js:298:19)
        at async setupWizard (C:\Users\sachi\AppData\Roaming\npm\node_modules\edge-impulse-cli\build\cli\daemon.js:601:17)
        at async SerialConnector.connectLogic (C:\Users\sachi\AppData\Roaming\npm\node_modules\edge-impulse-cli\build\cli\daemon.js:478:17)
    [SER] Cannot connect to remote management API using daemon, failed to read apiKey, deviceId or deviceType from device. Restarting your development board might help. Retrying in 5 seconds...
    [WS ] Connecting to wss://remote-mgmt.edgeimpulse.com
    [WS ] Connected to wss://remote-mgmt.edgeimpulse.com
    [WS ] Failed to authenticate, API key not correct? Missing deviceId

    But I have already added the API key as cmake argument, and changed the project ID on the URI as well.

  • Hello, 

    Using the out-of-box configuration of nRF Machine Learning, built for the Thingy:53 and connecting it to my nRF52840DK running Bluetooth: Central UART, I get the following output when connecting to Edge Impulse

    Note that I have tested the connection in the background to a PuTTy terminal to verify data. This is enabled by long pressing the button on the Thingy:53 putting it in Data Forwarder modus.

    Do you have a user on Edge Impulse Studio? If so, do you have a project to where you have collected data and trained your model? Adding the API in your project should download this model and add to your project.


    What version of nRF Connect SDK are you running?

    Kind regards,
    Øyvind

  • I get the following output when connecting to Edge Impulse

    Fabulous, This is what I want. 

    Okay, now I know what will be successful connectivity will look like.

    Please help me more by by sharing

    1. What are the complete steps or add on you have done in the default sample, so that you are not facing the error like API key, deviceID and devicetype.

    2. Please share your prj.conf, and show me the actual line what you have passed as an cmake argument for API key(you can make this ticket private in order to share the confidential  data but I need the actual thing)

    Do you have a user on Edge Impulse Studio?

    Yes, I have and it is private account.

    If so, do you have a project to where you have collected data and trained your model?

    Yes, I named it as 

    What version of nRF Connect SDK are you running?

    ncs v1.9.1

    This is what I get when I tried 

    Your assistance would be greatly valued.

  • Hello, 

    Unknown said:
    1. What are the complete steps or add on you have done in the default sample, so that you are not facing the error like API key, deviceID and devicetype.

    I built the application following the documentation. No alteration done to the application. 

    Unknown said:
    2. Please share your prj.conf, and show me the actual line what you have passed as an cmake argument for API key(you can make this ticket private in order to share the confidential  data but I need the actual thing)

    Please see your applicaiton.

    Unknown said:
    ncs v1.9.1

    I used v2.2.0. Is there a reason for using v1.9.1?

    -Øyvind

Related