RV01 SCV Reader (System-C Transactions)
Outline
The SCV (SystemC Transaction DB) format is used by the default transaction db writer of the SystemC Verification Library (TLM transactions).
Platforms: |
|
|||
Requirements: |
|
|||
Known limitations: |
|
|||
Status: |
|
|||
Operations: |
|
|||
Parameters: |
|
|||
Configuration: |
|
Video
The text db
A SCV text database file stores transaction traces in plain text format. It contains the following definition, followed by a list of attribute and transaction definition.- scv_tr_stream : A transaction stream containing a collection of related transactions.
- scv_tr_generator : A transaction generator for a specific transaction type, containing information such as the transaction type names, and attribute names.
Here a typical example:
scv_tr_stream (ID 1, name "pipelined_stream", kind "transactor") scv_tr_stream (ID 2, name "addr_stream", kind "transactor") scv_tr_stream (ID 3, name "data_stream", kind "transactor") scv_tr_generator (ID 4, name "read", scv_tr_stream 1, begin_attribute (ID 0, name "addr", type "UNSIGNED") end_attribute (ID 1, name "data", type "UNSIGNED") ) scv_tr_generator (ID 5, name "write", scv_tr_stream 1, begin_attribute (ID 0, name "addr", type "UNSIGNED") end_attribute (ID 1, name "data", type "UNSIGNED") ) scv_tr_generator (ID 6, name "addr", scv_tr_stream 2, begin_attribute (ID 0, name "addr", type "UNSIGNED") ) scv_tr_generator (ID 7, name "data", scv_tr_stream 3, begin_attribute (ID 0, name "data", type "UNSIGNED") ) tx_begin 1 4 0 s a 0 tx_begin 2 6 0 s a 0 tx_relation "addr_phase" 2 1 tx_end 2 6 100 ns tx_begin 3 7 100 ns a UNDEFINED tx_relation "data_phase" 3 1 tx_end 3 7 260 ns tx_end 1 4 260 ns a 0
To generate a SCV text database, your code need to add few additional lines, similar to the code below:
scv_startup(); scv_tr_text_init(); scv_tr_db db("my_db"); scv_tr_db::set_default_db(&db);
Here you find an extended
guide how to generate TLM transaction traces.
Usage
The reader can be used to open workspace resources.
Configuration
The SCV reader does not require any configuration.
Parse errors
The reader will provide a parse error message if the input can not be read. The message usually contains the error position, the reason for the failure and a stack trace.
If you can not resolve the problem (e.g. obvious format error in the input file), please send this message together with the input file to "This email address is being protected from spambots. You need JavaScript enabled to view it.".
Reader: de.toem.impulse.serializer.xyz Error at position: 4800 Text at position: "o !. Up Uq Ur" Message: Invalid character Type: class de.toem.impulse.serializer.ParseException Stack trace: de.toem.impulse.serializer.xyz.xyzReader.parse(XYZReader.java:459) de.toem.impulse.serializer.xyz.xyzReader.parse(xyzReader.java:363) de.toem.impulse.serializer.xyz.xyzReader.read(xyzReader.java:269) de.toem.impulse.serializer.xyz.xyzReader.read(xyzReader.java:237) de.toem.pattern.element.Element$1.execute(Element.java:1063) de.toem.eclipse.hooks.actives.EclipseActives$3.run(EclipseActives.java:73)