DM355EVM X windows apps

What version of DVSDK are you using? When I have run startx in the past it opens the full x windows environment properly, you can see a terminal window open but you can also open additional applications as well from what I recall, though I did not go much further with it. When you say you see a console display is this just the text or a window of the terminal console, and can you see the mouse on the screen and move it with a USB mouse?

I have not tried running xlogo, but this is something I can test tomorrow.

Hi Bernie, thanks for getting back to me. Here's my setup:
 
We are using a  loaner  TI / Infinity OC package that comes with 4 CD's, called TMS320DM355 Digital Evaluation Module.
 
 Tool chain: MontaVista 3.4.3-25.0.104.0600975 2006-07-06
 mvl_pro_4_0_1_demo_ lsp_setuplinux_ 01_20_00_14.bin
 dvsdk_1_30_01_41
 I unpacked the root target from mvl_pro_4_0_1_demo_ target_setuplinux.bin which doesn't have a version

I tried startx& both running loadmodules.sh first and then not running it with the same results. It comes up initially in green then after 10 secs a blue  icewm graphic X display with a toolbar at the bottom which looks normal . Starting in the upper left corner and extending about 3/4 across and down the screen I see a white "terminal" window which displays a few lines of  text outputed from the serial port console before
issuing startx.  There is a text cursor displayed at the end of the directory prompt and also  mouse cursor about the middle of the screen. Invoking xlogo I get the error:

root@10.1.2.51:/opt/dvsdk/dm355# xlogo
Error: Can't open display: davincifb.vid0

 I tried other X apps in the /usr/X11R6/bin dir with the same results.
Is DISPLAY=davincifb.vid0 the proper evn var for this ?

Here's a  partial ps -ax list after invoking startx&

 1027 ?        Ssl    0:00 /usr/bin/mvltd -p 34577 -b /usr/lib/mvltd -M 5
 1053 ?        S<s    0:00 udevd
 1448 ?        Ss     0:00 xdm
 1454 ?        Ss     0:00 -bash
 1596 ?        S      0:00 /bin/sh /usr/bin/X11/startx
 1607 ?        S      0:00 xinit /usr/X11R6/lib/X11/xinit/xinitrc --
 1608 ?        S<     0:15 X :0
 1652 ?        S      0:02 icewm

 John

Bernie,

 After about 10 mins the screen goes green with the following partial ps -ax listing :

 1448 ?        Ss     0:00 xdm
 1454 ?        Ss     0:00 -bash
 1596 ?        S      0:00 /bin/sh /usr/bin/X11/startx
 1607 ?        S      0:00 xinit /usr/X11R6/lib/X11/xinit/xinitrc --
 1608 ?        S<     0:19 X :0
 1652 ?        S      0:07 icewm

When I bring startx& to the foreground and kill it with control-C  I get:

root@10.1.2.51:/usr# fg
startx
<Control-C>
waiting for X server to shut down

xinit:  unexpected signal 2.
Couldnt get a file descriptor referring to the console

I get the same response if I do this before the screen goes green.

At  this point I can startx& again and repeat the behavior.

 I also tried running jpegdec out /dev/fb/0 with the sample 480x720 jpeg file. The jpeg image comes out grainy on my VGA display.

After I run X& it clears up for about 15 secs then goes grainy again. After about 10 mins the image

comes out clear with X still running !

John

I think the issue regarding it breaking after 10 minutes is due to an issue discussed in this thread here, so you should be able to work around that with 'setterm -blank 0 > /dev/vc/0'.

As to the running of actual X applications, I think the problem is that you have to run the applications from the terminal within X as opposed to the UART serial terminal, that this requires you to have a USB keyboard and optionally a USB mouse (note you can only use one or the other at any given time due to a USB endpoints limitation, so it is kind of ackward to do this sort of thing by switching between keyboard and mouse). Below is a screen shot of output from my DM355 EVM running both xlogo and xclock.

 I get the same error/warning you do about a file descriptor for the console when I halt x, so I don't think it is related.

One can use both USB Keyboard and USB mouse simultaneously provided these devices are simple devices, meaning they do not support extra functionalities such as Audio streaming controls, Volume controls etc.

Bernie, I can start xclock now when I place it in xinitrc. Before I was trying to run it from the serial

console, as you mentioned. I also disabled the frame buffer console in the

kernel and added "setterm -blank 0 > /dev/vc/0"  to  xinitrc, but the screen goes green after about 10 mins.

I have to kill startx and when I restart it, it goes green after 10 mins again

 If I want to start apps at boot, what script in /etc should I place them in. I was looking in there but couldn't find

any rc.local type boot scripts

 Thanks fro the help,

 John

swami, we don't plan on using any X input devices, just running a graphic app that paints the screen.

 Thanks,

 John

Further testing shows that running "setterm -blank 0 > /dev/vc/0" from the serial console has no effect on my X video going green after 10 mins.I tried "setterm -blank 1 > /dev/vc/0"  to see if it would blank in 1 min, but the X windows video still went green in 10 mins. I can see the various /dev/vc/* devices via ls. I tried defaulting the kernel using the "make davinci_dm355_evm_defconfig,  and disabled CONFIG_FRAMEBUFFER_CONSOLE and various other combos to no avail :(

 John