[Simulavr-devel] (no subject)

[Keith Gudger]

Ted:

I'm checking out the additions I made to the simulavr code for the
AT43USB.. devices.  Currently, when Timer 0 fires, simulavr says the
following:

MESSAGE: file ../../src/avrcore.c: line 823: Raising irq # 10
MESSAGE: file ../../src/avrcore.c: line 1033: Vectoring to irq at addr:40
offset:0

This is the wrong irq.  It's supposed to be #7.

The devsupp.c file says:
static DevSuppDefn defn_at43usb320 = {
/* name         */  "at43usb320",
/* stack_type   */  STACK_MEMORY,
/* sram_base    */  SRAM_BASE,
/* irq_vect_idx */  VTAB_AT43USB320,
...
and the intvects.c file says:
static IntVect vtab_at43usb320[] = {
    { "IRQ_RESET",        0x00,    0x00 },

    { "IRQ_INT0",         0x02,    0x00 },
    { "IRQ_INT1",         0x04,    0x00 },

    { "IRQ_TIMER1_CAPT",  0x06,    0x00 },
    { "IRQ_TIMER1_COMPA", 0x08,    0x00 },
    { "IRQ_TIMER1_COMPB", 0x0a,    0x00 },
    { "IRQ_TIMER1_OVF",   0x0c,    0x00 },
    { "IRQ_TIMER0_OVF",   0x0e,    0x00 },

    { "IRQ_SPI_STC",      0x10,    0x00 },
...

I feel pretty certain that this is the code used because when I issue int
(signal SIG92) 12, I get the correct jumps to my USB interrupt code.  When
I used the '355 instead of the '320, I get "illegal interrupt" (which is
correct.)

Is there something funny going on in timers.c maybe?  Do I need to worry
about "mask_TOV0"?  Thanks.

Keith