Re: Problem getting I2C port 1 and 5 working on MOD54415
Posted: Tue Nov 03, 2020 8:45 am
Hello,
I just ran some tests with a MOD54415 module on a MOD-DEV-70 board. For I2C1 I had to add 4.7k resistors on sda and scl.
The PIC I2C board has the following devices:
Microchip Pickit Serial I2C Demo Board Driver
* Platforms Supported: MOD5441x, NANO54415, MCF5441x OEM
*
* Demonstrates the use of 5 Microchip I2C Peripherals:
* 24LC0B EEPROM, 2Kbit (256 x 8)
* MCP9800 Temperature sensor
* MCP23008 GPIO port expander, connected to LEDs
* TC1321 10-bit DAC
* MCP3221 12-bit ADC
The applications were:
1. \nburn\examples\MOD5441X\MOD5441x-I2C\I2CAddressScan
Using the example with no modifications than changing the I2C port from default of 0 to 1. The peripherals were detected correctly in both cases.
2. \nburn\examples\MOD5441X\MOD5441x-I2C\PicKitI2CSerialDemoBd
Using the example with no modifications than changing the I2C port from default of 0 to 1. All 5 of the peripherals were identified and operated correctly.
So I am uncertain why you are seeing the behavior you describe. I did verify if the proper pull up resistors are not installed the behavior is erratic, but never a crash, just I2C error messages. I am attaching my .s19 file for the address search configured for I2C1. Can you reply with a photo of the pcb you made assembled with the module?
I am using tools revision 2.9.3 and a rev 2.2 module. If you have an older rev module that should still be fine, but I would recommend 1.10 or higher.
If you are still stuck after all this, I would recommend opening a ticket at support.netburner.com.
I just ran some tests with a MOD54415 module on a MOD-DEV-70 board. For I2C1 I had to add 4.7k resistors on sda and scl.
The PIC I2C board has the following devices:
Microchip Pickit Serial I2C Demo Board Driver
* Platforms Supported: MOD5441x, NANO54415, MCF5441x OEM
*
* Demonstrates the use of 5 Microchip I2C Peripherals:
* 24LC0B EEPROM, 2Kbit (256 x 8)
* MCP9800 Temperature sensor
* MCP23008 GPIO port expander, connected to LEDs
* TC1321 10-bit DAC
* MCP3221 12-bit ADC
The applications were:
1. \nburn\examples\MOD5441X\MOD5441x-I2C\I2CAddressScan
Using the example with no modifications than changing the I2C port from default of 0 to 1. The peripherals were detected correctly in both cases.
2. \nburn\examples\MOD5441X\MOD5441x-I2C\PicKitI2CSerialDemoBd
Using the example with no modifications than changing the I2C port from default of 0 to 1. All 5 of the peripherals were identified and operated correctly.
So I am uncertain why you are seeing the behavior you describe. I did verify if the proper pull up resistors are not installed the behavior is erratic, but never a crash, just I2C error messages. I am attaching my .s19 file for the address search configured for I2C1. Can you reply with a photo of the pcb you made assembled with the module?
I am using tools revision 2.9.3 and a rev 2.2 module. If you have an older rev module that should still be fine, but I would recommend 1.10 or higher.
If you are still stuck after all this, I would recommend opening a ticket at support.netburner.com.