Re: Where is source code of isr_setinterruptvector?

"Kris Ardis" <Kristopher.Ardis-6tN4nzCoH/[email protected]>
Newsgroups gmane.comp.hardware.microcontrollers.tini
Message-ID <007301c41d70$de26e490$764000b4@kardis>
> The interrupt timer1 execute is to slowly (~=400KHz on P5.2pin) and
doesn't
> depend of value TH1 and TL1.

What values have you tried?  How is TMOD set up?

> The interrupt time of timer1 depend of _nop_() , P5 &=~4 and TH1=0xFF
(body
> of interrupt function)
> I  think one instruction for examples one NOP operation on TINI400 with
> CLOCK = 14.7MHz X 4 take time = 1/14.7MHz or am I wrong ?

Based on your code, your interrupt probably takes at least 27 cycles to run
(estimating 18 for the interrupt code, + 4 for initial LJMP +5 for reti),
which comes to 1.8 uS.  You might want to see what exactly Keil has compiled
into your interrupt, because that's not too many instructions away from 2.5
uS (400KHz).

>
> Where is i can get source code of isr_setinterruptvector function for
KEIL?
>

This code just installs an 'LJMP my_interrupt' at the appropriate address.
You can dump the IVT using JavaKit to make sure it is writing the correct
code.

Kris


> void myinterrupt(void) interrupt 3
> {
> P5 &= ~4;
> _nop_ ();
> _nop_ ();
> _nop_ ();
> _nop_ ();
> _nop_ ();
> _nop_ ();
> _nop_ ();
> _nop_ ();
> TH1=0xFF;
> TL1=0xFF;
> P5 |= 4; //ET0 = 0;
> }
>
> Why Dallas doesn't support the sdcc compiler ?
> No rom_init,rom_sock library for sdcc compiler.
> http://sdcc.sourceforge.net/
>
>
> --
> Andrew
> _______________________________________________
> TINI mailing list
> TINI-6tN4nzCoH/[email protected]
> To UNSUBSCRIBE, edit your profile, or see list archives:
> http://lists.dalsemi.com/mailman/listinfo/tini
>


_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.