<?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>To add firmware revision in advertisement packet</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6620/to-add-firmware-revision-in-advertisement-packet</link><description>Hello Everyone, 
 I want firmware revision to be added in advertisement packet how can i do it . is it ok to add it to manufacturer data or it is nordic proprietary . 
 i have done it like this. to add firmware revision 1.2 
 adv_manuf_data_data[0</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Apr 2015 11:46:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6620/to-add-firmware-revision-in-advertisement-packet" /><item><title>RE: To add firmware revision in advertisement packet</title><link>https://devzone.nordicsemi.com/thread/23164?ContentTypeID=1</link><pubDate>Mon, 27 Apr 2015 11:46:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7376b6bd-9958-4c6e-a187-d86748034d61</guid><dc:creator>asma</dc:creator><description>&lt;p&gt;Thank you David&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: To add firmware revision in advertisement packet</title><link>https://devzone.nordicsemi.com/thread/23163?ContentTypeID=1</link><pubDate>Mon, 27 Apr 2015 10:49:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8df3c3b6-4489-4ca6-9b7e-0ee851b2741d</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;If you are not a Bluetooth SIG member I would urge you to use the Device Information Service and the Firmware revision number. Yes, there will be a marginal impact during Service Discovery if you add the Device Information Service to the GATT, other wise you can use the Device Information Service Details only on the Advertising packet and not in the GATT.&lt;/p&gt;
&lt;p&gt;Choose whichever works for you , the important point is to know the options available and the advice provided for each option.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: To add firmware revision in advertisement packet</title><link>https://devzone.nordicsemi.com/thread/23162?ContentTypeID=1</link><pubDate>Wed, 22 Apr 2015 04:04:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:09c5fdd1-7635-4666-a932-a284ebf1efde</guid><dc:creator>asma</dc:creator><description>&lt;p&gt;I agree,but i dont want to add more service to my profile as it will take more time for app to read the services and their characteristics. once the firmware revision is advertised along with other data and accepted by client(Mobile App) it will store it in memory thats my idea.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: To add firmware revision in advertisement packet</title><link>https://devzone.nordicsemi.com/thread/23161?ContentTypeID=1</link><pubDate>Tue, 21 Apr 2015 14:50:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:883d0522-15a0-48eb-b360-4e0c261fc753</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;I think a better solution may be to use the &lt;a href="https://developer.bluetooth.org/gatt/services/Pages/ServiceViewer.aspx?u=org.bluetooth.service.device_information.xml"&gt;Device Information Service&lt;/a&gt; the AD type Service Data to have the firmware version in it as date.
I.e. &amp;lt;UUID = Device Information&amp;gt;&amp;lt;Data = Firmware Revision&amp;gt;
The Firmware Revision is a characteristic in the Device Information Service.
This leverages existing UUIDs and does not use a vendor specific format.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: To add firmware revision in advertisement packet</title><link>https://devzone.nordicsemi.com/thread/23160?ContentTypeID=1</link><pubDate>Tue, 21 Apr 2015 11:52:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d80af371-3597-4bfe-a26e-af7370440289</guid><dc:creator>asma</dc:creator><description>&lt;p&gt;thank you so much.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: To add firmware revision in advertisement packet</title><link>https://devzone.nordicsemi.com/thread/23159?ContentTypeID=1</link><pubDate>Tue, 21 Apr 2015 11:50:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a199e37-8fc5-4d1f-a799-4ca307b83eaa</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;You can use the manufacturer specific data for whatever you want. The &amp;quot;manufacturer&amp;quot; is you, not Nordic :) Check out &lt;a href="https://www.bluetooth.org/en-us/specification/assigned-numbers/company-identifiers"&gt;this list&lt;/a&gt; of company IDs to see why you get that MCP message. As you can see the value 0xFF00 is categorized as reserved. Change the value to e.g. 0x0059 and you will see &amp;quot;Nordic Semiconductor ASA&amp;quot; instead. To get your own ID I&amp;#39;m afraid you will have to be a &amp;quot;&lt;em&gt;Bluetooth SIG member in good standing&lt;/em&gt;&amp;quot;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/tutorials/5/a-beginners-tutorial-advertising/"&gt;Here is a tutorial&lt;/a&gt; discussing various properties of the advertising packet.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>