Activity

Hi Jim

I am using the AXI memory model. I think it is all working as it should. I actually tried using the ‘-‘ in the scoreboard data for the inactive bytes. I then used check() and it worked well.
Thanks
Jon

Hi Jon,
Which OSVVM VC are you using?

For AXI4 Manager, it writes a U to memory in locations when WSTRB is 0. The U will not be stored in memory. For reading, there is no indication the data is valid or not. Hence, if your burst FIFO is organized as words, you will need to exclude those bits from comparing to X”020100–“. The ‘-‘ is…[Read more]

I just created a function to sero out the unused bytes in the read data and scoreboard data.

It looks like the problem was that I was defining the generic as a default value in the testbench top. Doing that I needed to use the -G option. If i delete that statement then the -g option works.

Be sure to try setting the generic defaults via the component (if used) or entity (if component not used).

Setting it to -G solved the problem.
Thanks
Jon

In VendorScripts_Questa (if version is 2025 or newer) or VendorScripts_Siemens, the generic switch is set by the following:
# -------------------------------------------------
proc vendor_generic {Name Value} {

return "-g${Name}=${Value}"
}

According to the Questa command reference,
-g <Name>=<Value> …
(optional) Assigns a value to all s…[Read more]

But actually I still have the same issue at the end of the burst if the bytes arent a multiple of the bus width.

I just realized that I can read the AXI memory using a byte address which then shifts the data into the correct position.

Hi Jim

Yes that was the issue.
Thanks
Jon

Hi Jim
Sorry for the delay.
The genric is in the testbench file where all items are instantiated (DUT, AXI compoents etc).
Thanks
Jon

Hi Jim,

I agree with you, all 3 files had the same error.

Thanks,
Best Regards,
Jerome

Hi Jerome,
I suspect that I agree.

It seems to be in:
* xMiiMacTransmitter.vhd (as you reported)
* xMiiPhyRxTransmitter.vhd
* xMiiPhyTxReceiver.vhd

Do you concur that all of these should be updated?

They pass all my tests – but only because they all have the same issue.

I have updated these and pushed them to the dev branch of OSVVM.

Best…[Read more]