Cannot connect to ATECC508A through TWI with NRF52832. Tested with nRF5_SDK_12 twi_master and deprecated twi_sw_master. It was working fine only with NRF51822 nRF5_SDK_12 using deprecated twi_sw_master.
Cannot connect to ATECC508A through TWI with NRF52832. Tested with nRF5_SDK_12 twi_master and deprecated twi_sw_master. It was working fine only with NRF51822 nRF5_SDK_12 using deprecated twi_sw_master.
Have you checked that you have connected the correct pins defined in your code? Do you get any error codes? Have you checked the bus using a logic analyzer, to see if there are any activity?
Have you checked that you have connected the correct pins defined in your code? Do you get any error codes? Have you checked the bus using a logic analyzer, to see if there are any activity?
Hi,
I also have this problem, when connect to ATECC508A and send a simple info command, but I always got
NRF_DRV_TWI_EVT_ADDRESS_NACK and NRF_DRV_TWI_EVT_DATA_NACK and never get it done.
I re-send the info command when receiving NRF_DRV_TWI_EVT_ADDRESS_NACK or NRF_DRV_TWI_EVT_DATA_NACK but situation is the same.
Any idea what's wrong?
thanks..
If you get an address or data NACK, the TWI peripheral does not find the device on the TWI bus. Are you sure that the address and pin connections are correct? You can check that the device is detected and its address by running the TWI Scanner example.
hi,
thanks for the reply, i did use TWI scanner and found the correct address of my I2C device,
strange thing is, if I send write command when I got ADDRESS_NACK, sometimes i get DATA_NACK,
I suspect that I sent the wrong command packet to I2C?
thanks..
That is strange, the TWI peripheral should not proceed with the data if the slave does not ACK the address. It is hard to say anything about what could be causing this without seeing a logic trace of the bus, etc.