This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Problem connection to centrals to one peripheral

Hello,

I need help. I cannot see my earlier ongoing ticket!? I have been working With it for the last couple of Days and today i was asked to share my Project but now the whole ticket is gone:( What to do, do i need to do it all again or can you guys pick it up somewere?

/Kalle

Parents Reply Children
  • I am getting a linker error: "undefined symbol m_app_twi" in the file mma8552fc.c. The file includes globals.h, where the variable m_app_twi is declared as an extern const. I can see that the definition of m_app_twi is inside m_applicationInit.c, and according to this thread, I would think this should work.

    Did you get this error? Where did you place your project, what SDK did you use and what version of Keil did you use?

    Best regards,

    Simon

  • I didnt have any errors, maybe something With paths..

    I have my Project under c:\nRF_13.0.0

    So the SDK is 13.0.0 and i am currently running KEIL V5.22.0.0. (i am now migrating all our Projects to IAR). 

    If you want i can build a new Project without m_app_twi but maybe it is good to have Everything included.

  • I got rid of the issue regarding m_app_twi by placing the definition APP_TWI_DEF() inside globals.h instead.

    The reason sd_ble_gap_adv_start() failed with 0x3001 (BLE_ERROR_NOT_ENABLED) is because the function PMBLE_ble_stack_init()-->softdevice_enable()-->sd_ble_enable() failed with 0x04 (NRF_ERROR_NO_MEM). 

    This can be resolved by adjusting the values RAM_START and RAM_SIZE. To figure out what to adjust it to you can enable logging and check the NRF_LOG_WARNING(..) in PMBLE_ble_stack_init()-->softdevice_enable().

    I adjusted RAM_SIZE to  0xDA64 and RAM_START to 0x20002CD8 and the error messages disappeared.

    Best regards,

    Simon

  • How did you enable the logging? I dont get it to work....What do you mean with check the NRF_LOG_WARNING(..)..This things are  new to me:)

    Can you also attach the hex file of your build?

    /Kalle

  • Isnt it just to check the value of ram_start after that the function

        err_code = softdevice_app_ram_start_get(&ram_start);

    In the debugger this gives me the ram_start adress of: 0x20002598 which also is the same
    number that I can see in the "Options for target..." in keil IRAM1 ? How does the numbers in Keil "options for target" correlate with the ones in the code?

Related