Search Engine

Why Interrupts

Add Question

41 Threads found on Why Interrupts
why do we need to use like thet?why cant we check only one flag? PIC18 user manual answers your question Interrupt flag bits are set when an interrupt condition occurs regardless of the state of its corresponding enable bit or the Global Interrupt Enable bit
The code is confusing. why wait 1 second then check if there is still data in the UART? Any data would ahve been sent long ago. You also seem to enable the GIE and PEIE bits inside a loop and at the same time not use interrupts anyway! As Klauss points out "TXREG = ADC_value;" can at best only send 8 of the 10 ADC bits. If you really want to sen
That is why every one uses RTOS like To handle multiple things at once inside microcontrollers in a elegant manner.
why do you not use unsigned long jj = 3700000; char txt; ... LongWordToStr(jj, txt); // txt is " 3700000" (three blanks here) and UART Hardware ... Try firts to display a long value on terminal.. and further treat Frequency probleme..
Hi, That's why there are interrupts and internal periferal hardware. I don't know the internals of the 89s52. The easiest way for a 1s pulse is to set up a timer/counter periferal as wave generating mode. Then you should be able to choose frequency and duty cycle. Once set up it needs no additional processing power, and no code. The is a hardwar
Hello! You don't say what is your "desired output", so it's difficult to fix it for you. Beside this, in the case you want to generate 2 PWMs at 180 degrees (like sin and -sin), why don't you just invert one signal instead of bothering with 2 timers? Another thing. why this while loop in the interrupt function? You get interrupts at (...)
why not use an external clock with 50ppm or even 1ppm TCXO stability instead of internal > 1%? (cheap)
I want to use external interrupt in pic16f877 but cannot get the interrupt. Code is given below. why it is not getting ??? I am using switch on RB0 pin and want to toggle the RB1 pin connected with LED. Plz support. #include #include void main() { TRISB0=1; TRISB1=0; // Configure Po
You forgot to turn off the timer by "clr tr0". That's why it can't get out of interrupt. And your timer doesn't have any significant role here. Here's your code below reorganized a little bit neatly, but you need to look onto some mistakes, such as your ISR code needs a jump to another vector address & there's no R1 register under delay subroutine.
I am using ATMEGA16 and mikroC PRO AVR compiler. I need to know why serial reception using interrupts is not working. The UART transmit is working fine. // LCD module connections sbit LCD_RS at PORTB2_bit; sbit LCD_EN at PORTB3_bit; sbit LCD_D4 at PORTB4_bit; sbit LCD_D5 at PORTB5_bit; sbit LCD_D6 at PORTB6_bit; sbit LCD_D7 a
I notice that you have connected your 'zero-cross-detector' to both INT0 and INT1. why both ? Secondly in your code, you have commented out the MCUSR and GICR initialisation pieces. Where are you doing this instead ? In the absence of this initialisation, i'm not sure how the interrupts will function. Lastly - you stated that code works good w/o
There is some problem with the 7 Segment Proteus model you used. It flickers, I don't know why. Maybe some timing issue with the model. I have fixed the code. It uses 12 MHz Fosc. If you change Fosc to 4 MHz then you should also change the Timer1 interrupt reload value accordingly. I am attaching the working CCS C Code and Proteus file which I modi
hi guys, This is my first time here in edaboard, I hope this post finds you all well .. I have worked on HCS12XEP100 kit with a very simple project, just capturing an interrupt on port p pin 0 and toggling the state of port A. But, it never worked for me and I really don't know why !! Need help, If you please Thanks CODE: *****
To be honest, using up to three timers is too difficult for me to manage what is happen now. It seems so. Presently you enabled three timer interrupts but have only two interrupt functions defined. That's the final reason why the enable_display code gets never executed.
hey everybody i'm working on Telit GM862-GPS i already write some scripts in order to be familliare with it , the problem is when the script is running and i call the telit , it shows me RING RING in the terminal , the script stops completly. i understand that calls are considred like interrupts , but why after ending the call he don't continue
lks, is everybody ok? I'm making a Track System using a GSM and GPS module, both controlled by a PIC18F4680. At the moment, I'm facing a big problem to handle the data that come through USART using the interrupt approach. I don't know why, but after enabling the RS232 receive data available (#INT_RDA) interrupt, the LCD stops working (lcd_putc o
Hi ! I am using for the first time PIC24, programming in C and using MPLab + Hitech. I do not know why, but I am not getting the interrupt work. I put a breakpoint inside the interrupt, but seems it never comes inside... Someone could help me, please ? My code: Setting: //----- TIMER1 ------------- T1CON = 1000000000000000 ;
Your code is not commented and it's hard to analyze it but there's a subtle detail I realized from a first glance. You are using making use of the #asm("cli") and #asm("sei") commands. I don't know why you use them but it doesn't seem correct. Although AVR interrupts have priorities, they are prioritized only if they occur simultaneously. From this
what does mean by EVENT ? What's the use of events in I2C ? Please Elaborate !!!