Change asset tracker (thingy91) example to PASSIVE MODE

[hubert_11]

Hi all,

I'm new to the whole kconfig system, and I can't seem to change the Asset Tracker to passive mode. 

I've tried adding these lines to the prj.conf file:

CONFIG_DATA_DEVICE_MODE_PASSIVE=y

CONFIG_DATA_DEVICE_MODE_ACTIVE=n

and I changed the default of the DATA_DEVICE_MODE choice in Kconfig.data_module to DATA_DEVICE_MODE_PASSIVE

 

Which does seem to add the following line to the autogenerated autoconf.h file:

#define CONFIG_DATA_DEVICE_MODE_PASSIVE 1

But the asset tracker is still in active mode. I checked this by placing break points in the 

apply_config() function in sensor_module.c, which shows me that it is still configuring the system based on messages that turn it into active mode, so it is calling:

accelerometer_callback_set(false);

Where do these messages come from, and how do I change this?

[Øyvind]

Sorry, I just repilcated what you stated.

[hubert_11]

I tried using 2.2.0 and setting those lines in the prj.conf but this still evaluates to true:

msg->module.data.data.cfg.active_mode

in:

static void apply_config(struct sensor_msg_data *msg)
{
#if defined(CONFIG_EXTERNAL_SENSORS)
	configure_acc(&msg->module.data.data.cfg);

	if (msg->module.data.data.cfg.active_mode) {
		accelerometer_callback_set(false);
	} else {
		accelerometer_callback_set(true);
	}
#endif /* CONFIG_EXTERNAL_SENSORS */
}

So the accelerometer callback is still set to false in 2.2.0, while it should be set to true right?

[Øyvind]

Are you able to rebuild your project with the overlay-debug.conf? This should provide more information for our developers to see what is going on. 

Thanks!

[hubert_11]

How exactly should I do this? I can see this already in the kconfig:

rsource "src/modules/Kconfig.debug_module"

and I do see the overlay-debug.conf in my file browser in vs code.

If I select debug options when creating the build configuration the build fails, which I already reported here:
https://devzone.nordicsemi.com/f/nordic-q-a/96553/build-configuration-fails-for-sdk-2-2-0/409413

[Øyvind]

hubert_11 said:

If I select debug options when creating the build configuration the build fails, which I already reported here:
https://devzone.nordicsemi.com/f/nordic-q-a/96553/build-configuration-fails-for-sdk-2-2-0/409413

I am not talking about the debug options in VS Code, this is the debug configuration which enables misc. debug settings in the application itself. 

In VS Code you can add this to your build configuration under Add Fragment, which will give you a dropdown menu of available overlay config files