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

[Jeffery]

Hi 

As title. Thanks.

Jeffery

[Jeffery]

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.

West vs. SES.docx

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. 

[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

[Jeffery]

Hi

The error log was already posted at previous mail. 

Could you check it with your internal team. 

As NRF5340, if bluetooth sample at application core and RPMsg at network core, could it support changing tx power at application core?

Thanks.

[Priyanka]

Hi,

I am looking into this and will get back to you by next week.

-Priyanka

[Jeffery]

Hi Priyanka

Thanks. I also tested hci_pwr_ctrl at ncs 1.9.0.

This issue still existed. Wait for your checking.

Jeffery