We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue reported by @azaidy.
Proposal is to have an optional shape field like numpy when declaring interfaces:
shape
interfaces = { 'umi_in': dict(type='umi', dw=dw, aw=aw, cw=cw, direction='input', shape=(m,n), txrx='umi'), 'umi_out': dict(type='umi', dw=dw, aw=aw, cw=cw, direction='output', shape=(m,n), txrx='umi'), 'umi_aux': dict(type='umi', dw=dw, aw=aw, cw=cw, direction='output', shape=(p,)) }
Elements in arrays should be accessible with standard array notation; this should apply to both coupled UmiTxRx interfaces and decoupled interfaces.
UmiTxRx
dut.net.intfs['umi'][i][j].write(...) dut.net.intfs['umi_aux'][k].send(...)
The text was updated successfully, but these errors were encountered:
Note: this should also be possible with bundled clocks and resets
Sorry, something went wrong.
No branches or pull requests
Issue reported by @azaidy.
Proposal is to have an optional
shape
field like numpy when declaring interfaces:Elements in arrays should be accessible with standard array notation; this should apply to both coupled
UmiTxRx
interfaces and decoupled interfaces.The text was updated successfully, but these errors were encountered: