• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 80 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.

IWR6843AOP: About porting idlePowerCycle / idlePowerDown(SDK3.6) to SDK3.5.4

takahiro hama
Prodigy 10 points
Part Number: IWR6843AOP

Dear TI support 

I have a question to port the idlePowerCycle / idlePowerDown to SDK3.5.4.

We are considering that idlePowerCycle / idlePowerDown at SDK3.6 is using in  SDK3.5.4.

We were ported libsleep_xwr68xx to  SDK3.5.4.

Also,do we need that the SDK3.6 library of  libsoc_xwr68xx.aer4f and libmmwavelink_xwr68xx.aer4f is ported to SDK3.5.4？

In this case,does it affect the behavior action of SDK3.5.4 and toolbox_4_7_0  by changed  SDK3.6 library( libsoc_xwr68xx.aer4f and libmmwavelink_xwr68xx.aer4f )?

Best regards

  • 0
    TI__Genius 17265 points

    Hi,

    I believe you are correct in that you will need those two additional libs in order to back-port the libsleep to SDK 3.5. I believe this should not have any additional negative affects, but please keep in mind that this combination is not tested, so you would need to do your own testing in order to verify functionality is as expected.

    Best Regards,
    Alec