Post Created date
need for disabling interrupt for "2 cycles instructions
david.prentice wrote:The multiple read would obviously work. IN save,SREG / CLI / sequence / OUT SREG,save would work Oh, I see what you are saying. Atomic access. Gee, I wish...
Friday, 8 February 2013 - 15:45
need for disabling interrupt for "2 cycles instructions
david.prentice wrote:Until I get a convincing scenario from ChaunceyGardiner: As I see it, the OP has a 16-bit counter and has no need to worry about disabling interrupts. The...
Friday, 8 February 2013 - 15:39
Interrupt does not fire on correct address
Post your circuit.
Friday, 8 February 2013 - 15:24
Timer application with unexpected results.
Steve_C wrote:I changed that count variable back to 8 bit "int" instead of "word" Forgot to mention that. int is at least 16 bits in C and C++. I'm getting tired of this. Would...
Friday, 8 February 2013 - 11:05
need for disabling interrupt for "2 cycles instructions
david.prentice wrote:@Sid, Go on then. Describe a specific set of circumstances. I did, but I'll rephrase it: is it possible for one or more ISRs to keep the mcu busy for any...
Friday, 8 February 2013 - 10:15
need for disabling interrupt for "2 cycles instructions
djdav wrote:I am using a integer initialized to a duration value. An timer interrupt decreases this integer every loop and my background tasks is checking for this integer!=0 to...
Friday, 8 February 2013 - 10:07
need for disabling interrupt for "2 cycles instructions
david.prentice wrote:think about it. You are testing for 0x0000. The risk is only when the counter goes from 0x0100 to 0x00FF. i.e you read the low-byte as 0x00, IRQ occurs...
Friday, 8 February 2013 - 09:57
Interrupt does not fire on correct address
Of course. I kinda knew I was wrong, so I shouldn't have posted that. I guess the interrupt is not the only thing that doesn't work in sleep mode.
Friday, 8 February 2013 - 04:04
Timer application with unexpected results.
If your new variable is 16-bit, modified by an ISR and you're not accessing it atomically in main(), the program is not working perfectly. You just haven't noticed it failing yet.
Friday, 8 February 2013 - 03:55
Interrupt does not fire on correct address
(Disclaimer: I just woke up.) According to the datasheet, "Pin change interrupts PCI0 will trigger if any enabled PCINT7:0 pin toggles". Does that imply the need of a handler for...
Friday, 8 February 2013 - 01:30
Timer application with unexpected results.
You have to access shared multibyte variables atomically. This applies to count. If state is not shared, it does not have to be volatile and it should be a local static rather...
Thursday, 7 February 2013 - 04:31
need help with itoa funtion
Koshchi wrote:Quote:If you don't want to do that, do what Cliff told you - ADSC clears automaticallyThat depends on how the ADC is set up. If this is free-running (which is highly...
Wednesday, 6 February 2013 - 18:10

Pages