How to get accelerometer value of Thingy:91?

[Yusuke]

I want to tranceive data to ADXL362 through SPI and refer to this program.

https://github.com/Rallare/fw-nrfconnect-nrf/tree/nrf9160_samples/samples/nrf9160/spi

However, I can't get data.

I only modified tx_buffer value.

void spi_test_send(void)
{
	int err;
	u8_t tx_buffer[1] = {0x00}; // Modified here
	u8_t rx_buffer[1];

	const struct spi_buf tx_buf = {
		.buf = tx_buffer,
		.len = sizeof(tx_buffer)
	};
	const struct spi_buf_set tx = {
		.buffers = &tx_buf,
		.count = 1
	};

	struct spi_buf rx_buf = {
		.buf = rx_buffer,
		.len = sizeof(rx_buffer),
	};
	const struct spi_buf_set rx = {
		.buffers = &rx_buf,
		.count = 1
	};

	err = spi_transceive(accel_spi_dev, &spi_cfg, &tx, &rx);
	if (err) {
		printk("SPI error: %d\n", err);
	} else {
		/* Connect MISO to MOSI for loopback */
		printk("TX sent: 0x%02x\n", tx_buffer[0]);
		printk("RX recv: 0x%02x\n", rx_buffer[0]);
//		tx_buffer[0]++;
	}	
}

Also, I added nrf9160_pca20035_v0_3_0.overlay file.

Any tip?

[MJD093]

I am trying to do the same thing, Zephyr do have a sensor example for the ADXL362.

/path/to/ncs/zephyr/samples/sensor/adxl362

As Didrik says, this example uses the sensor.h API library. Don't ask me how to get it to work though, it straight up refused to get the device for 2 hours then randomly started working and I didn't change the example code apart from enabling SPI in the prj.conf .

[Yusuke]

May I ask one more related question?

I want to configure motion detection function of ADXL362 and let it output H level when it detects movement. This is a simple function.

How can I achieve this? 

To do so, you need to write value in a certain register through SPI. 

However, there is no writing and even reading functions in sensor.h. 

I added the above spi_test_send function to  /path/to/ncs/zephyr/samples/sensor/adxl362 program but it returns -35 error code. Any help?

[MJD093]

Not sure to be honest, it should have been simple for the code sample I posted to work. All I needed was the code, a prj.conf and  a generic CMakeList.txt.

It really did look like your Thingy:91 was acting like it had been reflashed without an erase command.

[Didrik Rokhaug]

I agree with MJD093 in that it looked like a missing erase command. To rule out any issues with your code, can you try to program your code using the programmer application?

[Dheeraj]

Hi Yusuke, 

I am facing the same rebooting issue as above on nRF9160 DK (PCA10090).

Actually, I bought the new nRF9160 DK (PCA10090) and trying to connect it, but unfortunately, its getting reboot automatically (Logs similar as above).

I have tried to flash the latest Nordic's pre-compiled Image from nRF9160 DK ==> Downloads [ nrf9160dk_asset_tracker_09-10-2019_c9c833b1.hex ], but no luck. 

I have tried to compile manually with v1.1.0 branch code, no use. 

Could you please help me with this issue. 

Refer me, how you had overcome with this issue. 

This is a roadblock for me. 

Thank you. 

[Didrik Rokhaug]

Hi, Dheeraj.

I looked at the ticket you have, where Heidi-Irene Harvey Sollie is helping you.

She is waiting for a reply to her latest comment. Could you try to work with her to solve your problem?

Best regards,

Didrik

[Dheeraj]

Hi Didrik,

I hope you are doing good..!! 

Yes. She is trying to help me. But looks like this is pretty much a critical issue. 

Please suggest me, if you have some solution as it completely blocked my work. 

I hope you might have remembered, as we are NOT able to flash the nRF52840 on thingy91 (PCA20035) device using " mcumgr " (MCUBoot driver issue on Windows 10),

[   https://devzone.nordicsemi.com/f/nordic-q-a/53730/nrf-connect-v3-2-0-issue-for-nfr9160  ]

I have bought this nRF9160 DK (10090), but unfortunately, it is NOT working as expected. 

I am wondering nRF9160 DK (10090) is NOT working with pre-compiled Images provided by Nordic as well.  

Thank you.