Fix Function Timer Component help

I changed your device to an PSoC5LP (I don't have another PSoC active in ma lab) compiled, setting breakpoints at lines 80 and 82 in main()where you write to the LEDs and I get only one stop, not more.

Bob

When reaching a breakpoint the CPU stops, but all internal hardware keeps running. This sometimes leads to strange behave.

Under Creator -> Tools -> Options -> Program/Debug you find an option mamed "Disable Clear-On-Read". I was told that this may have influence in situations like yours.

Bob

Why not add a 1 bit status register tied to the Tc pin of the timer,

and set it as sticky ? Then just poll that status register.

Regards, Dana.

I cannot reproduce that reading the status of a one-shot-timer resets it or restarts it for a PSoC5LP.

I will create a test-program for the CY9CKIT-050 and post it here.

Bob

If you set the timer to one shot mode it stops at count = 0,and does not

start back up. So you can get the timeout event with the status register and

with an API at a time of your choosing reset and restart the timer. Or

use a control reg on reset pin, either way.

Regards, Dana.

Probably the reset is the problem. The datasheet tells only about the hardware reset and a software-reset via API is not provided.

So you need to stop() and Start() the one-shoot when it has couted down.

See attached project.

Bob

The reset is as Bob stated not available from an API, per se. The Start()

seems to handle that.

If you use a control reg and reset input the following apply -

Regards, Dana.

Afaik the Start() API allone does not work as a reset, you have to Stop() the timer before.

Bob

Yes, you are quite right, many of the components could be less complex, to serve as many users as possible Cypress has built some jack of all trades devices (hopefully my translator didn't guide me wrong) and so there might be a lack of simplicity.

But

Nobody hinders you to build your very own timer component that exactly reflects the properties you just mentioned. You may even copy the existing files for the timer, rename the component-name and strip down the component to the barest. There is a Component Author Guide installed in your cypress directory that might help you with the design.

This takes some time, I did it and later with this knowledge I was able to solve some other projects for my customers.

Bob

This one had me scratching my head for a while but I think this is what you need.

The _Start API does start the timer running. In the following I use the TC output to control a flip-flop. After the 1s timer period my LED comes on forever. The only C code is Timer_Start();

In your project you are using SW to detect the TC. I did that with the following:

In C I wrote this...

    LED_Write( 0 );     // LED Off
   
    Timer_Start();  
   
    for(;;)
    {
        status_reg = Timer_ReadStatusRegister();

        if( status_reg & 0x80 )
        {
            LED_Write( 1 ); 
            CyDelay( 250 );     // Allow time for my old eyes to see the LED
        }
        else
        {
            LED_Write( 0 );  
        }
    }

Note that the timer does not restart in this case but the TC bit I am reading does get cleared. I think that is because it is only asserted for one cycle. The datasheet is a little misleading on this matter. it says "The tc output is available to monitor the
current value of the counter register; it is high while the counter is zero." and "The TC signal is always a single clock cycle pulse". The former implies that it remains high for a long while but, actually, the counter is reloaded on terminal count but the timer is stopped. As a result the TC is asserted for just one clock pulse. The word "while" in the first sentence is what threw me off.

Hope this helps...

-- Mark