• State Verified Answer
  • Replies 3 replies
  • Subscribers 74 subscribers
  • Views 423 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 331731
Options

Building Thingy53 edge impulse FW with VSCode

OldFarmerHarmon

As instructed in the thingy53 getting started documentation I installed VSCode and the nrf Connect SDK extensions.  Using VScode I am able to build and run examples.

However I was unable to figure out how to build the Edge Impulse firmware (GitHub - edgeimpulse/firmware-nordic-thingy53: Official Edge Impulse firmware for Nordic Semiconductor Thingy:53) .

Subsequently I installed the nRF Connect SDK manually, using a different ncs folder than the vscode extension.  Using this installation I was able to build the FW.

Is the Edge Impulse FW buildable from VSCode?  How?

I have been using the Nordic Developer Academy courses and now see a failure with GUICONFIG launching from VSCode.

Is this because of the second installation? 

Regards

  • 0

    Hello, 

    unable to figure out how to build the Edge Impulse firmware (GitHub - edgeimpulse/firmware-nordic-thingy53: Official Edge Impulse firmware for Nordic Semiconductor Thingy:53) .

    The Edge Impulse firmware is based on nRF Connect SDK v2.4.0. This is stated in e.g. the Dockerfile, where you can see it will download v2.4.0 with the following Docker command:

    RUN cd /ncs && west init -m https://github.com/nrfconnect/sdk-nrf --mr v2.4.0

    I can confirm that it does not build with e.g. v.2.6.1 but does build with v2.4.0 when testing here in the VS Code extension.

    Kind regards,
    Øyvind

  • 0 in reply to Øyvind

    I was able to build the code from a command line using the v2.4.0 SDK installed via VSCode extension.

    I will try to build it from within VSCode today.

  • +1 in reply to OldFarmerHarmon

    After building the Edge Impulse firmware from the command line I was able to open the app in VSCode.  I was then able to do a pristine build!

    Thew build configuration included the following overlay

    thingy53_nrf5340_cpuapp.overlay

    The build configuration included 4 extra CMake arguments

    -Dhci_rpmsg_OVERLAY_CONFIG="C:/ncs/v2.4.0/nrf/samples/common/mcumgr_bt_ota_dfu/rpmsg_child_image_overlay.conf;C:/ncs/v2.4.0/nrf/subsys/bootloader/image/secure_boot.conf;C:/ncs/v2.4.0/nrf/subsys/partition_manager/partition_manager_enabled.conf;C:/Nordic/EI/firmware-nordic-thingy53/child_image/hci_rpmsg.conf"

    -Dmcuboot_DTC_OVERLAY_FILE="C:/ncs/v2.4.0/nrf/modules/mcuboot/flash_sim.overlay"

    -Dmcuboot_OVERLAY_CONFIG="C:/ncs/v2.4.0/nrf/subsys/pcd/pcd.conf;C:/ncs/v2.4.0/nrf/subsys/partition_manager/ext_flash_mcuboot_secondary.conf;C:/ncs/v2.4.0/nrf/subsys/partition_manager/partition_manager_enabled.conf"

    -DCACHED_CONF_FILE="c:/Nordic/EI/firmware-nordic-thingy53/prj.conf;c:/Nordic/EI/firmware-nordic-thingy53/boards/thingy53_nrf5340_cpuapp.conf"

    Now I wonder If I can build the firmware without 1st building from the command line using these build configuration settings.

Related
Terms of service