- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I try to implement an internal RTC starting up from seconds timer.
I tried to use timer block and LFCLK but it make a timing violation warning of:
"Warning-1366: Setup time violation found in a path from clock ( CyHFCLK ) to clock ( CyHFCLK )."
when I tried to use Timercounter Block it make an error at build with:
"The listed clock input does not allow arbitrary signals for clocking and requires an input from the clock block. Update your design and rebuild."
plz advise about that and also if there is a BLE project that implement RTC mention it.
regards,
Fayek
Solved! Go to Solution.
- Labels:
-
BLE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I filed a CASE on the timer. In the component catalog its symbol
is shown as fixed, but only UDB is available in PSOC 4, so that
is an error.
Then the tool reports an error because it is not UDB, even though
its config dialog only shows UDB as a selection.
Regards, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You cannot clock a timer from the LFCLK, from the TRM (UDB Clocking) -
Consider posting the rest of your project so forum can take a look
for issues.
“File” Creator
“Create Workspace Bundle”
Regards, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You could use the PSoC4 WDT for the interrupt.
There is a new version of Creator at hand, when you download and install Creator 3.2 early access (it is a beta!) you can have a working RTC component running on PSoC4 and PSoC4 BLE as two example projects.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dana,
thank you for your reply.
but it's strange to have a warning about timing delays in the first case.
regarding the 2nd case of TCPWM as I know it's fixed function not UDM.
if both have the same situation you mentioned, so why selecting LFCLK exist in configuration? it mean that it can't be used in programming the PSOC4.
BR,
Fayek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Bob,
Great news. thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I filed a CASE on the timer. In the component catalog its symbol
is shown as fixed, but only UDB is available in PSOC 4, so that
is an error.
Then the tool reports an error because it is not UDB, even though
its config dialog only shows UDB as a selection.
Regards, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dana,
thank you for following.
regarding fixed function I meant the fixed function digital components in the chip like TCPWM, SCB, ... not FF blocks
I don't know how they are handled like UDB or not.
also, I don't know that there are special icons for FF & UDB components, may you give more details about that?
BTW, I downloded new version 3.2 and the RTC component is great.
also new clock configuration look very good.
BR,
Fayek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Turns out there is a bug in Timer component. When you
first palce on schematic the lable under it is F-F, but then
if you open up config, then "apply" it changes that label to
UDB which it is.
Yes the new parts great, eg. with RTC.
Regards, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For RTC Implementation with BLE, please have a look at the project: http://www.cypress.com/?rID=110543&cache=0