<?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>Building modified code then flashing with ninja flash flashes the old version of the application in a multi-image build</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/74809/building-modified-code-then-flashing-with-ninja-flash-flashes-the-old-version-of-the-application-in-a-multi-image-build</link><description>This has been happening for a very long time when building nRF connect SDK applications on a windows 10 machine via the command line with cmake and ninja. In an application whereby it only runs on one core e.g. application core, if a program is built</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 May 2021 11:05:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/74809/building-modified-code-then-flashing-with-ninja-flash-flashes-the-old-version-of-the-application-in-a-multi-image-build" /><item><title>RE: Building modified code then flashing with ninja flash flashes the old version of the application in a multi-image build</title><link>https://devzone.nordicsemi.com/thread/309962?ContentTypeID=1</link><pubDate>Mon, 17 May 2021 11:05:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:608b0b51-95f6-484b-a78b-e218db8b5d2b</guid><dc:creator>Torsten Rasmussen</dc:creator><description>&lt;p&gt;This should be fixed here.&lt;br /&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrf/pull/4558"&gt;https://github.com/nrfconnect/sdk-nrf/pull/4558&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If you have the time, it would be great if you can verify that this is fixing the exact issue you are experiencing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Building modified code then flashing with ninja flash flashes the old version of the application in a multi-image build</title><link>https://devzone.nordicsemi.com/thread/309715?ContentTypeID=1</link><pubDate>Fri, 14 May 2021 08:23:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41eeac78-838b-4bb1-b7b4-e3f68922cb72</guid><dc:creator>Carl Richard</dc:creator><description>&lt;p&gt;Thank you, Jamie! We have reproduced this on our side and are investigating. I&amp;#39;ll report back to you as soon as I know more. Thank you for your patience!&lt;br /&gt;&lt;br /&gt;Could you try to use the &amp;quot;west&amp;quot; tool instead and see if the same issues are present for you there? Version 0.11 was recently released, so you might need to update it.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Carl Richard&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Building modified code then flashing with ninja flash flashes the old version of the application in a multi-image build</title><link>https://devzone.nordicsemi.com/thread/308646?ContentTypeID=1</link><pubDate>Fri, 07 May 2021 07:15:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf11f606-12e2-4cd5-bb99-ceb2d90c4acd</guid><dc:creator>jm_laird</dc:creator><description>&lt;p&gt;Hi Carl,&lt;/p&gt;
&lt;p&gt;Sure. I just got the latest version by using: west init -m &lt;a href="https://github.com/nrfconnect/sdk-nrf"&gt;github.com/.../sdk-nrf&lt;/a&gt; --mr master&lt;/p&gt;
&lt;p&gt;I then used zephyr\samples\bluetooth\peripheral_csc as a sample app, built as follows:&lt;br /&gt;set GNUARMEMB_TOOLCHAIN_PATH=C:\gcc-arm&lt;br /&gt;set ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb&lt;br /&gt;zephyr-env.cmd&lt;br /&gt;cd samples\bluetooth\peripheral_csc&lt;br /&gt;mkdir build&lt;br /&gt;cd build&lt;br /&gt;cmake -GNinja -DBOARD=nrf5340dk_nrf5340_cpuapp ..&lt;br /&gt;ninja&lt;/p&gt;
&lt;p&gt;I flashed it to the board using: ninja flash, it ran as expected.&lt;/p&gt;
&lt;p&gt;I then changed the main.c file to add this in main(): printk(&amp;quot;boom\n&amp;quot;);&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;I then built it again using ninja and flashed using ninja flash and the output was as follows:&lt;br /&gt;*** Booting Zephyr OS build v2.4.99-ncs1-3519-g5585355dde0c ***&lt;br /&gt;Bluetooth initialized&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;Advertising successfully started&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;The output is not there, so I verified it using nrfjprog:&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;nrfjprog -f NRF53 --verify .\zephyr.hex&lt;br /&gt;Parsing image file.&lt;br /&gt;Verifying programming.&lt;br /&gt;ERROR: Write verify failed.&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;I then erased all the .hex files in the zephyr directory, did ninja and ninja flash again and the output was:&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;*** Booting Zephyr OS build v2.4.99-ncs1-3519-g5585355dde0c ***&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;Bluetooth initialized&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;Advertising successfully started&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;boom&lt;/p&gt;
&lt;p style="margin:0px;text-indent:0px;"&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br /&gt;Jamie&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Building modified code then flashing with ninja flash flashes the old version of the application in a multi-image build</title><link>https://devzone.nordicsemi.com/thread/308580?ContentTypeID=1</link><pubDate>Thu, 06 May 2021 14:22:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d8d4829-45c7-45f8-a55b-8cb6e170375f</guid><dc:creator>Carl Richard</dc:creator><description>&lt;p&gt;Hello!&lt;br /&gt;&lt;br /&gt;Thanks for reaching out.&amp;nbsp;This is very similar to a known bug that we&amp;#39;re working on getting fixed. Though, I haven&amp;#39;t seen it happening with ninja+cmake, only with the &amp;quot;west&amp;quot; tool, so this is interesting. I will report your findings internally. Could you describe the procedure exactly (the chain of commands), so that I can try to reproduce?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Carl Richard&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>