AnsweredAssumed Answered

ADuCM320 Restart during sending or receiving data, I2C peripheral

Question asked by sin on Nov 20, 2015
Latest reply on Dec 17, 2015 by sin

Hi

 

I have some questions about ADuCM320 from my customer.

Please let me know the following.

 

A)  Regarding restart in sending data, I2C peripheral.

     Condition:

     ADuCM320 works as slave in I2C transfer.

     ADuCM320 receives Read Frame from master.

     Although master generates restart-condition in sending TxFIFO data,

     the arbitration lost about master Tx-frame occurs after sending data completely.

     My customer has found the above and have following questions.

    Q1) When master generates restart in sending Tx-data, does the I2CxSSTA.bit13(REPSTART) indicate it ?

    Q2) When master generates restart in sending Tx-data, how should we do to interrupt sending Tx-data ? 

           To reset Tx shifter ?

 

B)  Regarding restart in receiving data, I2C peripheral.
     Condition:
     ADuCM320 works as slave in I2C transfer.
     ADuCM320 receives Write Frame from master.
     When Rx-data is loaded into Rx shifter, master generates restart-condition.
     In this case, how does ADuCM320 work ?
     My customer has following questions.
     Q3) When master generates restart in receiving Rx-data, does I2CxSSTA.bit13(REPSTART) indicate it ?
     Q4) When master generates restart in receiving Rx-data, how does the receiving data which is loaded into
            Rx shifter become ? Canceled ?  To keep receiving data after restart, and is wrong data loaded into Rx-FIFO ?
     Q5) Master generates restart in receiving Rx-data and device id is matched.
            In this case, is it possible that ADuCM320 ackowledges the frame to be its own frame ?
            Can START and IDMAT indicate those ?

 

Sorry for many questions.

 

Best Regards.

Outcomes