AT24C512 + BMI160 + NRF52

RE: AT24C512 + BMI160 + NRF52

awneil — Fri, 21 Jun 2019 07:37:05 GMT

[quote userid="77062" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186196"]@awneil, I agree. This is very confusing, even for me[/quote]

It seems to be a general problem throughout the Nordic documentation:

https://devzone.nordicsemi.com/f/nordic-q-a/48848/pin-configuration-limitation/194009#194009

😞

RE: AT24C512 + BMI160 + NRF52

awneil — Wed, 15 May 2019 08:55:56 GMT

[quote userid="74103" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/187130"]can you tell me how to save the negative value in eeprom like (-2.05) [/quote]

This is standard 'C' - nothing specifically to do with Nordic.

The EEPROM just stores bytes - it neither knows not cares what those bytes represent.

So you need to write functions to take your data, and write it to the EEPROM as a sequence of bytes;

And, conversely, code to read a sequence of bytes from EEPROM and form it into your data.

https://en.wikipedia.org/wiki/Serialization

RE: AT24C512 + BMI160 + NRF52

Sunil vignesh — Wed, 15 May 2019 07:08:15 GMT

HI,

I have combined the code in a same TWI0 as

void E_twi_init (void)
{
    ret_code_t err_code;
const nrf_drv_twi_config_t twi_e_config = {
       .scl                = ARDUINO_SCL_PIN,
       .sda                = ARDUINO_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
       .clear_bus_init     = false
    };

    err_code = nrf_drv_twi_init(&m_twi, &twi_e_config, NULL, NULL);
    
    APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi);
		NRF_LOG_INFO("EEPROM TWI init success...");	
	}
}

/ <e> TWI0_ENABLED - Enable TWI0 instance
//==========================================================
#ifndef TWI0_ENABLED
#define TWI0_ENABLED 1
#endif
// <q> TWI0_USE_EASY_DMA  - Use EasyDMA (if present)
 

#ifndef TWI0_USE_EASY_DMA
#define TWI0_USE_EASY_DMA 1
#endif

// </e>

// <e> TWI1_ENABLED - Enable TWI1 instance
//==========================================================
#ifndef TWI1_ENABLED
#define TWI1_ENABLED 0
#endif
// <q> TWI1_USE_EASY_DMA  - Use EasyDMA (if present)

can you check my code

it is reliable ?! (i.e - It work for long real time process)

#include <stdio.h>
#include "boards.h"
#include "app_util_platform.h"
#include "app_error.h"
#include "nrf_drv_twi.h"
#include "nrf_delay.h"


#include "nrf_log.h"
#include "nrf_log_ctrl.h"
#include "nrf_log_default_backends.h"

#include "bmi160.h"

/* TWI instance ID. */
#define TWI_INSTANCE_ID     0
#define TWI1_INSTANCE_ID     1
#define I2C_24C128_SLAVE_ADDR        (0x50)
#define G_TO_LSB (16384.0f)

#define DPS_TO_LSB (131.072f)

/* Indicates if operation on TWI has ended. */
static volatile bool m_xfer_done = false;

/* TWI instance. */
static const nrf_drv_twi_t m_twi = NRF_DRV_TWI_INSTANCE(TWI_INSTANCE_ID);
//static const nrf_drv_twi_t m_twi_e = NRF_DRV_TWI_INSTANCE(TWI1_INSTANCE_ID);

void eep_WriteByte(uint16_t eep_address, unsigned char val);
unsigned char eep_readByte(uint16_t eep_address);
ret_code_t err_codecpy;

struct bmi160_dev sensor;
struct bmi160_sensor_data accel;
struct bmi160_sensor_data gyro;
struct bmi160_int_settg int_config;

int8_t rslt = BMI160_OK;



void B_twi_init (void)
{
    ret_code_t err_code;

    const nrf_drv_twi_config_t twi_config = {
       .scl                = ARDUINO_SCL_PIN,
       .sda                = ARDUINO_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
       .clear_bus_init     = false
    };

    err_code = nrf_drv_twi_init(&m_twi, &twi_config, NULL, NULL);
    NRF_LOG_INFO("err_code :%d", err_code);
    APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi);
		NRF_LOG_INFO("BMI TWI init success...");	
	}
}

