Nrf52840 one wire protocol usage with MAX17211 IC.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Tue, 15 Mar 2022 12:48:28 GMT

[quote user="vibe"]are you getting a NRF_DRV_TWI_EVT_ADDRESS_NACK or NRF_DRV_TWI_EVT_DATA_NACK event?[/quote]

You are only handling the NRF_DRV_TWI_EVT_DONE event in your twi_handler(), and ignoring NRF_DRV_TWI_EVT_ADDRESS_NACK and NRF_DRV_TWI_EVT_DATA_NACK. Please add these events to your handler and see if either of these are triggered.

Your screenshot does not show the source file from where you are getting the "unsigned conversion from 'int' to 'uint8_t' {aka 'unsigned char'} changes value from '437' to '181' [-Woverflow]" warning from.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Tue, 15 Mar 2022 10:02:56 GMT

I am getting warning as shown below:-

#define NPACKCFG_REG 0x1B5

when i try to read NPACKCFG_REG some conversion is happening.

There are actually 2 slaves on the same i2c instance.

I2c1_slave address = 0x6B

I2c2_slave address = 0x6C

I am able to communicate with slave 1 but when i try to communicate with slave 2 it gets hanged while sending data through nrf_drv_twi_tx in i2c_register_read_max17211 function.

/*****************************************************************************
* Copyright (c) [2021], Netobjex INC
* All rights reserved.
*
* File:    task_psf_comm.c
* Summary: PSF Control Task
*
*/

#include <stdint.h>
#include <stdio.h>
#include <string.h>

#include "error_defs.h"

#include "task_psf_comm.h"
#include "FreeRTOS.h"
#include "task.h"
#include "semphr.h"
#include "timers.h"

#include "tasks.h"
#include "boards.h"
#include "nrf_gpio.h"
#include "nrf_drv_gpiote.h"

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

#include "main.h"
#include "task_led_button.h"

#include "product_config.h"
#include "nrf_drv_twi.h"
#include "psf_i2c.h"
#include "bq24292i.h"
#include "max17211_i2c.h"


/* I2C SLAVE 1*/
#define BQ2429_ADDRESS_LEN  1         //BQ2429
#define BQ2429_ADDRESS     (0xD6>>1)  //BQ2429 Device Address
#define BQ2429_WHO_AM_I     0x6BU     //BQ2429 ID

/* I2C SLAVE 2*/
#define MAX17201_ADDRESS_LEN  1         
#define MAX17201_ADDR     (0xD8>>1) //(0xD8>>1)  
#define MAX17201_WHO_AM_I   0x6CU   

#define TWI_INSTANCE_ID     0 //snehal




/* TWI instance. */
static const nrf_drv_twi_t m_twi = NRF_DRV_TWI_INSTANCE(TWI_INSTANCE_ID);
static volatile bool m_xfer_done = false;

//Event Handler
void twi_handler(nrf_drv_twi_evt_t const * p_event, void * p_context)
{
    //Check the event to see what type of event occurred
    switch (p_event->type)
    {
        //If data transmission or receiving is finished
	case NRF_DRV_TWI_EVT_DONE:
        m_xfer_done = true;//Set the flag
        break;
        
        default:
        // do nothing
          break;
    }
}

void twi_init (void)
{
    ret_code_t err_code;

    const nrf_drv_twi_config_t twi_config = {
       .scl                = PSF_SCL_PIN,
       .sda                = PSF_SDA_PIN,
       .frequency          = NRF_DRV_TWI_FREQ_400K, 
       .interrupt_priority = APP_IRQ_PRIORITY_HIGH,
       .clear_bus_init     = false
    };

    err_code = nrf_drv_twi_init(&m_twi, &twi_config, twi_handler, NULL);
    APP_ERROR_CHECK(err_code);

    nrf_drv_twi_enable(&m_twi);
}



bool bq2429i_i2c_init(void)
{
    ret_code_t err_code;
    uint8_t address = 0x6B;  
    uint8_t sample_data = 0x00;

    err_code = nrf_drv_twi_rx(&m_twi,address,&sample_data,sizeof(sample_data));
    if(err_code == NRF_SUCCESS)
    {
       NRF_LOG_INFO("SUCCESS");
       return true;
    }
    else
    {
       NRF_LOG_INFO("FAILED");
       return false;
    }

}


