search

alexforencich / cocotbext-axi

AXI interface modules for Cocotb
MIT License
214 stars 70 forks source link

Using custom signal names #20

Open kschoos opened 3 years ago

kschoos commented 3 years ago

Hi, is there a way I'm overlooking to use custom signal names during bus creation (for StreamBus for example)?

alexforencich commented 3 years ago

Currently all of the *Bus objects extend from cocotb_bus.bus.Bus. I think that object supports some method for passing a dict or something for non-standard names. However, at some point I am going to implement a new base bus object to use instead of the one in cocotb-bus that should be significantly more flexible. So you can use the cocotb-bus dict for now, but eventually that's going to be replaced by some other method. And right now that's a bit cumbersome, as I think you would need to create all of the AXI channels separately and then stick them together into the AxiBus object.

nickvanderstel commented 7 months ago

Has there been any progress on this? Or could someone provide an example of a workaround? I'm trying to create an AXI-Lite bus and my DUT follows a coding standard which requires a suffix on each signal name. I spent a couple hours trying to build the channels separately but haven't had any luck yet.