void E_twi_init (void)
{
    ret_code_t err_code;
const nrf_drv_twi_config_t twi_e_config = {
       .scl                = ARDUINO_SCL_PIN,
       .sda                = ARDUINO_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
       .clear_bus_init     = false
    };

    err_code = nrf_drv_twi_init(&m_twi, &twi_e_config, NULL, NULL);
    
    APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi);
		NRF_LOG_INFO("EEPROM TWI init success...");	
	}
}
unsigned char eep_readByte(uint16_t eep_address)
{

    unsigned char eep_by_address[2];
    unsigned char reg=0;
    eep_by_address[1]   = eep_address;
    eep_by_address[0] = (unsigned char)(eep_address << 8);
    // setting the start address
    nrf_drv_twi_tx(&m_twi, I2C_24C128_SLAVE_ADDR, eep_by_address, 2, true);
    // read a byte
    nrf_delay_ms(5);

    nrf_drv_twi_rx(&m_twi, I2C_24C128_SLAVE_ADDR, &reg,1);

    nrf_delay_ms(5);
	return reg;
}
void eep_WriteByte(uint16_t eep_address, unsigned char val)
{

    unsigned char eep_by_address[3];
    eep_by_address[2] = val;
    eep_by_address[1] = eep_address;
    eep_by_address[0] = (unsigned char)(eep_address << 8);

    err_codecpy = nrf_drv_twi_tx(&m_twi, I2C_24C128_SLAVE_ADDR, eep_by_address, 3, false);
    nrf_delay_ms(5);
    if(err_codecpy == 0)
    {
      NRF_LOG_INFO("\r\nWritten Sucess");
    NRF_LOG_FLUSH();
    }

}



int8_t Acc_i2c_Write(uint8_t dev_id, uint8_t reg_addr, uint8_t *reg_data, uint16_t len)
{

    //  NRF_LOG_INFO("WRITE: dev_id: %x reg_addr: %x reg_data: %x len: %i\n", dev_id, reg_addr, *reg_data, len);
	int8_t rslt = 0;
	uint8_t data[len + 1];
	data[0] = reg_addr;
	for (uint16_t i = 0; i < len; i++) {
		data[i + 1] = reg_data[i];
	}
	
	rslt = nrf_drv_twi_tx(&m_twi, dev_id, data, len + 1, false);
	APP_ERROR_CHECK(rslt);
        return rslt;
  
}


int8_t Acc_i2c_Read(uint8_t dev_id, uint8_t reg_addr, uint8_t *reg_data, uint16_t len)
{
	int8_t rslt = 0;
   //     NRF_LOG_INFO("READ: dev_id: %x reg_addr: %x len: %i\n", dev_id, reg_addr, len);
	rslt = nrf_drv_twi_tx(&m_twi, dev_id, &reg_addr, 1, false);
        APP_ERROR_CHECK(rslt);

	if (rslt == 0)
	{
		rslt = nrf_drv_twi_rx(&m_twi, dev_id, reg_data, len);
	}
    //    NRF_LOG_INFO("READ: %x",*reg_data);
	return rslt;
}

void Acc_delay_ms(uint32_t period)
{ 
  nrf_delay_ms( period ) ;
}

void BMI_init (void)
{
    sensor.id = BMI160_I2C_ADDR;         //0x69
    sensor.interface = BMI160_I2C_INTF;  //0x00
    sensor.read = &Acc_i2c_Read;
    sensor.write = &Acc_i2c_Write;
    sensor.delay_ms = &Acc_delay_ms;

    rslt = bmi160_init(&sensor);
    APP_ERROR_CHECK(rslt);

    if(rslt == BMI160_OK){
    NRF_LOG_INFO("BMI160 Initialized...");
    } else {
    NRF_LOG_INFO("BMI160 not Initialized...");
    }NRF_LOG_FLUSH();

    sensor.accel_cfg.odr = BMI160_ACCEL_ODR_1600HZ;
    sensor.accel_cfg.range = BMI160_ACCEL_RANGE_2G;
    sensor.accel_cfg.bw = BMI160_ACCEL_BW_NORMAL_AVG4;
    sensor.accel_cfg.power = BMI160_ACCEL_NORMAL_MODE;

    sensor.gyro_cfg.odr = BMI160_GYRO_ODR_3200HZ;
    sensor.gyro_cfg.range = BMI160_GYRO_RANGE_2000_DPS;
    sensor.gyro_cfg.bw = BMI160_GYRO_BW_NORMAL_MODE;
    sensor.gyro_cfg.power = BMI160_GYRO_NORMAL_MODE;

    rslt = bmi160_set_sens_conf(&sensor);
    APP_ERROR_CHECK(rslt);

     if(rslt == BMI160_OK){
    NRF_LOG_INFO("sensor Configured...");
    } else {
    NRF_LOG_INFO("sensor not Configured...");
    }NRF_LOG_FLUSH();
}
/**
 * @brief Function for reading data from temperature sensor.
 */
static void read_sensor_data()
{
    m_xfer_done = false;
    unsigned char  reg1 = 0;
    bmi160_get_sensor_data((BMI160_ACCEL_SEL | BMI160_GYRO_SEL | BMI160_TIME_SEL), &accel, &gyro, &sensor);
    float accelX = ((((float)accel.x) / G_TO_LSB) * 9.80655); // in m/s^2
      float gyrX = ((((float)gyro.x) / DPS_TO_LSB) * 0.0174532925); // in rad/sec
      NRF_LOG_INFO("DataX in m/s^2   : " NRF_LOG_FLOAT_MARKER, 
      NRF_LOG_FLOAT( accelX));
      NRF_LOG_INFO("DataY in rad/sec : " NRF_LOG_FLOAT_MARKER, 
      NRF_LOG_FLOAT(gyrX));
      NRF_LOG_FLUSH();
       nrf_delay_ms(50);
       eep_WriteByte(0x00051,accelX);
        reg1=eep_readByte(0x00051);
	if(reg1!=0){
		NRF_LOG_INFO("\r\n Read value 51 : %d",reg1);
                NRF_LOG_FLUSH();
                nrf_delay_ms(5);
	}
	else if(reg1==0){
        NRF_LOG_INFO("\r\n can't Read value 51 ");
	 nrf_delay_ms(5);
	}
}

