Bug #5684


Added by Sergey Smolov about 6 years ago. Updated over 3 years ago.

Engine (Simulator)
Target version:
Start date:
Due date:
% Done:


Estimated time:
Detected in build:
Published in build:


I've tried to add the "example" project to the Retrascope's test suite (in fact, I've tried to uncomment corresponding lines in the VhdlFiles class).
Upon "test.vhd" I've got an error.

Tool arguments: src/test/vhdl/example/test.vhd --target test --toplevel test --engine efsm-test-generator

Error log:

2015.03.04 17:04:41.337. INFO: EFSM.TestGenerator: starting a new sequence
2015.03.04 17:04:41.338. INFO: EFSM.Simulator.WORK.TEST(BEHAVIORAL)_0: resetting EFSM
2015.03.04 17:04:41.338. INFO: EFSM.TestGenerator.RandomGenerator.WORK.TEST(BEHAVIORAL)_0: generating a new input vector
2015.03.04 17:04:41.339. INFO: EFSM.TestGenerator.RandomGenerator.WORK.TEST(BEHAVIORAL)_0: resetting the EFSM
2015.03.04 17:04:41.362. INFO: EFSM.TestGenerator.RandomGenerator.WORK.TEST(BEHAVIORAL)_0: the guarded action has been enabled successfully. Input vector: {events: {CLK}; transaction: {RESET = false}}
2015.03.04 17:04:41.362. INFO: EFSM.TestGenerator.RandomGenerator.WORK.TEST(BEHAVIORAL)_0: the EFSM has been reset successfully
2015.03.04 17:04:41.363. INFO: EFSM.Simulator.WORK.TEST(BEHAVIORAL)_0: processing the events: {CLK}
2015.03.04 17:04:41.363. INFO: EFSM.Simulator.WORK.TEST(BEHAVIORAL)_0: input dump: {RESET = false}
2015.03.04 17:04:41.383. INFO: EFSM.Simulator.WORK.TEST(BEHAVIORAL)_0: initialising the simulator. The reset guarded action: {{CLK}: {predicate: (NOT RESET)}->{{assignment: C[0:0] := false; assignment: C[0:0] := false}}}
2015.03.04 17:04:41.403. INFO: EFSM.Simulator.WORK.TEST(BEHAVIORAL)_0: the reset guard is enabled
2015.03.04 17:15:05.161. ERROR: The exception has been encountered: java.lang.IllegalArgumentException: Uncompatible data types: LOGIC_BOOLEAN vs (MAP LOGIC_INTEGER LOGIC_BOOLEAN)
    at ru.ispras.retrascope.engine.efsm.simulator.EfsmSimulator.computeExpression(
    at ru.ispras.retrascope.engine.efsm.simulator.EfsmSimulator.executeAssignment(
    at ru.ispras.retrascope.engine.efsm.simulator.EfsmSimulator.executeAction(
    at ru.ispras.retrascope.engine.efsm.simulator.EfsmSimulator.initialise(
    at ru.ispras.retrascope.engine.efsm.simulator.EfsmSimulator.processEvents(
    at ru.ispras.retrascope.engine.efsm.generator.test.RandomGenerator.submitVector(
    at ru.ispras.retrascope.engine.efsm.generator.test.EfsmTestGenerator.start(
    at ru.ispras.retrascope.engine.efsm.generator.test.EfsmTestGenerator.start(
    at ru.ispras.retrascope.basis.Engine.start(
    at ru.ispras.retrascope.basis.ToolChain.start(
    at ru.ispras.retrascope.basis.Engine.start(
    at ru.ispras.retrascope.Retrascope$Run.start(
    at ru.ispras.retrascope.Retrascope.main(
    at ru.ispras.retrascope.Retrascope.main(
    at ru.ispras.retrascope.util.VhdlUtilTest.runRetrascope(
    at ru.ispras.retrascope.util.VhdlUtilTest.runVhdl(
    at ru.ispras.retrascope.util.HdlUtilTest.runVhdl(
    at ru.ispras.retrascope.engine.efsm.generator.test.EfsmTestGeneratorVhdlTestCase.generate(

The cause is that when x is array of type MAP(x,y), the x[i] element of array x is of type y, not of type MAP(x,y).



Updated by Sergey Smolov about 6 years ago

The Retrascope project now is not in consistent state for this bug to be successfully resolved.
In fact, the processing of STD_LOGIC/STD_ULOGIC variables is implemented but not committed.
When this job will be done, the bug status will be raised to Normal.


Updated by Sergey Smolov almost 6 years ago

  • Subject changed from [efsm][simulator] computeExpression -> LOGIC_BOOLEAN vs (MAP LOGIC_INTEGER LOGIC_BOOLEAN) to computeExpression -> LOGIC_BOOLEAN vs (MAP LOGIC_INTEGER LOGIC_BOOLEAN)
  • Category set to Engine (Simulator)

Updated by Sergey Smolov almost 5 years ago

  • Target version changed from 0.1 to 0.2

Updated by Sergey Smolov over 4 years ago

  • Detected in build changed from svn to master

Updated by Sergey Smolov over 3 years ago

  • Status changed from New to Rejected

The tool does not fall on this design. The bug is rejected.

Also available in: Atom PDF