asoc: no valid backend routes for PCM: SDP4430 Media
List,
After capturing data from DMIC on OMAP4 blaze board with kernel 2.6.38 and save wav data to 38.wav.
But aplay complains "no valid backend routes". See following,
$aplay -f dat 38.wav
[ 157.167724] asoc: no valid backend routes for PCM: SDP4430 Media
aplay: main:654: audio open error: Invalid argument
$ uname -a Linux ubuntu 2.6.38.4+ #58 SMP PREEMPT Fri Jun 3 09:44:19 PDT 2011 armv7l GNU/Linux
Does ALSA add new functionality of backend?
Thanks.
---henry
Quoted 10 lines · hong zhang
List,
After capturing data from DMIC on OMAP4 blaze board with kernel 2.6.38 and save wav data to 38.wav.
But aplay complains "no valid backend routes". See following,
$aplay -f dat 38.wav
[ 157.167724] asoc: no valid backend routes for PCM: SDP4430 Mediaaplay: main:654: audio open error: Invalid argument
This means you have not configured an audio route for playback (i.e. the audio is not routed anywhere from pcm hw:0,0). Use alsamixer and configure the kcontrols to define the audio path. The kcontrol mappings to audio paths are detailed here for OMAP4 :-
http://omappedia.org/wiki/Audio_Drive_Arch
Liam
Liam,
Actually, I could not prove DMIC on OMAP4 blaze board is working in both kernel 2.6.35 and 2.6.38 using arecord and gstreamer-alsa.
In 2.6.35, arecord returns 44 bytes with read error In 2.6.38, arecord collects native data.
Gstreamer-alsa could not get voice after turning off analog captures using amixer.
Any information regarding DMIC on OMAP4? I see people send DMIC patch to 2.6.38.
Please advise.
---henry
Quoted 34 lines · Liam Girdwood
From: Liam Girdwood <[email protected]>
Subject: Re: [alsa-devel] asoc: no valid backend routes for PCM: SDP4430 Media
To: "hong zhang" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Tuesday, June 7, 2011, 3:38 AMQuoted 3 lines · hong zhang
List,
After capturing data from DMIC on OMAP4 blaze board
with kernel 2.6.38 and save wav data to 38.wav.
Quoted 2 lines
But aplay complains "no valid backend routes". See
following,
Quoted 3 lines
$aplay -f dat 38.wav
[ 157.167724] asoc: no valid backend routes forPCM: SDP4430 Media
Quoted 2 lines
aplay: main:654: audio open error: Invalid argument
This means you have not configured an audio route for playback (i.e. the audio is not routed anywhere from pcm hw:0,0). Use alsamixer and configure the kcontrols to define the audio path. The kcontrol mappings to audio paths are detailed here for OMAP4 :-
http://omappedia.org/wiki/Audio_Drive_Arch
Liam
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Quoted 11 lines · hong zhang
Liam,
Actually, I could not prove DMIC on OMAP4 blaze board is working in both kernel 2.6.35 and 2.6.38 using arecord and gstreamer-alsa.
In 2.6.35, arecord returns 44 bytes with read error In 2.6.38, arecord collects native data.
Gstreamer-alsa could not get voice after turning off analog captures using amixer.
Any information regarding DMIC on OMAP4? I see people send DMIC patch to 2.6.38.
DMIC works on OMAP4, can you try my branch :-
https://gitorious.org/omap-audio/linux-audio/commits/lrg/topic/omap-asoc-next-3.1
Liam
Liam,
I have downloaded kernel tar ball. Three questions need your help.
1. which defconfig should be used in arch/arm/configs?
I do not see OMAP4 for SDP4430 (blaze board). Panda does not have DMIC only blaze has it.
2. On blaze board, I have to turn off two analog captures and leave DMIC open. Can you verify my gst-launch is correct? I cannot capture voice from DMIC on OMAP4 blaze board us it.
gst-launch-0.10 -v alsasrc num-buffers=1000 ! 'audio/x-raw-int,rate=8000,channels=1,endianness=1234,width=16,depth=16' ! audioconvert ! wavenc! filesink location=/home/normanc/Desktop/8000.wav
3. If I specify DMIC device, command is rejected.
gst-launch-0.10 -v alsasrc device="hw:0,10" num-buffers=1000 ! 'audio/x-raw-int, rate=8000,channels=1,endianness=1234,width=16,depth=16' ! audioconvert ! wavenc! filesink location=/home/normanc/Desktop/8000.wav
TI support team in France says item 2 should work for DMIC. But I simply could not get it. TI team says item 2 works for "official release 2.6.35-990-omap4 #9".
I have spent 1 week on it with 2.6.35-990-omap4 #9
Please advise!
Thanks.
---henry
Quoted 29 lines · Liam Girdwood
From: Liam Girdwood <[email protected]>
Subject: Re: [alsa-devel] asoc: no valid backend routes for PCM: SDP4430 Media
To: "hong zhang" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Wednesday, June 8, 2011, 9:22 AMQuoted 3 lines · hong zhang
Liam,
Actually, I could not prove DMIC on OMAP4 blaze board
is working in both kernel 2.6.35 and 2.6.38 using arecord and gstreamer-alsa.
Quoted 5 lines
In 2.6.35, arecord returns 44 bytes with read error In 2.6.38, arecord collects native data.
Gstreamer-alsa could not get voice after turning off
analog captures using amixer.
Quoted 2 lines
Any information regarding DMIC on OMAP4? I see people
send DMIC patch to 2.6.38.
Quoted 1 line
DMIC works on OMAP4, can you try my branch :-
https://gitorious.org/omap-audio/linux-audio/commits/lrg/topic/omap-asoc-next-3.1
Liam
Hi Henry,
Quoted 8 lines · hong zhang
Liam,
I have downloaded kernel tar ball. Three questions need your help.
1. which defconfig should be used in
arch/arm/configs?
I do not see OMAP4 for SDP4430 (blaze board). Panda does not have DMIC only blaze has it.
There is an omap2plus defconfig.
Quoted 8 lines
2. On blaze board, I have to turn off two analog captures and leave DMIC open. Can you verify my gst-launch is correct? I cannot capture voice from DMIC on OMAP4 blaze board us it.
gst-launch-0.10 -v alsasrc num-buffers=1000 ! 'audio/x-raw-int,rate=8000,channels=1,endianness=1234,width=16,depth=16' ! audioconvert ! wavenc! filesink location=/home/normanc/Desktop/8000.wav3. If I specify DMIC device, command is rejected.
gst-launch-0.10 -v alsasrc device="hw:0,10" num-buffers=1000 ! 'audio/x-raw-int, rate=8000,channels=1,endianness=1234,width=16,depth=16' ! audioconvert ! wavenc! filesink location=/home/normanc/Desktop/8000.wav
The easiest thing todo first is to get arecord working. Use hw:0,1 for DMIC and make sure you use alsamixer to configure the correct audio paths for DMIC to hw:0,1.
Quoted 6 lines
TI support team in France says item 2 should work for DMIC. But I simply could not get it. TI team says item 2 works for "official release 2.6.35-990-omap4 #9".
I have spent 1 week on it with 2.6.35-990-omap4 #9
Please advise!
It does look like you have not configured the audio route here for the DMIC to hw:0,1. Use the ABE diagram to create your route with alsamixer.
Liam
Quoted 35 lines
Thanks.
---henry
Quoted 29 lines · Liam Girdwood
From: Liam Girdwood <[email protected]>
Subject: Re: [alsa-devel] asoc: no valid backend routes for PCM: SDP4430 Media
To: "hong zhang" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Wednesday, June 8, 2011, 9:22 AMQuoted 3 lines · hong zhang
Liam,
Actually, I could not prove DMIC on OMAP4 blaze board
is working in both kernel 2.6.35 and 2.6.38 using arecord and gstreamer-alsa.
Quoted 5 lines
In 2.6.35, arecord returns 44 bytes with read error In 2.6.38, arecord collects native data.
Gstreamer-alsa could not get voice after turning off
analog captures using amixer.
Quoted 2 lines
Any information regarding DMIC on OMAP4? I see people
send DMIC patch to 2.6.38.
Quoted 1 line
DMIC works on OMAP4, can you try my branch :-
https://gitorious.org/omap-audio/linux-audio/commits/lrg/topic/omap-asoc-next-3.1
Liam
Liam,
Arecord gets data from DMIC! Using following commands.
"arecord -f dat -D plughw:0,0 dmic.wav" with "amixer cset numid=61 1 and amixer cset numid=60 2" to get data from DMIC after turning off two analog captures.
Information from "arecrod -l" is not sync with ABE routing table. For example, "arecord -l" indicates hw:0,10 is DMIC capture but ABE diagram indicates plughw:0,0 can be used for DMIC input.
Are "arecord -l" and "aplay -l" still useful?
---henry
Quoted 109 lines · Liam Girdwood
From: Liam Girdwood <[email protected]>
Subject: Re: [alsa-devel] asoc: no valid backend routes for PCM: SDP4430 Media
To: "hong zhang" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Thursday, June 9, 2011, 4:42 AM
Hi Henry,Quoted 3 lines · hong zhang
Liam,
I have downloaded kernel tar ball. Three questions
need your help.
Quoted 2 lines
1. which defconfig should be used in
arch/arm/configs?Quoted 1 line
I do not see OMAP4 for SDP4430 (blaze
board). Panda does not have DMIC
Quoted 2 lines
only blaze has it.
There is an omap2plus defconfig.
Quoted 1 line
2. On blaze board, I have to turn off two analog
captures and leave DMIC open. Can you verify my gst-launch is correct? I cannot capture voice from DMIC on OMAP4 blaze board us it.
Quoted 2 lines
gst-launch-0.10 -v alsasrc
num-buffers=1000 ! 'audio/x-raw-int,rate=8000,channels=1,endianness=1234,width=16,depth=16' ! audioconvert ! wavenc! filesink location=/home/normanc/Desktop/8000.wav
Quoted 4 lines
3. If I specify DMIC device, command is rejected.
gst-launch-0.10 -v alsasrc device="hw:0,10"
num-buffers=1000 ! 'audio/x-raw-int, rate=8000,channels=1,endianness=1234,width=16,depth=16' ! audioconvert ! wavenc! filesink location=/home/normanc/Desktop/8000.wav
Quoted 1 line
The easiest thing todo first is to get arecord working. Use hw:0,1 for DMIC and make sure you use alsamixer to configure the correct audio paths for DMIC to hw:0,1.
Quoted 1 line
TI support team in France says item 2 should work for
DMIC. But I simply could not get it. TI team says item 2 works for "official release 2.6.35-990-omap4 #9".
Quoted 5 lines
I have spent 1 week on it with 2.6.35-990-omap4 #9
Please advise!
It does look like you have not configured the audio route here for the DMIC to hw:0,1. Use the ABE diagram to create your route with alsamixer.
Liam
Quoted 8 lines
Thanks.
---henry
Quoted 2 lines · Liam Girdwood
From: Liam Girdwood <[email protected]>
Subject: Re: [alsa-devel] asoc: no valid backendroutes for PCM: SDP4430 Media
Quoted 2 lines
Quoted 2 lines
To: "hong zhang" <[email protected]>
Cc: "[email protected]"Quoted 5 lines
Quoted 5 lines
Date: Wednesday, June 8, 2011, 9:22 AM
Quoted 3 lines · hong zhang
Liam,
Actually, I could not prove DMIC on OMAP4
blaze board
Quoted 1 line
Quoted 1 line
is working in both kernel 2.6.35 and 2.6.38 using
arecord
Quoted 3 lines
Quoted 3 lines
and gstreamer-alsa.
Quoted 2 lines
In 2.6.35, arecord returns 44 bytes with read
error
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
In 2.6.38, arecord collects native data.
Gstreamer-alsa could not get voice after
turning off
Quoted 3 lines
Quoted 3 lines
analog captures using amixer.
Quoted 2 lines
Any information regarding DMIC on OMAP4? I see
people
Quoted 10 lines
Quoted 10 lines
send DMIC patch to 2.6.38.
Quoted 1 line
DMIC works on OMAP4, can you try my branch :-
https://gitorious.org/omap-audio/linux-audio/commits/lrg/topic/omap-asoc-next-3.1
Liam
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Quoted 11 lines · hong zhang
Liam,
Arecord gets data from DMIC! Using following commands.
"arecord -f dat -D plughw:0,0 dmic.wav" with "amixer cset numid=61 1 and amixer cset numid=60 2" to get data from DMIC after turning off two analog captures.
Information from "arecrod -l" is not sync with ABE routing table. For example, "arecord -l" indicates hw:0,10 is DMIC capture but ABE diagram indicates plughw:0,0 can be used for DMIC input.
Are "arecord -l" and "aplay -l" still useful?
Yes, but not for OMAP4 atm.
Thanks
Liam
Quoted 115 lines
---henry
Quoted 109 lines · Liam Girdwood
From: Liam Girdwood <[email protected]>
Subject: Re: [alsa-devel] asoc: no valid backend routes for PCM: SDP4430 Media
To: "hong zhang" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Thursday, June 9, 2011, 4:42 AM
Hi Henry,Quoted 3 lines · hong zhang
Liam,
I have downloaded kernel tar ball. Three questions
need your help.
Quoted 2 lines
1. which defconfig should be used in
arch/arm/configs?Quoted 1 line
I do not see OMAP4 for SDP4430 (blaze
board). Panda does not have DMIC
Quoted 2 lines
only blaze has it.
There is an omap2plus defconfig.
Quoted 1 line
2. On blaze board, I have to turn off two analog
captures and leave DMIC open. Can you verify my gst-launch is correct? I cannot capture voice from DMIC on OMAP4 blaze board us it.
Quoted 2 lines
gst-launch-0.10 -v alsasrcnum-buffers=1000 ! 'audio/x-raw-int,rate=8000,channels=1,endianness=1234,width=16,depth=16' ! audioconvert ! wavenc! filesink location=/home/normanc/Desktop/8000.wav
Quoted 4 lines
3. If I specify DMIC device, command is rejected.
gst-launch-0.10 -v alsasrc device="hw:0,10"
num-buffers=1000 ! 'audio/x-raw-int, rate=8000,channels=1,endianness=1234,width=16,depth=16' ! audioconvert ! wavenc! filesink location=/home/normanc/Desktop/8000.wav
Quoted 1 line
The easiest thing todo first is to get arecord working. Use hw:0,1 for DMIC and make sure you use alsamixer to configure the correct audio paths for DMIC to hw:0,1.
Quoted 1 line
TI support team in France says item 2 should work for
DMIC. But I simply could not get it. TI team says item 2 works for "official release 2.6.35-990-omap4 #9".
Quoted 5 lines
I have spent 1 week on it with 2.6.35-990-omap4 #9
Please advise!
It does look like you have not configured the audio route here for the DMIC to hw:0,1. Use the ABE diagram to create your route with alsamixer.
Liam
Quoted 8 lines
Thanks.
---henry
Quoted 2 lines · Liam Girdwood
From: Liam Girdwood <[email protected]>
Subject: Re: [alsa-devel] asoc: no valid backendroutes for PCM: SDP4430 Media
Quoted 2 lines
Quoted 2 lines
To: "hong zhang" <[email protected]>
Cc: "[email protected]"Quoted 5 lines
Quoted 5 lines
Date: Wednesday, June 8, 2011, 9:22 AM
Quoted 3 lines · hong zhang
Liam,
Actually, I could not prove DMIC on OMAP4
blaze board
Quoted 1 line
Quoted 1 line
is working in both kernel 2.6.35 and 2.6.38 using
arecord
Quoted 3 lines
Quoted 3 lines
and gstreamer-alsa.
Quoted 2 lines
In 2.6.35, arecord returns 44 bytes with read
error
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
In 2.6.38, arecord collects native data.
Gstreamer-alsa could not get voice after
turning off
Quoted 3 lines
Quoted 3 lines
analog captures using amixer.
Quoted 2 lines
Any information regarding DMIC on OMAP4? I see
people
Quoted 10 lines
Quoted 10 lines
send DMIC patch to 2.6.38.
Quoted 1 line
DMIC works on OMAP4, can you try my branch :-
https://gitorious.org/omap-audio/linux-audio/commits/lrg/topic/omap-asoc-next-3.1
Liam
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Quoted 17 lines · Liam Girdwood
From: Liam Girdwood <[email protected]>
Subject: Re: [alsa-devel] asoc: no valid backend routes for PCM: SDP4430 Media
To: "hong zhang" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Thursday, June 9, 2011, 12:48 PMQuoted 3 lines · hong zhang
Liam,
Arecord gets data from DMIC! Using following
commands.
Quoted 2 lines
"arecord -f dat -D plughw:0,0 dmic.wav" with "amixer
cset numid=61 1 and
Quoted 1 line
amixer cset numid=60 2" to get data from DMIC after
turning off two analog captures.
Quoted 2 lines
Information from "arecrod -l" is not sync with ABE
Quoted 8 lines
routing table. For example, "arecord -l" indicates hw:0,10 is DMIC capture but
Quoted 1 line
ABE diagram indicates plughw:0,0 can be used for DMIC
input.
Quoted 2 lines
Are "arecord -l" and "aplay -l" still useful?
Yes, but not for OMAP4 atm.
1. What is OMAP4 ATM?
2. Why "hw:0,10 DMIC capture" does not work for DMIC input?
Quoted 4 lines
Thanks
Liam
Re: asoc: no valid backend routes for PCM
Hello,
I am not able to hear audio on my headset when it connect it to panda board.
What mite be the issue?
Also panda does not has DMIC does this make any difference ?
Regards
Sarika
Re: asoc: no valid backend routes for PCM
Quoted 3 lines · Sarika
Hello,
I am not able to hear audio on my headset when it connect it to panda board.
What mite be the issue?
This means you have no valid audio route from your pcm device to your headphone.
Please use the supplied UCM configuration files (with Ubuntu) to set the route or use alsamixer to do this manually.
http://www.omappedia.org/wiki/Audio_Drive_Arch
Quoted 2 lines
Also panda does not has DMIC does this make any difference ?
No.
Liam
Quoted 8 lines
Regards
Sarika_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
A message that is not in the archive (sent off-list or not yet received): CAHgabbYxe-mzwhxiivj5Xmqdq3FQuZ3ZFhgU4wy_bCosm2BhwA@mail.gmail.com
Re: asoc: no valid backend routes for PCM
Please don't drop the list from replies.
Quoted 3 lines · sarika baby
Hello,
Thanks for your information, but can you tell that if i have to add the audio route should i have to do it at kernel drivers level or else at ALSA (mydroid level) ?
The routes are all configured in userspace with either UCM, alsamixer, amixer or by calling the alsa-lib C API.
Liam
Quoted 38 lines
Thanks and Regards
SoujanyaOn Fri, Aug 19, 2011 at 9:50 PM, Liam Girdwood <[email protected] <mailto:[email protected]>> wrote:
On 19/08/11 08:53, Sarika wrote:
> Hello,
> I am not able to hear audio on my headset when it connect it to panda board.
> What mite be the issue?This means you have no valid audio route from your pcm device to your headphone.
Please use the supplied UCM configuration files (with Ubuntu) to set the route or use alsamixer to do this manually.
http://www.omappedia.org/wiki/Audio_Drive_Arch
> Also panda does not has DMIC does this make any difference ?
>No.
Liam
> Regards
> Sarika
>
>
> _______________________________________________
> Alsa-devel mailing list
> [email protected] <mailto:[email protected]> > http://mailman.alsa-project.org/mailman/listinfo/alsa-develSignature · 1 line
SarikA