S
siso
Guest
I was looking for a way to parametrise a design which heavily uses
interface constructs. Surprisingly or not - it appears to be a
challenge and I'm struggling to find my way trough. The biggest
trouble being ".... not implemented yet" or even worse - buggy tool
behaviour. The feeling is that I'm stepping on a thin ice.
The question is - has anybody around already been trough a similar
pain?
Some ideas so far:-
- Interface arrays -> DC is not happy with modport arrays (at least)
- Modport expressions -> simulators don't like them ("yet")
- aliases (trying to rewire the stuff inside the interfaces)-> same as
above
The only (kind of OK) way found so far is using packed typedefs inside
the interfaces - they can be parametrised. It doesn't look very nice
though when you try to split a slice from the whole bundle - looks
ugly and confusing.
Your thoughts will be appreciated.
s1s0
interface constructs. Surprisingly or not - it appears to be a
challenge and I'm struggling to find my way trough. The biggest
trouble being ".... not implemented yet" or even worse - buggy tool
behaviour. The feeling is that I'm stepping on a thin ice.
The question is - has anybody around already been trough a similar
pain?
Some ideas so far:-
- Interface arrays -> DC is not happy with modport arrays (at least)
- Modport expressions -> simulators don't like them ("yet")
- aliases (trying to rewire the stuff inside the interfaces)-> same as
above
The only (kind of OK) way found so far is using packed typedefs inside
the interfaces - they can be parametrised. It doesn't look very nice
though when you try to split a slice from the whole bundle - looks
ugly and confusing.
Your thoughts will be appreciated.
s1s0