IAR with SDK9.0; files broken

RE: IAR with SDK9.0; files broken

sowmya — Thu, 04 Feb 2016 09:28:52 GMT

Update: The issue is fixed. Thank you for the support.

RE: IAR with SDK9.0; files broken

sowmya — Thu, 04 Feb 2016 09:26:58 GMT

Well I was able to fix issue for setting the breakpoint :). But the following code is not executing:

    SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_8000MS_CALIBRATION, NULL);

    #if defined(S110) || defined(S130) || defined(S310)
    // Enable BLE stack.
    ble_enable_params_t ble_enable_params;
    memset(&ble_enable_params, 0, sizeof(ble_enable_params));
  #if defined(S130) || defined(S310)
   ble_enable_params.gatts_enable_params.attr_tab_size   = BLE_GATTS_ATTR_TAB_SIZE_DEFAULT;
  #endif
   ble_enable_params.gatts_enable_params.service_changed = IS_SRVC_CHANGED_CHARACT_PRESENT;
   err_code = sd_ble_enable(&ble_enable_params);
   APP_ERROR_CHECK(err_code);
  #endif

sd_ble_enable() function is not getting called. I have defined the symbol S110. Do I am missing any settings?

RE: IAR with SDK9.0; files broken

Susheel Nuguru — Thu, 04 Feb 2016 09:22:02 GMT

Sowmya found solution here

RE: IAR with SDK9.0; files broken

Susheel Nuguru — Thu, 04 Feb 2016 08:21:36 GMT

seems like you have flashed the wrong softdevice version, can you please double check that.

RE: IAR with SDK9.0; files broken

sowmya — Thu, 04 Feb 2016 05:00:45 GMT

Update: I tested with your project, no compilation error :) , but application is not running. After run, when I stop, the code is executing at address 0x2506, which is the startup code I think.

RE: IAR with SDK9.0; files broken

sowmya — Thu, 04 Feb 2016 04:44:48 GMT

Hello Aryan,

Now I need to first work with LED_Blinky project. I changed the Target options but breakpoint is not hitting at main :( and it is not allowing to set a breakpoint. Can you provide IAR tool settings guide ?

RE: IAR with SDK9.0; files broken

Susheel Nuguru — Wed, 03 Feb 2016 14:01:37 GMT

You have to select device like below assuming you have QFAC, else select the appropriate one.

I missed to see that your problem is that you are not able to debug!!!??? I set the breakpoints and it is working OK.

RE: IAR with SDK9.0; files broken

sowmya — Wed, 03 Feb 2016 13:32:30 GMT

I had fixed the issue. Now I changed as per your guide, changed General options->Target-> Processor variant Cortex M0 and Device ->NordicSemi nRF51822-QFAA to Core->ARM7TDMI and Device->None. Now getting the error Error[Ta097]: Cannot call intrinsic function "__nounwind __DSB" from Thumb mode in this architecture D:\Keil_v5\ARM\PACK\ARM\CMSIS\4.4.0\CMSIS\Include\core_cm0.h 727

RE: IAR with SDK9.0; files broken

Susheel Nuguru — Wed, 03 Feb 2016 13:20:47 GMT

I have

I just changed Project_settings->Target->Device and added Nordicsemiconductor there. After that it builds ok in SDK9.0 and S110_8.0

I am attaching my project for you just for reference. ble_app_hrs.rar extract this to nRF51_SDK_9.0.0_2e23562\examples\

The project I tried will then be nRF51_SDK_9.0.0_2e23562\examples\ble_peripheral\ble_app_hrs\pca10028\s110\iar

I do not see any of the errors you mentioned :(

RE: IAR with SDK9.0; files broken

sowmya — Wed, 03 Feb 2016 12:34:02 GMT

I tested with LED_Blinky example and I manually added pre-processor in compiler settings. But the board is getting reset after few seconds of the application run. Didn't get the cause for that.

So now I am testing with ble_app_hrs heart-rate application, for this I am getting array is too large error for SOFTDEVICE_HANDLER_INIT function. Found a solution here. If I change BLE_STACK_EVT_MSG_BUF_SIZE to 1, will it effect the project workspace which I am using with keil?

Update: Fixed the error array is too large by adding BLE_STACK_SUPPORT_REQD symbol in compiler settings. Now I am not able to debug. It is not allowing to set breakpoint.

RE: IAR with SDK9.0; files broken

Susheel Nuguru — Wed, 03 Feb 2016 12:28:37 GMT

Which example project did you try? I can try to see if I see the same thing. (I am OoO rest of this week after today, so I will wait for your answer two more hours)