Re: Constant assignments in co-simulation

On 5/26/2015 12:22 PM, Nikolay Kavaldjiev wrote:
>> Ahhh yes, you are trying to Cosimulate a design
>> that has no inputs.  I forget the particular
>> reasons but I don't believe it is possible to
>> Cosimulate such a limited design.
>> http://docs.myhdl.org/en/latest/manual/cosimulation.html#restrictions
>
> To exclude this as a possibility I modified the example module in the gist (
> https://gist.github.com/nkavaldj/7cc69372246e64d68f58) to have an input and
> I still have the same issue with co-simulation (only with co-simulation).
>
> The modified code:

Add a transition of the input in the `stim` and
see if anything changes.   Example, create a loop
and increment `y` and monitor the outputs.

>> You shouldn't have any issue Cosimulating a
>> complete design.
>
> Actually we have the issue in a large/complete design with plenty of inputs
> and outputs. The gist is just a minimalistic example that demonstrates the
> issue. We are using myhdl for more that two years now, including
> co-simulation, so it should not be a beginners issue. I hit the issue a
> week ago, and I cannot move since.
>

Sorry my foray hasn't been productive.  The additional
background is useful.  I don't recall running across
an issue like this.

Regards,
Chris




------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y