nRF52832 cannot stop adxl362's spi

RE: nRF52832 cannot stop adxl362's spi

haakonsh — Tue, 07 Jan 2020 10:28:26 GMT

[quote user="bardia3000"]Actually there are some other chips on the SPI bus, So I set the spi_config.ss_pin as NRF_DRV_SPI_PIN_NOT_USED and control CS pin manually.[/quote]

Fair enough.

[quote user="bardia3000"]Also I use SDK version 16.0.0. Can this happen because of NFC2 pin which is at the same pin as P0.10?[/quote]

Not unless it's configured as an NFC pin and not a GPIO. To use these pins as GPIO's you need to set the preprocessor definition CONFIG_NFCT_PINS_AS_GPIOS.

You should always scope your communication lines whenever there's a problem, it will help immensely in debugging the issue.

RE: nRF52832 cannot stop adxl362's spi

bardia3000 — Mon, 06 Jan 2020 15:56:11 GMT

Actually there are some other chips on the SPI bus, So I set the spi_config.ss_pin as NRF_DRV_SPI_PIN_NOT_USED and control CS pin manually. Also I use SDK version 16.0.0. Can this happen because of NFC2 pin which is at the same pin as P0.10?

RE: nRF52832 cannot stop adxl362's spi

haakonsh — Mon, 06 Jan 2020 15:22:17 GMT

You seem to be controlling the CS pin manually, the driver should handle that. What SDK version are you using?

RE: nRF52832 cannot stop adxl362's spi

bardia3000 — Mon, 06 Jan 2020 14:45:57 GMT

Thanks a lot, I define SPI_ACC_SS_PIN as p0.10, It seems like it is always zero with a digital analyzer! Why is that and what can I do? (I set this pin as an output before)

RE: nRF52832 cannot stop adxl362's spi

haakonsh — Mon, 06 Jan 2020 13:13:08 GMT

Take a scope of the SPI lines with a digital analyzer and share it with us.

Also, the first two bytes you receive are not valid for a single register read, so your return value should only be one byte long.