<?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>TF-M GPIO MCU-select IOCTL compiled out</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128058/tf-m-gpio-mcu-select-ioctl-compiled-out</link><description>It seems there might be a small issue with the TF-M GPIO MCU-select IOCTL plumbing on nRF54L — specifically when a non-secure app tries to configure sQSPI GPIOs (and presumably any other co-processor pins, e.g. FLPR) via TF-M&amp;#39;s secure GPIO service. 
</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Nov 2017 10:43:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128058/tf-m-gpio-mcu-select-ioctl-compiled-out" /></channel></rss>