Forum - Recent Threads

Support required for HMC356LP3ETR Low-Noise Amplifier

alphaise — Wed, 25 Mar 2026 07:33:21 GMT

During probing of the IC, we observed that pins 6 (GND) and 7 (ACG) are shorted together, and are also shorted to pin 15 (Vdd). However, the other GND pins (ground paddle, pins 2, 4, and 16) do not appear to be shorted together.

This issue was observed consistently in 2 units that were tested. For reference, I have attached the pinout diagram and a top-view image of the IC.

Urgent Support is required for EVAL-AD9984AEBZ

neerajrd82 — Tue, 30 Dec 2025 00:14:00 GMT

I m writing the issue observations in a clear and structured manner given below:

1. We have interconnected EVAL-AD9984AEBZ board with our test bench as given below:

2. We first switch "ON" RGsB video generator source. Then changed the settings on VESA complaint Sync on Green Analog signal with 1600x1200 pixels at 60 Hz.

3. We checked RGsB display, if this display is working correctly. We found that above shown RGsB Display was actually showing Sync on green signal. Now, we can actually change the resolution of Sync on green video signal.

4. We connected EVAL-AD9984AEBZ to CPU using USB cable provided -> this made USB PWR LED (D7) glow onboard & switch "ON" the EVAL-AD9984AEBZ board using AC to DC adapter provided with board -> this made main power LED (D6) glow on board.

5. Now, we loaded AVES Blue & selected the connection tab. Thereafter, double clicked on CY7C68013 which actually connect this board with Windows based PC.

6. We added "AD9984A-VER.1.0c.txt" script in AVES Blue which gives us the options given below:

Out of these, we have selected "162MHz 60Hz UXGA(1600x1200)". Now, this settings will load default settings for AD9984A & ADV7511 as recommended by ADI.

Now, HDMI Display connected with this evaluation board gets refresh just for second & then goes into sleep mode displaying nothing at all.

Upon loading AD9984.xml file in AVESBlue, we get these answers on loading settings from AD9984 given below:

PLL of AD9984 is getting locked can be seen in above screenshot.

Please note: Given below procedure is not written in the documentation of EVAL-AD9984AEBZ but still we have managed to monitor the functioning of ADV7511.

Upon loading ADV7511.xml file in AVESBlue, we get these answers on loading default settings from ADV7511 given below:

PLL of ADV7511 is not getting locked can be seen in above screenshot.
Since PLL of ADV7511 is not getting locked, there is no picture on HDMI output.

these are default settings given by Analog Devices:

98 00 01 ; Chip revision
98 01 87 ; PLL Div
98 02 00 ; PLL Div
98 03 F0 ; VCO range, Charge pump current
98 04 E0 ; VCO range, Charge pump current
98 05 00 ; Red Gain
98 06 80 ; Red Gain
98 07 00 ; Green Gain
98 08 80 ; Green Gain
98 09 00 ; Blue gain
98 0A 80 ; Blue gain
98 0B 00 ; Red offset
98 0C 80 ; Red offset
98 0D 00 ; Green offset
98 0E 80 ; Green offset
98 0F 00 ; Blue offset
98 10 80 ; Blue offset
98 11 20 ; Sync separator
98 12 00 ; Hsync
98 13 20 ; Hsync duration
98 14 04 ; Vsync
98 15 0A ; Vsync duration
98 16 04 ; precoset
98 17 04 ; postcoast
98 18 00 ; clamping
98 19 08 ; clamp placement
98 1A 14 ; clamp duration
98 1B 33 ; clamp polarity
98 1C FF ; ADI recommended write
98 1D 78 ; sync on green
98 1E 34 ; Input channel select
98 1F 93 ; Output video mode
98 20 07 ; Output impedance
98 21 20 ; ADI recommended write
98 22 32 ; ADI recommended write
98 23 14 ; sync filter window width
98 24 A8 ; sync detect
98 25 FD ; sync polarity
98 26 4E ; Hsync per vsync
98 27 20 ; Hsync per vsync
98 28 8F ; ADI recommended write
98 29 02 ; ADI recommended write
98 2A 00 ; ADI recommended write
98 2B 00 ; ADI recommended write
98 2C 00 ; ADI recommended write
98 2D 08 ; ADI recommended write
98 2E 20 ; ADI recommended write
98 3C 0E ; Auto gain
72 01 00 ; Set 'N' value at 6144
72 02 18 ; Set 'N' value at 6144
72 03 00 ; Set 'N' value at 6144
72 15 00 ; 24-bit, 444 RGB input
72 16 50 ; RGB
72 18 08 ; Disable CSC
72 17 01 ; Enable DE Generation
72 35 7B ; DE Generation
72 36 F0 ; DE Generation
72 37 0C ; DE Generation
72 38 80 ; DE Generation
72 39 4B ; DE Generation
72 3A 00 ; DE Generation
72 3B 40 ; Set Pixel Repetition
72 3C 00 ; Set VIC
72 40 80 ; General control packet enable
72 41 10 ; Power down control
72 49 A8 ; Set dither mode - 12-to-10 bit
72 4C 05 ; Set 10 bit output
72 96 20 ; HPD interrupt clear
72 55 00 ; Set to RGB
72 56 08 ; Set active format aspect
72 98 03 ; ADI recommended write
72 99 02 ; ADI recommended write - lock count limit
72 9C 30 ; PLL filter R1 value
72 9D 61 ; Set clock divide
72 A2 A4 ; ADI recommended write
72 A3 A4 ; ADI recommended write
72 AF 16 ; Select HDMI mode
72 BA A0 ; Set TX Clock Delay
72 DE 9C ; ADI recommended write
72 E4 60 ; VCO_Swing_Reference_Voltage
72 FA 7D ; Nbr of times to look for good phase
72 48 00 ; Evenly distrubuted output
72 55 10 ; RGB out
72 56 00 ; Set AVI
72 57 00 ; Adobe RGB

