• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 39 subscribers
  • Views 1078 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS: I2C Master Interrupt on CC3220

Minh Nguyen50
Prodigy 10 points
Other Parts Discussed in Thread: CC3220SF, MSP430FR2633, CC3200

Tool/software: TI-RTOS

I want to use CC3220SF with MSP430FR2633 over I2C:

MSP430FR2633(slave) >> send data over I2C >> CC3220SF (master).  

I want to use interrupts - no polling on CC3220SF.

I found a driver on CC3200 link but I am not sure it can work on CC3220SF (need port?), so I need some suggest/example for how to resolve it (i2C interrupts).

Thanks,

  • 0
    TI__Guru 64455 points

    Hello,

    All I2C examples in the SDK uses the default blocking mode and not the interrupt (or callback mode).

    The ti-drivers layer, as you can see in i2c.c/h, uses I2C_open() where it configures your I2C_Params structure.

    The default is:

    /* Default I2C parameters structure */
const I2C_Params I2C_defaultParams = {
    I2C_MODE_BLOCKING,  /* transferMode */
    NULL,               /* transferCallbackFxn */
    I2C_100kHz,         /* bitRate */
    NULL                /* custom */
};

    You can set it in your application as I2C_MODE_CALLBACK instead of I2C_MODE_BLOCKING and provide a callback function.

    Regards,

    Shlomi

  • 0 in reply to Shlomi Itzhak
    TI__Guru 64455 points
    Just to clarify, both blocking mode and callback mode should use interrupts.