Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread John Syne
Reviewing my previous work, the two package you need are: alsa-lib alsa-utils apt-get source alsa-utils cd alsa-utils-1.0.25 export DEB_BUILD_OPTIONS=“nostrip noopt debug" dpkg-buildpackage -rfakeroot -uc -us make make install or dpkg -i libasound2*.deb or apt-get install libasound2-dbg apt-g

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread John Syne
I did this years ago. From what I can find, I believe this is how you get this done: sudo apt-get build-dep libasound2 apt-get source libasound2 cd alsa-lib-1.0.22/ export DEB_BUILD_OPTIONS=nostrip,noopt dpkg-buildpackage -rfakeroot -uc -us After that, you will have some *.deb files created, whi

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread Robert Nelson
On Wed, Apr 6, 2016 at 8:44 PM, Rick Mann wrote: > That looks like something that would be useful to figure out how to do. > The only part that's not immediately clear is "rebuild the entire ALSA > library and tools with debug symbols. Also, your Kernel must have debug > symbols turned on." > > C

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread Rick Mann
That looks like something that would be useful to figure out how to do. The only part that's not immediately clear is "rebuild the entire ALSA library and tools with debug symbols. Also, your Kernel must have debug symbols turned on." Can I do this with RCN's kernel build script setup? Thanks.

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread John Syne
OK, so you have to rebuild the entire ALSA library and tools with debug symbols. Also, your Kernel must have debug symbols turned on. You will need to enable various ftrace features with make config. Here is a typical script I use to capture program flow. === #!/bin/bash set -x pause() { lo

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread Rick Mann
> On Apr 6, 2016, at 16:53 , Peter Hurley wrote: > > If this is a latency problem, ftrace is probably your best bet, but > function_graph and the other tracers can induce even more latency. Nothing so esoteric. I'm just trying to get the damn thing to work at all. It's worked in previous kerne

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread John Syne
> On Apr 6, 2016, at 5:27 PM, 'Mark Lazarewicz' via BeagleBoard > wrote: > > If it's a company project the Lauterbach is well worth the money Definitely. Lauterbach is one of my favorite tools and I cannot imagine doing some work without it. It is a difficult tool to learn, but it is very pow

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread 'Mark Lazarewicz' via BeagleBoard
If it's a company project the Lauterbach is well worth the money  Sent from Yahoo Mail on Android On Wed, Apr 6, 2016 at 5:56 PM, Rick Mann wrote: What would I need to get/do to enable me to single-step through kernel code on BBB/G? JTAG header, some kind of interface, and a bunch of soft

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread John Syne
> On Apr 6, 2016, at 4:53 PM, Peter Hurley wrote: > > On 04/06/2016 02:56 PM, Rick Mann wrote: >> What would I need to get/do to enable me to single-step through >> kernel code on BBB/G? JTAG header, some kind of interface, and a >> bunch of software installed on Ubuntu? Can anyone make specific

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread Peter Hurley
On 04/06/2016 02:56 PM, Rick Mann wrote: > What would I need to get/do to enable me to single-step through > kernel code on BBB/G? JTAG header, some kind of interface, and a > bunch of software installed on Ubuntu? Can anyone make specific > recommendations? Is it even possible? On 04/06/2016 03:3

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread John Syne
For audio, your best solution is ftrace. If you use function_graph option, then you can see the hierarchy of the call sequence. You can also use trace_printk to display variables at specific locations. BTW, Lauterbach is about $5K investment for the base tool with USB3 connection. You might be

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread Rick Mann
Thanks, John. I've tried printk and other logging, but it's virtually impossible to trace something like audio, which spans many modules. I'll look into Lauterbach. > On Apr 6, 2016, at 15:31 , John Syne wrote: > > You can do this with CCSV6 with a USB200 JTAG adapter, but CCSV6 is no longer

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread John Syne
You can do this with CCSV6 with a USB200 JTAG adapter, but CCSV6 is no longer kernel aware. CCSV4 was kernel aware, but won’t work with the current kernels. You can still debug with single stepping, software and hardware breakpoints, read/write memory, etc. Trying to debug a kernel module withou

[beagleboard] Source-level single-stepping kernel code on BBB?

2016-04-06 Thread Rick Mann
What would I need to get/do to enable me to single-step through kernel code on BBB/G? JTAG header, some kind of interface, and a bunch of software installed on Ubuntu? Can anyone make specific recommendations? Is it even possible? Thanks, -- Rick Mann rm...@latencyzero.com -- For more optio