<?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>SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/86973/softdevice-and-application-firmware-upgrade-from-6-1-1-to-7-2-0-issue</link><description>I am trying to upgrade SoftDevice and Application firmware from v6.1.1 to v7.2.0 on Nordic USB840M dongle and I am facing a strange issue after such upgrade. 
 
 Please find below the steps I am doing: 
 
 
 Generate the upgrade zip package: 
 nrfutil</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 21 Apr 2022 06:17:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/86973/softdevice-and-application-firmware-upgrade-from-6-1-1-to-7-2-0-issue" /><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/364081?ContentTypeID=1</link><pubDate>Thu, 21 Apr 2022 06:17:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1cbcce85-550d-4dcb-b83b-886b4311b5cb</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;Yuriy,&lt;/p&gt;
&lt;p&gt;That is good to hear! Thanks for letting us know.&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/364033?ContentTypeID=1</link><pubDate>Wed, 20 Apr 2022 19:30:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da861876-f12c-4676-9f0b-6e1ad4d91488</guid><dc:creator>Yuriy Sharamaha</dc:creator><description>&lt;p&gt;Hi Einar,&lt;/p&gt;
&lt;p&gt;Please disregard&amp;nbsp;my above request - I have already implemented the serialization/deserialization code in nRF5 SDK and pc-ble-driver for&amp;nbsp;&lt;strong&gt;BLE_GATTC_OPT_UUID_DISC&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;&lt;span&gt;option.&lt;/span&gt;&amp;nbsp;So that, &lt;strong&gt;sd_ble_opt_set&lt;/strong&gt; does not throw an error now when calling with&amp;nbsp;&lt;strong&gt;BLE_GATTC_OPT_UUID_DISC &lt;/strong&gt;option&lt;b&gt;. &lt;/b&gt;Seems working. Thank you very much for your help.&lt;/p&gt;
&lt;p&gt;Yuriy&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363967?ContentTypeID=1</link><pubDate>Wed, 20 Apr 2022 13:39:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:51a83f8c-2ee2-488f-aeaf-dbd472fe648a</guid><dc:creator>Yuriy Sharamaha</dc:creator><description>&lt;p&gt;In&amp;nbsp;&lt;strong&gt;nRF5_SDK_15.3.0_59ac345\components\serialization\connectivity\codecs\ble\serializers\ble_conn.c&lt;/strong&gt; there are following implementations of&amp;nbsp;&lt;strong&gt;ble_opt_set_req_dec&lt;/strong&gt;/&lt;strong&gt;ble_opt_set_rsp_enc&lt;/strong&gt; functions:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;uint32_t ble_opt_set_req_dec(uint8_t const * const   p_buf,
                             uint16_t                packet_len,
                             uint32_t *  const       p_opt_id,
                             ble_opt_t **const       pp_opt )
{
    SER_REQ_DEC_BEGIN(SD_BLE_OPT_SET);

    SER_ASSERT_NOT_NULL(p_opt_id);
    SER_ASSERT_NOT_NULL(pp_opt);
    SER_ASSERT_NOT_NULL(*pp_opt);

    SER_PULL_uint32(p_opt_id);

    SER_PULL_COND(pp_opt, NULL);
    if (*pp_opt)
    {
        field_decoder_handler_t fp_decoder = NULL;
        void * p_struct = NULL;

        switch (*p_opt_id)
        {
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION &amp;lt; 4
            case BLE_COMMON_OPT_CONN_BW:
                fp_decoder = ble_common_opt_conn_bw_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;common_opt.conn_bw);
            break;
#endif
            case BLE_COMMON_OPT_PA_LNA:
                fp_decoder = ble_common_opt_pa_lna_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;common_opt.pa_lna);
            break;
            case BLE_COMMON_OPT_CONN_EVT_EXT:
                fp_decoder = ble_common_opt_conn_evt_ext_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;common_opt.conn_evt_ext);
            break;
            case BLE_GAP_OPT_CH_MAP:
                fp_decoder = ble_gap_opt_ch_map_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.ch_map);
            break;
            case BLE_GAP_OPT_LOCAL_CONN_LATENCY:
                fp_decoder = ble_gap_opt_local_conn_latency_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.local_conn_latency);
            break;
            case BLE_GAP_OPT_PASSKEY:
                fp_decoder = ble_gap_opt_passkey_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.passkey);
            break;
            case BLE_GAP_OPT_AUTH_PAYLOAD_TIMEOUT:
                fp_decoder = ble_gap_opt_auth_payload_timeout_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.auth_payload_timeout);
            break;
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION &amp;lt; 4
            case BLE_GAP_OPT_EXT_LEN:
                fp_decoder = ble_gap_opt_ext_len_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.ext_len);
            break;
