LPDS doesn't wake up from timer interruption

Jason Corona

Part Number: CC3200

Tool/software: Code Composer Studio

I have been working over the CC3200 since quite a long time, I achieved what I needed before but now I wanted to make it with low power profile, I tried to implement the idle_profile example code onto my project and it does work good, button and HTTP interruptions both wake up my system but the problem is with the timer interruption it does not work always. First I thought it was a problem with my code but even using the example code it doesn't work always, does any one have experienced this behavior? or there is a pre configuration I'm ignoring

EDIT

I think I've isolated the problem, my code runs (or at least it tries to) like this:

1)Run AP and HTTP server

2)Receive AP parameters and sample time over html

3)Change mode to STA and tries to connect (Red led blinks showing LPDS in/out)

upto this point the codes works just fine, the timer interrupt is generated aswell as the http interrupts and GPIO but when I press a button to restart the process to (1) and send new connections parameters there's where my interrupts stop working when I send the parameters (3) and as I can see it doesn't get to LPDS anymore (Red led is on)

over 7 years ago

0 Benjamin Moore over 7 years ago

TI__Mastermind 30820 points

Hi Jason,

To make sure I understand correctly, you are saying that the system will successfully associate with an AP and then enter a cycle of LPDS time / active time for a while. Then this only breaks down when you reset the process?

Is it a full hardware reset that you are performing or is it a soft reset where the application state machine just starts over? Do you mean that the interrupts will stop working right after the second set of AP parameters are sent? Does the system still connect to an AP based on the new parameters or does it just hang somewhere?

Thanks,
Ben M

0 Jason Corona over 7 years ago in reply to Benjamin Moore

Prodigy 70 points

The reset it's just and script I make triggered by a button interrupt to restart the process and get new parameters for connecting to an AP without loosing the recopiled information and that's when the systems broke, It receives the parameters for second time but when it tries to connect it gets stopped by something.

But anyway I think I've found the problem, it was the idle profile example de-starting the watchdog when successfully connecttion to an AP happened.

this code lines on Wlanconnect

  iRetCode = MAP_WatchdogRunning(WDT_BASE);
    if(iRetCode)
    {
       WDT_IF_DeInit();
       MAP_PRCMPeripheralClkDisable(PRCM_WDT, PRCM_RUN_MODE_CLK);
    }

0 Benjamin Moore over 7 years ago in reply to Jason Corona

TI__Mastermind 30820 points

Hi Jason,

Was the code to de-initialize the WDT what was causing the problem? Can you confirm that your system is able to enter LPDS now on the second attempt?

Thanks,
Ben M

0 Jason Corona over 7 years ago in reply to Benjamin Moore

Prodigy 70 points

Yes, erasing that segment of code resulted on my system able to reset the process, it seems that the code was design to run just one time maybe? I'm not sure because i don't understand completely that section but I knew how to make it work

Wi-Fi

Wi-Fi forum

LPDS doesn't wake up from timer interruption