Hi, John - thanks for the reply. I don't believe, however, that I'll need to use JTAG, at least not for this specific example.
Here's my current thinking: I already have a cross-development platform (Qt Creator) set up for the BBB, so I'm going to try to use it to build kernel modules. I know that at a minimum, I'll need the kernel header files, which I can get from RCN's repository. I just have to figure out where to put them on my host so I don't overwrite anything (my host isn't the same Debian version as my BBB). I welcome any feedback on this idea. On Friday, June 23, 2017 at 1:02:33 PM UTC-6, john3909 wrote: > > You need a kernel aware JTAG debugger like Lauterbach. This will allow you > to debug u-boot, kernel code, including all the drivers as they are loaded, > etc. It is expensive, but it is the gold standard for kernel/driver > debugging. > > TI have Code Composer Studio that will do some debugging of the kernel > using a blackhawk JTAG adapter, but CCSV7 has several limitations as they > no longer support kernel aware debugging (dropped after CCSV4). It is > somewhat helpful and a lot less expensive ($99) than Lauterbach. > > I hope this helps. > > Regards, > John > > > > > -- 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/b08c6a13-5bd6-4693-a466-9b5596a8e117%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
