Apparently the issue was some USB block sizing that was happening in the flowgraph, a flowgraph that someone in my research lab provided, when I enabled scheduler logging as per Eric's suggestion I found that the scheduler wasn't calling the work function at all. When I enabled logging from the "gr_flat_flowgraph.cc" file I found that the flowgraph was dying as the buffer were being allocated. Anyways, the code works now but for the future I will do more testing with the USB block sizes with the DSP in the loop to be understand this issue.
thanks again for your help Eric. al fayez -----Original Message----- From: Eric Blossom <[email protected]> To: [email protected]; [email protected] Sent: Sat, Jul 24, 2010 1:34 pm Subject: Re: [Discuss-gnuradio] GNU Radio scheduler behavior On Thu, Jul 22, 2010 at 07:40:29PM -0700, Eric Blossom wrote: > On Thu, Jul 22, 2010 at 10:18:41PM -0400, [email protected] wrote: > > > I think I'm running into some scheduler issues in GNU Radio that I > > don't really understand. I've been working on running GNU Radio > > blocks on the Beagleboard's DSP by writing new DSP specific custom > > signal processing blocks When I run simple QA python test scripts > > everything works fine. > Sorry, I should have mentioned this earlier. Try enabling the scheduler logging by #define ENABLE_LOGGING 1 In gr_block_executor.cc, line 38. This will create a separate ascii log file for each block. They'll be created in the current directory and have names "sst-%3d.log", where the numbers are unique. The log files contain the name of the block as the first line. Good luck, and let us know what you find out! Eric
_______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
