<?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>Communication with MT8852B</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23944/communication-with-mt8852b</link><description>Hi
I am sending my BT module with nRF51822 for some regulation test and the Test Lab is using Anritsu MT8852B to communicate with my module through USB-to-UART adaptor and they found the equipment cannot find the address of the module. What is the suggestion</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 31 Jul 2017 21:14:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23944/communication-with-mt8852b" /><item><title>RE: Communication with MT8852B</title><link>https://devzone.nordicsemi.com/thread/94277?ContentTypeID=1</link><pubDate>Mon, 31 Jul 2017 21:14:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30dbb7db-262f-42cc-b01c-6afae314c4b5</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;yes most simple testing just needs the DTM code - if the house is looking for a much more full featured HCI interface, I&amp;#39;ve not tried it but I believe Zephyr supports a full HCI stack on nRF52.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/blogs/1059/nrf5x-support-within-the-zephyr-project-rtos/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;might be easier to find a different testing house.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Communication with MT8852B</title><link>https://devzone.nordicsemi.com/thread/94279?ContentTypeID=1</link><pubDate>Mon, 31 Jul 2017 15:39:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b52ea59c-f37d-4731-af0e-e7b19c5a695d</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;To work with any BT SIG DTM host over UART (as defined in V4.0/4.1 specifications) it&amp;#39;s usually enough to incorporate &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v12.3.0/ble_sdk_app_dtm_serial.html?cp=4_0_2_4_4"&gt;nRF5 SDK DTM example&lt;/a&gt; into your FW + find the way how to switch to it (e.g. during boot procedure) once it is on test-bed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Communication with MT8852B</title><link>https://devzone.nordicsemi.com/thread/94278?ContentTypeID=1</link><pubDate>Mon, 31 Jul 2017 15:10:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:241522e1-2559-48e5-88d4-91ea755b89c9</guid><dc:creator>Li chi hung</dc:creator><description>&lt;p&gt;Thanks RK and endnode to answer my question.  Firstly, &amp;quot;cannot find the address of the module&amp;quot; is feedback from test Lab and I will check with them to clarify their problem.  For the software inside, we are using the code to match DTM test inside nRFgo Studio so I cannot 100% sure this firmware can connect to BT tester with standard BT DTM (test) and HCI command or not.  What is your recommendation to make the firmware to well communicate with standard DTM(TEST and HCI command?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Communication with MT8852B</title><link>https://devzone.nordicsemi.com/thread/94282?ContentTypeID=1</link><pubDate>Mon, 31 Jul 2017 12:12:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8c6e17d9-ff0f-4365-bf9e-72ad9461107f</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;by &amp;#39;address&amp;#39; my guess was one of the HCI commands, possibly one of the first ones, is expected to return some kind of device address. You&amp;#39;d have thought the testing device before it got to &amp;#39;no address&amp;#39; error would have produced a &amp;#39;no device&amp;#39; error but who knows.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Communication with MT8852B</title><link>https://devzone.nordicsemi.com/thread/94281?ContentTypeID=1</link><pubDate>Mon, 31 Jul 2017 12:09:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3adc6364-e9b7-4044-9845-21a47bd0f8eb</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;the only &amp;quot;standard&amp;quot; protocols on top of UART in BLE are DTM (test) and HCI. Nordic BLE stacks don&amp;#39;t support standard BT SIG HCI and DTM you would need to incorporate into your APP firmware (but that&amp;#39;s easy, there are examples in nRF5 SDK). Also your complain about &amp;quot;address&amp;quot; doesn&amp;#39;t make sense, UART is simply point-to-point wire, no &amp;quot;addressing&amp;quot; unless you mean some higher level things in your protocol or e.g. serial port numbers on your PC host;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Communication with MT8852B</title><link>https://devzone.nordicsemi.com/thread/94280?ContentTypeID=1</link><pubDate>Mon, 31 Jul 2017 11:04:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6a4fb65d-f7cf-4377-ac2e-c50a346c0576</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;What software do you have running on the module? The nrf51822 doesn&amp;#39;t have any built-in support for HCI over UART on it (or HCI over USB for that matter). So unless you are running some HCI software, the chip isn&amp;#39;t going to do anything.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>