Nordic didn't update custom characteristic after porting from Keil to SES

RE: Nordic didn't update custom characteristic after porting from Keil to SES

grabro — Tue, 26 May 2020 11:20:04 GMT

Looks like I solved the problem by changing the Optimization Level from Level 2 to Level 0.

But still curious on why this would change the performance behavior of the device. Any information on this will be much appreciated! =)

RE: Nordic didn't update custom characteristic after porting from Keil to SES

grabro — Tue, 26 May 2020 10:53:43 GMT

Hi Joakim,

Strange things happen when I am using the SES IDE:

Case 1:

Sometimes the system is able to trigger the flag (used to indicate BLE transmission activity) but sometime doesn't.

// Function for handling BLE events.
static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)
{
    uint32_t err_code;

    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
            NRF_LOG_INFO("Connected");
            err_code = bsp_indication_set(BSP_INDICATE_CONNECTED);
            APP_ERROR_CHECK(err_code);
            m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
            err_code = nrf_ble_qwr_conn_handle_assign(&m_qwr, m_conn_handle);
            APP_ERROR_CHECK(err_code);
            ble_flag = true;
            break;

        case BLE_GAP_EVT_DISCONNECTED:
            NRF_LOG_INFO("Disconnected");
            // LED indication will be changed when advertising starts.
            m_conn_handle = BLE_CONN_HANDLE_INVALID;
            ble_flag = false;
            break;

        case BLE_GAP_EVT_PHY_UPDATE_REQUEST:
        {
            NRF_LOG_DEBUG("PHY update request.");
            ble_gap_phys_t const phys =
            {
                .rx_phys = BLE_GAP_PHY_AUTO,
                .tx_phys = BLE_GAP_PHY_AUTO,
            };
            err_code = sd_ble_gap_phy_update(p_ble_evt->evt.gap_evt.conn_handle, &phys);
            APP_ERROR_CHECK(err_code);
        } break;

        case BLE_GAP_EVT_SEC_PARAMS_REQUEST:
            // Pairing not supported
            err_code = sd_ble_gap_sec_params_reply(m_conn_handle, BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP, NULL, NULL);
            APP_ERROR_CHECK(err_code);
            break;

        case BLE_GATTS_EVT_SYS_ATTR_MISSING:
            // No system attributes have been stored.
            err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);
            APP_ERROR_CHECK(err_code);
            break;

        case BLE_GATTC_EVT_TIMEOUT:
            // Disconnect on GATT Client timeout event.
            err_code = sd_ble_gap_disconnect(p_ble_evt->evt.gattc_evt.conn_handle,
                                             BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
            APP_ERROR_CHECK(err_code);
            break;

        case BLE_GATTS_EVT_TIMEOUT:
            // Disconnect on GATT Server timeout event.
            err_code = sd_ble_gap_disconnect(p_ble_evt->evt.gatts_evt.conn_handle,
                                             BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
            APP_ERROR_CHECK(err_code);
            break;
        
        case BLE_GATTS_EVT_HVN_TX_COMPLETE:
            uart_busy_flag = false;
            packet_sent++;
            break;
        
        default:
            // No implementation needed.
            break;
    }
}

In which that ble_flag is declared as global variable:

volatile static bool ble_flag = false;

Case 2:

In the case when ble_flag is triggered in "Release" project configuration, the system will return err_code = 0x05.

Also, it won't return any error in "Debug" project configuration, which means that the system can send data to my phone without any problem.

All of these problem didn't exist when I am using Keil.

Looks like there are several misconfigurations here. I will need to check again with my code and update soon.

Thanks.

RE: Nordic didn't update custom characteristic after porting from Keil to SES

Joakim Jakobsen — Tue, 26 May 2020 08:45:46 GMT

You are correct. If you are not using an older nRF SDK without native support for SES I wouldn't recommend following the guide I linked to.

I would recommend using a template SES project instead of actually migrating the example.
Do you see any errors or abnormal behavior if you debug the application with SES?

Br,
Joakim

RE: Nordic didn't update custom characteristic after porting from Keil to SES

grabro — Tue, 26 May 2020 08:35:21 GMT

Thanks Joakim,

I am using nRF SDK 16.0.0.

I had read the guide that you provided, and thought that it would be easier by copying and pasting my custom source code directly to the provided SES template file. (I used ble_app_uart example as template). Have also added required paths and updated memory size and location in the project settings.

Perhaps I can try to do the migration and see the result again. Will update soon.

RE: Nordic didn't update custom characteristic after porting from Keil to SES

Joakim Jakobsen — Tue, 26 May 2020 08:12:42 GMT

Hi.

Which version of the nRF5 SDK are you working with?

We have a guide on migrating an existing project from Keil -> SES:
https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/segger-embedded-studio-a-cross-platform-ide

Br,
Joakim