The way I work is to have the BBB mount rootfs over NFS which resides on my desktop. When I create a Kernel Module, I do the following:
1) I clone Robert’s kernel repo 2) I build the kernel 3) I add my kernel module code 4) I rebuild the kernel 5) I modify Robert’s deploy script to copy the kernel/kernel modules to my NFS share directory 6) I run modprobe <mykernelmodule> 7) If there is a problem; modprobe -r <mykernelmodule> 8) Modify my code an goto step 4 9) Once everything is working, I create a patch and add it to the patches folder and modify Robert’s build script. By using Robert’s build scripts, you don’t have to worry about kernel headers, compiler versions, etc. It all just works. No need for any special tools, just use your favorite editor. I tend to use Eclipse as I can index the entire kernel source code so I can just <cntl> click on any function and it will switch to that function. <alt> left arrow returns to your previous location. This link will show you how to make Eclipse work. https://wiki.eclipse.org/HowTo_use_the_CDT_to_navigate_Linux_kernel_source <https://wiki.eclipse.org/HowTo_use_the_CDT_to_navigate_Linux_kernel_source> I hope this helps. Regards, John > On Jun 23, 2017, at 12:23 PM, mzimmers <[email protected]> wrote: > > 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 > <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/b08c6a13-5bd6-4693-a466-9b5596a8e117%40googlegroups.com > > <https://groups.google.com/d/msgid/beagleboard/b08c6a13-5bd6-4693-a466-9b5596a8e117%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/FC8127CE-8BE9-419A-B126-6679043EAB72%40gmail.com. For more options, visit https://groups.google.com/d/optout.
