<?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>Can one run a custom c-application in the Arm TrustZone (especially using VSCode)?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/111843/can-one-run-a-custom-c-application-in-the-arm-trustzone-especially-using-vscode</link><description>Hi, here in the documentation ( https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/config_and_build/board_support/processing_environments.html ) for the latest nRF Connect SDK it says: &amp;quot;The application is built as a non-secure image and Trusted</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 10 Jun 2024 07:39:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/111843/can-one-run-a-custom-c-application-in-the-arm-trustzone-especially-using-vscode" /><item><title>RE: Can one run a custom c-application in the Arm TrustZone (especially using VSCode)?</title><link>https://devzone.nordicsemi.com/thread/488029?ContentTypeID=1</link><pubDate>Mon, 10 Jun 2024 07:39:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6127b5b4-62a3-4f94-a54c-e075ad045c0e</guid><dc:creator>gdl</dc:creator><description>&lt;p&gt;Many thanks for the explaination&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can one run a custom c-application in the Arm TrustZone (especially using VSCode)?</title><link>https://devzone.nordicsemi.com/thread/487717?ContentTypeID=1</link><pubDate>Thu, 06 Jun 2024 12:17:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3884402c-5b97-48bf-a26d-1b434cbeda6f</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There is nothing from a hardware perspective that dictates that you must use TF-M. You can in theory also run another secure image, like we did early on in the SDK before introducing TF-M. However, TF-M is the only thing we support now, ant it is heavily integrated in the SDK. So I would strongly advice that you stick with TF-M.&lt;/p&gt;
&lt;p&gt;That said, you can expand TF-M yourself. Both with pure software servicds, and services that integrade with specific hardware. This is demonstrated by the &lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/nrf/samples/tfm/tfm_secure_peripheral/README.html"&gt;TF-M secure peripheral partition&lt;/a&gt;&amp;nbsp;sample.&lt;/p&gt;
&lt;p&gt;The VS code extension supports multi image builds and also debugging multi image builds. You can experiment with this using SDK examples to see how it works, but in generall it is quite seemless and behaves as you would expect.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>