Zoom™ AM3517 eXperimenter Kit install VNC

Hi,

I believe the Arago feeds have been removed some time ago since they hadn't been updated. Check this post out.

Maybe you can use the Angstrom base feed instead: feeds.angstrom-distribution.org

http://www.angstrom-distribution.org/repo/?section=base

Check this forum topic: http://e2e.ti.com/support/arm/sitara_arm/f/791/p/266848/934991.aspx#934991 where I have pointed out how to add a package feed source to your opkg configuration.

Best regards,
Miroslav

it doesn´t work are any other way???

You can always cross compile it.

Download the x11vnc source code from here: http://www.karlrunge.com/x11vnc/

There is a pretty good explanation on how to cross compile it inside the README file:

   Q-118: How do I cross compile x11vnc for a different architecture than
   my Linux i386 or amd64 PC?

   You will need a cross-compiling toolchain. Perhaps your distro
   provides these or you can find a HOWTO for your distro. We found a
   nice one at qtmoko.org for building armel binaries on Debian Linux
   i386 machines. It includes most of the libraries that x11vnc needs. We
   use that example here.

   We ran this script to set PATH, configure, and build:
#!/bin/sh

# toolchain from: qtmoko-debian-toolchain-armv4t-eabi.tar.gz

export PATH=/opt/toolchains/arm920t-eabi/bin:$PATH

env CC=arm-linux-gcc ./configure --host=arm-linux --without-avahi

make

arm-linux-strip ./x11vnc/x11vnc
ls -l ./x11vnc/x11vnc

   Note we had to include --without-avahi due to lack of
   libavahi-client.so.3 supplied by the toolchain we used. One would need
   to add it if it was desired on the target machine. We also stripped
   the binary to make it smaller.

   For an embedded system one may also want to add --without-x if the
   embedded system does not use X11 and the -rawfb mechanism must be
   used.

Of course you need to specify the gcc cross compiler path and name from the SDK you are using.

Best regards,
Miroslav

Hello Miroslav and everybody

I use ti-sdk-am335x-evm-06.00.00.00 and I have cross compiled x11vnc-0.9.13 so:

source ../ti-sdk-am335x-evm-06.00.00.00/linux-devkit/environment-setup

./configure --host=arm-linux-gnueabihf --without-avahi --without-x --without-filetransfer --without-crypt --without-crypto --without-ssl 

make

I can run x11vnc on AM3358 but I does not find X buffer and it does not work:

root@am335x-evm:~/vnc# ./x11vnc 
###############################################################
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@                                                           @#
#@  **  WARNING  **  WARNING  **  WARNING  **  WARNING  **   @#
#@                                                           @#
#@        YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!!        @#
#@                                                           @#
#@  This means anyone with network access to this computer   @#
#@  may be able to view and control your desktop.            @#
#@                                                           @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@                                                           @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@                                                           @#
#@  You can create an x11vnc password file by running:       @#
#@                                                           @#
#@       x11vnc -storepasswd password /path/to/passfile      @#
#@  or   x11vnc -storepasswd /path/to/passfile               @#
#@  or   x11vnc -storepasswd                                 @#
#@                                                           @#
#@  (the last one will use ~/.vnc/passwd)                    @#
#@                                                           @#
#@  and then starting x11vnc via:                            @#
#@                                                           @#
#@      x11vnc -rfbauth /path/to/passfile                    @#
#@                                                           @#
#@  an existing ~/.vnc/passwd file from another VNC          @#
#@  application will work fine too.                          @#
#@                                                           @#
#@  You can also use the -passwdfile or -passwd options.     @#
#@  (note -passwd is unsafe if local users are not trusted)  @#
#@                                                           @#
#@  Make sure any -rfbauth and -passwdfile password files    @#
#@  cannot be read by untrusted users.                       @#
#@                                                           @#
#@  Use x11vnc -usepw to automatically use your              @#
#@  ~/.vnc/passwd or ~/.vnc/passwdfile password files.       @#
#@  (and prompt you to create ~/.vnc/passwd if neither       @#
#@  file exists.)  Under -usepw, x11vnc will exit if it      @#
#@  cannot find a password to use.                           @#
#@                                                           @#
#@                                                           @#
#@  Even with a password, the subsequent VNC traffic is      @#
#@  sent in the clear.  Consider tunnelling via ssh(1):      @#
#@                                                           @#
#@    http://www.karlrunge.com/x11vnc/#tunnelling            @#
#@                                                           @#
#@  Or using the x11vnc SSL options: -ssl and -stunnel       @#
#@                                                           @#
#@  Please Read the documention for more info about          @#
#@  passwords, security, and encryption.                     @#
#@                                                           @#
#@    http://www.karlrunge.com/x11vnc/faq.html#faq-passwd    @#
#@                                                           @#
#@  To disable this warning use the -nopw option, or put     @#
#@  'nopw' on a line in your ~/.x11vncrc file.               @#
#@                                                           @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
###############################################################
28/06/2013 15:28:05 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 1664
28/06/2013 15:28:05 This x11vnc was built without X11 support (-rawfb only).
28/06/2013 15:28:05 
28/06/2013 15:28:05 *** XOpenDisplay failed. No -display or DISPLAY.
28/06/2013 15:28:05 *** Trying ":0" in 4 seconds.  Press Ctrl-C to abort.
28/06/2013 15:28:05 *** 1 2 3 4 
28/06/2013 15:28:09 This x11vnc was built without X11 support (-rawfb only).
28/06/2013 15:28:09 

