Q&A - Recent Threads

Invalid Frequency Error at ADICUP Power Detector App (AD8302) for ADICUP3029

JBALL38 — Thu, 05 Feb 2026 14:39:51 GMT

Hello ,

I buy EVAL-AD8302-ardz and EVAL-ADICUP3029 to follow this wiki: https://wiki.analog.com/resources/eval/user-guides/eval-ad8302-ardz

So I install drivers, I connect the two board together, I lauch the application, I found the good port COM and I connect with succes because I can go to Measurement page, but when I try to click on Measure button (skip Calibration and use Default Calibration Coefficients)

The message display is an error on Frequency and don"t display result...

I try to go to calibrate page @ frequency 0.1GHZ the values appears and I try again a measure but same résult...

When I change my RF signal I measure differents voltage on TP1 and TP2 336mv to 1V8.

TP3 is 5V

TP5 is 1V86

TP6 is GND ref 0V

can you help me to have a good measurement ?

best regard.

Using boundary scan with the MAX78000

SilentBob — Tue, 06 Jan 2026 09:32:26 GMT

I am looking at incorporating the MAX78000 AI processor into a new design and intend on using boundary scan for testing in both a development and production environment. Is it possible to access boundary scan registers in this device? If so, how?

I2C stray repeated read

PFrank — Wed, 10 Dec 2025 03:11:44 GMT

Datasheet shows the following sequence for a single byte read.

Using MXC_I2C_MasterTransaction() with rx_len = 1, tx_len = 1, restart = 1, I get the following output on my logic analyzer:

After the intended read (returning 0xA8) with a NAK, a RESTART is issued and a second read is sent by the main with a dummy return of 0x00. This second dummy read is causing hangups later in my code while attempting to interface the MAX20303 with the opcodes.

This is using the i2c_reva driver.

Getting Time out error when in debug mode for afe_load_trims API in HART_UART example

Siddalingayya — Tue, 25 Nov 2025 09:44:14 GMT

Hi Team,

I have following questions for the MAX32675C Evaluation board

> I am getting time out error -10 when i am trying to step into the HART_UART example for afe_load_trims API . This is blocking my code debugging. But in release mode i dont see this error. i am attaching the snapshot as well.

> I am not able to see HART waveform at FSK_OUT pin and CC loop . I am running the HART_UART Example . Please suggest what setting needs to be done in code or in the MAX32675C evaluation board

Please respond to above queries as soon as possible

Regards

Siddalingayya

Need MAX32655FTHR DAPLink Firmware File

aramy — Mon, 24 Nov 2025 12:02:09 GMT

Hello,

I need the correct DAPLink interface firmware for the MAX32655FTHR development board.

**Current Issue:**
- My board is incorrectly flashed with MAX78000FTHR firmware
- OpenOCD fails with "target examination failed"
- details.txt shows URL: www.maximintegrated.com/max78000fthr

**Required File:**
- max32655fthr_if_crc.bin (64KB)
- The interface firmware only, not the full factory image

Could you please attach the correct firmware file to your reply?

Thank you!

Need Help: SPI1 Not Working on MAX32675 EV-KIT Rev-D

Ndp1995 — Mon, 24 Nov 2025 06:22:46 GMT

Hi Team,

I am using the MAX32675 EV-KIT Rev-D and trying to run the SPI1 Master example from the MSDK. The example is not working on the evaluation board, so I need clarification on the hardware and pin configuration.

Could you please confirm the following:

Which pins are officially used for SPI1 on the MAX32675 EV-KIT Rev-D?
(MISO, MOSI, SCK, SS0)
Are there any jumper settings required on the EV-KIT to enable SPI1?
Do the SPI examples in the MSDK need any code changes for EV-KIT Rev-D?
Or should the example work with the default pin configuration?
Is SPI1A (P0.14, P0.15, P0.16, P0.17) supported on this EV-KIT revision?
Which pin mapping should we connect to an external SPI device on EV-KIT Rev-D?

I am unable to get the SPI1 example working, so your guidance on correct pin mapping, jumpers, and configuration will be very helpful.

Flashing Issue on MAX32675 After PWM Switching Code

Ndp1995 — Fri, 21 Nov 2025 05:58:42 GMT

