Confusion of Axi4Full Testcases

Why OSVVM™? Forums OSVVM Confusion of Axi4Full Testcases

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #2857
    Veit
    Member

    Hi,
    with my marriage (see “https://osvvm.org/forums/topic/using-vcs-without-the-built-in-scripts”) of OSVVM and VUNIT I found a confusion in the TbAXI4_[AXI?]ManagerRandomTiming Testcase:

    ——————————————————-
    TbAxi4_ManagerRandomTiming1 :
    architecture: ManagerRandomTiming1

    Configuration TbAxi4_ManagerRandomTiming1 of TbAxi4Memory is
    for TestHarness
    for TestCtrl_1 : TestCtrl
    use entity work.TestCtrl(ManagerRandomTiming1) ;

    ——————————————————-
    TbAxi4_AXIManagerRandomTiming1 :
    architecture ManagerRandomTiming1 of TestCtrl is — <- should named AxiManagerRandomTiming1

    Configuration TbAxi4_AxiManagerRandomTiming1 of TbAxi4Memory is
    for TestHarness
    for TestCtrl_1 : TestCtrl
    use entity work.TestCtrl(ManagerRandomTiming1) ; — <- includes the last compiled architecture, should named AxiManagerRandomTiming1

    ——————————————————-
    In the TbAxi4_AxiManagerRandomTiming2 is the configuration without the AXI in the architecture name, too:
    Configuration TbAxi4_AxiManagerRandomTiming2 of TbAxi4Memory is
    for TestHarness
    for TestCtrl_1 : TestCtrl
    use entity work.TestCtrl(ManagerRandomTiming2) ; — <- should named AxiManagerRandomTiming2

    #2858
    Veit
    Member

    Found 2 more cases (checking currently only AXIFull):
    TbAxi4_MemoryBurstAsyncPattern2.vhd:
    architecture name: MemoryBurstAsyncPattern1

    TbAxi4_MemoryReadWriteDebug1.vhd:
    architecture name: MemoryReadWrite1 (debug missing)

    #2859
    Jim Lewis
    Member

    Hi Veit,
    Thanks for the issue reports. I have updated the names so they match. That said, since the test runner compiles and then runs the test case, the test case execution was still correct. I still hate it when the names do not match though.

    You can also file issue reports like this on the VC’s issue page, such as for this one:
    https://github.com/OSVVM/AXI4/issues

    This will be fixed in the Dev branch as soon as I test and push it. It will be on the main branch in the next release.

    Cheers,
    Jim

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.