All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Howard <mike@dewberryfields.co.uk>
To: alsa-devel@alsa-project.org
Subject: Re: Wandboard Quad - SPDIF issue, no sound
Date: Thu, 26 Jun 2014 15:29:45 +0100	[thread overview]
Message-ID: <53AC2E59.1030601@dewberryfields.co.uk> (raw)
In-Reply-To: <53AAD9D3.2000107@dewberryfields.co.uk>


On 25/06/2014 15:16, Michael Howard wrote:
>
> On 25/06/2014 00:49, Sinan Akman wrote:
>>
>>   Hi Mike
>>
>>> I have tried a second receiver and the results are the same, as in, the
>>> wandboard fails, the cubietruck works. I fear that this a design issue
>>> and I'm wasting your time.
>>
>>   There is one another thing. When you run aplay for testing I suggest
>> you define the format and the rate explicitly and don't use plugin
>> as part of your device. It is possible that your default format that
>> your aplay on wandbord picks is not compatible with what your receiver
>> can handle.
>>
>>   Regards
>>
>>   Sinan Akman
>>
>>
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> Hi Sinan,
>
> Well I've tried all the formats and various rates without suceess.
>
> I've determined the capabilities of the Wandboard spdif to be;
>
> alsacap -d hw:0,0
> *** Exploring configuration space of device `hw:0,0' for playback ***
> 2 channels
> Sampling rate 32000..48000 Hz
> Sample formats: S16_LE, S24_LE
>
> as opposed to the Cubietruck (which works - as does Win7);
>
>  alsacap -d hw:1,0
> *** Exploring configuration space of device `hw:1,0' for playback ***
> 1..2 channels
> Sampling rate 8000..192000 Hz
> Sample formats: S16_LE
> Significant bits: 16
>
> The ouputs of speaker test are almost identical;
>
> Wnadboard;
>
> speaker-test -Dsysdefault:CARD=imxspdif -c2
>
> speaker-test 1.0.25
>
> Playback device is sysdefault:CARD=imxspdif
> Stream parameters are 48000Hz, S16_LE, 2 channels
> Using 16 octaves of pink noise
> Rate set to 48000Hz (requested 48000Hz)
> Buffer size range from 64 to 16384
> Period size range from 32 to 8192
> Using max buffer size 16384
> Periods = 4
> was set period_size = 4096
> was set buffer_size = 16384
>
> Cubietruck;
>
> speaker-test -Dsysdefault:CARD=sunxisndspdif -c2
>
> speaker-test 1.0.25
>
> Playback device is sysdefault:CARD=sunxisndspdif
> Stream parameters are 48000Hz, S16_LE, 2 channels
> Using 16 octaves of pink noise
> Rate set to 48000Hz (requested 48000Hz)
> Buffer size range from 4096 to 32768
> Period size range from 1024 to 8192
> Using max buffer size 32768
> Periods = 4
> was set period_size = 8192
> was set buffer_size = 32768
>
> One obvious difference is that the Wandboard uses 'snd-soc-dummy-dai'.
>
> I'll get a scope on the job this evening, is there anything 
> inparticular I should be looking for?
>
> Cheers,
> Mike.
>
I've used a scope on both the CT & WB but it didn't shed any light on 
the matter. Voltages are as advertised (which maybe the problem) and 
there is very little difference between the frequencies of the two 
boards or how the wave looks. Frequencies are approx 1.78MHz for the 
Cubietruck and approx 1.8MHz for the wandboard.

The volatges match the spec sheets, i.e. 5v for the Cubietruck and 3.3v 
for the Wandboard at VCC whether audio is playing or not.

So unless both my receivers have a problem with only 3.3v I'm at a loss. 
I can't find anything on the limited specs for the receivers relating to 
this.

I guess I'll just sideline the Wandboards and use proper kit instead. I 
can still compile on them, until they overheat :)

Cheers,
Mike.

-- 

  reply	other threads:[~2014-06-26 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 18:07 Wandboard Quad - SPDIF issue, no sound Michael Howard
2014-06-24  5:33 ` Sinan Akman
2014-06-24 14:57   ` Michael Howard
2014-06-24 23:49     ` Sinan Akman
2014-06-25 14:16       ` Michael Howard
2014-06-26 14:29         ` Michael Howard [this message]
2014-06-26 19:07           ` Sinan Akman
2014-06-26 18:56         ` Sinan Akman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53AC2E59.1030601@dewberryfields.co.uk \
    --to=mike@dewberryfields.co.uk \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.