I flashed the below PWM code on the MAX32675 EVKIT to switch PWM output between P0.9 and P0.17 inside the TMR0 interrupt.
After flashing this code, the board stopped responding to the MAX32625PICO debugger, and I couldn’t program new firmware.

I had to recover it using J-Link mass erase.

Can you please check what might be wrong in this code and why this flashing issue happened?

After loading this firmware:

PWM switches initially,
But after reset the debugger stops detecting the MCU,
Only J-Link mass erase brings the board back.

Can you please review the code and help identify what is causing this issue?

Thanks,

Nandan
/******************************************************************************/ #include <stdio.h> #include <stdint.h> #include "mxc_device.h" #include "mxc_sys.h" #include "nvic_table.h" #include "gpio.h" #include "board.h" #include "tmr.h" #include "led.h" #define CLOCK_SOURCE MXC_TMR_IBRO_CLK #define PWM_TIMER0 MXC_TMR0 uint8_t timerPinFlag9 = 1; uint8_t timerPinFlag17 = 0; void PWMTimer0(uint32_t PwmFre, uint32_t Dutycycle) { mxc_tmr_cfg_t tmr; unsigned int periodTicks = MXC_TMR_GetPeriod(PWM_TIMER0, CLOCK_SOURCE, 16, PwmFre); unsigned int dutyTicks = periodTicks * Dutycycle / 100; MXC_TMR_Shutdown(PWM_TIMER0); tmr.pres = TMR_PRES_16; tmr.mode = TMR_MODE_PWM; tmr.clock = CLOCK_SOURCE; tmr.cmp_cnt = periodTicks; tmr.pol = 1; MXC_TMR_Init(PWM_TIMER0, &tmr, true); MXC_TMR_SetPWM(PWM_TIMER0, dutyTicks); MXC_TMR_Start(PWM_TIMER0); } void GPIO_Config_TMR09(uint8_t alt) { mxc_gpio_cfg_t cfg; cfg.port = MXC_GPIO0; cfg.mask = MXC_GPIO_PIN_9; cfg.func = alt; cfg.pad = MXC_GPIO_PAD_NONE; cfg.vssel = MXC_GPIO_VSSEL_VDDIO; cfg.drvstr = MXC_GPIO_DRVSTR_0; MXC_GPIO_Config(&cfg); } void GPIO_Config_TMR017(uint8_t alt) { mxc_gpio_cfg_t cfg; cfg.port = MXC_GPIO0; cfg.mask = MXC_GPIO_PIN_17; // now correctly 17 cfg.func = alt; cfg.pad = MXC_GPIO_PAD_NONE; cfg.vssel = MXC_GPIO_VSSEL_VDDIO; cfg.drvstr = MXC_GPIO_DRVSTR_0; MXC_GPIO_Config(&cfg); } void PwmTimerHandler(void) { MXC_TMR_ClearFlags(PWM_TIMER0); if (timerPinFlag9) { timerPinFlag9 = 0; timerPinFlag17 = 1; GPIO_Config_TMR017(4); // P0.17 → timer GPIO_Config_TMR09(1); // P0.9 → alt1 PWMTimer0(2000, 30); } else { timerPinFlag9 = 1; timerPinFlag17 = 0; GPIO_Config_TMR09(4); // P0.9 → timer GPIO_Config_TMR017(1); // P0.17 → alt1 PWMTimer0(1000, 50); } } int main(void) { MXC_NVIC_SetVector(TMR0_IRQn, PwmTimerHandler); NVIC_EnableIRQ(TMR0_IRQn); GPIO_Config_TMR09(4); PWMTimer0(1000, 50); while (1) { } return 0; }

Why does MAX32666 i2s PCM always truncate samples to 24 bits?

obones — Sat, 15 Nov 2025 22:17:19 GMT

Hello,

I'm trying to output some 32bits audio samples on the DOUT port from the Audio Subsystem of the MAX32666 and I find that all samples are lacking the bottom 8 bits, effectively leading to a down conversion to 24 bit samples.

In the PCM_Config register, I have placed the 0xC0 value, thus asking for 32 bit channel size, I2S format and extra bits transmitted as zero, while I set the PCM_CLOCK_SET_UP register to 0x04 to get a 64 BCLK to LRCLK ratio to cater for two 32bits channels.

