<?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>How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/31332/how-to-run-uart-serial-port-emulation-over-ble-on-sdk-v14-2-0</link><description>I try to run UART/Serial Port Emulation over BLE on SDK v14.2.0 with nRF52 DK and nRF Connect on Android phone following link &amp;quot; http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v12.2.0%2Fble_sdk_app_nus_c.html&amp;amp;cp=4_0_1_4_2_0_2</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 04 Apr 2018 11:01:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/31332/how-to-run-uart-serial-port-emulation-over-ble-on-sdk-v14-2-0" /><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/126819?ContentTypeID=1</link><pubDate>Wed, 04 Apr 2018 11:01:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4417505e-f152-4805-addc-1f591f13500b</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;You should follow the steps in the order described in the&amp;nbsp;&lt;a title="Serialization software setup" href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.0.0/nrf51_setups_serialization.html?cp=4_0_0_1_5_1#serialization_software"&gt;Serialization software setup&lt;/a&gt;&amp;nbsp;section. Also make sure you first cut the solderbridges as described in&amp;nbsp;&lt;a title="Serialization hardware setup" href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.0.0/nrf51_setups_serialization.html?cp=4_0_0_1_5_0#serialization_hardware"&gt;Serialization hardware setup&lt;/a&gt;. The application board should not have the softdevice programmed, only the connectivity board need this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/126289?ContentTypeID=1</link><pubDate>Wed, 28 Mar 2018 08:56:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2e644d7-83dd-4cae-bfe7-74776555e06d</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen:&amp;nbsp; I try to follow this your&amp;nbsp;link to set up serialization test with two nRF52DK boards, &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.2.0/nrf51_setups_serialization.html?cp=4_0_0_1_4"&gt;http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.2.0/nrf51_setups_serialization.html?cp=4_0_0_1_4&lt;/a&gt;&amp;nbsp;&amp;nbsp; and&amp;nbsp;find it lack of details, should I power up both board in set up connectivity board and application board? Or prepare software separately and then connect them together to do the test? Regarding application software, it mentioned only Keil, and I cannot find any examples in SDK14.2.0 in ser_s13x_transport folder. The normal BLE examples, they all need soft device programmed. Where can I find right examples? There is instructions to verify test results, should I use Mobile phone to verify test connectivity board or Tera term to verify UART in application board? Any more details of examples I can follow! Thank you in advance!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125701?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2018 10:13:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d397008-78bb-4035-bc40-de4b2f1ba7d5</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Yes, it is recommended to place it on the side to allow the signals to radiate freely. The reduction in signal will be dependent on many factors, we do not have any numbers on this,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125681?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2018 09:23:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fcd9e1b9-90aa-47d0-8984-06c251788cb5</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen, many thanks for your help. I download PC version nRF connect and am studying serialization and will try it next week. Regarding BLE module placement on a daughter PCB, I thought the module should be placed on the edge of outside of daughter PCB, not on the side between two PCBs, even it is on the edge of daughter PCB, am I right? How much percentage of signal loss comparing to mounted on the outside of PCB if I have to place it on this disadvantage position?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125573?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 14:38:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eb536481-6d3d-40f5-97df-ee07f62f432e</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;We have &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.2.0/nrf51_setups_serialization.html?cp=4_0_0_1_4"&gt;serialization examples&lt;/a&gt; in the SDK, which allows you to control the softdevice over UART and SPI. You can &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.2.0/serialization_porting_guide.html?cp=4_0_0_3_38_5"&gt;port these libraries&lt;/a&gt; to other architectures if you want. nRF Connect for desktop is open source, and available on &lt;a href="https://github.com/NordicSemiconductor?utf8=%E2%9C%93&amp;amp;q=nrfconnect&amp;amp;type=&amp;amp;language="&gt;our GitHub account&lt;/a&gt;. Bluetooth Classic have much higher current consumption than BLE, and is not in our scope of ultra low power devices.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125564?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 14:01:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89e3d148-f6a8-48c6-94b5-adf8840d4013</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Is there any example code similar to this &lt;a href="http://www.ti.com/lit/ug/tidu532/tidu532.pdf"&gt;http://www.ti.com/lit/ug/tidu532/tidu532.pdf&lt;/a&gt;? What is the recommended protocol between nRF52832 and host processor over UART port? Is nRF Connect code is open source code? Does Nordic semi has plan to produce dual mode BLE 5 IC in future?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125552?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 13:24:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c41f10bd-315d-4d3e-afd3-efdbfae99ab3</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Ok, sounds like we cannot help you with getting the Murata board to work. We only produce chips, no complete modules. Modules are created by our &lt;a href="https://www.nordicsemi.com/eng/Products/3rd-Party-Bluetooth-low-energy-Modules"&gt;module partners&lt;/a&gt;. What do you mean by &amp;quot;host processor firmware development interface to&amp;nbsp;nRF52 SoC&amp;quot;?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125549?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 13:15:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:424973ee-c458-4c9b-a409-5fc96bed33b8</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;If &amp;quot;No&amp;quot; is clicked, it cannot find Com port. I&amp;#39;ll use nRF52 DK in development but still design Murata in product if there is no better choice. Has Nordic Semi has any BLE 5 module for sale that already got license and FCC certificate like MBN52832 has? Is there any SDK to help host processor firmware development interface to&amp;nbsp;nRF52 SoC? Is there open source code in C that I can download? Thank you in advance for help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125527?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 12:35:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ae9ce577-193b-4575-b150-25369a2d0351</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;nRF Connect v2.3.0 works fine with this firmware on my board. Most likely nRF Connect think you have a different chip/board based on your serial number, and tries to flash a different firmware. What happens if you choose &amp;quot;No&amp;quot; when you are asked to flash the latest firmware?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125514?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 12:04:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:22205403-87c1-46f6-ba45-093e8a51538a</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Thank you for quick response. Programming the connectivity_1.2.2_1m is successful with your real hex file.&amp;nbsp;It could be&amp;nbsp;programed as soft device, boot loader or application, which one is correct? However,&amp;nbsp;nRF Connect 2.3.0 cannot find COM port without Segger Embedded Studio active. When&amp;nbsp;SES is active and application is download, nRF Connect still request to re-program it&amp;nbsp;to&amp;nbsp;the latest connectivity firmware, then still cannot find COM port when it tries to reprogram. It seems nRF Connect like different version firmware other than _1.2.2_1m!?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125495?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 10:15:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:819c470d-ff1e-4019-aca1-ae0351a8a472</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Like I explained above, if you left click it on GitHub (the page I linked is our account on GitHub), it will store the HTML page that shows the hex-file, not the actual hex-file. Please follow the method I described above to download the file, (or download this:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-783b6df0bcce4487944bf6fe95a09d39/connectivity_5F00_1.2.2_5F00_1m_5F00_with_5F00_s132_5F00_3.0.hex"&gt;devzone.nordicsemi.com/.../connectivity_5F00_1.2.2_5F00_1m_5F00_with_5F00_s132_5F00_3.0.hex&lt;/a&gt;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125490?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 09:54:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5116a9ee-fa1f-4348-b632-1968f7710042</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;I download the hex file from your web site the link in your last reply here &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver/tree/v2.2.1/hex/sd_api_v3"&gt;https://github.com/NordicSemiconductor/pc-ble-driver/tree/v2.2.1/hex/sd_api_v3&lt;/a&gt;&amp;nbsp;and store in my local PC,&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Capture2018032203.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;It is 2425kB shown above, is this right file. Why should I download it from GitHUB?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125462?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 08:33:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d191d951-92bb-45f9-82c8-b9e44720c88e</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;How large is the hex-file on your computer? If it is other than 460KB, there might have happened something to the download from GitHub. When I left click the file and select download on GitHub, it looks like the file is actually downloaded, but when I open the file in an editor, I see a HTML file. Make sure you click in the file, click on &lt;a href="https://raw.githubusercontent.com/NordicSemiconductor/pc-ble-driver/v2.2.1/hex/sd_api_v3/connectivity_1.2.2_1m_with_s132_3.0.hex"&gt;RAW&lt;/a&gt;, and then left click and select &amp;quot;save page as&amp;quot; or similar.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125452?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2018 07:52:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41e195ee-2214-403f-8415-3e0e9aa9a03b</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen: Thank you for help. My first attempt is failed, here&amp;nbsp;are screen shots&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Capture2018032201.PNG" /&gt;&amp;nbsp;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Capture.2018032202PNG.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;I tried erase all, program application, boot loader, but all end up in fail to read hex file. I am reading how to use nrfjprog and will try it and let you know outcome when I go through it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125312?ContentTypeID=1</link><pubDate>Wed, 21 Mar 2018 09:34:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ea103a9b-e033-441d-9736-47db523ef248</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Different versions of nRF Connect will flash different versions of the connectivity firmware, as the API in the low level driver used by nRF Connect (pc-ble-driver) have to correspond with the API of the used softdevice version. Different chips will have different softdevices, and this will decide which connectivity firmware that is flashed. nRF Connect use the serial number of the SEGGER chip to determine which chip is present, and to flash the correct connectivity firmware. This might be causing some issues for you, when you have a board with a serial number (4830* vs 68*) that is not recognized by nRF Connect as one of our DevKits. This could cause wrong connectivity firmware to be flashed to your board. You can try flashing the correct firmware manually (for nRF Connect 2.3.0, this will be&amp;nbsp;&lt;em&gt;connectivity_1.2.2_1m_with_s132_3.0.hex&lt;/em&gt; from &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver/tree/v2.2.1/hex/sd_api_v3"&gt;here&lt;/a&gt;), using &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.tools/dita/tools/nrf5x_command_line_tools/nrf5x_nrfjprogexe.html?cp=5_1_3"&gt;nrfjprog&lt;/a&gt;&amp;nbsp;or &lt;a href="https://www.nordicsemi.com/eng/Products/2.4GHz-RF/nRFgo-Studio/"&gt;nRFgo Studio&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/125288?ContentTypeID=1</link><pubDate>Wed, 21 Mar 2018 08:27:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e1c038db-817f-433a-a108-ca93e0cd884f</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen: Great! Both nRF Connect v1.1.1 and V2.3.0 works with nRF52DK, I try to find out why Murata DVK module does not work, it has the same host MCU and nRF52832 SoC. I noticed that&amp;nbsp;both versions like to re-program DK with&amp;nbsp;the latest connectivity firmware, are they programming different&amp;nbsp;connectivity firmware? How important is the latest connectivity firmware, it seems mobile version nRF Tool box does not requires the latest firmware, is this firmware mainly required on serial communication that nRF52832 talk to the&amp;nbsp;host MCU, not BLE radio communication? If yes, do I need the latest firmware code in my host processor to control Murata module apart from your SDK code to control BLE radio, if yes, where can I find the source code? Murata does not&amp;nbsp;know why its module cannot be reprogrammed and they has&amp;nbsp;no tool to program its module, their support is really poor.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124810?ContentTypeID=1</link><pubDate>Fri, 16 Mar 2018 16:51:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bc29ca7e-4fd2-4f07-9ce6-8640587c63e5</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen: Just let you know that I tested older&amp;nbsp;version 1.1.1 and it is worse,&amp;nbsp;it does not discover COM13 and ask to re-program the latest firmware,&amp;nbsp;all three pull down menus are not responsive,&amp;nbsp;the open log, clear log functions works, as shown in screenshot.&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Capture18031601.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp; My order of nRF52DK has not arrived, Mouser is slower and I&amp;#39;ll chase next Monday. I&amp;#39;ll let you know after test them. Have a good weekend!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124641?ContentTypeID=1</link><pubDate>Thu, 15 Mar 2018 17:19:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6fb2cf81-0ec1-428e-ac58-1d86915a0dbe</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;I should have specified this in more detail. I meant an even older version of nRF Connect (v1.x.x). There have been some changes in how the J-Link devices are identified in the later versions. Maybe Murata have not tested this with their DKs. Note that a new version of the product specifications does not neccessary indicate a change in silicone, only that the documentation have been updated to make sure the information within is as complete and accurate as possible. Silicone revision is given by the markings on the chip and can be compared to the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52/dita/nrf52/compatibility_matrix/ic_revision_overview.html?cp=2_1_3_0"&gt;compatibility matrix&lt;/a&gt;, but I do not know if you have this markings available on the module?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124635?ContentTypeID=1</link><pubDate>Thu, 15 Mar 2018 16:19:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93303002-ef6a-447b-8029-07ba93c4925f</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Just let you know that I tried an older nRF Connect-Windows V2.2.1,&amp;nbsp;the outcome is the same as V2.3.0. Here is the screenshots:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Capture18031503.PNG" /&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Capture18031504.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;As far as I know, MBN52832 module&amp;nbsp;and DVK use nRF52832 IC silicone version&amp;nbsp;specification v1.3, not the latest v1.4, not sure it is too old? Why does Murata not update it&amp;nbsp;to latest connectivity firmware.&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp;I&amp;#39;ll test nRF52 DK when they arrived. Thank you for advise!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124459?ContentTypeID=1</link><pubDate>Wed, 14 Mar 2018 19:44:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:25a6f936-d836-4c41-a530-c2e4012c592a</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;That is good to hear! Happy to help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124442?ContentTypeID=1</link><pubDate>Wed, 14 Mar 2018 16:52:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b708da54-a8ea-4262-9071-e885a9b550e9</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen, Great, it works now!&lt;/p&gt;
&lt;p&gt;Here are two screenshots:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Capture18031402.PNG" /&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Screenshot_5F00_2018_2D00_03_2D00_14_2D00_16_2D00_48_2D00_52_2D00_86_5B00_1_5D00_.png" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Thank you for help.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Good night!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124435?ContentTypeID=1</link><pubDate>Wed, 14 Mar 2018 16:36:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b5173e5-9b2b-458e-a059-88c5b1b73aa2</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Please also check that you are not bonded&amp;nbsp;with the device. If you are, you need to delete the bonding information from the Android Bluetooth settings.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124420?ContentTypeID=1</link><pubDate>Wed, 14 Mar 2018 15:17:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f3fc5aa5-e4d5-45c2-b606-014a51da3323</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen:&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Here are two screenshots from SES debug and nRF Tool Box log (only the initial part in screenshot)&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Capture18031401.PNG" /&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Screenshot_5F00_2018_2D00_03_2D00_14_2D00_14_2D00_44_2D00_37_2D00_50_5B00_1_5D00_.png" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;It seems there are repeated reports &amp;quot;Error (0x81) GATT INTERNAL ERROR&amp;quot;, how this can it be fixed.&lt;/p&gt;
&lt;p&gt;&amp;nbsp; I tried to run old SDK 14.1.0 yesterday after reading Mark&amp;#39;s blog 5 months ago,&amp;nbsp;he&amp;nbsp;has&amp;nbsp;the same problem as I have. The 14.1.0 contains the same bug as we already changed, wonder why Mark does not had the same problem!&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Will try an old nRF Connect later and let you know outcome. Thank you for help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124405?ContentTypeID=1</link><pubDate>Wed, 14 Mar 2018 14:32:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c53b1041-d9a2-4ce5-b9e9-bf2a33393926</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Unfortunately, I don&amp;#39;t think we have any user guide for nRF Toolbox. You can modify the buttons by clicking edit in the right corner (color turns red-ish), and clicking on each button. When done editing, click done. You can also slide the screen towards right, or rotate the phone, to see the &amp;quot;terminal view&amp;quot;.&lt;/p&gt;
&lt;p&gt;I have not tested Muratas DK, so you should ask murata about this. It looks like hey are using similar debugger chip and UART pins, so in theory it should work. You could aslo&amp;nbsp;test with an &lt;a href="http://www.nordicsemi.com/eng/nordic/Products/nRF-Connect-for-desktop/nRF-Connect-Windows/56311"&gt;older version of nRF Connect&lt;/a&gt;. The connectivity firmware is for the nRF52832 IC, and is used to control the softdevice using the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.2.0/lib_serialization.html"&gt;serialization API&lt;/a&gt;. The &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52/dita/nrf52/development/nrf52_dev_kit/interf_mcu.html?cp=2_1_4_4"&gt;interface MCU&lt;/a&gt; has its own firmware (&lt;a href="http://www.nordicsemi.com/eng/nordic/Products/nRF52-DK/nRF5x-OB-JLink-IF/52275"&gt;Segger J-Link OB&lt;/a&gt;).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?</title><link>https://devzone.nordicsemi.com/thread/124348?ContentTypeID=1</link><pubDate>Wed, 14 Mar 2018 10:44:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1607e998-cbd8-4248-a764-f6a57045ad9e</guid><dc:creator>Jian Li</dc:creator><description>&lt;p&gt;Hi, Jorgen, Thank you for help. I download nRF Toolbox, it is better, but more complicated. There are 9 buttons are blank and there is no guide how to set them, I cannot find manual here &lt;a href="http://www.nordicsemi.com/eng/Products/Nordic-mobile-Apps/nRF-Toolbox-App"&gt;http://www.nordicsemi.com/eng/Products/Nordic-mobile-Apps/nRF-Toolbox-App&lt;/a&gt;&amp;nbsp;or other places. Where is it hidden?&lt;/p&gt;
&lt;p&gt;My DVK is Murata MBN52832, Murata claims all your firmware and test codes could be tested without modification, it works fine with Blinky, Heart Rate etc examples. When PC version nRF Connect discovery the DVK,&amp;nbsp;request to&amp;nbsp;program the DVK with the&amp;nbsp;latest connectivity firmware, but cannot program it because&amp;nbsp;nRF Connect cannot find com port.&amp;nbsp;I have to ask Murata why it behaviour like that, how its connectivity firmware could be re-programmed? Mean while I cannot wait so that I ordered two more nRF52 DK yesterday to see what differences when they arrive. This seriously damages my confidence to design MBN52832 module in my product if it could not be reprogrammed later. Am I right that the connectivity firmware is for ATSAM3U2CA-AU MCU, not for nRF52832 that is programmed by soft device S132.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>