While debugging the reasons of misbehaviour of this board, we found that HSOUT,VSOUT & DATACK output from AD9984a was not compliant as per standard VESA timing for 1600x1200 pixel at 60 Hz sync on green with help of good quality 350MHz oscilloscope. These 3 signals were not stable, there was jitter in all 3 signals.

So, we decided to stabilized the waveform by changing the settings of following registers:

CHIP REGISTER SETTINGS

AD9984A 0x12 0x48

AD9984A 0x13 0xC0

AD9984A 0x14 0x0C

AD9984A 0x1D 0xB8

AD9984A 0x34 0xB4

ADV7511 0x41 0x00

These settings stabilized all 3 signals as per VESA timing standards for 1600x1200 pixel at 60Hz SoG.

We were able to secure the PLL lock of ADV7511 as result of above settings as per screenshot given below:

but still there was no picture output on HDMI Display shown above.

Now, I sincerely think that all of whom are accessing this, should be able to understand the how we are able reproduce the failure of this board.

if experts are able to understand this procedure ?

Kindly! help on urgent basis as this is critical problem. Since i m not getting any support.

THANKS WITH REGARDS

NEERAJ GUPTA

Cannot maintain a constant PWM - only get about 10 cycles out of my DS1050-025

dfansler — Fri, 01 Aug 2025 18:29:41 GMT

Hi Andy -

I had my DS1050-025 running, for a while, but now I can only get about 3 to 10 cycles out it. I have gone back over changes I have made, but nothing seems to help. Here is the test code I am currently trying. I open the DS1050 i2c, using address 0x28 ( as shown by i2cdetect on my Raspberry Pi, which this hardware is on). Then I write 0x50 (set PMW command) followed by the data (shown as 0x10h - which should be 50% PWM).

I close the file descriptor, call the second function, where I open the DS1050 in i2c again, writing 0x50 (set PWM command) followed by the data 0x20 as shown on the DS1050 data sheet. Then again close the file descriptor. I have tried combining the two functions and write 0x50, 0x10, 0x50, 0x20 and the close i2c with the same results.

#include <stdio.h>
#include <stdlib.h>
#include <math.h>
#include "/home/dvf/glg/include/GlgApi.h"
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>    // read/write usleep     
#include <inttypes.h>  // uint8_t, etc
#include <linux/i2c-dev.h> // I2C bus definitions
#include <sys/ioctl.h>			//Needed for I2C port
#include "/home/dvf/glg/include/GlgApi.h"
#include <sys/socket.h>
#include <netinet/in.h>
#include <string.h>
#include <arpa/inet.h>


#include <termios.h>

#include <stdio.h>
#include <sys/types.h> // open
#include <sys/stat.h>  // open
#include <fcntl.h>     // open
#include <unistd.h>    // read/write usleep
#include <stdlib.h>    // exit
#include <inttypes.h>  // uint8_t, etc
#include <linux/i2c-dev.h> // I2C bus definitions
#include <sys/ioctl.h>
#include "PWM.h"
int PWM_Write2(void);
int fd_pwm, fd;
   int16_t val;
   uint8_t writeBuf[5], readBuf[2];

void main(void)
{
   

   // open device on /dev/i2c-1 
   if ((fd_pwm = open("/dev/i2c-1", O_RDWR)) < 0) 
   {
      printf("Error: Couldn't open I2C device\n");
      return;
   }

   // connect to ads1115 as i2c slave
   if (ioctl(fd_pwm, I2C_SLAVE, PWM_Addrs) < 0)
    {
      printf("Error: Couldn't find device on address!\n");
      return;
   }
   // set config register and start conversion

   writeBuf[0] = SetPWM;    // config register is 1
   writeBuf[1] = 0x10;
  // Set newm PWM duty
   if (write(fd_pwm, writeBuf, 4) != 4) 
   {
       printf("Can't write to register 1\n");
       return;
   }

   close(fd_pwm);

   PWM_Write2();
   while(1)
{
   ;
}

}

