<?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>Thingy:52 SDK v2.1.0 No logs with JLink v6.22g</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/49120/thingy-52-sdk-v2-1-0-no-logs-with-jlink-v6-22g</link><description>Hello, 
 I have inherited a Thingy:52 project which was using some old versions of SDKs. Now I am trying to port it to a newer version in order to make it compatible with Bluetooth mesh. 
 In the current version I am using JLink v6.22g to see debug messages</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 01 Jul 2019 14:22:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/49120/thingy-52-sdk-v2-1-0-no-logs-with-jlink-v6-22g" /><item><title>RE: Thingy:52 SDK v2.1.0 No logs with JLink v6.22g</title><link>https://devzone.nordicsemi.com/thread/195707?ContentTypeID=1</link><pubDate>Mon, 01 Jul 2019 14:22:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bcc042a1-78c2-46ff-946a-d78a532ae9e1</guid><dc:creator>robertsehlstedt</dc:creator><description>&lt;p&gt;Apparently I shouldn&amp;#39;t have defined the NRF_LOG_ENABLED in the main.c file, but actually in the config file, not sure what went wrong because of it, but something did :) And I didn&amp;#39;t need to add to the makefile either.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:52 SDK v2.1.0 No logs with JLink v6.22g</title><link>https://devzone.nordicsemi.com/thread/195702?ContentTypeID=1</link><pubDate>Mon, 01 Jul 2019 14:12:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9729e653-212f-4918-ad31-b713f06afa2d</guid><dc:creator>robertsehlstedt</dc:creator><description>&lt;p&gt;Ahh yes I had forgot to enable it actually. I added a #define NRF_LOG_ENABLED 1 to the start of my main.c file for now.&lt;/p&gt;
&lt;p&gt;Now I have this strange error which is not necessarily relevant to Nordic, but this is part of my output&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="batchfile"&gt;...
Linking target: nrf52832_xxaa_s132.out
_build/main.o: In function `m_batt_meas_handler&amp;#39;:
/home/robban/sommarjobb/hubben/nrf5_sdk_for_mesh/external/thingysdkv210/project/pca20020_s132/thingy.c:149: undefined reference to `nrf_log_frontend_std_3&amp;#39;
...&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;However I did add nrf_log_frontend.c to the source files in my Makefile, and libraries/log to include paths.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="batchfile"&gt;...
$(abspath ../../../sdk_components/libraries/log/src/nrf_log_frontend.c) \
...
INC_PATHS += -I$(abspath ../../../sdk_components/libraries/log)
INC_PATHS += -I$(abspath ../../../sdk_components/libraries/log/src)
...&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;No clue what&amp;#39;s happening here.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:52 SDK v2.1.0 No logs with JLink v6.22g</title><link>https://devzone.nordicsemi.com/thread/195669?ContentTypeID=1</link><pubDate>Mon, 01 Jul 2019 13:20:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d0645dd5-60ee-4128-a5eb-7576f46ee6f4</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I tested this myself, and I was able to see the log output using RTT viewer.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you made sure that logging is enabled in the sdk_config.h file? From what I can see, logging is not enabled by default in the SDK.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim Jakobsen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>