West debug does not work with Bluetooth shell and nRF52840 DK

[mkarhumaa]

Describe the bug
west debug does not work anymore with Bluetooth shell on nRF52840 DK. According to git bisect, commit enabling null pointer detection in tests caused this problem.

Inspired by this change I was able to figure out workaround that fixes the problem:

diff --git a/boards/arm/nrf52840dk_nrf52840/Kconfig.defconfig b/boards/arm/nrf52840dk_nrf52840/Kconfig.defconfig
index bc06b9074f..0192cd9217 100644
--- a/boards/arm/nrf52840dk_nrf52840/Kconfig.defconfig
+++ b/boards/arm/nrf52840dk_nrf52840/Kconfig.defconfig
@@ -21,4 +21,8 @@ endif # USB
 config BT_CTLR
        default BT
+choice CORTEX_M_DEBUG_NULL_POINTER_EXCEPTION_DETECTION
+       default CORTEX_M_DEBUG_NULL_POINTER_EXCEPTION_DETECTION_NONE
+endchoice
+
 endif # BOARD_NRF52840DK_NRF52840

To Reproduce
Steps to reproduce the behavior:

1. cd tests/bluetooth/shell
2. west build -b nrf52840dk_nrf52840
3. open console for shell: sudo minicom -D /dev/ttyACM0 -b 115200
4. west debug
5. In gdb prompt type continue to try to start running the program
6. Interactive shell does not start

Expected behavior
When typing "continue" in gdb test application, Bluetooth shell in this case, should start running.

Impact
annoyance, workaround exists

Environment (please complete the following information):

• OS: Linux
• Toolchain: Zephyr SDK
• Commit: master (4aed856)

[carlescufi]

I am hitting this as well, and I would say this is at least medium prio, it's breaking the Bluetooth shell for most of us.

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

[nashif]

close as duplicate to #34222