Create optional conf overlay that is triggered by writing to a service/characteristic

[jclyde]

I want to define config values in an optional overlay that is enabled after writing to a custom service/characteristic using NCS. Based on this https://devzone.nordicsemi.com/nordic/b/archives/posts/nrf-connect-sdk-tutorial---part-2-1478313418#h128sk64757ef1a0yr9w1h6gklfucy966 it looks like it is possible to have optional overlay files, but I am not sure if I can trigger it in a conditional statement. 

If anyone can help point me in a direction of if it is possible and any potential examples it would be greatly appreciated. 

[dejans]

Hi,

Configuration overlay files are specified and used in the build process and cannot be used in the way that you would want after build process has finished.

Best regards,
Dejan

[jclyde]

Thank you, Do you know if it would be possible to assign GATT device information then in a custom service? I've only been able to find examples of values assigned in the prj.conf but I would like to be able to change the value of some of the config_bt_dis values or to treat the device as two completely different devices based on which service is in use. 

[dejans]

Hi,

Could you provide an example of what you are trying to achieve?

Best regards,
Dejan

[jclyde]

There is one specific instance when my device needs to have a PNP ID, even though I'm not actually using usb, so I wanted to have a value to submit only when this instance occurs

[dejans]

Hi,

jclyde said:

I've only been able to find examples of values assigned in the prj.conf but I would like to be able to change the value of some of the config_bt_dis values or to treat the device as two completely different devices based on which service is in use.

Could you provide link to examples?
How would you like to change the values in config_bt_dis?
Could you please elaborate on "... to treat the device as two completely different devices based on which service is in use"?

Best regards,
Dejan