Disabling SPI on Thingy91

RE: Disabling SPI on Thingy91

Cody — Thu, 18 Feb 2021 20:03:58 GMT

Thanks for the insight Simon Ferres, I think there was something else causing an issue and it appeared as though it was the SPI configuration initially.

RE: Disabling SPI on Thingy91

Simon — Tue, 16 Feb 2021 10:59:41 GMT

By the way, unless you already know about it, running ninja rom_report inside the build folder of your sample gives you a really nice overview of how much memory drivers and libraries of your sample occupies.

RE: Disabling SPI on Thingy91

Simon — Mon, 15 Feb 2021 16:59:39 GMT

I'm not able to reproduce this, I set CONFIG_SPI=n in both the hello_world as well as the blinky example, and they worked. By the way, the configuration CONFIG_SPI defaults to 'n' with an ontouched prj.conf, I confirmed this by checking the file <ncs location>\zephyr\samples\basic\blinky\<build folder>\zephyr\.config.

Could you tell me what sample you're using?

Best regards,

Simon

RE: Disabling SPI on Thingy91

Simon — Fri, 12 Feb 2021 15:39:41 GMT

I'm not sure why this is. I know that the adxl372 and the adxl362 are enabled by default in the Device Tree (see nrf\boards\arm\thingy91_nrf9160\thingy91_nrf9160_common.dts) but I still don't see why it fails when CONFIG_SPI=n.

What sample do you use? Are you able to debug the Thingy:91 or get some logs to see exactly where it fails?

I don't have access to a 10-pin cable to test the Thingy:91 at the moment, but will get ahold of one and test it on Monday/Tuesday.

Best regards,

Simon