<?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>What is the best way to merge two existing examples with SEGGER Embedded studio?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20093/what-is-the-best-way-to-merge-two-existing-examples-with-segger-embedded-studio</link><description>Hello, 
 I was wondering what is the best option/way to merge two functionalities which are developed in different examples of the nRF52 sdk12.2. 
 For instance, I would be interested on mergin into one project the ble_app_beacon_pca10040s132 and the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 02 Mar 2017 13:20:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20093/what-is-the-best-way-to-merge-two-existing-examples-with-segger-embedded-studio" /><item><title>RE: What is the best way to merge two existing examples with SEGGER Embedded studio?</title><link>https://devzone.nordicsemi.com/thread/78231?ContentTypeID=1</link><pubDate>Thu, 02 Mar 2017 13:20:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c17179b-3d81-45dd-8afe-19e7bafd03a0</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I don’t think there are any specific guidelines on how to do this. I recommend starting with the BLE example, and then add the TWI to the BLE example. Add the relevant project files to the project in SES, add the relevant TWI paths to the “User Include Directories”. Also, configure the sdk_config.h to enable the resources that TWI uses.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>