/**
 * @brief Function for main application entry.
 */
int main(void)
{ bsp_board_init(BSP_INIT_LEDS);
    APP_ERROR_CHECK(NRF_LOG_INIT(NULL));
    NRF_LOG_DEFAULT_BACKENDS_INIT();
     NRF_LOG_INFO("EEPROM get started.\n");
    NRF_LOG_FLUSH();
    Acc_delay_ms(100);


    E_twi_init();
    Acc_delay_ms(50);
    unsigned char  reg1 = 0;
    
    nrf_delay_ms(1000);
    nrf_delay_ms(5);
	   reg1=eep_readByte(0x0000);
	if(reg1!=0){
		NRF_LOG_INFO("\r\n Read value 00 : %x",reg1);
                NRF_LOG_FLUSH();
                nrf_delay_ms(5);
	}

	else if(reg1==0){
	 nrf_delay_ms(5);
	}
        nrf_delay_ms(3000);

     eep_WriteByte(0x0000,'S');
    nrf_delay_ms(5);
	   reg1=eep_readByte(0x0000);
	if(reg1!=0){
		NRF_LOG_INFO("\r\n Read value 00 : %x",reg1);
                NRF_LOG_FLUSH();
                nrf_delay_ms(5);
	}

	else if(reg1==0){
	 nrf_delay_ms(5);
	}

    NRF_LOG_INFO("BMI160 get started.\n");
    NRF_LOG_FLUSH();
    Acc_delay_ms(100);
   // nrf_drv_twi_disable(&m_twi_e);


    //B_twi_init();
    Acc_delay_ms(50);

    BMI_init();
    Acc_delay_ms(100);
    uint8_t reg_addr = BMI160_CHIP_ID_ADDR;
    uint8_t data;
    uint16_t len = 1;
    Acc_delay_ms(1000);
    rslt = bmi160_get_regs(reg_addr, &data, len, &sensor);
    NRF_LOG_INFO("Data:%x", data);
    NRF_LOG_FLUSH();
    Acc_delay_ms(3000);
    
    while (true)
    {
        nrf_delay_ms(250);
        read_sensor_data();

        NRF_LOG_FLUSH();
    }
}

/** @} */

OUTPUT:

<info> app: EEPROM get started.

<info> app: EEPROM TWI init success...
<info> app: 
 Read value 00 : 53
<info> app: 
Written Sucess
<info> app: 
 Read value 00 : 53
<info> app: BMI160 get started.

<info> app: BMI160 Initialized...
<info> app: sensor Configured...
<info> app: Data:D1
<info> app: DataX in m/s^2   : 2.60
<info> app: DataY in rad/sec : -0.00
<info> app: 
Written Sucess
<info> app: 
 Read value 51 : 2
<info> app: DataX in m/s^2   : 2.56
<info> app: DataY in rad/sec : -0.00
<info> app: 
Written Sucess
<info> app: 
 Read value 51 : 2

can you tell me how to save the negative value in eeprom like (-2.05) in an address

RE: AT24C512 + BMI160 + NRF52

awneil — Fri, 10 May 2019 13:14:07 GMT