bool max17211_i2c_init(void)
{
    ret_code_t err_code;
    uint8_t address = 0x6C;  
    uint8_t sample_data = 0x00;

    err_code = nrf_drv_twi_rx(&m_twi,address,&sample_data,sizeof(sample_data));
    if(err_code == NRF_SUCCESS)
    {
       NRF_LOG_INFO("SUCCESS");
       return true;
    }
    else
    {
       NRF_LOG_INFO("FAILED");
       return false;
    }

}


/*
  A Function to read data from the MPU6050
*/ 
bool i2c_register_read(uint8_t register_address, uint8_t * destination, uint8_t number_of_bytes)
{
    ret_code_t err_code;

    //Set the flag to false to show the receiving is not yet completed
    m_xfer_done = false;
    
    // Send the Register address where we want to write the data
    err_code = nrf_drv_twi_tx(&m_twi, BQ2429_ADDRESS, &register_address, 1, true);
	  
    //Wait for the transmission to get completed
    while (m_xfer_done == false){}
    //vTaskDelay(1000);

    // If transmission was not successful, exit the function with false as return value
    if (NRF_SUCCESS != err_code)
    {
        return false;
    }

    //set the flag again so that we can read data from the MPU6050's internal register
    m_xfer_done = false;
	  
    // Receive the data from the MPU6050
    err_code = nrf_drv_twi_rx(&m_twi, BQ2429_ADDRESS, destination, number_of_bytes);
		
    //wait until the transmission is completed
    while (m_xfer_done == false){}
    //vTaskDelay(1000);

	
    // if data was successfully read, return true else return false
    if (NRF_SUCCESS != err_code)
    {
        return false;
    }
    
    //NRF_LOG_INFO("DATA IS %x",destination);
    return true;
}

/*
   A function to write a Single Byte to MPU6050's internal Register
*/ 
bool i2c_register_write(uint8_t register_address, uint8_t value)
{
    ret_code_t err_code;
    uint8_t tx_buf[BQ2429_ADDRESS_LEN+1];
	
    //Write the register address and data into transmit buffer
    tx_buf[0] = register_address;
    tx_buf[1] = value;

    //Set the flag to false to show the transmission is not yet completed
    m_xfer_done = false;
    
    //Transmit the data over TWI Bus
    err_code = nrf_drv_twi_tx(&m_twi, BQ2429_ADDRESS, tx_buf, BQ2429_ADDRESS_LEN+1, false);
    
    //Wait until the transmission of the data is finished
    while (m_xfer_done == false)
    {
      }

    // if there is no error then return true else return false
    if (NRF_SUCCESS != err_code)
    {
        NRF_LOG_INFO("FAILED");
        return false;
    }

   // NRF_LOG_INFO("SUCCESS");

    return true;	
}


bool i2c_register_write_max17211(uint16_t register_address, uint16_t value)
{

      ret_code_t err_code;
      uint8_t tx_data[4];

      tx_data[0] = ( (register_address >> 8)& 0xFF );
      tx_data[1] = register_address & 0xFF;
      tx_data[2] = ((value>>8)& 0xff);
      tx_data[3] = value & 0xFF;

      m_xfer_done = false;
    
      err_code = nrf_drv_twi_tx(&m_twi, MAX17201_WHO_AM_I, tx_data, sizeof(tx_data), false);
  //Wait until the transmission of the data is finished
    while (m_xfer_done == false)
    {  }
    //vTaskDelay(1000);

   // if there is no error then return true else return false
    if (NRF_SUCCESS != err_code)
    {
        NRF_LOG_INFO("FAILED");
        return false;
    }

    NRF_LOG_INFO("SUCCESS");

    return true;	

}

