TI E2E Community
BeagleBone DVI-D cape none syncing display
I received my DVI-D cape (s/n: 1412DVID375) as goes with my Beaglebone (Rev A5. S/N: 0812BB000176) last week (purchased through Farnell).
Next I moved to your latest Android release (ICS 4.0.3 with devkit 3.0.1) as available from: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_ICS_4_0_3_DevKit_3_0_1/index_FDS.html
To get me quickly up (just to see if all is OK) I downloaded the pre-built Android images for the above configuration (which tells me that DVI-D is supported on Beaglebone.
Booting the device goes OK, and I also see the DVI init messages coming by (see below):
My problem / issue as of now is, I tried with various LCD monitors (also different HDMI-DVI cables), but none of them seems to be working fine. It is the fact that the "Android" boot animation screen is displayed in a flickering way with strike through's in text (~1sec "ANDROID" next few seconds black screen). In the end, I get a black screens where only one monitor is capable to display some part of the Android desktop (initial screen) and even then, only in a flickering way. More in detail, this one monitor gives me a screen which is only now and then visible (tens of seconds black screen, next 1-3 seconds I see the Android desktop :-(
An other related observation I did, when I do not connect any (mouse / keyboard) USB device, I even do not get any Android screen ad all (only the "Android" boot animation screen popping now and then up).
When testing with the pre-built Linux kernel only (so not Android), I get the blue Angstrom login screen (http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_DVI-D) etc as it should be via the DVI interface !!
Please, advice. I was wondering, how to change the video mode, or what else could I do?
Btw., I'm located in the Netherlands (50HZ).
127|root@android:/ # dmesg<5>[ 0.000000] Linux version 3.2.0-gb02ab39 (x0029463@psplinux052) (gcc version 4.4.3 (GCC) ) #1 Wed Apr 11 14:03:37 IST 2012<4>[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d<4>[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache<4>[ 0.000000] Machine: am335xevm<4>[ 0.000000] Memory policy: ECC disabled, Data cache writeback<7>[ 0.000000] On node 0 totalpages: 65536<7>[ 0.000000] free_area_init_node: node 0, pgdat c06f36ec, node_mem_map c0824000<7>[ 0.000000] Normal zone: 512 pages used for memmap<7>[ 0.000000] Normal zone: 0 pages reserved<7>[ 0.000000] Normal zone: 65024 pages, LIFO batch:15<6>[ 0.000000] AM335X ES1.0 (sgx neon )<7>[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768<7>[ 0.000000] pcpu-alloc:  0<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024<5>[ 0.000000] Kernel command line: console=ttyO0,115200n8 androidboot.console=ttyO0 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait init=/init ip=off<6>[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)...<4>[ 0.907501] i2c-core: driver [tsl2550] using legacy suspend method<4>[ 0.913970] i2c-core: driver [tsl2550] using legacy resume method<6>[ 0.920379] at24 1-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write<6>[ 1.001220] No daughter card found on AM335x EVM<6>[ 1.006072] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write<6>[ 1.021270] Board name: A335BONE<6>[ 1.024658] Board version: 00A5<6>[ 1.027923] The board is a AM335x Beaglebone.<6>[ 1.033111] tps65217 1-0024: TPS65217 ID 0x7 version 1.0<6>[ 1.040466] print_constraints: DCDC1: 900 <--> 1800 mV at 1800 mV<6>[ 1.048767] print_constraints: DCDC2: 900 <--> 3300 mV at 1275 mV<6>[ 1.057098] print_constraints: DCDC3: 900 <--> 1500 mV at 1100 mV<6>[ 1.065307] print_constraints: LDO1: 1000 <--> 3300 mV at 1800 mV<6>[ 1.073608] print_constraints: LDO2: 900 <--> 3300 mV at 3300 mV<6>[ 1.081787] print_constraints: LDO3: 1800 <--> 3300 mV at 3300 mV<6>[ 1.090026] print_constraints: LDO4: 1800 <--> 3300 mV at 3300 mV<4>[ 1.096893] omap_hsmmc.0: alias fck already exists<4>[ 1.102233] omap_i2c.3: alias fck already exists<6>[ 1.121307] omap_i2c omap_i2c.3: bus 3 rev2.4.0 at 100 kHz<6>[ 1.127624] at24 3-0054: 32768 byte 24c256 EEPROM, writable, 64 bytes/write<6>[ 1.134918] IN : bone_setup_daughter_board<6>[ 1.139373] usb 1-1: new high-speed USB device number 2 using musb-hdrc<6>[ 1.154388] Detected a daughter card on BeagleBone..<6>[ 1.159393] IN : dvi_init<4>[ 1.162780] da8xx_lcdc.0: alias fck already exists<6>[ 1.168090] da8xx_lcdc da8xx_lcdc.0: GLCD: Found 1024x768@60 panel<6>[ 1.186553] Setup DVI display<3>[ 1.190704] mtdoops: mtd device (mtddev=name/number) must be supplied<6>[ 1.197631] omap2-nand driver initializing<6>[ 1.201995] OneNAND driver initializing<6>[ 1.206481] CAN device driver interface...
1. Could you validate display with VNC viewer ? This is to eliminate problem with android
2. Also send us logcat for further analysis
Kindly click the verify answer button on this post if it answer your question.
Now it’s getting interesting. When launching VNC server on the Bone, I also get now and then (more often and more reproducible) the Android desktop to see on my DVI connected monitor (see included pictures = Beaglebone-setup.jpg + visible-desktop.jpg + none-visible-desktop.jpg Note, the Philips monitor / right hand is connected to the Beaglebone via DVI, where the left hand / Dell monitor is my TightVNC viewer). And when I see something :-) it looks bad (these lines in the image = flickering-lines.jpg) :-(
Regarding the logcat, see attached the full log’s I did (logcat + dumpstate, etc).
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.