nrf5340dk connection to a bosch's bhi260ab

RE: nrf5340dk connection to a bosch's bhi260ab

j-saur — Fri, 19 Mar 2021 16:49:35 GMT

Thanks Simon! I'll look at those and try to implement them. I didn't use bmm150 because I need an spi connection and I cannot reach the bmm150 data without getting the bhi260ab data first.

RE: nrf5340dk connection to a bosch's bhi260ab

Simon — Fri, 19 Mar 2021 11:00:48 GMT

That will not work. You have not defined the dts node bhi260ab_bmm150 in https://github.com/nrfconnect/sdk-zephyr/tree/master/dts/bindings/sensor. There are several more things that are lacking as well, but take a look at the down below instructions.

Take a look at this link, that demonstrates how to add a new driver to Zephyr: https://devzone.nordicsemi.com/f/nordic-q-a/66230/how-to-add-new-i2c-based-sensor-device-to-ncs-v1-3-0-zephyr-drivers-sensor

Btw. why don't you use the already present driver driver/sensor/bmm150 and the sample zephyr/samples/sensor/bmm150? You just have to add an overlay file in zephyr/samples/sensor/bmm150/boards.

Zephyr might be complicated and difficult in the beginning, but I would recommend you to put off some time to read through the documentation and trying to understand how stuff works. Take a look at these:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/kconfig/index.html

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/dts/index.html

Best regards,

Simon

RE: nrf5340dk connection to a bosch's bhi260ab

j-saur — Wed, 17 Mar 2021 01:02:35 GMT

So I added the api files from bhy as an external driver and tried to get the spi connection working from there. I'm normally 3D developer so I apologize for the basic questions

devzone.nordicsemi.com/.../extDriver.zip

RE: nrf5340dk connection to a bosch's bhi260ab

Simon — Mon, 15 Mar 2021 18:23:42 GMT

I took a look at your new sample and I still saw that bhi260ab_bmm150 and "bosch,bhi260_bmm150" was present. Could you tell me where you got these from? Please read through my previous reply and update your overlay file.

You are calling evice_get_binding(spi_dev->name). This will not do anything since spi_dev->name is null by default. You should instead call device_get_binding(<label used inside bmm150 node>). Take a look at the file \zephyr\samples\sensor\bmm150\src\main.c and update your main.c accordingly. The API used inside your sample is zephyr/includedrivers/spi.h, this is not correct you should use the API drivers/sensor.h. Read NCS tutorial part 3 to understand this better: https://devzone.nordicsemi.com/nordic/nrf-connect-sdk-guides/b/getting-started/posts/nrf-connect-sdk-tutorial---part-3-ncs-v1-4-0#h56sk0f6zs6u1qqs6nj2hbrjty9raxu

Best regards,

Simon

RE: nrf5340dk connection to a bosch's bhi260ab

j-saur — Mon, 15 Mar 2021 17:01:04 GMT

devzone.nordicsemi.com/.../5381.spi_5F00_only.zip

Thanks for your suggestions Simon I was in a hurry to post friday, so I've updated the overlay file and attached my project.

Also here is what my logic analyzer reads:

RE: nrf5340dk connection to a bosch's bhi260ab

Simon — Mon, 15 Mar 2021 15:22:08 GMT

I was not able to build the sample, as the content inside spi_only\boards\nrf5340dk_nrf5340_cpuapp.overlay is not valid:

The spi1 node is not terminated (no "};" at the end of the node).
The property "def-char" is not declared for "nordic,nrf-spim" (SPI master), but for "nordic,nrf-spis.yaml"
There is no yaml file for the compatible "bosch,bhi260_bmm150", use "bosch,bmm150" instead

&spi1 {
	compatible = "nordic,nrf-spim";
	status = "okay";
	sck-pin = <4>;
	mosi-pin = <5>;
	miso-pin = <6>;
	cs-gpios = < &gpio0 7 GPIO_ACTIVE_LOW>;
	def-char = <0x00>;

	spi_dev:bhi260ab_bmm150@2B {
		compatible = "bosch,bhi260_bmm150";
		reg = <0x2B>;
		spi-max-frequency = <4000000>;
		int1-gpios = <&gpio0 10 GPIO_ACTIVE_HIGH>;
	};

I suspect that you didn't use the same name as your overlay folder when building it (such that the overlay file was just ignored), since you were actually able to run the sample.

If you create an overlay file with the name nrf5340dk_nrf5340_cpuapp.overlay you should build using the board nrf5340dk_nrf5340_cpuapp for the changes in the overlay file to take effect.

I would recommend you to use the sample \zephyr\samples\sensor\bmm150\src\main.c as a reference for how to go about it. There is no overlay file in that sample for your particluar board, so you have to add it yourself. Take a look at e.g. https://github.com/nrfconnect/sdk-nrf/blob/v1.4.2/samples/nfc/tnep_poller/nrf5340dk_nrf5340_cpuapp.overlay to get a general idea how to implement the overlay file.

Best regards,

Simon

RE: nrf5340dk connection to a bosch's bhi260ab

niebert — Sat, 13 Mar 2021 07:22:33 GMT

A SPIM device ALWAYS receives data from the slave, even if nothing is connected to it. So you have to look into the data with logging to see what you actually receive (if anything). If that does not help, really, I'd recommend using a logic analyzer to observe what is going on between your MCU and the sensor (at least you can observe if the master is set up correctly). They are dead cheap these days really useful for understanding a symptom in the situation you describe.