#endif
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION &amp;lt; 6
            case BLE_GAP_OPT_SCAN_REQ_REPORT:
                fp_decoder = ble_gap_opt_scan_req_report_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.scan_req_report);
            break;
#endif
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION &amp;lt; 4
            case BLE_GAP_OPT_COMPAT_MODE:
                fp_decoder = ble_gap_opt_compat_mode_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.compat_mode);
            break;
#else
#ifndef S112
            case BLE_GAP_OPT_COMPAT_MODE_1:
                fp_decoder = ble_gap_opt_compat_mode_1_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.compat_mode_1);
            break;
#endif
            case BLE_GAP_OPT_SLAVE_LATENCY_DISABLE:
                fp_decoder = ble_gap_opt_slave_latency_disable_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.slave_latency_disable);
            break;
#endif
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION == 4
            case BLE_GAP_OPT_COMPAT_MODE_2:
                fp_decoder = ble_gap_opt_compat_mode_2_t_dec;
                p_struct   = &amp;amp;((*pp_opt)-&amp;gt;gap_opt.compat_mode_2);
            break;
#endif
            default:
                SER_ASSERT(NRF_ERROR_INVALID_PARAM,NRF_ERROR_INVALID_PARAM);
            break;
        }

        SER_PULL_FIELD(p_struct, fp_decoder);
    }

    SER_REQ_DEC_END;
}


uint32_t ble_opt_set_rsp_enc(uint32_t                return_code,
                             uint8_t * const         p_buf,
                             uint32_t * const        p_buf_len)
{
    SER_RSP_ENC_RESULT_ONLY(SD_BLE_OPT_SET);
}
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;In&amp;nbsp;&lt;strong&gt;pc-ble-driver\src\sd_api_v6\sdk\components\serialization\application\codecs\ble\serializers\ble_app.c&lt;/strong&gt;&amp;nbsp;&lt;span&gt;there are following implementations of&amp;nbsp;&lt;/span&gt;&lt;strong&gt;ble_opt_set_req_dec&lt;/strong&gt;&lt;span&gt;/&lt;/span&gt;&lt;strong&gt;ble_opt_set_rsp_enc&lt;/strong&gt;&lt;span&gt;&amp;nbsp;functions:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;uint32_t ble_opt_set_req_enc(uint32_t const          opt_id,
                             ble_opt_t const * const p_opt,
                             uint8_t * const         p_buf,
                             uint32_t * const        p_buf_len)
{
    SER_REQ_ENC_BEGIN(SD_BLE_OPT_SET);

    SER_PUSH_uint32(&amp;amp;opt_id);

    field_encoder_handler_t fp_encoder = NULL;
    void const *            p_struct = NULL;

    SER_PUSH_COND(p_opt, NULL);
    if (p_opt)
    {
        switch (opt_id)
        {
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION &amp;lt; 4
            case BLE_COMMON_OPT_CONN_BW:
                fp_encoder = ble_common_opt_conn_bw_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;common_opt.conn_bw);
            break;
#endif
            case BLE_COMMON_OPT_PA_LNA:
                fp_encoder = ble_common_opt_pa_lna_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;common_opt.pa_lna);
            break;
            case BLE_COMMON_OPT_CONN_EVT_EXT:
                fp_encoder = ble_common_opt_conn_evt_ext_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;common_opt.conn_evt_ext);
            break;
            case BLE_GAP_OPT_CH_MAP:
                fp_encoder = ble_gap_opt_ch_map_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.ch_map);
            break;
            case BLE_GAP_OPT_LOCAL_CONN_LATENCY:
                fp_encoder = ble_gap_opt_local_conn_latency_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.local_conn_latency);
            break;
            case BLE_GAP_OPT_PASSKEY:
                fp_encoder = ble_gap_opt_passkey_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.passkey);
            break;
            case BLE_GAP_OPT_AUTH_PAYLOAD_TIMEOUT:
                fp_encoder = ble_gap_opt_auth_payload_timeout_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.auth_payload_timeout);
            break;
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION &amp;lt; 4
            case BLE_GAP_OPT_EXT_LEN:
                fp_encoder = ble_gap_opt_ext_len_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.ext_len);
            break;
#endif
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION &amp;lt; 6
            case BLE_GAP_OPT_SCAN_REQ_REPORT:
                fp_encoder = ble_gap_opt_scan_req_report_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.scan_req_report);
            break;
#endif
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION &amp;lt; 4
            case BLE_GAP_OPT_COMPAT_MODE:
                fp_encoder = ble_gap_opt_compat_mode_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.compat_mode);
            break;
#else
#ifndef S112
            case BLE_GAP_OPT_COMPAT_MODE_1:
                fp_encoder = ble_gap_opt_compat_mode_1_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.compat_mode_1);
            break;
#endif
            case BLE_GAP_OPT_SLAVE_LATENCY_DISABLE:
                fp_encoder = ble_gap_opt_slave_latency_disable_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.slave_latency_disable);
            break;
#endif
#if defined(NRF_SD_BLE_API_VERSION) &amp;amp;&amp;amp; NRF_SD_BLE_API_VERSION == 4
            case BLE_GAP_OPT_COMPAT_MODE_2:
                fp_encoder = ble_gap_opt_compat_mode_2_t_enc;
                p_struct   = &amp;amp;(p_opt-&amp;gt;gap_opt.compat_mode_2);
            break;
#endif
            default:
                SER_ASSERT(NRF_ERROR_INVALID_PARAM,NRF_ERROR_INVALID_PARAM);
            break;
        }

        SER_PUSH_FIELD(p_struct, fp_encoder);
    }

    SER_REQ_ENC_END;
}