As I continuously fill the TX_PCM_CH0_ADDR and TX_PCM_CH1_ADDR with 0xFFFFFFFF, I expect to observe an always "high level" on the DOUT pin. But sadly, here is what I observe:

The BCLK is in red while the DOUT is in yellow and you can clearly see that there are 8 BCLK periods at zero. If I change PCM_CONFIG value to 0x80, I observe the same result, thus leading me to believe 32 bit channel size is not working.

What could be the reason for the 32 bits channel size not working? What configuration have I missed?

Getting the MAX32666 pulse trains output on a single pin outside of SDHC pins

obones — Thu, 13 Nov 2025 15:00:55 GMT

Hello,

I have a MAX32666FTHR board and would like to use the Pulse Train modules to generated precisely timed signals with them.

Reading the user guide, I see that I can "chain" them using the PTn_RESTART.on_pt_x_loop_exit register values for instance, giving me the possibility to create a signal of up to 32*16=512 bits

What I have not been able to figure out is how I could get those "multiplexed" into the same output pin.

I mean, there is the alternate function table that tells me I can get pulse trains each on their respective pin, effectively preventing me from using the SDHC card at the same time. But I was kinda expecting the ability to route the pulse trains output to a single unique pin in the P0 group.

Is this doable?

MAX32666 I²S Stereo Capture – Right Channel Data Issue & Example Code Request

Surajkumar — Fri, 07 Nov 2025 07:04:10 GMT

I am currently developing a stereo I²S audio capture system using the MAX32666 microcontroller and two DMM-4026-B-I2S-EB-R MEMS microphones. The setup uses a shared data line (I2S_DATA_IN) with common BCLK and LRCLK, configured for a 64-bit frame (2 × 32-bit slots) at 48 kHz LRCLK and 3.072 MHz BCLK. While valid audio samples are successfully captured from one microphone channel(CH0 - Left Channel), the second channel (CH1 - Right Channel) continues to output invalid or zero data despite enabling both RX channels (CH0 and CH1) and verifying hardware connections. Several configuration attempts—including interleaved (TDM) mode, slot mapping adjustments, and clock tuning—have not resolved the issue.

I would greatly appreciate it if you could review the source code included below and confirm whether any register configurations or initialization steps may be missing or incorrect. Additionally, please share any available example code or application notes demonstrating stereo I²S read/write operations on the MAX32666. If there are specific considerations or internal settings for dual-microphone operation over a shared data line, your recommended approach would be highly valuable. As this functionality is critical to our ongoing audio development, I kindly request your feedback and solution at the earliest convenience.

/**
 * @file main.c
 * @brief I2S Stereo Microphone Capture + UART 16-bit PCM Sender @115200 baud
 *
 * This program captures 24-bit stereo audio samples from two I²S digital MEMS microphones
 * connected to the MAX32666 (or similar MAXIM MCU). It then converts the 24-bit samples
 * into 16-bit signed PCM format, downsamples them to ~8 kHz (for simplicity and bandwidth) || right now no downsampling is not applied,
 * and transmits interleaved stereo samples over UART for logging or audio recording on PC.
 *
 * ----------------
 *  Audio Path:
 *  I²S Mics (L & R) → I²S Peripheral → Interrupt Handler → PCM Buffers
 *  → Interleaved Stereo PCM → UART → PC
 *
 * ----------------
 *  Author: Surajkumar Sharma
 *  Date: Nov 2025
 */

#include <stdio.h>
#include <stdint.h>
#include <string.h>
#include "mxc_device.h"
#include "mxc_delay.h"
#include "mxc_pins.h"
#include "board.h"
#include "gpio.h"
#include "drv_uart.h"
#include "nvic_table.h"
#include "icc.h"
#include "gcr_regs.h"
#include "audio_regs.h"

/* -------------------------------------------------------------------------
 *                          CONFIGURATION PARAMETERS
 * ------------------------------------------------------------------------- */

// Sampling and bit rate configuration
#define SAMPLE_RATE 48000U        // Original sampling rate of I²S microphones (48 kHz)
#define NUM_SLOTS 2               // Stereo → 2 channels
#define BITS_PER_SLOT 32          // Each I²S slot = 32 bits
#define AUDIO_CLOCK_IN 96000000U  // 96 MHz input clock to audio peripheral
#define AUDIO_CLOCK_OUT (NUM_SLOTS * BITS_PER_SLOT * SAMPLE_RATE)

