Debug Output

Debug Output

[Abot Botbot]

Hello all,


    I'm trying to edit the RF6 refference framework application to suit my 
purposes. At the moment I want to get a feel for how many samples go through 
their filter with each message from the GPP. My algorithm works on a sample 
by sample basis, so I'm guessing I want to do my loop multiple times per 
message from the GPP. My questions is, how can I output basic debug material 
to the console? Can I just throw printf statements in any place in the code 
and see the output in the console? I see statments like "UTL_logDebug( 
"Application started." );" etc, where does that output end up?

Thanks,
Andy

_________________________________________________________________
Windows Live Spaces is here! It’s easy to create your own personal Web site. 
  http://spaces.live.com/signup.aspx

RE: Debug Output

[Abot Botbot]

Folks,


   Thanks for the help Robin!

   I've been reading the refference framework userguide, SPRA796A, it has 
been very helpful in understanding the mechanics of the system. There is a 
section in here about debugging the DSP side applicaiton, and it makes 
refference to viewing logs containing debug output. The problem is that I 
cannot figure out how to view these logs in code composer (2.21). I set a 
breakpoint that the code should hit (on one UTL debug line when the volume 
is changed), but when I run and change the volume via the terminal, CCS 
never breaks or otherwise informs me of the debug output. Is there a window 
for this that can be docked with the rest of the GUI? Does anyone know where 
this is in the menus?

Thanks,
Andy


>From: "Boivin, Robin" <RBoivin@oerlikon.ca>
>To: "Abot Botbot" <dejanigma@hotmail.com>
>Subject: RE: Debug Output
>Date: Thu, 31 Aug 2006 10:32:38 -0400
>
>The UTL* are for the DSP side. The prints are stored by the RTDX and sent 
>through JTAG to your Code Composer when you break. I find it quite 
>difficult to trace and debug using that. You could try your algorythm on 
>the data stream received on the ARM side. From there you can printf and 
>trace more easily.
>
>The CCS debugger is buggy. Well mine is, maybe because I use the CCS 31 
>EVAL version. Tell me whether you can use the CCS debugger, it would be 
>helpful for me.
>
>To integrate your algorytm through the RF6/DSP side using the TI XDAIS 
>method, you may have a couple of reading to do:
>spra796a
>spra795a
>
>The way I did is that I started from their VOL module. Adapt your algo 
>based on that. You have to get familiar with their multi-thread stuff 
>(cell, channel, task, etc)
>
>Hope it helps
>
>Robin
>
>
>-----Original Message-----
>From: linux-omap-open-source-bounces@linux.omap.com
>[mailto:linux-omap-open-source-bounces@linux.omap.com]On Behalf Of Abot
>Botbot
>Sent: August 31, 2006 10:10 AM
>To: Linux-omap-open-source@linux.omap.com
>Subject: Debug Output
>
>
>Hello all,
>
>
>     I'm trying to edit the RF6 refference framework application to suit my
>purposes. At the moment I want to get a feel for how many samples go 
>through
>their filter with each message from the GPP. My algorithm works on a sample
>by sample basis, so I'm guessing I want to do my loop multiple times per
>message from the GPP. My questions is, how can I output basic debug 
>material
>to the console? Can I just throw printf statements in any place in the code
>and see the output in the console? I see statments like "UTL_logDebug(
>"Application started." );" etc, where does that output end up?
>
>Thanks,
>Andy
>
>_________________________________________________________________
>Windows Live Spaces is here! It's easy to create your own personal Web 
>site.
>   http://spaces.live.com/signup.aspx
>
>_______________________________________________
>Linux-omap-open-source mailing list
>Linux-omap-open-source@linux.omap.com
>http://linux.omap.com/mailman/listinfo/linux-omap-open-source

_________________________________________________________________
Call friends with PC-to-PC calling -- FREE   
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline

Debug output

[damateem]

There are a fair number of debug print statements in the V4L2 code. How
do I turn those on?

For instance, I'd like the following code to print

if ((vfd->debug & V4L2_DEBUG_IOCTL) &&
                !(vfd->debug & V4L2_DEBUG_IOCTL_ARG)) {
        v4l_print_ioctl(vfd->name, cmd);
        printk(KERN_CONT "\n");
    }

so I can trace the IOCTL calls.

Thanks,
David

Re: Debug output

[damateem]

Ok, if I set debug as follows

vfd->debug =V4L2_DEBUG_IOCTL | V4L2_DEBUG_IOCTL_ARG;

I can see the debug trace in dmesg, but this doesn't seem like the
correct way to set the flags.

What is the typical method of setting these debug flags?

Is this the best place to ask these type of questions?

Thanks,
David


On 11/30/2011 7:46 PM, damateem wrote:
> There are a fair number of debug print statements in the V4L2 code. How
> do I turn those on?
>
> For instance, I'd like the following code to print
>
> if ((vfd->debug & V4L2_DEBUG_IOCTL) &&
>                 !(vfd->debug & V4L2_DEBUG_IOCTL_ARG)) {
>         v4l_print_ioctl(vfd->name, cmd);
>         printk(KERN_CONT "\n");
>     }
>
> so I can trace the IOCTL calls.
>
> Thanks,
> David

Re: Debug output

[Mauro Carvalho Chehab]

On 01-12-2011 17:01, damateem wrote:
> Ok, if I set debug as follows
>
> vfd->debug =V4L2_DEBUG_IOCTL | V4L2_DEBUG_IOCTL_ARG;
>
> I can see the debug trace in dmesg, but this doesn't seem like the
> correct way to set the flags.

In general, what it is none is to add a debug modprobe parameter that
would enable those logs with something like:

static unsigned int debug;
module_param(debug, int, 0644);
MODULE_PARM_DESC(debug, "debug message mask (1 = ioctl, 2 = ioctl args)");


...
	vfd->debug = debug;

>
> What is the typical method of setting these debug flags?
>
> Is this the best place to ask these type of questions?
>
> Thanks,
> David
>
>
> On 11/30/2011 7:46 PM, damateem wrote:
>> There are a fair number of debug print statements in the V4L2 code. How
>> do I turn those on?
>>
>> For instance, I'd like the following code to print
>>
>> if ((vfd->debug&  V4L2_DEBUG_IOCTL)&&
>>                  !(vfd->debug&  V4L2_DEBUG_IOCTL_ARG)) {
>>          v4l_print_ioctl(vfd->name, cmd);
>>          printk(KERN_CONT "\n");
>>      }
>>
>> so I can trace the IOCTL calls.
>>
>> Thanks,
>> David
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html