I am trying to get this ADXL357 eval board to work, in connection with either Arduino Uno or Due via I2C. Sometimes I get a connection and can read out data, however often there are problems with setting up the device and I cannot read out data.

I am now using a logic analyser with sigrok/pulseview to take a closer look at what is happening on the I2C bus. I noticed that a) the clock line seems very irregular, the width of the pulses changes, see print screen (n.b. this happens on both the Due and Uno) b) the values that are being transferred are not what I'd expect.

Does the SCL line look normal to you? Or is there maybe something wrong with the wiring or Arduino wire.h library?

See script I am using from Seeed (n.b., the library I am using is for a different breakout board, but does work sometimes).

#include "Seeed_adxl357b.h"

#if defined(ARDUINO_ARCH_AVR)
    #pragma message("Defined architecture for ARDUINO_ARCH_AVR.")
    #define SERIAL Serial
#elif defined(ARDUINO_ARCH_SAM)
    #pragma message("Defined architecture for ARDUINO_ARCH_SAM.")
    #define SERIAL SerialUSB
#elif defined(ARDUINO_ARCH_SAMD)
    #pragma message("Defined architecture for ARDUINO_ARCH_SAMD.")
    #define SERIAL SerialUSB
#elif defined(ARDUINO_ARCH_STM32F4)
    #pragma message("Defined architecture for ARDUINO_ARCH_STM32F4.")
    #define SERIAL SerialUSB
    #pragma message("Not found any architecture.")
    #define SERIAL Serial

#define CALI_BUF_LEN           15
#define CALI_INTERVAL_TIME     250
int32_t cali_buf[3][CALI_BUF_LEN];
int32_t cali_data[3];

float factory;

Adxl357b  adxl357b;

int32_t deal_cali_buf(int32_t* buf) {
    int32_t cali_val = 0;

    for (int i = 0; i < CALI_BUF_LEN; i++) {
        cali_val += buf[i];
    cali_val = cali_val / CALI_BUF_LEN;
    return (int32_t)cali_val;

void calibration(void) {
    int32_t x;
    SERIAL.println("Please Place the module horizontally!");
    SERIAL.println("Start calibration........");

    for (int i = 0; i < CALI_BUF_LEN; i++) {
        if (adxl357b.checkDataReady()) {
            if (adxl357b.readXYZAxisResultData(cali_buf[0][i], cali_buf[1][i], cali_buf[2][i])) {
        // SERIAL.print('.');
    // SERIAL.println('.');
    for (int i = 0; i < 3; i++) {
        cali_data[i] =  deal_cali_buf(cali_buf[i]);
    x = (((cali_data[2] - cali_data[0]) + (cali_data[2] - cali_data[1])) / 2);
    factory = 1.0 / (float)x;
    // SERIAL.println(x);
    SERIAL.println("Calibration OK!!");

void setup(void) {
    uint8_t value = 0;
    float t;

    if (adxl357b.begin()) {
        SERIAL.println("Can't detect ADXL357B device .");
        while (1);
    SERIAL.println("Init OK!");
    /*Set full scale range to ±40g*/
    /*Switch standby mode to measurement mode.*/
    /*Read Uncalibration temperature.*/

    SERIAL.print("Uncalibration  temp = ");


void loop(void) {
    int32_t x, y, z;
    uint8_t entry = 0;
    if (adxl357b.checkDataReady()) {
        if (adxl357b.readXYZAxisResultData(x, y, z)) {
            SERIAL.println("Get data failed!");
        SERIAL.print("X axis = ");
        SERIAL.print(x * factory);
        SERIAL.print("Y axis = ");
        SERIAL.print(y * factory);
        SERIAL.print("Z axis = ");
        SERIAL.print(z * factory);


enter image description here

enter image description here


EDIT: Turns out I didn't have the driver for the logic analyser installed correctly. Changed it (using this instruction) and now the clock signal does look 'normal'. enter image description here

  • \$\begingroup\$ Are you sure your sampling rate is high enough? There are so few samples per pulse, sometimes just one. Please repeat with a higher sampling rate, at least 5 to 10 times. \$\endgroup\$ Commented Mar 29, 2021 at 6:45
  • \$\begingroup\$ Hi @thebusybee, see edit in post. Also increased sample rate to 8 MHz - sorry for the grainy pic :/ \$\endgroup\$
    – daniel
    Commented Mar 30, 2021 at 12:39

3 Answers 3


I²C doesn't care whether it has a steady clock or not; it can't even tell. All it cares is that there's a clock pulse that tells it when to send (or receive) the next bit of data. So this may be unusual, but I don't think it's necessarily a problem in itself. It may be symptomatic of a problem with your arduino or your code, however.


Your added labels on the scope trace seem to be swapped: the upper trace looks like data, the lower trace like clock.

That aside, I2C doesn't much care about the spacing between pulses so long as they're no faster than the standard you intend to support (100kHz, 400kHz).

Generally, SDA should only change state during the SCL low-time except for START and STOP. During the data transfer time it should have a hold time after SCL low and setup time before SCL high. It's hard to tell from your trace, but you should check that carefully.


I was having a similar behaviour with this little device. It shows there are 2 ground pins (5 and 6), but connecting pin 5 gives bad data. Make sure you connect pin 6 to ground.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.