PSoC™ 4 Forum Discussions

DeepSleep / Watchdog timing problems when using BLE

Hi, I try to implement the following scenario: boots -> process a task in ACTIVE mode for exectly 2 sec -> deep sleep for 5 sec -> task for 2 sec ... Show More

Hi,

I try to implement the following scenario:

boots -> process a task in ACTIVE mode for exectly 2 sec -> deep sleep for 5 sec -> task for 2 sec -> deep sleep 5 sec and so on.

This works great with WDT (wakeup from deep sleep after counting WDT intervals until 5 sec are reached) and a one shot timer (to time the 2 sec task duration).
But if I add BLE functionality into the design, something does not fit any more. I invested already two days into it, and read of course all the available PDFs (BLE getting started + Low-Power Modes and Power Reduction Techniques) , I analised the LPM example project but it uses the WDT differently then me.

I prepared a use case project (with oth) to analyse the problem, which uses LEDs and UART for logging.

So without BLE, where everything is fine, the following expected LED sequence can be observed:

GREEN (task) for 2 sec
BLUE (deep sleep) for 5 sec
during BLUE phase above 4 WHITE flashes every 1 sec (WDT interval ticks, reentering deep sleep)
end of BLUE phase above 1 WHITE double flash (wake up from deep sleep)

and so on...

UART logs the following sequence, (the single point after each WDT tick stays for reentering deep sleep mode).

Do something...
Try to sleep...

WDT tick: 1
.
WDT tick: 2
.
WDT tick: 3
.
WDT tick: 4
.
WDT wakeup

