<?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>Using the NFC pins as GPIO breaks SPI instance</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/28754/using-the-nfc-pins-as-gpio-breaks-spi-instance</link><description>On a custom board with an nRF52832, I have some LEDs I&amp;#39;m driving from the pins 9 and 10. One or both of these pins are used for the NFC antenna unless you configure them as GPIO. Many posts here show how to do that. One of them explains that, for gcc</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 24 Dec 2017 12:25:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/28754/using-the-nfc-pins-as-gpio-breaks-spi-instance" /><item><title>RE: Using the NFC pins as GPIO breaks SPI instance</title><link>https://devzone.nordicsemi.com/thread/113939?ContentTypeID=1</link><pubDate>Sun, 24 Dec 2017 12:25:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7877ec80-8e90-4e47-b356-ecab00567f24</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;The UICR value is sticky across resets, if it wasn&amp;#39;t then nothing would work. The code is in the gcc tool section so you&amp;#39;d expect it to work. I don&amp;#39;t even vaguely get how setting the NFC pin register could affect SPI, but if there&amp;#39;s a better way to enable it, I&amp;#39;d just use that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using the NFC pins as GPIO breaks SPI instance</title><link>https://devzone.nordicsemi.com/thread/113938?ContentTypeID=1</link><pubDate>Sun, 24 Dec 2017 10:27:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0529c24d-2409-46ef-9334-0d935e0862d5</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;@RK Because I was following this answer and that didn&amp;#39;t make it clear that using &lt;code&gt;CONFIG_NFCT_PINS_AS_GPIOS&lt;/code&gt; alone was sufficient, even for gcc: &lt;a href="https://devzone.nordicsemi.com/question/96013/how-to-enable-p009-and-p010-as-gpio-pins-on-the-nrf52-instead-of-nfc-pins/?answer=96017#post-id-96017"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using the NFC pins as GPIO breaks SPI instance</title><link>https://devzone.nordicsemi.com/thread/113940?ContentTypeID=1</link><pubDate>Sun, 24 Dec 2017 00:14:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:656fc0fe-c69a-4d52-83b1-f069826d2b30</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Why don&amp;#39;t you just use the standard method of setting the NFC pins off by defining &lt;code&gt;CONFIG_NFCT_PINS_AS_GPIOS&lt;/code&gt;. The system_nrf52.c file will then fix it on first run and reset. Done. All this messing about with linker maps just isn&amp;#39;t necessary&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using the NFC pins as GPIO breaks SPI instance</title><link>https://devzone.nordicsemi.com/thread/113937?ContentTypeID=1</link><pubDate>Sat, 23 Dec 2017 12:58:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ea1b6b69-c3c2-4944-9d8f-f62308bb2b4a</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;I think you mean the value should be &lt;code&gt;0xFFFFFFFE&lt;/code&gt;, not &lt;code&gt;0x01&lt;/code&gt;.
I can get both the GPIO and the SPI to work only if I write to the UICR using &lt;code&gt;nrfjproj&lt;/code&gt; before flashing my code. I can&amp;#39;t get it to work using the const in code, even when setting the correct value. Will add my linker script above. The &lt;code&gt;nrfjproj&lt;/code&gt; approach is a bit of a hack, so I&amp;#39;d like to get this working in code.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using the NFC pins as GPIO breaks SPI instance</title><link>https://devzone.nordicsemi.com/thread/113941?ContentTypeID=1</link><pubDate>Fri, 22 Dec 2017 13:03:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:650be081-168e-415d-bc22-70e9e5cce15d</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;I would suggest you to try writing to UICR (to the address 0x1000120c) using nrfjprog, just for testing first. Check if both GPIO and SPI work or not.&lt;/p&gt;
&lt;p&gt;If that work then you need to check your attribute declaration, I don&amp;#39;t see you set it to a value (should be 0x01). This is how we set the address of the bootloader in UICR:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;   volatile uint32_t m_uicr_bootloader_start_address  __attribute__ ((section(&amp;quot;.uicr_bootloader_start_address&amp;quot;)))
                                            = BOOTLOADER_START_ADDR;
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>