Bluetooth: controller: Introduce debug pins Kconfig option
A new Kconfig debug option now controls the usage of pin toggling to debug the BLE controller. Change-Id: I24c5c13ca71e3395e10f14e27ad4bca9f2e94687 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
This commit is contained in:
parent
34e0c4b253
commit
3141dcf3b4
2 changed files with 10 additions and 2 deletions
|
@ -100,4 +100,12 @@ config BLUETOOTH_CONTROLLER_PROFILE_ISR
|
|||
contains current, minimum and maximum ISR entry latencies; and
|
||||
current, minimum and maximum ISR CPU use in micro-seconds.
|
||||
|
||||
config BLUETOOTH_CONTROLLER_DEBUG_PINS
|
||||
bool "Bluetooth Controller Debug Pins"
|
||||
help
|
||||
Turn on debug GPIO toggling for the BLE Controller. This is useful
|
||||
when debugging with a logic analyzer or profiling certain sections of
|
||||
the code. When enabled, pins P0.16 to P0.25 are taken over exclusively
|
||||
by the controller and cannot be used outside of it.
|
||||
|
||||
endif # BLUETOOTH_CONTROLLER
|
||||
|
|
|
@ -22,7 +22,7 @@ void bt_controller_assert_handle(char *file, uint32_t line);
|
|||
* which can be defined to SoC's GPIO toggle to observe/debug the
|
||||
* controller's runtime behavior.
|
||||
*/
|
||||
#if (DEBUG == 1)
|
||||
#ifdef CONFIG_BLUETOOTH_CONTROLLER_DEBUG_PINS
|
||||
#define DEBUG_INIT() do { \
|
||||
NRF_GPIO->DIRSET = 0x03FF0000; \
|
||||
NRF_GPIO->OUTCLR = 0x03FF0000; } \
|
||||
|
@ -209,6 +209,6 @@ void bt_controller_assert_handle(char *file, uint32_t line);
|
|||
|
||||
#define DEBUG_RADIO_START_M(flag)
|
||||
|
||||
#endif /* DEBUG */
|
||||
#endif /* CONFIG_BLUETOOTH_CONTROLLER_DEBUG_PINS */
|
||||
|
||||
#endif /* _DEBUG_H_ */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue