Kinetis MicrocontrollersのトピックRe: Confusion using Component I2C_LDD Kinetis L

Confusion using Component I2C_LDD Kinetis L

steve_fae — Tue, 05 Mar 2013 22:13:15 GMT

If you look at typical usage for the component, you see this example below and then the prototype of the real component. Why are they different?

But in my CW 10.3 it seems the component is different, in fact there are only 3 parameters to pass.

byte I2C2_SendBlock(void* Ptr, word Siz, word *Snt);

-Return value: Error code, possible codes:

ERR_OK - OK

ERR_SPEED - This device does not work in the active speed mode

ERR_DISABLED - Device is disabled

ERR_BUSY - The slave device is busy, it does not respond by the acknowledge (only in master mode and when interrupt service is disabled)

ERR_BUSOFF - Clock timeout elapsed or device cannot transmit data

ERR_TXFULL - Transmitter is full. Some data has not been sent. (slave mode only)

ERR_ARBITR - Arbitration lost (only when interrupt service is disabled and in master mode)

-1. parameter: Pointer to the block of data to send.

-2. parameter: Size of the block.

-3. parameter: Amount of data sent (moved to a buffer). In master mode, if interrupt support is enabled, the parameter always returns the same value as the parameter 'Siz' of this method.

Re: Confusion using Component I2C_LDD Kinetis L

Lukas_Heczko — Wed, 06 Mar 2013 16:48:04 GMT

Hi Steven,

I think you compare methods of two different components: Internal2C component which implements SendBlock method and I2C_LDD which has MasterSendBlock. Am I right?

Best Regards,

Lukas

Re: Confusion using Component I2C_LDD Kinetis L

steve_fae — Wed, 06 Mar 2013 16:54:20 GMT

I figured that out after posting but couldn't find how to retract my post. Thanks

Re: Confusion using Component I2C_LDD Kinetis L

JimDon — Wed, 06 Mar 2013 22:06:56 GMT

Actually, you can delete your post....

Posters regret. Too bad you can't take back emails...