samples: bluetooth: Disable console by default in Power Profiling

To reduce power as much as possible in
Power Profiling, this commit disables
UART console by default in all targets.

Signed-off-by: Dominik Kilian <[email protected]>

Author: doki-nordic

samples/bluetooth/peripheral_power_profiling/README.rst

@@ -229,7 +229,8 @@ CONFIG_BT_POWER_PROFILING_LED_DISABLED - Disable LEDs
 CONFIG_BT_POWER_PROFILING_NFC_DISABLED - Disable NFC
    Disables the NFC to reduce power consumption.
 
-You can also consider using the following global configuration options to disable the console and UART, reducing power consumption:
+The console is disabled by default to reduce power consumption.
+To enable the console, set the following Kconfig options to ``y``:
 
 * :kconfig:option:`CONFIG_SERIAL`
 * :kconfig:option:`CONFIG_CONSOLE`
@@ -259,6 +260,12 @@ Testing with Bluetooth Low Energy app and Power Profiler Kit II (PPK2)
 
 1. Set up `Power Profiler Kit II (PPK2)`_ and prepare your development kit for current measurement.
 #. Run the `Power Profiler app`_ from nRF Connect for Desktop.
+#. To see terminal messages (at the cost of a very small increase in power consumption), enable the following Kconfig  options:
+
+   * :kconfig:option:`CONFIG_SERIAL`
+   * :kconfig:option:`CONFIG_CONSOLE`
+   * :kconfig:option:`CONFIG_UART_CONSOLE`
+
 #. |connect_terminal_ANSI|
 #. Reset your development kit.
 #. Observe that the sample starts.

samples/bluetooth/peripheral_power_profiling/prj.conf

@@ -33,3 +33,9 @@ CONFIG_POWEROFF=y
 
 CONFIG_BT_ASSERT=n
 CONFIG_ASSERT_VERBOSE=n
+
+# Disable UART console by default.
+# Comment following lines to bring UART console back.
+CONFIG_SERIAL=n
+CONFIG_CONSOLE=n
+CONFIG_UART_CONSOLE=n