This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

help regarding using VNC server on beagleboard-xm

Hi,

I have ported android gingerbread on beagleboard-xm.  I want to use  vnc server on beagleboard-xm.

I think usb over ethernet is enabled on this gingerbread image  that is i am using, because when i type command through minicom it shows usb0 instead of eth0.

I have following doubts :

1. How to configure ethernet over usb  ?

2. in my college there are proxy settings for internet with username and password, so how to configure net ?

3. Which cable should i use usb-mini-A  or usb-mini-B ?

4. is there direct vncserver application or i have to cross compile it ? Please provide me links for vncserver .

  • Hi,

    #1.

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_UserGuide#adb_over_USB_Ethernet_.28Ethernet_over_USB.29

    #2.

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_UserGuide#Browser_Configuration

    3. USB mini-B

    4.  For VNC server do the following

               $ cd <android source path>/external 

               $ git lone git://gitorious.org/rowboat/droid-vnc-server.git

               $ cd droid-vnc-server/jni

               $ source <android source path>/build/envsetup.sh

              $ mm TARGET_PRODUCT=beagleboard

    This sould generate a android vnc server executable (androidvncserver) which will be used to run on board.

    Regards,

    Pankaj Bharadiya

     

  • Thanks Pankaj for your reply.

    i have following doubts :

    1. as you said for VNC server :

     $ cd <android source path>/external

    in this  what is <android source path> ? which packages i have to download ?

    2. I have downloaded compiled binary for vnc server from following link :

    http://code.google.com/p/android-vnc-server/downloads/list

    but when i run this on the beagleboard it gives following error :

    Initializing framebuffer device /dev/graphics/fb0...                                                                                                                     
    xres=640, yres=480, xresv=640, yresv=2880, xoffs=0, yoffs=1920, bpp=32                                                                                                   
    Initializing keyboard device /dev/input/event3 ...                                                                                                                       
    cannot open kbd device /dev/input/event3

    3. I want to use ethernet  over usb then i have to use USB mini-B cable.  If i use mini-B cable then will it supply power to the board   or i need to use external power supply ?

    In which application we need USB mini-A cable ?

    4. This is not related  to  VNC server. I want to use Beagleboard as video streaming server. will you please provide some info about this ?

    thanks in advance...

    regards,

    sachin kharude.


  • Hi Sachin,

    Ref #1.  Android source path is a path which points to android source directory.

    You should download and compile Android sources before building Android VNC server.

    Please refer to below wiki for more details about getting and compiling source code.

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_DeveloperGuide#Source_locations

    Ref #2.

    Connect keyboard and mouse to your board and try running your VNC server binary.

  • thanks again for your quick reply.

    Ref #2.

    I did as you said Connected keyboard and mouse to board and tried running  VNC server binary. it gives following error now.

    Initializing framebuffer device /dev/graphics/fb0...                                                                                                                    
    xres=640, yres=480, xresv=640, yresv=2880, xoffs=0, yoffs=1920, bpp=32                                                                                                  
    Initializing keyboard device /dev/input/event3 ...                                                                                                                      
    Initializing touch device /dev/input/event1 ...                                                                                                                         
    cannot get ABS_X info, Invalid argument     

  • Hi,

    Please try with attached Android vnc server binary.

    Rename androidvncserver.txt to androidvncserver,  set executable permission and try.

    8233.androidvncserver.txt

    Regards,

    Pankaj Bharadiya

  • Hi,

       Thank you very much pankaj the androidvnceserver you provided is working. but the problem is on the screen it is only showing green android robot and it hangs there.

     for this problem i followed your solution on the following link : http://groups.google.com/group/rowboat/browse_thread/thread/5bb21fec8ec19743/ea10d03c16eac453?pli=1

    to change the bootargs I used setenv and saveenv command in uboot but it is not working. then i realised that i have to edit boot.scr file. then using nano command in terminal i did edit boot.scr. then i copied that boot.scr to memory card then tried to boot Beagleboardxm but it's not working.

    i got following error on terminal

    Texas Instruments X-Loader 1.51 (Jul 11 2011 - 21:11:32)                                         
    Unsupported Chip!                                                            
    Beagle xM Rev C                                                              
    Starting X-loader on MMC                
    Reading boot sector                     
                                            
    213256 Bytes Read from MMC              
    Starting OS Bootloader from MMC...      
    Starting OS Bootloader...               


    U-Boot 2010.06 (Jul 08 2011 - 04:37:45)

    OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz
    OMAP3 Beagle board + LPDDR/NAND
    I2C:   ready
    DRAM:  384 MiB
    NAND:  HW ECC [Kernel/FS layout] selected
    0 MiB
    *** Warning - bad CRC or NAND, using default environment

    In:    serial
    Out:   serial
    Err:   serial
    Beagle xM Rev A/C
    ie ID #763e00029ff80000016830101700a022
    Hit any key to stop autoboot:  0
    mmc1 is available                                                                                                                                                       
    reading boot.scr                                                                                                                                                        
    C535 bytes read                                                                                                                                                         
    Running bootscript from mmc ...                                                                                                                                         
    ## Executing script at 82000000                                                                                                                                         
    Bad data crc                                                                                                                                                            
    OMAP3 beagleboard.org #

    after this i used bootd  it gives following error

    mmc1 is available                                                                                                                                                       
    reading boot.scr                                                                                                                                                        
                                                                                                                                                                            
    535 bytes read                                                                                                                                                          
    Running bootscript from mmc ...                                                                                                                                         
    ## Executing script at 82000000                                                                                                                                         
    Bad data crc       

    then i used bootm command     it gives following error

    OMAP3 beagleboard.org # bootm                                                                                                                                           
    ## Booting kernel from Legacy Image at 82000000 ...                                                                                                                     
       Image Name:   Execute uImage.bin                                                                                                                                     
       Image Type:   ARM Linux Script (uncompressed)                                                                                                                        
       Data Size:    396 Bytes = 396 Bytes                                                                                                                                  
       Load Address: 00000000                                                                                                                                               
       Entry Point:  00000000                                                                                                                                               
       Contents:                                                                                                                                                            
          Image 0: 388 Bytes = 388 Bytes                                                                                                                                    
       Verifying Checksum ... Bad Data CRC                                                                                                                                  
    ERROR: can't get kernel image!

    will you please help me with this ?

    thanks again for your help...

    regards,

    sachin kharude





  • Editing boot.scr will not work. You need to use the mkbootscr utility to generate the new boot.scr.

    This is available in the DevKit Download page in the Tools package. Do refer to the README file for instructions.
    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_4_DevKit_2_1/index_FDS.html

  • Thank you very much.... Vishveshwar Bhat

    everything is working fine now.

    regards,

    sachin kharude

  • Hi Team,

    am getting blank screen on PC , i on ICS 4.0.3 is it any update for ICS

    Regards