kel8157
Full Member level 2
I am doing C++/NCVerilog cosimulation.
The setup is C++ test vector creation/injection by calling a HDL task in systemverilog front-end, the SV frontend interfaces with DUT in a verilog TB.
Write to the DUT goes well, but read is problematic, and the error is not easy to find. The C++ code is a complex external package plus my background is more in generic C.
The setup is C++ test vector creation/injection by calling a HDL task in systemverilog front-end, the SV frontend interfaces with DUT in a verilog TB.
Write to the DUT goes well, but read is problematic, and the error is not easy to find. The C++ code is a complex external package plus my background is more in generic C.
Code:
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::at