2010-10-26 11:10:23     problems starting uclinux

Document created by Aaronwu Employee on Aug 23, 2013
Version 1Show Document
  • View in full screen mode

2010-10-26 11:10:23     problems starting uclinux

tataru relu (ROMANIA)

Message: 95231   


I will be gratefull if somebody can help me with a problem. I am new in the domain, and I'm referring here at programming in uclinux for a bf537 . I have a program in VDSP and I want to implement it in uclinux in order to do the same thing.


So I started installing uclinux(I have an Ubuntu virtual machine). I installed the toolchain and everything needed. I compilled with succes the 'Hello world' program but I didn't know how to see the result. I understand that I need an emulator. I couldn't find one. If somebody can help me even if probably my queries sound stupid...




so...what I need is a link for a how to tutorial about installing uclinux...with everything needed in order to be sure that I correctly installed it


I also need a link for an emulator of the bf537, in order to see the result for the "hello world" program.




These 2 things will help me in my adventure with uclinux and bf537.


Sorry if my questions are funny for those who read the post and thank you for any help.




2010-10-26 11:25:48     Re: problems starting uclinux

Frank Van Hooft (CANADA)

Message: 95232   


Information on how to install the toolchain (compiler etc) plus a lot of other useful information can be found on the wiki on this site:




To see the output of "hello world" usually rhe easiest way is to just plug into the serial port (RS232 port) on your board, assuming of course your board has one.




2010-10-26 11:25:56     Re: problems starting uclinux

Mike Frysinger (UNITED STATES)

Message: 95233   


you dont need an emulator to run Linux.  what board exactly are you using ?




2010-11-15 09:45:56     Re: problems starting uclinux

tataru relu (ROMANIA)

Message: 95854   


I am relatively new in this area but I am decided to learn some things in order to realize a school project. I have to implement a talkthrough on a ADZS BF537 STAMP, using ucLinux. In the Blackfin examples(VDSP++) I found the implementation of a talkthrought, I studied it and I understood some things. My question is what will be the differences between that implementation and the one from ucLinux for the  ADZS BF537 STAMP. The one from the Blackfin examples is realized using BF537 EZ-KITLITE and I understood that this stamp is somehow the same with ADZS BF537 STAMP, but with some differences. The second one is especially for ucLinux and does not have all the necesary drivers. I will be glad if somebody tells me how to proceed in order to realize what  I want. Also I did not find a complex satisfactory tutorial for my stamp on the internet.




2010-11-15 15:28:39     Re: problems starting uclinux

Mike Frysinger (UNITED STATES)

Message: 95866   


for STAMP vs EZKIT, please read the documentation:



audio "talkthrough" under linux is trivial.  simply execute `arecord | aplay`.




2010-11-16 09:54:23     Re: problems starting uclinux

tataru relu (ROMANIA)

Message: 95878   


          I read the documentation and I saw the missing codecs from bf 537 STAMP. I understand also that  is easy to realize audio "talkthrough" using those commands.  I am interested to use somehow the same C functions() with ucLinux from the audio "talkthrogh" application which can be found in the analog devices, blackfin examples for ez-kit board, in order to realize the same thing , but using the bf537 stamp  which does not have  the ad 1854 and ad 1871 codecs. I have also an implementation in VDSP++ using an audio ez-extender which use ad 1938 codec. What I ask is which method should I use in order to implement the talkthrough in ucLinux and what will be the differences between this one and the VDSP++ implementation.


Thank you very much for your help!





2010-11-16 09:59:39     Re: problems starting uclinux

Mike Frysinger (UNITED STATES)

Message: 95879   


you're free to write your own SPORT driver to do whatever you want, it just doesnt make much sense in the Linux world since we have proper driver frameworks to accomplish audio setup/transport/codec management.


a raw SPORT driver can be found in the tree: