Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 55 subscribers
  • Views 260 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2652P: any reason why radio transmit power is not persisted in NV in sample projects?

Zhiyong Li (FT)
Expert 2710 points
Part Number: CC2652P
Other Parts Discussed in Thread: Z-STACK

Hi,

I am going through the sample projects and noticed that although API exists to change transmit power, changed transmit power is not saved into NVS. The default value set in syscfg is loaded after a power cycle. I believe we can add a customized NV item and call the API to change it upon system startup.

zstack_sysSetTxPowerReq_t txPowerReq;
zstack_sysSetTxPowerRsp_t txPowerRsp;
txPowerReq.requestedTxPower = POWER_TEST_TX_PWR;
Zstackapi_sysSetTxPowerReq(appServiceTaskId, &txPowerReq, &txPowerRsp);

My question is: is there any special consideration that transmit power is handled separately from other system configurations such as panID etc.? Are we as users supposed set a desirable value at firmware cimpilation time and don't change it afterwards?

Please advise and thanks.

ZL

  • +1
    TI__Guru**** 208927 points

    Hi ZL,

    NV items as established by the default Z-Stack solution are used for specific Zigbee network configurations.  There is no issue with creating a custom NV item for output TX power or changing this value during run-time.

    Regards,
    Ryan