Wrong initialization value in static variables

RE: Wrong initialization value in static variables

Loosli — Mon, 19 Feb 2018 09:50:46 GMT

Thank you for your fast answer!

I tried Splitting the linker script in two parts, like in an old one that already worked and the initalisation works now fine.

The bss-sections are getting erased and the Reset_Handler is called as it should.

Values of the static variables are now as they should be.

Problem with enabling the Softdevice stil exists, but I think this should be questioned in an other thread, as it has nothing to do with static variables...

Thank you for your Support!

I'll mark your answer as solution.

Best regards,

Dominic

RE: Wrong initialization value in static variables

ekrashtan — Mon, 19 Feb 2018 09:44:46 GMT

Ok, just try to add symbol __STARTUP_CLEAR_BSS to your build and check again. Probably you use some library which already has .bss initialization on startup, but with different bss address, and this symbol will enable additional clean-up of your bss.
Also, check if your gcc_startup_nrf52.S compiled and linked.

RE: Wrong initialization value in static variables

Loosli — Mon, 19 Feb 2018 07:54:55 GMT

If desired, I can provide full linkerscript, .map-file, startup-code and makefile...

RE: Wrong initialization value in static variables

Loosli — Mon, 19 Feb 2018 07:52:44 GMT

Hi ekrashtan,

I tried to check your hints but when I set a breakpoint in the startup-file at the very beginning of the Reset_Handler, then this Breakpoint is never hit.

Some lines below the Reset_Handler I saw this comment in the startup code:

/* Call _start function provided by libraries.
 * If those libraries are not accessible, define __START as your entry point.
 */

Could this be a Problem, if i don't set this correctly?

__bss_start__ is at 0x200021fc

__bss_end__ is at 0x200035dc

m_nrf_sdh_enabled is at 0x20003368

So this variable is located between bss_start and bss_end.

RAM ORIGIN is set to 0x20002088 in linkerscript, as the correct address could only be known after the first enable of the softdevice as far as i know. This setting is made according to the ble_app_template from the sdk.

Best regards

Dominic

RE: Wrong initialization value in static variables

ekrashtan — Thu, 15 Feb 2018 07:53:29 GMT

All static variables are located in .bss segment. By default in startup code you should erase .bss section of RAM before code start.

FALSE value equal to 0, so I suppose your startup code has wrong init sequence. Please set the breakpoint at Reset_Handler address and check if _bss_start__ and __bss_end__ have the correct value. Also in .map file address of m_nrf_sdh_enabled shoul be between these values.

RE: Wrong initialization value in static variables

Loosli — Thu, 15 Feb 2018 06:46:57 GMT

Does anyone else have some hints or recommendations?

RE: Wrong initialization value in static variables

Loosli — Thu, 08 Feb 2018 13:02:10 GMT

Hi Kenneth,

Toolchain and Debugging are working fine with my Eclipse setup.

I have some code which is executed before interfacing with the softdevice and this part is running fine and can be debugged without any Problems.

Thanks for the hint about SES. I'll check this out as soon as possible. But I would still prefer to get the code working within Eclipse, as this IDE is used also for other Projects in our Company.

Best regards,

Dominic

RE: Wrong initialization value in static variables

Kenneth — Thu, 08 Feb 2018 12:53:32 GMT

Hello,

I do not have a solution for you problem, but hopefully someone here in the open forum have experienced the same and may help you.

I would like to make a recommendation in general, because I see many issues using Eclipse, such as:

Issues to integrate toolchain in Eclipse
Issues setup debugging in Eclipse
Issues setup project settings in Eclipse

Most of issues are caused by Eclipse is not natively support in nRF5 SDK, and there is no plan to do so.

So instead, have you considered using SEGGER Embedded Studio (SES) for development?

Latest nRF5 SDK releases do support SES and some of the advantages using SES are:

SDK examples are setup with SES projects ready to compile and run
Debugger is integrated
GCC compiler
Multi-platform (Linux, Windows, OSX)
No code limitations using nRF devices for development

For more information, also check out: https://www.segger.com/products/development-tools/embedded-studio/

Best regards,
Kenneth