2008-05-30 00:29:37     including audio driver in BF527EZKIT

2008-05-30 00:29:37     including audio driver in BF527EZKIT

deepthi kiran (INDIA)

Message: 56441   

Hi,

   I tried to add SoC WM8731 audio driver for BF527EZkit board in uClinux-dist-2008R1-RC8 dist, but Iam getting lot of compilation  problems with this , first I selected only "SoC WM8731 Audio support for BF5xx ezkit" with the option " ALSA for SoC audio support  " ," SoC Audio for the ADI BF5xx chip", "Enable True MMAP Support" selected. with this Iam getting compilation error

"(.text+0x12b54): undefined reference to `bf5xx_ac97_write'

sound/built-in.o: In function `sport_tx_stop':

(.text+0x12b60): undefined reference to `bf5xx_ac97_write'

sound/built-in.o: In function `sport_tx_start':

(.text+0x13b0a): undefined reference to `bf5xx_ac97_write'

sound/built-in.o: In function `sport_tx_start':

(.text+0x13b14): undefined reference to `bf5xx_ac97_write'

make[1]: *** [.tmp_vmlinux1] Error 1"

Then I tried selecting  "SoC AC97 Audio support for BF5xx" also then Iam getting error like

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_send_and_recv':

(.text+0xe18): multiple definition of `sport_send_and_recv'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x122c): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_set_err_callback':

(.text+0x2e4): multiple definition of `sport_set_err_callback'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x6f8): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_dump_stat':

(.text+0x3bc): multiple definition of `sport_dump_stat'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x7d0): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_tx_start':

(.text+0x12d8): multiple definition of `sport_tx_start'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x16ec): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_rx_start':

(.text+0x110c): multiple definition of `sport_rx_start'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x1520): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `incfrag':

(.text+0xe0): multiple definition of `incfrag'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x4f4): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_set_multichannel':

(.text+0x670): multiple definition of `sport_set_multichannel'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0xa84): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_config_rx_dma':

(.text+0x1024): multiple definition of `sport_config_rx_dma'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x1438): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_init':

(.text+0xa40): multiple definition of `sport_init'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0xe54): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_rx_stop':

(.text+0x740): multiple definition of `sport_rx_stop'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0xb54): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_done':

(.text+0x268): multiple definition of `sport_done'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x67c): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_tx_stop':

(.text+0x478): multiple definition of `sport_tx_stop'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x88c): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_config_rx':

(.text+0x5f8): multiple definition of `sport_config_rx'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0xa0c): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_curr_offset_rx':

(.text+0x45c): multiple definition of `sport_curr_offset_rx'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x870): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `decfrag':

(.text+0x10c): multiple definition of `decfrag'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x520): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_curr_offset_tx':

(.text+0x440): multiple definition of `sport_curr_offset_tx'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x854): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_set_rx_callback':

(.text+0x374): multiple definition of `sport_set_rx_callback'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x788): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_config_tx_dma':

(.text+0x898): multiple definition of `sport_config_tx_dma'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0xcac): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_set_tx_callback':

(.text+0x32c): multiple definition of `sport_set_tx_callback'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0x740): first defined here

sound/soc/blackfin/snd-soc-bf5xx-i2s.o: In function `sport_config_tx':

(.text+0x638): multiple definition of `sport_config_tx'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.text+0xa4c): first defined here

sound/soc/blackfin/snd-soc-bf5xx-wm8731.o:(.bss+0x0): multiple definition of `sport_handle'

sound/soc/blackfin/snd-soc-bf5xx-ac97.o:(.bss+0x0): first defined here

Only if I compile with the   "SoC WM8731 " as a module along with selecting  "SoC AC97 Audio support for BF5xx", I am able to compile the dist. If I load the image on BF527 board and try to do insmod the Iam getting,

insmod snd-soc-bf5xx-wm8731.ko

snd_soc_bf5xx_wm8731: Unknown symbol _soc_codec_dev_wm8731

snd_soc_bf5xx_wm8731: Unknown symbol _bf5xx_i2s_dai

snd_soc_bf5xx_wm8731: Unknown symbol _wm8731_dai

insmod: cannot insert 'snd-soc-bf5xx-wm8731.ko': Unknown symbol in module (-1):

No such file or directory

what need to be done for this, Is audio is tested for BF527 EZkit board or is it experimantal, please suggest me if I have missed any thing while incluing the audio driver.

  actually we should not select "SoC AC97 Audio support for BF5xx" only right?? if so it will try to initilize AD1980 SoC Audio Codec during the initilization only.

QuoteReplyEditDelete

2008-05-30 00:36:23     Re: including audio driver in BF527EZKIT

Mike Frysinger (UNITED STATES)

Message: 56442   

the audio codec on the BF527c does not work currently

QuoteReplyEditDelete

2008-05-30 00:37:53     Re: including audio driver in BF527EZKIT

Yi Li (CHINA)

Message: 56443   

We are still working on that driver.

QuoteReplyEditDelete

2008-05-30 00:45:47     Re: including audio driver in BF527EZKIT

deepthi kiran (INDIA)

Message: 56445   

We are working on BF527 not on BF527c,so what about BF527, i.e, "WM8731" audio driver

Do we have internal audio codec or external audio codec on BF527EZkit

QuoteReplyEditDelete

2008-05-30 03:53:33     Re: including audio driver in BF527EZKIT

Yi Li (CHINA)

Message: 56450   

There is no audio codec on BF527 EZkit. (There is internal audio codec on BF527C EZkit).

QuoteReplyEditDelete

2008-05-30 04:10:53     Re: including audio driver in BF527EZKIT

Konstantin Hartwich (GERMANY)

Message: 56452   

If you have BF527 EZKIT LITE Rev 1.4  like I do, this means, as far as i know, there is no codec on board, neither on the BF527 (which by design has none) nor on the kit board. Analog Devices Page reads to that as follows: AUDIO CODEC obly on Revision 1.0

this is on my oponion a big deal, since I got it in the belief it were there. now I am waiting for a reference board my enterprise is designning, including a top codec for audio hi performance processing, which means to adapt ALSA and stuff.

The forum also reads of a USB OTG bug in the silicon Revisions 0.0 and 0.1 on the BF527, which stands in the way of successfully trzing out the OTG under uClinux, or am I informed wrong? Please correct if so..

QuoteReplyEditDelete

2008-05-30 05:00:04     Re: including audio driver in BF527EZKIT

Michael Hennerich (GERMANY)

Message: 56468   

AFAIK all the newer BF527-EZkit (including 1.4) are assembled with a BF527C.

So you should have an Audio Codec!

And you should be able to test USB HOST and DEVICES. It's just no guarantee that it works reliably.

I haven't seen issues so far.

-Michael