Now if I enable BLE (un-comment #define ENABLE_BLE in main.h), I observe the following pattern

GREEN for 2 sec
GREEN for 2 sec
BLUE flickering for about 3 sec
during BLUE phase above 2 WHITE flashes every 1 sec (WDT interval ticks, reentering deep sleep)
end of BLUE phase above 1 WHITE double flash (wake up from deep sleep)

and so on...

UART logs the following sequence

Do something...
Try to sleep...
Update GATT database...
Do something...
Try to sleep...

WDT tick: 2
....................................................
WDT tick: 3
..............................................................................
WDT tick: 4
.............................................................................
WDT wakeup

One can see many single points between WDT ticks, so the program tries reentering deep sleep very often but stays there only for a short time. I suppose it is because of the BLE subsystems interrupts, which would be fine if the average power savings were OK which I did not measure now. Am I correct with this assumption? How can I tune the intervals here, I did not catch this in the docs.
But what really bothers me is the fact, that work phase (GREEN) occurs twice without any sleep phase between, and that the deep sleep phase itself is shorter as expected (something above 2 sec instead of 5).
Eventually the program crashes after some time sooner or later. I am not experienced enough yet to debug this 🙂

Why does BLE interfere with the WDT timer so radically? I would expect, that the WDT does it work in background without any distortions using LFCLK. Giving WDT higher interrupt priority than BLESS or changing the LFCLK source from WCO to ILO does not make any difference in the pattern.

Is there anything I can do to fix my design? I will appreciate any optimizations.
What can I do to better understand the BLE low power behavior?

My project is attached to this post.

Thx

Edit: I found a logical error, now the timings are OK but the connection from a GAP client (CySmart app) can not be established reliably, especially during sleep phase. I would say this is my actual problem now + the random crashes after long running times.

Show Less

By Anonymous

Mar 12, 2017

499

PSoC™ 4

Cannot change Watch Dog Timer interupt interval

Solved

I want to be able to control the wake from deep sleep interval using the watchdog timer intrupt. But no matter what value I use for sleep_time, the i... Show More

I want to be able to control the wake from deep sleep interval using the watchdog timer intrupt. But no matter what value I use for sleep_time, the interval always is about one second. Here is my code:

#define SLEEP_INTERVAL_500MS 500
#define SLEEP_INTERVAL_1000MS 1000

#define SLEEP_INTERVAL_2000MS 2000
#define ILO_FREQ 32000

/*******************************************************************************
* Function Name: InitWatchdog
********************************************************************************
* Summary:
*   Initialize watchdog counter0 with specific sleep interval parameter
*
* Parameters:
*   uint16 sleep_interval   reset interval, in millisecond unit
*
* Return:
*   void
*
*******************************************************************************/
void InitWatchdog(uint16 sleep_interval)
{
    /*==============================================================================*/
    /* configure counter 0 for wakeup interrupt                                     */
    /*==============================================================================*/
    /* Counter 0 of Watchdog time generates peridically interrupt to wakeup system */
    CySysWdtWriteMode(CY_SYS_WDT_COUNTER0, CY_SYS_WDT_MODE_INT);
    /* Set interval as desired value */
CySysWdtWriteMatch(CY_SYS_WDT_COUNTER0, ((uint32)(sleep_interval * ILO_FREQ) / 1000));
    /* clear counter on match event */
CySysWdtWriteClearOnMatch(CY_SYS_WDT_COUNTER0, 1u);

    /*==============================================================================*/
    /* enable watchdog                                                              */
    /*==============================================================================*/
    /* enable the counter 0 */
    CySysWdtEnable(CY_SYS_WDT_COUNTER0_MASK);
    /* check if counter 0 is enabled, otherwise keep looping here */
    while(!CySysWdtReadEnabledStatus(CY_SYS_WDT_COUNTER0));
}
CY_ISR(isr_WDT)
{
    /* clear interrupt flag to enable next interrupt */

    Sensors_Power_Write(1);
    ADC_Start();                                          /* Start up the ADC */
ADC_StartConvert();                                   /* Start ADC conversion */
ADC_IsEndConversion(ADC_WAIT_FOR_RESULT);             /* Wait for result to complete */
ADC_StopConvert();                                    /* Stop ADC conversions */
updateSensorData(); //read sensordata and alarm, compare update adData if needed(stop advert, update, start advert)
    ADC_Sleep();
    Sensors_Power_Write(0);

    CySysWdtClearInterrupt(CY_SYS_WDT_COUNTER0_INT);
}
int main()
{
     /*===========================================================================================
     * this code piece initializes the watchdog function
     *==========================================================================================*/
    /* initialize watchdog */
    InitWatchdog(SLEEP_INTERVAL_500MS);
    /* connect ISR routine to Watchdog interrupt */
    ISR_WDT_StartEx(isr_WDT);
    /* set the highest priority to make ISR is executed in all condition */
    ISR_WDT_SetPriority(0);
    /* enable global interrupt */

    CyGlobalIntEnable; /* Enable global interrupts. */


    CyBle_Start(Stack_Handler);
    //SetupWDT(ONE_SECOND_PERIOD);

    for(;;)
    {
        if(sensor0Counts < alarmValue){
            appendFlagToLocalName(0x20);
        } else {
            appendFlagToLocalName(0x2a);
        }

        CyBle_ProcessEvents();

        /* clear watchdog counter before deep sleep */
        CySysWdtResetCounters(CY_SYS_WDT_COUNTER0_RESET);
        /* reset watchdog counter requires several LFCLK cycles to take effect */
        CyDelayUs(200);
        /* go to deep sleep mode */
        if( CyBle_EnterLPM( CYBLE_BLESS_DEEPSLEEP ) == CYBLE_BLESS_DEEPSLEEP )
        {
            ADC_Sleep();
            CySysPmDeepSleep();
        }

    }

}
/* [] END OF FILE *

Also, is there a way to cascade the two counters in the WDT to obtain a sleep interval of 5 or 10 seconds. I read somewhere that the maximum interval is 2048 ms.

Thanks

Show Less

By PaDo_1228851

Mar 22, 2017

1336

PSoC™ 4

Flash Utilisation

hi, i am have been working on psoc-4. my flash is almost full.its about 99.1% and Sram is around 43.5%. when i starting the program right now th... Show More

By chmoc_1567941

Mar 24, 2017

516

PSoC™ 4

Use for status/control block in parallel in/out mode? Examples?

Hi all, I'm a newcomer to the PSoC 4 world, trying to learn the architecture reading the TRM (and again, and again...). One thing I don't quite get... Show More

By Anonymous

Mar 19, 2017

930

PSoC™ 4

OTA update using CYBLE-202007-EVAL not working

Solved

Hello I am trying to get the Bootloader and Boootable modules to work for Fixed Stack OTA Bootloader with the CYBLE-202007-EVAL board and the BLE ... Show More

Hello

I am trying to get the Bootloader and Boootable modules to work for Fixed Stack OTA Bootloader with the CYBLE-202007-EVAL board and the BLE radio does no appear to be working when the device is put into program mode. Below I have listed the steps I have taken.

All work is done using PSoC Creator 3.3 DP1 which supports the CYBLE-202007 module and has been used to develop our existing application which uses the CYBLE-202007-01 module.

I have followed the step by step directions listed in application node AN97060 to get the Fixed Stack OTA Bootloader project working using the CYBC4247LQI-BL483 EVAL board working with the CY8CKIT-042-BLE pioneer kit. I am using the Android Cysmart mobile app to upload new firmware to the module. This is working fine.

1. Installed the CYBLE-202007-EVAL board on the CY8CKIT-042-BLE pioneer kit main board.

2. In the Device selector for the BLE_OTAFixedStack_Bootloader01 project and for the PWMExample01 project set the current device to CYBLE-202007.

3. Modified the linker scripts in the BLE_OTAFixedStack_Bootloader01 project and the PWMExample01 project to reflect the 256K ROM and 32K RAM memories.

4. Run the mk.bat from the scripts folder of the BLE_OTAFixedStack_Bootloader01 project.

5. Added the necessary code to the BLE AppCallBack to support the CYBLE-202007 module switching of the PA/LNA hardware control pins.

6. Changed the pin assignment in the BLE_OTAFixedStack_Bootloader01 project for the Bootloader_Service_Activation pin from p2.7 to p1.0 to support the hardware IO changes between the CYBC4247LQI-BL483 EVAL board and the CYBLE-202007-EVAL board.

After these steps the project builds and runs with the green LED pulsing correctly.

The problem is that when SW2 is pushed and the unit is put into program mode and the red LED comes on and flashes the Cysmart app does not see the device. It is acting like the BLE component is not advertising or the BLE radio isn't coming on. I have include the zipped work space with the example projects I am using.

Show Less

By chsi_1572801

Mar 24, 2017

514

PSoC™ 4

how to code for custom ble profile as client

I have two cyble022001-00 module.with reference to how to create custom ble profile (rgb led) i created one custom profile with one cherecterestic hav... Show More

By Anonymous

Sep 14, 2016

767

PSoC™ 4

PSOC 4 ADC Configuration Help

Hi all! I am having trouble configuring my adc to my current sense circuit. I don't know what my sample rate should be and how the Acquisition time... Show More

By Anonymous

Mar 17, 2017

437

PSoC™ 4

UART send AT command and rcx response from MODEM

Good day all, I am working on project using the UART component for serial communication with the NEOWAY M590E modem. In my project i wait till the ... Show More

By gamac_2277161

Mar 23, 2017

1080

PSoC™ 4

CapSense Slider Design for CSD

Hello, Community. I have designed two CSD sensor fields. I need round sensors, one as an endless slider like an rotary encoder. And the other... Show More

By Anonymous

Mar 22, 2017

532

PSoC™ 4

Cypress showing build error : .cy_checksum_exclude loaded at . . .

Solved

Hello everyone, I am using Cypress chip CYBL11172-56LQXI for BLE. I get the following 2 errors and I am not sure how to debug it. Build er... Show More

By Anonymous

Mar 6, 2017

368