[quote userid="77062" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186415"]the TWI transaction manager library can schedule transfer requests from different contexts and realize them in the order they were scheduled[/quote]

Sunil vignesh obviously, that adds a layer of complexity.

The alternative is that you have to manage the bus accesses yourself in your own code so that the 2 sensors do not interfere with each other.

If you have a simple use case, with only the 2 sensors, it may not be (too) difficult to manage this "manually"...

But only you know the details of your application - so only you can decide what's appropriate to it.

RE: AT24C512 + BMI160 + NRF52

Øyvind — Fri, 10 May 2019 12:05:26 GMT

The application communicates over the two-wire interface (TWI) with two devices: the MMA7660 triple axis accelerometer and the LM75B temperature sensor.

The example uses the RTC peripheral to generate regular tick events (32 per second). The interrupt handler, executed in reaction to each tick event, schedules data transfers to read the current values from the devices. The obtained values are averaged and printed every 500 milliseconds or when the tilting status reported by the accelerometer changes. Additionally, the user can generate asynchronous data transfer requests (reading all registers available in the devices) by pressing Button 1 or Button 4. Such additional transfer requests show that the TWI transaction manager library can schedule transfer requests from different contexts and realize them in the order they were scheduled.

RE: AT24C512 + BMI160 + NRF52

awneil — Fri, 10 May 2019 11:51:56 GMT

[quote userid="74103" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186388"]my concern is to make multiple slaves for a one master is getting complexes[/quote]

I suggest that you go back to basics:

Make sure that you understand the basics of I2C.
Start with the TWI Scanner example.
This will verify that your hardware connections are correct & working, and confirm that you have the correct Slave Addresses.
Spend time studying this example, to understand how it works.
Practice using the debugger to step through your code, examine variables, etc
Practice using an oscilloscope or logic analyser to view what's happening on the wires.
Save the Project - so that you can come back to it for reference later.
Use the TWI Master example with just one of your slaves.
Get that Slave working on its own.
Again, practice using the debugger, scope, etc.
Save the Project - you will need it later.
Start again with the unmodified TWI Master example with the other of your slaves.
Get that Slave working on its own.
Save the Project - so that you can come back to it for reference later
Now merge your two TWI Master projects together

I suggest that you adopt an approach like this for all your projects:

Start with working examples;
Know your tools;
Take small steps at a time;
Keep "snapshots" of your work so that you can go back if things go wrong.

RE: AT24C512 + BMI160 + NRF52

Sunil vignesh — Fri, 10 May 2019 11:39:24 GMT

[quote userid="77062" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186395"]Not sure what example you mean, as the link points to the start of the SDK documentation.[/quote]

is this TWI Transaction Manager Example

<InstallFolder>\examples\peripheral\twi_master_using_nrf_twi_mngr

RE: AT24C512 + BMI160 + NRF52

Øyvind — Fri, 10 May 2019 11:35:26 GMT

[quote user="Sunil vignesh"]but my concern is to make multiple slaves for a one master is getting complexes.[/quote]

In your case, you should only need to configure one master. As long as the sensor and EEPROM are connected and powered correctly, you should only need to issue their address and then the command (as per the I2C standard).

[quote user="Sunil vignesh"]can yu please explain how this example works.[/quote]

Not sure what example you mean, as the link points to the start of the SDK documentation.

[quote user="Sunil vignesh"]can you please how these functions are working:[/quote]

These are part of the Common Application Error Handler, more information here and here.

Kind regards,

Øyvind

RE: AT24C512 + BMI160 + NRF52

Sunil vignesh — Fri, 10 May 2019 11:19:11 GMT

Thank you,

i understand what awneil going to tell. but my concern is to make multiple slaves for a one master is getting complexes.

can yu please explain how this example works.

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fstruct_sdk%2Fstruct%2Fsdk_nrf5_latest.html&cp=5_0

can you please how these functions are working:

NRF_TWI_MNGR_DEF(m_nrf_twi_mngr, MAX_PENDING_TRANSACTIONS, TWI_INSTANCE_ID);
APP_TIMER_DEF(m_timer);



 err_code = nrf_twi_mngr_init(&m_nrf_twi_mngr, &config);
    APP_ERROR_CHECK(err_code);
    
    
    
     APP_ERROR_CHECK(nrf_twi_mngr_perform(&m_nrf_twi_mngr, NULL, lm75b_init_transfers,
        LM75B_INIT_TRANSFER_COUNT, NULL));
        
    APP_ERROR_CHECK(nrf_twi_mngr_perform(&m_nrf_twi_mngr, NULL, mma7660_init_transfers,
        MMA7660_INIT_TRANSFER_COUNT, NULL));

RE: AT24C512 + BMI160 + NRF52

Øyvind — Fri, 10 May 2019 07:45:48 GMT

I'm sorry, but this is just code from your software. I need you to debug your software.

Please see this page.

Kind regards,
Øyvind

RE: AT24C512 + BMI160 + NRF52

awneil — Thu, 09 May 2019 15:31:19 GMT

[quote userid="74103" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186244"]when i changed the different scl sda pins separate then it works[/quote]

That has already been explained to you: you cannot have two different TWI Masters sharing the same pins!

[quote userid="74103" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186244"]i need to connect both eeprom and sensor in a same pins[/quote]

Then you must use just one TWI Master - as Øyvind showed you in the diagram he posted earlier:

RE: AT24C512 + BMI160 + NRF52

Sunil vignesh — Thu, 09 May 2019 15:08:40 GMT

The error code

#define ARDUINO_SCL_PIN             27    // SCL signal pin
#define ARDUINO_SDA_PIN             26    // SDA signal pin
#define ARDUINO1_I2C_SCL_PIN 30
#define ARDUINO1_I2C_SDA_PIN 31

void twi_init (void)
{
    ret_code_t err_code;

    const nrf_drv_twi_config_t twi_mma_EEP_config  = {
       .scl                = ARDUINO_SCL_PIN,
       .sda                = ARDUINO_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
       
    };
    const nrf_drv_twi_config_t twi_config = {
       .scl                = ARDUINO_SCL_PIN,
       .sda                = ARDUINO_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
      // .clear_bus_init     = false
    };

    err_code = nrf_drv_twi_init(&m_twi_mma_EEP, &twi_mma_EEP_config, NULL, NULL); //twi_handler
     APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi_mma_EEP);
		NRF_LOG_INFO("TWI0 init success...");	
	}
    err_code = nrf_drv_twi_init(&m_twi, &twi_config, NULL, NULL);

       APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi);
		NRF_LOG_INFO("TWI init success...");	
	}
		
   err_codecpy=err_code;
		nrf_delay_ms(5);
}

code changed

#define ARDUINO_SCL_PIN             27    // SCL signal pin
#define ARDUINO_SDA_PIN             26    // SDA signal pin
#define ARDUINO1_I2C_SCL_PIN 30
#define ARDUINO1_I2C_SDA_PIN 31

void twi_init (void)
{
    ret_code_t err_code;

    const nrf_drv_twi_config_t twi_mma_EEP_config  = {
       .scl                = ARDUINO1_I2C_SCL_PIN,
       .sda                = ARDUINO1_I2C_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
       
    };
    const nrf_drv_twi_config_t twi_config = {
       .scl                = ARDUINO_SCL_PIN,
       .sda                = ARDUINO_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
      // .clear_bus_init     = false
    };

    err_code = nrf_drv_twi_init(&m_twi_mma_EEP, &twi_mma_EEP_config, NULL, NULL); //twi_handler
     APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi_mma_EEP);
		NRF_LOG_INFO("TWI0 init success...");	
	}
    err_code = nrf_drv_twi_init(&m_twi, &twi_config, NULL, NULL);

       APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi);
		NRF_LOG_INFO("TWI init success...");	
	}
		
   err_codecpy=err_code;
		nrf_delay_ms(5);
}

