Activity
-
Sten became a registered member 2 years, 8 months ago
-
Jim Lewis replied to the topic Synopsys VCS-MX in the forum OSVVM 2 years, 8 months ago
Hi Antonio,
I should be able to look into it shortly too. Also if it is a TCL error, you may need to update your TCL version.Cheers,
Jim -
John became a registered member 2 years, 8 months ago
-
Antonio Bergnoli changed their profile picture 2 years, 8 months ago
-
Antonio Bergnoli replied to the topic Synopsys VCS-MX in the forum OSVVM 2 years, 8 months ago
Hi Jim,
starting from the commit 66e31acb for the repository “Scripts” i discover that VCS does not work anymore, hence the
799f7963 is the last working commit. I was not able right now to submit a pull request, in any case i will try to investigate which is the root cause of that. -
Tobias became a registered member 2 years, 8 months ago
-
Antonio became a registered member 2 years, 9 months ago
-
Francis became a registered member 2 years, 9 months ago
-
Ulf became a registered member 2 years, 9 months ago
-
Jonas became a registered member 2 years, 9 months ago
-
Ryan's profile was updated 2 years, 9 months ago
-
M became a registered member 2 years, 9 months ago
-
Jim Lewis wrote a new post 2 years, 9 months ago
Summary of recent changes in OSVVM:
Scripts updated for better signaling to continuous integration (CI) tools
MemoryPkg updated to remove 31 bit limitation and support storage policies.
Reports keep […]-
Ha, very nice.
In my current system test bench of a AXI-QDMA Interface I model memory using my own dictionary implementation. First I used plain `std_logic_vector`, but it became slower & slower with increasing writes to new addresses in the dict. Then I’ve remembered that integers are “faster” than values with 9-state logic. So I’ve done something similar to your MemoryPkg, using an `integer_vector(0 to 1)` to store 64-bit wide `std_logic_vector` values, and also using integers for the address in the dictionary.
I’ve looked into an older version of your MemoryPkg before, which was limited to 31 bit – which was the reason for my own memory implementation. Now that this restriction is gone, it’s maybe finally time to try OSVVMs MemoryPkg.
Greetings,
Torsten
-
-
Jim Lewis replied to the topic Standard messaging feature in OSVVM? in the forum OSVVM 2 years, 9 months ago
See OSVVM’s AlertLogPkg for today’s answer to this question
-
MS became a registered member 2 years, 9 months ago
-
Wojtek became a registered member 2 years, 9 months ago
-
Samuel became a registered member 2 years, 9 months ago
-
Mehdi became a registered member 2 years, 9 months ago
-
Rick became a registered member 2 years, 9 months ago
-
Eiichi became a registered member 2 years, 9 months ago
- Load More