int PWM_Write2(void)
{
   // open device on /dev/i2c-1 
   if ((fd = open("/dev/i2c-1", O_RDWR)) < 0) {
      printf("Error: Couldn't open I2C device\n");
      return 1;
   }
printf("fd = %d\n",fd);
   // connect to ads1115 as i2c slave
   if (ioctl(fd, I2C_SLAVE, PWM_Addrs) < 0) {
      printf("Error: Couldn't find device on address!\n");
      return 1;
   }
// set config register and start conversion

   writeBuf[0] = SetPWM;    // config register is 1
   writeBuf[1] = 0x20;
   // Set newm PWM duty
   if (write(fd, writeBuf, 2) != 2) 
   {
       printf("Can't write to register 1\n");
       return 1;
   }

	close(fd);
}

Hope you can help,

David
YouTube "Sailing Solo at 70"

Maxim Integrated MAX17703 Dev Kit Power On Issue

hamza nasir — Wed, 03 Jul 2024 15:22:16 GMT

I have purchased the Maxim Integrated Analog Devices development kit MAX17703. Here is the link to the datasheet: MAX17703EVKITA Datasheet. The kit is designed for 4.2V, but I have changed the kit's output voltage to suit my application. I want to charge multi-cell lithium-ion batteries with two batteries in series. I am using Panasonic NRC 3400mAh 3.7V green batteries (NRC18650B). The kit's datasheet states that the input voltage range is 6.3V to 60V.

In my case, I changed the VOUT to 8.4V by adjusting RTOP and RBOT, choosing 42.2kΩ for RTOP and 7.32kΩ for RBOT. I also changed the battery deep discharge level to 6V by adjusting R4 in the dev kit to 22kΩ. The charger seems to work fine and charges the batteries, but I am encountering a problem: when the input voltage DCIN to the kit is less than or qual to 12.5v and the battery voltage is around 6.5 to 7V or less, the charger will not start until I provide 13.8V or 14V. When I apply a DCIN input greater than 13.5V, the charging kit turns on and starts charging.

If the charging kit's minimum DC input voltage is 6.3V, why does the charger kit not start at 10V or 11V? Additionally, sometimes the charging kit does not stop charging, and the batteries overheat. I simply connect the batteries at the VOUT pin with two batteries in series. Please help me resolve this issue as soon as possible.

MAX17263 SOC Changing on Power Cycle

nolannirsense — Fri, 03 May 2024 04:46:11 GMT

Hello,

I've been working with the MAX17263 battery gauge recently via the MAX17263 EVKIT, and I'm connecting to it and reading the SPI outputs via an NRF5340 dev kit. I also have the MAX17263 EVKIT connected to a battery and a charger. I have the device set to print out the state of charge by reading the RepSOC register and dividing it by 256. My device polls the SOC every two seconds. When I first turn the device on, it gives me an initial SOC reading, let's say 55%. After a few minutes of charging, it'll go up to 57%. If I then power cycle the device, the percentage I will see is often a few percent higher after the first power cycle, so maybe 61%. Then, if I power cycle it again, the SOC returns to 57%, or sometimes even lower than the initial value, such as 56%.

I notice this inaccuracy trend when reading the RepCap register as well. My battery has a total capacity of 250 mAh, so the DesignCap register is set to 500. After charging for a while, the capacity will be around 324 before power cycling, 337 after power cycling once, and 323 after power cycling a second time. This pattern is pretty consistent, and I've checked a lot of settings and different registers, but I'm not sure how the RepCap and RepSOC registers are calculated. What could be causing these variations? My device needs to be accurate within one percent, and I was using the RepCap to give a more detailed view of the battery state.

What controls the RepCap and RepSOC registers within the MAX17263, and what could be causing this inaccuracy?

Thanks!

PROBLEM whith MAX17632C

Fabrizio70 — Fri, 23 Feb 2024 15:50:21 GMT

Hi , I have a problem whith max17632c i use it for dc/dc 24v/5v .if i put i small load ( 100mW) the output voltage is 4,0V , while i put a load of 2W tthe output voltage go to 2,5V.

then i desolder the condensator C1 (2,2 uF 10V ceramic used for bypass ldo pin 2) and i have 5v output whit load of 2W (the condensator not have problem) , Where is the prblem?

MAX17320G20+T 2 cell series 18650 LiPo battery balancing issue

ninjax8 — Mon, 16 Oct 2023 04:34:46 GMT

Hello,

We are currently working on MAX17320G20+T based circuit for cell protection and fuel gauge of a 2 cell series LiPo battery. I've made a arduino library to read/write registers via I2C and able to get the fuel gauge registers working (BATT, PKP, VCELL, CELL1, CELL2 etc.).

But now I'm trying to implement the battery balancing function of the IC. The cell balancing is not happening.

We are enabling the zener for cell balancing with 80mV difference but the higher voltage cell is not going down. We have connected a small load too (LED) at the circuit output. Both cells are draining in the proportional way.

Cell 1 voltage = 3.5V

Cell 2 voltage = 3.9V

So ideally Cell 2 voltage should be 3.58 to 3.6V via the zener drop if the balancing is happening.

But nothing is happening.

Schematic and test code is attached

#include <Wire.h>
#include "MAX17320.h"