when i changed the different scl sda pins separate then it works

but my case i need to connect both eeprom and sensor in a same pins

RE: AT24C512 + BMI160 + NRF52

Øyvind — Thu, 09 May 2019 13:33:20 GMT

I'm sorry, I am not able to see what is wrong from your code. Can you please debug the code and give me the error message you receive with the fatal error?

Kind regards,
Øyvind

RE: AT24C512 + BMI160 + NRF52

Øyvind — Thu, 09 May 2019 13:30:21 GMT

As the device has EasyDMA present, you want to enable this:

TWI0_USE_EASY_DMA 1

RE: AT24C512 + BMI160 + NRF52

awneil — Thu, 09 May 2019 13:15:25 GMT

[quote userid="74103" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186165"]if i give same sda and scl pin to eeprom and bmi. it gives fatal error[/quote]

If you're going to use two separate TWI Masters, then they need to be separate - they cannot share the same pins!

Again, this is clearly stated in the Product Specification:

"Only one peripheral can be assigned to drive a particular GPIO pin at a time. Failing to do so may result in unpredictable behavior."

RE: AT24C512 + BMI160 + NRF52

Øyvind — Thu, 09 May 2019 12:55:52 GMT

My mouse pointer is all over the place today, did mean to suggest this as the answer for this case.

[quote user="awneil"]I find it unclear whether it is a separate module, or if TWIM and/or TWIS are just "operating modes" of the TWI module?[/quote]

@awneil, I agree. This is very confusing, even for me. But the easy explanation is:

TWI is legacy driver for nRF51
TWIM and TWIS are new for nRF52 which also uses EasyDMA

There is no connection between TWI and TWIM/TWIS.

[quote user="awneil"]and are there two TWIS modules plus two TWIM modules - or is it just a total of two modules, each of which can be either TWIM or TWIS ?[/quote]

Have a look at the memory Instantiation, as long as they do not collide. I.e. Address 0x40003000 is shared between SPIM, SPIS, SPI, TWIM, TWIS and TWI. Only one can be instance can be used at one memory location. Address 0x40003000 has the same. So you can have an instance of TWIM in each, but then you have filled max instances.

I hope this helps to clarify 🙂

RE: AT24C512 + BMI160 + NRF52

Sunil vignesh — Thu, 09 May 2019 11:59:11 GMT

hi,

please verify the code:


#include <stdio.h>
#include "boards.h"
#include "app_util_platform.h"
#include "app_error.h"
#include "nrf_drv_twi.h"
#include "nrf_delay.h"
#include "bmi160.h"

#include "nrf_log.h"
#include "nrf_log_ctrl.h"
#include "nrf_log_default_backends.h"


#define G_TO_LSB (16384.0f)

#define DPS_TO_LSB (131.072f)
#define I2C_24C128_SLAVE_ADDR        (0x57)
#define BMI160_I2C_ADDR1                      UINT8_C(0x68)

#define ARDUINO1_I2C_SCL_PIN 30
#define ARDUINO1_I2C_SDA_PIN 31
/* TWI instance ID. */
#define TWI0_INSTANCE_ID     0
#define TWI1_INSTANCE_ID     1

struct bmi160_dev sensor;
struct bmi160_sensor_data accel;
struct bmi160_sensor_data gyro;
struct bmi160_int_settg int_config;

int8_t rslt = BMI160_OK;
/* Indicates if operation on TWI has ended. */
static volatile bool m_xfer_done = false;

/* TWI instance. */
static const nrf_drv_twi_t m_twi_mma_EEP = NRF_DRV_TWI_INSTANCE(TWI0_INSTANCE_ID);
static const nrf_drv_twi_t m_twi = NRF_DRV_TWI_INSTANCE(TWI1_INSTANCE_ID);

void eep_WriteByte(uint16_t eep_address, unsigned char val);
unsigned char eep_readByte(uint16_t eep_address);
ret_code_t err_codecpy;
float accelX;



void twi_init (void)
{
    ret_code_t err_code;

    const nrf_drv_twi_config_t twi_mma_EEP_config  = {
       .scl                = ARDUINO1_I2C_SCL_PIN,
       .sda                = ARDUINO1_I2C_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
       
    };
    const nrf_drv_twi_config_t twi_config = {
       .scl                = ARDUINO_SCL_PIN,
       .sda                = ARDUINO_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
      // .clear_bus_init     = false
    };

    err_code = nrf_drv_twi_init(&m_twi_mma_EEP, &twi_mma_EEP_config, NULL, NULL); //twi_handler
     APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi_mma_EEP);
		NRF_LOG_INFO("TWI0 init success...");	
	}
    err_code = nrf_drv_twi_init(&m_twi, &twi_config, NULL, NULL);

       APP_ERROR_CHECK(err_code);
    if (NRF_SUCCESS == err_code)
	{
		nrf_drv_twi_enable(&m_twi);
		NRF_LOG_INFO("TWI init success...");	
	}
		
   err_codecpy=err_code;
		nrf_delay_ms(5);
}

