From: Daniel Mack <zonque@gmail.com>
To: Julian Scheel <julian@jusst.de>
Cc: alsa-devel@alsa-project.org, lee188@singnet.com.sg
Subject: Re: USB asynchronous mode feedback format
Date: Thu, 14 Oct 2010 17:39:13 +0200 [thread overview]
Message-ID: <20101014153912.GA28334@wok> (raw)
In-Reply-To: <201010141710.02194.julian@jusst.de>
On Thu, Oct 14, 2010 at 05:10:01PM +0200, Julian Scheel wrote:
> I did a capture of the same signal, but this time not just a short snap, but a
> whole memory dump of the oscilloscope. I did a plot with gnuplot and uploaded
> it here:
> http://jusst.de/files/i2s_plot.png
>
> As it's 0,5MB big I didn't want to send it as attachment...
>
> Would you agree that the data (this time blue channel) is delayed too much?
> Looks like it's at least 2 cycles behind the LRCK toggle.
> Would it be possible that this is the reason for the DAC not understanding the
> data?
Well, even if it was, you should hear some sound. It might be distorted,
but if you don't get any output, the reason is somewhere else.
Did you check the schematics of your board in comparison to the
reference diagrams in the codec's datasheet? Are there any other things
to be considered maybe?
What about the voltage levels? Are they within the specs? I had a quick
look and it seems that Vdd on the codec has to be within 3.0 .. 3.6V,
while the signals you provide rather seem to be in the range of 5V? The
absolute maximum ratings say that Vdd must not be greater than 4.0V.
Also note that ~11MHz is already in high-speed in a way, so you should
pay attention to data integrity on your bus. I mention that because the
board you sent a link about earlier seems to have terminal blocks for
all signals, so keep the traces short.
I'd suggest to double-check such electicals details first :)
Daniel
next prev parent reply other threads:[~2010-10-14 15:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 8:47 USB asynchronous mode feedback format lee188
2010-10-14 10:27 ` Julian Scheel
2010-10-14 10:48 ` Daniel Mack
2010-10-14 11:01 ` Julian Scheel
2010-10-14 11:16 ` Daniel Mack
2010-10-14 11:32 ` Julian Scheel
2010-10-14 12:06 ` Daniel Mack
2010-10-14 12:30 ` Julian Scheel
2010-10-14 12:33 ` Daniel Mack
2010-10-14 12:56 ` Julian Scheel
2010-10-14 15:10 ` Julian Scheel
2010-10-14 15:33 ` Alex Lee
2010-10-14 15:39 ` Daniel Mack [this message]
2010-10-14 15:54 ` Julian Scheel
2010-10-14 16:11 ` Daniel Mack
2010-10-14 20:14 ` Julian Scheel
2010-10-15 8:59 ` Julian Scheel
2010-10-15 9:03 ` Daniel Mack
2010-10-18 16:53 ` Julian Scheel
[not found] ` <3879AFD1-61E6-47FB-8ECB-8A7D7B233B3B@singnet.com.sg>
2010-10-14 11:44 ` Julian Scheel
2010-10-14 11:56 ` Daniel Mack
2010-10-14 11:58 ` Julian Scheel
2010-10-14 15:28 ` Alex Lee
2010-10-14 15:43 ` Julian Scheel
2010-10-15 12:08 ` Julian Scheel
2010-10-15 12:52 ` Alex Lee
2010-10-15 13:04 ` Julian Scheel
2010-10-15 13:31 ` Alex Lee
2010-10-15 14:24 ` Julian Scheel
2010-10-15 14:34 ` Clemens Ladisch
2010-10-16 10:23 ` Julian Scheel
2010-10-15 14:41 ` Alex Lee
2010-10-15 17:16 ` Julian Scheel
2010-10-15 17:19 ` Julian Scheel
2010-10-16 1:52 ` Alex Lee
2010-10-16 10:25 ` Julian Scheel
2010-10-16 13:58 ` Alex Lee
2010-10-16 16:30 ` Julian Scheel
2010-10-16 18:52 ` Julian Scheel
2010-10-17 10:53 ` Julian Scheel
2010-10-17 11:16 ` Alex Lee
-- strict thread matches above, loose matches on Subject: below --
2010-10-13 15:50 Julian Scheel
2010-10-14 1:28 ` Alex
2010-10-14 5:57 ` Julian Scheel
2010-10-14 6:25 ` Alex
2010-10-14 8:46 ` lee188
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=20101014153912.GA28334@wok \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=julian@jusst.de \
--cc=lee188@singnet.com.sg \
/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.