2011-01-11 08:51:58     BF537, AD73311 - ALSA SOC Problems

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

2011-01-11 08:51:58     BF537, AD73311 - ALSA SOC Problems

Frank Gill (UNITED STATES)

Message: 97343   

 

Hi,

 

My client has a custom board with BF537 and AD73311 as the audio codec. I'm using 2010RC5 (I haven't changed any of the default options).

 

The tone test runs fine. Also I ran (arecord | aplay) and I can hear everything I say.

 

However, when I run linphone, it rings on both ends, but when I answer there is no voice. There is nothing being transmitted over TX or RX once the call is answered.

 

There are 2 problems:

 

1. Unknown Parameters 0 / Invalid CTL Argument

 

2. The Network Address is unreachable output. (even though it connects the call on the other end)

 

I also tried changing between OSS and ALSA using the soundcard use option.

 

Could someone please help? Thanks in advance.

 

Below is the output from the console:

 

root:  /> modprobe snd-pcm-os

root:  /> modprobe snd-ad73311

 

No device for DAI AD7331

dma rx:3 tx:4, err irq:45, regs:ffc0080

dma_alloc_init: dma_page @ 0x001d5000 - 256 pages at 0x07f0000

asoc: AD73311 <-> bf5xx-i2s mapping ok

 

root:  /> ton

TONE: generating sine wave at 1000 Hz...

 

root:  /> arecord | aplay

Recording WAVE 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono

Playing WAVE 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono snd_pcm_update_hw_ptr0: 2 callbacks suppressed

 

root: /> linphonec

 

NLS disabled.

 

ALSA lib /home/fgill/2010R1-RC5/lib/alsa-lib/alsa-lib-1.0.18/src/conf.c:3952:(snd_config_expand) Unknown parameters 0  ALSA lib /home/fgill/2010R1-RC5/lib/alsa-lib/alsa-lib-1.0.18/src/control/control.c:909:(snd_ctl_open_noupdate) Invalid CTL default: 0 Ready Warning: video is disabled in linphonec, use -V or -C or -D to enable

linphonec> DEBUG: [get_output_if] connect: Network is unreachable linphonec> soundcard -list   

0: ALSA: default device

1: ALSA: bf5xx_ad73311

2: OSS: /dev/dsp

 

QuoteReplyEditDelete

 

 

2011-01-12 01:45:36     Re: BF537, AD73311 - ALSA SOC Problems

Frank Gill (UNITED STATES)

Message: 97361   

 

I broke the message above into multiple lines. The horizontal scroll was hiding the Reply buttons.

 

Hi,

 

My client has a custom board with BF537 and AD73311 as the audio codec. I'm using 2010RC5 (I haven't changed any of the default options). 

 

The tone test runs fine. Also I ran (arecord | aplay) and I can hear everything I say. However, when I run linphone, it rings on both ends, but when I answer there is no voice. There is nothing being transmitted over TX or RX once the call is answered. 

 

There are 2 problems:

 

1. Unknown Parameters 0 / Invalid CTL Argument

 

2. The Network Address is unreachable output. (even though it connects the call on the other end)

 

I also tried changing between OSS and ALSA using the soundcard use option.

 

Could someone please help? Thanks in advance.

 

Below is the output from the console:

root: /> modprobe snd-pcm-os

root: /> modprobe snd-ad73311

No device for DAI AD7331

dma rx:3 tx:4, err irq:45, regs:ffc0080

dma_alloc_init: dma_page @ 0x001d5000 - 256 pages at 0x07f0000

asoc: AD73311 <-> bf5xx-i2s mapping ok

 

root: /> tone

TONE: generating sine wave at 1000 Hz...

 

root: /> arecord | aplay

Recording WAVE 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono

Playing WAVE 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono snd_pcm_update_hw_ptr0: 2 callbacks suppressed

 

root: /> linphonec

NLS disabled.

