<?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>Port nRF51-ble-bcast-mesh-master to RedBear Lab BLE Nano</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8316/port-nrf51-ble-bcast-mesh-master-to-redbear-lab-ble-nano</link><description>I use Keil uVision 4.74.0.22 to compile nRF51-ble-bcast-mesh-master with nrf51_sdk_v6_1_0_b2ec2e6 and get the rbc_mesh_BLE_Gateway.hex. However, I drag and drop the hex file to MBED drive and it&amp;#39;s not working. I heard that uVision trial version only support</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Nov 2015 18:30:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8316/port-nrf51-ble-bcast-mesh-master-to-redbear-lab-ble-nano" /><item><title>RE: Port nRF51-ble-bcast-mesh-master to RedBear Lab BLE Nano</title><link>https://devzone.nordicsemi.com/thread/30065?ContentTypeID=1</link><pubDate>Fri, 27 Nov 2015 18:30:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:11632500-9b97-4676-b85b-44ff7a48864d</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;As of the 0.7.x release on the sdk-8-support branch of the ble-bcast-mesh , the format of the advertising has been made compatible with Bluetooth 4.0 and uses the Service Data AD type.
See &lt;a href="https://github.com/NordicSemiconductor/nRF51-ble-bcast-mesh/blob/sdk-8-support/docs/how_it_works.adoc"&gt;github.com/.../how_it_works.adoc&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Port nRF51-ble-bcast-mesh-master to RedBear Lab BLE Nano</title><link>https://devzone.nordicsemi.com/thread/30064?ContentTypeID=1</link><pubDate>Mon, 27 Jul 2015 13:05:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:43b066f0-4d19-4218-bb2f-7dd04f410161</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Max: Currently the packet between LED-Mesh is not BLE compatible. We have the option RBC_MESH_PACKET_FORMAT_ADV_COMPATIBLE for the init_params.packet_format but it&amp;#39;s under development not ready yet.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Port nRF51-ble-bcast-mesh-master to RedBear Lab BLE Nano</title><link>https://devzone.nordicsemi.com/thread/30063?ContentTypeID=1</link><pubDate>Mon, 27 Jul 2015 07:13:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:104b4556-0720-474a-9b8f-138669d454a2</guid><dc:creator>Max</dc:creator><description>&lt;p&gt;I see. Previously, I was expecting to see advertising packets from LED example. Now I can turn LED on/off on LED example by writing LED1 value characteristic on Gateway example.&lt;/p&gt;
&lt;p&gt;Because I still can&amp;#39;t see any rebroadcasting packets, I am wondering how the change of LED1 value on Gateway example got to propagate to other nodes?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Port nRF51-ble-bcast-mesh-master to RedBear Lab BLE Nano</title><link>https://devzone.nordicsemi.com/thread/30062?ContentTypeID=1</link><pubDate>Thu, 23 Jul 2015 12:47:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2fd7ea84-0b67-4ab1-8cfd-e2e1aed77f64</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Max: How did you test the LED example ?&lt;/p&gt;
&lt;p&gt;Note that the BLE_Gateway allow a phone to connect and join the network, that&amp;#39;s why we have nrf_adv_conn_init() so that BLE central device can connect and control the other nodes.&lt;/p&gt;
&lt;p&gt;In the LED example, they only do broadcast mesh, won&amp;#39;t allow connection. The control is either from button press, or from a phone connected to the BLE Gateway.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Port nRF51-ble-bcast-mesh-master to RedBear Lab BLE Nano</title><link>https://devzone.nordicsemi.com/thread/30061?ContentTypeID=1</link><pubDate>Thu, 23 Jul 2015 08:47:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:710fe833-571d-4707-9105-860404b1385d</guid><dc:creator>Max</dc:creator><description>&lt;p&gt;Thanks for the tip. I got rbc_mesh_BLE_Gateway working by merging it with s110_nrf51822_7.3.0_softdevice (didn&amp;#39;t know merge is required). However, rbc_mesh_led_example is not working and I found that its main.c doesn&amp;#39;t include nrf_adv_conn_init(). Would that be the problem?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Port nRF51-ble-bcast-mesh-master to RedBear Lab BLE Nano</title><link>https://devzone.nordicsemi.com/thread/30060?ContentTypeID=1</link><pubDate>Wed, 22 Jul 2015 09:35:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53289216-5129-45c4-bf5f-66865ae21347</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Max: have you also drag and drop softdevice to the mbed driver ? When compiling normal project with KEIL, the softdevice is not included.&lt;/p&gt;
&lt;p&gt;You can follow this link: &lt;a href="https://devzone.nordicsemi.com/blogs/11/using-nrf51-sdk-with-the-nrf51822-mbed-kit/"&gt;https://devzone.nordicsemi.com/blogs/11/using-nrf51-sdk-with-the-nrf51822-mbed-kit/&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>