// GPIO pin definitions for I²S interface
#define BCLK_PIN   MXC_GPIO_PIN_27
#define DIN_PIN    MXC_GPIO_PIN_26
#define LRCLK_PIN  MXC_GPIO_PIN_24

// I²S pin configuration (alternate function mapping)
const mxc_gpio_cfg_t gpio_cfg_i2s = {
    MXC_GPIO0,
    BCLK_PIN | DIN_PIN | LRCLK_PIN,
    MXC_GPIO_FUNC_ALT1,
    MXC_GPIO_PAD_PULL_UP
};

/* -------------------------------------------------------------------------
 *                          AUDIO BUFFER DEFINITIONS
 * ------------------------------------------------------------------------- */

#define AUDIO_BUFFER_SIZE (8000 * 10)  // Samples per channel (≈10 seconds of audio)
#define SAMPLE_SKIP 1                  // Downsampling factor → 48kHz / 6 = 8kHz effective

// Buffers for Left and Right channels
static volatile int16_t audio_buffer_L[AUDIO_BUFFER_SIZE];
static volatile int16_t audio_buffer_R[AUDIO_BUFFER_SIZE];

// State variables
static volatile uint32_t sample_index = 0;  // Current index in buffer
static volatile uint8_t skip_count = 0;     // Downsampling counter
static volatile uint8_t buffer_full = 0;    // Flag when buffer is filled

/* -------------------------------------------------------------------------
 *                              HELPER FUNCTIONS
 * ------------------------------------------------------------------------- */

/**
 * @brief Compute greatest common divisor (used for clock ratio setup)
 */
static uint32_t gcd(uint32_t a, uint32_t b)
{
    return b ? gcd(b, a % b) : a;
}

/* -------------------------------------------------------------------------
 *                          I2S AUDIO INTERRUPT HANDLER
 * ------------------------------------------------------------------------- */

/**
 * @brief Handles incoming I²S samples from both stereo channels.
 *
 * The handler performs the following steps:
 * 1. Reads raw 24-bit PCM samples from left and right channels.
 * 2. Extracts and sign-extends 24-bit samples to 32-bit integers.
 * 3. Converts 24-bit samples to 16-bit for UART transmission.
 * 4. Downsamples data by a factor of SAMPLE_SKIP.
 * 5. Stores samples into audio buffers until full.
 */
void AUDIO_IRQHandler(void)
{
    // Step 1: Read raw 24-bit PCM samples (packed in 32-bit words)
    uint32_t raw_L = MXC_AUDIO->rx_pcm_ch0_addr;
    uint32_t raw_R = MXC_AUDIO->rx_pcm_ch1_addr;

    // Step 2: Extract 24-bit MSB-aligned samples
    int32_t s24_L = (int32_t)((raw_L >> 8) & 0x00FFFFFFU);
    int32_t s24_R = (int32_t)((raw_R >> 8) & 0x00FFFFFFU);

    // Step 3: Sign-extend 24-bit to 32-bit integer
    if (s24_L & 0x00800000U) s24_L |= 0xFF000000U;
    if (s24_R & 0x00800000U) s24_R |= 0xFF000000U;

    // Step 4: Convert to 16-bit signed PCM by discarding LSBs
    int16_t s16_L = (int16_t)(s24_L >> 8);
    int16_t s16_R = (int16_t)(s24_R >> 8);

    // Step 5: Downsample to reduce UART bandwidth || right now SAMPLE_SKIP = 1 (no downsampling)
    if (++skip_count >= SAMPLE_SKIP)
    {
        skip_count = 0;

        if (!buffer_full)
        {
            // Store samples into buffers
            audio_buffer_L[sample_index] = s16_L;
            audio_buffer_R[sample_index] = s16_R;
            sample_index++;

            // If buffer filled, mark full
            if (sample_index >= AUDIO_BUFFER_SIZE)
            {
                buffer_full = 1;
                sample_index = 0;
            }
        }
    }

    // Clear interrupt flags
    MXC_AUDIO->int_pcm_rx_clr = 0xFFFFFFFF;
}

/* -------------------------------------------------------------------------
 *                          I2S MICROPHONE INITIALIZATION
 * ------------------------------------------------------------------------- */