uint32_t ble_opt_set_rsp_dec(uint8_t const * const p_buf,
                             uint32_t              packet_len,
                             uint32_t * const      p_result_code)
{
    SER_RSP_DEC_RESULT_ONLY(SD_BLE_OPT_SET);
}
&lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Unfortunately none of functions do have&amp;nbsp;&lt;strong&gt;BLE_GATTC_OPT_UUID_DISC&lt;/strong&gt; option handled.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;How should that code look like for nRF SDK and pc-ble-driver?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363935?ContentTypeID=1</link><pubDate>Wed, 20 Apr 2022 12:50:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:61f45b04-3bf8-46d8-85ad-d35fec42b28b</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Did you add support for the new option (BLE_GATTC_OPT_UUID_DISC) in the serialization library, in&amp;nbsp;ble_opt_set_req_dec()&amp;nbsp;and&amp;nbsp;ble_cfg_set_req_enc()?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363908?ContentTypeID=1</link><pubDate>Wed, 20 Apr 2022 12:15:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5487c413-92e9-47d5-abd2-7e3590c63729</guid><dc:creator>Yuriy Sharamaha</dc:creator><description>&lt;p&gt;Hi Einar,&lt;/p&gt;
&lt;p&gt;So, I have just recompiled the connectivity application from&amp;nbsp;&lt;strong&gt;nRF SDK 15.3.0&lt;/strong&gt;&amp;nbsp;and used&lt;span&gt;&amp;nbsp;the &lt;strong&gt;S140&amp;nbsp;&lt;/strong&gt;&lt;/span&gt;&lt;span&gt;&lt;strong&gt;v7.2.0&lt;/strong&gt; headers. I have also adjusted the linker script to accommodate&amp;nbsp;the larger SoftDevice.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span style="text-decoration:underline;"&gt;Original memory config&lt;/span&gt;:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;MEMORY&lt;br /&gt;{&lt;br /&gt; FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0xda000&lt;br /&gt; RAM (rwx) : ORIGIN = 0x2001ad58, LENGTH = 0x252a8&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span style="text-decoration:underline;"&gt;Updated memory config&lt;/span&gt;:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;MEMORY&lt;br /&gt;{&lt;br /&gt; FLASH (rx) : ORIGIN = 0x27000, LENGTH = 0xd9000&lt;br /&gt; RAM (rwx) : ORIGIN = 0x200198d8, LENGTH = 0x26728&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The compilation succeeded and new connectivity application firmware hex files have been generated.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Then I have used nrfutil to create the upgrade zip package containing new&amp;nbsp;connectivity application firmware hex file and new SoftDevice v7.2.0 hex file.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The device has been programmed successfully and now it appears properly in the device manager.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Moreover,&amp;nbsp;&lt;strong&gt;sd_rpc_open&amp;nbsp;&lt;/strong&gt;API succeeds and&amp;nbsp;&lt;strong&gt;sd_ble_version_ge&lt;/strong&gt;t API returns&amp;nbsp;&lt;strong&gt;subversion_number&lt;/strong&gt; set to 0x100 which corresponds to &lt;strong&gt;SoftDevice v7.2.0&lt;/strong&gt;.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Apparently, the connectivity application and SoftDevice seem to be run fine.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;However,&amp;nbsp;call&amp;nbsp;&lt;strong&gt;sd_ble_opt_set(adapter, BLE_GATTC_OPT_UUID_DISC, &amp;amp;uuid_opt) &lt;/strong&gt;still fails&amp;nbsp;with the same error&amp;nbsp;&lt;strong&gt;0x8001 NRF_ERROR_SD_RPC_ENCODE. &lt;/strong&gt;Am I missing something?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363907?ContentTypeID=1</link><pubDate>Wed, 20 Apr 2022 12:14:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d29eedb-8f83-40bc-b2af-bec90c0fd60f</guid><dc:creator>Einar Thorsrud</dc:creator><description>[quote user="Yuriy Sharamaha"]So, now my main question (and challenge) is how to port &lt;strong&gt;nRF SDK 15.3.0&lt;/strong&gt; to &lt;strong&gt;SoftDevice 7.2.0&lt;/strong&gt;. I would appreciate any help or insights on this.[/quote]
&lt;p&gt;I suggest you refer to the migration document for 7.2.0. This is part of the zip distribution of the SoftDevice. That contains the API changes for the SoftDevice, and you need to follow that back to 6.1.1 and accommodate for any changes to SDK code that is being used.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363864?ContentTypeID=1</link><pubDate>Wed, 20 Apr 2022 10:53:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d9a2dc8-32df-4447-8dde-1ea1d24e2213</guid><dc:creator>Yuriy Sharamaha</dc:creator><description>&lt;p&gt;Hi Einar,&lt;/p&gt;
&lt;p&gt;this is what I was originally doing - I was adding the serialization code for&amp;nbsp;&lt;span&gt;&lt;strong&gt;BLE_GATTC_OPT_UUID_DISC&lt;/strong&gt; option&lt;/span&gt; to &lt;strong&gt;nRF SDK 15.3.0&lt;/strong&gt; and &lt;strong&gt;pc-ble-driver&lt;/strong&gt;.&amp;nbsp;Then in my client application I was attempting to call&amp;nbsp;&lt;strong&gt;sd_ble_opt_set(adapter, BLE_GATTC_OPT_UUID_DISC, &amp;amp;uuid_opt)&lt;/strong&gt;, but it was failing with the error&amp;nbsp;&lt;strong&gt;0x8001 NRF_ERROR_SD_RPC_ENCODE&lt;/strong&gt;. I&amp;#39;ve made an assumption that it fails because I was still using &lt;strong&gt;SoftDevice 6.1.1&lt;/strong&gt; which does not have&amp;nbsp;&lt;strong&gt;BLE_GATTC_OPT_UUID_DISC&lt;/strong&gt; option.&lt;/p&gt;
&lt;p&gt;So, now my main question (and challenge) is how to port &lt;strong&gt;nRF SDK 15.3.0&lt;/strong&gt; to &lt;strong&gt;SoftDevice 7.2.0&lt;/strong&gt;. I would appreciate any help or insights on this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363781?ContentTypeID=1</link><pubDate>Wed, 20 Apr 2022 07:52:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b4f93563-0e57-4b59-97b7-75922d8be2b7</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;There is always a way, provided you are willing to do the effort. There are API changes between major versions of the SoftDevice, so some porting will have to be involved. I suspect the easiest is to stick with SDK 15.3 and the patch form the from pc-ble-driver repo, and use that as a starting point. Then port that to SoftDevice 7.2.0&amp;nbsp;first and get that working. Then add BLE_GATTC_OPT_UUID_DISC to the serialization code on the nRF and the pc-ble-driver. I cannot say exactly how much effort this will take, though.&lt;/p&gt;
&lt;p&gt;An alternative could perhaps be to consider if you can achieve your end goal differently, without using&amp;nbsp;BLE_GATTC_OPT_UUID_DISC.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363684?ContentTypeID=1</link><pubDate>Tue, 19 Apr 2022 16:20:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd759b76-c440-4341-8288-f3f4b846fb51</guid><dc:creator>Yuriy Sharamaha</dc:creator><description>&lt;p&gt;Understood, thank you!&lt;/p&gt;
&lt;p&gt;Is there any way to use SoftDevice v7.2.0 with the connectivity application of v6.1.1? For example, generate the upgrade zip package with SD v7.2.0 and the connectivity app of v6.1.1 and then program the dongle by nrfutil. I need SD v7.2.0 because it supports the BLE_GATTC_OPT_UUID_DISC option.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363668?ContentTypeID=1</link><pubDate>Tue, 19 Apr 2022 15:01:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aeb9643b-ae62-422a-be0f-f016ce87b253</guid><dc:creator>Einar Thorsrud</dc:creator><description>[quote user="Yuriy Sharamaha"]I have applied the patch&amp;nbsp;&lt;strong&gt;nRF5_SDK_15.3.0_connectivity.patch&lt;/strong&gt; to&amp;nbsp;&lt;span&gt;&lt;strong&gt;nRF5_SDK_15.3.0&lt;/strong&gt;, but I did not apply it to&amp;nbsp;&lt;strong&gt;nRF5_SDK_17.1.0&lt;/strong&gt;. Is there any similar patch for&amp;nbsp;&lt;strong&gt;nRF5_SDK_17.1.0&lt;/strong&gt;? Or can I apply &lt;strong&gt;nRF5_SDK_15.3.0_connectivity.patch&lt;/strong&gt;&amp;nbsp;to&amp;nbsp;&lt;strong&gt;nRF5_SDK_17.1.0&lt;/strong&gt;?&lt;/span&gt;[/quote]
&lt;p&gt;No, there is no similar patch for 17.1.0 and you cannot apply the 15.3.0 patch to 17.1.0. SDK 15.3.0 is the latest that is (and will be) supported.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363665?ContentTypeID=1</link><pubDate>Tue, 19 Apr 2022 14:52:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59fba687-c8c0-47f9-b312-a546159ba60a</guid><dc:creator>Yuriy Sharamaha</dc:creator><description>&lt;p&gt;Yes, I have built the connectivity firmware using existing &lt;strong&gt;pc-ble-driver&lt;/strong&gt;. I have noticed that it does not&amp;nbsp; have &lt;strong&gt;sd_api_v7&lt;/strong&gt; folder and does not use &lt;strong&gt;nRF5_SDK_17.1.0.&lt;/strong&gt;&amp;nbsp;That&amp;#39;s why I have modified &lt;strong&gt;CMakeLists.txt&lt;/strong&gt; and &lt;strong&gt;util.cmake&lt;/strong&gt; files to consume the new &lt;strong&gt;nRF5_SDK_17.1.0&lt;/strong&gt;&amp;nbsp;and new &lt;strong&gt;SoftDevice&lt;/strong&gt; id&amp;nbsp;&lt;strong&gt;0x0100&lt;/strong&gt;. After that the folder &lt;strong&gt;sd_api_v7&lt;/strong&gt; is getting created and connectivity firmware hex files are placed there.&lt;/p&gt;
&lt;p&gt;I have applied the patch&amp;nbsp;&lt;strong&gt;nRF5_SDK_15.3.0_connectivity.patch&lt;/strong&gt; to&amp;nbsp;&lt;span&gt;&lt;strong&gt;nRF5_SDK_15.3.0&lt;/strong&gt;, but I did not apply it to&amp;nbsp;&lt;strong&gt;nRF5_SDK_17.1.0&lt;/strong&gt;. Is there any similar patch for&amp;nbsp;&lt;strong&gt;nRF5_SDK_17.1.0&lt;/strong&gt;? Or can I apply &lt;strong&gt;nRF5_SDK_15.3.0_connectivity.patch&lt;/strong&gt;&amp;nbsp;to&amp;nbsp;&lt;strong&gt;nRF5_SDK_17.1.0&lt;/strong&gt;?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363653?ContentTypeID=1</link><pubDate>Tue, 19 Apr 2022 14:13:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:08b1ca47-05c5-47da-a806-55c2685dae16</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Ah, I see. Did you build both connectivity firmwares yourself? If you are interfacing with the pc-ble-driver, you need to build it as specified&amp;nbsp;under &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver#compiling-connectivity-hex-files"&gt;Compiling connectivity HEX files&lt;/a&gt;&amp;nbsp;and include a bunch of patches as described. That is only provided for SDK 15.3. We do not support newer SDK versions for the pc-ble-driver, and do not indent to do so either. Among other things, the patch will adjust the USB PID (0xC00A), so without it the device will not be recognized.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363640?ContentTypeID=1</link><pubDate>Tue, 19 Apr 2022 13:54:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1fa9bb20-205c-477c-a7c4-3d8b1afc84f2</guid><dc:creator>Yuriy Sharamaha</dc:creator><description>&lt;p&gt;Hi Einar,&lt;/p&gt;
&lt;p&gt;Thank you for your response!&lt;/p&gt;
&lt;p&gt;I am changing the SDK version. Previously the connectivity application firmware was built using&amp;nbsp;nRF5_SDK_15.3.0 and SoftDevice of v6.1.1 is part of that SDK. Now I am building the connectivity application firmware using&amp;nbsp;nRF5_SDK_17.1.0 where SoftDevice of v7.2.0 is part of.&lt;/p&gt;
&lt;p&gt;It seems the problem is not with just drivers, the device itself is not functioning -&amp;nbsp;&lt;span&gt;&lt;strong&gt;sd_rpc_open&lt;/strong&gt; API which initializes the SoftDevice module fails with error&amp;nbsp;&lt;b&gt;0x000d NRF_ERROR_TIMEOUT &lt;/b&gt;after an upgrade.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363631?ContentTypeID=1</link><pubDate>Tue, 19 Apr 2022 13:40:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d7377de-abc4-4700-a6d4-9d2ddefa6f90</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This seems related to USB only, so the SoftDevice itself should not be relevant, but the SDK could be. Are you also&amp;nbsp;changing&amp;nbsp;SDK version, or only SoftDevice? Which (two) SDK versions are you using? Also, are there any issues or does this still work and you just&amp;nbsp;wonder why Windows picks one driver in one case and another diver in the other case?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SoftDevice and Application firmware upgrade from 6.1.1 to 7.2.0 issue</title><link>https://devzone.nordicsemi.com/thread/363280?ContentTypeID=1</link><pubDate>Thu, 14 Apr 2022 13:51:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de8ea9e2-0a5a-4d60-83f1-2f4a8ca6246f</guid><dc:creator>Yuriy Sharamaha</dc:creator><description>&lt;p&gt;Attaching the SoftDevice and Application firmware v6.1.1.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/5466.s140_5F00_nrf52_5F00_6.1.1_5F00_softdevice.hex"&gt;devzone.nordicsemi.com/.../5466.s140_5F00_nrf52_5F00_6.1.1_5F00_softdevice.hex&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/connectivity_5F00_4.1.1_5F00_usb_5F00_for_5F00_s140_5F00_6.1.1.hex"&gt;devzone.nordicsemi.com/.../connectivity_5F00_4.1.1_5F00_usb_5F00_for_5F00_s140_5F00_6.1.1.hex&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>