//uint8_t r_sense = 1;
void setup() {
  Wire.begin(DEVICE_ADDRESS);
  Wire.begin(NVM_ADDRESS);
  Serial.begin(9600);
}

void loop() {
  //  read_cell1();
  delay(1000);
  //  Serial.println(MAX17320::read_cell1());
  MAX17320::set_cell_balancing(ZenerEnable, mV800, 11.7, 100);
}

Function call

void set_cell_balancing(BatteryBalancingZener zener_enable, CellBalancingConfig bal_cfg, float r_mismatch, uint8_t imbalance)
  {
    r_mismatch = 32 * r_mismatch / 125;
    uint16_t RMismatch = round(r_mismatch) << 5;
    imbalance = round(imbalance / 10);
    if (imbalance <= 31 && r_mismatch <= 31)
    {
      uint16_t code = zener_enable | static_cast<uint16_t>(bal_cfg) | static_cast<uint16_t>(RMismatch) | static_cast<uint16_t>(imbalance);
      unlock_write_protection();
      write_named_register_nvm(RegisterNvm::NBalTh, code);
      lock_write_protection();
    }
  }

Cell balancing function

enum BatteryBalancingZener
{
  ZenerDisable = 0,
  ZenerEnable = 1 << 13,
};

enum CellBalancingConfig
{
  Disable = 0,
  /// For 2.5mV
  mV25 = 1 << 10,
  /// For 5mV
  mV50 = 2 << 10,
  /// For 10mV
  mV100 = 3 << 10,
  /// For 20mV
  mV200 = 4 << 10,
  /// For 40mV
  mV400 = 5 << 10,
  /// For 80mV
  mV800 = 6 << 10,
  /// For 160mV
  mV1600 = 7 << 10,
};

config file

Ref : Datashet : https://www.analog.com/media/en/technical-documentation/data-sheets/MAX17320.pdf (Page 70, Battery Balancing section)

Pls suggest a solution for this. And let us know if you need more information on the test results.

Best regards

Porting six cameras on Qualcomm QCS610 using MAX 9296A Deserializer

Hari_123 — Fri, 15 Sep 2023 12:24:13 GMT

Hi Andy Waller

I am Engaged in porting six cameras using three MAX 9296A Deserializer on Qualcomm QCS610. I need your advice, what are sequence of operations need to perform in 9296A driver development and standard properties involve in device tree modification.

824 bytes of calibration vector obtained in calibration procedure of max32664D with max30101

md_adhil — Mon, 31 Jul 2023 09:44:14 GMT

Hi,

After the calibration procedure in BPT algorithm (MAX 32664D), we will get 824 bytes of calibration vector. What does each byte in that vector means?

And what is the reason for getting 255 as the value of byte in calibration vector.

And also, in calibration vector array after 56th byte, i am getting 255 from 57th byte to 824th byte. By default (before calibration), it should be zero and after calibration also I am getting 255. Please help with it.

Queries during calibration procedure for MAX32664D with sensor MAX 30101

md_adhil — Mon, 17 Jul 2023 05:30:53 GMT

Hi,

This queries has been raised when performing calibration procedure of BPT algorithm,

1. What is the reading samples procedure in calibration of BPT algorithm does?

2. Where does the given calibration values get stored either in host or MAX32664 registers?

2. Is it possible to read the written calibration values (written during calibration procedure of BPT algorithm using MAX32664D), as per I2C read dataframe shown in user guide datasheet of MAX32664D.

3. After calibration start procedure, there is a statement, "Wait for 100ms before sending the next command. Any command to change sensor registers should appear AFTER enabling algorithm or they will be overwritten." which was mentioned after the start calibration procedure and before reading samples procedure. So there should be delay after each commands in reading sample procedure?

4.On giving delays between each commands of reading samples, we are getting different values in FIFO (number of samples). why?

MAX32664D doesn't work

AliMozaffari — Tue, 22 Nov 2022 08:58:33 GMT

I'm trying to build an spo2 measurement with MAX30102 and MAX32664D. I'm sending my commands from TI CC2640R2F using I2C 400KHz mode. I made a library for MAX32664D and tried to send commands below and I explained the results that I got by running these commands:

1 MAX32664_EnterBootLoaderMode();
2 MAX32664_ReadDeviceMode();
3 MAX32664_ReadMCUType();
4 MAX32664_ReadBootloaderVersion();
5 MAX32664_ReadBootloaderPageSize();
6 MAX32664_EnterAppMode();
7 MAX32664_ReadDeviceMode();
8 MAX32664_BPTalgorithmMode(0x02);
9 MAX32664_SetOutputMode(0x01);
10 MAX32664_SetFifoInterruptThreshold(0x04);
11 MAX32664_SensorEnable(true);
12 MAX32664_ReadSensorMode();
13 MAX32664_ReadSensorHubVersion();
14 MAX32664_GetNumOfSamplesInFifo();
15 receivedData = MAX32664_GetFifoData();
16 MAX32664_ReadSensorFifoLength();
17 MAX32664_ReadNumOfSamplesInSensorFifo();

