Defining an I2C communications module in existing code
Posted: Tue Dec 17, 2013 6:31 pm
Hi, so far I have had good success in using MOD5270 and a dev board with the existing UART for all my applications. All commands for the menus are available through regular serial terminals on PCs etc.
For a special version of my microthruster control unit research platform I have to use I2C to interface with an external equipment that has a microprocessor board also using I2C, the Microchip dsPIC33FJ256GP710 instead of this UART channel. In the lab, both systems will be located in very very close proximity to each other, but separate, perhaps 2-3".
I would like to have the Microchip application code send me the same serial commands using I2C instead of a UART if possible.
Would the sample MOD5270 I2C2Serial code suffice for a test application on a MOD54415 as well? Could I use the two platforms to test out I2C -- I2C communication?
Would the I2C interface (I am not into the details yet) on the netburner platforms be wholly compatible the dSPIC33 ? Is this is a case of a multi-master implementation?
Any tips / guides would be greatly appreciated.
For a special version of my microthruster control unit research platform I have to use I2C to interface with an external equipment that has a microprocessor board also using I2C, the Microchip dsPIC33FJ256GP710 instead of this UART channel. In the lab, both systems will be located in very very close proximity to each other, but separate, perhaps 2-3".
I would like to have the Microchip application code send me the same serial commands using I2C instead of a UART if possible.
Would the sample MOD5270 I2C2Serial code suffice for a test application on a MOD54415 as well? Could I use the two platforms to test out I2C -- I2C communication?
Would the I2C interface (I am not into the details yet) on the netburner platforms be wholly compatible the dSPIC33 ? Is this is a case of a multi-master implementation?
Any tips / guides would be greatly appreciated.