• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 237 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.

CC1352P7: ability to go into STANDBY

Shawn O'Neil
Prodigy 195 points
Part Number: CC1352P7
Other Parts Discussed in Thread: CC1310, , CC2652P7, CC2652R

Hello,

We are porting a CC1310 design to a CC1352P7 design. I am not able to get the device into STANDBY. As you can see below I am printing out data just prior to us doing a semaphore_Post operation which should allow the system to take advantage of STANDBY. There is only 1 constraint (#2 which disallow standby shown below) which is due to the serial port being active. Post printing of this message, I release the UART and the last statements just prior to posting the Semaphore to be awaken on a push button, I check the status of "if(PowerCC26X2_module.constraintCounts[2])" is set, then I'll turn on a LED. The LED is off, so it should be OK for the Power Policy (standard one) to take advantage of STANDBY.

I'm drawing around 2 mA and I'm sure that other parts of my system will not use 2 mA of current. Any thoughts/comments welcome.

Thank you,

Shawn

*********************************************************

Power_getConstraintsMask = 4
Power_getPerformanceLevel = 0
Power_getTransitionState = 1
Power_getDependencyCount[0] = 0x0
Power_getDependencyCount[1] = 0x0
Power_getDependencyCount[2] = 0x0
Power_getDependencyCount[3] = 0x0
Power_getDependencyCount[4] = 0x0
Power_getDependencyCount[5] = 0x1
Power_getDependencyCount[6] = 0x0
Power_getDependencyCount[7] = 0x0
Power_getDependencyCount[8] = 0x1
Power_getDependencyCount[9] = 0x0
Power_getDependencyCount[10] = 0x0
Power_getDependencyCount[11] = 0x0
Power_getDependencyCount[12] = 0x0
Power_getDependencyCount[13] = 0x1
Power_getDependencyCount[14] = 0x1
Power_getDependencyCount[15] = 0x1
Power_getDependencyCount[16] = 0x0
Power_getDependencyCount[17] = 0x0
Power_getDependencyCount[18] = 0x0
Power_getDependencyCount[19] = 0x0
Power_getDependencyCount[20] = 0x0
Power Constraint Count[0] = 0
Power Constraint Count[1] = 0
Power Constraint Count[2] = 1
Power Constraint Count[3] = 0
Power Constraint Count[4] = 0
Power Constraint Count[5] = 0
Power Constraint Count[6] = 0
Entering deep sleep (S)

  • 0
    TI__Mastermind 20332 points

    Hi Shawn, 

    Is this in the debug mode? It is not allowed to go to standby when using the debugger. 

    If it is not in the debug mode,

    1. Are you posting the semaphore immediately after releasing the constraint? Are there any other active peripherals at this point in time?

    Regards.
    Sid

  • 0 in reply to Sid
    Prodigy 195 points

    Sid,

    I am aware when in debug mode that the system will NOT be able to go into Standby and when in that mode our LED will be energized to represent that bit #2 of the constraint structure is set, to disallow standby. When I run in stand-alone mode (no debugger) the LED is not energized which represents bit #2 of the constraints structure is cleared.

    I am not setting or releasing any constraints in my application. This would all be OS/drivers setting/releasing any constraints. We are using TIRTOS7. What is TIRTOS7 vs just TIRTOS. My experience with CC1310 was always TIRTOS. In the example for provided by TI for standby operations used 'sleep()' and our code base is using "Task_sleep(SLEEP_FOR_1S);"

    We have other peripherals such as SPI, I2C, etc. that are configured via the *.syscfg file, but they are not opened/active. If they were configured in error I would expect that the count value, bit #2 for the DISALLOW STANDBY would be increased. From my assessment the main determination in going to STANDBY and done by the 'PowerCC26XX_standbyPolicy" is looking at the Power Constraints for moving to STANDBY, which are all clear. Anything with XOSC would do this? Both HF and LF are created by external crystals (48 MHZ & 32.768KHz).

    Thank you,
    Shawn

  • 0 in reply to Shawn O'Neil
    TI__Mastermind 20332 points

    Hi Shawn,

    I do not think XOSC has anything to do with this. 

    Could you also check the CPU and peripheral states with Energy Trace ++? I will check if there is any other power driver setting needed. 

    www.ti.com/.../ENERGYTRACE

    Regards,

    Sid

  • 0 in reply to Sid
    Prodigy 30 points

    I have the same problem. CC1352P7 & CC2652P7 do not enter Deep Sleep. I get about 2mA also at 2V. I need to place them into deep sleep. Im using the same code with CC1352p-4 AND cc2652r and they work.