Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > PSoC® Software > Strange static analysis warning:

Bookmark and Share
Cypress Developer CommunityTM
Forums | Videos | Blogs | Training | Rewards Program | Community Components



Strange static analysis warning:
Moderator:
JFMD

Post Reply
Follow this topic



Strange static analysis warning:

hli posted on 05 Jun 2012 5:35 AM PST
Top Contributor
675 Forum Posts

I have a somewhat strange issue with the static analysis. I basically need a 24bit-counter which is driven by an internal clock (MASTER/3). Since it is 24 bits, it needs to be UDB-based, and therefore needs a sync clock. For that I also use an internal clock (MASTER/1). Now I get the warning that there is a clock path between these two clock, and they are not synchronized:

Warning: sta.M0019: Design01_timing.html: Warning-1350: Path(s) exist between clocks Clock_1(routed) and Clock_2, but the clocks are not synchronous to each other: (ClockBlock/dclk_0, \Counter_1:CounterUDB:sC24:counterdp:u2\/ci)  (File=D:\dev\psoc\freqmeter\Design01.cydsn\codegentemp\Design01_timing.html)

Warning: sta.M0019: Design01_timing.html: Warning-1366: Setup time violation found in a path from clock ( Clock_2 ) to clock ( Clock_2 ). (File=D:\dev\psoc\freqmeter\Design01.cydsn\codegentemp\Design01_timing.html)

But both clocks are set to 'synced'. This is part of a larger project, but I have reduced it to this simple example - see the attachement.

What is the problem here, and how can I avoid it?




Re: Strange static analysis warning:

Bob Marlowe posted on 05 Jun 2012 06:25 AM PST
Top Contributor
1768 Forum Posts

Not as strange...

First, for a UDB counter with 24 bit the maximum clock frequency is 29 MHz (and not 33)

Second, a sync-component helps.

 

Happy syncing..

Bob

 



Re: Strange static analysis warning:

hli posted on 05 Jun 2012 07:24 AM PST
Top Contributor
675 Forum Posts

Regarding the maximum frequency: this is strange - for 24bits it is 29MHz, for 32 bit it is 39MHz? (Also, in the 2.10 version of the component it was 30 vs. 25MHz). (and btw: the 2.20 data sheet duplicates the PSoC3 FF implementation data)

And I still think that the sync component should not be needed here. IMHO this is the whole purpose of the clock/count combination is to do exactly what the sync component does: sample the count input on the rising flank of the clock input.

There is some description of how the inputs are handled in the 2.10 data sheet, but it is confusing to me: it talks about many different clocks (clock, component clock, synchronization clock and master_clk), and doesn't talk about how this relates to the clock/count input pair.

(btw: when testing different bit-depths of the counter, the maximum frequency I get for 16 bit is 33.1MHz, for 24bit it is 28.3MHz, for 32bit it is 25.7MHz)






ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". CYPRESS SEMICONDUCTOR AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY CYPRESS SEMICONDUCTOR. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM CYPRESS SEMICONDUCTOR.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms and Conditions of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms and Conditions of this site. Cypress Semiconductor and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Spec No: None; Sunset Owner: GRAA; Secondary Owner: RAIK; Sunset Date: 01/01/20