<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>thingy91x nrf5340 bmi270 spi no communication</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125502/thingy91x-nrf5340-bmi270-spi-no-communication</link><description>Dear community, we&amp;#39;re having trouble connecting our thingy91x to the BMI270 via the nRF5340 using SPI. We&amp;#39;ve tried many similar cases without success. Here&amp;#39;s our setup: Visual Studio Code (1.105) with nRF Connect SDK and Toolchain (V3.1.1) 
 The app.overlay</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Nov 2025 19:18:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125502/thingy91x-nrf5340-bmi270-spi-no-communication" /><item><title>RE: thingy91x nrf5340 bmi270 spi no communication</title><link>https://devzone.nordicsemi.com/thread/554595?ContentTypeID=1</link><pubDate>Mon, 17 Nov 2025 19:18:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bad230ee-efcf-4943-839c-447c16e23eb6</guid><dc:creator>Benjamin</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The default configuration gives the I2C and SPI to the nRF9151. These buses can only be controlled by a single host.&lt;br /&gt;&lt;br /&gt;The&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/main/boards/nordic/thingy91x/dts/thingy91x_no_buses.dtsi"&gt;thingy91x_no_buses.dtsi&lt;/a&gt;&amp;nbsp;file shows how you can disable the buses on the nRF9151. You will&amp;nbsp;also need to use a different partition layout since the secondary app partition is on the SPI flash by default.&amp;nbsp;This is already done with this &lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/main/boards/nordic/thingy91x/thingy91x_nrf5340_pm_static_ext_flash_no_tfm.yml"&gt;file&lt;/a&gt;.&amp;nbsp;One way to apply that&lt;/span&gt;&lt;span&gt;&amp;nbsp;memory layout is by adding the following Kconfig symbol in sysbuild.conf:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;SB_CONFIG_THINGY91X_STATIC_PARTITIONS_NRF53_EXTERNAL_FLASH=y&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;There is also a bug in NCS 3.1.1 where this symbol can only be selected on the nRF53 side. The q&lt;/span&gt;&lt;span&gt;uick fix is to&amp;nbsp;remove&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/7a762b56f289684e7d8140f43d75ed46611a8212/boards/nordic/thingy91x/Kconfig.sysbuild#L21"&gt;this&lt;/a&gt;&amp;nbsp;line. See&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/pull/25630"&gt;this PR&lt;/a&gt;.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Benjamin&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: thingy91x nrf5340 bmi270 spi no communication</title><link>https://devzone.nordicsemi.com/thread/554200?ContentTypeID=1</link><pubDate>Thu, 13 Nov 2025 04:09:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:18141070-42a1-4b61-b86d-5ff53e34038f</guid><dc:creator>SergeiA</dc:creator><description>&lt;p&gt;I got similar problem on Thingy:53. With very similar settings and same internal BMI270. What I see is bmi270 fails to initialize way before my code tries to use it, it is back in driver initialization. When driver attempts to init this sensor it reads deviceId, and in my case it is always 0, not what driver code expects. After that game is over, any call to device_is_ready() just checks flag that was set during driver initialization and return false. I traced system calls&amp;nbsp;before driver reads deviceId at the first time, and it seems that all SPI settings like mode, CS level, clock polarity, etc - are compatible with bmi270 specs. I had issues with other sensors because of that, but not in this case.&lt;/p&gt;
&lt;p&gt;I tried to find any Nordic sample that uses bmi270, nothing there. Edge Impulse firmware uses second internal accelerometer, not bmi270, it works for them, but I need gyro data.&lt;/p&gt;
&lt;p&gt;So my&amp;nbsp;request is: nice people in Nordic Semi, could you provide a simple working sample, that successfully reads data from bmi270?&lt;/p&gt;
&lt;p&gt;It could be useful for us to see, how to enable this sensor in overlay, what kind of config settings to use. I understand that bmi270 is really funky beast -- it requires loading 6kb of code into the chip, it could do this and that -- but I have it failed on the very first access, before all this. If it is broken, I could appreciate that you will tell it and we will stop wasting time on fixing it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;Sergei&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: thingy91x nrf5340 bmi270 spi no communication</title><link>https://devzone.nordicsemi.com/thread/553989?ContentTypeID=1</link><pubDate>Tue, 11 Nov 2025 14:18:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:79a68dc0-d55f-40fa-a79d-b2afbbb09435</guid><dc:creator>MartinPDU</dc:creator><description>&lt;p&gt;The&amp;nbsp;VDD_BMI270 @SB4&amp;nbsp;is 1.734V when running the code.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: thingy91x nrf5340 bmi270 spi no communication</title><link>https://devzone.nordicsemi.com/thread/553944?ContentTypeID=1</link><pubDate>Tue, 11 Nov 2025 10:22:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bcffdc7-566a-4614-83de-f48b887b5d1a</guid><dc:creator>MartinPDU</dc:creator><description>&lt;p&gt;What about the load switch for the bmi supply? How is it activated?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: thingy91x nrf5340 bmi270 spi no communication</title><link>https://devzone.nordicsemi.com/thread/553925?ContentTypeID=1</link><pubDate>Tue, 11 Nov 2025 08:55:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:80820c8d-a2a6-4919-bb4a-f7ef4c5fef0a</guid><dc:creator>MartinPDU</dc:creator><description>&lt;p&gt;Hi Benjamin,&lt;/p&gt;
&lt;p&gt;yes, we are talking about the onboard BMI270.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We can read out the BMI270 from the nrf9151 side. However, if we flash a blinky sample on the 9151 and try to read out the BMI270 via the nrf5340, it is not accessible as described.&lt;/p&gt;
&lt;p&gt;Is there possibly a problem with the 5340 device tree?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Martin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: thingy91x nrf5340 bmi270 spi no communication</title><link>https://devzone.nordicsemi.com/thread/553917?ContentTypeID=1</link><pubDate>Tue, 11 Nov 2025 08:17:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:322f0f69-ae0c-43da-9913-dba00fe66391</guid><dc:creator>Benjamin</dc:creator><description>&lt;p&gt;Hi Martin,&lt;br /&gt;Thanks for writing us, I assume you are talking about the onboard BMI270 or an external one?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Benjamin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>