unsigned char eep_readByte(uint16_t eep_address){

    unsigned char eep_by_address[2];
unsigned char reg=0;
    eep_by_address[1]   = eep_address;
    eep_by_address[0] = (unsigned char)(eep_address << 8);
    // setting the start address
    nrf_drv_twi_tx(&m_twi_mma_EEP, I2C_24C128_SLAVE_ADDR, eep_by_address, 2, true);
    // read a byte
    nrf_delay_ms(5);

    nrf_drv_twi_rx(&m_twi_mma_EEP, I2C_24C128_SLAVE_ADDR, &reg,1);

    nrf_delay_ms(5);
	return reg;
}
void eep_WriteByte(uint16_t eep_address, unsigned char val){

    unsigned char eep_by_address[3];
    eep_by_address[2] = val;
    eep_by_address[1] = eep_address;
    eep_by_address[0] = (unsigned char)(eep_address << 8);

    err_codecpy = nrf_drv_twi_tx(&m_twi_mma_EEP, I2C_24C128_SLAVE_ADDR, eep_by_address, 3, false);
    nrf_delay_ms(5);
    if(err_codecpy == 0)
    {
      NRF_LOG_INFO("\r\nWritten Sucess");
    NRF_LOG_FLUSH();
    }

}

int8_t Acc_i2c_Write(uint8_t dev_id, uint8_t reg_addr, uint8_t *reg_data, uint16_t len)
{

    //  NRF_LOG_INFO("WRITE: dev_id: %x reg_addr: %x reg_data: %x len: %i\n", dev_id, reg_addr, *reg_data, len);
	int8_t rslt = 0;
	uint8_t data[len + 1];
	data[0] = reg_addr;
	for (uint16_t i = 0; i < len; i++) {
		data[i + 1] = reg_data[i];
	}
	
	rslt = nrf_drv_twi_tx(&m_twi, dev_id, data, len + 1, false);
	APP_ERROR_CHECK(rslt);
        return rslt;
  
}


int8_t Acc_i2c_Read(uint8_t dev_id, uint8_t reg_addr, uint8_t *reg_data, uint16_t len)
{
	int8_t rslt = 0;
   //     NRF_LOG_INFO("READ: dev_id: %x reg_addr: %x len: %i\n", dev_id, reg_addr, len);
	rslt = nrf_drv_twi_tx(&m_twi, dev_id, &reg_addr, 1, false);
        APP_ERROR_CHECK(rslt);

	if (rslt == 0)
	{
		rslt = nrf_drv_twi_rx(&m_twi, dev_id, reg_data, len);
	}
    //    NRF_LOG_INFO("READ: %x",*reg_data);
	return rslt;
}

void Acc_delay_ms(uint32_t period)
{ 
	
/*if (period==NULL){
period = 1;
}// delay time*/
	
  nrf_delay_ms( period ) ;
}

