In general when a lower level method detects an error then two concepts are used. Primarily, the method will either issue a UVM info with some information about what went wrong or issue a UVM error/fatal immediately. The first one will then return 1'b0 to signal that something went wrong. Thus, it is up to the parent levels to catch the error and convert them into UVM errors/fatals etc. This method was chosen since the parent level typically provides more and better information when things go wrong.
There are several ERROR categories. The following table lists them with some explanation:
Error Category | Description |
|---|---|
IMPL_ERROR | Implementation error. Something is really broken |
QUEUE_ERROR | A queue related error, e.g. the queue could not be found |
CFG_ERROR | Configuration error. Usually, because the configuration object is missing |
TYPE_ERROR | Type error. Typically issued when $cast() fails |
COMPARE_ERROR | Compare error. Issued, e.g. when the in order compare fails /table> |
Both the top level class cl_syoscb and the configuration class cl_syoscb_cfg contains handles to all queues. The former uses an ordinary array which provides a fast way of looping over the queues and the latter an associative which makes it easy to find a queue using only its name.
|
Project: SyoSil ApS UVM Scoreboard, Revision: 1.0.2.1 Copyright 2014-2015 SyoSil ApS All Rights Reserved Worldwide Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. |
 Doxygen Version: 1.6.1 IDV SV Filter Version: 2.6.2 Thu Jun 4 23:02:22 2015 |
