Linker giving error when building the ble_app_alert_notification_pca10028_s130

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Simonr — Wed, 25 May 2022 14:06:48 GMT

Error code 0x04 is an NRF_ERROR_NO_MEM, pointing to there not being enough memory available. You say that you have changed the RAM_START and FLASH_START, macros, but did you also edit the RAM and FLASH_SIZE to match these values? As explained in the RAM and Flash memory adjustment blog post, the size should be set to be the device's total RAM/Flash minus the RAM_START and FLASH_START.

Additionally, it's not generally a good idea to step through the SoftDevice functions/initialization, as some of them are time sensitive and will time out returning errors if they aren't run at run-time.

Best regards,

Simon

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Wed, 25 May 2022 08:43:06 GMT

Hi Simon,

Sorry for the delay in responding.

I wanted to track the changes I did from the beggining:

I started again by importing the project ble_app_proximity.

1. I followed the importing procedures as described above.

2. I imported the flash_placement.xml as shown.

3. I was getting the linking errors. I realized that I had to change "flash1" to "flash" and "ram1" to ram" in the memory placement macro in the project options.

4. In the ses_nrf51_startup.s file, I had to change, "__SRAM_segment_end__" to "__RAM_segment_end__".

(with step 3 and step4", all the linker errors went away)

5. I also made changes to the Section placement macros to ensure RAM_START and FLASH_START as per the s130, 2.0.1 version guidelines.

With this I was able to compile and link the application successfully

Now, when I flashed the softdevice and then started the debugger, the application got flashed.

When I started stepping through the main program, at "ble_stack_init" when I stepped into this function and continued stepping inside the "ble_stack_init" function, when I did "softdevice_enable()", the return value always shows error code "0x04" and the application goes into fault.

Can you please tell me what I could be doing wrong? Thank you very much for your help. (There were no changes made to the code)

regards,

Rajkumar

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Simonr — Mon, 09 May 2022 08:27:47 GMT

Glad to hear you were able to flash the device now. When the ble_stack_init() returns error code 8, which means it is in an "invalid state", that generally means that the BLE stack is already enabled, and you're trying to enable it again it seems. Are you calling it multiple times, or what?

What kind of error are you seeing when the peer_manager_init() fails? What changes did you make between the first and second time you flash the SoftDevice and application code to your nRF51?

Best regards,

Simon

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Fri, 06 May 2022 16:07:50 GMT

Hi Simon,

I made the changes to the Section placement macros as shown in attached file. I also made changes to the memory segment macros as attached in the 2nd file.

However, when I flash the 2.0.1 Softdevice hex file(using Nrfgo studio) and then use "Debug" menu option in EMbedded studio to run the application(app_ble_ancs_c),

1. First time I run the debugger after flashing the soft device, the program stops and main and then after a few functions, the ble_stack_init runs through successfully but then fails either at peer_manager_init() or later.

2. The 2nd time and after that, when I run the debugger after flashing the softdeviec code and running the debugger, the function ble_stack_init() always gives error code 8 at the app_error.c.

I have not been able to see the bluetooth device using my phone bluetooth scanning even once.

The failure seems to happen at sd_softdevice_enable() which causes the fault.

The clock use is the external crystal. There is no change made to the example code.

Please let me know where I could be going wrong.

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Simonr — Fri, 06 May 2022 08:29:24 GMT

Hi again Rajkumar

Okay, if your flash_placement file is now set up correctly, you also need to set up RAM and Flash memory segments in your project settings as explained in this blog post. Remember to select the Common configuration in the project options window.

Best regards,

Simon

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Fri, 06 May 2022 05:38:12 GMT

Hi Simon,

I did as you suggested(importing a project) from scratch. I imported a new project(ble_app_proximity). I did all the import steps you mentioned and did a compile.

I am now getting some linker errors. Please see attached file.

I am using Nordic Segger Embedded studio version 5.68 from the following site:

https://www.nordicsemi.com/Products/Development-tools/Segger-Embedded-Studio/Download?lang=en as suggested by my team member.

Please let me know what I should do.

regards,

Rajkumar

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Thu, 05 May 2022 17:30:16 GMT

Hi Simon,

Actually I was able to completely build the project by changing the "__RAM_segment_end__" reference to "__RAM1_segment_end__". Hope that is fine.

However, When I tried the s130 softdevice 2.0.1 with the peripheral example in the 12.3.0 SDK, the soft device initialization returns error code 8.

My device kit is an nrf51422 device. From the compatibility matrix I read that for nrf51422, the peripheral examples are compatible with S110 softdevice and the (central and peripheral) examples are compatible with S130.

Is that true?

So for trying out a peripheral example in the 12.3.0 SDK, I would need S110?

Thanks.

best regards,

Rajkumar

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Simonr — Thu, 05 May 2022 07:41:23 GMT

Why exactly are you changing stuff in the flash placement file? Is there a reason you set the RAM name to RAM1? This is only necessary when updating to SDK v17.0.2, so please revert this change. This likely causes a conflict with where where the RAM name "RAM" is used define the RAM segments, which is why you're getting this new error.

Next for your actual issue, I think that is due to missing a step somewhere in the SES import guide https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/segger-embedded-studio-a-cross-platform-ide. Can you double check that you for example have done the Adding nRF5 MDK files section correctly?

Download ses_nrf51_startup.s and save it into NRF5_SDK/components/toolchain/embedded_studio/ (create the folder)
Remove Cortex_M_Startup.s from the Internal Files folder in the Project Explorer
Right click the Internal Files folder and select Add Existing File...
In NRF5_SDK/components/toolchain/ select system_nrf51.c
Do the same for NRF5_SDK/components/toolchain/embedded_studio/ses_nrf51_startup.s
Select Project -> Edit Options... and then select the Preprocessor tab
Add ../../../../../../components/device to the User Include Directories field to include the device header files in our Embedded Studio project

Best regards,

Simon

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Wed, 04 May 2022 09:45:43 GMT

Hi Simon,

Can you please clarify the above? Thanks.

regards,

Rajkumar

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Wed, 04 May 2022 02:11:34 GMT

Hi Simon,

After the last error of "

cannot find run section .fast_run referenced in fast,

I changed the "RAM_NAME=RAM" to "RAM_NAME="RAM1" and now I am getting the following error:

undefined reference to `__RAM_segment_end__'

I am attaching my last flash_placement file here for your reference. This error is not going away. Please check this one.devzone.nordicsemi.com/.../7651.flash_5F00_placement.xml

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Wed, 04 May 2022 02:06:19 GMT

Hi Simon,

Sorry, I noticed that I had #defined my "SRAM_segment_end__" to resolve the previous undefined reference error. Now I followed the flash_placement steps and have renamed FLASH to FLASH1 and SRAM to SRAM1.

I am getting the following error now:

cannot find run section .fast_run referenced in fast

Here, attached is my flash_placement.xml. Can you please tell me what is wrong? Thanks.devzone.nordicsemi.com/.../4606.flash_5F00_placement.xml

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Tue, 03 May 2022 14:05:41 GMT

Hi Simon,

Actually I was able to finally flash the softdevice-130 using the nrfgo. I am using nrf51422xxxac.

I was able to then flash the application using the debugger. However the ble_stack_init() function when it calls sd_softdevice_enable, hits the app_error handler function with error code 8. I have not made any changes to the application, so I was wondering why I am getting this error all the time. I have tried multiple times. I have also tried with other applications.

My RAM and flash settings are:

FLASH1 RX 0x1B000 0x00025000;RAM1 RWX 0x200013C8 0x00006c38

Please tell me where I am going wrong. Thanks.

regards,

Rajkumar

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Simonr — Tue, 03 May 2022 11:22:29 GMT

The nRFGo Studio app is outdated at this point and it's strongly recommended using the Programmer app in the nRF Connect for Desktop Programmer application instead.

Best regards,

Simon

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Tue, 03 May 2022 03:03:25 GMT

Hi Simon,

Please ignore last entry. I was using a wrong thumb_crt0.s. Now the program is compiling and linking correctly. But when I try to flash the softdevice 130 using the hex file provided, I am getting an error, please see attached. Please let me know what I should do. Thanks again.

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Tue, 03 May 2022 02:42:01 GMT

Hi Simon,

I was able to resolve the linker errors. Now I am getting one more "undefined symbol" error. I was wondering where to define the "_start" symbol. The error file is attached. Can you please see? Thanks.

regards,

Rajkumar

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Simonr — Tue, 26 Apr 2022 05:55:02 GMT

Hi, did you generate a flash_placement.xml file and thumb_crt0.s file for your project? These will need to be added in your project folder. How to do so is discussed in detail here.

Best regards,

Simon

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Rajkumar V — Mon, 25 Apr 2022 06:00:13 GMT

Hi Simon,

I was able to do the "Import Section Placement" after editing the "Section placement location" under project options.

However the linker errors are still there. Can you please help as soon as you can. I am currently stuck for a while now and really need your help.Thanks.

regards,

Rajkumar

RE: Linker giving error when building the ble_app_alert_notification_pca10028_s130

Simonr — Tue, 19 Apr 2022 10:46:40 GMT

Hi Rajkumar

You should be able to activate a free SES license if you have an nRF product, so please try activating your SEGGER license and see if this Import Section Placement option is added then. If not it might have been moved in one of the later SES updates, as I think the Import option should be available somehow.

Best regards,

Simon