| View previous topic :: View next topic |
| Author |
Message |
newCCSUser
Joined: 25 Aug 2013
Posts: 12
|
| Connecting i2C lines on dspic33 |
 Posted: Tue Jul 08, 2014 1:40 pm |
 |
|
Hi.
Am confused regarding the i2c connection.
We are building demo board and as far as i know i2c should be connected to sda i scl line but there are some schematics examples where he uses INT.
Is this possible or am missing something ? |
|
 |
newCCSUser
Joined: 25 Aug 2013
Posts: 12
|
|
| Posted: Wed Jul 09, 2014 1:06 am |
|
|
forget it, i will connect it by the book.
Thank you anyway. |
|
|
Ttelmah
Joined: 11 Mar 2010
Posts: 19359
|
|
| Posted: Wed Jul 09, 2014 8:22 am |
|
|
There are two ways of handling I2C.
'Soft' I2C (master only) can use any pins. 'Hardware' I2C. The chip hardware sends and receives the bytes for you.
For the 'hardware' I2C, you have to use the hardware pins. The software implementation can use any pins you want.
The hardware implementation, is faster, and can be sending/receiving, while the chip is doing other things. |
|
|
bkamen
Joined: 07 Jan 2004
Posts: 1611
Location: Central Illinois, USA
|
|
| Posted: Fri Jul 11, 2014 10:50 am |
|
|
If you see pins on an I2C chip like INT or IRQ, that's because the chip can generate flags (like MCHP's GPIO extenders that can create an interrupt-on-change).
So these can optionally be hooked to a pin on a PIC or other MCU that can generate interrupts.
Good examples are INT_RB or INT0/INT1/etc....
but yes, SDA and SCL are the 2 major pins of importance.
Cheers,
-Ben
_________________
Dazed and confused? I don't think so. Just "plain lost" will do. :D |
|
|
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