/**
 * @brief Initializes the I²S hardware for stereo microphone capture.
 *
 * Steps:
 * 1. Enable required peripheral clocks.
 * 2. Configure GPIO pins for I²S signals.
 * 3. Set up clock ratio (M/N) for target audio rate.
 * 4. Configure PCM format and slot mapping.
 * 5. Enable RX channels and global audio engine.
 * 6. Enable interrupt for RX data availability.
 */
void i2s_mic_init(void)
{
    uint16_t m, n;

    MXC_ICC_Enable();  // Enable instruction cache
    MXC_GCR->perckcn0 &= ~MXC_F_GCR_PERCKCN0_GPIO0D;   // Enable GPIO0 clock
    MXC_GCR->perckcn1 &= ~MXC_F_GCR_PERCKCN1_AUDIOD;   // Enable Audio clock
    MXC_GPIO_Config(&gpio_cfg_i2s);                    // Configure I²S pins

    // Compute M/N divider for audio clock generation
    m = AUDIO_CLOCK_IN / gcd(AUDIO_CLOCK_IN, AUDIO_CLOCK_OUT);
    n = (AUDIO_CLOCK_OUT * (uint64_t)m) / AUDIO_CLOCK_IN;

    MXC_AUDIO->m_val = m;
    MXC_AUDIO->n_val = n;

    // Configure I²S/PCM clock and format
    MXC_AUDIO->modulator_controls = MXC_AUDIO_MOD_CNTL_PCM_SEL;         // PCM mode
    MXC_AUDIO->pcm_clock_set_up = MXC_AUDIO_CLK_CFG_BSEL_64;            // 64-bit frame (2x32)
    MXC_AUDIO->pcm_config = MXC_AUDIO_PCM_CFG_CHANSZ_32 | MXC_AUDIO_PCM_CFG_FRMT_I2S | MXC_AUDIO_PCM_CFG_CHANSEL; // 32-bit, I²S format

    // Sample rate configuration
    MXC_AUDIO->pcm_rx_sample_rates = MXC_AUDIO_PCM_RX_SR_DATAPORT_48000 |
                                     MXC_AUDIO_PCM_RX_SR_INTERFACE_48000;

    // Enable RX channels (Left + Right)
    MXC_AUDIO->pcm_rx_enables_byte_0 = MXC_AUDIO_PCM_RX_EN_0_CH0 | MXC_AUDIO_PCM_RX_EN_0_CH1;

    // Select master clocking
    MXC_AUDIO->pcm_clock_dividers_msb = MXC_AUDIO_CLK_DIV_MSB_BLCK_MASTER_SEL |
                                        MXC_AUDIO_CLK_DIV_MSB_BLCK_SEL_MASTER;

    // Map data ports to PCM slots
    MXC_AUDIO->dataport_2_slot_mapping_channel_0 = MXC_AUDIO_PCM_DP2_SLOT_MAP_CH0_EN;
    MXC_AUDIO->dataport_2_slot_mapping_channel_1 = MXC_AUDIO_PCM_DP2_SLOT_MAP_CH1_EN;

    // Enable global PCM and interrupt
    MXC_AUDIO->global_enable = MXC_AUDIO_PCM_GLOBAL_EN;
    MXC_AUDIO->int_en = MXC_AUDIO_PCM_RX_AF_EN;

    // Attach ISR and enable NVIC interrupt
    MXC_NVIC_SetVector(AUDIO_IRQn, AUDIO_IRQHandler);
    NVIC_EnableIRQ(AUDIO_IRQn);
}

/* -------------------------------------------------------------------------
 *                                  MAIN LOOP
 * ------------------------------------------------------------------------- */

/**
 * @brief Main entry point.
 *
 * Initializes UART and I²S, then continuously captures and sends audio frames.
 *
 * Flow:
 *  1. Initialize UART for transmission at 115200 baud.
 *  2. Initialize I²S microphone interface.
 *  3. Wait for buffer to fill with samples.
 *  4. Once full, interleave stereo data (L0R0, L1R1...) and send over UART.
 *  5. Reset buffer and repeat.
 */