line 1&2: device goes into boot loader mode successfully
line 3 : command works and indicates that MCU is MAX32664 or MAX32660
line 4 : command doesn't work and returns 0xFE that is ERR_TRY_AGAIN but trying agail also doesn't work - boot loader version is not sent to host by MAX32664D
line 5 : command doesn't work and returns 0xFE that is ERR_TRY_AGAIN but trying agail also doesn't work - boot loader pagesize which must be 8192 is not sent to host by MAX32664D
line 6&7: device goes into application mode successfully
line 8 : command doesn't work and returns 0xFE that is ERR_TRY_AGAIN but trying agail also doesn't work - unable to select estimation mode for BPT algorithm
line 9 : command worked and sensor data is selected as MAX32664D output
line 10 : command worked and interrrupt threshold is set to 0x04
line 11: command doesn't work and returns 0xFE that is ERR_TRY_AGAIN but trying agail also doesn't work - the MAX30102 deosn't get enabled
line 12: command works and indicates that MAX30102 is disable
line 13: command works and indicates that msbl file version is 40.2.2
line 14: command works and indicates that there is 0 samples in output fifo
line 15: command works and recieved data is LED1 = 0x202 , LED2 = 0x440109 ,LED3 = 0x70000 and other data are all zero.
line16: command works and indicates that input fifo length is 160
line17: command works and indicates that there is 160 samples in input fifo
why some of command do not work? is any thing I can do? is it a physical issue or corrupted msbl file? what should I do to be able to read data?
below is my library codes for each command:

bool MAX32664_EnterBootLoaderMode(void){
bool successful;
uint8_t TxBuffer[3];
uint8_t RxBuffer[1];
TxBuffer[0] = 0x01;//Family byte
TxBuffer[1] = 0x00;//Index byte
TxBuffer[2] = 0x08;//Enter boot loader mode
RxBuffer[0] = 0xFF;//Initialization
I2C_Send(TxBuffer, 3, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 1, MAX32664_ADDR);
successful = (RxBuffer[0] == 0x00)? true:false;
#ifdef DEBUG_PRINTS
System_printf(successful ? "BootLoader Mode Enabled\n" : "BootLoader Mode Failed\n");
System_flush();
#endif
return successful;
}

uint8_t MAX32664_ReadDeviceMode(void){
uint8_t TxBuffer[2];
uint8_t RxBuffer[2];
TxBuffer[0] = 0x02;//Family byte
TxBuffer[1] = 0x00;//Index byte
RxBuffer[0] = 0xff;//Reset
RxBuffer[1] = 0xff;//Initialization
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 2, MAX32664_ADDR);
#ifdef DEBUG_PRINTS
switch(RxBuffer[1]){
case 0x00:
System_printf("Device is in application mode\n");
break;
case 0x02:
System_printf("Device is reset\n");
break;
case 0x08:
System_printf("Device is in bot loader mode\n");
break;
default:
System_printf("Invalid data received\n");
}
System_flush();
#endif
return RxBuffer[1];
}

void MAX32664_ReadMCUType(void){
uint8_t TxBuffer[2];
uint8_t RxBuffer[2] = {0xff,0xff};
TxBuffer[0] = 0xFF;//Family byte
TxBuffer[1] = 0x00;//Index byte
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 2, MAX32664_ADDR);
#ifdef DEBUG_PRINTS
switch(RxBuffer[1]){
case 0x00:
System_printf("MCU is MAX32625\n");
break;
case 0x01:
System_printf("MCU is MAX32664 or MAX32660\n");
break;
default :
System_printf("Unknown MCU\n");
}
System_flush();
#endif
}

void MAX32664_ReadBootloaderVersion(void){
uint8_t TxBuffer[2];
uint8_t RxBuffer[4] = {0xff,0xff,0xff,0xff};
TxBuffer[0] = 0x81;//Family byte
TxBuffer[1] = 0x00;//Index byte
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 4, MAX32664_ADDR);
#ifdef DEBUG_PRINTS
System_printf("Bootloader firmware version is %d.%d.%d \n",RxBuffer[1],RxBuffer[2],RxBuffer[3]);
System_flush();
#endif
}

uint16_t MAX32664_ReadBootloaderPageSize(void){
uint16_t pageSize;
uint8_t TxBuffer[2];
uint8_t RxBuffer[3] = {0xff,0xff,0xff};
TxBuffer[0] = 0x81;//Family byte
TxBuffer[1] = 0x01;//Index byte
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 3, MAX32664_ADDR);
pageSize = (RxBuffer[1]<<8) + RxBuffer[2];
#ifdef DEBUG_PRINTS
System_printf("page size is %d\n",pageSize);
System_flush();
#endif
return pageSize;
}

