<?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>identifying BLE DFU target</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22223/identifying-ble-dfu-target</link><description>We have both nrf51 and nrf52 running DFU.
How can I identify on the mobile application side whether I&amp;#39;m connecting to nrf51 or nrf52?
They will need to get different firmware hex file updates.
There are obviously some trivial solutions (say, different</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 May 2017 11:01:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22223/identifying-ble-dfu-target" /><item><title>RE: identifying BLE DFU target</title><link>https://devzone.nordicsemi.com/thread/87320?ContentTypeID=1</link><pubDate>Mon, 22 May 2017 11:01:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4e515063-f33a-47f9-a44b-cef27c7bbaa9</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Changing the device name would be the easiest solution. If you don&amp;#39;t want to change device name,  you can add some data in advertising packet. You can add any data using Manufacturer Data field. Please have a look at advertising_data_init() function in main.c in ble_app_pwr_profilling example. Of course you need to use your app to read this data and then decide to use which firmware to do DFU.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>