<?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>TFM SecureFault Accessing RTC device on V2.5.0-rc1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/104904/tfm-securefault-accessing-rtc-device-on-v2-5-0-rc1</link><description>Hi, 
 I have a PCF8523 RTC on a I2C bus connected on a custom board with a NRF9160 Dev board runing it (Acctinius Iccarus Dev board to be exact). Communicating with it over I2C works perfectly however when trying to communicate with it using the RTC driver</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 25 Oct 2023 14:09:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/104904/tfm-securefault-accessing-rtc-device-on-v2-5-0-rc1" /><item><title>RE: TFM SecureFault Accessing RTC device on V2.5.0-rc1</title><link>https://devzone.nordicsemi.com/thread/452309?ContentTypeID=1</link><pubDate>Wed, 25 Oct 2023 14:09:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90418385-89ba-4793-8a56-98b4a4866b8c</guid><dc:creator>4DoorToyota</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Did some digging through the code and turns out I was trying to access the RTC device through:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;RTCdevice = DEVICE_DT_GET(DT_NODELABEL(pcf8523));&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Which in my hubris I assumed would work instead of splitting the DT_NODELABEL off into a define like the examples show.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Spliting this up into two different lines with a define completly fixed the problem.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thank you very much for taking the time to help me!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TFM SecureFault Accessing RTC device on V2.5.0-rc1</title><link>https://devzone.nordicsemi.com/thread/451740?ContentTypeID=1</link><pubDate>Mon, 23 Oct 2023 13:24:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7878cd3a-22bd-4674-b147-340c2689e2dc</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;TF-M assigned different parts of hardware as secure and others as non-secure.&lt;/p&gt;
&lt;p&gt;The error you face could be caused because the driver tries to access a secure part from non-secure code.&lt;br /&gt;The I2C driver should be non-secure, but to check this, could you try some different I2C instances?&lt;/p&gt;
&lt;p&gt;Maybe more likely is that it is using some pins designated as secure. Could you try to change the pins and see if you get the same issue?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TFM SecureFault Accessing RTC device on V2.5.0-rc1</title><link>https://devzone.nordicsemi.com/thread/451716?ContentTypeID=1</link><pubDate>Mon, 23 Oct 2023 12:22:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e2d34327-ed46-48fb-a600-820cb8c19287</guid><dc:creator>4DoorToyota</dc:creator><description>&lt;p&gt;The driver is here in the main zephyr repository and is part of the versiion included with NRF&amp;nbsp;&lt;span&gt;V2.5.0-rc1.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;a href="https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/rtc/rtc_pcf8523.c"&gt;https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/rtc/rtc_pcf8523.c&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The device however does not implement all of the features present on the device so I have a couple of functions that get the I2C&amp;nbsp;node and then commmunicate with the chip over the bus. Wasn&amp;#39;t sure if it was a relevant thing to mention but wanted to give the full picture and it shows that the device is alive and functioning.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TFM SecureFault Accessing RTC device on V2.5.0-rc1</title><link>https://devzone.nordicsemi.com/thread/451698?ContentTypeID=1</link><pubDate>Mon, 23 Oct 2023 11:45:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:02aa793a-7863-447b-b153-7a1b671d15ad</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]Communicating with it over I2C works perfectly however when trying to communicate with it using the RTC driver present in zephyr for it[/quote]
&lt;p&gt;Can you link to the RTC driver you refer to?&lt;/p&gt;
&lt;p&gt;Are we talking about an external RTC device that you communicate with over I2C?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>