I downloaded v10.72D of DC and installed it. In the previous version of 10.72 I
have (I don't know what letter version it is),I am using function
I2C_initClk() found in I2C_HW.LIB to switch between a 200kHz clock and a 400kHz
clock. But thatfunction is not there in v10.72D. Is there another mechanism
provided to do the same thing that I'm not seeing?
Steve
I2C with DC10.72D
Started by ●July 25, 2018
Reply by ●August 5, 20182018-08-05
Steve,
Sorry for the late response — I was on vacation and then fell behind on email replies.
It looks like I2C_initClk() is now called _I2C_initClk() for some reason. I’m not sure why Digi made it an “internal” API, but it happened before I was maintaining the codebase.
Regarding I2C_WriteToSlave(), it’s still present but has a different function signature. The I2C libraries went through a few revisions in each release, some of which introduced bugs. I feel good about the version in 10.72D, and received positive feedback from a customer using it in a product.
Let me know if you run into other I2C issues or have difficulty updating your program for the changes. If you were happy with the old code, you could revert all of the I2C libraries the the versions that shipped with 10.72. But I recommend reading the I2C entries in the release notes to understand some of the issues resolved with the updates.
-Tom
> On Jul 25, 2018, at 1:29 PM, Steve Trigero s...@yahoo.com [rabbit-semi] wrote:
> I downloaded v10.72D of DC and installed it. In the previous version of 10.72 I have (I don't know what letter version it is),
> I am using function I2C_initClk() found in I2C_HW.LIB to switch between a 200kHz clock and a 400kHz clock. But that
> function is not there in v10.72D. Is there another mechanism provided to do the same thing that I'm not seeing?
>
> Steve
Sorry for the late response — I was on vacation and then fell behind on email replies.
It looks like I2C_initClk() is now called _I2C_initClk() for some reason. I’m not sure why Digi made it an “internal” API, but it happened before I was maintaining the codebase.
Regarding I2C_WriteToSlave(), it’s still present but has a different function signature. The I2C libraries went through a few revisions in each release, some of which introduced bugs. I feel good about the version in 10.72D, and received positive feedback from a customer using it in a product.
Let me know if you run into other I2C issues or have difficulty updating your program for the changes. If you were happy with the old code, you could revert all of the I2C libraries the the versions that shipped with 10.72. But I recommend reading the I2C entries in the release notes to understand some of the issues resolved with the updates.
-Tom
> On Jul 25, 2018, at 1:29 PM, Steve Trigero s...@yahoo.com [rabbit-semi] wrote:
> I downloaded v10.72D of DC and installed it. In the previous version of 10.72 I have (I don't know what letter version it is),
> I am using function I2C_initClk() found in I2C_HW.LIB to switch between a 200kHz clock and a 400kHz clock. But that
> function is not there in v10.72D. Is there another mechanism provided to do the same thing that I'm not seeing?
>
> Steve