bool MAX32664_EnterAppMode(void){
bool successful;
uint8_t TxBuffer[3];
uint8_t RxBuffer[1];
TxBuffer[0] = 0x01;//Family byte
TxBuffer[1] = 0x00;//Index byte
TxBuffer[2] = 0x00;//Exit boot loader mode,Enter application mode
RxBuffer[0] = 0xFF;//Initialization
I2C_Send(TxBuffer, 3, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 1, MAX32664_ADDR);
successful = (RxBuffer[0] == 0x00)? true:false;
#ifdef DEBUG_PRINTS
System_printf(successful ? "Application Mode Enabled\n" : "Application Mode Failed\n");
System_flush();
#endif
return successful;
}

bool MAX32664_BPTalgorithmMode(uint8_t modeByte){
bool successful;
uint8_t TxBuffer[3];
uint8_t RxBuffer[1];
TxBuffer[0] = 0x52;//Family byte
TxBuffer[1] = 0x04;//Index byte
TxBuffer[2] = modeByte;
RxBuffer[0] = 0xff;//Initialization
I2C_Send(TxBuffer, 3, MAX32664_ADDR);
Task_sleep(DURATION_MS(20));//command delay
I2C_Receive(RxBuffer, 1, MAX32664_ADDR);
successful = (RxBuffer[0] == 0x00)? true:false;
return successful;
}

bool MAX32664_SetOutputMode(uint8_t formatByte){
bool successful;
uint8_t TxBuffer[3];
uint8_t RxBuffer[1];
TxBuffer[0] = 0x10;//Family byte
TxBuffer[1] = 0x00;//Index byte
TxBuffer[2] = formatByte;
RxBuffer[0] = 0xff;//Initialization
I2C_Send(TxBuffer, 3, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 1, MAX32664_ADDR);
successful = (RxBuffer[0] == 0x00)? true:false;
return successful;
}

bool MAX32664_SetFifoInterruptThreshold(uint8_t thrByte){
bool successful;
uint8_t TxBuffer[3];
uint8_t RxBuffer[1];
TxBuffer[0] = 0x10;//Family byte
TxBuffer[1] = 0x01;//Index byte
TxBuffer[2] = thrByte;
RxBuffer[0] = 0xff;//Initialization
I2C_Send(TxBuffer, 3, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 1, MAX32664_ADDR);
successful = (RxBuffer[0] == 0x00)? true:false;
return successful;
}

bool MAX32664_SensorEnable(bool enable){
bool successful;
uint8_t TxBuffer[3];
uint8_t RxBuffer[1];
TxBuffer[0] = 0x44;//Family byte
TxBuffer[1] = 0x03;//Index byte
TxBuffer[2] = (enable)? 0x01:0x00;
RxBuffer[0] = 0xff;//Initialization
I2C_Send(TxBuffer, 3, MAX32664_ADDR);
Task_sleep(DURATION_MS(40));//command delay
I2C_Receive(RxBuffer, 1, MAX32664_ADDR);
successful = (RxBuffer[0] == 0x00)? true:false;
return successful;
}

uint8_t MAX32664_ReadSensorMode(void){
uint8_t TxBuffer[2];
uint8_t RxBuffer[2];
TxBuffer[0] = 0x45;//Family byte
TxBuffer[1] = 0x03;//Index byte
RxBuffer[0] = 0xff;//Initialization
RxBuffer[1] = 0xff;//Initialization
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 2, MAX32664_ADDR);
#ifdef DEBUG_PRINTS
switch(RxBuffer[1]){
case 0x00:
System_printf("MAX30101/2 is disabled\n");
break;
case 0x01:
System_printf("MAX30101/2 is enabled\n");
break;
}
System_flush();
#endif
return RxBuffer[1];
}

void MAX32664_ReadSensorHubVersion(void){
uint8_t TxBuffer[2];
uint8_t RxBuffer[4];
TxBuffer[0] = 0xff;//Family byte
TxBuffer[1] = 0x03;//Index byte
RxBuffer[0] = 0xff;//Initialization
RxBuffer[1] = 0xff;//Initialization Major version byte
RxBuffer[2] = 0xff;//Initialization Minor version byte
RxBuffer[3] = 0xff;//Initialization Revision byte
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 4, MAX32664_ADDR);
#ifdef DEBUG_PRINTS
System_printf("SensorHub Version is %d.%d.%d \n",RxBuffer[1],RxBuffer[2],RxBuffer[3]);
System_flush();
#endif
}

uint8_t MAX32664_GetNumOfSamplesInFifo(void){
uint8_t TxBuffer[2];
uint8_t RxBuffer[2];
TxBuffer[0] = 0x12;//Family byte
TxBuffer[1] = 0x00;//Index byte
RxBuffer[0] = 0xff;//Index byte
RxBuffer[1] = 0xff;//Index byte
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
return RxBuffer[1];
}

fifoData MAX32664_GetFifoData(void){
fifoData receivedData;
uint8_t TxBuffer[2];
uint8_t RxBuffer[20]={0};
TxBuffer[0] = 0x12;//Family byte
TxBuffer[1] = 0x01;//Index byte
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 20, MAX32664_ADDR);
receivedData = MAX32664_RawDataToFifoData(RxBuffer);
Task_sleep(DURATION_MS(45));//command delay
return receivedData;
}