bool i2c_register_read_max17211(uint8_t register_address, uint8_t destination[2], uint8_t number_of_bytes)
{
   // uint8_t address = 0x6C;  

    ret_code_t err_code;

    //Set the flag to false to show the receiving is not yet completed
    m_xfer_done = false;
    
    // Send the Register address where we want to write the data
    err_code = nrf_drv_twi_tx(&m_twi, MAX17201_WHO_AM_I, &register_address, 1, true);
	  
    //Wait for the transmission to get completed
    while (m_xfer_done == false){}

    // If transmission was not successful, exit the function with false as return value
    if (NRF_SUCCESS != err_code)
    {
        return false;
    }

    //set the flag again so that we can read data from the MPU6050's internal register
    m_xfer_done = false;
	  
    // Receive the data from the MPU6050
    //err_code = nrf_drv_twi_rx(&m_twi, MAX17211_WHO_AM_I, destination, number_of_bytes);
    err_code = nrf_drv_twi_rx(&m_twi, MAX17201_WHO_AM_I, &destination[0], sizeof(destination));
		
    //wait until the transmission is completed
    while (m_xfer_done == false){}


    // if data was successfully read, return true else return false
    if (NRF_SUCCESS != err_code)
    {
        return false;
    }
    
    //NRF_LOG_INFO("DATA IS %x",destination);
    return true;

}

With slave 1 i have no issues reading and writing the data.

What might be the issue that I am not getting m_xfer_done= true after sending data to the 2nd slave??

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Tue, 15 Mar 2022 08:56:11 GMT

Hi,

[quote user="snehal_2789"]I have modified the code a bit in order to read 2bytes from register. I am not able to read 16bit registers. I tried to read NPACKCFG_REG but not able to read it properly.[/quote]

What do you mean by not being able to read it properly? Are you getting the NRF_DRV_TWI_EVT_DONE event after you have called nrf_drv_twi_rx(), or are you getting a NRF_DRV_TWI_EVT_ADDRESS_NACK or NRF_DRV_TWI_EVT_DATA_NACK event?

[quote user="snehal_2789"]unsigned conversion from 'int' to 'uint8_t' {aka 'unsigned char'} changes value from '437' to '181' [-Woverflow][/quote]

Please show me where you are getting this warning.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Mon, 14 Mar 2022 12:40:47 GMT

Hi Vidar,

We have solved the issue with MAX17211, we tried to check the pulses but it seemed that there was some problem with the hardware. So the hardware guy has now replaced the ic from MAX17211 to MAX17201. This IC is pure I2C based and I am able to connect and read some data from the IC. When I read 8bit registers I dont have any issue. But when I am trying to read 16bit register from the IC, I am getting errors:-

I have modified the code a bit in order to read 2bytes from register. I am not able to read 16bit registers. I tried to read NPACKCFG_REG but not able to read it properly.As well as while compiling I am getting warnings like this:-

unsigned conversion from 'int' to 'uint8_t' {aka 'unsigned char'} changes value from '437' to '181' [-Woverflow]

#define NPACKCFG_REG     0x1B5



bool i2c_register_write_max17211(uint16_t register_address, uint16_t value)
{

      ret_code_t err_code;
      uint8_t tx_data[4];

      tx_data[0] = ( (register_address >> 8)& 0xFF );
      tx_data[1] = register_address & 0xFF;
      tx_data[2] = ((value>>8)& 0xff);
      tx_data[3] = value & 0xFF;

      m_xfer_done = false;
    
      err_code = nrf_drv_twi_tx(&m_twi, MAX17211_WHO_AM_I, tx_data, sizeof(tx_data), false);
  //Wait until the transmission of the data is finished
    while (m_xfer_done == false)
    {
      }

   // if there is no error then return true else return false
    if (NRF_SUCCESS != err_code)
    {
        NRF_LOG_INFO("FAILED");
        return false;
    }

    NRF_LOG_INFO("SUCCESS");

    return true;	

}

