<?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>How to configure FOAT function for LE Audio project</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116646/how-to-configure-foat-function-for-le-audio-project</link><description>I am developing the LE Audio feature for nrf5340. My project is based on nrf5340_audio demo, base on NCS 2.7.0. I am not very familiar with sysbuild. In NCS2.4.0, I am able to configure FOTA functionality correctly through Python scripts. But on 2.7.0</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 06 Dec 2024 14:18:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116646/how-to-configure-foat-function-for-le-audio-project" /><item><title>RE: How to configure FOAT function for LE Audio project</title><link>https://devzone.nordicsemi.com/thread/513849?ContentTypeID=1</link><pubDate>Fri, 06 Dec 2024 14:18:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:779316f1-40ec-4caa-b91e-6333391fd00f</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Hello, &lt;/p&gt;
&lt;p&gt;I returned to this again today and had another read through the previous replies to see if I had missed anything. This part caught my attention:&lt;/p&gt;
[quote user="huniu"]&lt;p&gt;When I burn the program using the following command:&lt;/p&gt;
&lt;p&gt;nrfjprog -- program build/dfu/merge. hex -- coprocessor CP_APPLICATION -- chiperase - r&lt;/p&gt;[/quote]
&lt;p&gt;You don&amp;#39;t mention flashing the network core. Do you flash it before the application core? The application core has the peripherals which you use for external flash, so this should still be ok. Just as a sanity check, can you use west to flash both cores on your board?&lt;/p&gt;
&lt;p&gt;Can you also confirm that the external flash is registered in the &lt;em&gt;chosen&lt;/em&gt; node in the generated zephyr.dts for the application image as well?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Maria&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to configure FOAT function for LE Audio project</title><link>https://devzone.nordicsemi.com/thread/513320?ContentTypeID=1</link><pubDate>Wed, 04 Dec 2024 02:06:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47819805-1e16-47ff-b66f-f5ef00f611b8</guid><dc:creator>huniu</dc:creator><description>&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/pastedimage1733277734510v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;This is all the logs。&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to configure FOAT function for LE Audio project</title><link>https://devzone.nordicsemi.com/thread/513266?ContentTypeID=1</link><pubDate>Tue, 03 Dec 2024 15:55:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b50369b4-ba78-4daf-99dc-c9c9a9fd7ed6</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Sorry to hear that.&lt;/p&gt;
[quote user="huniu"]&lt;p&gt;nrfjprog -- program build/dfu/merge. hex -- coprocessor CP_APPLICATION -- chiperase - r&lt;br /&gt;I received this error in the log:&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Failed to open flash area ID 1 (image 0 slot 1): -19, cannot continue&lt;/p&gt;[/quote]
&lt;p&gt;Is this the only error appearing in the log?&lt;/p&gt;
&lt;p&gt;Can you share more or all of the device log with us? If you can I will forward the information internally to get some assistance from our experts.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Maria&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to configure FOAT function for LE Audio project</title><link>https://devzone.nordicsemi.com/thread/513174?ContentTypeID=1</link><pubDate>Tue, 03 Dec 2024 11:16:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d00808fd-1c7d-4391-9cae-a571120531c1</guid><dc:creator>huniu</dc:creator><description>&lt;p&gt;&lt;br /&gt;I tried your suggestion, but it didn&amp;#39;t change anything&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to configure FOAT function for LE Audio project</title><link>https://devzone.nordicsemi.com/thread/512816?ContentTypeID=1</link><pubDate>Fri, 29 Nov 2024 16:25:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb03e417-c67c-482e-a524-ec6d3b6314c7</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Thank you for your patience.&lt;/p&gt;
&lt;p&gt;In the generated configuration file for your project, is CONFIG_SECURE_BOOT set? If it is, try to also disable SB_CONFIG_SECURE_BOOT_APPCORE. &lt;/p&gt;
&lt;p&gt;Adding &lt;code&gt;--qspieraseall&lt;/code&gt; to the programming command to erase the external memory can also help.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Maria&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to configure FOAT function for LE Audio project</title><link>https://devzone.nordicsemi.com/thread/512085?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2024 11:23:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:91ccad4e-617b-45a1-8686-4c2990c05821</guid><dc:creator>huniu</dc:creator><description>&lt;p&gt;During the waiting period for a response, I read the link you mentioned and made some attempts.&lt;br /&gt;Firstly, I would like to clarify that I did not use &lt;span&gt;nrf5340_audio_dk&lt;/span&gt;, but our own hardware.&lt;br /&gt;There is no 32K crystal oscillator on the hardware, and it&amp;nbsp;have external flash. Here is the schematic diagram of our flash and my configuration in DTS.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&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/pastedimage1732619239319v1.png" alt=" " /&gt;&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/pastedimage1732619319044v2.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&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/pastedimage1732619900729v3.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I believe there is no problem with this configuration and hardware, as I configured the hardware in the same way in NCS2.4.0 and successfully completed the external flash upgrade function.&lt;br /&gt;Returning to 2.7.0, first I use this command to compile:&lt;/p&gt;
&lt;p&gt;west build -d build/dfu -b nrf5340_audio_dk/nrf5340/cpuapp --sysbuild -- -DFILE_SUFFIX=fota&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;In order to be compatible with my hardware, I have added the following two configurations in prj_fota.conf&lt;/p&gt;
&lt;p&gt;&lt;span data-slate-fragment="JTVCJTdCJTIydHlwZSUyMiUzQSUyMnBhcmFncmFwaCUyMiUyQyUyMmNoaWxkcmVuJTIyJTNBJTVCJTdCJTIyaWQlMjIlM0ElMjJlamxYRDJYT3B6JTIyJTJDJTIycGFyYUlkeCUyMiUzQTQlMkMlMjJzcmMlMjIlM0ElMjIlRTMlODAlODIlRTQlQjglQkElRTQlQkElODYlRTUlODUlQkMlRTUlQUUlQjklRTYlODglOTElRTclOUElODQlRTclQTElQUMlRTQlQkIlQjYlRUYlQkMlOEMlRTYlODglOTElRTUlOUMlQThwcmpfZm90YS5jb25mJUU1JUEyJTlFJUU1JThBJUEwJUU0JUJBJTg2JUU0JUI4JThCJUU5JTlEJUEyJUU0JUI4JUE0JUU0JUI4JUFBJUU5JTg1JThEJUU3JUJEJUFFJUVGJUJDJTlBQ09ORklHX0NMT0NLX0NPTlRST0xfTlJGX0szMlNSQ19YVEFMJTNEbiUyMiUyQyUyMmRzdCUyMiUzQSUyMkluJTIwb3JkZXIlMjB0byUyMGJlJTIwY29tcGF0aWJsZSUyMHdpdGglMjBteSUyMGhhcmR3YXJlJTJDJTIwSSUyMGhhdmUlMjBhZGRlZCUyMHRoZSUyMGZvbGxvd2luZyUyMHR3byUyMGNvbmZpZ3VyYXRpb25zJTIwaW4lMjBwcmpfZm90YWNvbmYlM0ElMjBWTmV0JTIwQ0xPQ0stQ09OQ0xfTlJGX0szMlNSQ19YVEFMJTNEbiUyMiUyQyUyMm1ldGFkYXRhJTIyJTNBJTIyJTIyJTJDJTIybWV0YURhdGElMjIlM0ElNUIlNUQlMkMlMjJ0ZXh0JTIyJTNBJTIyQ09ORklHX0NMT0NLX0NPTlRST0xfTlJGX0szMlNSQ19YVEFMJTNEbiUyMiU3RCU1RCU3RCU1RA=="&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n&lt;/span&gt;&lt;br /&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=y&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Afterwards, I found that there was not enough space in the protocol stack. Following a suggestion in a post, I turned off :&lt;span data-slate-fragment="JTVCJTdCJTIydHlwZSUyMiUzQSUyMnBhcmFncmFwaCUyMiUyQyUyMmNoaWxkcmVuJTIyJTNBJTVCJTdCJTIyaWQlMjIlM0ElMjJ6bjFYUG1YTXhWJTIyJTJDJTIycGFyYUlkeCUyMiUzQTYlMkMlMjJzcmMlMjIlM0ElMjIlRTQlQjklOEIlRTUlOTAlOEUlRTYlODglOTElRTUlOEYlOTElRTclOEUlQjAlRTUlOEQlOEYlRTglQUUlQUUlRTYlQTAlODglRTclOUElODQlRTclQTklQkElRTklOTclQjQlRTQlQjglOEQlRTglQjYlQjMlRUYlQkMlOEMlRTYlQTAlQjklRTYlOEQlQUUlRTQlQjglODAlRTclQUYlODclRTUlQjglOTYlRTUlQUQlOTAlRTclOUElODQlRTUlQkIlQkElRTglQUUlQUUlRUYlQkMlOEMlRTYlODglOTElRTUlODUlQjMlRTklOTclQUQlRTQlQkElODZTQl9DT05GSUdfU0VDVVJFX0JPT1RfTkVUQ09SRSVFRiVCQyU4QyVFNCVCOSU4QiVFNSU5MCU4RSVFNyVCQyU5NiVFOCVBRiU5MSVFOSU4MCU5QSVFOCVCRiU4NyVFNCVCQSU4NiVFMyU4MCU4MiUyMiUyQyUyMmRzdCUyMiUzQSUyMkFmdGVyd2FyZHMlMkMlMjBJJTIwZm91bmQlMjB0aGF0JTIwdGhlcmUlMjB3YXMlMjBub3QlMjBlbm91Z2glMjBzcGFjZSUyMGluJTIwdGhlJTIwcHJvdG9jb2wlMjBzdGFjay4lMjBGb2xsb3dpbmclMjBhJTIwc3VnZ2VzdGlvbiUyMGluJTIwYSUyMHBvc3QlMkMlMjBJJTIwdHVybmVkJTIwb2ZmJTIwU0JWTmV0JTIwU0VDVVJFLUJPT1RfTkVUQ09SRSUyQyUyMGFuZCUyMHRoZSUyMGNvbXBpbGF0aW9uJTIwcGFzc2VkLiUyMiUyQyUyMm1ldGFkYXRhJTIyJTNBJTIyJTIyJTJDJTIybWV0YURhdGElMjIlM0ElNUIlNUQlMkMlMjJ0ZXh0JTIyJTNBJTIyU0JfQ09ORklHX1NFQ1VSRV9CT09UX05FVENPUkUlMjIlN0QlNUQlN0QlNUQ="&gt;SB_CONFIG_SECURE_BOOT_NETCORE&lt;/span&gt;, and the compilation passed.&lt;br /&gt;When I burn the program using the following command:&lt;/p&gt;
&lt;p&gt;nrfjprog -- program build/dfu/merge. hex -- coprocessor CP_APPLICATION -- chiperase - r&lt;br /&gt;I received this error in the log:&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Failed to open flash area ID 1 (image 0 slot 1): -19, cannot continue&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;This error is only received during software reset. If I reset by power off, there will be no such error.&lt;br /&gt;It seems that BOOT did not successfully read the flash, but I carefully checked the DTS file generated in the compilation path(build/dfu/mcuboot/zephyr/zephyer.dts) and it seems that there are no errors. How should I check this issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to configure FOAT function for LE Audio project</title><link>https://devzone.nordicsemi.com/thread/511960?ContentTypeID=1</link><pubDate>Mon, 25 Nov 2024 15:35:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d9e9985-055f-4677-9f0d-c330a475e1fe</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;My apologies, the documentation for FOTA configuration for the nRF5340 Audio application is not updated. After nRF Connect SDK v2.6.0, the buildprog Python script does not support the FOTA related flags. Please follow the &amp;quot;Building from command line&amp;quot; instructions in the application documentation, and also refer to the &lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/device_guides/nrf53/fota_update_nrf5340.html"&gt;FOTA updates for nRF5340 DK documentation&lt;/a&gt;. Also note that the external flash shield is still &lt;a href="https://docs.nordicsemi.com/bundle/ug_nrf5340_audio/page/UG/nrf5340_audio/hw_external_memory.html"&gt;required&lt;/a&gt; when using FOTA DFU on the nRF5340 Audio applications.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Maria&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>