Post Go back to editing

nRF52832 + ADXL362: “wrong part_id: 255” / device not ready in Zephyr (NCS v3.0.2)

Category: Software
Product Number: ADXL362

Hello,

I’m trying to bring up an ADXL362 accelerometer over SPI on an nRF52832 DK using NCS v3.0.2 / Zephyr v4.0.99.

What I did

  • Base sample: samples/sensor/accel_polling

  • Overlay for &spi0 with pinctrl (DK Arduino header pins):

    • SCK = P0.25 (D13)

    • MOSI = P0.23 (D11)

    • MISO = P0.24 (D12)

    • CS = P0.22 (D10) → also tried P0.17

  • Added aliases { accel0 = &adxl362; }

  • prj.conf has CONFIG_SPI=y, CONFIG_SENSOR=y, CONFIG_ADXL362=y

  • Reduced SPI speed: spi-max-frequency = <500000>

  • RTT console enabled for logging

What happens

On boot I always see:

My suspicion

It looks like the ADXL362’s SDO pin is not being driven, or CS is never really asserted. Could be:

  • Breakout board strapped in 3-wire SPI mode (no SDO routed).

  • Incorrect wiring on my breakout’s CS/SDO pin.

  • Some oversight in Zephyr overlay.

Question

Has anyone successfully run ADXL362 with nRF52832 in Zephyr?

  • Do I need to configure anything special for 4-wire mode?

  • Is my overlay missing something?

  • Could this be a breakout board (3-wire vs 4-wire) issue?

Any tips, example DTS overlays, or known-good wiring setups would be very helpful.

Thanks in advance!

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.