V_cmd.data Length Limitation in SPI VVC Prevents Sending More Than 31 Bytes

VVC Bitvis VIP SPI
1

Hi,

I’m currently using the UVVM SPI VVC in my verification environment.

In my testbench, I configured the VVC with the following generics:

GC_DATA_ARRAY_WIDTH => 1523

However, when I try to send 229 bytes of data using the v_cmd.data field in the test case, only 31 bytes are actually transmitted. The remaining bytes are replaced with ‘X’.

After debugging the issue, I realized that the root cause is the following constant defined in the adaptations_pkg:

constant C_SPI_VVC_DATA_ARRAY_WIDTH : natural := 31;

This constant appears to limit the usable width of v_cmd.data, even though I configured a higher width via the generic.

My question is: Is the only way to fix this problem by manually modifying the adaptation_pkg and increasing the value of C_SPI_VVC_DATA_ARRAY_WIDTH?
Or is there a better way to propagate the value from the VVC generic to avoid this mismatch?

Thanks in advance.

SPI VVC Instantiation:

12ce2a34-bdd9-432c-bbda-b95f9a005d83
12ce2a34-bdd9-432c-bbda-b95f9a005d83533×226 30.6 KB

Debuging points on spi_vvc.vhd

104d6864-0925-46af-87b4-a70057a42c7e
104d6864-0925-46af-87b4-a70057a42c7e821×490 98.6 KB

Waveform Screenshoot:

image
image1221×179 27.7 KB

2

Hi,

Yes, the only way to fix this is to modify the constant in adaptations_pkg, which is meant for user modifications. The VVC generic value cannot be propagated to the v_cmd.data since the vvc_cmd_pkg is compiled before the spi_vvc.

However, it would be a good idea to add a warning when setting GC_DATA_ARRAY_WIDTH with a higher value than the maximum supported by C_SPI_VVC_DATA_ARRAY_WIDTH to avoid confusion.