bool i2c_register_read_max17211(uint8_t register_address, uint8_t destination[2], uint8_t number_of_bytes)
{
    ret_code_t err_code;
    //uint8_t rx_buffer[2];

    //Set the flag to false to show the receiving is not yet completed
    m_xfer_done = false;
    
    // Send the Register address where we want to write the data
    err_code = nrf_drv_twi_tx(&m_twi, MAX17211_WHO_AM_I, &register_address, 1, true);
	  
    //Wait for the transmission to get completed
    while (m_xfer_done == false){}
    //vTaskDelay(1000);

    // If transmission was not successful, exit the function with false as return value
    if (NRF_SUCCESS != err_code)
    {
        return false;
    }

    //set the flag again so that we can read data from the MPU6050's internal register
    m_xfer_done = false;
	  
    // Receive the data from the MPU6050
    //err_code = nrf_drv_twi_rx(&m_twi, MAX17211_WHO_AM_I, destination, number_of_bytes);
    err_code = nrf_drv_twi_rx(&m_twi, MAX17211_WHO_AM_I, &destination[0], sizeof(destination));
		
    //wait until the transmission is completed
    while (m_xfer_done == false){}
    //vTaskDelay(1000);


    // if data was successfully read, return true else return false
    if (NRF_SUCCESS != err_code)
    {
        return false;
    }
    
    //NRF_LOG_INFO("DATA IS %x",destination);
    return true;

}

Can you please help? Also Is my code proper for writing 16bit register?

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Wed, 09 Mar 2022 07:55:06 GMT

Hi Snehal,

I guess it may be ok to share it with the i2c clock line, but this is something you need to confirm yourself. Check the datasheets and see if you can use the same pullups, etc

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Wed, 09 Mar 2022 06:32:31 GMT

Hi Vidar,

One more thing I wanted to ask is that on the same one wire line we have attached one more I2C based IC bq2429. so basically BQ2429 is I2c based and on the same line we have MAX17211 which is one wire based. So will it cause problems in getting data from the MAX17211??

The pins used for BQ2429 are as follows:-

#define PSF_SCL_PIN NRF_GPIO_PIN_MAP(1,9)
#define PSF_SDA_PIN NRF_GPIO_PIN_MAP(0,11)

The pins used for MAX17211 is as follows:-

#define PSF_SDA_PIN NRF_GPIO_PIN_MAP(0,11)

Thanks & Regards,

Snehal.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Wed, 09 Mar 2022 05:05:57 GMT

Hi Vidar,

yes you are right. we can use nrf_delay_us inside an rtos task. Thank you. I thought when rtos is used only vTaskDelay should be used for creating delays.I am going to test more with the IC max17211 today. will update you.

Regards,

Snehal

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Tue, 08 Mar 2022 13:45:25 GMT

Hi Snehal,

I don't see any problems with using nrf_delay_us() as long as you aren't using long delays.

Regards,

Vidar

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Tue, 08 Mar 2022 12:40:23 GMT

Hi Vidar,

Thanks for your reply. But we cant use nrf_delay_us() function inside an rtos task right??

Regards,

Snehal

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Tue, 08 Mar 2022 12:26:07 GMT

Hi Snehal,

You can't use vTaskDelay() for delays that are shorter than the RTOS tick interval. I think it's best to continue with busy waits using the nrf_delay_us() function as long as it provides you with sufficient accuracy. Otherwise you will have use a HW timer.

Regards,

Vidar

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Tue, 08 Mar 2022 07:49:26 GMT

Hi Vidar,

I also had one doubt. currently in my project I will be using FREERTOS. The above code which I shared uses "nrf_delay_us" to put delays after setting and clearing the pin. In FREERTOS , if I want to communicate with max17211, how can we generate delay of microseconds using vTaskDelay?

Thanks & Regards,

Snehal

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Mon, 07 Mar 2022 13:14:43 GMT

ok I will try to check and get back.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Mon, 07 Mar 2022 13:03:39 GMT

It likely means that it's not responding to your command. With a scope trace you could verify the timing and check if the sensor replies at all.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Mon, 07 Mar 2022 11:26:18 GMT

okay I removed the reset command but still when i read val1, i get 0xff. I don't think that's proper data.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Mon, 07 Mar 2022 11:19:44 GMT

The sequence looks OK, but why the reset at the end? It seems like there should only be one reset at the start according to the datasheet:

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Mon, 07 Mar 2022 11:04:34 GMT

But is my code proper?? I will do the debugging but is the reading pattern in the code ok?

Thanks & Regards,

Snehal.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Mon, 07 Mar 2022 11:03:08 GMT

