CCSV4 was partially aware, but CCSV5 and CCSV6 are not. http://processors.wiki.ti.com/index.php/Linux_Aware_Debug_(CCSv4.x) <http://processors.wiki.ti.com/index.php/Linux_Aware_Debug_(CCSv4.x)>
Regards, John > On Mar 18, 2016, at 2:29 PM, Mark Lazarewicz <lazar...@yahoo.com> wrote: > > John I remember using Lauterbach to do this isn't CCS kernel aware? > > Sent from Yahoo Mail on Android > <https://overview.mail.yahoo.com/mobile/?.src=Android> > On Fri, Mar 18, 2016 at 1:24 PM, John Syne > <john3...@gmail.com> wrote: > Problem with GDB, is you cannot start the debugger until after the kernel > module is loaded, which means no debugging of init or probe sections. The > reason is GDB doesn’t know where in memory the kernel module is loaded until > after it is loaded. This is why you need a kernel aware debugger like > Lauterbach which loads the kernel module code, loads the debug symbols and > breaks at the start of init. > > Regards, > John > > > > >> On Mar 18, 2016, at 1:50 AM, William Hermans <yyrk...@gmail.com >> <javascript:return>> wrote: >> >> https://www.google.com/search?q=how+to+debug+linux+kernel+modules >> <https://www.google.com/search?q=how+to+debug+linux+kernel+modules> >> >> Just like you would on any platform. >> >> On Thu, Mar 17, 2016 at 8:46 PM, John Syne <john3...@gmail.com >> <javascript:return>> wrote: >> To debug kernel modules with JTAG, you have to have a debugger which is >> kernel aware like Lauterbach. If you don’t want to use JTAG, then use printk >> or dev-dbg, dev-err, etc. You can also use ftrace, which requires you to >> build your own kernel and add support for the various ftrace features. Read >> kernel docs under documentation/trace/ftrace.txt to learn more. >> >> Regards, >> John >> >> >> >> >>> On Mar 17, 2016, at 7:49 PM, cmajor.merch...@gmail.com <javascript:return> >>> wrote: >>> >>> I have a question about the beaglebone black. How am suppose to debug with >>> it? I really would prefer not to have to solder a JTAG header. Also the >>> JTAG header would be under the board which is really inconvenient. The case >>> that came with my board also has no room for the JTAG header so it would >>> basically render the case useless. I know it has a serial debug header but >>> how could I debug with it? I want to debug kernel modules. >>> >>> -- >>> 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 beagleboard+unsubscr...@googlegroups.com <javascript:return>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> 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 beagleboard+unsubscr...@googlegroups.com <javascript:return>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> >> >> -- >> 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 beagleboard+unsubscr...@googlegroups.com <javascript:return>. >> 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
