<?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>Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116319/unable-to-flash-nrf5340-audio-dk-using-buildprog-script</link><description>I am working with the unicast samples where one board is configured as a server and the other as client. Initially i had trouble installing the SDK, but it seems to be working properly now. 
 I recently came up with this issue where the buildprog wont</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 18 Dec 2024 00:42:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116319/unable-to-flash-nrf5340-audio-dk-using-buildprog-script" /><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/515361?ContentTypeID=1</link><pubDate>Wed, 18 Dec 2024 00:42:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad08f1b4-1ee3-4fc4-8cdf-1f19cbb93618</guid><dc:creator>SNJY</dc:creator><description>&lt;p&gt;Okay, thanks. I&amp;#39;ll do that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/515234?ContentTypeID=1</link><pubDate>Tue, 17 Dec 2024 09:10:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f596523-1035-4aee-9a7f-b39a40c7cb7d</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Unfortunately, I don&amp;#39;t see any other option but to modify the buildprog script to support additional arguments.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/515203?ContentTypeID=1</link><pubDate>Mon, 16 Dec 2024 23:12:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b464479-b949-43a9-9b23-a5665ad43775</guid><dc:creator>SNJY</dc:creator><description>&lt;p&gt;Got it, Vidar.&lt;/p&gt;
&lt;p&gt;So how can i make this work? How can i have a custom conf file for each different board that i program using the buildprog script?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/514654?ContentTypeID=1</link><pubDate>Thu, 12 Dec 2024 07:50:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f6ace2d-a35d-4739-8ec4-eeeb07eec6d9</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;No problem. I&amp;#39;m glad to hear the issue was resolved after deleting the build folder. Unfortunately, the build script does not support passing additional&amp;nbsp;cmake arguments.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/514624?ContentTypeID=1</link><pubDate>Wed, 11 Dec 2024 23:25:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:11f013d4-0220-4d1a-8283-394e4952cf9b</guid><dc:creator>SNJY</dc:creator><description>&lt;p&gt;Hi Vidar,&lt;/p&gt;
&lt;p&gt;Sorry for the late response. I was finishing up my quarter and took a break. I am able to work with the buildprog script now. I cleaned the existing build files and mostly there was some broken link which was creating problems.&lt;/p&gt;
&lt;p&gt;It works now but i wanted to know&amp;nbsp;one more thing.&lt;/p&gt;
&lt;p&gt;I have two seperate conf files that i have created for different boards. when using west build command, I can specifiy the conf file as an argument. Is the same handled with the buildprog script, If so, how do i use it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/510886?ContentTypeID=1</link><pubDate>Mon, 18 Nov 2024 12:58:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b13c651c-1b60-4bba-b712-12ad95ac1ad7</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Thanks for confirming. Please also make sure that sysbuild is enabled by default in your west workspace (&lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/config_and_build/config_and_build_system.html#sysbuild_enabled_by_default"&gt;https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/config_and_build/config_and_build_system.html#sysbuild_enabled_by_default&lt;/a&gt; ).&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/510861?ContentTypeID=1</link><pubDate>Mon, 18 Nov 2024 09:46:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4883ed8b-e2bc-44aa-b8f3-c1bd273885e0</guid><dc:creator>SNJY</dc:creator><description>&lt;p&gt;I am currently using SDK ver 0.16.5 and v2.7.0 toolchain&lt;/p&gt;
&lt;p&gt;The trace for the net core hex path that gets printed is as below:&lt;/p&gt;
&lt;p&gt;Net core hex path {} /Users/sanjayvarghese/Documents/waveworks/mhm_ble_prototype/build/dev_headset/build_debug/merged_CPUNET.hex&lt;br /&gt;Net core hex path {} /Users/sanjayvarghese/Documents/waveworks/mhm_ble_prototype/build/dev_gateway/build_debug/merged_CPUNET.hex&lt;br /&gt;NET core hex not found. Built as APP core child image.&lt;br /&gt;NET core hex not found. Built as APP core child image.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/510453?ContentTypeID=1</link><pubDate>Thu, 14 Nov 2024 11:22:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2be8b735-2c5d-44da-9a70-2a46e294a646</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;It&amp;#39;s strange that the path.is_file() check is failing. Are you able to share the path to the hex file that was printed? It would also be helpful to know which SDK version you are using.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/510371?ContentTypeID=1</link><pubDate>Wed, 13 Nov 2024 20:00:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46c2d0ef-2ef0-4afb-9357-03cee6c56c71</guid><dc:creator>SNJY</dc:creator><description>&lt;p&gt;I already tried deleting build folder for a clean rebuild, but that didnt help.&lt;/p&gt;
&lt;p&gt;And I tried printing the path. The path seems correct. Hex files are inside their respective configurations inside the build folder that buildprog creates.&lt;/p&gt;
&lt;p&gt;It seems to work just fine&amp;nbsp;on the command line. I use west to build and flash the project.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to flash nrf5340 audio dk using Buildprog script</title><link>https://devzone.nordicsemi.com/thread/510348?ContentTypeID=1</link><pubDate>Wed, 13 Nov 2024 15:58:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c1beb52c-6a93-4be2-832a-79736362e931</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I wouldn&amp;#39;t expect the VS Code extension update to affect anything as this application is built from the command line. Have you tried deleting the build folder to see if a clean rebuild fixes the problem? Another troubleshooting step is to print the hex file path in the program.py script to&amp;nbsp;check where it expects to find the hex file.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1731513491227v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>