I think you need a logic analyzer or oscilloscope if you don't have one already and confirm if the transaction meet the timing requirements outlined in the datasheet. It will be difficult to do much troubleshooting without it.

Regards,

Vidar

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Mon, 07 Mar 2022 10:57:26 GMT

I am not sure. I am really going in circles on how to read data from MAX17211. Can you please help me. I want to read data 0x06h REPSOC. I am using the below function but I am not able to get proper values

float max1720x_getSOC1()
{
unsigned char check;

check=max17211_reset();
if(check)
{

max17211_send_byte(0xCC); //skip rom command
max17211_send_byte(0x69); //READ command
max17211_send_byte(0x06); //SOC REGISTER
max17211_send_byte(0x00); //SOC REGISTER
max17211_reset();
//val1=max17211_read_byte();
val1=OneWire_read(); //read_byte();
}

soc = (double)val1/256;
return soc;

}

Your help will be appreciated.

Thanks & Regards,
Snehal

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Thu, 03 Feb 2022 14:25:47 GMT

Hi Snehal,

The read and write sequences seem to be well documented in the datasheet. For instance, Figure 82 on page 109 which show the communication sequences. There's also guide for the SW implementation for this sensor here: https://www.maximintegrated.com/en/design/technical-documents/userguides-and-manuals/6/6260.html

[quote user="snehal_2789"]Scratch Pad memory[/quote]

I'm not familiar with the driver, but isn't it just a buffer to hold the received data?

Regards,

Vidar

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Wed, 02 Feb 2022 10:02:16 GMT

Hi Vidar,

Thank you so much for your reply. I am trying to implement the above shared code in my project for MAX17211. I will check the timings for sure. Now I had one question. The github code shows how to read temperature from READSCRATCH method(Reading the Scratch Pad Memory). The Scratch Pad memory provides the user with all the necessary device data including temperature, TH and TL programmable thermometer settings, as well as the Count Remain and Count Per C data used in fractional temperature measurements. The CRC byte is also included in Scratch Pad memory. This was for temperature sensor. If I want to read another register from MAX17211, how to read that register?? I can't use the scratchpad method as I directly want to read the register. Will I have to use it this way??

ds18b20_send_byte(0x00A);

uint16_t data =ds18b20_read_byte();

Is this the right way to read register?

Regards,
Snehal

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Fri, 28 Jan 2022 13:54:55 GMT

Hi Snehal,

I see. At first glance it looked like all the variants had i2c support.

Timing requirements, communication sequences, etc. are documented in the datasheet (starting on page 104 - section 1-Wire Bus System (MAX17211/MAX17215 Only)), and you may have to implement this yourself. I am not aware of any third party examples for this IC.

[quote user="snehal_2789"]Also can I use this library "">github.com/.../Nordic-DS18B20" to read data from MAX17211?? will have to modify reg values?? Is it possible? [/quote]

It may serve as a starting point. You will still need to make sure the timing is correct and implement the command sequences to control the chip.

Regards,

Vidar

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

sne_333 — Thu, 27 Jan 2022 13:16:21 GMT

Hi Vidar,

Actually the IC which we are using(MAX17211) in our hardware supports only 1 wire. I asked the Maxim support team if we can communicate via I2c, so they replied that MAX17211 can be communicated using only One wire protocol. How can it be implemented in NRF52840 ??

I saw the link which you had shared so driving the bus high and low and giving the reset pulse is possible with appropriate delays. That can be done. But if I want to read any register from the MAX17211, how to do that? How to sample the bus to read the data from a particular register??

Also can I use this library "">github.com/.../Nordic-DS18B20" to read data from MAX17211?? will have to modify reg values?? Is it possible?

Regards,

Snehal.

RE: Nrf52840 one wire protocol usage with MAX17211 IC.

Vidar Berg — Thu, 27 Jan 2022 12:49:28 GMT

Hello,

Looks like this Maxim IC also supports TWI (i2c), so is there any reason for selecting 1-wire over TWI in this case? With the 1-wire interface you would have to bit bang the protocol as explained in their app note here: https://www.maximintegrated.com/en/design/technical-documents/app-notes/1/126.html

Best regards,

Vidar