+ Post New Thread
Results 1 to 3 of 3
  1. #1
    Newbie level 1
    Points: 22, Level: 1

    Join Date
    Feb 2018
    Posts
    1
    Helped
    0 / 0
    Points
    22
    Level
    1

    Cadence lint warning: FFWASR

    Hi am doing LINT analysis for our design using cadence HAL it generates a warning as

    halstruct: *W,FFWASR (../../test.v,620|0): Flip-flop 'a47' does not have any asynchronous set or reset.
    a47 <= out47;


    We designed the logic using synchronous reset mechanism only.
    How can i analyze the above warning ?
    Can i ignore it?


    regards
    raj

    •   Alt12th March 2018, 07:14

      advertising

        
       

  2. #2
    Advanced Member level 4
    Points: 7,451, Level: 20
    Achievements:
    7 years registered Created Blog entry
    dpaul's Avatar
    Join Date
    Jan 2008
    Location
    Germay
    Posts
    1,094
    Helped
    244 / 244
    Points
    7,451
    Level
    20
    Blog Entries
    1

    Re: Cadence lint warning: FFWASR

    We designed the logic using synchronous reset mechanism only.
    Then the warning msg makes sense.

    How can i analyze the above warning ?
    By looking at your RTL code and comparing it with the translated flop after synthesis.

    Can i ignore it?
    I don't know your design, so can't comment on it.
    .....yes, I do this for fun!



    •   Alt12th March 2018, 09:32

      advertising

        
       

  3. #3
    Advanced Member level 4
    Points: 6,068, Level: 18

    Join Date
    Apr 2016
    Posts
    1,286
    Helped
    222 / 222
    Points
    6,068
    Level
    18

    Re: Cadence lint warning: FFWASR

    Quote Originally Posted by Rajashekar_m View Post
    Hi am doing LINT analysis for our design using cadence HAL it generates a warning as

    halstruct: *W,FFWASR (../../test.v,620|0): Flip-flop 'a47' does not have any asynchronous set or reset.
    a47 <= out47;


    We designed the logic using synchronous reset mechanism only.
    How can i analyze the above warning ?
    Can i ignore it?


    regards
    raj
    This is why FFWASR is a warning and not an error. It's benign for this design as you know that was not the intention.
    Really, I am not Sam.



--[[ ]]--