BOARD_ROOT

[Bert Baselmans]

I am working with SDK v2.3.0 and a custom board with nRF9160

When I wanted to start my project again after some time, the build configuration had disappeared.

And creating a new one is no longer possible. While building the configuration, the following message appears:


 BOARD_ROOT element without a 'boards' subdirectory:

  /usr
  

But the west command has this option

-DBOARD_ROOT:STRING="c:/Repos/Nordic/YYYYY"

Apparently BOARD_ROOT is being overwritten. What could be the cause of that?

[runsiv]

Hi, 

This was a bit strange. So you can't see the old build config in VScode and you can't create a new one? And your custom pcb folder is located inside the project in a folder named boards? Just for the fun of it. If you just copy out your custom board folder, what happens then? 
Also, if possible, could you upload the project so I can try to replicate it?

Regards

Runar

[Bert Baselmans]

runsiv said:

So you can't see the old build config in VScode and you can't create a new one?

Correct

runsiv said:

And your custom pcb folder is located inside the project in a folder named boards?

Correct

runsiv said:

If you just copy out your custom board folder, what happens then? 

It still cannot find the board. My PC is used for another project. System settings may have been messed up. Reinstalling nRF Connect for Desktop makes no difference

Tryout2.3.zip

[Bert Baselmans]

Somehow the file C:\ncs\v2.3.0\.west\config got the cmake argument -DBOARD_ROOT="/usr"

I removed it and all works as before again

Thanks for your help

Bert

[runsiv]

Glad to hear it, I will just close the case. 

Have a nice weekend

Regards

Runar

[fiaerne]

It suggests using photo editing tools to paper io customize images to better fit the desired style and branding.

[goldfinchbig]

Does the other way around work btw? The v2 one programming the v3?

gorilla tag