nRF Connect - Changes to prj.conf not shown in autoconf.h even after Project reload.

RE: nRF Connect - Changes to prj.conf not shown in autoconf.h even after Project reload.

HillRipper21 — Thu, 21 Oct 2021 14:15:32 GMT

Ah, the last reply made me realize my mistake. I was looking in wrong path the whole time and I was changing the prj.conf for the wrong example. In case anyone else runs into this, there are 2 spots where the example can be:

1. ...\ncs\v1.6.1\zephyr\samples\bluetooth\direction_finding_connectionless_tx

or 2. ...\ncs\v1.6.1\nrf\samples\bluetooth\direction_finding_connectionless_tx

I didn't realize the 2nd path existed since I was only looking at the Zephyr documentation which told me to work from the first path. Thanks for the help.

RE: nRF Connect - Changes to prj.conf not shown in autoconf.h even after Project reload.

Priyanka — Wed, 20 Oct 2021 09:03:15 GMT

Hi,

1. Now you might see a folder as shown below called 'build' or 'build_nrf52833dk_nrf52833' or something similar. First, manually delete this folder from here.

If there is no such folder then good, let's begin with the next step.

2. Next, Set the CONFIG_BT_DEVICE_NAME to "DF Connectionless Beacon App 1" and then, go to the nRF Connect -> Toolchain Manager and choose 'Open Command Prompt'

3. This opens west and you can navigate to you folder location to where the direction_finding_connectionless_tx is, for eg, I used '' cd C:\NCS\v1.7.0\nrf\samples\bluetooth\direction_finding_connectionless_tx'' command since this is my path.

Then enter the command ''west build -b nrf52833dk_nrf52833''.

Now try checking the autoconf.h file. You should see "DF Connectionless Beacon App 1" in autoconf.h.

4. Now again do step 1.

5. Next, Set the CONFIG_BT_DEVICE_NAME to "DF Connectionless Beacon App 2" and then build using SES (which you already have experience doing)

6. Check the autoconf.h file. You should see "DF Connectionless Beacon App 2" in autoconf.h

7. Next, Change CONFIG_BT_DEVICE_NAME to "DF Connectionless Beacon App 3". Build again, but don't delete the build folder, just do a clean build.

You should see "DF Connectionless Beacon App 3" in autoconf.h

Hope this helps!

Regards,

RE: nRF Connect - Changes to prj.conf not shown in autoconf.h even after Project reload.

HillRipper21 — Tue, 19 Oct 2021 14:05:50 GMT

Can you please clarify where these build folders should be and which directories I should run the west command from? I have been using SES to build everything so I am not sure where these build folders should be. I do not see them in the direction_finding_connectionless_tx folder

RE: nRF Connect - Changes to prj.conf not shown in autoconf.h even after Project reload.

Priyanka — Tue, 19 Oct 2021 13:09:27 GMT

Hi,

Could you try the following steps to verify exactly where it fails:

Set CONFIG_BT_DEVICE_NAME to "DF Connectionless Beacon App 1"
Delete the build folder manually
Test with the command line (open it through Toolchain Manager)
west build -b nrf52833dk_nrf52833
You should see "DF Connectionless Beacon App 1" in autoconf.h
If that works, manually delete build (delete all build folders, both 'build' and 'build_nrf52833dk_nrf52833') folder and set CONFIG_BT_DEVICE_NAME to "DF Connectionless Beacon App 2"
Then build again using SES
You should see "DF Connectionless Beacon App 2" in autoconf.h
Change CONFIG_BT_DEVICE_NAME to "DF Connectionless Beacon App 3"
Build again, but don't delete the build folder, just do a clean build
You should see "DF Connectionless Beacon App 3" in autoconf.h

Regards,

RE: nRF Connect - Changes to prj.conf not shown in autoconf.h even after Project reload.

HillRipper21 — Tue, 19 Oct 2021 02:22:19 GMT

Hi sorry for the late response was away for a few days. The nRF Connect SDK version is 1.6.1 (required for compatibility with project) and I am on Windows 10. I did try the 'Clean Build Directory' but no luck there either. Thanks.

RE: nRF Connect - Changes to prj.conf not shown in autoconf.h even after Project reload.

Priyanka — Thu, 14 Oct 2021 09:14:21 GMT

Hi,

Could you tell me what is your nRF Connect SDK version and also, did you try selecting 'Clean Build Directory' when Opening the nRF Connect SDK Project?

Also, which OS are you trying this on? (Windows, MacOS or Linux)

Regards,

Priyanka