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

CC3200 Lockup When Using SimpleLink File Services with Low Power Deep Sleep Mode

Craig Carson
Intellectual 780 points

I've noticed when using the SimpleLink File Services inside an application also taking advantage of the Low Power Deep Sleep mode the system will go into LPDS and lockup after entering the file services routines.  I haven't ready anywhere in the documentation where there may be a compatibility issue and just wanted to check with others and see what their experience has been.  The file services may be used with LPDS however I've been forced to use cc_app_putoff_pm() and cc_app_resume_pm() bookmarks to prevent the system from entering LPDS while using them.  Also when LPDS is turned off the file services also work without any issues.

Here is the setup:

1)  Application initializes and enables LPDS mode (POWER_POLICY_STANDBY).

2)  Application invokes function with requires a file update using sl_Fsxxxx  services.   This may happen either before or after the application actually has entered a LPDS mode.

3)  Application runs normally until it hits the sl_FsOpen() statement.  At this point the code enters sl_FsOpen and the system will go into LPDS mode and lock up.

Has anyone else had any issues with this or know what I should check if I'm doing something incorrectly?  As stated previously all my file operations function seamlessly when LPDS is either not used or temporarily disabled.

  • 0
    TI__Expert 5025 points

    Hi Craig,

    Thanks for your input! We will check this.

    The recommended usage of the LPDS mode is captured in the section "Disabling PM framework" of the PM framework document. It would be good to identify a wait_loop in the application where it would be ideal to enter LPDS and disable PM at all other instants.

    All Simplelink APIs can potentially cause the APPs to enter LPDS and hence is not recommended to enable LPDS as it would be an overkill.

    Best regards,

    Naveen

  • 0 in reply to Naveen Narayanan
    Intellectual 780 points

    Naveen,

    Thanks.  Again the unusual aspect of this is after entering LPDS it would actually lock up the system and it would become totally unresponsive.  So neither the GPIO used to wakeup the system nor timer would function.

  • 0 in reply to Craig Carson
    TI__Intellectual 1500 points

    Hi Craig,

    some question that I have:

    1. just to confirm, did you try to wake up the system using GPIO or timer?(Assuming they were setup before entering into LPDS)

    2. can you tell me about your code flow in more detail and also details of your setup (so that I can recreate this condition at my end).

    Regards,

    Rahul

  • 0 in reply to Rahul Goyal
    Intellectual 780 points

    Rahul,

    I have both a timer a GPIO used as wakeup sources.  This morning I went into my code and commented out all the cc_app_putoff_pm and cc_app_resume_pm statements around the file services code and can no longer replicate the issue. 

    It may be a service pack has corrected the issue or possibly some changes I've made to correct timer issues fixed it.

    Earlier it would reliably fail after sl_start, connect to AP, acquire IP, then go through an sl_fsopen/sl_fsread/sl_fsclose sequence while POWER_POLICY_STANDBY was enabled.  Initially my max file size was 256 and now it's 512 which is another change.

    At this point I can no longer replicate the original problem.

    Craig