dvi signal error

Hi,

I get an error message on my monitor that there is a signal error. I
would expect the orange screen. It worked once, than I moved my work
place several times.

Trying to find the problem, I discovered that I accidentely powered
the board with 6V. I suspect that I damaged the DVI interface with
that.

Angstrom boots ok, so the processor seems to be fine.

calling printenv I get:

Environment size: 1189/131068 bytes
OMAP3 beagleboard.org # printenv
bootdelay=10
baudrate=115200
loadaddr=0x82000000
console=ttyS2,115200n8
vram=12M
dvimode=1024x768MR-16@60
defaultdisplay=dvi
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
nandroot=/dev/mtdblock4 rw
nandrootfstype=jffs2
mmcargs=setenv bootargs console=${console} vram=${vram}
omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${default}
nandargs=setenv bootargs console=${console} vram=${vram}
omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaul}
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run nandargs; nand read $
{loadaddr} 280000 400000; bootm ${loadaddr}
dieid#=66fa000400000000040365fa1701701d
bootcmd=mmc init;fatload mmc 0 80300000 uImage;bootm 80300000
bootargs=console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rw
rootfstype=ext3 rootwait omapfb.video_mode=1024x768MR-240
stdin=serial
stdout=serial
stderr=serial

Any ideea what could be the reason, why i get the signal error?

thanks,
Willy

If you plugged in a 6V supply, there could be several things wrong. I suggest you go back and try the verification SW that is used at the factory. That will remove any question as to whether it is a SW or HW issue

http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidation

Gerald

hi,

I copied the MLO and u-boot.bin from the C4 link (
http://www.angstrom-distribution.org/demo/beagleboard/ ) and the rest
of the files for the C3 hw ( linked files at
http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidation ).

Although I have the boot.scr on the mmc and pressed the user button
during power-up (5V not USB), it seems that the reading of boot.scr is
skiped and the uImage is read directly.
This is already one think that does not work as described on beagle
board validation page.
Further the uImage is loaded..

X-Loader 1.41
Starting on with MMC
Reading boot sector

188600 Bytes Read from MMC
Starting OS Bootloader from MMC...

U-Boot 2009.11-rc1 (Jan 08 2010 - 21:19:52)

OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Board revision C4
Die ID #66fa000400000000040365fa1701701d
Hit any key to stop autoboot: 0
mmc1 is available
reading uImage

2578044 bytes read
## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.28-omap1
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2577980 Bytes = 2.5 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

but it stucks at some point after recognzing the usb mouse attached on
the usb hub.
When using the uImage for the C4 hw, the startup phase comes further
but stucks when it tries to mount the root fs (probably expecting a
2nd partition on mmc).

any ideea? :slight_smile:

Willy