adxl345 i2c nrf51422

RE: adxl345 i2c nrf51422

Yassine31 — Wed, 26 Apr 2017 14:55:40 GMT

It's working. Thank you Sigurd

RE: adxl345 i2c nrf51422

Sigurd — Wed, 26 Apr 2017 12:51:41 GMT

For 2) you can add an extra NULL, e.g. ret = nrf_drv_twi_init(&m_twi_master, &config, NULL,NULL); I can upload a KEIL project that uses the drivers if you cannot get it to work.

RE: adxl345 i2c nrf51422

Yassine31 — Wed, 26 Apr 2017 12:50:21 GMT

The version is 12.2

I have two errors, which i managed, i thought that ..., but it still not working

error: #140: too many arguments in function call ret_code = nrf_drv_twi_rx(p_twi_master,slave_addr, pdata, bytes, false);

knowing that in nrf_drv_twi.c it's declared like this:

ret_code_t nrf_drv_twi_rx(nrf_drv_twi_t const * p_instance, uint8_t address, uint8_t * p_data, uint8_t length)

(I deleted the 'FALSE' ... )

error: #165: too few arguments in function call ret = nrf_drv_twi_init(&m_twi_master, &config, NULL);

it's declared like this:

ret_code_t nrf_drv_twi_init(nrf_drv_twi_t const * p_instance, nrf_drv_twi_config_t const * p_config, nrf_drv_twi_evt_handler_t event_handler, void * p_context) So one argument is missing.

RE: adxl345 i2c nrf51422

Sigurd — Wed, 26 Apr 2017 12:20:24 GMT

Hi,

The register addresses is close to identical, so it should not be a big problem to get it to work with ADXL345. Actually the registers that the driver uses have the exact same addresses on both ADXL375 and ADXL345.