[Open-graphics] Re: Some small changes
wpmcnamara at yahoo.com
Fri Nov 5 14:29:37 EDT 2010
I think I may have asked this before, but I'll ask it again, just in case. One
your board, to the lower left of the S3 are two oscillators. One will be
133MHz, and the other is what?
I suspect your memory errors are, as you say, actually bridge errors. I also
suspect you have a faster clock for the input to the bridge clock generator.
This would mean that the XP10 image I build, which was built for a 125MHz clock,
would actually run the bridge at a faster speed. If this is the case, there are
likely some signals that are violating setup timing do to the faster clock.
From: Mark Marshall <mark.marshall at csr.com>
To: open-graphics at duskglow.com
Sent: Fri, November 5, 2010 1:14:15 PM
Subject: [Open-graphics] Re: Some small changes
On 03/11/2010 02:44, Patrick McNamara wrote:
> On 11/02/2010 07:13 AM, Mark Marshall wrote:
>> First some good news. I've managed to produce images for both FPGA's.
>> For the XP10 I've used "ispLever Starter FPGA 8.1.00.34.21.10". For
>> the S3 I used version 12..00 of the xilinx tools (I forget which
>> I chose, we seem to have every version from 9.1 to 12.3 installed at
> Very cool. What timing errors did you get on the XP10? Assuming that you
> used the constraints from the repo, you likely got errors on the
> bridge_ad signals.
I've not really used my S3 image - I've stuck with yours and tried to not break
compatability. I've made a number of XP10 images and they all seem to have
broadly worked. I have to admit that I find it very hard to find the
significant errors amongst the noise, and I also struggle to understand what
they mean. I can send a log if you are interested, but they are quite boring!
I do get some errors somewhere, but I don't know if this is because I'm running
on a pre-production part? At the moment I see quite obvious errors when the HQ
code reads the text buffer while doing text-convert. I get spurious '$' and '('
characters all over the screen (actually there are a set of places where such a
character might appear, and then I randomly get or don't get it at those
locations - I assume the locations are where the address is some multiple of
The intersting thing is that the font data is read back from the S3 perfectly
(as far as I can tell) as the characters themselves are always perfect. Maybe
it is only the last word of a read that is corrupted? It could also be a bug in
the HQ code.
memtest fails with a minimum of 7000 erros or so, and I can see a definate
pattern to them. I think all of the errors are in the S3 -> XP10 stage, and are
not really memory errors. I'm not sure how to test that.
Open-graphics mailing list
Open-graphics at duskglow.com
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Open-graphics