• State Verified Answer
  • Replies 10 replies
  • Subscribers 69 subscribers
  • Views 139 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 338361
Options

Unable to create a working example

Ros

Hi,

I was using nRF products a while ago, and now coming back to the platform again. However, it looks like everything has been changed with the nRF connect.

Anyway, I installed nRF SDK, but not in the default location for Windows 10, now the nRF tool chain manager cannot open the SDK and I cannot find a setting to change the location, this is the problem 1.

Therefore, I opened the VS code with nRF connect extension installed, and tried to create a new application (Under welcome -> create a new application -> copy a sample) based on a zypyre/blinky.

Used scan the kits to configure/select the kit but nothing happened, note that the development board is connected.

Since nothing happened, I try to configure west (step 7) in the following link

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/create_application.html

It took considerable amount of time again to fetch various repos when I click "West Update".

After that the next step is configure and build system which is pointed to this page.

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/config_and_build/index.html#configuration-and-build

which needs another PhD to understand the whole but to blink an LED.

Parents Reply
  • 0 in reply to Øyvind

    I was configuring a build using the sysbuild option (which is the default), and I had to select my_app under APPLICATIONS -> my_app -> build -> my_app to remove warnings from IntelliSense. This setup is fine, but with this selection, when I build or debug (using the icons under ACTIONS), the build does not include the latest changes from main.c. I figured this out after spending almost an entire day, as my debug session would not start.

    However, if I select APPLICATIONS -> my_app -> build, then building and debugging work fine, but it shows warnings in the code, as well as issues stating that the GPIO driver must be enabled. When I enable the GPIO configuration in prj.conf, I get a warning indicating that GPIO drivers are enabled in multiple locations.

    (I got the build works with a blank prj.conf, which was the default).


    This entire process was very frustrating, as I spent too much time debugging the IDE setup instead of focusing on actual development.

    For now, I think I should avoid using sysbuild.

Children
  • 0 in reply to Ros
    Ros said:
    When I enable the GPIO configuration in prj.conf, I get a warning indicating that GPIO drivers are enabled in multiple locations.

    Are you referring to the "Problems" tab in VS Code? We are aware of this and are working on the issue. What you should focus on is the output from the build log, which is shown under Terminal when you click on the blue highlighted text in the pop-up, in this case Sysbuild. 

    Ros said:
    I got the build works with a blank prj.conf, which was the default

    What exactly did you add to the prj.conf to make it fail to build?

    What board are you connecting to?

  • 0 in reply to Øyvind

    That warning can be ignored, but the real problem was this:

    ```

    I was configuring a build using the sysbuild option (which is the default), and I had to select my_app under APPLICATIONS -> my_app -> build -> my_app to remove warnings from IntelliSense. This setup is fine, but with this selection, when I build or debug (using the icons under ACTIONS), the build does not include the latest changes from main.c.

    ```

    So I cannot start debug, or when starting it goes to some asm files.

    Then documentation says, I have to set CONFIG_GPIO=y, but it seems works without this settings.

Related