Subject: Re: Assignment reminder
From: John Stickley (johns@ikos.com)
Date: Fri Mar 29 2002 - 07:10:24 PST
Jason,
The way I would do this is to create a special
"error transactor" that interfaces to a companion
error handler C model on the software side.
DUT errors can be "raised" with signal inputs to the
"error transactor" which can, in turn, send an output
transaction over a SceMiMessageOutPort with the
error code encoded. The receive callback for that
message port would, in effect, be the callback you're
suggesting. It could process the error appropriately.
More steps could be taken to make this transactor,
and its companion C model a reusable piece of code
that will always run over any implementation of the
SCE-MI interface.
-- johnS
Jason Andrews wrote:
> One of the features for debugging that is important is
> a callback mechanism to the C model/testbench.
> Whenever an error condition occurs or something happens
> in the DUT that it important there should be a way
> to have a C function be called automatically.
> This way errors are flagged immediately and the user
> can place a breakpoint in the callback function to
> further inspect the state of the design.
>
> I am still in the process of learning the SCE-MI spec
> so maybe this is already covered, but if not I think
> it should be.
>
> Regards,
> Jason
>
> ------------------------------------------
> Jason Andrews
> Axis Systems
> jason@axiscorp.com
> 763-862-1655
--
/\
/\ | \
| \ / |
/ \ \
/\_/ K2 \_ \_
____________________________/\/ \ \
John Stickley \ \_________________
Principal Engineer, HDL Group \ johns@ikos.com
Ikos Systems, Inc. \_
17 E. Cedar Place \ Phone: (201) 818-2585
Ramsey, NJ 07446 FAX: (201) 327-4395
______________________________________________________________
This archive was generated by hypermail 2b28 : Fri Mar 29 2002 - 07:11:14 PST