I ported the XBMC app to IntelCE baord. And trying to play audio by connecting board to HDMI port.

When an audio file is played i get the error "Failed to innitialise device Please check audio settings".

Follwoing details may help in providing the solution:

# xbmc --version
XBMC Media Center 11.0-BETA2 Git:Unknown
Copyright © 2005-2011 Team XBMC - http://www.xbmc.org


# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: IntelCE310041 [], device 0: pcm_0 [pcm_0]
Subdevices: 1/1
Subdevice #0: subdevice #0

pleaes let me know how to overcome this problem

Is that your only audio device? Is there an onboard soundcard as well as hdmi.

Hi bussiness kid,

Onboard we have this card only.to board we have HMDI port.

I connected HDMI port to TV and trying to play the audio file via XBMC player(by launching the XBMX app in board).

Please let me know how i need to get ridoff this audio issue?

Regards,
Garry

Have you unmuted the card in alsamixer? Run alsamixer, and use 'm' to mute/unmute and arrows to vary other things. Then run 'sudo alsactl store'

we don't have alsa mixer in the board.we have PCM on the board.

In /etc/asounds.conf file folowing settings are used:

pcm.!default {
type plug
slave.pcm "dmixer"

}

pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm "hw:0,0"
rate 48000


}
bindings {
0 0
1 1
}

}

ctl.dmixer {
type hw
card 0
}


Following lines are present in log file:

00:33:23 T:3062356528 ERROR: Creating a Null Audio Renderer, Check your audio
00:35:17 T:3062356528 ERROR: Previous line repeats 1 times.
00:35:17 T:3062356528 WARNING: CLinuxInputDevice::RelEvent: Unknown rel event co
00:36:22 T:3062356528 WARNING: Previous line repeats 3 times.
00:36:22 T:3062356528 ERROR: Creating a Null Audio Renderer, Check your audio
00:37:06 T:3007396720 WARNING: CreateLoader - Unsupported protocol(addons) in ad
00:40:35 T:3062356528 WARNING: Previous line repeats 1 times.
00:40:35 T:3062356528 ERROR: Creating a Null Audio Renderer, Check your audio
00:41:30 T:3062356528 WARNING: CLinuxInputDevice::RelEvent: Unknown rel event co
00:41:46 T:3013606256 WARNING: Previous line repeats 4 times.
00:41:46 T:3013606256 WARNING: Create - Unsupported protocol(newsmartplaylist) i
00:41:46 T:3013606256 WARNING: CreateLoader - Unsupported protocol(newsmartplayl

post the output of
or just copy & paste it.

i Didn't find asound.state

# find -name asound*
./opt/camore/XBMC/share/xbmc/system/asound.conf
./opt/canmore/XBMC.wrking.butcrashing/share/xbmc/system/asound.conf
./opt/canmore/XBMC.latest/system/asound.conf
./opt/canmore/XBMC.latest/share/xbmc/system/asound.conf
./opt/canmore/XBMC/system/asound.conf.xbmcorg
./opt/canmore/XBMC/system/asound.conf
./opt/canmore/XBMC/share/xbmc/system/asound.conf
./opt/canmore/XBMC.nothing/share/xbmc/system/asound.conf
./opt/canmore/XBMC.new/share/xbmc/system/asound.conf
./proc/asound
./etc/asound.conf

I imagine it must be asound.conf. Mine has this sort of thingfor each control in the sound card - there's usually a dozen or so virtual devices in there.
try 'ls -l /etc/asound.state'
note the date/time, and run 'sudo alsactl store'. Then ls -l it again and see if the time has updated. Grok it and see what's enabled/disabled and post that.

below are Contents of asound.conf

pcm.!default {
type plug
slave.pcm "dmixer"

}

pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm "hw:0,0"
rate 48000


}
bindings {
0 0
1 1
}

}

ctl.dmixer {
type hw
card 0
}

That's not what I was hoping for, but it may be the problem. I have 22 controls in /etc/asound.state.

Run alsamixer. If you haven't got alsamixer, install alsa-utils. Then set volumes on anything you can see. I don't know XBMC, and I'd get sound going before I start with some unknown app. If you know it, that's ok. After alsamixer exits (esc) immediately run 'alsactl store'

Then go looking for /etc/asound.state.

Hi All,

Today finally got break through the audio problem over HDMI.
we needed to run /bin/audio_setup_outputs which will eventually configure the HDMI port.

This solution is specific to intelCE boards.

Thanks all for sharing the idea on the issue.

mark this solved, then & thanks for telling us