Well, you won’t be able to do much. For example, as you single step, the kernel 
can switch tasks and then you will be stepping through an unrelated thread. No 
way to switch back to your original thread, so you will have to set breakpoints 
in the source and hope to get back to your original code. Second, you cannot 
debug Kernel Modules because you don’t know the address of the module. There 
are several other limitations, but you get my point when the debugger isn’t 
kernel aware. 

TI use to have some limited kernel awareness in CCS4, but removed that 
functionality in CCSV5 because they wanted to stay as close to the Eclipse 
releases so heavy customization was out. I know the TI CCS developers and they 
explained that I was one of the only developers asking for kernel awareness. 
Perhaps if more developers asked for this feature, they might add it back in. 

Regards,
John




> On Jun 14, 2016, at 11:17 AM, [email protected] wrote:
> 
> Hi,
> 
> An experience:
> I can debug the linux kernel with both openocd + TIAO/flyswatter2/.. or the 
> TI dongles like blackhawk with CCS.
> 
> Note, one very tricky thing: Recent linux kernels mess with the jtag during 
> boot on the bbb. You need a kernel patch -just- to be able to debug:
> 
>  diff arch/arm/mach-omap2/omap_hwmod_33xx_data.c
> diff --git a/arch/arm/mach-omap2/omap_hwmod_33xx_data.c 
> b/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
> index 6b406ca..8cb0b85 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
> @@ -223,6 +223,7 @@ static struct omap_hwmod am33xx_debugss_hwmod = {
>         .class          = &am33xx_debugss_hwmod_class,
>         .clkdm_name     = "l3_aon_clkdm",
>         .main_clk       = "trace_clk_div_ck",
> +       .flags      = (HWMOD_INIT_NO_IDLE | HWMOD_INIT_NO_RESET),/*Added this 
> line*/
>         .prcm           = {
>                 .omap4  = {
>                         .clkctrl_offs   = 
> AM33XX_CM_WKUP_DEBUGSS_CLKCTRL_OFFSET,
> 
> 
> Op donderdag 5 mei 2016 06:52:22 UTC+2 schreef Raul Piper:
> Is TIN FlysWatter2 <http://www.tincantools.com/JTAG/Flyswatter2.html> a 
> better tool for debugging the kernel driver in BBB.Can some one please post 
> thier experience?
> -Rp
> 
> -- 
> For more options, visit http://beagleboard.org/discuss 
> <http://beagleboard.org/discuss>
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/d2c6c6d1-31e2-444a-8ec7-4af6d3d5fac2%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/beagleboard/d2c6c6d1-31e2-444a-8ec7-4af6d3d5fac2%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/F91AAA68-F879-4669-9049-1F99356B3207%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to