[Simulavr-devel] Re: raising signals from gdb

[Keith Gudger]

Ted:

I implemented the signal stuff, using "SIG80" as the start interrupt (to
make room for all 32 vectors).  It works great.

I checked out my changes to devsupp.c and intvects.c for the USB devices,
and they look OK.

To finish checking it out, I need to add support for Ports E & F.  I did
that, and it compiled OK.  My ports are 4 bits wide, so I added "
PORT_4_BIT  = 4" to the ports.h file.  At that point, simulavr can finally
try out a couple of the new devices ... and it gives a core dump.

Can you point me to documentation on what to do with the dump?  Thanks.
Keith

On Thu, 9 Oct 2003, Theodore A. Roth wrote:

> 
> 
> On Thu, 9 Oct 2003, Keith Gudger wrote:
> 
> > Ted:
> >
> > Your latest patches work great.  I have some information for you on the
> > SIGXX values.  The '14' offset is, I think, a fixed value.  If you look at
> > the output from "info signal" you will find that SIG96 is entry #110.
> > That explains it!  Here's my suggestion.  Why don't you suggest that
> > interrupts start at "SIG100" and we'll use the offset of 86 in the code.
> > This way, it's easy to think "If I want interrupt 11, I type 'signal
> > SIG111'".  What do you think?
> 
> I vaguely remember choosing 96 since it was easily maskable (96 ->
> 0x60). Don't remember why I wanted to be able to mask it though.  ;-)
> 
> The major problem with starting with SIG100 is in limiting the number
> of irq's you can raise to 27. The mega128 has 34 interrupt. Of course,
> starting at 96 only gives 31 available interrupts, so we still lose.
> 
> Ted Roth
> 
> 
>