DS1307 with PIC32

[Coccoliso]

Hi at all,

I have a problem with a source that worked with the FW24 but with the FW32 I have some long term problems.
The program reads the Time structure of the DS1307 by comparing the value of the minutes with the one previously stored.
In the FW24 version, the thing works constantly without blocks for hours, with the FW32 after a dozen reading cycles freezes.
I have found several postings in web that refer to the I2C of the PI32MX that can cause problems but I seem to understand from the sources that any FW (18/24/32) does not use the routines of a "native" I2C .. either wrong?
I would implement native routines (..the thing is dated 2014) but before that I would like to know if I am going to meet other problems I do not know, is there something more that I'm lost?

[Jerry Messina]

There are hardware I2C modules (HI2C.bas) for MCU08 and MCU16, but I don't remember seeing one for MCU32.

For the 32MX I think it's just the bit-banged I2C.bas module unless there's one floating around I didn't see.

[Coccoliso]

Hi Jerry,

I thank you for clarification, I thought there was no native I2C module (FW24 or FW32) because the DS1307 library always loads the I2C.BAS module even when you compile FW24.
Now that you told me this I try to look at the HI2C.bas of the FW24 version.
For the clock then I'll still ask you something because there is a GetPeripheralClock and an FCL clock that will definitely give me a twist on the I2CnBRG calculation.

[David John Barker]

I2C support in Firewing defaults to software (bit banged) in order to provide pin compatibility with the Arduino platform. However, there are hardware I2C libraries available for 8 and 16 bit (but not 32)

[Coccoliso]

Hi at all,

all clear!

[David John Barker]

Just to be clear on anyone reading this thread:

(1)
bit banged I2C routines provide Arduino shield compatibility

(2)
Hardware I2C pinout is not compatible with Arduino shields.

(3)
Firewing defaults to software I2C for the reasons given in (1)