Hardware I2C

[skimask]

This is for the same project that I was having difficulties with my interrupts interrupting SEROUT commands. I assume the I2CREAD and I2CWRITE would have the same problems when interrupted?

I2CRead/I2CWrite can be as fast as the PIC and/or device can make use of them...
Same thing with SerIn/SerOut...if the PIC is set up to run fast and the device can run just as fast, they don't take up much time.
The I2C commands won't get interrupted by ON INTERRUPT but they would get interrupted by DT's fast interrupts.
I would think you could easily go into the I2C macro's and add a couple of lines to turn the interrupts on and off before and after the I2C command (or do it manually each time an I2C command is executed).

Forget that other link. I think this one is better:
http://www.i2c-bus.org/I2C-Primer.520.0.html

[Kamikaze47]

I am using ASM interrupts, as some of them are time critical. I also would prefer not to turn off the interrupts during I2C usage, as I don't want to miss any interrupt events.

I just found this on MicroChip's site. It looks helpful: http://ww1.microchip.com/downloads/e...tes/00989A.pdf

[skimask]

I am using ASM interrupts, as some of them are time critical. I also would prefer not to turn off the interrupts during I2C usage, as I don't want to miss any interrupt events.

I just found this on MicroChip's site. It looks helpful: http://ww1.microchip.com/downloads/e...tes/00989A.pdf

Looks helpful, but I'd suggest reading that other site on I2C and learn a bit about what has to happen behind the scenes for an I2C transaction to be successful.
I2C isn't like serial. You can't really just 'plug a byte' and assume the receiver got it (well, you can for a few things). There's a few steps involved (start, control, address, data, stop/ack/nak, etc). Some under PIC control, some under user control.

How time critical are those 'time critical' interrupts?
Keep in mind that I2C is a lot faster than 9600 baud serial...

[Kamikaze47]

Thanks skimask, i'll give it a read.

I guess when I think about it, they aren't extremely time critical. My main worry was about missing interrupt events. But I guess as long as the interrupt does trigger - say a millisecond late, that shouldn't impact the performance.

[skimask]

I guess when I think about it, they aren't extremely time critical.

It happens...more often than not.
You hear 'I need sub-nanosecond accuracy to time my slot cars!'...come on...do you really?

My main worry was about missing interrupt events. But I guess as long as the interrupt does trigger - say a millisecond late, that shouldn't impact the performance.

Well if I knew what the trigger and the items involved were, I might have a better idea laying in the back of my head on how to compensate...

[Kamikaze47]

Ok, i've got 3 interrupts at the moment.

- USB interrupt that just does a USBSERVICE to keep the USB alive - i'm not sure how often this triggers - i heard somewhere that it was every few milliseconds, but that could be wrong.

- INT0 interrupt hooked to the clock line of a PS2 keyboard (High-Low transition means theres a new bit to capture) - don't want to miss any of these bits.

- TMR0 interrupt that triggers every 6mS to scan a grid of buttons.

[skimask]

- USB interrupt that just does a USBSERVICE

That's a bit of a tough one. I've heard anywhere from 10ms all the way up to 250ms (I don't believe that one for a second, or 4 service interrupts )

- INT0 interrupt hooked to the clock line of a PS2 keyboard

Only takes a split uSec to handle this one, if all you do is read and store, then return.

- TMR0 interrupt that triggers every 6mS to scan a grid of buttons.

Could probably extend this out a bit, or maybe put the work off to a 2nd PIC talking serial to the 1st PIC.

This almost sounds like a game controller, like for a flight sim...

Also, as you read the I2C doc's, keep in mind that the PIC controls everything about the I2C when in master mode. The device being talked to only does something after the PIC makes it do it. Therefore, if the PIC starts something, and then has to wait for a bit to continue doing something, the device will just sit there and happily hang out and wait for it.