From: [email protected]
To: [email protected]
Subject: RE: embedded ossie dm6446
Date: Wed, 14 Apr 2010 20:18:15 +0500
> Date: Tue, 13 Apr 2010 11:43:32 -0400
> From: [email protected]
> To: [email protected]
> Subject: Re: embedded ossie dm6446
>
> On 04/13/2010 11:30 AM, saleh usman wrote:
> >
> > If I build another waveform on desktop OSSIE and want to run on my board
> > whether I've to again build complete file system using console-image or
> > bitbaking of only new waveform related files will work? Actually my board
> > doesn't have support for any sound out device and I can't check
> > fm-from-file waveform therefore I want to build another waveform which
> > print output on console. will ossie lab 1 work fine?
>
> You could create recipes for your new components and build them.
>
> Existing OSSIE components from VT will not work because they do not use
> SCA parameters for component startup (and likely a few other issues
> revolving around SCA compatibility).
Then how can I build waveform using components and run it on my board means
which ossie components I should use so that those components will work.
Saleh
>
> Philip
>
> > Saleh
> >> Date: Thu, 1 Apr 2010 10:37:04 -0400
> >> From: [email protected]
> >> To: [email protected]
> >> Subject: Re: embedded ossie dm6446
> >>
> >> On 04/01/2010 10:33 AM, saleh usman wrote:
> >>>
> >>> Hi
> >>> console-image has been built successfully and /sdr directory is present
> >>> in file system image.But as mentioned on page
> >>> http://www.opensdr.com/node/11 file /etc/pulse/daemon.conf is not there.
> >>
> >> OK, you are now the first person to try this on the dm6446!
> >> Unfortunately, the only hw I can test on is the beagleboard. I'll try
> >> and test my build on it and see if I can see where that file went.
> >>
> >> Thanks for your patience.
> >>
> >>> Also I've board on which linux is already runing so if I replace the
> >>> already flashed file system with OE generated will it work or I has to
> >>> replace old kernel with OE generated kernel?
> >>
> >> As long as you put any modules for your kernel in the rootfs, your
> >> existing kernel should be fine.
> >>
> >> Philip
> >>
> >>
> >>>
> >>> Saleh
> >>>
> >>>
> >>>> Date: Mon, 29 Mar 2010 10:43:24 -0400
> >>>> From: [email protected]
> >>>> To: [email protected]
> >>>> Subject: Re: embedded ossie dm6446
> >>>>
> >>>> On 03/29/2010 10:31 AM, saleh usman wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Date: Sun, 28 Mar 2010 08:14:21 -0400
> >>>>>> From: [email protected]
> >>>>>> To: [email protected]
> >>>>>> Subject: Re: Boost library issue
> >>>>>>
> >>>>>> On 03/28/2010 08:03 AM, saleh usman wrote:
> >>>>>>>
> >>>>>>> I'm proceeding now by manually changing
> >>>>>>> AC_CHECK_LIB([boost_filesystem], [main], [], [AC_MSG_ERROR([cannot
> >>>>>>> find boost_filesystem library.])]).
> >>>>>>
> >>>>>> Two things: Do not build ossie-image. Follow the instructions from the
> >>>>>> article at:
> >>>>>>
> >>>>>> http://www.opensdr.com/node/7
> >>>>>
> >>>>>
> >>>>> I am bitbaking console-image now by following this page but when I
> >>>>> bitbake conosle-image after adding following lines nothing builds more
> >>>>> than the first bitbake of console-image.
> >>>>>
> >>>>> NGSTROM_EXTRA_INSTALL = " screen oprofile ossie-fm-from-file "
> >>>>> require /sdr/ossie_collection/conf/distro/include/sane-ossie-revs.inc
> >>>>>
> >>>>> BBFILES = "/sdr/openembedded/recipes/*/*.bb
> >>>>> /sdr/ossie_collection/packages/*/*.bb"
> >>>>>
> >>>>> BBFILE_COLLECTIONS = "upstream ossie"
> >>>>>
> >>>>> BBFILE_PATTERN_upstream = "^/sdr/openembedded/recipes"
> >>>>> BBFILE_PRIORITY_upstream = "5"
> >>>>>
> >>>>> BBFILE_PATTERN_ossie = "^/sdr/ossie_collection/packages"
> >>>>> BBFILE_PRIORITY_ossie = "10"
> >>>>>
> >>>>> Terminal log follows which is same as the output of the console-image
> >>>>> without adding above lines.
> >>>>>
> >>>>>
> >>>>> [sa...@localhost ~]$ bitbake console-image
> >>>>> NOTE: Handling BitBake files: \ (8169/8169) [100 %]
> >>>>> NOTE: Parsing finished. 7504 cached, 335 parsed, 330 skipped, 0 masked.
> >>>>> NOTE: Resolving any missing task queue dependencies
> >>>>> NOTE: Preparing runqueue
> >>>>> NOTE: Executing runqueue
> >>>>> NOTE: Running task 3000 of 3005 (ID: 18,
> >>>>> /sdr/openembedded/recipes/images/console-image.bb,
> >>>>> do_package_update_index_ipk)
> >>>>> NOTE: Running task 3004 of 3005 (ID: 10,
> >>>>> /sdr/openembedded/recipes/images/console-image.bb, do_rootfs)
> >>>>> NOTE: Running task 3005 of 3005 (ID: 4,
> >>>>> /sdr/openembedded/recipes/images/console-image.bb, do_build)
> >>>>> NOTE: Tasks Summary: Attempted 3005 tasks of which 3002 didn't need to
> >>>>> be rerun and 0 failed.
> >>>>
> >>>> Do a "bitbake -c clean task-base" then build console-image. (Actually, I
> >>>> think bitbake -c clean console-image is enough, but my fingers are
> >>>> trained to clean task-base. When you change the ANGSTROM_EXTRA_INSTALL
> >>>> var, bitbake does not have a way of seeing the change, so you have to
> >>>> help it some.)
> >>>>
> >>>> Philip
> >>>
> >>> _________________________________________________________________
> >>> Hotmail: Trusted email with powerful SPAM protection.
> >>> https://signup.live.com/signup.aspx?id=60969
> >>
> >
> > _________________________________________________________________
> > Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
> > https://signup.live.com/signup.aspx?id=60969
>
Hotmail: Powerful Free email with security by Microsoft. Get it now.
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
https://signup.live.com/signup.aspx?id=60969