Failed to get/set TX power to NRF5340 as \v1.8.0\zephyr\samples\bluetooth\hci_pwr_ctrl

If I tried NRF52840, it's ok to get/set TX power. 

Hi Priyanka

I tested github hci_pwr_ctrl sample you shared to me. Copied this sample at SDK Connect folder

( \TOOLCHAIN\v1.8.0\zephyr\samples\bluetooth)

Then, compiled this sample with DK NRF52840 and DK NRF5340 both.

NRF52840 DK can work get/set TX power. 

NRF5340 DK cannot work get/set TX power.

TX power levels were selected {0, -8, -20} . Both IC can support this levels according to spec .

Please double check. Attachments are uart log results.

The log: Reboot DK--> Connected-->Disconnected.

Hi,

This sample is already available in the nRF Connect SDK:

Also, when building with the nRF5340DK, you should flash this into the network core of the DK, i.e., nrf5340dk_nrf5340_cpunet

Regards,

Priyanka

Hi Priyanka

1.

Are you sure to flash hci_pwr_ctrl  to network core? Which core did you flash BLE controller?  It confused

me.  I did try flashing hci_pwr_ctrl at network cor and empty_app_core at application core. Then, no uart

log. Nothing works. It thinks wrong.

2.

At my test previously,

Network core: hci_rpmsg sample which included BLE controller.  Application core: hci_pwr_ctrl sample. 

These two cores used message handler to communicate. So, bluetooth can work. Uart log can work, too.

My only questions was NRF5340 cannot get/set TX power.

Could you mind checking this question internally for me? It took me much time to confirm this issue.

Jeffery

Hi Jeffery,

This looks strange as it did work for me. Could you try this through west? Just open the Toolchain manager and select the "Open Command prompt" and then navigate to your project file location.

Then try west build -b nrf5340dk_nrf5340_cpunet

followed by west flash 

Then you could take another DK which can be used to check the RSSI values obtained from the peripheral DK into which you flashed the hci_pwr_ctrl.

This DK could be nRF5340DK, nRF52840DK, etc but you should flash the RSSI viewer firmware into it first and then use the RSSI Viewer application in the nRF Connect for Desktop to view the RSSI measurements.

Hi 

1. WEST can work. TX power can be changed at NRF5340. Besides, I found SES also can work. The reason

    why  no uart log data out was that application core was empty. It shall flash empty_app_core at application

    core.

2. Below was from SDK Connect documentation. There are two options for BLE. RPMsg or RPC at network

    core. I chose RPMsg since all bluetooth examples can work at application core. Then, at peripheral_uart

    example,  I used set_tx_power and get_tx_power API from hci_pwr_ctrl to change 5340 tx power. But, it

    failed. 

Hi,

Glad that you are able to build the hci_pwr_ctrl sample. When you make the changes in peripheral_uart, what are the errors that you see?

-Priyanka

Hi,

Glad that you are able to build the hci_pwr_ctrl sample. When you make the changes in peripheral_uart, what are the errors that you see?

-Priyanka