<?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>nrfutil device should respect system library path</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123161/nrfutil-device-should-respect-system-library-path</link><description>I would assume that nrfutil device will respect MacOS DYLD_LIBRARY_PATH environment variable but instead it fails to load libjlinkarm.dylib. Steps to reproduce: - Run nrfutil device with specified DYLD_LIBRARY_PATH: DYLD_LIBRARY_PATH=&amp;#39;./segger-jlink-852</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 24 Jul 2025 14:03:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123161/nrfutil-device-should-respect-system-library-path" /><item><title>RE: nrfutil device should respect system library path</title><link>https://devzone.nordicsemi.com/thread/543531?ContentTypeID=1</link><pubDate>Thu, 24 Jul 2025 14:03:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:586662ee-2b8f-4c4d-891a-ebd259874ba7</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Unfortunately yes. Sorry I could not be of more help&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfutil device should respect system library path</title><link>https://devzone.nordicsemi.com/thread/543396?ContentTypeID=1</link><pubDate>Wed, 23 Jul 2025 17:49:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:61f34b7f-4d5e-40a9-b12a-739ad82924ad</guid><dc:creator>michal4132</dc:creator><description>&lt;p&gt;It&amp;nbsp;means that user needs to type jlink-dll option every time or wrap it into some kind of helper script. I will just move to J-Link. Thanks for help :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfutil device should respect system library path</title><link>https://devzone.nordicsemi.com/thread/543374?ContentTypeID=1</link><pubDate>Wed, 23 Jul 2025 14:00:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:82f44f81-ae8b-499c-aad7-020d827f7f6f</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;&lt;span&gt;The &lt;code&gt;--jlink-dll&lt;/code&gt; option can be used to specify the path to the J-Link DLL. If that is not set, we try to use the J-Link DLL from the default location at &lt;code&gt;/Applications/SEGGER/JLink/&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Runar&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfutil device should respect system library path</title><link>https://devzone.nordicsemi.com/thread/543365?ContentTypeID=1</link><pubDate>Wed, 23 Jul 2025 13:20:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:05350124-398d-48ab-b142-f29f1e6e38d6</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I&amp;#39;m running this by the nrfutil team and will get back to you&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>