int main(void)
{
    uart_init();     // Initialize UART driver
    i2s_mic_init();  // Initialize I²S interface

    MXC_Delay(200000);  // Small delay before starting capture

    while (1)
    {
        // When buffer is full → send data
        if (buffer_full)
        {
            // Interleave L & R channels: L0R0 L1R1 L2R2 ...
            for (uint32_t i = 0; i < AUDIO_BUFFER_SIZE; i++)
            {
                int16_t sample_pair[2] = { audio_buffer_L[i], audio_buffer_R[i] };
                uart_write((uint8_t *)sample_pair, sizeof(sample_pair));
            }

            // Reset buffer flag to capture next frame
            buffer_full = 0;
        }
    }
}

MAX32666GXMBT+T LXA ball shorted to GND

CKR1 — Tue, 21 Oct 2025 18:05:17 GMT

I just finished a small prototype run with qty = 20 boards, with each board having a MAX32666GXMBT+T on it. 2 of the boards failed my power supply check and upon deeper analysis, and desoldering this part, I was able to confirm that the LXA pin (ball B11) was dead shorted (0 ohms) on the BGA part. Seeing how this occurred on only 10% of my boards, with all the others working just fine, I am hoping to determine if there is something that I could have done with my testing that would result in creating this internal short on the BGA or if there is potential for these parts to just be bad out of the box. I am unable to find specific electric specifications around this pin that could help me further understand how this could be happening. Are you able to provide any additional information on this pin and if it has known sensitivities? I have a planned larger production run and would like to not experience this in larger quantities.

ADuCM4050 SPORT cannot word continuously

GyroZhang — Fri, 01 Aug 2025 06:10:09 GMT

I used the ADuCM4050 as an MCU to receive PCM data from the ADAU7002, with HCLK at 26MHz, BCLK at 2.6MHz, and Frame Syn at 2.6/256 MHz(about 10kHz). I got two questions for now:

1. I found that the SPORT only generates clocks when submited a buffer, and stops after the buffer is full, causing the microphone chip to stop working. Can the SPORT interface be configured to continuously output clocks?

2. The maximum serial word length of SPORT is 32 bits. Does this mean that only the 32 bits of data in the begining are received between two frame sync signals? However, in my current setup with ADAU7002 using TDM8 and 5/6 slot mode (see the figure below), the SPORT mode fails to receive valid data, only capturing 0 and -1.

Below is figure from ADAU7002 datasheet.

Below is screenshot of 7002 output waveform.

Below is data collected by 4050，1st column is No. of sample points, 2nd column is data.

deployment support

cps007 — Thu, 31 Jul 2025 11:20:56 GMT

I have a small ML model created using image analysis. I wanted to deploy it in max78000 and predict with live footage using the camera. i have converted to onnx version, getting trouble in converting to tensorflow lite and then so on... deploying. What are the things i should taken care of. As per some instruction, it said that ai8x-synthesis.py can convert onnx to tflite. but i can't get the so named file

OTA on arrival support for max32666

firmadv — Fri, 11 Jul 2025 07:46:44 GMT

Hi,

We are designing a compact PCB with MAX32666. Does it support OTA programming via Bluetooth when it arrives as a blank part to us? This would help us in reducing the size of the PCB significantly.

Looking forward for the quick response.

Support Request: ADC Linearity Issue in MAX32690 Microcontroller

Akshay17 — Tue, 01 Jul 2025 11:47:56 GMT

Dear Team,

we are developing a Temperature Transducer. For this application, we are using the MAX32690 microcontroller, specifically leveraging its internal 12-bit ADC for temperature sensing.

We have encountered a linearity issue with the internal ADC that we would like your assistance with.

Issue Summary

We are using the MAX32690 ADC example code provided by Analog Devices.
From -40°C to +2°C, both the input to the ADC and the ADC counts increase linearly; however, between +2°C and +4°C, while the input continues to rise linearly, the ADC counts exhibit non-linear behavior as shown in the graph below, after that ADC counts increases linearly with offset as shown in graph below.

(X axis: Temperature value & Y axis: ADC counts)

This behavior is consistent across multiple tests and setups.

Testing Details

We have tested with both internal and external voltage references:
- With 3.3V external reference, the issue appears around 1.7V.
- With 2.0V internal reference, the issue appears around 1.0V.
We have verified our analog front-end circuitry, including the op-amp stage, and confirmed it is functioning correctly.
We also tested by applying a known external millivolt signal directly to the development board, and the issue persisted.

