![]() |
|
|
Hello, |
|
|
Paul McManus
Senior Software Engineer
Tel: +44 (0) 1224 775700
Fax: +44 (0) 1224 775800
Email: Paul.M...@nautronix.co.uk
Website: www.nautronix.com |
|
This email is sent and received in accordance with the terms and conditions as defined on our website. To view click here Nautronix is a public limited company registered in Scotland. Registered number: SC062293. Registered office: Nautronix House, Howe Moss Avenue, Kirkhill, Dyce, Aberdeen, AB21 0GP |
|
--------------------------------------------------------------------- This email has been scanned for Nautronix plc, by the Postini Message Security System. ---------------------------------------------------------------------
On Jan 11, 3:37 am, "Paul McManus" <Paul.McMa...@Nautronix.co.uk>
wrote:
> www.nautronix.com:http://clicks.nautronix.co.uk/linktrack.php?ZWlkPTI1OTc1OTUmbGlkPTQzN...http://clicks.nautronix.co.uk/linktrack.php?ZWlkPTI1OTc1OTUmdWlkPTIxO...
> click here:http://clicks.nautronix.co.uk/linktrack.php?ZWlkPTI1OTc1OTUmbGlkPTU5N...
>
> ---------------------------------------------------------------------
> This email has been scanned for Nautronix plc,
> by the Postini Message Security System.
> ---------------------------------------------------------------------
>
> nautronixlogo.jpg
> 15KViewDownload
>
> nautronixfooter.jpg
> 7KViewDownload
>
> 316055f.jpg
> 54KViewDownload
> dsplink driver open: /dev/dsplink: No such device or address
>
Does the /dev/dsplink node exists?
I've noticed that your load scripts remove and renew the nodes. for LPM
and dsplink this should not be nessesary. At least on my system the
kernel modules generate the nodes themselfs. You could try to just
insert the modules on a just booted system. insmod lpm_omap3530.ko
should do all the work since it also loads dsplink into the kernel.
Cheers,
Nils
http://ossie.wireless.vt.edu/trac/wiki/BeagleBoard_DSPLink#IntroductiontoDSPLink
http://wiki.davincidsp.com/index.php/Building_DSPLink_Applications
http://wiki.davincidsp.com/index.php/Building_DSPLink
http://wiki.davincidsp.com/index.php/Troubleshooting_DSPLink_configuration_issues
I am probably making the classic newbie mistake of mixing different configs and not really understanding them.
Cheers,
Nils
---------------------------------------------------------------------
I don't know about any other sites. There is very little information on
the net. Also it always depends on how you want to use dsplink. I for
example don't want any of the codec-engine stuff. I need a lightweight
solution, so the bare kernel-module and the user-space libraries is all
I need.
Setting everything up was easy. I just compiled dsplink against the
kernel I'm using (2.6.29 I think), linked my applications against the
new built dsplink user-space library and everything worked as it should.
Getting LPM running was a bit messy due to the lack of the user-space
library source, but in the end it worked as well.
> I am probably making the classic newbie mistake of mixing different configs and not really understanding them.
>
That is very likely the root of the problem..
Have you tried running lpmON as root in the meantime? Does it now work
as it should?
Cheers,
Nils Pipenbrinck
Thanks for your replies
Paul
-----Original Message-----
From: beagl...@googlegroups.com [mailto:beagl...@googlegroups.com]
On Behalf Of Nils Pipenbrinck
Sent: 13 January 2010 15:58
To: beagl...@googlegroups.com
Subject: Re: [beagleboard] Question about DSPlink test apps
Cheers,
Nils Pipenbrinck
Thanks,
Saladino.
On Jan 14, 6:52 am, "Paul McManus" <Paul.McMa...@Nautronix.co.uk>
wrote:
> Thanks Nils,
> I tracked down the problem to be not adding the correct Beagle
> options in the configuration step using the prel script before building
> the source. It seems fine now. Next up is playing with the memory
> allocation, then benchmarking the DSP app with an FFT or something. I am
> porting over an old app running on an ARM7 and ADSP2188 to either
> OMAP3550 or BF537. I'll be embarrassing myself on the Blackfin forums
> next 8-) .
>
> Thanks for your replies
> Paul
>
> -----Original Message-----
> From: beagl...@googlegroups.com [mailto:beagl...@googlegroups.com]
>
> On Behalf Of Nils Pipenbrinck
> Sent: 13 January 2010 15:58
> To: beagl...@googlegroups.com
> Subject: Re: [beagleboard]QuestionaboutDSPlinktest apps
>
> Paul McManus wrote:
> > Thanks for the suggestion Nils. I will give this a try today. By the
> way what websites can you suggest would be useful for me to follow to
> useDSPLINKon Beagle.
>
> I don't know about any other sites. There is very little information on
> the net. Also it always depends on how you want to usedsplink. I for
> example don't want any of the codec-engine stuff. I need a lightweight
> solution, so the bare kernel-module and the user-space libraries is all
> I need.
>
> Setting everything up was easy. I just compileddsplinkagainst the
> kernel I'm using (2.6.29 I think), linked my applications against the
> new builtdsplinkuser-space library and everything worked as it should.
FFT-Size Time (average)
----------------------------
8 0.58 �s
16 0.30 �s
32 0.58 �s
64 0.96 �s
128 2.14 �s
256 4.03 �s
512 9.11 �s
1024 17.7 �s
2048 40.3 �s
4096 80.1 �s
8192 0.86 ms
16384 10 ms
32767 21 ms
65536 44 ms
(I hope the table comes out nice).
Btw, the big leap at 8192 samples is due to the fact that the data does
not fit into the cache anymore. the library doesn't do any DMA and
internal RAM management, so it starts to crawl as soon as cache misses
start to occur.
I hope this table is what you've been looking for.
> Can you post a step by step guide to setup the DSP for this
> purpose or are the links from Paul my best bet?
I thought about writing one, but I see the problem that with the next
dsplink release it becomes wrong and may only confuse people. But it's
not rocket science. The dsplink archive has a nice installation guide.
If you follow it step by step and apply common sense it is not that hard.
If there is enough interest I could write something up though...
> Did you have to do anything special to get LPM running?
>
Yes. The sources of the user-mode libraries are missing in the TI package.
Instead you find two precompiled libraries of which one after some
tweaking works. The library references two mysterious symbols (some
transport layer stuff which I never heard of ). Fortunately the lib only
references the symbols but never calls them, so it's fine to just
declare them somewhere. That makes the linker happy.
Cheers,
Nils Pipenbrinck
> Can you post a step by step guide to setup the DSP for this
>> purpose or are the links from Paul my best bet?
> I thought about writing one, but I see the problem that with the next
> dsplink release it becomes wrong and may only confuse people. But it's
> not rocket science. The dsplink archive has a nice installation guide.
> If you follow it step by step and apply common sense it is not that hard.
>
> If there is enough interest I could write something up though...
With OpenEmbedded you need to do 2 steps:
1) download TI codegen 6.1.9
2) 'bitbake ti-dsplink-module'
That will build a dsplink that matches the angstrom kernel and leave a tree in staging you can build against. You even get an include file that sets all the FOO_INSTALL_DIR vars for you!
regards,
Koen
Thanks.
https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm
You may have to register, but it's free.
Btw, since an hour I'm using version 6.1.13. Got a nice 15% speed-up on
some routines.
Cheers,
Nils
Thanks,
Saladino.
On Jan 19, 10:40 pm, Nils Pipenbrinck <n...@planetarc.de> wrote:
> saladino wrote:
> > Where do I get TI codegen 6.1.9 ? I don't really know what it is.
>
> It's the compiler for DSP executables. It can be found here:
>
> https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/down...
It can compile C and C++ code.
Cheers,
Nils
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/wwG2mvA0Qqg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.