1st Floor, HIG/ C-54, Shailendra Nagar, Raipur (INDIA).

Ticket Status

Next-Gen Solutions

Status Table of Support Tickets

Following table shows status of all filed support tickets in a chronological order. Please read description about table at the bottom of this page.

Ticket No.DateIssue TypeIssue DescriptionResolutionStatus
114-07-2019TechnicalI am not able to use get_randstate() and set_randsatate(no) on any process or object satisfactorily.Pl check next build.closed
217-07-2019Technicalstandard package/ library function randomize() is not working in the atssim. It has following syntax:
int randomize(list_of_vars) with {constraints}
fixed. Check in next buildclosed
319-08-2019TechnicalI am not able to set srandom() in a process using process::self.srandom(100)fixedclosed
414-12-2019TechnicalConsuming too much storage for UVM testcasesfixed: storage is optimized for all datatypes.closed
510-01-2020Techlogic/ reg or bit type consuming more storage in implementation of uvm_regreduced storage size for reg/logic and bitclosed
615-01-2020TechIssue reported related to int datatype storage sizereduced int datatype storageclosed
716-01-2020TechIssue reported for storage consumption by integral type long int, byte etc.reduced storage for integral typesclosed
81-02-2020Techissue related to lexical conversionfixedclosed
911-02-2020Techissued related to static castfixedclosed
1020-02-2020TechIssue related to wait forksolvedclosed
1122-02-2020Techbasic data unit storage is largebasic data unit storage is reduced: solvedclosed
1224-02-2020Techmore memory consumption for UVM testcasereduced memory consumption for UVM testcasesclosed
133-03-2020Techin built function naming convention is creating issuefixed: a special string is added to all internal c++ functions as prefixclosed
1417-04-2020TechNeeded to integrate c++ based verification componentssolved: DPI (Direct Programing Interface) is addedclosed
1522-04-2020TechDPI related issuefixedclosed
161-05-2020LicenseLicense issue is reportedfixedclosed
174-05-2020TechIssue related to Interactive modefixedclosed
1809-05-2020TechCompiled database related issuefixedclosed
1912-05-2020TechIssue related to Compiled database for interactive modesolvedclosed
2010-06-2020TechDataBase saving structure issuefixedclosed
2116-08-2020TechConstrained Randomization related issuefixedclosed
2219-08-2020TechIssue related to virtual function accesssolvedclosed
2328-08-2020TechConstrained Randomization issuefixedclosed
2401-09-2020TechIssue related to multi-dimensional array iterationfixedclosed
2505-09-2020Techmulti-dimensional array issueresolvedclosed
2610-09-2020Techanother issue in iteration of multi-dim arrayresolvedclosed
2726-09-2020TechIssue related to variable and port storage: consuming more storage in simulationresolvedclosed
2829-09-2020Techissue related to storage of various SV construct blocks: consuming more storagefixedclosed
2930-09-2020Techfine grain process object is consuming more storagefixedclosed
3016-11-2020Techissue related to assertions implementationimplemented phase 1closed
3111-12-2020Techassertions implementationimplemented phase 2closed
3218-02-2021Techassertion: sequences and properties implementation issuefixedclosed
3327-03-2021TechVCD file related issue is reportedfixedclosed
3430-05-2021TechGate and Switch level models implementation issueimplementedclosed
3518-06-2021TechIssue related to always_comb blockfixedclosed
3603-07-2021Techalways_comb issuefixedclosed
3720-07-2021TechIssue related to event datatypefixedclosed
3823-09-2021TechIssue of implementation of checkersimplementedclosed
3909-12-2021TechIssue reported related to fine grain process objectfixedclosed
4015-12-2021TechIssue related to disable block and kill of processresolvedclosed
Table above contains a chronological list of all issues filed by users related to atssim.
Please Note following points:
1. Users can filter/ search their tickets at the header of the table on ticket number etc.
2. If you have recently filed a ticket, which is not appearing in table then you need to wait till ticket is authenticated by our system after validation of user.
3. Following 3 values may appear in status field of your ticket:
Open: Investigation or fixing process is on for your problem at our end
On-Hold: We are waiting for some relevant inputs from user (User need to check their mail for details on inputs)
Closed: User's issue is resolved. User must look in resolution column of this ticket for details on resolution.
4. If resolution indicates that your issue is fixed in next release, then you will have to update your simulator package. Please see license FAQ section for how to update your simulator package.
5. Usually we upload updated version on site once a week or even more frequently if required.