Request for Support

We would appreciate your insights on the following:

Is this a known issue with the MAX32690 ADC?
Are there any errata or limitations related to ADC linearity in this device?
Are there any recommended workarounds or configuration changes we can try?

EVAL-ADICUP3029 and EVAL-AD5941BATZ Battery Impedance results are too small

yigit1802 — Fri, 27 Jun 2025 10:50:51 GMT

Hello, I am using EVAL-ADICUP3029, EVAL-AD5941BATZ and SensorPal 2.5.3.2 to perform EIS test on li-ion batteries. I have performed the tests on 3 different cells, 2 of them are in similar conditions (internal resistance, SOC) and one of them is different from them. I can see the difference between cells as I expected there is no problem but my impedance values are too small. For example, my cell has an 40mOhm internal resistance but when i performed the test my sensorpal Real Z data is always below 1mOhm. I have checked the voltages on AIN2 and AIN3 and I think the voltages okay. Also the nyquist plots I get from various tests are stable and looks okay too. Could be a problem at SensorPal? I have tried various combinations on DC bias and AC amplitude results but results are still below 1mOhm.

Ultrasonic sensor driver solutions

ayyanar — Thu, 26 Jun 2025 12:12:51 GMT

Hi All,

I'm looking for Hardware development of Ice level sensing in the range of 10 cm to 150cm (subject to change) with Ultrasonic sensors.

To drive and sense the ultrasonic sensors, we are looking for the solution from Analog Devices and found the IC MAXQ7667 DS
Looks like this IC is standalone microcontroller based ultrasonic sensing IC. Is there any IC with focus only on analog frontend of the Ultrasonic transducers which should support burst generation to ultrasonic sensor and sense the return signal. another side it has to support the communicating with existing microcontroller.
Please let me know, if you need any clarifications. I'm looking forward to your response!

Programming MAX96717f + MAX96714F once

FK123 — Fri, 13 Jun 2025 08:32:35 GMT

HI,

I am using SerDes MAX96717F Ser and MAX96714F Des (MAXIM INTEGRATED) along with raspberry pi 4 to get the output of Raspi Camera on RPi4.

1: The pipeline has been generated using the GMSL gui through script generation.

2: Once cpp file is loaded, i am able to get the display at the Rpi4.

The issue is whenever i power cycle the boards. I need to load the script again to get the output.

How can i program it for once and use it even after power cycle?

Any leads?

Visual inspection / acceptance criteria - industry or MIL standard?

meeotch — Wed, 11 Jun 2025 02:32:30 GMT

Is there an industry or MIL standard or other requirement that the ADUCM4050BCBZ is inspected to? I'm looking for an answer similar to this one I found for another product.

ez.analog.com/.../131248

Some problems encountered when using EVAL-ADICUP3029

zezeze — Tue, 10 Jun 2025 11:43:05 GMT

Hello, everyone！
I'd like to ask a few questions about the EVAL-ADICUP3029 board.
1.Programming problems:
After I uploaded a piece of code related to uart and directly operated on the hardware registers (involving pADI_UART0 and GPIO Settings), our EVAL-ADICUP3029 board became unresponsive:
The motherboard can no longer be programmed through keil. No matter how you upload the code, it fails and will display the situation as shown in the following figure.

Even pressing the RESET button cannot restore it to normal operation.
The red light on the board will keep on and not flash.

Currently, the development board is in an unusable state. Apart from the normal upload of code, we have not caused any human damage.

2.Questions related to BLE:
Furthermore, we have noticed that the BLE module on ADICUP3029 is marked as deprecated in the documentation.

We want to confirm:
Can the BLE module that comes with the EVAL-ADICUP3029 board still be used and developed at present?
If so, can BLE applications be developed using Keil (μ Vision IDE)? Or is it necessary to use CCES?
If it cannot be used any longer, do you have any updated guidelines or alternative suggestions for developing BLE on the ADuCM3029 board?

Thank you very much for your help.

How to debug core1

nthzera — Tue, 29 Apr 2025 13:24:25 GMT

Hello. I've been trying to implement some features using the 2nd core on the MAX32666 but unfortunately I'm not able to debug the 2nd core.

Debugging core0 is working as expected. Code running on code1 is also running as expected but I haven't found a way to inspect what core1 is doing through the CMSIS-DAP (MAX3265PICO).

