Attachments (3) Download All
Nordic Case Info
  • Case ID: 314569
Options

nrf-connect.boardRoots does not work. Custom board are not picked up.

jakkra

Hi, in the video you can see:

1. Me first removing/re-adding the application by editing .vscode/settings.json just to verify the plugin is picking up the settings.json file.

2. Then I try to create a new build configuration, but my custom boards are not there.

3. I show the folder structure that I have boards in app/boards correctly.

I have also tried using the "Create a new board", but those are not either picked up.

Also tried on Linux, but same there. Attached generated support info.

Tried re-installing the plugin.


Fullscreen 2084.debug_log.json Download

Parents
  • 0

    Hi jakkra,

    I'm sorry if things have taken more time than you might expect. I probably ran more tests than I should have, but I got some interesting results.

    First of all, I unfortunately cannot reproduce your issue. Are you by any chance working on a Workspace Application?

    My tests are with a standalone application. However, if there are any differences in the behavior, you should still be able to use the nRF Connect for VS Code extension settings to browse the available custom board.

    Below are my test logs and an attachment of my test setup. Could you please take a look at them and see if you can replicate the result.

    Hieu

  • 0 in reply to Hieu

    Hi thank you very much, I'm indeed using a workspace application. I'll take a look at your tests and try to replicate them. I'll get back to you.

    root

        -.vscode

            -setting.json (with boardRoots set to  ["${workspaceFolder}/app)]

        -app

            -boards/arm/custom_board

            - west.yml

            - zephyr

            ...

    I'll try creating a minimal reproduceable sample. 

  • 0 in reply to jakkra

    By the way, I realized that my notes might appear cryptic. Here is some information:

    I have three different "board root" folders to test with:
    - test_folder_settings_board_root
    - test_user_settings_board_root
    - test_workspace_settings_board_root

    They are completely out of tree and outside of the application folder.

    Here are the three settings location in VS Code that I tested with:

    - User Settings: Opened by Ctrl+P > Preferences: Open User Settings (JSON)
    - Folder Settings: When opening a folder, the settings is in <folder>/.vscode/settings.json
    - Workspace Settings: When opening a VS Code Workspace, the settings is in the same .code-workspace file.

  • 0 in reply to Hieu

    Hi   I have now a full reproduceable sample for you to try.

    Follow the instructions in the README.md

    You may need to change in settings.json the path to windows style if you are on Windows.

    "${workspaceFolder}/app" =>  "${workspaceFolder}\\app"
Reply
  • 0 in reply to Hieu

    Hi   I have now a full reproduceable sample for you to try.

    Follow the instructions in the README.md

    You may need to change in settings.json the path to windows style if you are on Windows.

    "${workspaceFolder}/app" =>  "${workspaceFolder}\\app"
Children
  • 0 in reply to jakkra

    correct_test_app.zip

    Uploaded wrong .zip, now it's the correct one. Find README inside

  • 0 in reply to jakkra

    Hi jakkra,

    I fell sick over the weekend and will have to be away for a few days. My apologies, but I will return to support you as soon as I can.

    Meanwhile, could you please let me know, do none of the methods I described work for your project setup? What about on a completely independent setup?

  • 0 in reply to Hieu

    Hi thank you, no problem. I did not test all scenarious you listed, but during the last few days I have been jumping back and forth building samples, different applications and so on and for those custom boards seems to work.

    However it's this specific folder setup that does not work (and I think it should, correct me if I'm wrong), and I have attached a sample in my previous post for you to confirm it's not working for you either.

    If I change project setup, for example don't use a west workspace, i.e. removing west.yml and never running west update, my structure works. But I really would like to have this folder structure as you can se in my previous post. 

    Get well.

Terms of service