void BMI_init (void)
{
    sensor.id = BMI160_I2C_ADDR;         //0x69
    sensor.interface = BMI160_I2C_INTF;  //0x00
    sensor.read = &Acc_i2c_Read;
    sensor.write = &Acc_i2c_Write;
    sensor.delay_ms = &Acc_delay_ms;

    rslt = bmi160_init(&sensor);
    APP_ERROR_CHECK(rslt);

    if(rslt == BMI160_OK){
    NRF_LOG_INFO("BMI160 Initialized...");
    } else {
    NRF_LOG_INFO("BMI160 not Initialized...");
    }NRF_LOG_FLUSH();

    sensor.accel_cfg.odr = BMI160_ACCEL_ODR_1600HZ;
    sensor.accel_cfg.range = BMI160_ACCEL_RANGE_2G;
    sensor.accel_cfg.bw = BMI160_ACCEL_BW_NORMAL_AVG4;
    sensor.accel_cfg.power = BMI160_ACCEL_NORMAL_MODE;

    sensor.gyro_cfg.odr = BMI160_GYRO_ODR_3200HZ;
    sensor.gyro_cfg.range = BMI160_GYRO_RANGE_2000_DPS;
    sensor.gyro_cfg.bw = BMI160_GYRO_BW_NORMAL_MODE;
    sensor.gyro_cfg.power = BMI160_GYRO_NORMAL_MODE;

    rslt = bmi160_set_sens_conf(&sensor);
    APP_ERROR_CHECK(rslt);

     if(rslt == BMI160_OK){
    NRF_LOG_INFO("sensor Configured...");
    } else {
    NRF_LOG_INFO("sensor not Configured...");
    }NRF_LOG_FLUSH();
}

static void read_sensor_data()
{
      m_xfer_done = false;
      bmi160_get_sensor_data((BMI160_ACCEL_SEL | BMI160_GYRO_SEL | BMI160_TIME_SEL), &accel, &gyro, &sensor);
      /*NRF_LOG_INFO("DataX:%d", accel.x);
      NRF_LOG_INFO("DataY:%d", accel.y);
      NRF_LOG_INFO("DataZ:%d", accel.z);
      NRF_LOG_INFO("GyroX:%d", gyro.x);
      NRF_LOG_INFO("GyroY:%d", gyro.y);
      NRF_LOG_INFO("GyroZ:%d", gyro.z);*/

      /* need the calculation to study  */
      accelX = ((((float)accel.x) / G_TO_LSB) * 9.80655); // in m/s^2
      float gyrX = ((((float)gyro.x) / DPS_TO_LSB) * 0.0174532925); // in rad/sec
      NRF_LOG_INFO("DataX in m/s^2   : " NRF_LOG_FLOAT_MARKER, 
      NRF_LOG_FLOAT( accelX));
      NRF_LOG_INFO("DataY in rad/sec : " NRF_LOG_FLOAT_MARKER, 
      NRF_LOG_FLOAT(gyrX));
      NRF_LOG_FLUSH();
}


/**
 * @brief Function for main application entry.
 */
int main(void)
{
    APP_ERROR_CHECK(NRF_LOG_INIT(NULL));
    NRF_LOG_DEFAULT_BACKENDS_INIT();
    NRF_LOG_INFO("\r\nTWI sensor example started.");
    NRF_LOG_FLUSH();
    twi_init();
    NRF_LOG_FLUSH();

	unsigned char  reg1 = 0;
        Acc_delay_ms(50);

    BMI_init();
    Acc_delay_ms(100);
    uint8_t reg_addr = BMI160_CHIP_ID_ADDR;
    uint8_t data;
    uint16_t len = 1;
    Acc_delay_ms(1000);
    rslt = bmi160_get_regs(reg_addr, &data, len, &sensor);
    NRF_LOG_INFO("Data:%x", data);
    eep_WriteByte(0x0000,data);

    while(true)
    {
        nrf_delay_ms(1000);
		//	    eep_WriteByte(0x0000,'w');
	 nrf_delay_ms(5);
	//eep_WriteByte(0x0001,'B');
	 nrf_delay_ms(5);
	   reg1=eep_readByte(0x0000);
	if(reg1!=0){
		NRF_LOG_INFO("\r\n Read value 00 : %x",reg1);
                NRF_LOG_FLUSH();
                nrf_delay_ms(5);
	}

	else if(reg1==0){
	 nrf_delay_ms(5);
	}
        reg1=eep_readByte(0x00051);
	if(reg1!=0){
		NRF_LOG_INFO("\r\n Read value 51 : %c",reg1);
                NRF_LOG_FLUSH();
                nrf_delay_ms(5);
	}
	else if(reg1==0){
	 nrf_delay_ms(5);
	}
        read_sensor_data();
        eep_WriteByte(0x00051,accelX);
        reg1=eep_readByte(0x00051);
	if(reg1!=0){
		NRF_LOG_INFO("\r\n Read value 51 : %d",reg1);
                NRF_LOG_FLUSH();
                nrf_delay_ms(5);
	}
	else if(reg1==0){
	 nrf_delay_ms(5);
	}



    }
}

output:

it works in two different TWI wire pins

that is

eeprom scl in 27

eeprom sda in 26

bmi scl in 30

bmi sda in 31

if i give same sda and scl pin to eeprom and bmi. it gives fatal error ;

can you give how to manage this in single TWI wire.

i have seen TWI mangr

in that

i have difficult to interface the eeprom with bmi

can you give a solution

RE: AT24C512 + BMI160 + NRF52