fifoData MAX32664_RawDataToFifoData(uint8_t *RxBuffer){
fifoData receivedData;
receivedData.err = RxBuffer[0];
receivedData.led_1 = (RxBuffer[1]<<16) + (RxBuffer[2]<<8) + RxBuffer[3];
receivedData.led_2 = (RxBuffer[4]<<16) + (RxBuffer[5]<<8) + RxBuffer[6];
receivedData.led_3 = (RxBuffer[7]<<16) + (RxBuffer[8]<<8) + RxBuffer[9];
receivedData.led_4 = (RxBuffer[10]<<16) + (RxBuffer[11]<<8) + RxBuffer[12];
receivedData.status = RxBuffer[13];
receivedData.progress = RxBuffer[14];
receivedData.hr = RxBuffer[15];
receivedData.sys = RxBuffer[16];
receivedData.dia = RxBuffer[17];
receivedData.spo2 = RxBuffer[18];
receivedData.r = RxBuffer[19];
receivedData.hrAboveResting = RxBuffer[20];
return receivedData;
}

uint16_t MAX32664_ReadSensorFifoLength(void){
uint16_t fifoLength;
uint8_t TxBuffer[2] ;
uint8_t RxBuffer[3] = {0xff};
TxBuffer[0] = 0x13;
TxBuffer[1] = 0x01;
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 3, MAX32664_ADDR);
fifoLength = (RxBuffer[1]<<8) + RxBuffer[2];
#ifdef DEBUG_PRINTS
System_printf("fifo length is %d\n",fifoLength);
System_flush();
#endif
return fifoLength;
}

uint16_t MAX32664_ReadNumOfSamplesInSensorFifo(void){
uint16_t numOfSamples;
uint8_t TxBuffer[2] ;
uint8_t RxBuffer[3] = {0xff};
TxBuffer[0] = 0x13;
TxBuffer[1] = 0x01;
I2C_Send(TxBuffer, 2, MAX32664_ADDR);
Task_sleep(DURATION_MS(2));//command delay
I2C_Receive(RxBuffer, 3, MAX32664_ADDR);
numOfSamples = (RxBuffer[1]<<8) + RxBuffer[2];
#ifdef DEBUG_PRINTS
System_printf("number of samples currently in the sensor FIFO is %d\n",numOfSamples);
System_flush();
#endif
return numOfSamples;
}

MAX 30105 programing

Rafai — Sat, 08 Oct 2022 23:34:10 GMT

I'm trying to program my MAX 30105 sensor to work with 15 BITS and increase it's sample rate using this library (www.arduino.cc/.../), and it this dosn't work for us. I'm programming the sensor to work at 1.000 Hz, but it works at 30 Hz. ¿Could you help me to solve this problem or tell me where can I find the solution?

GY-MAX30100 SENSORS with NodeMcu reading gets is zero when connect to thingspeak/ubidots but get readings when using webservers?

CHOWS — Mon, 18 Apr 2022 03:00:07 GMT

GY-MAX30100 SENSORS with NodeMcu reading gets is zero when connect to thingspeak/ubidots but get readings when using webservers?this images shows the values at 5:14 in https://www.youtube.com/watch?v=65ZKoxykhqs which i get totally same as the figure shown on serial monitor using same coding but after 5.37 in the youtube as shown figure ,the author get the reading from MAX30100, in detailed i use GY-MAX30100 which no need to troubleshoot as before.How can i get the values as the author

Why Is Analog Design Harder Than Digital Design?

rscasny — Thu, 27 Feb 2020 23:21:13 GMT

Are you an analog design engineer or digital? By most standards, the marketplace is producing more digital design engineers than analog. Ask most engineers and they would tell you why: analog design is harder than digital, and requires more knowledge and more factors to consider such as a deep understanding of efficient power, precision measurement, wireless connectivity, and reliable circuit protection. What do you think?

Let's talk about that a bit more. Is analog design just a matter of knowledge, or is there something more involved? It likely boils down to that fact that analog design involves more than just analog. It's influenced by circuit theory, signal processing, control systems, and device physics, and more. When you consider that circuits and components are more integrated and operated at ultra low power, one needs to consider both pow power, low noise, and stability over the required temperature range.

What's analog design require? Efficient power ICs to extend the lifetime and reduce heat dissipation for your design. Precision measurement ICs to feature high accuracy and high performance for across-the-board precision analog applications. Rugged connectivity to offer the industry’s highest level of protection for connectivity in hazardous environments. Reliable protection ICs to protect systems from faults by maintaining and monitoring proper voltage, current, and temperature levels.

For sure, analog design has always been more complicated than digital design. While both require the engineer to make design compromises, analog beats digital design in the arena of complexity. All the variables involved just make it nothing but hard.

I've told you what I think. How about you?

Why do you think analog design is more difficult than digital design? If you have an example, share it with the element14 community?

[Please visit the site to access the poll]

What's So Special About 1-Wire Bus Technology?

rscasny — Tue, 14 Mar 2017 13:48:41 GMT

Let's start with a basic question: What is 1-Wire Bus Technology?

