RE: [Jove-devs] Using JOVE with Modelsim

[Silvio B. <SBR...@al...>]

Judging from the traces, it seems that JOVE is scheduling callbacks in
absolute simulation time, but Modelsim believes that these times are
relative to the current sim time. I've been looking for knobs in JOVE to
make it use relative times instead, but so far I couldn't find any.
Where would be the fastest place to modify the code in order to use
relative times? Assuming that this hasn't yet been implemented.

Cheers,

Silvio

-----Original Message-----
From: Jon Nall [mailto:jon...@gm...]=20
Sent: Friday, November 04, 2005 7:25 AM
To: Silvio Brugada
Cc: jov...@li...
Subject: Re: [Jove-devs] Using JOVE with Modelsim

Hi Silvio.

Thanks for helping to port Jove to Modelsim! Posting your trace logs is
probably the best way for us to figure out what's going on.

To trace the C++ side of the world, you'll need to uncomment PLI_DEBUG
in native/comp/pli4j/src/Configuration.h.

To trace the Java side of the world, you should change the enabled
member in com.newisys.dv.Debug to true. You also want to run "ant clean;
ant" in the jove directory after this change (since enabled is final, it
gets inlined into some classes so you need to recompile them to get the
change).


nall.

On 11/4/05, Silvio Brugada <SBR...@al...> wrote:
>
>
>
> Hey there,
>
> I just came across JOVE a couple of days ago and since then became=20
> quite interested in it. This past few days, I've been working on=20
> porting it to Modelsim with some degree of success. So far, I'm able=20
> to drive signals but they don't properly synchronize with the clock.=20
> For instance, the following
> code:
>
>         while(true)
>         {
>                 bind.write.drive(bit);
>                 bind.clk.syncEdge(EdgeSet.POSEDGE);
>                 count++;
>                 System.out.println("Counted " + count + " clocks" );
>                 System.out.println("write should be " + bit);
>                 bit =3D !bit;
>         }
>
> Should drive the signal write hi and low, alternating every clock=20
> cycle, yet it ends up alternating every other cycle. I tried running=20
> this code on cver and then it works correctly. I've also traced both=20
> runs (the one using cver and the one using Modelsim) and it seems as=20
> if there are some missing callbacks (as one might expect). Is there=20
> anyone who could give me a hand deciphering the differences between=20
> these two traces? I can definitely use some help =3D).
>
> Thanks in advance,
>
> Silvio