10 Replies Latest reply on Jan 5, 2012 10:14 AM by user_1377889

    Static timing analysis

    malvin.nkomo

      Hi

         

      I am having the following warning

         

      Warning-1350: Path(s) exist between clocks ClockBlock/dclk_1 and CyBUS_CLK, but the clocks are not synchronous to each other: (ClockBlock/dclk_1, \Counter:CounterUDB:sC16:counterdp:u1\/ci)

         

      To what extent does it affect my timing accuracy?

        • 1. Re: Static timing analysis
          gautam.das.g

          Hi Maduna,

             

           

             

          The Clock Summary Section shows that frequency violation has occurred in CyBUS_CLK.

             

          Did you use the "Sync" component available under the "System" section in the component catalog?

             

          It can be used to synchronize the clock to bus clock.

          • 2. Re: Static timing analysis
            malvin.nkomo

            Hi

               

             

               

             Do you have any example project how the sync can be implemented. I have looked on the site and i seem not to find anything.

            • 3. Re: Static timing analysis
              user_1377889

              That's a rarther easy one:

                 

              Sync is a three terminal module: a clock to synchronize with (inyour case should be the bus-clock,

                 

              a clock signal to synchronize (dont know the name here)

                 

              an output resulting in a synchronized clock which you should connect to your module(s)

                 

              So: the Sync-Module is placed BETWEEN the unsynchronized signal and the module where the unsynchronized signal was originally connected to.

                 

              Still need an example?

                 

              Happy New Year!

                 

              Bob

              • 4. Re: Static timing analysis
                udayan.umapathi

                What BOB has told is absolutely correct. 

                   

                You can as well read this blog post by Brad Budlong to better understand the need for a SYNC component, http://www.cypress.com/?rID=48686&cache=0  . 

                • 5. Re: Static timing analysis
                  content.librarian

                  Hi

                     

                  I have implemented the SYNC block as per the previous recomendations and I have no build errors but a timing violation warning which is affecting the way my PWM modules are being cloocked and hence run. The warning is as below and find attached the Static Timing analysis log.

                     

                   

                     

                  Warning-1350: Path(s) exist between clocks ClockBlock/dclk_1 and CyBUS_CLK, but the clocks are not synchronous to each other: (ClockBlock/dclk_1, \Counter:CounterUDB:sC16:counterdp:u1\/ci)

                  The static timing analyzer reported a warning. See the warning message for details. Additional information may be available in the timing report file.

                     

                   

                     

                  Any idea on how i can get over this?

                     

                   

                  • 6. Re: Static timing analysis
                    malvin.nkomo

                    Hi

                       

                    I have implemented the SYNC block as per the previous recomendations and I have no build errors but a timing violation warning which is affecting the way my PWM modules are being cloocked and hence run. The warning is as below and find attached the Static Timing analysis log.

                       

                     

                       

                    Warning-1350: Path(s) exist between clocks ClockBlock/dclk_1 and CyBUS_CLK, but the clocks are not synchronous to each other: (ClockBlock/dclk_1, \Counter:CounterUDB:sC16:counterdp:u1\/ci)

                    The static timing analyzer reported a warning. See the warning message for details. Additional information may be available in the timing report file.

                       

                     

                       

                    Any idea on how i can get over this?

                       

                     

                    • 7. Re: Static timing analysis
                      user_1377889

                      I re-built your project, but I didn't get the error. And my Counter-module (v2.10) is watermaked with "Prototype".

                         

                      Can you please strip down your project, build, clean, archive (minimal) and finally upload your project to have a look at it.

                         

                      Bob

                      • 8. Re: Static timing analysis
                        malvin.nkomo

                        Hi Bob.

                           

                         

                           

                        Find attached.

                        • 9. Re: Static timing analysis
                          user_78878863

                          This look really strange. When I open the timing analysis result (just double click on the 'notice list' entry, one can see that the error lies within the counter component. dclk1 is connected to the count input, and CyBUS_CLK comes from the clock input.

                             

                          The 'ClockBlock' component mentioned in the warning seems to be something PSoC creator internal. I don't find any component containing it...

                             

                           I was able to solve this by syncing both clock and count input of the counter component, though this seems unnecessary. Both are derived from the same clock (at least I tested it that way - have them both generated from MASTER_CLK). Seems like a routing bug to me...

                          • 10. Re: Static timing analysis
                            user_1377889

                            Another interesting aspect is: when I change the device to a PSoC3 the timing analyse runs fine!

                               

                            Bob