I need help with converting any example from Keil to SES

[JacobBudny]

Hello,

I've been trying for days to convert any example from Keil to SES, I have road probably every question here on the dev zone but I am unable to fix this, I ever specially install windows on my mac to try if there it would work.

So, I have done everything from official nordic documents, I've been through several problems which I happily solve, but that I'm not able to.

I get those errors:

unplaced section: .log_dynamic_data_app [nrf_log_frontend.o], size=12, align=4

undefined symbol: __SRAM_segment_end__

undefined symbol: __start_log_const_data

undefined symbol: __start_log_dynamic_data

undefined symbol: __stop_log_const_data

I'm working on latest SEGGER, I have tried latest SDK, also 14.2 . The same errors. 

Thanks for reply

[Nguyen Hoan Hoang]

It seems like you are not using the correct startup code.  Startup code and linker scripts are different.  Startup code and linker script go in pair. You need to use the one made for SES.

[JacobBudny]

Hey, I have followed instructions from here https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/segger-embedded-studio-a-cross-platform-ide but its a little bit outdated since now there is SES 4.50.

Maybe there is a tutorial of how to rewrite programs from Keil to SES? Please like, I have spent so much hours for that, everyone seems get it done, and I am unable to transfer even Blinky example... 

[JacobBudny]

But if not moving there is still force acting on the Z axis, which should be something about 9,8 and even with scale 16 I am getting 8 only, and 16 is the biggest scale. 

Okay I see it now, and that is causing NAN in all of that values:


How can I set up this range?

[Nguyen Hoan Hoang]

gravity is 1g not 9g

[JacobBudny]

Yes yes, but I am talking m/s^2, and 1 g = 9,8 m/s^2. We misunderstood each other. I was thinking earlier that accdata is in m/s^2 unit not g unit, sorry. If it's in g unit now it seems fine. 

How about the gyro?

[Nguyen Hoan Hoang]

Didn't you read my message.  I said gyro was missing the rage setting in the driver.

The accel data gives you in g as described in the data structure comment.

[JacobBudny]

Yes I did read. But what can I do to fix it? I was reading about sensor acc range and I found that:

The ADC range is the maximum and minimum ADC input (e.g., 0 to +3.3V). The ADC resolution is the smallest distinguishable change in input (e.g., 3.3V/4096, which is about 0.81 mV). The resolution is the change in input that causes the digital output to change by 1.

So it means that, something in my sensor is broke and is not delivering this values? Or there is something wrong with the code?

[Nguyen Hoan Hoang]

I just push new change. Could you check it out ?

Where did you get those ADC values ? Are they from the MUP datasheet ?

[JacobBudny]

I updated it, and while building debug and realese for IOsonata_nRF52832 for eliminating error from gcc (as you said before) I got this error:

make: *** No rule to make target `/Users/jacobbudny/Desktop/DEVELOPMENT/IOsonata/ARM/Nordic/src/i2s_nrfx.cpp', needed by `src/coredev/i2s_nrfx.o'.  Stop.

[Nguyen Hoan Hoang]

it's something i am working on unfinished.  Could you delete it from the project.

[JacobBudny]

Okay I deleted, Now when I am compiling motion sensor demo I got:

/Users/jacobbudny/Desktop/DEVELOPMENT/IOsonata/exemples/sensor/mot_sensor_demo.cpp:46:10: fatal error: timer_nrf5x.h: No such file or directory

   46 | #include "timer_nrf5x.h"

      |          ^~~~~~~~~~~~~~~

compilation terminated.

make: *** [src/mot_sensor_demo.o] Error 1

[Nguyen Hoan Hoang]

it has been renamed to timer_nrfx.h