• State
  • Locked Locked
  • Replies 40 replies
  • Subscribers 100 subscribers
  • Views 4469 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM3517 EVM Display parameters

T B
Intellectual 370 points
Other Parts Discussed in Thread: AM3517

I did few changes to uboot so now I cannot run the already installed kernel from the nand but now I use the TFTP to reboot and take the kernel from there.

 

but in this case display does not allow me to run some graphics demo application which were running previously on the board. I fear that I might have changed the display parameters at some point and I don't have the default uboot enviournment settings with me.

 

So how can I change the display parameters for this kit. It has 480x272 WQVGA lcd display on it. 

which setenv command can I give to set its parameter? do you have the default display parameter settings so that I can refer to it?

 

  • 0
    TI__Expert 8180 points

    Hi,

    The information is completely partial, please provide more details like,

    U-boot changes you are talking about?

    U-Boot and kernel version you are using?

    Elaborate more on  "some of the applications are failing"? which are these applications?

    Thanks,

    Vaibhav

  • 0
    TI__Expert 8180 points

    Hi,

    The information is really partial, I could not able to get anything out of it.  Please provide more details like,

    U-boot changes you are talking about?

    U-Boot and kernel version you are using?

    Elaborate more on  "some of the applications are failing"? which are these applications?

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    Thanks.

    I will put details and paste the my errors ASAP in the mean time can you tell me what are the default LCD display parameter settings for this AM3517 EVM kit. What are the commands to set it or How can we set them from the uboot environment? I would like to see the output on LCD display of the kit.

  • 0 in reply to T B
    Intellectual 370 points

    I am booting using TFTP. Normally after booting we get the demo program on the screen (showing colourfull cube).   But now after booting it gives following error.

    omap3517-evm login: Profiling enabled
                                         Demo started.
                                                      Capture device: /dev/video3
                                                                                 display[0] w: 480, h: 272
                                                                                                          'eglCreateWindowSurface': egl error 'EGL_NOT_INITIALIZED' (0x3001)
                                                                                                                                                                          ;   init tex stream failed
                 Error: Failed to create display device
                                                       display thread exits

                                                                           main thread exits

    root@omap3517-evm:/opt# ./bccube
    Demo started.
    display[0] w: 480, h: 272
    Capture device: /dev/video3
    'eglCreateWindowSurface': egl error 'EGL_NOT_INITIALIZED' (0x3001)
    init tex stream failed
    Error: Failed to create display device
    display thread exits

    main thread exits

    root@omap3517-evm:/opt#

  • 0 in reply to T B
    TI__Expert 8180 points

    Hi TB,

    Are you using TI release package? If yes, then please refer to the UserGuide available with release package for all possible boot argument options. Also please refer to the link below

    http://wiki.davincidsp.com/index.php/UserGuideDisplayDrivers_PSP_03.00.00.05#Command_Line_arguments

    NOTE: Please note that, above link is with reference to TI release PSP03.00.00.05 based on 2.6.32 kernel version.

     

    Thanks,

    Vaibhav

  • 0 in reply to T B
    Intellectual 370 points

     

    i tried following commands to set the size

     

    OMAP3517EVM # setenv bootargs mem=256M console=ttyS2, 115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 eth=__:__:__:__:__:__ , rsize=272, wsize=480

    but this does not work.

     

  • 0 in reply to T B
    TI__Expert 8180 points

    TB,

     

    I can't help you unless you provide specific details here, I need to know the kernel version which you are using?

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    oh...ok

    here i have pasted the screenshot.  It shows the Linux version 2.6.31

     

    Texas Instruments X-Loader 1.44 (Oct  1 2009 - 19:12:00)
    Starting OS Bootloader...


    U-Boot 2009.03-dirty (Oct 15 2009 - 11:03:05)

    OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
    OMAP3 omap3517evm board + LPDDR/NAND
    DRAM:  256 MB
    NAND:  512 MiB
    In:    serial
    Out:   serial
    Err:   serial
    Ethernet PHY: GENERIC @ 0x00
    I2C read: I/O error
    HECC U20: port before = 000000FF
    I2C read: I/O error
    I2C read: I/O error
    HECC U20: programmed CAN_STB low
    I2C read: I/O error
    HECC U20: port after = 000000FF
    Die ID #607600000000000001543b210200c009
    Hit any key to stop autoboot:  0
    TFTP from server 172.16.5.239; our IP address is 172.16.6.5
    Filename 'uImage'.
    Load address: 0x80000000
    Loading: #################################################################
             #########################################################T ########
             #T #################################################T ###############
             #################################################################
             #################################################################
             #########################T ###################################T #####
             ########################################T ##########
    done
    Bytes transferred = 2248832 (225080 hex)
    ## Booting kernel from Legacy Image at 80000000 ...
       Image Name:   Linux-2.6.31-rc7-omap1-06331-g75
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2248768 Bytes =  2.1 MB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK

    Starting kernel ...

    Uncompressing Linux............................................................................................................................................. done, bootin    g the kernel.
    Linux version 2.6.31-rc7-omap1-06331-g757f531 (x0029463@psplinux050) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Thu Oct 1 19:29:57 IST 2009
    CPU: ARMv7 Processor [411fc087] revision 7 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
    Machine: OMAP3517 EVM
    Memory policy: ECC disabled, Data cache writeback
    OMAP3517 ES1.0 (full speed SGX, IVA2)
    SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
    Reserving 4194304 bytes SDRAM for VRAM
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
    Kernel command line: mem=256M console=ttyS2,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 eth=00:08:EE:03:77:FC
    PID hash table entries: 1024 (order: 10, 4096 bytes)

     

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    oh...ok

    here i have pasted the screenshot.  It shows the Linux version 2.6.31. Please, let me know if you need any other details.

     

    Texas Instruments X-Loader 1.44 (Oct  1 2009 - 19:12:00)
    Starting OS Bootloader...


    U-Boot 2009.03-dirty (Oct 15 2009 - 11:03:05)

    OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
    OMAP3 omap3517evm board + LPDDR/NAND
    DRAM:  256 MB
    NAND:  512 MiB
    In:    serial
    Out:   serial
    Err:   serial
    Ethernet PHY: GENERIC @ 0x00
    I2C read: I/O error
    HECC U20: port before = 000000FF
    I2C read: I/O error
    I2C read: I/O error
    HECC U20: programmed CAN_STB low
    I2C read: I/O error
    HECC U20: port after = 000000FF
    Die ID #607600000000000001543b210200c009
    Hit any key to stop autoboot:  0
    TFTP from server 172.16.5.239; our IP address is 172.16.6.5
    Filename 'uImage'.
    Load address: 0x80000000
    Loading: #################################################################
             #########################################################T ########
             #T #################################################T ###############
             #################################################################
             #################################################################
             #########################T ###################################T #####
             ########################################T ##########
    done
    Bytes transferred = 2248832 (225080 hex)
    ## Booting kernel from Legacy Image at 80000000 ...
       Image Name:   Linux-2.6.31-rc7-omap1-06331-g75
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2248768 Bytes =  2.1 MB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK

    Starting kernel ...

    Uncompressing Linux............................................................................................................................................. done, bootin    g the kernel.
    Linux version 2.6.31-rc7-omap1-06331-g757f531 (x0029463@psplinux050) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Thu Oct 1 19:29:57 IST 2009
    CPU: ARMv7 Processor [411fc087] revision 7 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
    Machine: OMAP3517 EVM
    Memory policy: ECC disabled, Data cache writeback
    OMAP3517 ES1.0 (full speed SGX, IVA2)
    SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
    Reserving 4194304 bytes SDRAM for VRAM
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
    Kernel command line: mem=256M console=ttyS2,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 eth=00:08:EE:03:77:FC
    PID hash table entries: 1024 (order: 10, 4096 bytes)

     

  • 0 in reply to T B
    TI__Expert 8180 points

    Jase,

    Since earlier you mentioned that you are able to execute some of the Video display applications, I assume you have display driver supported into your kernel version. The reason why I am asking these question is, we do have one release based on 2.6.31-rc5 and your kernel version is referring to 2.6.31-rc7. And at that stage Git kernel doesn't have support for Video Display driver for AM3517.

    Ok, considering the fact that you have Video Display driver ported to your kernel version, below are some of the options you could try -

    - Without any video related argument, the display is diverted to LCD output (480x272-16BPP)

    - Possible Boot argument options -

    http://wiki.davincidsp.com/index.php/UserGuideDisplayDrivers_PSP_03.00.00.05#Command_Line_arguments

    - You can control some of the configurations through SYSFS dynamically -

    http://wiki.davincidsp.com/index.php/UserGuideDisplayDrivers_PSP_03.00.00.05#SYSFS_Software_Interfaces

     

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    Thanks.. Display gets initialized for a moment, so I think that the display drivers are initialize during booting sequence.  I tried these commands but still I get following error.

    OMAP3517EVM # setenv bootargs console=ttyS2, 115200n8 mem=256M root=/dev/mtdblock4 rw rootfstype=jffs2 eth=00:08:EE:03:77:FC, rsize=4096,wsize=4096,omap_vout.video1_numbuffers=3 omap_vout.video2_numbuffers=3 omap_vout.video1_bufsize=64400 omap_vout.video2_bufsize=64400 omap_vout.vid1_static_vrfb_alloc=y omap_vout.vid2_static_vrfb_alloc=y
    OMAP3517EVM #

    Do you know what could be the reason for following error.

     

    root@omap3517-evm:/opt# ./bccube
    Demo started.
    Capture device: /dev/video3
    display[0] w: 480, h: 272
    'eglCreateWindowSurface': egl error 'EGL_NOT_INITIALIZED' (0x3001)
    init tex stream failed
    Error: Failed to create display device
    display thread exits

    main thread exits



    root@omap3517-evm:/opt#

  • 0 in reply to T B
    Intellectual 370 points

    I tried various commands provide on user guide, some of them I have mentioned here. But still facing the same problem.

    Also on EVM board there is no file named 'omap_vout.ko' There is one file in host BSP folder named 'linux-03.00.00.02 ' omap_vout.o.

    Please, tell me what is wrong in this. If possible please send me the steps to solve this problem. These commands use the nfsroot but in my case I am using tftp to boot new kernel


    omap3517evm# insmod omap_vout.ko video1_numbuffers=3 video2_numbuffers=3 video1_bufsize=644000 video2_bufsize=644000 vid1_static_vrfb_alloc=y vid2_static_vrfb_alloc=y

    omap3517evm# setenv bootargs 'console=ttyS2,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock,rsize=272,wsize=480 omapfb.vram=8M'

    OMAP3517EVM# setenv bootargs console=ttyS2,115200n8 mem=256M root=/dev/nfs noinitrd nfsroot=172.24.190.19:nfsserver/home,nolock,rsize=4096,wsize=4096,proto=tcp ip=dhcp omap_vout.video1_numbuffers=3 omap_vout.video2_numbuffers=3 omap_vout.video1_bufsize=64400 omap_vout.video2_bufsize=64400 omap_vout.vid1_static_vrfb_alloc=y omap_vout.vid2_static_vrfb_alloc=y

  • 0 in reply to T B
    TI__Expert 8180 points

    Hi TB,

    The omap_vout source files are present under "<linux kernel>/drivers/media/video/ti-media/" directory. i believe the omap_vout is built into the kernel, you will not find any .ko file.

    If I understand correctly, you are able to run some application without any issues and you are facing some issues with some specific application. Is that understanding correct?

    If yes, then I need to get further details on application which you are trying to run. I would suggest you to use sample application available with release package to verify the display output. Please refer to the <release package>/src/examples/examples.tar.gz

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    Ok...thanks.

    I think there is some misunderstanding here.

    I was able to run demo programs of OMAP35X graphics sdk earlier through nfs.

    Also we get one demo program already installed on EVM board (named bccube) in folder /opt which starts automatically whenever we reboot the board.

    But now I am not able to run any of these demos and it gives me the error as I mentioned above. I am not getting what is wrong with this. Is it something wrong with display parameters or something else?

     

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    Hi Vaibhav,

    Thanks for your help.

    I think there is some misunderstanding here.

    I was able to run demo program of OMAP35x graphics sdk earlier through nfs.

    Also we get one demo program already installed on EVM board (named bccube) in folder /opt which starts automatically whenever we reboot the board.

    But now I am not able to run any of these demos and it gives me the error as I mentioned above. I am not getting what is wrong with this. Is it something wrong with display parameters or something else?

     

  • 0 in reply to T B
    TI__Expert 8180 points

    Hi TB,

    This makes sense now, Ok can we just quickly cross check following options -

     

    - Can you go back to your boot log and see whether driver is throwing any error related to Video display? Can you paste complete boot log here?

    - Can you rebuild the kernel with Linux LOGO enabled and try? This would display Linux penguin Logo using Fbdev, this is completely kernel component so if /dev/fb0 device node is getting created then I expect Logo to come up without any issues.

    - Can you rebuild the kernel with DSS and Fbdev debug options enabled and boot it with argument "omapdss.debug=y omapfb.debug=y".  To enable DSS and Fbdev debug option, please go to

    menuconfig --> Device Drivers --> Graphics support --> OMAP2/3 Display Subsystem support (EXPERIMENTAL)  --> Debug support

    AND

    menuconfig --> Device Drivers --> Graphics support --> OMAP2/3 Display Subsystem support (EXPERIMENTAL)  --> OMAP2/3 frame buffer support (EXPERIMENTAL)  --> Debug support for OMAP2/3 FB

    I am sure we might get something here.

    - Run the sample application available with release package. You can use any of the display sample application, although I would suggest you to use saFbdevDisplay.c, since it is simple and plain application which just write color bar to fbdev buffer.

     

    Thanks,

    Vaibhav

  • 0 in reply to T B
    Intellectual 370 points

    Hi Vaibhav,

    I also have one another doubt which confuses me so I thought let me ask you. This could be the reason or may be not. I tried to find out *.ko files on EVM Board and it gave me following files.

    When kerenel extracts it shows 2.6.31-rc7 as I have shown in previous communication  but on evm board I see these files so why are they under 2.6.29-omap1 folder?

    Is this normal or something wrong in this also?

    /lib/modules/2.6.29-omap1/kernel/drivers/hid/hid-dummy.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/scsi/scsi_wait_scan.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/pwc/pwc.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/uvc/uvcvideo.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_sonixb.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_sonixj.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_main.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/m5602/gspca_m5602.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_mars.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_tv8532.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/stv06xx/gspca_stv06xx.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_spca500.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_spca501.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_spca505.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_spca506.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_spca508.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_spca561.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_t613.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_pac207.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_sunplus.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_stk014.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_ov519.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_ov534.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_finepix.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_etoms.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_conex.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_vc032x.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_pac7311.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/gspca/gspca_zc3xx.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/sn9c102/sn9c102.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/s2255drv.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/videobuf-vmalloc.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/et61x251/et61x251.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/zc0301/zc0301.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/stkwebcam.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/usbvideo/ultracam.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/usbvideo/konicawc.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/usbvideo/usbvideo.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/usbvideo/ibmcam.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/usbvideo/vicam.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/usbvideo/quickcam_messenger.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/zr364xx.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/se401.ko
    /lib/modules/2.6.29-omap1/kernel/drivers/media/video/ov511.ko
    /opt/omaplfb.ko
    /opt/bc_cat.ko
    /opt/pvrsrvkm.ko

  • 0 in reply to T B
    Intellectual 370 points

    Hi Vaibhav,

    ok thanks...i will paste the result soon and also try to go through the options u have recommended ASAP

  • 0 in reply to T B
    Intellectual 370 points

    Hi Vaibhav,

     

    I have attached the booting data here for reference.

    I am trying the options as you said but at very fist option, I don't know how to boot using linux logo. In which file do I have to change to rebuild kernel with linux logo?

     

    ************************

     

    Texas Instruments X-Loader 1.44 (Oct 1 2009 - 19:12:00)

    Starting OS Bootloader...

     

     

    U-Boot 2009.03-dirty (Oct 15 2009 - 11:03:05)

     

    OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz

    OMAP3 omap3517evm board + LPDDR/NAND

    DRAM: 256 MB

    NAND: 512 MiB

    In: serial

    Out: serial

    Err: serial

    Ethernet PHY: GENERIC @ 0x00

    I2C read: I/O error

    HECC U20: port before = 000000FF

    I2C read: I/O error

    I2C read: I/O error

    HECC U20: programmed CAN_STB low

    I2C read: I/O error

    HECC U20: port after = 000000FF

    Die ID #607600000000000001543b210200c009

    Hit any key to stop autoboot: 0

    TFTP from server 172.16.5.239; our IP address is 172.16.6.5

    Filename 'uImage'.

    Load address: 0x80000000

    Loading: ##############T ###################################################

    ################################T ###T ###########T ###################

    ######################################################T ###########

    #################################################################

    #############################T ################T #########T ###########

    ##########################T #######################################

    ####T ##############T ############T ####################

    done

    Bytes transferred = 2248832 (225080 hex)

    ## Booting kernel from Legacy Image at 80000000 ...

    Image Name: Linux-2.6.31-rc7-omap1-06331-g75

    Image Type: ARM Linux Kernel Image (uncompressed)

    Data Size: 2248768 Bytes = 2.1 MB

    Load Address: 80008000

    Entry Point: 80008000

    Verifying Checksum ... OK

    Loading Kernel Image ... OK

    OK

     

    Starting kernel ...

     

    Uncompressing Linux............................................................................................................................................. done, booting the kernel.

    Linux version 2.6.31-rc7-omap1-06331-g757f531 (x0029463@psplinux050) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Thu Oct 1 19:29:57 IST 2009

    CPU: ARMv7 Processor [411fc087] revision 7 (ARMv7), cr=10c53c7f

    CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

    Machine: OMAP3517 EVM

    Memory policy: ECC disabled, Data cache writeback

    OMAP3517 ES1.0 (full speed SGX, IVA2)

    SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000

    Reserving 4194304 bytes SDRAM for VRAM

    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024

    Kernel command line: mem=256M console=ttyS2,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 eth=00:08:EE:03:77:FC

    PID hash table entries: 1024 (order: 10, 4096 bytes)

    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

    Memory: 256MB = 256MB total

    Memory: 251008KB available (3904K code, 360K data, 148K init, 0K highmem)

    SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

    NR_IRQS:368

    Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz

    IVA2 clocking rate: 0 MHz

    GPMC revision 5.0

    IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts

    Total of 96 interrupts on 1 active controller

    OMAP34xx GPIO hardware version 2.5

    OMAP clockevent source: GPTIMER1 at 32768 Hz

    Console: colour dummy device 80x30

    Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)

    Mount-cache hash table entries: 512

    CPU: Testing write buffer coherency: ok

    regulator: core version 0.5

    NET: Registered protocol family 16

    MUX: setup N5_3517_GPIO57_OUT (0xd80020ba): 0x0100 -> 0x0004

    MUX: setup Y9_3430_USB1HS_PHY_STP (0xd80025d8): 0x0018 -> 0x0003

    MUX: setup Y8_3430_USB1HS_PHY_CLK (0xd80025da): 0x0000 -> 0x0003

    MUX: setup AA14_3430_USB1HS_PHY_DIR (0xd80025ec): 0x0100 -> 0x010b

    MUX: setup AA11_3430_USB1HS_PHY_NXT (0xd80025ee): 0x0100 -> 0x010b

    MUX: setup W13_3430_USB1HS_PHY_D0 (0xd80025dc): 0x0100 -> 0x010b

    MUX: setup W12_3430_USB1HS_PHY_D1 (0xd80025de): 0x0100 -> 0x010b

    MUX: setup W11_3430_USB1HS_PHY_D2 (0xd80025e0): 0x0108 -> 0x010b

    MUX: setup Y11_3430_USB1HS_PHY_D3 (0xd80025ea): 0x0100 -> 0x010b

    MUX: setup W9_3430_USB1HS_PHY_D4 (0xd80025e4): 0x0100 -> 0x010b

    MUX: setup Y12_3430_USB1HS_PHY_D5 (0xd80025e6): 0x0100 -> 0x010b

    MUX: setup W8_3430_USB1HS_PHY_D6 (0xd80025e8): 0x0100 -> 0x010b

    MUX: setup Y13_3430_USB1HS_PHY_D7 (0xd80025e2): 0x0100 -> 0x010b

    MUX: setup AA16_34XX_GPI181 (0xd80021dc): 0x010c -> 0x011c

    MUX: setup AE17_34XX_GPIO182 (0xd80021de): 0x010c -> 0x011c

    MUX: setup AE15_34XX_GPIO176 (0xd80021d0): 0x010c -> 0x011c

    Display initialized successfully

    OMAP DMA hardware revision 4.0

    bio: create slab <bio-0> at 0

    i2c_omap i2c_omap.1: bus 1 rev3.12 at 400 kHz

    regulator: VDCDC1: 1200 mV

    regulator: VDCDC2: 3300 mV

    regulator: VDCDC3: 1800 mV

    regulator: LDO1: 1800 mV

    regulator: LDO2: 3300 mV

    i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz

    i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz

    SCSI subsystem initialized

    usbcore: registered new interface driver usbfs

    usbcore: registered new interface driver hub

    usbcore: registered new device driver usb

    musb_hdrc: version 6.0, cppi4.1-dma, otg (peripheral+host), debug=0

    Waiting for PHY clock good...(CONF0=0xf003622)

    OMAP3517 OTG revision 4ea41001, PHY f0036a2, control 00

    musb_hdrc: USB OTG mode controller at d0810000 using DMA, IRQ 71

    NET: Registered protocol family 2

    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

    TCP established hash table entries: 8192 (order: 4, 65536 bytes)

    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

    TCP: Hash tables configured (established 8192 bind 8192)

    TCP reno registered

    NET: Registered protocol family 1

    OMAP3517 Linux PSP version 03.00.00.02 (OMAP3517EVM)

    VFS: Disk quotas dquot_6.5.2

    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

    JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.

    msgmni has been set to 490

    alg: No test for stdrng (krng)

    io scheduler noop registered

    io scheduler anticipatory registered (default)

    io scheduler deadline registered

    io scheduler cfq registered

    OMAP DSS rev 2.0

    OMAP DISPC rev 3.0

    OMAP VENC rev 2

    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

    serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654

    serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654

    serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654

    console [ttyS2] enabled

    brd: module loaded

    loop: module loaded

    i2c /dev entries driver

    emac-mii: probed

    vcan: Virtual CAN interface driver

    CAN device driver interface

    TI High End CAN Controller Driver 0.4

    ti_hecc ti_hecc.1: device registered (reg_base=d0808000, irq=24)

    usbcore: registered new interface driver asix

    usbcore: registered new interface driver cdc_ether

    usbcore: registered new interface driver net1080

    usbcore: registered new interface driver cdc_subset

    usbcore: registered new interface driver zaurus

    omap2-nand driver initializing

    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V 16-bit)

    Creating 5 MTD partitions on "omap2-nand.0":

    0x000000000000-0x000000080000 : "xloader-nand"

    0x000000080000-0x000000240000 : "uboot-nand"

    0x000000240000-0x000000280000 : "params-nand"

    0x000000280000-0x000000780000 : "linux-nand"

    0x000000780000-0x000020000000 : "jffs2-nand"

    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

    ehci-omap ehci-omap.0: OMAP-EHCI Host Controller

    ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1

    ehci-omap ehci-omap.0: irq 77, io mem 0x48064800

    ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00

    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

    usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

    usb usb1: Product: OMAP-EHCI Host Controller

    usb usb1: Manufacturer: Linux 2.6.31-rc7-omap1-06331-g757f531 ehci_hcd

    usb usb1: SerialNumber: ehci-omap.0

    usb usb1: configuration #1 chosen from 1 choice

    hub 1-0:1.0: USB hub found

    hub 1-0:1.0: 3 ports detected

    Initializing USB Mass Storage driver...

    usbcore: registered new interface driver usb-storage

    USB Mass Storage support registered.

    g_ether gadget: using random self ethernet address

    g_ether gadget: using random host ethernet address

    usb0: MAC 7e:dc:b8:8e:c0:a8

    usb0: HOST MAC 0a:3b:29:40:84:a5

    g_ether gadget: Ethernet Gadget, version: Memorial Day 2008

    g_ether gadget: g_ether ready

    musb_hdrc musb_hdrc: MUSB HDRC host driver

    musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2

    usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

    usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

    usb usb2: Product: MUSB HDRC host driver

    usb usb2: Manufacturer: Linux 2.6.31-rc7-omap1-06331-g757f531 musb-hcd

    usb usb2: SerialNumber: musb_hdrc

    usb usb2: configuration #1 chosen from 1 choice

    hub 2-0:1.0: USB hub found

    hub 2-0:1.0: 1 port detected

    Linux video capture interface: v2.00

    vpfe_init

    vpfe-capture: vpss clock vpfe_ck enabled

    vpfe-capture: vpss clock vpfe_pck enabled

    vpfe-capture vpfe-capture: v4l2 device registered

    vpfe-capture vpfe-capture: video device registered

    tvp514x 3-005c: tvp514x 3-005c decoder driver registered !!

    vpfe-capture vpfe-capture: v4l2 sub device tvp514x registered

    dm644x_ccdc_init

    vpfe_register_ccdc_device: DM6446 CCDC

    DM6446 CCDC is registered with vpfe.

    usbcore: registered new interface driver uvcvideo

    USB Video Class driver (v0.1.0)

    OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec

    mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock

    mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock

    usbcore: registered new interface driver usbhid

    usbhid: v2.6:USB HID core driver

    Advanced Linux Sound Architecture Driver Version 1.0.20.

    usbcore: registered new interface driver snd-usb-audio

    No device for DAI tlv320aic23

    No device for DAI omap-mcbsp-dai-0

    No device for DAI omap-mcbsp-dai-1

    No device for DAI omap-mcbsp-dai-2

    No device for DAI omap-mcbsp-dai-3

    No device for DAI omap-mcbsp-dai-4

    OMAP3 EVM SoC init

    AIC23 Audio Codec 0.1

    tlv320aic23_write cannot write 000 to register R15

    asoc: tlv320aic23 <-> omap-mcbsp-dai-0 mapping ok

    tlv320aic23_write cannot write 047 to register R6

    tlv320aic23_write cannot write 004 to register R5

    tlv320aic23_write cannot write 117 to register R0

    tlv320aic23_write cannot write 117 to register R1

    tlv320aic23_write cannot write 010 to register R4

    tlv320aic23_write cannot write 070 to register R2

    tlv320aic23_write cannot write 070 to register R3

    tlv320aic23_write cannot write 001 to register R9

    tlv320aic23_write cannot write 047 to register R6

    ALSA device list:

    #0: omap3517evm (tlv320aic23)

    TCP cubic registered

    NET: Registered protocol family 17

    NET: Registered protocol family 15

    can: controller area network core (rev 20090105 abi 8)

    NET: Registered protocol family 29

    can: raw protocol (rev 20090105)

    can: broadcast manager protocol (rev 20090105 t)

    RPC: Registered udp transport module.

    RPC: Registered tcp transport module.

    Power Management for TI OMAP3.

    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1

    regulator_init_complete: incomplete constraints, leaving LDO2 on

    regulator_init_complete: incomplete constraints, leaving LDO1 on

    regulator_init_complete: incomplete constraints, leaving VDCDC3 on

    regulator_init_complete: incomplete constraints, leaving VDCDC2 on

    regulator_init_complete: incomplete constraints, leaving VDCDC1 on

    omapdss DPI: display already enabled

    omap_vout omap_vout: 'lcd' Display already enabled

    omapdss DPI: display already enabled

    omap_vout omap_vout: 'lcd' Display already enabled

    omap_voutBuffer Size = 3686400

    omap_vout: registered and initialized video device 1 [v4l2]

    omap_voutBuffer Size = 3686400

    omap_vout: registered and initialized video device 2 [v4l2]

    Empty flash at 0x01308acc ends at 0x01309000

    jffs2_scan_inode_node(): CRC failed on node at 0x05877ff0: Read 0xffffffff, calculated 0x6fb3f3d5

    Empty flash at 0x05878110 ends at 0x05878800

    Empty flash at 0x1b8b809c ends at 0x1b8b8800

    VFS: Mounted root (jffs2 filesystem) on device 31:4.

    Freeing init memory: 148K

    INIT: version 2.86 booting

    Please wait: booting...

    Starting udev

    udev: starting version 141

    /etc/rcS.d/S03udev: line 79: rm: not found

    Remounting root file system...

    WARNING: Couldn't open directory /lib/modules/2.6.31-rc7-omap1-06331-g757f531: No such file or directory

    FATAL: Could not open /lib/modules/2.6.31-rc7-omap1-06331-g757f531/modules.dep.temp for writing: No such file or directory

    modprobe: FATAL: Could not load /lib/modules/2.6.31-rc7-omap1-06331-g757f531/modules.dep: No such file or directory

     

    modprobe: FATAL: Could not load /lib/modules/2.6.31-rc7-omap1-06331-g757f531/modules.dep: No such file or directory

     

    root: mount: mounting rootfs on / failed: No such file or directory

    Setting up IP spoofing protection: rp_filter.

    Configuring network interfaces... eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:00, id=7c0f1)

    udhcpc (v1.13.2) started

    Sending discover...

    PHY: 1:00 - Link is Up - 100/Full

    Sending discover...

    Sending select for 172.16.6.5...

    Lease of 172.16.6.5 obtained, lease time 268435455

    adding dns 172.16.4.2

    adding dns 202.148.200.3

    done.

    Wed Sep 23 04:29:00 UTC 2009

    INIT: Entering runlevel: 5

    Starting telnet daemonmodprobe: FATAL: Could not load /lib/modules/2.6.31-rc7-omap1-06331-g757f531/modules.dep: No such file or directory

     

    .

    Starting syslogd/klogd: done

    Starting thttpd.

    PVRSRV_PIXEL_FORMAT_RGB565

    rcinit.sh done

     

    _____ _____ _ _

    | _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_

    | | _| .'| . | . | | __| _| . | | | -_| _| _|

    |__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|

    |___| |___|

     

    Arago Project http://arago-project.org omap3517-evm ttyS2

     

    Arago 2009.09 omap3517-evm ttyS2

     

    omap3517-evm login: Profiling enabled

    Demo started.

    Capture device: /dev/video3

    display[0] w: 480, h: 272

    'eglCreateWindowSurface': egl error 'EGL_NOT_INITIALIZED' (0x3001)

    init tex stream failed

    Error: Failed to create display device

    display thread exits

     

    main thread exits

    Texas Instruments X-Loader 1.44 (Oct 1 2009 - 19:12:00)

     

     

  • 0 in reply to T B
    TI__Expert 8180 points

    Hi TB,

    I could see display is getting initializes properly here,  so believe if you run any application on top of Fbdev or V4L2 display the output should come on LCD. Have you tried writing any data to Fbdev buffer? As I mentioned you can use sample application available with release.

     

    To enable Logo follow below steps -

    menuconfig --> Device Drivers --> Graphics Support --> Bootup logo               [It will enable all the options inside]

    And

    menuconfig --> Device Drivers --> Graphics Support --> Console display driver support  ---> Framebuffer Console support

     

    This should bring penguin Logo on to LCD during bootup.

    Thanks,

    Vaibhav

  • 0 in reply to T B
    TI__Guru**** 173511 points

    T B said:

    i tried following commands to set the size

    OMAP3517EVM # setenv bootargs mem=256M console=ttyS2, 115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 eth=__:__:__:__:__:__ , rsize=272, wsize=480

    but this does not work.

    restore env partition back to defalut:

    "nand erase 260000 20000"

    then add "omapfb.vram=0:4M" at the end of your boorargs. This will fix your problem.

     

  • 0 in reply to Bin Liu
    TI__Guru**** 173511 points

    "1M" should be sufficient to make the demo work.

  • 0 in reply to Bin Liu
    Intellectual 370 points

    Hi,

    I can see the Linux LOGO and omap3517-evm login: prompt so it is good to see some text on screen.

    now so what should I do next? I am still exploring the other options that you have told me.

     

     

     

  • 0 in reply to Bin Liu
    Intellectual 370 points

    Hi,

    Thank you for your help.

    I tried following things and now I can see the linux logo also I see the text after booting showing the login prompt. Which is great relief however still way to go.I am still exploring other options that you have given me but I am new with this so bit slow in progress.

    So what should I do next?

     

    menuconfig --> Device Drivers --> Graphics Support --> Bootup logo               [It will enable all the options inside]

    And

    menuconfig --> Device Drivers --> Graphics Support --> Console display driver support  ---> Framebuffer Console support

  • 0 in reply to T B
    TI__Expert 8180 points

    TB,

    That means everything is clean and working fine, now its all yours. I can help you to unblock you but I can't tell you what to do next.

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    Dear Vaibhav,

    I appreciate your help. It is good to know that everything is clean and working fine.

    But my original problem still remains. As you know I could not see the output on screen from some default demo programs (which were running fine earlier). Still it remains the same. So why is it so? Do I need to do anything else to see these demo again on screen?

    following is the error when I run the demo program of  "bccube"

    root@omap3517-evm:/opt# ./bccube
    Demo started.
    Capture device: /dev/video3
    display[0] w: 480, h: 272
    'eglCreateWindowSurface': egl error 'EGL_NOT_INITIALIZED' (0x3001)
    init tex stream failed
    Error: Failed to create display device
    display thread exits

    main thread exits

    Please, give me your inputs on this.

    Regards,

     

     

  • 0 in reply to T B
    TI__Guru**** 173511 points

    Have you tried the bootargs I mentioned?

  • 0 in reply to T B
    TI__Expert 8180 points

    HI TB,

    I am not GFXDSK expert so not sure how much I can help you here. But I can help you to unblock any driver issue. Quick check -

    It could possible GFXSDK demos are using double buffering, in that case you have to pass boot argument to allocate sufficient memory. Again please refer to the UserGuide (link I had already shared).[vram= and omapfb.vram=]

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    TI__Guru**** 173511 points

    TB,

    The demo uses triple frame buffers.
    If you did not overwrite u-boot, simple do "nand erase 260000 20000" to reverse ENV partition back to default will make the demo work. the vram= option is already in the default setup.

  • 0 in reply to Bin Liu
    Intellectual 370 points

    Hi Bin Liu,

    Thanks for your inputs. Your confidence says that it must work but I am not as confident as you in trying nand erase command so please let me know your input for the following.

    I have not tried erase nand command yet but now I am going to try these commands as you have suggested. I have given them here.

    omap3517evm# nand erase 260000 20000

    omap3517evm# setenv bootargs mem=256M console=ttyS2, 115200n8 noinitrd root=/dev/mtdblock4 rwo rootfstype=jffs2 eth=00:11:22:33:44:55, omapfb.vram=0:4M

     

    please let me know if anything is wrong.

    Are these addresses same for my board (AM3517 EVM) also? Actually, I am not very familiar with these nand addresses so I am worried that I don't erase the file system on nand or something else important. As you know this is where my problems started.

    Therefore, I have attached the script file here for your reference. Please let me know if I need to change anything in these command.

     

    ------------reflash-micron.txt------------------------------------------------

    setenv rf_unlock nand unlock

    setenv rf_blank_ram mw.b 0x81600000 0xff 0x1400000

    setenv rf_er_xloader nand erase 0 20000

    setenv rf_er_uboot nand erase 80000 40000

    setenv rf_er_env nand erase 260000 20000

    setenv rf_er_kernel nand erase 280000 260000

    setenv rf_er_ramdisk nand erase 780000 1000000

    setenv rf_er_fs nand erase 780000 1400000

    setenv rf_get_xloader tftpboot 0x81600000 images/boot-strap/omap3517/x-load.bin.ift

    setenv rf_get_uboot tftpboot 0x81600000 images/u-boot/omap3517/u-boot.bin

    setenv rf_get_kernel tftpboot 0x81600000 images/kernel/omap3517/uImage

    setenv rf_get_ramdisk tftpboot 0x81600000 images/fs/omap3517/ramdisk.gz

    setenv rf_get_min_rd tftpboot 0x81600000 images/fs/ramdisk-base.gz

    setenv rf_get_fs tftpboot 0x81600000 images/fs/omap3517/rootfs.jffs2

    setenv rf_wr_xloader_new nandecc hw\; nand write.i 0x81600000 0 20000

    setenv rf_wr_uboot_new nandecc sw\; nand write.i 0x81600000 80000 40000

    setenv rf_wr_kernel_new nandecc sw\; nand write.i 0x81600000 280000 260000

    setenv rf_wr_ramdisk_new nandecc sw\; nand write.i 0x81600000 780000 1000000

    setenv rf_wr_fs_new nandecc sw\; nand write.i 0x81600000 780000 1400000

    setenv rf_wr_xloader_old nand ecc hw\; nand write.i 0x81600000 0 20000

    setenv rf_wr_uboot_old nand ecc sw\; nand write.i 0x81600000 80000 40000

    setenv rf_wr_kernel_old nand ecc sw\; nand write.i 0x81600000 280000 220000

    setenv rf_wr_ramdisk_old nand ecc sw\; nand write.i 0x81600000 780000 1000000

    setenv rf_wr_fs_old nand ecc sw\; nand write.i 0x81600000 780000 1400000

    setenv rf_ev run rf_unlock\; run rf_er_env

    setenv rf_xl_old run rf_unlock\; run rf_blank_ram\; run rf_er_xloader\; run rf_get_xloader\; run rf_wr_xloader_old

    setenv rf_ub_old run rf_unlock\; run rf_blank_ram\; run rf_er_uboot\; run rf_get_uboot\; run rf_wr_uboot_old

    setenv rf_kn_old run rf_unlock\; run rf_blank_ram\; run rf_er_kernel\; run rf_get_kernel\; run rf_wr_kernel_old

    setenv rf_rd_old run rf_unlock\; run rf_blank_ram\; run rf_er_ramdisk\; run rf_get_ramdisk\; run rf_wr_ramdisk_old

    setenv rf_min_rd_old run rf_unlock\; run rf_blank_ram\; run rf_er_ramdisk\; run rf_get_min_rd\; run rf_wr_ramdisk_old

    setenv rf_fs_old run rf_unlock\; run rf_blank_ram\; run rf_er_fs\; run rf_get_fs\; run rf_wr_fs_old

    setenv rf_xl_new run rf_blank_ram\; run rf_er_xloader\; run rf_get_xloader\; run rf_wr_xloader_new

    setenv rf_ub_new run rf_blank_ram\; run rf_er_uboot\; run rf_get_uboot\; run rf_wr_uboot_new

    setenv rf_kn_new run rf_blank_ram\; run rf_er_kernel\; run rf_get_kernel\; run rf_wr_kernel_new

    setenv rf_rd_new run rf_blank_ram\; run rf_er_ramdisk\; run rf_get_ramdisk\; run rf_wr_ramdisk_new

    setenv rf_min_rd_new run rf_blank_ram\; run rf_er_ramdisk\; run rf_get_min_rd\; run rf_wr_ramdisk_new

    setenv rf_fs_new run rf_blank_ram\; run rf_er_fs\; run rf_get_fs\; run rf_wr_fs_new

    setenv rf_all_rd_old run rf_xl_old\; run rf_ub_old\; run rf_kn_old\; run rf_rd_old

    setenv rf_all_min_rd_old run rf_xl_old\; run rf_ub_old\; run rf_kn_old\; run rf_min_rd_old

    setenv rf_all_fs_old run rf_xl_old\; run rf_ub_old\; run rf_kn_old\; run rf_fs_old

    setenv rf_all_rd_new run rf_xl_new\; run rf_ub_new\; run rf_kn_new\; run rf_rd_new

    setenv rf_all_min_rd_new run rf_xl_new\; run rf_ub_new\; run rf_kn_new\; run rf_min_rd_new

    setenv rf_all_fs_new run rf_xl_new\; run rf_ub_new\; run rf_kn_new\; run rf_fs_new

    printenv

    echo done

     

    -----------initenv-mocron.txt---------------------------------

    setenv get_kernel run nand_kernel

    setenv get_initrd run nand_initrd

    setenv nand_kernel nand read.i 0x80000000 280000 260000

    setenv nand_initrd nand read.i 0x81600000 780000 1000000

    setenv tftp_kernel tftpboot 0x80000000 uImage

    setenv tftp_initrd tftpboot 0x81600000 ramdisk.gz

    setenv bootargs_rd mem=128M console=ttyS2,115200n8 root=/dev/ram0 initrd=0x81600000,40M ramdisk_size=40960

    setenv bootargs_fs mem=128M console=ttyS2,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2

    setenv bootargs_nfs mem=128M console=ttyS2,115200n8 noinitrd rw root=/dev/nfs nfsroot=/mnt/nfs,nolock

    setenv addip setenv bootargs \$bootargs ip=\$ipaddr:\$serverip:\$gatewayip:\$netmask:\$hostname:eth0:on

    setenv boot_rd run get_kernel\; run get_initrd\; setenv bootargs \$bootargs_rd\; run addip\; bootm 0x80000000

    setenv boot_fs run get_kernel\; setenv bootargs \$bootargs_fs\; run addip\; bootm 0x80000000

    setenv boot_nfs run get_kernel\; setenv bootargs \$bootargs_nfs\; run addip\; bootm 0x80000000

    setenv bootcmd run boot_fs

    setenv bootdelay 20

    setenv bootkernel

    setenv bootkernel_1

    printenv

    echo Make sure to set MAC address

  • 0 in reply to T B
    TI__Guru**** 173511 points

    Okay, I understood you concern.

    Can you please just simply add "omapfb.vram=0:1M" at the end of your bootargs? and if the demo still does not work. Please paste your whole bootargs here to let me double check.

  • 0 in reply to Bin Liu
    Intellectual 370 points

    Hi,

    thanks for quick reply.

    I tried following bootarg command first and restart the board. But it did not start demo.

    omap3517evm# setenv bootargs mem=256M console=ttyS2, 115200n8 noinitrd root=/dev/mtdblock4 rwo rootfstype=jffs2 eth=00:11:22:33:44:55, omapfb.vram=0:1M

     

    Now shall I try these two together as below? Please, confirm this.

    omap3517evm# nand erase 260000 20000

    omap3517evm# setenv bootargs mem=256M console=ttyS2, 115200n8 noinitrd root=/dev/mtdblock4 rwo rootfstype=jffs2 eth=00:11:22:33:44:55, omapfb.vram=0:1M

     

     

  • 0 in reply to Bin Liu
    Intellectual 370 points

    Great news..now I can see the demo program also........hurray!

    Thank you all...It has been great talking with you all, I really appreciate your help in this matter.

     

    omap3517evm# nand erase 260000 20000

    omap3517evm# setenv bootargs mem=256M console=ttyS2, 115200n8 noinitrd root=/dev/mtdblock4 rwo rootfstype=jffs2 eth=00:11:22:33:44:55, omapfb.vram=0:1M

     

    I did above commands and it worked but I could not understand it completely, how did it help? In fact after giving above commands it boot from tftp but after that when I restart it started to boot from the nand itself. I did not write anything to nand.

    Does it mean that nothing was lost while I tried 'saveenv' command ealier?

    As you mentioned that “nand erase 260000 20000” restore the env partition back to default. Does that mean that if I use “saveenv” command in future to save different environment and it does not work fine then I can run this command to set the default environment?

     

     

  • 0 in reply to T B
    TI__Guru**** 173511 points

    T B said:

    omap3517evm# nand erase 260000 20000

    omap3517evm# setenv bootargs mem=256M console=ttyS2, 115200n8 noinitrd root=/dev/mtdblock4 rwo rootfstype=jffs2 eth=00:11:22:33:44:55, omapfb.vram=0:1M

    only the first command is sufficient. after erase the env partition, env will be restored back to default, and bootargs is something similar in your 2nd command.

    "omapfb.vram=0:1M" is the key to run the demo.

    "rwo" is strange to me. I always use "rw".

    I did above commands and it worked but I could not understand it completely, how did it help? In fact after giving above commands it boot from tftp but after that when I restart it started to boot from the nand itself. I did not write anything to nand.

    I suspect somehow you messed up your uboot env, so the demo cannot get enough framebuffer then refuse to run. after erase env, all the env setup comes from uboot built-in, which means "vram=" is in bootargs to make the demo work.

    After erase i think you did not reboot, so it boots from tftp, which was your setup before erase but already in ram. but after reboot, the uboot built-in is set to boot from nand.

    Does it mean that nothing was lost while I tried 'saveenv' command ealier?

    correct, as long as you did not destroy mlo, uboot, or rootfs partition. uImage is not an issue since it is easy to restore. But the u-boot.bin you built fromPSP src will not work directly with the demo since "vram=" is not built-in.

    As you mentioned that “nand erase 260000 20000” restore the env partition back to default. Does that mean that if I use “saveenv” command in future to save different environment and it does not work fine then I can run this command to set the default environment?

    correct. but just double check the numbers you typed in before press 'Enter' ;)

     

  • 0 in reply to Bin Liu
    Intellectual 370 points

    Hi,

    thanks for the help. As everything is back to previous stage. I have two new different questions please, let me know if you can help.

     

    1 ) At present when we reboot the system we see the kernel extract details on the Teraterm (hyper terminal ) but can I see the same detail on the LCD screen? What should I do for this?

     

    2) I am working on QT 4.6.2  for embedded linux and want to run the demos of QT on EVM board. I can run its ./cofigure and gmake command and it works without error but when I run following commands using omap3_qt46_config.patch but it give me following error.

    Please let me know if you can help me in this problem.

    gmake confclean

    ./configure_omap3

    gmake

     

    ../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:405: warning: lowering visibility of ‘QSharedPointer<X> QtSharedPointer::copyAndSetPointer(X*, const QSharedPointer<Y>&) [with X = X, Y = Y, T = QAbstractAnimation]’ to match its type
    {standard input}: Assembler messages:
    {standard input}:560: Error: no such instruction: `swpb %cl,%al,[%edi]'
    {standard input}:573: Error: no such instruction: `swpb %al,%sil,[%edi]'
    {standard input}:585: Error: no such instruction: `swpb %cl,%al,[%edi]'

    :

    :

    {standard input}:3858: Error: no such instruction: `swpb %cl,%al,[%edi]'
    gmake[1]: *** [.obj/release-shared-emb-arm/qabstractanimation.o] Error 1
    gmake[1]: Leaving directory `/opt/qtembedded/qt-everywhere-opensource-src-4.6.2/src/corelib'
    gmake: *** [sub-corelib-make_default-ordered] Error 2

    regards,

  • 0 in reply to T B
    TI__Expert 8180 points

    Hi TB,

    I can answer you first Question,

    To divert all serial console prints to LCD (more precisely on /dev/fb0) follow below steps -

    - Enable CONFIG_FRAMEBUFFER_CONSOLE option in kernel config

    - Do not specify "console=ttyS0,115200n8" boot argument on u-boot.

    This will automatically push all serial messages to /dev/fb0 output.

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    Ok..thanks

    But right now I am booting from nand only so in that case what can I do to show it on screen?

    regards,

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    Hi Vaibhav,

    I can see the kernel on screen now, thanks for your help.

    But after extracting the kernel it transfers control to the teraterm. I tried to interface keyboard with board but it did not work. I run the menuconfig commande and selected following options.

    Device drivers----->Input device support ----> Keyboards --> Selected all options

    Is this correct? Do I need to select any other options also?

     

    regards,

    TB

     

  • 0 in reply to Vaibhav Hiremath
    Intellectual 370 points

    Hi,

    I just tried to give supply externally to apple keyboard by connecting its extra usb of keyboard to computer and connected the keyboard usb cable to the board.

    Now it detects the keypad but when the prompt comes after the booting, it does not write anything in it??

    what could be the problem? Why is it not taking input from keyboard?

     

    regards.

    TB

     

     

     

  • 0 in reply to T B
    TI__Genius 9460 points

    We would require to setup system console to USB keyboard. We normally test USB keyboard using evtest program which captured the keyboard events and throws to serial console.

    -Ajay