• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 632 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Alsa lib layer error with DM365

Sivagamy Govindasamy
Expert 6950 points


Hello All,

I compiled alsa library (to enable profiling of alsa src) for DM365. It gives error during open call itself as below.

ALSA lib pcm.c:2111:(snd_pcm_open_noupdate) Unknown PCM default
unable to open pcm device: No such file or directory

The .conf files seem to be ok only.

Any suggestions on how to resolve this issue?

Thanks,

Sivagamy

  • 0
    TI__Expert 5290 points

    Hi,

    It seems like there are no ALSA device files present (under /dev/snd).

    Was the sound support compiled in the kernel or kept as a module? If it is in the form of kernel modules did you get any errors or warnings when you loaded the modules?

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Bedia
    TI__Expert 6950 points

    Hi,

    Device filse are present. Kernel also supports alsa. I had a working version of alsa lib layer also (part of toolchain / target file system). If I use the original libasound.xx with the same kernel, alsa conf files, this issue doesnt occur.

    I compiled alsa-lib from source (used same version also) to enable some profiling. Problem occurs only with this new version compiled by me - not sure if I there is some problem with compile options. These are the steps used.

    export LD=/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-ld

    export CC=/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc

     

    ./configure --prefix=/home/rootfs --libdir=/home/rootfs/usr/lib --includedir=/home/rootfs/usr/include --host=i686-linux

     

    make install

     

    Thanks & Regards,

    Sivagamy

     

  • 0 in reply to Sivagamy Govindasamy
    TI__Expert 5290 points

    Hi,

    The config options that you pass should match with what the filesystem expects. Since you have an already working filesystem you could check the location of the files which alsa-lib generates and pass the options appropriately.

    One issue i see is that In the configure options you have not specified datadir. The filesystem that i am using expects the "share" folder which alsa-lib compilation generates to be present in /usr/ and that is done via the datadir option. It is Inside /usr/share/alsa/pcm that the file default.pcm is present. Since the error you encountered was "Unknown PCM default" wrong location of the "share" folder could be the issue.

    If you are using the filesystem from arago then the recipe for compiling alsa-lib looks something like this http://arago-project.org/git/?p=arago-oe-dev.git;a=blob_plain;f=recipes/alsa/alsa-lib_1.0.23.bb;hb=HEAD.

    Hope that helps.

    --Vaibhav