<?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>Multiple nRF52832 to a single nRF51 dongle</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/57451/multiple-nrf52832-to-a-single-nrf51-dongle</link><description>Dear all 
 I currently have a single nRF52832 SoC (custom PCB) transferring data to a single nRF51 dongle via BLE, which in turn passes the data to my PC via UART. I have been using ble_app_uart_c codes for this purpose. 
 I would like to edit the codes</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 07 Feb 2020 13:10:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/57451/multiple-nrf52832-to-a-single-nrf51-dongle" /><item><title>RE: Multiple nRF52832 to a single nRF51 dongle</title><link>https://devzone.nordicsemi.com/thread/233294?ContentTypeID=1</link><pubDate>Fri, 07 Feb 2020 13:10:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b00fe7aa-c978-47f2-be60-13717cd1ee7e</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This would be a merge of our&lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/ble_sdk_app_multilink.html?cp=7_1_4_2_0_2"&gt; NUS client example&lt;/a&gt; and the &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/ble_sdk_app_multilink.html?cp=7_1_4_2_0_2"&gt;multi link example&lt;/a&gt;. I suggest that you start by first understanding how the two examples work and then try to merge them.&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;
&lt;p&gt;Jared&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>