https://devzone.nordicsemi.com/f/nordic-q-a/110338/issue-with-matter-template-code-in-nrf-connect-sdk-v2-6-0-on-custom-boardI&#39;m encountering an issue with the Matter template code in nRF Connect SDK v2.6.0 on my custom board. Strangely, the same code runs perfectly fine on my board when using the example code from the previous SDK version, v2.4.0. In my debugging, I&#39;ve observeden-USTelligent Community 13Mon, 22 Apr 2024 10:06:06 GMThttps://devzone.nordicsemi.com/thread/479945?ContentTypeID=1Mon, 22 Apr 2024 10:06:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9e99719a-b9cb-43a2-837a-bffc5a988329Ashique<div> <div><span># Disable Matter OTA DFU</span></div> <div><span>CONFIG_CHIP_OTA_REQUESTOR</span><span>=n</span></div> <div><span></span></div> </div> <p>Adding the configuration to the prj.conf file resolved the issue. However, I&#39;m curious to understand why this adjustment was necessary for the newer version of the SDK.</p> <p>Could you provide an explanation or insight into why adding this configuration made the code work on my custom board with nRF Connect SDK v2.6.0, while it was unnecessary for older versions like v2.4.0?</p> <p>Understanding the underlying reasons would be valuable for further development and troubleshooting.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/479848?ContentTypeID=1Mon, 22 Apr 2024 05:33:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:14c16caf-a3e5-458d-a39e-ef69a273020eAshique<p><span>Furthermore, I&#39;ve observed that older versions of the template work perfectly on my custom board. Specifically, the Matter template code below the nRF Connect SDK 2.4.0 functions properly.</span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/479721?ContentTypeID=1Fri, 19 Apr 2024 13:14:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:518b3b0e-2485-45dc-82dd-e6fab12745afAmanda Hsieh<p>Hi,&nbsp;</p> <p>I would suggest you create a new support case for board design review.</p> <p>-Amanda H.&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/479580?ContentTypeID=1Fri, 19 Apr 2024 04:33:42 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bd825830-ce0f-4416-b734-e281107fa695Ashique<p>Thank you for your response.</p> <p>I appreciate your suggestions. However, I&#39;d like to provide some additional information. I have not made any changes to the example code provided in the nRF Connect SDK v2.6.0. There have been no configuration alterations or partition changes either. My custom board is based on the nRF52840 chip, and it does not utilize any external flash via SPI or QSPI</p> <p>Interestingly, the code runs perfectly fine on the nRF52840 Development Kit (DK). However, on my custom board, it seems to be stuck in the bootloader without transitioning to the application image.</p> <p>I hope this additional information helps in diagnosing the issue further.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/479555?ContentTypeID=1Thu, 18 Apr 2024 21:14:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b6528928-c7d5-44cf-8c84-0e37fceb2eaaAmanda Hsieh<p>Hi,&nbsp;</p> <p>Do you use a&nbsp;<span>static partition file&nbsp;</span>like this&nbsp;<a title="pm_static_nrf52840dk_nrf52840.yml" href="https://github.com/nrfconnect/sdk-nrf/blob/main/samples/matter/template/pm_static_nrf52840dk_nrf52840.yml">pm_static_nrf52840dk_nrf52840.yml</a>?</p> <p>Does your custom board use the external flash? via SPI or QSPI?</p> <p>Is it nRF52840 or nRF5340 on your custom board?</p> <p>Are you able to reproduce the issue on nRF52840DK?</p> <p>Regards,<br />Amanda H.</p><div style="clear:both;"></div>