Linux/AM5726: Debugging Linux Kernel

Christine,

Kernel debugging is a very important but broad topic. But there is no one-fit-for-all debug technique to cover all scenarios in kernel bugging. Depending on what exact the issue to tackle, there is always one way which does better job than others.

I do kernel debugging in daily basis, but only used CCS live debugging once a long time ago, mainly to understand the setup. Again, depending on the issue to be debugged, Jtag connection is better than kgdb sometimes. And CCS is not a good choice for hardware peripheral related debugging, because most of those cases don't allow halting the system.

Other than printfs, kernel already provides many debug infrastructure, which could be helpful in many cases. The training series in the link below introduces some of them, but I guess you know most of them.

training.ti.com/debugging-embedded-linux-systems-training-series

But its module 1.5 talks about kernel dynamic debug, which could be useful to dynamically enabling/disabling debug logs. Kernel doc has details:
<kernel source code>/Documentation/admin-guide/dynamic-debug-howto.rst

Ftrace is another very helpful tool provided in kernel, I mainly use ftrace + printks in my daily kernel debugging. Kernel doc has details about ftrace:

<kernel source code>/Documentation/trace/

Hope this information is helpful.