NRF_ERROR_DRV_TWI_ERR_ANACK ?

RE: NRF_ERROR_DRV_TWI_ERR_ANACK ?

Karl Ylvisaker — Fri, 22 Oct 2021 08:16:22 GMT

Hello again, Rixtronixlab

Great - I am glad to see that the devices are showing up in the scanner (so we know there is no hardware issues), and that you have found the right addresses for your device!

[quote user="RixtronixLAB"]I wrote for WRITE :[/quote][quote user="RixtronixLAB"]how can I write for READ ?[/quote]

I would recommend that you make use of the nrf_drv_twi_xfer function in combination with the NRF_DRV_TWI_XFER_DESC_TX and _RX transfer descriptors, instead of the deprecated nrf_drv_twi_tx and _rx functions with manually loaded packets, for your transfers. The nrf_drv_twi_xfer function gives you a lot more functionality easily accessible (see the different FLAGS descriptions), compared to the deprecated versions.

If you would still like to use the deprecated functions you could see their usage demonstrated in the twi_sensor example.

Are you creating your device's driver from scratch, or are you basing it on an existing driver for the device?
Usually, the header file of provided drivers will include all the registers as #defines, with a different name for read and write of the same register - since the values are different. This is a usual way to do it, in order to avoid manually having to add the read write bit, and to avoid confusion.

Best regards,
Karl

RE: NRF_ERROR_DRV_TWI_ERR_ANACK ?

RixtronixLAB — Fri, 22 Oct 2021 02:34:20 GMT

I wrote for WRITE :

//WRITE TO 0xFE REGISTER ON MAX17408 (CMD) BEGIN
                  buffer_tx[0] = 0xFE;
                   buffer_tx[1] = 0x54;
                   buffer_tx[2] = 0x00;
               ret = nrf_drv_twi_tx(&m_twi_master_MAX17048, 0X36, buffer_tx, 3, false);

how can I write for READ ?

RE: NRF_ERROR_DRV_TWI_ERR_ANACK ?

RixtronixLAB — Fri, 22 Oct 2021 02:30:19 GMT

The address is 0x36,

////////////////////////////////
#define MAX1704x_ADDRESS 0x36 // Unshifted I2C address. Becomes 0x6C for write and 0x6D for read.

RE: NRF_ERROR_DRV_TWI_ERR_ANACK ?

RixtronixLAB — Thu, 21 Oct 2021 12:54:37 GMT

the schematic :

nfo> app: TWI scanner started.

nfo> app: TWI device detected at address 0x8.

nfo> app: TWI device detected at address 0x36.

nfo> app: TWI device detected at address 0x3C.

nfo> app: TWI device detected at address 0x50.

nfo> app: TWI device detected at address 0x51.

nfo> app: TWI device detected at address 0x52.

nfo> app: TWI device detected at address 0x53.

nfo> app: TWI device detected at address 0x54.

nfo> app: TWI device detected at address 0x55.

nfo> app: TWI device detected at address 0x56.

nfo> app: TWI device detected at address 0x57.

from MAX17048 datasheet,

The 7-bit slave address
is fixed to 0x6C (write)/0x6D (read):

Any clues ? thanks

RE: NRF_ERROR_DRV_TWI_ERR_ANACK ?

Karl Ylvisaker — Thu, 21 Oct 2021 11:32:11 GMT

Hello,

Your error indicates that the address is not acknowledged. How have you connected the TWI slaves to the nRF, could you show a diagram or schematic exempt?

Please try to run the TWI scanner example from the SDK to ensure that the slave devices can be found on the bus, and let me know what your logger says when you run this example.

Best regards,
Karl

RE: NRF_ERROR_DRV_TWI_ERR_ANACK ?

RixtronixLAB — Thu, 21 Oct 2021 07:36:48 GMT

the buffer is correct but p_data is different, what do I miss here ?

Screenshot :