Unable to configure TX_PWR in project config when building #217
-
|
Has anyone run into an issue where they can't set the transmit power in the project config due to "Missing dependencies" in VSCode? I'm running nRF SDK/Toolchain v2.5.0, although I had the same issue when running @ v2.7.0 and v2.3.0. I've linked screenshots of the compile warnings and my current build config. Also I'm using this module, if that is relevant at all. Any help would be appreciated, thanks!
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Hey @francisliardet. Unfortunately I cannot reproduce the issue. I just double checked and we do have some recent clean builds on With the |
Beta Was this translation helpful? Give feedback.
-
|
Heya, thanks for the reply! So I've done a few things and still haven't managed to quash that warning unfortunately:
On that last point I managed to get rid of the I think I'll set up a new, clean workspace on my laptop and try again - I'm hoping I've just busted something locally through all of the version changes and SDK updates. If I were to start fresh, what version of Toolchain + SDK + b-parasite repo would be the most reliable?
|
Beta Was this translation helpful? Give feedback.
-
|
Tks for the update. I think for now the 2.5 SDK/toolchain is the way to go. I noticed from the screenshot that you're on windows. I wonder if there's something odd going on with the extension there. Could you paste the full log from a 2.5 pristine build? If you have time, could you try building it with docker instead? I'd be curious to see if the error goes away. I hope I can finish the port to 2.7 when I'm back home in a week, but until then the 2.5 is the latest, most battle tested one. |
Beta Was this translation helpful? Give feedback.
-
|
So, it looks like it may have been a false alarm all along... I managed to build everything using Docker successfully (using 2.5 SDK) and the functional range didn't change at all, even after what I had assumed was a 8db boost. I did some tests building the firmware in both Docker and VSCode, changing the transmit power in the config each time, switching between +8db, +0db (no config), and -8db. As you can see, both Docker and VSCode gave the exact same result as measured via the "Signal Strength" HA entity, even though VSCode was consistently giving me warnings that my configuration wasn't making it through to the build. Given these results, I'm pretty confident in assuming those warnings are total BS, and everything is totally fine, so I'll just ignore those messages for now and pretend everything is working normally!
|
Beta Was this translation helpful? Give feedback.
-
|
Nice, I'm glad to hear. That's a nice visualization too. Happy hacking! |
Beta Was this translation helpful? Give feedback.
So, it looks like it may have been a false alarm all along...
I managed to build everything using Docker successfully (using 2.5 SDK) and the functional range didn't change at all, even after what I had assumed was a 8db boost.
I did some tests building the firmware in both Docker and VSCode, changing the transmit power in the config each time, switching between +8db, +0db (no config), and -8db.
As you can see, both Docker and VSCode gave the exact same result as measured via the "Signal Strength" HA entity, even though VSCode was consistently giving me warnings that my configuration wasn't making it through to the build.
Given these results, I'm pretty confident in assuming those warning…