nRF Connect SDK v.1.5.0 : How/Where to change PHY and TX power for long range application

[Mickael_Marport]

Hello 

I'm using nRF5340 DK with nRF Connect SDK 1.5.0 and SES IDE and I want to change the PHYs and TX power of the peripheral_uart sample (v1.5.0\nrf\samples\bluetooth\peripheral_uart) to switch to the long range configuration. The problem is, with this version of nRF Connect SDK, I do not know where to write to change these parameters.

I flashed peripheral_uart in the core application and hci_rpmsg in the network core

I tried to look for answers in the forum but, unless I'm mistaken, I couldn't find any answer because all the cases in the forum are based on the old versions of the SDK and none on the new one (nRF Connect SDK 1.5.0).

Can someone please enlighten me on this :)

Any help is welcome

Thanks

Mickael 

[JONATHAN LL]

Hi Mickael,

There is a similar question here: (+) How to config nrf5340 tx power? - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

As far as i am aware implementing the hci_pwr_ctrl example should work, but i have not tested this myself.

Regards,
Jonathan

[Mickael_Marport]

Hi Jonathan

thank you for responding ! 

But I have further questions : 

Should I modify prj.conf for peripheral_uart sample AND hci_rpmsg sample to increase TX power?

And to change PHY I have to do the same? I.e. modify the prj.conf for both samples?  but for peripheral_uart, I have prj.conf and prj_minimal.conf, which one should I modify? 

Sorry if sometimes my questions seem far-fetched, I'm a bit confused about this net core and app core stuff and with this new nRF Connect SDK :)

Thanks

[Sigurd]

Hi,

You don't need to build hci_rpmsg manually, it will be built as a child-image when you build a bluetooth sample for nRF5340. To configure the hci_rpmsg image, create a hci_rpmsg.conf and put it into a child_image folder.

E.g. like shown in the attached sample here:

peripheral_uart_coded.rar

The sample works fine here, and I can see it advertise using Coded PHY.

Here is my hex file(combined app&hci_rpmsg image)8130.merged_domains.hex

If you can't see it advertise after programming the hex file, then try to press the RESET button on the DK.

[Mickael_Marport]

Hi Sigurd, 

8130.merged_domains.hex works fine, I flashed it with nRF Connect -> Programmer.

For peripheral_uart_coded.rar, I opened it with SES through nRF Connect -> Toolchain Manager 

i chose the nrf5340_cpuapp, (before flashing, I erased all the memory with nRF Connect -> Programmer.) I flashed with SES : Build -> Build and Run but it doesn't work, I think I'm doing it the wrong way because if 8130.merged_domains.hex works, there is no reason why peripheral_uart_coded.rar should not work

Thanks, 

[Sigurd]

Hi,

Maybe you did not program the network core?

See this link: http://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/nrf/ug_nrf5340.html#building-and-programming-a-sample

Maybe the easiest approach is to program it with nrfjprog. (it can be done from within SES as well, although maybe a bit more cumbersome).

nrfjprog -f NRF53 --coprocessor CP_NETWORK --program your_buid_folder\hci_rpmsg\zephyr\zephyr.hex --chiperase

[KarthikKumar]

Hi Michael_Marpot,

I used the peripheral_uart_coded.rar code, but when tried to flash it on the nRF5340-DK board there is an error been prompted as     invalid use of undefined type 'struct bt_conn'.  what might be the issue.

I'm using SDK v1.8.0 and Visual studio code.

Regards

Karthik Kumar

[JONATHAN LL]

Hi Kumar,
Could you create a new Devzone ticket asking for help, and link to this case as a similar problem?

And include some details on you work environment.

Regards,
Jonathan