This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

About AHB5 protection control signals

In AHB5, we have extended memory bits as [6:4] hprot. Previously we have [3:0] hprot. For implementation purpose, i treated [6:4] as a separate signal. This separate signal am qualifying based on some filter, just because not to consider for older AHB. Please suggest me, whether am doing in correct way.

Parents
  • Thank you.

    One more query regarding implementation is, for the extended HPROT bits {lookup, allocate, shareable} there are de-assert conditions for each bit i.e. {non_lookup, non_allocate, non_shareable}. Test is randomizing all the bits, still am not able to hit non_allocate and non_shareable. In all way am trying, giving more weightage in constraint or by directed test, still not able hit.

    Can you please suggest, is there any restriction to hit those 2 bits or we can ignore in normal functionality or how it is.

Reply
  • Thank you.

    One more query regarding implementation is, for the extended HPROT bits {lookup, allocate, shareable} there are de-assert conditions for each bit i.e. {non_lookup, non_allocate, non_shareable}. Test is randomizing all the bits, still am not able to hit non_allocate and non_shareable. In all way am trying, giving more weightage in constraint or by directed test, still not able hit.

    Can you please suggest, is there any restriction to hit those 2 bits or we can ignore in normal functionality or how it is.

Children
No data