28/06/2013 15:28:09 ***************************************
28/06/2013 15:28:09 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

Some tips and guidelines:

** An X server (the one you wish to view) must be running before x11vnc is
   started: x11vnc does not start the X server.  (however, see the -create
   option if that is what you really want).

** You must use -display <disp>, -OR- set and export your $DISPLAY
   environment variable to refer to the display of the desired X server.
 - Usually the display is simply ":0" (in fact x11vnc uses this if you forget
   to specify it), but in some multi-user situations it could be ":1", ":2",
   or even ":137".  Ask your administrator or a guru if you are having
   difficulty determining what your X DISPLAY is.

** Next, you need to have sufficient permissions (Xauthority) 
   to connect to the X DISPLAY.   Here are some Tips:

 - Often, you just need to run x11vnc as the user logged into the X session.
   So make sure to be that user when you type x11vnc.
 - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
   file may be accessed.  The cookie file contains the secret key that
   allows x11vnc to connect to the desired X DISPLAY.
 - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
   by the -auth option, e.g.:
       x11vnc -auth /home/someuser/.Xauthority -display :0
       x11vnc -auth /tmp/.gdmzndVlR -display :0
   you must have read permission for the auth file.
   See also '-auth guess' and '-findauth' discussed below.

** If NO ONE is logged into an X session yet, but there is a greeter login
   program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
   to find and use the raw display manager MIT-MAGIC-COOKIE file.
   Some examples for various display managers:

     gdm:     -auth /var/gdm/:0.Xauth
              -auth /var/lib/gdm/:0.Xauth
     kdm:     -auth /var/lib/kdm/A:0-crWk72
              -auth /var/run/xauth/A:0-crWk72
     xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
     dtlogin: -auth /var/dt/A:0-UgaaXa

   Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.

   Starting with x11vnc 0.9.9 you can have it try to guess by using:

              -auth guess

   (see also the x11vnc -findauth option.)

   Only root will have read permission for the file, and so x11vnc must be run
   as root (or copy it).  The random characters in the filenames will of course
   change and the directory the cookie file resides in is system dependent.

See also: http://www.karlrunge.com/x11vnc/faq.html

When I remove "--without-x" option it does not compile:

==========================================================================
*** A working X window system build environment is required to build ***
x11vnc.  Make sure any required X development packages are installed.
If they are installed in non-standard locations, one can use the
--x-includes=DIR and --x-libraries=DIR configure options or set the
CPPFLAGS and LDFLAGS environment variables to indicate where the X
window system header files and libraries may be found.  On 64+32 bit
machines you may need to point to lib64 or lib32 directories to pick up
the correct word size.

If you want to build x11vnc without X support (e.g. for -rawfb use only
or for native Mac OS X), specify the --without-x configure option.
==========================================================================

How can I get VNC working in AM335x EVM?

And what command do you use to run the VNC server?

Best regards,
Miroslav

I have tried:

root@am335x-evm:~/vnc# ./x11vnc

root@am335x-evm:~/vnc# ./x11vnc -display :0

root@am335x-evm:~/vnc# ./x11vnc -display /dev/fb0

root@am335x-evm:~/vnc# ./x11vnc -display /dev/fb

I execute it by hand from uart0 terminal.

Does ti-sdk-am335x-evm-06.00.00.00 include X11?. Maybe x11vnc is not the best vnc server or whatever software that allows me to control AM335x EVM with a broken touchscreen from my computer .

Best regards

Have you compiled and installed the Graphics SDK with X11 support?

http://processors.wiki.ti.com/index.php/Graphics_SDK_Quick_installation_and_user_guide#AM335x_Execution_instructions

Best regards,
Miroslav

No, I haven't, I use the root filesystem /home/sitara/ti-sdk-am335x-evm-06.00.00.00/targetNFS, maybe it is already installed.

lsmod returns 0 modules, so I think it is not installed.

My custom Qt aplication runs fine, should I install Graphics SDK for vnc?, is there any other simmilar software? (remote control)

Best regards

I think it is included in the larger root file system, but it's pre-compiled with SUPPORT_XORG=0, so you will need to follow the instructions here and compile it with Xorg support, then install it into your targetfs.

Best regards,
Miroslav

P.S. Please check this post by Josh Elliott: http://e2e.ti.com/support/arm/sitara_arm/f/791/p/314332/1094502.aspx#1094502