ALSA lib /home/fgill/2010R1-RC5/lib/alsa-lib/alsa-lib-1.0.18/src/conf.c:3952:(snd_config_expand) Unknown parameters 0 ALSA lib /home/fgill/2010R1-RC5/lib/alsa-lib/alsa-lib-1.0.18/src/control/control.c:909:(snd_ctl_open_noupdate) Invalid CTL default: 0

Ready Warning: video is disabled in linphonec, use -V or -C or -D to enable

 

linphonec>

DEBUG: [get_output_if] connect: Network is unreachable

 

linphonec> soundcard -list

0: ALSA: default device

1: ALSA: bf5xx_ad73311

2: OSS: /dev/dsp

QuoteReplyEditDelete

 

 

2011-01-12 01:53:05     Re: BF537, AD73311 - ALSA SOC Problems

Aaron Wu (CHINA)

Message: 97362   

 

We will look into this and be back to you

QuoteReplyEditDelete

 

 

2011-01-12 02:14:25     Re: BF537, AD73311 - ALSA SOC Problems

Frank Gill (UNITED STATES)

Message: 97367   

 

Thanks Aaron.

 

I've attached the .linphonerc file that i've staged in romfs. I also tried changing the settings in my host linphonerc file to match these as well, but no luck there.

 

File attached below.

 

I haven't made any changes to the alsa conf files.

 

linphonec

QuoteReplyEditDelete

 

 

2011-01-12 05:40:59     Re: BF537, AD73311 - ALSA SOC Problems

Aaron Wu (CHINA)

Message: 97393   

 

I had a try on my side, did not find the two problems. Looks like you are encountering some network problem. Maybe you should first make sure the network  is OK? here is some info for linphone on wiki:    docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:linphone

QuoteReplyEditDelete

 

 

2011-01-12 08:44:56     Re: BF537, AD73311 - ALSA SOC Problems

Frank Gill (UNITED STATES)

Message: 97398   

 

Yeah, I was following that link that you sent over. I'm verifying the network connectivity again.

 

Let's see. I'll update the thread once I find out more. Thanks.

QuoteReplyEditDelete

 

 

2011-01-12 11:40:28     Re: BF537, AD73311 - ALSA SOC Problems

Mike Frysinger (UNITED STATES)

Message: 97401   

 

the linphone network settings can be a bit picky.  how many interfaces do you have ?  are they all routable to the internet ?  if not, the warning might be harmless.

QuoteReplyEditDelete

 

 

2011-01-12 12:03:38     Re: BF537, AD73311 - ALSA SOC Problems

Frank Gill (UNITED STATES)

Message: 97403   

So the network issues are resolved. It had to do with my registrar setting, so the sip address wasn't registered correctly as a result of which when I would call the network address it would say network unreachable. Another reason for those network related print statements was that I had not set a default gateway. Unless you do that, it will spit out some network related messages, but they're just warnings. I didnt need a default gateway but I'm just putting this info here for other people's help.

 

In short, no more software/hardware connectivity issues.

 

I've run linphone again, but i'm still getting the following error when I launch linphone:

 

ALSA lib /home/fgilani/2010R1-RC5/lib/alsa-lib/alsa-lib-1.0.18/src/conf.c:3953:(snd_config_expand) Unknown parameters 0 ALSA lib /home/fgilani/2010R1-RC5/lib/alsa-lib/alsa-lib-1.0.18/src/control/control.c:909:(snd_ctl_open_noupdate) Invalid CTL default:0

 

In addition while the call is connected, I'm getting the following errors related to ORTP.

 

linphonec> warning: Unknown nb_ctl request: 12

ortp-error-Could not set vbr mode to speex encoder.

warning: Unknown nb_ctl request: 34

 

Also if anyone has any alsa configuration files or linphone files that they're using in any configuration that works, maybe that might help? I want to rule out any sampling issues and make sure both sides are running the same settings. I've tried with one set of files, but those didn't appear to make any difference.

 

i'm kinda stuck. Can anyone help troubleshoot?

Attachments

Outcomes