Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Build and Run with SEGGER Embedded Studio (SES) v6.20a on nRF5 SDK 17.1.0 and S140 7.2.0 on nRF52840

Hi DevZone,

I have recently updated:

  • nRF5 SDK to 17.1.0 from 15.3.0
  • S140 to 7.2.0 from 6.1.1
  • SES to v6.20a from 4.16

The SoftDevice now fails to initialize when using the "Build and Run" option with SES.

The code initializes without issue if I:

  • Use Programmer v2.3.3 from nRF Connect for Desktop v3.10.0
  • If I Power Cycle the hardware after each flash of the .hex files
  • If I "Build and Debug" with SES

Is this a known issue, and could it potentially be a timing issue?

Code that fails:

void ble_stack_init(void)
{
    ret_code_t err_code;

    err_code = nrf_sdh_enable_request();
    APP_ERROR_CHECK(err_code);

    // Configure the BLE stack using the default settings.
    // Fetch the start address of the application RAM.
    uint32_t ram_start = 0;
    err_code = nrf_sdh_ble_default_cfg_set(BLE_CONN_CFG_TAG, &ram_start);
    APP_ERROR_CHECK(err_code);

    // Enable BLE stack.
    err_code = nrf_sdh_ble_enable(&ram_start);
    APP_ERROR_CHECK(err_code);

//    // NO OBSERVERS AT THIS POINT 
//    // Register a handler for BLE events.
//    NRF_SDH_BLE_OBSERVER(m_ble_observer, APP_BLE_OBSERVER_PRIO, ble_evt_handler, NULL);
}

Specifically the call to nrf_sdh_enable_request() returns with error code NRF_ERROR_INVALID_STATE (0x00000008).

This should mean that the SoftDevice is already initialized when reading the documentation. However, preceding the nrf_sdh_enable_request() call with a nrf_sdh_is_enabled()

tells me that it is not.

Comparing with example projects:

I have compared to the example projects given in SDK 17.1.0, and the initialization code for the BLE stack seems unchanged between versions 17.1.0 and 15.3.0. 

Also, I have tried building and running the peripheral example from SDK 17.1.0 "usbd_ble_uart_freertos" both on our hardware and an nRF52840-DK, which fails with the same error code.

So, even with code directly from the SDK and on multiple hardware the issue is the same.

Thanks in advance.

Br. Casper

Parents
  • Hello,

    I added the line "nrf_sdh.c line 214, err code %02x", err code" outside the if, since it didn't trigger otherwise:

    from your log it seems that it returns 08 from the initial run, unless the line "app: USBD BLE UART example started is not the first thing that is printed when you run your application (If there are more logs above that).

    Let us take two steps back. What Hardware are you using? nRF52840 DK? did you actually try to download the file that you uploaded here?  (don't copy it from your already existing project folder, but download it and unzip it) and copy it into an unmodified SDK v17.1.0. Do you still see the same? If so, I find it very strange that we see different behavior if we are running the same FW on the same HW and get two different outcomes. Have you tried to run it on another DK (another nRF52840 DK), and/or another computer? 

    Seeing as you are trying to port a project/application, please make sure that you do not copy any files outside the folder that you sent me from the old SDK. 

    If you try to unzip the file that you uploaded here into another unmodified SDK, and it still works. Please try to think if there are any details that you didn't mention that you did, other than compiling and running the sample in SES. Even if you think it is not of importance, it may make a difference, such as copying some old files from the old SDK because you thought they were needed.

    You can also try to delete and reinstall SES (there are some files that are not part of the SDK as well, that you may have changed). 

    If that doesn't lead anywhere, perhaps you can try to zip your entire SDK and upload it here. You may need to delete the rest of the examples if the file is too big to upload on DevZone. 

    BR,
    Edvin

Reply
  • Hello,

    I added the line "nrf_sdh.c line 214, err code %02x", err code" outside the if, since it didn't trigger otherwise:

    from your log it seems that it returns 08 from the initial run, unless the line "app: USBD BLE UART example started is not the first thing that is printed when you run your application (If there are more logs above that).

    Let us take two steps back. What Hardware are you using? nRF52840 DK? did you actually try to download the file that you uploaded here?  (don't copy it from your already existing project folder, but download it and unzip it) and copy it into an unmodified SDK v17.1.0. Do you still see the same? If so, I find it very strange that we see different behavior if we are running the same FW on the same HW and get two different outcomes. Have you tried to run it on another DK (another nRF52840 DK), and/or another computer? 

    Seeing as you are trying to port a project/application, please make sure that you do not copy any files outside the folder that you sent me from the old SDK. 

    If you try to unzip the file that you uploaded here into another unmodified SDK, and it still works. Please try to think if there are any details that you didn't mention that you did, other than compiling and running the sample in SES. Even if you think it is not of importance, it may make a difference, such as copying some old files from the old SDK because you thought they were needed.

    You can also try to delete and reinstall SES (there are some files that are not part of the SDK as well, that you may have changed). 

    If that doesn't lead anywhere, perhaps you can try to zip your entire SDK and upload it here. You may need to delete the rest of the examples if the file is too big to upload on DevZone. 

    BR,
    Edvin

Children
No Data
Related