<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: BLE Scan Request Rx Callback on Advertising Mode in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505691#M13550</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The QN9090 is Bluetooth LE 5 compliant and covers the mandatory features, but some features such as the extended advertisement, long range or coded PHY are optional features that QN9090 does not support. Our available MCU that supports the complete Bluetooth LE 5 spec is the &lt;A href="https://www.nxp.com/products/wireless/bluetooth-low-energy/freedom-development-kit-for-kw39-38-37-mcus:FRDM-KW38" target="_blank"&gt;KW38&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Also, it is only possible to generate the Scan Request event and PDU under Extended Advertising as per the Bluetooth Core specification.&lt;/P&gt;
&lt;P&gt;I apologize for any inconvenience this may cause you.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Eduardo.&lt;/P&gt;</description>
    <pubDate>Fri, 12 Aug 2022 16:28:29 GMT</pubDate>
    <dc:creator>EduardoZamora</dc:creator>
    <dc:date>2022-08-12T16:28:29Z</dc:date>
    <item>
      <title>BLE Scan Request Rx Callback on Advertising Mode</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1503934#M13534</link>
      <description>&lt;P&gt;We are working on QN9090 SDK2.6.5.&amp;nbsp; Our device is in BLE advertisement mode. Actually, the device needs to verify the RSSI value before it connects to any central device.&amp;nbsp; As of my knowledge, After every advertisement packet, the device will receive a scan request packet from central devices around it.&lt;/P&gt;&lt;P&gt;In the firmware, Where do we check for the received scan request packet?&lt;/P&gt;</description>
      <pubDate>Wed, 10 Aug 2022 11:07:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1503934#M13534</guid>
      <dc:creator>dileep_d</dc:creator>
      <dc:date>2022-08-10T11:07:48Z</dc:date>
    </item>
    <item>
      <title>Re: BLE Scan Request Rx Callback on Advertising Mode</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505205#M13547</link>
      <description>&lt;P&gt;Hello Dileep,&lt;/P&gt;
&lt;P&gt;If you need to know the RSSI value, it is possible from the scanner device side. If your central device (Scanner) is a QN9090 board, Advertising device information can be found in gapScanningEvent_t.eventData.scannedDevice on gDeviceScanned_c event; this event is received when an advertising device has been scanned.&lt;/P&gt;
&lt;P&gt;Regarding to the Scan Request packet, it is possible to add the gExtScanNotification_c event as a case in the BleApp_AdvertisingCallback function. This event indicates that a SCAN_REQ PDU has been received by an &lt;STRONG&gt;extended advertiser&lt;/STRONG&gt;. Also, it is important to consider that the Scan Type must be set as &lt;STRONG&gt;Active Scanning&lt;/STRONG&gt;, so the scanner device can send Scan Requests to the advertiser.&lt;/P&gt;
&lt;P&gt;Once the event occurs, you can get this information in gapAdvertisingEvent_t.eventData.scanNotification:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="EduardoZamora_0-1660248686957.png" style="width: 858px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/189980i97193259FC55DE94/image-dimensions/858x93?v=v2" width="858" height="93" role="button" title="EduardoZamora_0-1660248686957.png" alt="EduardoZamora_0-1660248686957.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2022 20:14:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505205#M13547</guid>
      <dc:creator>EduardoZamora</dc:creator>
      <dc:date>2022-08-11T20:14:34Z</dc:date>
    </item>
    <item>
      <title>Re: BLE Scan Request Rx Callback on Advertising Mode</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505585#M13548</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/200888"&gt;@EduardoZamora&lt;/a&gt;&amp;nbsp;for the response,&lt;/P&gt;&lt;P&gt;Here we need to take action on the peripheral side. That is why we selected this option.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We tried to enable the &lt;FONT face="arial,helvetica,sans-serif"&gt;extended&lt;/FONT&gt; advertisement on QN9090 SDK(2.6.5). But the&amp;nbsp;&lt;FONT face="courier new,courier"&gt;Gap_SetExtAdvertisingData() &lt;FONT face="arial,helvetica,sans-serif"&gt;API is return error as&amp;nbsp;&lt;FONT face="courier new,courier"&gt;gBleFeatureNotSupported_c (4).&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;bleResult_t ret_code = Gap_SetExtAdvertisingData(gAppExtAdvParams.handle, &amp;amp;gAppAdvertisingData, NULL);&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;if (ret_code != gBleSuccess_c) {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp; &amp;nbsp; PRINTF("&amp;lt;app&amp;gt; errr : %10d : Gap_SetExtAdvertisingData failed ret: %x\n\r",&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; TICKS_TO_pdMS(xTaskGetTickCount()), ret_code);&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;}&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Does QN9090 support BLE5.0 errata?&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Does it not possible to read the scan request packets in the normal BLE advertisement??&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2022 11:26:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505585#M13548</guid>
      <dc:creator>dileep_d</dc:creator>
      <dc:date>2022-08-12T11:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: BLE Scan Request Rx Callback on Advertising Mode</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505691#M13550</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The QN9090 is Bluetooth LE 5 compliant and covers the mandatory features, but some features such as the extended advertisement, long range or coded PHY are optional features that QN9090 does not support. Our available MCU that supports the complete Bluetooth LE 5 spec is the &lt;A href="https://www.nxp.com/products/wireless/bluetooth-low-energy/freedom-development-kit-for-kw39-38-37-mcus:FRDM-KW38" target="_blank"&gt;KW38&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Also, it is only possible to generate the Scan Request event and PDU under Extended Advertising as per the Bluetooth Core specification.&lt;/P&gt;
&lt;P&gt;I apologize for any inconvenience this may cause you.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Eduardo.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2022 16:28:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505691#M13550</guid>
      <dc:creator>EduardoZamora</dc:creator>
      <dc:date>2022-08-12T16:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: BLE Scan Request Rx Callback on Advertising Mode</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505990#M13555</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/200888"&gt;@EduardoZamora&lt;/a&gt;&amp;nbsp;Thank you so much for the clarification&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 06:02:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1505990#M13555</guid>
      <dc:creator>dileep_d</dc:creator>
      <dc:date>2022-08-15T06:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: BLE Scan Request Rx Callback on Advertising Mode</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1793010#M16495</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Eduardo,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; The latest SDK will have support for BLE Extended Advertising?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Jebin&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2024 13:19:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/BLE-Scan-Request-Rx-Callback-on-Advertising-Mode/m-p/1793010#M16495</guid>
      <dc:creator>Jebin_SK</dc:creator>
      <dc:date>2024-01-22T13:19:26Z</dc:date>
    </item>
  </channel>
</rss>

