Hi,
I read on this page for I2C https://www.matrixtsl.com/blog/i2c-slave-coming-soon/ .
I can`t find example from this page. I want to check in real.
Is posible to get this sample?
I2C Slave Demo.fcfx
Moderator: Benj
-
lomovic
- Posts: 18
- Joined: Tue Jul 07, 2015 10:58 am
- Has thanked: 1 time
- Been thanked: 1 time
- Contact:
Re: I2C Slave Demo.fcfx
Thanks.
Just another questions.
Where used
1. Comms: Interface --- I2C Master or I2C Slave
2. Peripheral CAL --- I2C ?
When initialise slave where to find address ?
cal_i2c1::Slave_Init (0x54,0ff) - in samples mentions 0x54 for PIC16F1937, but in data sheet for PIC 16F1937 in MSSP don`t find this address ?
Just another questions.
Where used
1. Comms: Interface --- I2C Master or I2C Slave
2. Peripheral CAL --- I2C ?
When initialise slave where to find address ?
cal_i2c1::Slave_Init (0x54,0ff) - in samples mentions 0x54 for PIC16F1937, but in data sheet for PIC 16F1937 in MSSP don`t find this address ?
-
LeighM
- Matrix Staff
- Posts: 2178
- Joined: Tue Jan 17, 2012 10:07 am
- Has thanked: 481 times
- Been thanked: 699 times
- Contact:
Re: I2C Slave Demo.fcfx
You can use the Master/Slave components or the CAL I2C component, which gives you lower level access.
What are you trying to do?
The Master is usually the controlling processor, the Slave is a peripheral, or one of many, connected to the Master.
In the case of a Slave it's up to you to decide what address it should have, then use that address to access it from the Master.
Have a good look those Master and Slave pairs of examples.
What are you trying to do?
The Master is usually the controlling processor, the Slave is a peripheral, or one of many, connected to the Master.
In the case of a Slave it's up to you to decide what address it should have, then use that address to access it from the Master.
Have a good look those Master and Slave pairs of examples.