I'm not sure if the 2nd core supports debug at all. Looking through the MaximSDK OpenOCD scripts, there isn't a ".cfg" file especifically for the MAX32666, only for the MAX32665.

I hope someone could help me locate the issue or clarify if this is supported at all.

Thank you.

Debug problem

IdanMichaely — Wed, 19 Mar 2025 16:32:50 GMT

We use ADuCM3029 ARM Cortex M3 evaluation module (

https://wiki.analog.com/resources/eval/user-guides/eval-adicup3029

with Crosscore embedded studio IDE ver 3.02.

We open a simple project following the instructions in this link :

https://wiki.analog.com/resources/eval/user-guides/eval-cog-ad3029lz/tools/cces_guide

The build was successful, and we got this message :

15:37:15 Build Finished. 0 errors, 0 warnings. (took 2s.219ms)

We would like to put a break point on the first line of the main() function.

We set the JTAG to : CMSIS-DAP (What is the recommended target interface?)

What is the recommended settings for the Max speed?

When we tried to load the code to the target Debug button we get these errors :

Open On-Chip Debugger (Analog Devices 0.12.0-1.1.2) OpenOCD 0.12.0 (2024-10-10-14:46)
Licensed under GNU GPL v2
Report bugs to <processor.tools.support@analog.com>
0
DEPRECATED! use 'adapter speed' not 'adapter_khz'
C:/analog/cces/3.0.2/ARM/packs/AnalogDevices/ADuCM302x_DFP/3.2.1/openocd/scripts//target/aducm302x.tcl:55: Error: target requires -dap parameter instead of -chain-position!
in procedure 'script'
at file "embedded:startup.tcl", line 28
at file "C:/analog/cces/3.0.2/ARM/packs/AnalogDevices/ADuCM302x_DFP/3.2.1/openocd/scripts/target/aducm3029.cfg", line 6
at file "C:/analog/cces/3.0.2/ARM/packs/AnalogDevices/ADuCM302x_DFP/3.2.1/openocd/scripts//target/aducm302x.tcl", line 55

How can we resolve these errors?

In addition, the code example of a blinking LED in the reference design link https://wiki.analog.com/resources/eval/user-guides/eval-adicup3029/reference_designs/demo_blink is broken. Is there an active git with working examples for our board?

Thanks

putting the CM4 into standby mode

biosbob — Sun, 16 Mar 2025 13:25:09 GMT

i am trying to put the MAX32655 into STANDBY mode, with the RTC programmed for a 1s wakeup.... my code works just fine when i enter SLEEP MODE....

section 3.3.5 of the User Guide explains the steps from a CM4-RV perspective.... in my use-case, i'm just using the CM4; i'm not sure what state the RV is at POR, but i want it powered-off....

could someone tell me the exact sequence i need to follow???

and could someone explain whether i need to deal with the PWRSEQ, as my only wakeup source is the RTC....

MAX7800FTHR

MohamedElwakil — Wed, 05 Mar 2025 20:27:58 GMT

I've got a couple of questions:

1. With the MAX7800FTHR boards is it possible to monitor the DAPLink Debugger information with a software analyzer?

2. If the board is transmitting data over USB, is it possible to see that information from the virtual UART console?

Regards,

Mohamed Elwakil

ADuCM3029_demo_cn0418 software unresponsive

NormS — Fri, 21 Feb 2025 22:34:27 GMT

I purchased the EVAL-CN0418-ARDZ board and have mated it to EVAL-ADICUP3029 board. I dragged and dropped this hex file:

https://github.com/analogdevicesinc/EVAL-ADICUP3029/releases/download/Latest/ADuCM3029_demo_cn0418.hex

onto the DAPLINK drive as instructed on this page:

https://wiki.analog.com/resources/eval/user-guides/eval-adicup3029/reference_designs/demo_cn0418

I have PuTTY set up as shown in the user guide and when resetting the processor board see the welcome screen which ends with the prompt:

Welcome to cn0418 application!
Type <help> or <h> to see available commands...

The problem is that when I type h or help there's no response from board. Is there something I'm missing? The guide says "This is the EASIEST way to get started with the reference design". I tried installing CCES and compiling the source code but that became a rabbit hole of errors I couldn't resolve!