<?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>Testing GNSS firmware on a custom device (with nRF9160)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/86915/testing-gnss-firmware-on-a-custom-device-with-nrf9160</link><description>We are trying to compare the accuracy of received coordinates and satellites using GNSS firmware on two devices: 1) nRF9160 DK with external antenna; 2) Our custom board with nRF9160 (with internal antenna). 
 Our microcontroller has a physical connection</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 14 Apr 2022 07:31:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/86915/testing-gnss-firmware-on-a-custom-device-with-nrf9160" /><item><title>RE: Testing GNSS firmware on a custom device (with nRF9160)</title><link>https://devzone.nordicsemi.com/thread/363267?ContentTypeID=1</link><pubDate>Thu, 14 Apr 2022 07:31:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3cf5099b-4e7a-489a-910a-dd6d691b7178</guid><dc:creator>Stas Jis</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;a class="internal-link view-user-profile" href="https://devzone.nordicsemi.com/members/markus-schellenberger"&gt;Albrecht Markus Schellenberger&lt;/a&gt;.&lt;br /&gt;Thanks for your help, it worked.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Testing GNSS firmware on a custom device (with nRF9160)</title><link>https://devzone.nordicsemi.com/thread/363126?ContentTypeID=1</link><pubDate>Wed, 13 Apr 2022 08:28:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f46a7316-8094-418c-9ee3-0c6958303584</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p style="line-height:100%;margin-bottom:0;" lang="en-GB"&gt;&lt;strong&gt;&lt;span style="font-weight:normal;"&gt;Hello Stas,&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
[quote user=""]Actually, what is the question, can we somehow change the &amp;quot;GNSS&amp;quot; firmware in such a way that the trace from it goes to the specified UART pins? Or is it impossible to do?[/quote]
&lt;p style="line-height:100%;margin-bottom:0;" lang="en-GB"&gt;&lt;strong&gt;&lt;span style="font-weight:normal;"&gt;What do you exactly mean by trace? The application log output in a terminal or a &lt;a href="https://infocenter.nordicsemi.com/topic/ug_trace_collector/UG/trace_collector/collect_modem_trace.html"&gt;modem trace&lt;/a&gt;?&lt;br /&gt;&lt;br /&gt;Anyhow, you can freely change the pin configuration of the UART peripherals using an .&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/zephyr/guides/dts/howtos.html#use-devicetree-overlays"&gt;overlay file&lt;/a&gt; with the GNSS sample. For e.g. the nRF9160 DK, the naming would be: &lt;em&gt;../gnss/nrf9160dk_nrf9160_ns.overlay&lt;/em&gt;. As a devicetree reference for your board, I recommend you having a look at the file &lt;em&gt;../gnss/&amp;lt;your_build_folder&amp;gt;/zephyr/zephyr.dts&lt;/em&gt;.&lt;br /&gt;&lt;br /&gt;Regards,&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p style="line-height:100%;margin-bottom:0;" lang="en-GB"&gt;&lt;strong&gt;&lt;span style="font-weight:normal;"&gt;Markus&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p style="line-height:100%;margin-bottom:0;" lang="en-GB"&gt;&lt;/p&gt;
&lt;p style="line-height:100%;margin-bottom:0;" lang="en-GB"&gt;&lt;strong&gt;&lt;span style="font-weight:normal;"&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>