BasedHardware
Firmware - dk2 - Kernel Panic on Ozone debug step
Describe the bug
Kernel Panic on Ozone debug step
To Reproduce Steps to reproduce the behavior:
- Follow guideline to compile firmware to compile firmware for dev kit 2.
- Connect Jlink debugger to SWD interface on dev kit 2
- Open OZone IDE
- Start debugging , then pause / resume -> hard fault
Current behavior Zephyr Kernel panic
Expected behavior Able to debug firmware normally without any hard fault, it is helpful for deep debugging for critical cases like memory leak...
Screenshots
user ID (can we access the user info to validate the bug?): Can be found in settings => profile
device (please complete the following information):
- Device version : dev kit version 2
Nice observation. I just tested the SWD interface on Devkit 2 and encountered the same error as you. It seems to be an issue related to J-Link debugging rather than the firmware itself. Do you have any potential solutions or workarounds for this?
Can you try to enable some config and debug again:
CONFIG_THREAD_MONITOR=y
CONFIG_INIT_STACKS=y
CONFIG_THREAD_STACK_INFO=y