PSoC™ 4 Forum Discussions

Thanks to Bob,

I almost did implement RTC with WDT. and Now I want to know some caution about this process

1. I implemented 2 years-period timer with RTC. I used WDT2 with my generated interrupt.

but I worried about distortion. because of RTC, WDT2 must operate correctly. so tell me about caution that can distort WDT2.

2. can you tell me about guaranteed error related to RTC? last question, you said RTC could be almost precise. but i doubt that because of

clock accuracy, crystal characteristic or  load capacitance.

3. and now I calculate current in circumstance that is between deep sleep and active. but in datasheet. only wake time(25us) existed.

but in order to calculate exact time. I must know about code execution time, deep sleep time, active time during 1s.

- sean

Can I view the signal data of any pin through i2c bridge control panel . Eg i am controlling an LED connected to a pin through pwm and want to see the waveform in bridge control panel, how do i do it.

I am working through Alan Hawes' videos using the PSoC 4 BLE and am extending his code from the following video:

http://www.cypress.com/video-library/PSoC/psoc-4-ble-101-5-using-capsense-bluetooth-low-energy/108391?tid=84506&sort_by=created&form_build_time=0.95414400

To start experimenting with the API I am going to use the LED connected to a pin to indicate whether something happened or not. To start, I use the following code to turn the LED on as CYBLE_ERROR_OK must be returned (the slider function works fine):

int main()
{
    CYBLE_API_RESULT_T thingy;
    
    CyGlobalIntEnable; /* Enable global interrupts. */

    /* Place your initialization/startup code here (e.g. MyInst_Start()) */
        
    CapSense_Start();
    CapSense_InitializeAllBaselines();
    CapSense_ScanEnabledWidgets();
    
    thingy = CyBle_Start(Stack_Handler);
    
    if(thingy == CYBLE_ERROR_OK) LED_Write(1u);

    for(;;)

    {

When I turn on or reset the board the LED turns on and then turns off. I think that it should remain of forever, or until I turn the board off. I have

- disabled "HW connection" under "Digital output",

- set the "Drive mode" to "Strong drive"

- left all other pin settings at their default

- pin name is now "LED"

- set pin 43 (P2[6]) as the LED connection

I have tested the following added immediately after the "if" line shown above:

    CyDelay(500);
    LED_Write(0u);
    CyDelay(500);
    LED_Write(1u);

This causes the LED to blink, so I know that my code is working, just not as I expect it to. I expect the LED to remain on after the for(;;) loop is entered. That blinking code also works when made part of the "if" statement showing that "thingy" did indeed equal "CYBLE_ERROR_OK". 

What am I not understanding about pins?