awneil — Thu, 09 May 2019 09:46:06 GMT

[quote userid="74103" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186128"]Can you please tell me what is the difference of TWI0 and TWI1[/quote]

Again, look at the Product Specification!

The Block Diagram clearly shows you that there are two TWIM modules - called "TWIM0" and "TWIM1":

Yes, you could use both modules - with one slave on each.

But the whole point of I2C as a bus is that each one can support multiple peripherals - as Øyvind showed:

RE: AT24C512 + BMI160 + NRF52

Sunil vignesh — Thu, 09 May 2019 09:38:18 GMT

Hi, Can you please tell me what is the difference of TWI0 and TWI1

#ifndef TWI0_ENABLED
#define TWI0_ENABLED 1
#endif
// <q> TWI0_USE_EASY_DMA  - Use EasyDMA (if present)
 

#ifndef TWI0_USE_EASY_DMA
#define TWI0_USE_EASY_DMA 1
#endif

// </e>

// <e> TWI1_ENABLED - Enable TWI1 instance
//==========================================================
#ifndef TWI1_ENABLED
#define TWI1_ENABLED 0
#endif
// <q> TWI1_USE_EASY_DMA  - Use EasyDMA (if present)
 

#ifndef TWI1_USE_EASY_DMA
#define TWI1_USE_EASY_DMA 0
#endif

shall i enable both twi instance.

what is

TWI0_USE_EASY_DMA 1 - use case?

#define TWI1_USE_EASY_DMA 0 - use case?

if i enable both twi instance

means

the EASY_DMA of TWI1 also be '1' or '0'

RE: AT24C512 + BMI160 + NRF52

Sunil vignesh — Thu, 09 May 2019 09:34:30 GMT

Hi,

can i use

#define TWI0_ENABLED 1
#define TWI1_ENABLED 1

i.e
 two TWI Instance. one for EEPROM and another for SENSOR. 
it means is it TWIM or TWIS ?

is it advisable to go with two twi instance at a time

RE: AT24C512 + BMI160 + NRF52

awneil — Thu, 09 May 2019 08:13:27 GMT

[quote userid="77062" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186072"]I recommend reading the TWIM chapter and the TWIS chapter in the product specification for nRF52832[/quote]

But could you clarify the distinction between those and the "TWI — I²C compatible two-wire interface" - also in the product specification for nRF52832?

I find it unclear whether it is a separate module, or if TWIM and/or TWIS are just "operating modes" of the TWI module?

Or TWI is an "operating mode" of the TWIM module?

Or what??

The block diagram is not helpful as it shows no "TWI" module.

EDIT

and are there two TWIS modules plus two TWIM modules - or is it just a total of two modules, each of which can be either TWIM or TWIS ?

EDIT 2

The block diagram clearly suggests that there two TWIS modules plus two TWIM modules:

but the 'Key Features' at the start of the Product Specification says:

Up to 2x I2C compatible 2-wire master/slave

So it looks like the block diagram is misleading?

RE: AT24C512 + BMI160 + NRF52

awneil — Thu, 09 May 2019 07:58:59 GMT

[quote userid="74103" url="~/f/nordic-q-a/47060/at24c512-bmi160-nrf52/186004"]which one i need to act as slave and master[/quote]

Neither - they would both be slaves!

The nRF52832 would be the master - as Øyvind explains.

It sounds like you need to do some study on the basics of I2C.

It is a very well-established and widely-used standard - so there is plenty of material available; eg,

https://www.nxp.com/docs/en/user-guide/UM10204.pdf

https://en.wikipedia.org/wiki/I%C2%B2C

https://i2c.info/

https://learn.sparkfun.com/tutorials/i2c/all

RE: AT24C512 + BMI160 + NRF52

Øyvind — Thu, 09 May 2019 07:00:58 GMT

Hi,

I recommend reading the TWIM chapter and the TWIS chapter in the product specification for nRF52832.

The master device (TWIM) is in your case the nRF58832, while sensor and EEPROM are slaves.

If your nRF52832 will work as a slave (TWIS), then you need another microcontroller functioning as a master.

You will find a suitable example to communicate with two devices in the TWI Transaction Manager Example which I linked to yesterday.

Kind regards,
Øyvind

RE: AT24C512 + BMI160 + NRF52

Sunil vignesh — Wed, 08 May 2019 14:07:15 GMT

Hi,

Thank you for your reply.,

i have used the twi scanner, and sensor.

if i going to use one sensor and one EEPROM.

which one i need to act as slave and master.

how to mange the two communications

RE: AT24C512 + BMI160 + NRF52

Øyvind — Wed, 08 May 2019 13:00:52 GMT

Hello,

The nRF5 SDK includes several examples of how to use the TWI peripheral.

examples\peripheral\twi_master_using_nrf_twi_mngr

examples\peripheral\twi_master_with_twis_slave

examples\peripheral\twi_scanner

examples\peripheral\twi_sensor

A good place to start is with the TWI Scanner to ensure you can find the devices on the bus.

Kind regards,
Øyvind