• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 177 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.

CC1352P: radiotestlibrary 1.20 fails to set power

Nir Radzi
Prodigy 70 points
Part Number: CC1352P

When using Radio Test Library 1.20 with CC1352P connected with device id L42001YR the setParameter for txPower returns error when working in propriety mode.

It gives an error with the executable that comes with the library, but I also tried compiling it myself and changing a bit (e.g remove the PA use, change the output power value) and always got the error.

When working in ieee_15_4 mode or ble there are no errors.

Also, working with smart RF Studio, there are no issues and the power can be set for propriety mode (as well as the ieee_15_4 and ble).

  • 0
    TI__Guru**** 317180 points

    I have asked the tools department to look into this. 

  • 0
    TI__Expert 4800 points

    Hi Nir,

    There was a change in the back-end used by both the Radio Test Library and SRFStudio in the latest release. This change requires an update of the code examples for the devices with "high TX output power". For example the CC1352P. For one or the other reason this update is missing in the Radio Test Lib and I will file a bug report to get that fix in next version. In the meantime you can do the update and recompile the code examples yourself. 

    The following update is required: The target board must be set before the RF settings are red from file and applied to the RF command structure.

    So for all the examples where the function: pTestDevice->readCmdSettingsFromFile(txId, txConfig) is called, the following function must be called in front: pTestDevice->setParameter(txId, "targetboard", targetName)

    Attached you will find an updated main.cpp file that should work.

    main.cpp

    Sorry for the inconvenience.

    Regards,

    Øyvind

  • 0 in reply to Øyvind K
    Prodigy 70 points

    Thank you, this solved the problem