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]

Okay, I checked the user guide for my port, and SDA -> 26, SCL ->27. So I connect it. Also of course I connected VCC to 3.3V on my board and GND to GND. 



I am unable to see any i2c pins defined in board.h I really do not understand What do you mean by that it's defined "above" but I assume that if my user guide says its 26,27 so I need to connect it to those and maybe its not need to be defined in board.h yes? 

I am still getting the same error. 

[Nguyen Hoan Hoang]

Are you using the BlueIoThingy or another example ?  The board.h I was referring to is the one in the BlueIOThingy example.  If you use a different project, you can take the I2C setup from the BlueIOThingy example to creat the interface object.  See also this I2C example

https://github.com/IOsonata/IOsonata/tree/master/exemples/i2c

You should not defined in the SPI because it will initialize those pins as SPI.

[JacobBudny]

I dropped BlueIOThingy and said that I will try for the beginning to set up Motion Sensor Demo:
https://github.com/IOsonata/IOsonata/tree/master/ARM/Nordic/nRF52/nRF52832/exemples/MotionSensorDemo

So now I'm trying to get raw values from mpu9250 by using Motion Sensor Demo example. 

[JacobBudny]

So Am I able to get raw values from mpu2950 in Motion Sensor Demo example over I2C/SPI ? Which would you recommend on this example and always I2C or SPI? I heard that magnetometer from mpu9250 is not working with SPI. 

[Nguyen Hoan Hoang]

The MPU-9250 can be interfaced either SPI or I2C. You choose how you want to use it.  Check the data sheet of the MPU for pins configuration. The IOsonata driver supports both mode.

[JacobBudny]

Okay, so lets start again.

I want to get Motion Sensor Demo example to get working with MPU9250 with NRF 5 Dev Board.

I imported the project from IOSsonata library. 

Now. 

What Need to be change in mot_sensor_demo.cpp and board.h to get this example to work with mpu9250 and get it to stream data to eclipse terminal by printf ?

I checked the pinout of my board, and found SCL, SDA is 26,27 and I have connected it. Devboard + mpu9250 are connected and ready. 

Doing Run. I get "Failed initializing hardware" 
Doing Debug, I get:

[Nguyen Hoan Hoang]

You need to create an I2C object then pass it to the init of the MPU object.  

Instead of 

res = g_MotSensor.Init(s_AccelCfg, &g_Spi, &g_Timer);

replace the g_Spi with your g_I2c object you created.

res = g_MotSensor.Init(s_AccelCfg, &g_I2c, &g_Timer);

See also the TPHDemo how to select between SPI & I2C to interface with the environmental sensor.

[JacobBudny]

I did that and I can't build:

/Users/jacobbudny/Desktop/DEVELOPMENT/IOsonata/exemples/sensor/mot_sensor_demo.cpp:254:39: error: 'g_I2c' was not declared in this scope

  254 |   res = g_MotSensor.Init(s_AccelCfg, &g_I2c, &g_Timer);

      |                                       ^~~~~

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

"make all" terminated with exit code 2. Build might be incomplete

So in mot_sensor_demo.cpp there is no i2c communication option at all yes? I need to add it, to get it to work?

If I use SPI to communicate with MPU9250 all of it will be simpler or not? Because really, I do not even know where to start if I would need to write i2c communication for mpu9250 for this example. 

Maybe you can suggest any simpler way? Like I spent a week now and nothing works. 

[Nguyen Hoan Hoang]

Have you looked at the TPHDemo example ?

https://github.com/IOsonata/IOsonata/blob/master/exemples/sensor/env_tph_demo.cpp

The simplest way is to buy the sensor board https://www.crowdsupply.com/i-syst/blyst-nano,  The examples work with that board directly.

[JacobBudny]

Yes I am looking over right now and trying to understand:

static const I2CCFG s_I2cCfg = {

0, // I2C device number

{

{I2C0_SDA_PORT, I2C0_SDA_PIN, I2C0_SDA_PINOP, IOPINDIR_BI, IOPINRES_PULLUP, IOPINTYPE_OPENDRAIN},

{I2C0_SCL_PORT, I2C0_SCL_PIN, I2C0_SCL_PINOP, IOPINDIR_OUTPUT, IOPINRES_PULLUP, IOPINTYPE_OPENDRAIN},

},

100000, // Rate

I2CMODE_MASTER,

5, // Retry

0, // Number of slave addresses

{0,}, // Slave addresses

true, // DMA

false, // Use interrupt

7, // Interrupt prio

NULL // Event callback

};

I2C g_I2c;

#define TPH_I2C // To use I2C interface ---> If I change to TPH_SPI it would be using I2C yes?

#ifdef TPH_I2C

DeviceIntrf *g_pIntrf = &g_I2c;

#else

DeviceIntrf *g_pIntrf = &g_Spi;

#endif

That means defining I2C yes?

SO I need to copy that and paste that to the motion_sensor_demo.cpp?
And It should work?