The basis of 1-Wire® technology is a serial protocol using a single data line plus ground reference for communication. A 1-Wire® master initiates and controls the communication with one or more 1-Wire slave devices on the 1-Wire bus (Figure 1). Each 1-Wire slave device has a unique, unalterable, factory-programmed, 64-bit ID (identification number), which serves as device address on the 1-Wire bus. The 8-bit family code, a subset of the 64-bit ID, identifies the device type and functionality.

What's So Special About 1-Wire Bus Technology?

1-Wire is the only voltage-based digital system that works with two contacts, data and ground, for half-duplex bidirectional communication. In contrast to other serial communication systems such as I²C or SPI, 1-Wire devices are designed for use in a contact environment. Either disconnecting from the 1-Wire bus or a loss of contact puts the 1-Wire slaves into a defined reset state. When the voltage returns, the slaves wake up and signal their presence. With only one contact to protect, the built-in ESD protection of 1-Wire devices is extremely high. With two contacts, 1-Wire devices are the most economical way to add electronic functionality to nonelectronic objects for identification, authentication, and delivery of calibration data or manufacturing information.

Sound Interesting? Ready to learn more? then put March 21st on your calendar to attend a webinar by Maxim Integrated and Panasonic entitled A Deep Dive on the Maxim 1-Wire® Bus with Panasonic Grid-EYE® Sensor and Arduino-Compatible Building Automation Platform

Apply Now to RoadTest MAXREFDES143#: DeepCover Embedded Security in IoT

rscasny — Fri, 02 Dec 2016 17:50:22 GMT

Addressing the many issues related to system-security in Industrial Internet of Things (IIoT) installations, the MAXREFDES143# embedded security reference design from Maxim Integrated Products, Inc. provides protection against counterfeit sensor data, guaranteeing its authenticity and integrity along the entire data chain, from the transducer to the cloud.

The MAXREFDES143# is an Internet of Things (IoT) embedded security reference design, built to protect an industrial sensing node by means of authentication and notification to a web server. The hardware includes a peripheral module representing a protected sensor node monitoring operating temperature and remaining life of a filter (simulated through ambient light sensing) and an mbed shield representing a controller node responsible for monitoring one or more sensor nodes.

The design is hierarchical with each controller node communicating data from connected sensor nodes to a web server that maintains a centralized log and dispatches notifications as necessary. The mbed shield contains a Wi-Fi module, a DS2465 coprocessor with 1-Wire^® master function, an LCD, LEDs, and pushbuttons. The protected sensor node contains a DS28E15 authenticator, a DS7505 temperature sensor, and a MAX44009 light sensor. The mbed shield communicates to a web server by the onboard Wi-Fi module and to the protected sensor node with I²C and 1-Wire.

The MAXREFDES143# is equipped with a standard shield connector for immediate testing using an mbed board such as the MAX32600MBED#. The simplicity of this design enables rapid integration into any star-topology IoT network requiring the heightened security with low overhead provided by the SHA-256 symmetric-key algorithm.

Apply to RoadTest the MAXREFDES143#

how to compute heart rate and SPO2 from MAX30100

lavr2016 — Mon, 23 May 2016 14:46:01 GMT

Hello, everybody. I work with Pulse Oximeter and Heart-Rate Sensor MAX30100 from Maxim Intergarted. I get raw data from sensor, but don't find an algorithm, how to compute heart rate and SPO2 level. Can anybody help me? I will be grateful for C code.

I am trying to measure fuel gauge data

e14 Contributor — Wed, 28 May 2014 10:07:52 GMT

I am trying to calibrate fuel gauge IC Max17040 . According to datasheet we have RCOMP register (address = 0x0C-0x0D) in max17040 that is a r/w register, during testing using I2C I tried to write data to that register and then read the same, but all the time I am reading the default values 9700 . I am unable to write any value in this register.

I want to clarify if this register is really a r/w register or there is any mismatch in datasheet and chip.

Regards

Mrigendra

MAX3232CPE+

e14 Contributor — Sun, 12 Sep 2010 15:13:04 GMT

Hello Andi,

I would like to replace an existing scheme a MAX3232CPE+ by a SOIC model (to save space), can you tell me the model most appropriate?

Thank you

denis

LiFePO4 charger from USB

e14 Contributor — Mon, 31 May 2010 13:00:09 GMT

Hi,

I’m searching a charger component for battery pack of 2 cell LiFePO4 (7,2 or 7,4V) that can use USB supply (integer a step up regulator), or a step up regulator able to start in short circuit.

Thanks

Best regards.

Have a technical question for Maxim? Ask an Expert!

nlarson — Fri, 30 Oct 2009 19:24:35 GMT

If you need help on anything technical relating to Maxim products, please post your question here!

Don't forget to sign up for email notifications under the "Actions" box so you'll see when Andy answers your question.

Andy Waller

Andy is an Applications Engineer with Maxim Integrated Products. He specializes in technical support for Maxim's product range for the entire life cycle of a product - from design to field..

If not already, you'll need to

to ask your question.

Otherwise, click reply below.