Softdevice - how to get twi / i2c address from twi_handler

RE: Softdevice - how to get twi / i2c address from twi_handler

Einar Thorsrud — Tue, 07 May 2024 07:54:02 GMT

Hi Neeraj,

Not directly. The context is provided by nrf_drv_twi_init(), and not nrf_drv_twi_xfer(), so not for each transaction. You could of course provide a pointer to a variable and update that same variable before every call to nrf_drv_twi_xfer(), but that would not give you any benefits compared to using a global variable (it would just make things a bit more complicated).

Einar

RE: Softdevice - how to get twi / i2c address from twi_handler

Neeraj Dhekale — Tue, 07 May 2024 06:22:51 GMT

Hi Einar Thorsrud

Thanks for the reply.

Got it your logic using current_address.

[quote userid="7377" url="~/f/nordic-q-a/110921/softdevice---how-to-get-twi-i2c-address-from-twi_handler/482074"]The p_context is a void pointer that you can use to pass extra information to the event handler,[/quote]

Any chance to pass i2c address to p_context as extra information? if yes, how can I implement it?

Thanks and regards,

Neeraj Dhekale

RE: Softdevice - how to get twi / i2c address from twi_handler

Einar Thorsrud — Mon, 06 May 2024 14:09:39 GMT

Hi,

The NRF_DRV_TWI_EVT_ADDRESS_NACK event is triggered when the slave device does not acknowledge its address. However, the p_context does not hold the address of the non-acknowledging device. The p_context is a void pointer that you can use to pass extra information to the event handler, but it's not automatically filled with any specific data by the TWI driver.

To identify which device is not acknowledging its address, you could modify your code to store the address of the device you're currently trying to communicate with in a global variable. Then, in your event handler, you can check this global variable when you receive the NRF_DRV_TWI_EVT_ADDRESS_NACK event.

uint8_t current_address;

void twi_event_handler(nrf_drv_twi_evt_t const * p_event, void * p_context)
{
    switch (p_event->type)
    {
        case NRF_DRV_TWI_EVT_ADDRESS_NACK:
            printf("No ACK from device with address: 0x%x\n", current_address);
            break;
        // Handle other events...
    }
}

void communicate_with_device(uint8_t address)
{
    current_address = address;
    // Start communication...
}

In this example, before you start communicating with a device, you store its address in current_address. Then, if you receive a NRF_DRV_TWI_EVT_ADDRESS_NACK event, you know that current_address is the address of the device that didn't acknowledge its address.

Please note that this is a simple example and might not cover all your needs. For example, if you're communicating with multiple devices simultaneously from different threads, you'll need a more sophisticated way to track which address corresponds to which NACK event.