Activity

Thanks, aligns with my thoughts. Yes the generator already creates/uses clock/reset procedures.

Regards
Ajeetha

Depending on what becomes the pattern, it could be a concurrent procedure call (if it encapsulates the entire process), a sequential procedure call (if it only encapsulates most of the process), or as you suggested an entity (but may be more than we need).

Also note that OSVVM’s TbUtilPkg has a CreateClock and a CreateReset

Some of what is in the ControlProc is pretty standard. Some of it is not.
The main items above that are custom are:
UartScoreboard <= NewID("UART_SB", NUM_UARTS) ;
. . .
osvvm_uart.ScoreboardPkg_Uart.WriteScoreboardYaml(FileName => GetTestName & "_sb_Uart.yml") ;

Long term, we should be able to do the UartScoreboard as a constant:
constant…[Read more]

> I can see that the scripts use the explicit name of the file for analyze and run_test TCL commands. However, it is also possible to just do a file search and with the filenames in a list, iterate over the list and call analyze or run_test for each of them.

> Why isn’t it done in this way?

It comes down to testing philosophy. I see the s…[Read more]

The following are primary API commands. Note that library sets the

– library []
– Make LibraryName found in library directory specified by path the active library.
– Create the LibraryName if it does not exist.
– If path is not specified, use the library directory specified by SetLibraryDirectory.
– analyze [/] [options]…[Read more]

I can see that the scripts use the explicit name of the file for analyze and run_test TCL commands. However, it is also possible to just do a file search and with the filenames in a list, iterate over the list and call analyze or run_test for each of them.

Why isn’t it done in this way?

Also, I was expecting to see a whole lot of commands that…[Read more]

When OSVVM is compiling files, I get a whole lot of messages like this:

# QuestaSim-64 vcom 10.6c Compiler 2017.07 Jul 26 2017
# Start time: 23:57:14 on Jun 06,2024
# vcom -2008 -work osvvm_cosim ../OsvvmLibraries/CoSim/src/CoSimInterruptHandler.vhd
# — Loading package STANDARD
# — Loading package TEXTIO
# — Loading package std_logic_1164
# –…[Read more]

Thanks. I will get the updates in OSVVM scripting.

I did “global aldec”, all lower case.

The error message was referencing an all uppercase $ALDEC but “global aldec” fixed this issue. I noticed the same thing with “puts $aldec” vs “puts $ALDEC” as you describe.

No, there is no $aldec used in the $PATH_TO_SIM_DIR on my machine, that just points to the project directory on my C:/ drive.

Thanks,
Brad

Thanks Jim, I understand this better now – it’s scoping issue when multiple types are getting visible to a test.

Regards
Ajeetha

Hi Brad,
Did you add “global aldec” or “global ALDEC”? Your note above seemed to indicate that it is lower case. OTOH, the error messages are referencing an upper case $ALDEC. I should note if I do “puts $aldec” it works. If I do “puts $ALDEC” it does not work.

There is no “$aldec” in $PATH_TO_SIM_DIR right?

Cheers,
Jim

Hey,

I totally agree. This is part of what was so confusing to me. I could see that when using $aldec and running the test the variable would be properly expanded as you show, however, a bit further into the run, when attempting to load the aldec_matlab_cosim.dll the path would still show an unexpanded variable $ALDEC in the path.

I actually…[Read more]

Currently to get the HTML and JUnit XML reports you must use OSVVM scripting. The problem is that both the scripts and the VHDL code writes to the files.