#apertus IRC Channel Logs

morning everyone!

today I also woke up at 11 AM ;)

hehe

i.e. I think we need to improve that if we plan to stick with the ADV7511 in long term (for whatever reason)

all the monitors I could fine here :)

can the HDMI output mode be configured in the PL/PS 50HZ/60Hz, etc?

depends on what interface is used, the PL code from analog, which interfaces with the linux driver basically creates a 24bit framebuffer

the funny part is, that my LG monitor, which works fine with devices like the raspberry pi, does not show any output via HDMI on the zedboard, but definitely gets detected and also keeps showing a black screen (i.e. doesn't turn off)

my Phillips doesn't get detected and doesn't show anything

I see

btw, I recompiled a better/newer busybox, if anybody is interested, just drop me a note

(which is nice if you want to test a new u-boot version first)

nice!

I feel like nothing can stop us ;)

our lvds lanes have max 300mhz

Stuart said that 1ns = 6" of trace length

does that mean we can ignore any length differences of the lvds trace lines?

those might not be critical, but I'd definitely keep the differences small

you mean like positive/negative lanes of same LVDS pair right?

altera has an IMHO nice document about LVDS routing: www.altera.com/literature/wp/wp_lvdsboard.pdf

how much do they differ?

I am afraid expresspcb has no option to meassure trace lengths

well, you can estimate them by adding up the line lengths

or simply counting the grid squares (as a rough estimate)

of course, the closer the lengths (in general and to each other) the better the signal

all traces LVDS traces are P/N grouped next to each other and have a length of 1.1-1.4"

great

http://avnetexpress.avnet.com/store/em/EMController?term=ASP-134604-01&x=0&y=0&action=products&langId=-1&storeId=500201&catalogId=500201&hbxSType=&N=0&filterButton=true

cool, btw, you mentioned an FMC cable or flexible extension .. any idea what that would cost (e.g. for testing)?

yes

but you can choose that in the design

do I need to care about which LVDS goes to which pin on the FMC connector?

2x 16 LA Bus pairs in two different banks IIRC

the CC pairs are 'special' in such way that they are clock capable

sent enquiry to Samtec

no, the actual pin numbers

1 and 18 the second pair

the zedboard schematics should have that info

do we know what format of the sensor's output?

but I also need the numbering scheme for the footpring pads

the signalling protocol it uses...The format of the data it's sending. I know it uses a number of LVDS channels, but what does it send over those channels?

not to my knowledge

sent

point 4.3 pixel read out

but I'd check with the zedboard gerbers

I just want to double check

yes, I also suggested to build a sensor replacement, which connects to the FMC (or later instead of the sensor) for development and testing

FMC?

ah, yeah

sure, and the code could be used lateron

LVDS negative control channel output

lines are a lot longer than the normal LVDS lines

so its probably not a big deal right?

WARNING:PhysDesignRules:2500 - This design does not have a PS7 block. Instantiate the PS7 block in order to ensure proper fabric tie-offs and correct operation of the processing_system7.

(note: this is a PL only design, so I don't need/want the PS to run anything)

hurray found a schematic error in the design!

sure

yes, we don't want to make things too complicated

in the case of adjusting the sloping zones, it should allow much more detail/flexibility for grading where it's needed most.

time for bed, will be at the university shooting graduation ceremonies tomorrow ;)

"shooting" in the sense of "filming", for our non filmmakers here ;)

which leads me to one of my favourite quotes from my ex boss who has been a camera man for 40 years

where high ranking US diplomats were currently staying

and needed a pan of the city scape on camera

and asked her

good night :)

hehe