Yours sincerely,
Floris Bos
--
Yours sincerely,
Floris Bos
--
A10/A13 chips have mainly been used in systems with fixed monitors (or
semi-fixed like TVs) . There probably hasn't been much work done on
the code that supports general purpose plug-in monitors. It not that
hard to hook the code up, but someone has to do it. The kernel already
knows how to decode the EDID. The decoded bits just need to poke into
the right places in the A10/13 video drivers to set the indicated
mode. Some of that poking code is likely missing.
In your older kernel, the kernel decodes the EDID. It then pokes the
video driver and says 'set RGB mode'. If you go look the function for
setting RGB mode it is probably empty in the source code because
nobody has written it yet. In your later kernel someone added it.
EDID also tells the resolution. The functions in the A10/13 video
driver for setting the resolution are probably do-nothing stubs and
they need to be implemented.
Anthony
--
Think the DDC pins should be hooked up as well, in order to be able to
get EDID support at some stage.
(to detect what resolutions the monitor supports, and as a means to
detect if anything is connected to the port. So that video output can be
handled dynamically in the future, instead of the current practice of
hardcoding settings in .fex files)
Yours sincerely,
Floris Bos
On Tuesday, October 2, 2012 4:09:48 PM UTC-7, Max wrote:
Think the DDC pins should be hooked up as well, in order to be able to
get EDID support at some stage.
(to detect what resolutions the monitor supports, and as a means to
detect if anything is connected to the port. So that video output can be
handled dynamically in the future, instead of the current practice of
hardcoding settings in .fex files)
Yours sincerely,
Floris Bos
I think that would be a good idea so it is future proof. Do you happen to know if the DDC pins are broken out on the cubieboard? Or even if the A10 provides this signalling natively? According to Wikipedia it looks like it is based in I2C, so theoretically we could just do it manually if it doesn't, correct?
If you could provide some additional details about DDC if you know more that'd be helpful. To be honest I don't really know anything about the VGA spec, I'm just going off of the schematics that others have posted.
I am afraid I'm not going to be much help with that.
More of a software development person, then into the electronics side of things.
Just know enough about it, that if the pins are not connected anywhere in the first place, DCC/EDID never has a chance of working. :-)
And I do think that functionality is essential and "not optional", if there is the intention of making devices like this a bit more mainstream in the future.
End-users expect to be able to insert the plug into either the vga or hdmi port, and have it "just work".
Yours sincerely,
Floris Bos
Anyone got time to looks for a shallow HD15 connector for the VGA? The spot I want to put it on only has about 11mm before it runs into the mounting post of the Cubieboard. I know there are some shallow HD15 connectors but the first couple I looked at were ~15mm deep.
[disp_init]disp_init_enable = 1disp_mode = 0screen0_output_type = 4screen0_output_mode = 4screen1_output_type = 2screen1_output_mode = 14fb0_framebuffer_num = 2fb0_format = 10fb0_pixel_sequence = 0fb0_scaler_mode_enable = 1fb1_framebuffer_num = 2fb1_format = 10fb1_pixel_sequence = 0fb1_scaler_mode_enable = 1
;----------------------------------------------------------------------------------;disp init configuration;;disp_mode (0:screen0<screen0,fb0> 1:screen1<screen1,fb0> 2:two_diff_screen_diff_contents<screen0,screen1,fb0,fb1>; 3:two_same_screen_diff_contets<screen0,screen1,fb0> 4:two_diff_screen_same_contents<screen0,screen1,fb0>);screenx_output_type (0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga);screenx_output_mode (used for tv/hdmi output, 0:480i 1:576i 2:480p 3:576p 4:720p50 5:720p60 6:1080i50 7:1080i60 8:1080p24 9:1080p50 10:1080p60 11:pal 14:ntsc);screenx_output_mode (used for vga output, 0:1680*1050 1:1440*900 2:1360*768 3:1280*1024 4:1024*768 5:800*600 6:640*480 10:1920*1080 11:1280*720);fbx format (4:RGB655 5:RGB565 6:RGB556 7:ARGB1555 8:RGBA5551 9:RGB888 10:ARGB8888 12:ARGB4444);fbx pixel sequence (0:ARGB 1:BGRA 2:ABGR 3:RGBA) --- 0 for linux, 2 for android;---------------------------------------------------------------------------------
OK guys, I'm posting this here as to not clutter up the Baseboard thread. I've made some progress with some other action items and decided I would try VGA today. I'm running the Linaro Ubuntu Desktop off of a SD Card because at the moment it's easier for me to modify the script.bin file.
Anyone got any ideas on what else I can try?
-- Yours sincerely, Floris Bos
To use VGA or composite output, download mele-a1000-vga_hwpack_2012.06.13.7z instead of mele-a1000_hwpack_2012.06.13.7z.
So we are getting signals out to the VGA connector, there's just something not right. Note that the RED signal is at a lower level than the syncs which I believe is correct, syncs should be at 5V and RGB at 1.8V?
So we are getting signals out to the VGA connector, there's just something not right. Note that the RED signal is at a lower level than the syncs which I believe is correct, syncs should be at 5V and RGB at 1.8V?
The level is actually at 1.4V so double what it's supposed to be. I wonder if the levels need to be reduced and that's the problem? There wasn't any on the reference schematic and it would be a bit odd if the A10 has dedicated RGB pins yet puts out the wrong level, or on 2nd hand that could just be yet another undocumented item we're uncovering... --
--
You received this message because you are subscribed to the Google Groups "Cubieboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cubieboard+...@googlegroups.com.
I do have a ton of new information to digest but what still isn’t making sense is that the TVOUT circuit in the A10 is referenced to 3.3V and all schematics I have seen only have the 75 ohm pull-downs on the RGB signals so if I’m measuring 1.4V there must be something I/we are missing?
--
You received this message because you are subscribed to the Google Groups "Cubieboard" group.
To unsubscribe from this group, send email to cubieboard+...@googlegroups.com.
OK, I need to fix my SD Card but I'll do that shortly and post the results. I forgot all about xrandr!
OK guys, I need you help please. I'm not getting a signal on the VGA and I'm thinking it must be something to do with the kernel not set properly. I started thinking about the 1.4V levels on the RGB signals and decided that the level was double because the signal was being single-ended terminated by my 75 ohm pull-downs. Ideally the Cubie would also have these 75 ohm pull-downs at the source creating a 75 ohm impedance signal.
I got Mele A1000 that can be flashed with anything you want. So if you guys need to check something on another hardware just let me know.
--
You received this message because you are subscribed to the Google Groups "Cubieboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cubieboard+...@googlegroups.com.
Visit this group at http://groups.google.com/group/cubieboard?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
I just feel better putting out a board that I confirmed worked but I just don't have the time right now for VGA. Need to start shipping the baseboard too, I see others are already starting to design them for some reason.
First google's link to manual http://www.henriknordstrom.net/code/A10/doc/A10%20EVB%20Manual.pdf
HI,Do you use buffers for Hsync and Vsync? What is the buffer chip you use? and whats screen resolution is set? I guess 640X480 resolution clocks the pixel information at 25Mhz. and for something like 1024X768 it is far more than that, causing the buffer IC to drop some pulses and to cause the issue you mentioned.You will have to set the resolution to minimum and see.- Shashank
--To unsubscribe from this group and stop receiving emails from it, send an email to cubieboard+...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "Cubieboard" group.