Hi all,
I hvae both a beagle board and a TI OMAP 35xEVM board,
first I was able to run the Angstrom x11 demo image on the beagle
board with DVI outout on my LCD monitor,
then I installed the same image on my OMAP35x EVM, the Angstrom image
booted up on the EVM board and displayed a terminal on serial comm
windows, I was able to log in as root and access the thow system,
but there''s no output from the DVI on EMV to my LCD monitor anymore.
I think maybe that's beacuse there is a touchscreen LCD on the EVM
board already and something messed up.
does anybody know what could go wrong with my DVI and how to get
display from DVI on LCD monitor?
Thanks!
These boards have similar, yet different designs. There is an enable pin for the DVI output that needs to be set on the EVM. It is different than Beagle. On the EVM it is GPIO.7 off of the TWL4030. On the Beagle is is GPIO_150 off of the OMAP3530.
I am hoping that you are using uImage built for EVM from Angstrom.
On older EVMs, there was an issue with R18 (Near DVI port) not populated with correct resistance value. Just cross check R18 ~ 510 ohm.
I am able to use DVI on EVM with attached patches, copy to openembedded\packages\linux\linux-omap-pm\omap3evm folder and modify openembedded\packages\linux\linux-omap-pm_git.bb to add these 2 patches to SRC_URI_append_omap3evm
SRC_URI_append_omap3evm = " \
file://evm-mcspi-ts.diff;patch=1 \
file://DSS2_fifo_threshold.patch;patch=1 \
file://omap3evm_fix_dviout_color_issues.patch;patch=1 \
"
This should give you DVI output - but one catch is that DSI PLL is not used to generate pixel clock. I was getting DSI PLL lock failure with that setting. This can be done - but I did not spend much time to debug that as I needed a quick way to get DVI out on EVM.
Thanks for your reply.
I think my evm board is not one of the older ones.
I can get DVI output with EVM SDK1.0.2 on my LCD monitor.
so it looks I dont need these patches.
but do you know how I can get Angstrom for EVM?
Can I download it from somewhere or I have to use open embeded to make
one?
I searched on the web but did not find one such image.
Thank a lot. I have used the online build tool nad build a angstrom
image for EVM, I got a tar file after the build is finished,
what do I do with the tar file?
Shouldn't I expect to get an uimage file and a file system tar.bz
file?
Thanks!
Hi Pratheesh
I tried to use the Angstrom dist I got fromthe online image builder
nad still no luck.
here is what I did:
1. made a image for omap evm using the online image builder
2. formatted the SD card 2 partitions, copied MLO and u-boot.bin I got
from Angstrom demo image for beagleboard to the first partition.
3. tar the image.tar.bz to SD card;s second ext3 partion
4. copy uImage-2.6.28-omap1 to SD's first partition, renamed it to
uImage
5. inster the card to EMV board, powered up the board.
here is the output that shows version of Xloader and uboot
Texas Instruments X-Loader 1.4.2 (Aug 8 2008 - 16:59:05)
Reading boot sector
Booting from mmc
I guess nothing wrong with the setup, it seems you are using UART3 for console - on EVM, UART1 is default console. Connect the serial cable to UART1 and change bootargs to ttyS0, this should give you angstrom shell prompt and kernel startup messages.
By default, EVM display will be LCD, it does not work for you now because 1024x768MR-16@60 is not a valid mode for LCD. Just drop omapfb.videomode from bootargs , you should see GUI on LCD.
To get the output on DVI, try adding omap-dss.def_disp on bootargs. I am not sure this is valid for the latest DSS2, please refer to the DSS2 documentation - but you need to specify DVI output explicitly in bootargs or need to change runtime following a sequence of commands (bootargs is simpler)
thanks for your help as always.
It seems the console=ttyS2 is not a problem here, I sued x-loader and
uboot for beagle board, I found this xloader(1.4.2 (Aug 8 2008 -
16:59:05) ) will use UART3 instaed of UART1/2,
so I just connected serial cable on UART3 and I was able to boot into
angstrom image for Beagle board on EVM with UART3 before.
the problem seems still to be the kernel.
I changed the bootargs to " setenv bootargs console=ttyS2,115200n8
console=tty0 root
=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
omapfb.video_mode=640x480MR-16@60 "
the booting still stoped at " Starting kernel ..."
actually I also tried to git clone the latest u-boot your provided in
this post and compiled u-boot with omap3_evm_configuration
I copied this new u-boot.bin to sd card and powered up the evm,
this time I only got three lines of message, something like " checking
sector, loading mmc" then the boot stoped without even showing the u-
boot prompt.
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
On Behalf Of lwpcse
Sent: Tuesday, April 14, 2009 12:06 AM
To: Beagle Board
Subject: [beagleboard] Re: no DVI output from OMAP 35X EVM runnig beagle
board Angstrom x11 demo image
thanks for your help as always.
It seems the console=ttyS2 is not a problem here, I sued x-loader and
uboot for beagle board, I found this xloader(1.4.2 (Aug 8 2008 -
16:59:05) ) will use UART3 instaed of UART1/2,
so I just connected serial cable on UART3 and I was able to boot into
angstrom image for Beagle board on EVM with UART3 before.
It is a problem here. x-loader, u-boot and uImage for beagleboard, all configured to output at UART3 as well as serial console initialization scripts in beagleboard-demo-image.
When you use x-loader and u-boot from beagleboard, above behaviour won't change but omap3evm kernel still tries to output at UART1 and omap3evm-demo-image which you built using online-image-builder configures UART1 as application console.
So please check connecting UART1 to PC serial port instead of UART3.
the problem seems still to be the kernel.
I changed the bootargs to " setenv bootargs console=ttyS2,115200n8
console=tty0 root
=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
omapfb.video_mode=640x480MR-16@60 "
the booting still stoped at " Starting kernel ..."
actually I also tried to git clone the latest u-boot your provided in
this post and compiled u-boot with omap3_evm_configuration
I copied this new u-boot.bin to sd card and powered up the evm,
this time I only got three lines of message, something like " checking
sector, loading mmc" then the boot stoped without even showing the u-
boot prompt.
I connected back to UART 1 after "Starting Kernel..." displayed on
UART3, but there is nothing coming out of UART1.
As for the new uboot I compiled, I copied it to SD card, powered up
EVM, did not see uboot prompt at UART1.
I only get these on UART3 after I powered up EVM:
Texas Instruments X-Loader 1.4.2 (Aug 8 2008 - 16:59:05)
Reading boot sector
Booting from mmc
Then I switched to UART1, there 's no output AT UART3.