IWR6843ISK-ODS: I2CSlave_read() and I2CSlave_write()

Hello Connor,

It seems swru522e.pdf is HW spec. I am asking capability of I2CSlave_read() and I2CSlave_write(). Please kindly confirm and comment back to me.

Best regards,

Taka

Hello Connor,

Thank you for your reply regarding advanced format. Let me make two more questions in terms of I2C functions;

1. Is there any response if write data by master will be come during waiting by I2CSlave_write() ?

     Also, Is there any response if read data by master will be come during waiting by I2CSlave_read() ? 

2. Is there time-out rule or setting for waiting data input by master when I2CSlave_write() and I2CSlave_read() will be called ?

    Or, will the device continue to wait data input by master forever ?

Best regards,

Taka 

Hello Connor,

We are now testing I2C driver implementation to 6843ODS as slave by communicating with external MCU as master.

It is observed that 6843ODS halt execution by I2CSlave_write and it is recovered when I2C read data by master is called. 

But it is strange ACK is not returned by 6843ODS to master and 6843ODS is recovered when I2C read data to different I2C address is called.

Could you kindly advise in order to succeed I2C communication ? (If you can check, we can disclose our source code here.)

Best regards,

Taka

Hello,

I am digging into this, so give me a couple of days to give you an answer.

Best regards,

Connor Desmond

Hello Connor,

Let us update our findings ;

We have tested I2C blocking mode test by below software and all tests are passed with no error.

  mmwave_sdk_03_04_00_03\packages\ti\drivers\i2c\test\xwr68xx

    - xwr68xx_i2c_mss_slave.xer4f

    - xwr68xx_i2c_mss_master.xer4f

In case of slave mode test, 6843ODS is recovered from blocking mode by I2C data input from external master device but ACK is not replied.

Also, 6843ODS is recovered from blocking mode even if input data by wrong I2C address is called by external master device.

In case of master mode test, I2C data called by 6843ODS is observed. According to master.c, slave address is 0x48 and write data is 0x0A.

But it is observed by scilloscope that wrong address and wrong data is called as below ;

Expected write data)                                     start / address 0x48 + W(0) / write data 0x0A / stop /

observation by oscilloscope by write data)   start / address 0x00 + W(0) / write data 0x04 /

Expected read data)                                     start / address 0x48+R(1) / read data / stop

observation by oscilloscope by read data)    start / address 0x00 + R(1) / stop

For your reference, let us attach I2C waveform called by 6843ODS in master mode test.

Best regards,

Taka

Hello,

In the i2c_slave.c file here is the following code:

if (readWriteFlag == 1)
{
/* Enable all the WRITE interrupt flags */
I2CIntEnable(ptrHwCfg->ptrI2cBase,
I2C_INT_MASK_ADRR_SLAVE | I2C_INT_MASK_STOP_CONDITION | I2C_INT_MASK_TRANSMIT_READY | I2C_INT_MASK_NO_ACK);
}
else
{
/* Enable all the READ interrupt flags */
I2CIntEnable(ptrHwCfg->ptrI2cBase,
I2C_INT_MASK_ADRR_SLAVE | I2C_INT_MASK_STOP_CONDITION | I2C_INT_MASK_TRANSMIT_READY | I2C_INT_MASK_NO_ACK);
}

Can you try replacing the code above with the following:

if (readWriteFlag == 1)
    {
        /* Enable all the WRITE interrupt flags */
        I2CIntEnable(ptrHwCfg->ptrI2cBase,
                        I2C_INT_MASK_ADRR_SLAVE | I2C_INT_MASK_STOP_CONDITION | I2C_INT_MASK_TRANSMIT_READY | I2C_INT_RECV_READY);
    }
    else
    {
        /* Enable all the READ interrupt flags */
        I2CIntEnable(ptrHwCfg->ptrI2cBase,
                        I2C_INT_MASK_ADRR_SLAVE | I2C_INT_MASK_STOP_CONDITION | I2C_INT_MASK_TRANSMIT_READY | I2C_INT_RECV_READY);
    }

Let me know if this fixes you issues.

Best regards,

Connor Desmond

Hello Connor,

Unfortunately, it is observed that behaviour is not changed by your source code modification.

6843ODS is recovered from blocking mode by I2C data input from external master device but ACK is not replied.

Also, 6843ODS is recovered from blocking mode even if input data by wrong I2C address is called by external master device.

Please kindly advise to fix this issue.

Best regards,

Taka

Hello,

I am reaching to the relevant experts to assist in your issue. I will respond to this thread once I have an answer.

Best regards,

Connor Desmond

Hello Connor,

I am looking forward to your advice to fix this issue. I am fine if you let me know by when you will answer to me.

Best regards,

Taka

Hello,

Thank you for your patience on this issue. I am in the process for getting a patch for the I2C driver that you are using that will address your issue. Once that patch is in my hands, and then I will post the fix in this thread. I assuming that it will be ready in the next couple of days, but if it is beyond that I will check in on the status.

Best regards,

Connor Desmond

Hi Tom,

It has been being helped offline.
We have confirmed the improvements and still have some requests to fix.
Thank you and best regards,
Hitoshi

Hi Hitoshi,

Can you share the findings or bugFix?

Thanks,

Tom

Hello TOM,

I have sent a message to you accidentally.
I am sorry I can not share the info. on the thread.
Could you please make a new post onto e2e?
Thank you so much for your patient.

Best regards,
Hitoshi Sugawara

Hi Hitoshi,

I have already made a new post in below

IWR6843ISK-ODS: issue on I2C slave driver API - Sensors forum - Sensors - TI E2E support forums

Connor Desmond replied that the I2C slave driver is not ready ... But we need that function.

Best regards,

Tom