<?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>problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47461/problem-with-eddystone-in-nrf52832</link><description>Hi 
 
 I tried to implement Eddystone example in nRF52810. it worked successfully. Then i tried to implement same in nRF52832 using pca10040. But it not working. I only changed the led pin. why this not working?. 
 I am using SDK 15.3.0</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 28 May 2019 08:59:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47461/problem-with-eddystone-in-nrf52832" /><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/189515?ContentTypeID=1</link><pubDate>Tue, 28 May 2019 08:59:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8b47ecb6-297e-4be1-81d4-30eb2de30059</guid><dc:creator>NordicHam</dc:creator><description>&lt;p&gt;No problem, thank you&amp;nbsp;&lt;span&gt;Torbj&amp;oslash;rn.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards&lt;br /&gt;Jacques&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/189500?ContentTypeID=1</link><pubDate>Tue, 28 May 2019 08:33:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a55f355-8a4d-44f3-88c5-7ce1ea0e0e9a</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Jacques&lt;/p&gt;
&lt;p&gt;Thanks for the link.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I talked to Joakim, and he&amp;nbsp;will pick up the case again (once he replied it dropped out of the active list, and he unfortunately forgot to respond).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/189499?ContentTypeID=1</link><pubDate>Tue, 28 May 2019 08:33:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e90b8e02-2b4b-495c-94ec-6139b4d03c68</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Jacques&lt;/p&gt;
&lt;p&gt;Thanks for the link.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I talked to Joakim, and he&amp;nbsp;will pick up the case again (once he replied it dropped out of the active list, and he unfortunately forgot to respond).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/189245?ContentTypeID=1</link><pubDate>Mon, 27 May 2019 09:06:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:80680e41-d23c-4afc-8348-ea1008a23655</guid><dc:creator>NordicHam</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;Torbj&amp;oslash;rn,&lt;/p&gt;
&lt;p&gt;Here is the link:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/38729/nrf5_sdk_12-3-0_d7731ad---ble-peripheral-eddystone-beacon-application---cannot-connect"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/38729/nrf5_sdk_12-3-0_d7731ad---ble-peripheral-eddystone-beacon-application---cannot-connect&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Regards&lt;br /&gt;Jacques&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/189226?ContentTypeID=1</link><pubDate>Mon, 27 May 2019 08:14:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77975641-1b1f-43e8-a28b-4dc003af0476</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Can you send me a link to the other case, so I can follow up with whoever is handling it?&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/189155?ContentTypeID=1</link><pubDate>Sun, 26 May 2019 19:36:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2feed5ea-80ed-4cbf-a37f-7ec98fc109ba</guid><dc:creator>NordicHam</dc:creator><description>&lt;p&gt;I have similar problem with example BLE Eddystone 15.3.0 on nRF52-DK with nRF Connect Android app:&lt;/p&gt;
&lt;p&gt;- on Huawei T1 Mediapad with Android 4.3 I can connect&lt;br /&gt;- on Moto G5 with latest Android I cannot connect (separate thread logged for this issue)&lt;/p&gt;
&lt;p&gt;Interestingly, when I use SDK 12.3.0 on nRF51422 I can connect from both Android devices...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/188949?ContentTypeID=1</link><pubDate>Fri, 24 May 2019 06:46:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f023faef-38bf-4c47-8ef5-35efb3e52bb7</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Can you zip and send me your code project so I can give it a try on my side?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/188789?ContentTypeID=1</link><pubDate>Thu, 23 May 2019 10:17:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9af5f4ae-8881-467a-93c5-cd3cf77c1625</guid><dc:creator>sree</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;i tried with this one&amp;nbsp; &amp;nbsp;&lt;em&gt;uint8_t address_raw[] = {0x01, 0x02, 0x03, 0x04, 0x05, 0xC6};&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;and also try with other value.But no result.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/188787?ContentTypeID=1</link><pubDate>Thu, 23 May 2019 10:10:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88d56642-d485-446c-9167-5350f5dc5d28</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;There was a bug in my initial reply, and I fixed it some minutes later.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Which address did you try?&lt;/p&gt;
&lt;p&gt;It should be this one:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;uint8_t address_raw[] = {0x01, 0x02, 0x03, 0x04, 0x05, 0xC6};&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Not the one I originally posted.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/188695?ContentTypeID=1</link><pubDate>Thu, 23 May 2019 07:16:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9face1a1-58dd-4e34-b464-7d3d0db2c8a4</guid><dc:creator>sree</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;i added this to the gap_params_init() function. then it didnt detect in any phones&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/188681?ContentTypeID=1</link><pubDate>Thu, 23 May 2019 06:23:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:352c61b5-7833-4677-9c30-2e9a0a5a2cd4</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;It might be a caching problem.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you try to change the BLE address of the device and see if the problem disappears?&lt;/p&gt;
&lt;p&gt;To do this please add the following code snippet to the gap_params_init() function in your example:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;uint8_t address_raw[] = {0x01, 0x02, 0x03, 0x04, 0x05, 0xC6};&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;ble_gap_addr_t address;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;address.addr_type = BLE_GAP_ADDR_TYPE_RANDOM_STATIC;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;memcpy(address.addr, address_raw, 6); &lt;/em&gt;&lt;br /&gt;&lt;em&gt; sd_ble_gap_addr_set(&amp;amp;address);&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/188405?ContentTypeID=1</link><pubDate>Wed, 22 May 2019 05:48:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:be5d0a3c-a420-4b88-a8d6-6e8a08b87f99</guid><dc:creator>sree</dc:creator><description>&lt;p&gt;Please update the suggestions....&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/188125?ContentTypeID=1</link><pubDate>Tue, 21 May 2019 07:46:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b4c62bef-37aa-4740-a705-5f06b6aab279</guid><dc:creator>sree</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I am using honor 9 lite&lt;/p&gt;
&lt;p&gt;Segger embedded studio is using to build&lt;/p&gt;
&lt;p&gt;i tried to flash ble_app_blinky example. then same problem happened.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/188103?ContentTypeID=1</link><pubDate>Tue, 21 May 2019 07:24:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4e330629-870b-4eb4-8350-5a1d2eb3d8d3</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Which phone are you having issues with?&lt;/p&gt;
&lt;p&gt;Which compiler are you using to build the example?&lt;/p&gt;
&lt;p&gt;If you try to flash another example into your kit, such as ble_app_blinky, will it work?&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/187838?ContentTypeID=1</link><pubDate>Mon, 20 May 2019 09:18:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a922a039-058b-475e-b253-2ab66c110864</guid><dc:creator>sree</dc:creator><description>&lt;p&gt;first i flash program to nRf52810. it worked. then i changed led pin and necessary changes and flash program into nrf52832. then it not detect in nrf connect app in same phone. but it can detectable in other phones&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/187798?ContentTypeID=1</link><pubDate>Mon, 20 May 2019 08:06:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4dabbc58-217c-4dd9-be7c-024168961bb3</guid><dc:creator>NordicHam</dc:creator><description>&lt;p&gt;So you have 2 Android phones:&lt;/p&gt;
&lt;p&gt;Phone #1 can connect to&amp;nbsp;&lt;span&gt;nRF52810&amp;nbsp;and nRF52832&lt;br /&gt;&lt;/span&gt;&lt;span&gt;Phone #2 can only connect to&amp;nbsp;nRfF2810&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Is that correct?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/187795?ContentTypeID=1</link><pubDate>Mon, 20 May 2019 07:58:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:24cfd39d-e229-4f6b-a9f9-64fa277aec0b</guid><dc:creator>sree</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The code is fine. the problem is not connected to my phone. It connected to other phone but not to my phone that can connected to nRf52810 . Why this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem with Eddystone in nRF52832</title><link>https://devzone.nordicsemi.com/thread/187733?ContentTypeID=1</link><pubDate>Sat, 18 May 2019 19:32:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2401bda9-0a0e-4f07-b89f-6dbae7a25c8e</guid><dc:creator>NordicHam</dc:creator><description>&lt;p&gt;Hi Sree&lt;/p&gt;
&lt;p&gt;I programmed this pre-compiled hex file into my nRF52-DK which&amp;nbsp;has the&amp;nbsp;&lt;span&gt;nRF52832:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;..\external\nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\ble_app_eddystone\hex\ble_app_eddystone_pca10040_s132.hex&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Its working fine, I can connect to it using nRF Beacon for Eddystone Android app, as well as see the URL frames every 1 second in nRF Connect Android app.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Did you re-make the code after you&amp;#39;ve changed the led pin?&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;Jacques&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>