prj.conf definition is not activated on SES

[James_Lee_K]

Hi, there

I'm tring to use nRF9160 bh1749 example code.

As you know, there is example code about bh1749 in <Install Folder>/nrf/samples/sensor/bh1749.

And there are many definitions in prj.conf file.

CONFIG_LOG=y
CONFIG_I2C=y
CONFIG_SENSOR=y
CONFIG_BH1749=y
CONFIG_BH1749_TRIGGER=y

I tried to build this example by command window and SES.

When i'm done by command window, Below is my result.

Alternatively, if this build by SES, the result is different.

I checked why output size is different.

I figured out that  CONFIG_BH1749_TRIGGER is not activated on SES like below.

Does anyone know why this kinds of thing happnens?

[Håkon Alseth]

Hi,

 

Could you try re-importing the project after adding the entry to prj.conf? Remember to clean the folder.

It might be that segger isn't able to catch the new addition to your configuration.

 

Kind regards,

Håkon

[James_Lee_K]

Hi, Hakon

Before i add my comment, i found out that I should use board selection as nrf9160_pca20035.

not nrf9160_pca20035ns.

So i re-stared with this board selection.

I followed your advice. 

I used command window to clean directory.

>> west build -t pristine

But The result is same.

Below is my project start configuration of SES.

And i had a test to figure out reason.

I changed bh1749_trigger config on SES config wizard.

1. if i disabled bh1749_trigger on config wizard of SES, Below is my compilation result.

2. if i re-enable bh1749_trigger on config wizard, below is my test result.

It seems that bh1749_trigger defintion is activated.

But As i explained first question, this definion is not activated on SES window like this.

Coud you give any advies more?

[Håkon Alseth]

Hi,

 

James_Lee_K said:

But As i explained first question, this definion is not activated on SES window like this.

Unfortunately, SES isn't able to pick up on the configuration header in the indexing process. If the symbol is set in your .config file, then its enabled. 

 

Kind regards,

Håkon

[savenlid]

Hi Håkon,

Can I assume you dont use SES internally at Nordic.
Its not working very well.

Also lot of other problems that could not likely have gone under the radar at Nordic if used daily.

Setting breakpoints get marked "?"  "no-code", meaning SES thinks there is no code present where you want to set the break-point.

But it is.
Sometimes SES marks the break-point ok, but then turns it into a "?" as soon as you try to debug.
Also SES constantly wants to rebuild, and always compiles everything over and over again.

[Håkon Alseth]

Hi,

 

We are unfortunately aware that we are having issues with SES Nordic edition, and I apologize for the inconvenience this is causing.

I can assure you that we use SES, which is the reason I know about the workarounds for these issues.

If you cannot go to main(),  the issue might be related to another known issue:

https://devzone.nordicsemi.com/f/nordic-q-a/58454/ses-cant-find-arm_mpu_v8_internal-h-and-other-includes/237485#237485

If there's specific code that you cannot debug properly, could you try setting DEBUG_OPTIMIZATIONS in your configuration? (prj.conf -> CONFIG_DEBUG_OPTIMIZATIONS=y)

 

Kind regards,

Håkon

[savenlid]

Ok, no problem.

I will try.

Thanks