<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-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>Nordic Q&amp;amp;A - Recent Threads</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a</link><description>Nordic Tech Support - private tickets and public Q&amp;amp;A</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Thu, 11 Jun 2026 11:34:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a" /><item><title>Certificate issue</title><link>https://test-devzone.nordicsemi.com/thread/89131?ContentTypeID=0</link><pubDate>Thu, 11 Jun 2026 11:34:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4d904c73-9fa2-40e3-aff4-140913392d38</guid><dc:creator>tomasz</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89131?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89131/certificate-issue/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We have onboarded several hundred nrRF9151 devices using the nRF Cloud &amp;quot;bulk onboard&amp;quot;&amp;nbsp;UI (preconnect onboarding&amp;nbsp;using&amp;nbsp;&lt;span lang="EN-US"&gt;&lt;span&gt;device_credentials_installer.py&lt;/span&gt;&lt;/span&gt;). Generally, this works fine.&lt;/p&gt;
&lt;p&gt;However, for two devices we are getting an error during onboarding: &amp;quot;certificate already exists&amp;quot;. But the respective devices (UUID) are not present in nRF Cloud in any of our teams.&lt;/p&gt;
&lt;p&gt;We&amp;#39;re not sure why this is happening and&amp;nbsp;how to resolve the situation and finish onboarding the two devices.&lt;/p&gt;
&lt;p&gt;Any advice is appreciated.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Device onboarding: "certificate already exists"</title><link>https://test-devzone.nordicsemi.com/thread/89130?ContentTypeID=0</link><pubDate>Tue, 17 Mar 2026 15:15:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c6ba9a6e-89b3-4594-83cf-22d6a8b818c6</guid><dc:creator>tomasz</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89130?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89130/device-onboarding-certificate-already-exists/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We have onboarded several hundred nrRF9151 devices using the nRF Cloud &amp;quot;bulk onboard&amp;quot;&amp;nbsp;UI (preconnect onboarding&amp;nbsp;using&amp;nbsp;&lt;span lang="EN-US"&gt;&lt;span&gt;device_credentials_installer.py&lt;/span&gt;&lt;/span&gt;). Generally, this works fine.&lt;/p&gt;
&lt;p&gt;However, for two devices we are getting an error during onboarding: &amp;quot;certificate already exists&amp;quot;. But the respective devices (UUID) are not present in nRF Cloud in any of our teams.&lt;/p&gt;
&lt;p&gt;We&amp;#39;re not sure why this is happening and&amp;nbsp;how to resolve the situation and finish onboarding the two devices.&lt;/p&gt;
&lt;p&gt;Any advice is appreciated.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?</title><link>https://test-devzone.nordicsemi.com/thread/89129?ContentTypeID=0</link><pubDate>Mon, 16 Mar 2026 11:15:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30a26a45-dda5-4fd3-9a6c-111cd435a3a5</guid><dc:creator>tomasz</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89129?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89129/i-would-like-to-add-ble_advdata_manuf_data_t-to-gatt-when-proxy-enabled-where-should-it-be-placed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I would like to add some extra data to mesh-nodes, when not provisioned -- with&amp;nbsp;ble_advdata_manuf_data_t usage. What is the best way to do it and where?&lt;/p&gt;
&lt;p&gt;And, in case I would like to add&amp;nbsp;ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?&lt;/p&gt;
&lt;p&gt;Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>test</title><link>https://test-devzone.nordicsemi.com/thread/89128?ContentTypeID=0</link><pubDate>Mon, 16 Mar 2026 11:07:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd9b0318-ed04-42df-86cb-d77e4d051440</guid><dc:creator>tomasz</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89128?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89128/test/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;How can I get nordicsemi prodducts?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Help!</title><link>https://test-devzone.nordicsemi.com/thread/89127?ContentTypeID=0</link><pubDate>Wed, 11 Mar 2026 12:49:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b70c2edc-853b-4f56-8449-33860639fa39</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89127?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89127/help/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;my nRF54 is not transmitting BLE. Help me you dofus!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?</title><link>https://test-devzone.nordicsemi.com/thread/89126?ContentTypeID=0</link><pubDate>Tue, 10 Mar 2026 12:46:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aea35915-6078-4302-834f-a0f82f58d948</guid><dc:creator>Russ</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89126?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89126/i-would-like-to-add-ble_advdata_manuf_data_t-to-gatt-when-proxy-enabled-where-should-it-be-placed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I would like to add some extra data to mesh-nodes, when not provisioned -- with&amp;nbsp;ble_advdata_manuf_data_t usage. What is the best way to do it and where?&lt;/p&gt;
&lt;p&gt;And, in case I would like to add&amp;nbsp;ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?&lt;/p&gt;
&lt;p&gt;Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?</title><link>https://test-devzone.nordicsemi.com/thread/89125?ContentTypeID=0</link><pubDate>Tue, 10 Mar 2026 12:46:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b12993a-17bb-47f8-8f65-5a6f1e3d429b</guid><dc:creator>Russ</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89125?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89125/i-would-like-to-add-ble_advdata_manuf_data_t-to-gatt-when-proxy-enabled-where-should-it-be-placed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I would like to add some extra data to mesh-nodes, when not provisioned -- with&amp;nbsp;ble_advdata_manuf_data_t usage. What is the best way to do it and where?&lt;/p&gt;
&lt;p&gt;And, in case I would like to add&amp;nbsp;ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?&lt;/p&gt;
&lt;p&gt;Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>What should I do to run blinky sample on nRF52840 DK</title><link>https://test-devzone.nordicsemi.com/thread/89124?ContentTypeID=0</link><pubDate>Tue, 03 Mar 2026 15:34:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1537fb32-a8c6-4fb8-ab29-c73c2a65dc15</guid><dc:creator>tomasz</dc:creator><slash:comments>1</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89124?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89124/what-should-i-do-to-run-blinky-sample-on-nrf52840-dk/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;As in the question&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>What is love?</title><link>https://test-devzone.nordicsemi.com/thread/89123?ContentTypeID=0</link><pubDate>Tue, 03 Mar 2026 12:50:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4bb22825-3b4f-4814-a7ba-35a799f54219</guid><dc:creator>tomasz</dc:creator><slash:comments>1</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89123?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89123/what-is-love/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Test of love&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>My test</title><link>https://test-devzone.nordicsemi.com/thread/89122?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 12:17:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6366be54-bd85-4770-b9cb-fb23319fd763</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89122?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89122/my-test/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Any PMIC suitable for this product?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>asd</title><link>https://test-devzone.nordicsemi.com/thread/89121?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 12:13:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2db95c38-3510-4898-9a01-75ba5c54252e</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89121?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89121/asd/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Any help on this code?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;print(&amp;#39;Hello&amp;#39;);&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Another test</title><link>https://test-devzone.nordicsemi.com/thread/89120?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 11:52:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bfab8d43-0acd-4dc3-9328-3a90b1d49a5e</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89120?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89120/another-test/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;How to start using nRF52840?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Please help!!</title><link>https://test-devzone.nordicsemi.com/thread/89119?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 11:52:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:beface78-347e-43f4-90f4-e4a7cac42577</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89119?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89119/please-help/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;How to start with VS Code?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Please help!!</title><link>https://test-devzone.nordicsemi.com/thread/89118?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 11:51:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5419e391-9bd1-4291-929d-f985542f5e05</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89118?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89118/please-help/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;How to start with VS Code?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Testing AI</title><link>https://test-devzone.nordicsemi.com/thread/89117?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 11:34:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d5880f49-98ce-45b7-b5a0-2fd91ae5a275</guid><dc:creator>admin</dc:creator><slash:comments>1</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89117?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89117/testing-ai/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;How to start with VS Code?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Help</title><link>https://test-devzone.nordicsemi.com/thread/89116?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 11:23:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:78652a0b-63e7-469a-b733-211cfad4dd15</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89116?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89116/help/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;How to get started with nRF54L15?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>another try 123</title><link>https://test-devzone.nordicsemi.com/thread/89115?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 10:44:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:95cf29c6-b6e5-451c-a993-4dbfb5431181</guid><dc:creator>neeraj.jain+dev1</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89115?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89115/another-try-123/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I would like to ask you for your opinion, although it is not directly Nordic related, but indirectly, it is. The following:&lt;/p&gt;
&lt;p&gt;The customer ICP (Holten, The Netherlands) designed a system based around a Raytac BLE module, the MDBT50Q-1MV2. The customer is running the certification tests and is running in to problems with the end product. The radiated power is too high on one of the harmonic side channels, so the customer suspects the Raytac module (although, this one does have passed all certifications for CE, FCC, and more).&lt;/p&gt;
&lt;p&gt;The ICP product is tested for FCC compliancy at Telefication (authorized test and certification company). The reason for this is that the MDBT50Q-1MV2 already does have an FCC ID. Because of that, a minimum test and measurement procedure can be executed to verify whether the ICP board is still compliant with the FCC rules or not.&lt;/p&gt;
&lt;p&gt;Since the ICP end product failed the test, the customer took the Raytac development board to verify the emission of this one, and surprisingly this board shows the same behavior compared to the customer board. As well the Raytac evaluation board is fully certified. See the results in the&amp;nbsp; document: Emission Development Board.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>qwqwqwqw</title><link>https://test-devzone.nordicsemi.com/thread/89114?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 10:40:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5260528a-036e-4fcb-ac8a-7def6a7a44f1</guid><dc:creator>neeraj.jain+dev1</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89114?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89114/qwqwqwqw/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I would like to ask you for your opinion, although it is not directly Nordic related, but indirectly, it is. The following:&lt;/p&gt;
&lt;p&gt;The customer ICP (Holten, The Netherlands) designed a system based around a Raytac BLE module, the MDBT50Q-1MV2. The customer is running the certification tests and is running in to problems with the end product. The radiated power is too high on one of the harmonic side channels, so the customer suspects the Raytac module (although, this one does have passed all certifications for CE, FCC, and more).&lt;/p&gt;
&lt;p&gt;The ICP product is tested for FCC compliancy at Telefication (authorized test and certification company). The reason for this is that the MDBT50Q-1MV2 already does have an FCC ID. Because of that, a minimum test and measurement procedure can be executed to verify whether the ICP board is still compliant with the FCC rules or not.&lt;/p&gt;
&lt;p&gt;Since the ICP end product failed the test, the customer took the Raytac development board to verify the emission of this one, and surprisingly this board shows the same behavior compared to the customer board. As well the Raytac evaluation board is fully certified. See the results in the&amp;nbsp; document: Emission Development Board.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Since the ICP end product</title><link>https://test-devzone.nordicsemi.com/thread/89113?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 10:08:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9de64120-65a0-4670-a34f-5e74c34c36e1</guid><dc:creator>neeraj.jain+dev1</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89113?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89113/since-the-icp-end-product/rss?ContentTypeId=0</wfw:commentRss><description>&lt;div&gt;
&lt;p&gt;this is a deflector test&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;I would like to ask you for your opinion, although it is not directly Nordic related, but indirectly, it is. The following:&lt;/p&gt;
&lt;p&gt;The customer ICP (Holten, The Netherlands) designed a system based around a Raytac BLE module, the MDBT50Q-1MV2. The customer is running the certification tests and is running in to problems with the end product. The radiated power is too high on one of the harmonic side channels, so the customer suspects the Raytac module (although, this one does have passed all certifications for CE, FCC, and more).&lt;/p&gt;
&lt;p&gt;The ICP product is tested for FCC compliancy at Telefication (authorized test and certification company). The reason for this is that the MDBT50Q-1MV2 already does have an FCC ID. Because of that, a minimum test and measurement procedure can be executed to verify whether the ICP board is still compliant with the FCC rules or not.&lt;/p&gt;
&lt;p&gt;Since the ICP end product failed the test, the customer took the Raytac development board to verify the emission of this one, and surprisingly this board shows the same behavior compared to the customer board. As well the Raytac evaluation board is fully certified. See the results in the&amp;nbsp; document: Emission Development Board.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>sasaas</title><link>https://test-devzone.nordicsemi.com/thread/89112?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 10:02:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf0a69d7-a3c4-4174-94e1-829f5e473192</guid><dc:creator>neeraj.jain+dev1</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89112?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89112/sasaas/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;a#fragment-337_save&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>test deflector 1</title><link>https://test-devzone.nordicsemi.com/thread/89111?ContentTypeID=0</link><pubDate>Mon, 02 Mar 2026 09:17:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:96de2869-bafb-485e-b871-966e757a05fd</guid><dc:creator>neeraj.jain+dev1</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89111?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89111/test-deflector-1/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;this is a deflector test&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Build fails when enabling SQSPI in Device Tree (with MCUBoot)</title><link>https://test-devzone.nordicsemi.com/thread/89110?ContentTypeID=0</link><pubDate>Wed, 25 Feb 2026 17:12:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee406632-31a4-40c2-b5fa-46e7e9c655cc</guid><dc:creator>tomasz</dc:creator><slash:comments>1</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89110?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89110/build-fails-when-enabling-sqspi-in-device-tree-with-mcuboot/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi, &lt;br /&gt;I’m seeing a build failure after enabling SQSPI in the device tree when building with MCUBoot on NCS v3.2.1 for nRF54L15.&lt;br /&gt;&lt;br /&gt; The build works fine without SQSPI, but once it’s enabled the link step fails.&amp;nbsp;&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;In function &amp;#39;nrf_sqspi_init&amp;#39;,
    inlined from &amp;#39;dev_init&amp;#39; at /opt/nordic/ncs/v3.2.1/nrf/drivers/mspi/mspi_sqspi.c:513:8:
/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/src/nrf_sqspi.c:164:9: warning: &amp;#39;memcpy&amp;#39; reading 14144 bytes from a region of size 12088 [-Wstringop-overread]
  164 |         memcpy((void *)vpr_init_pc, nvm_fw_addr, meta-&amp;gt;fw_code_size &amp;lt;&amp;lt; 4);
      |         ^
/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/include/nrf54l/sqspi_firmware_v1.2.1.h: In function &amp;#39;dev_init&amp;#39;:
/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/include/nrf54l/sqspi_firmware_v1.2.1.h:12:15: note: source object &amp;#39;sqspi_firmware_bin&amp;#39; of size 12088
   12 | const uint8_t sqspi_firmware_bin[] = {
      |               ^
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `done_callback&amp;#39;:
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_dev_config&amp;#39;:
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o:/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o:/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_get_channel_status&amp;#39;:
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_transceive&amp;#39;:
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `dev_init&amp;#39;:
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init&amp;#39;
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init&amp;#39;
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
[15/20] Generating ../dfu_application.zip
FAILED: _sysbuild/sysbuild/images/bootloader/mcuboot-prefix/src/mcuboot-stamp/mcuboot-build /Users/ghazifaisal/github/project/build/_sysbuild/sysbuild/images/bootloader/mcuboot-prefix/src/mcuboot-stamp/mcuboot-build 
cd /Users/ghazifaisal/github/project/build/mcuboot &amp;amp;&amp;amp; /opt/nordic/ncs/toolchains/561dce9adf/Cellar/cmake/3.21.0/bin/cmake --build .
ninja: build stopped: subcommand failed.&lt;/pre&gt;&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Build fails when enabling SQSPI in Device Tree (with MCUBoot)</title><link>https://test-devzone.nordicsemi.com/thread/89109?ContentTypeID=0</link><pubDate>Wed, 25 Feb 2026 17:10:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e85c22d1-09d0-455e-ac93-ad136dd5c8ab</guid><dc:creator>tomasz</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89109?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89109/build-fails-when-enabling-sqspi-in-device-tree-with-mcuboot/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi, &lt;br /&gt;I’m seeing a build failure after enabling SQSPI in the device tree when building with MCUBoot on NCS v3.2.1 for nRF54L15.&lt;br /&gt;&lt;br /&gt; The build works fine without SQSPI, but once it’s enabled the link step fails.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In function &amp;#39;nrf_sqspi_init&amp;#39;,&lt;br /&gt;&amp;nbsp; &amp;nbsp; inlined from &amp;#39;dev_init&amp;#39; at /opt/nordic/ncs/v3.2.1/nrf/drivers/mspi/mspi_sqspi.c:513:8:&lt;br /&gt;/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/src/nrf_sqspi.c:164:9: warning: &amp;#39;memcpy&amp;#39; reading 14144 bytes from a region of size 12088 [-Wstringop-overread]&lt;br /&gt;&amp;nbsp; 164 |&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;memcpy((void *)vpr_init_pc, nvm_fw_addr, meta-&amp;gt;fw_code_size &amp;lt;&amp;lt; 4);&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; |&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;^&lt;br /&gt;/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/include/nrf54l/sqspi_firmware_v1.2.1.h: In function &amp;#39;dev_init&amp;#39;:&lt;br /&gt;/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/include/nrf54l/sqspi_firmware_v1.2.1.h:12:15: note: source object &amp;#39;sqspi_firmware_bin&amp;#39; of size 12088&lt;br /&gt;&amp;nbsp; &amp;nbsp;12 | const uint8_t sqspi_firmware_bin[] = {&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; |&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;^&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `done_callback&amp;#39;:&lt;br /&gt;/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_dev_config&amp;#39;:&lt;br /&gt;/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o:/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o:/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_get_channel_status&amp;#39;:&lt;br /&gt;/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_transceive&amp;#39;:&lt;br /&gt;/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `dev_init&amp;#39;:&lt;br /&gt;/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init&amp;#39;&lt;br /&gt;/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init&amp;#39;&lt;br /&gt;collect2: error: ld returned 1 exit status&lt;br /&gt;ninja: build stopped: subcommand failed.&lt;br /&gt;[15/20] Generating ../dfu_application.zip&lt;br /&gt;FAILED: _sysbuild/sysbuild/images/bootloader/mcuboot-prefix/src/mcuboot-stamp/mcuboot-build /Users/ghazifaisal/github/project/build/_sysbuild/sysbuild/images/bootloader/mcuboot-prefix/src/mcuboot-stamp/mcuboot-build&amp;nbsp;&lt;br /&gt;cd /Users/ghazifaisal/github/project/build/mcuboot &amp;amp;&amp;amp; /opt/nordic/ncs/toolchains/561dce9adf/Cellar/cmake/3.21.0/bin/cmake --build .&lt;br /&gt;ninja: build stopped: subcommand failed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>VSCode doesn't list the connected devices although nrfutil device can list them</title><link>https://test-devzone.nordicsemi.com/thread/89108?ContentTypeID=0</link><pubDate>Wed, 25 Feb 2026 17:01:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:51b0de6a-beae-494c-bc64-080412eacad1</guid><dc:creator>tomasz</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89108?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89108/vscode-doesn-t-list-the-connected-devices-although-nrfutil-device-can-list-them/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi all,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Note that I am using a Fedora Workstation VM on VirtualBox for keeping everything clean. I pass the connected USB development board to the VM. I am trying to evaluate the Channel Sounding functionality with&amp;nbsp;some Seeed nRF54L15 XIAO modules. I am using VSCode, I&amp;#39;ve installed the extension and everything without a problem, I&amp;#39;ve assembled a test project for both Initiator and Reflector based on your individual projects and I&amp;#39;ve hooked up the device. Unfortunately the device doesn&amp;#39;t show in the Connected Devices list, although when opening a console and using &lt;strong&gt;nrfutil device list&lt;/strong&gt; it lists the connected device. I&amp;#39;ve done everything (or so I believe) that was needed, I have installed openocd, jlink, added the USB rules, installed the nrfutil and the device command in my local (logged user) bin and yet, the devices do not appear in the list. As you can see from the screenshot below, the device can be listed with the nrfutil via the terminal (both the internal vscode and a normal terminal) but when pressing the refresh button in the Connected Devices, nothing happens. I see from the Output that it is starting the nrfutil but there is no error. Any ideas what could be the problem?&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:978px;max-width:978px;" src="https://test-devzone.nordicsemi.com/resized-image/__size/1956x1956/__key/communityserver-discussions-components-files/4/pastedimage1772038842385v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://test-devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1772038855900v2.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Replacement for pynrfjprog in NCS 3.0.1</title><link>https://test-devzone.nordicsemi.com/thread/89107?ContentTypeID=0</link><pubDate>Wed, 25 Feb 2026 16:55:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1c419d5-aa66-4045-b62a-a827a9e2c6a3</guid><dc:creator>tomasz</dc:creator><slash:comments>0</slash:comments><comments>https://test-devzone.nordicsemi.com/thread/89107?ContentTypeID=0</comments><wfw:commentRss>https://test-devzone.nordicsemi.com/f/nordic-q-a/89107/replacement-for-pynrfjprog-in-ncs-3-0-1/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;With the release of NCS 3.0.1, the required SEGGER JLink version to v8.18. pynrfjrprog is bundled with SEGGER JLink v7.94. From your website, it seems nrfjprog, being part of the nordic command line tools, has been replaced by nrfutil (which seems to be mainly for nrf5-sdk? &lt;a href="https://www.nordicsemi.com/Products/Development-tools/nRF-Util"&gt;https://www.nordicsemi.com/Products/Development-tools/nRF-Util&lt;/a&gt; ).&lt;/p&gt;
&lt;p&gt;I really like pynrfjprog. Is there a replacement python library based on nrfutil which I can use with NCS 3.0.1?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Fridtjof&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>