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.

Problem Setting Up DaVinci Eval Board

I'm having issues setting up my eval board. I have installed the ti-ezsdk_dm814x-evm_5_02_02_60.  I have a TMDXEVM8148 board.  I have tried to run the setup.sh script.  It seems to work fine up to the last moment when it sets up the board.  I set every thing to default (NFS and TFTP).  My services are all running.  Files have been created and placed in the correct locations.  The setup script created a minicom script.  Minicom is able to connect to the board.  The minicom script was able to stop the default boot.  However, nothing else happens.  The board has stopped at the 1st stage boot.

TI-MIN#

 

I looked at the minicom setup script.  I see it does a "stop autoboot:".  Then, it waits for "TI8164_EVM#".  Is it waiting for the 2nd stage boot?  I've tested the Ethernet connection between the host and board.  It seems fine.  I'm not sure what is wrong.

  • Hi Thanh,

              Have you been using the SD/MMC Card provided in the kit?

              Also post the complete log accordingly.

     

    Regards,

    N.S.SriHarsha

  • Welcome to minicom 2.4

    OPTIONS: I18n
    Compiled on Jan 25 2010, 06:49:09.
    Port /dev/ttyUSB0

    Press CTRL-A Z for help on special keys



    U-Boot 2010.06 (Aug 26 2011 - 01:19:25)

    TI8148-GP rev 2.1

    ARM clk: 600MHz
    DDR clk: 400MHz

    DRAM:  2 GiB
    Using default environment

    The 2nd stage U-Boot will now be auto-loaded
    Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is ald
    Hit any key to stop autobo 0                                                   
    TI-MIN#

     

    Yes, I'm using the provided SD card.  The log does not say much.  All it does is stop the normal boot process.

  • As an experiment, I modified the generated minicom script to recognize the TI-MIN# prompt.  I rebooted the board and got the following.  I noticed "saveenv" is not a valid command.  I also noticed the ip is set to dhcp.  I have a board connected directly to my pc host.  I want the board's ip address to be static assigned.

     

     

     

    Welcome to minicom 2.4

    OPTIONS: I18n
    Compiled on Jan 25 2010, 06:49:09.
    Port /dev/ttyUSB0

    Press CTRL-A Z for help on special keys



    U-Boot 2010.06 (Aug 26 2011 - 01:19:25)

    TI8148-GP rev 2.1

    ARM clk: 600MHz
    DDR clk: 400MHz

    DRAM:  2 GiB
    Using default environment

    The 2nd stage U-Boot will now be auto-loaded         
    Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is ald
    Hit any key to stop autobo 0                                                   
    TI-MIN#setenv bootdelay 4                                                      
    TI-MIN#setenv baudrate 115200                                                  
    ## Switch baudrate to 115200 bps and press ENTER ...TI-MIN#setenv oldbootargs $}
    TI-MIN#ip=dhcp                                                                 
    TI-MIN#setenv autoload no                                                      
    TI-MIN#setenv oldserverip ${serverip}                                          
    TI-MIN#setenv serverip 20.300.300.300                                          
    TI-MIN#setenv oldbootfile ${bootfile}                                          
    TI-MIN#setenv bootfile uImage-dm814x-evm.bin                                   
    TI-MIN#setenv oldbootcmd ${bootcmd}                                            
    TI-MIN#setenv bootcmd 'dhcp;setenv serverip 20.300.300.300;tftpboot;bootm'     
    TI-MIN#saveenv                                                                 
    Unknown command 'saveenv' - try 'help'                                         
    TI-MIN#

     

     

  • Here is the generated minicom setup script.

     

    timeout 300
    verbose on

    expect {
        "stop autoboot:"
    }
    send ""

    expect {
        "TI8164_EVM#"
    }
    send "setenv bootdelay 4"

    expect {
        "TI8164_EVM#"
    }
    send "setenv baudrate 115200"

    expect {
        "ENTER ..."
    }
    send ""

    expect {
        "TI8164_EVM#"
    }
    send "setenv oldbootargs $\{bootargs\}"

    expect {
        "TI8164_EVM#"
    }
    send "setenv bootargs console=ttyO0,115200n8 rootwait rw mem=256M earlyprintk \c"

    send "notifyk.vpssm3_sva=0xBF900000 vram=50M \c"
    send "ti814xfb.vram=0:16M,1:16M,2:6M \c"
    send "root=/dev/nfs nfsroot=20.300.300.300:$(ROOTPATH) \c"
    send "ip=dhcp"
    expect {
        "TI8164_EVM#"
    }
    send "setenv autoload no"

    expect {
        "TI8164_EVM#"
    }
    send "setenv oldserverip $\{serverip\}"

    expect {
        "TI8164_EVM#"
    }
    send "setenv serverip 20.300.300.300"

    expect {
        "TI8164_EVM#"
    }
    send "setenv oldbootfile $\{bootfile\}"

    expect {
        "TI8164_EVM#"
    }
    send "setenv bootfile uImage-dm814x-evm.bin"

    expect {
        "TI8164_EVM#"
    }
    send "setenv oldbootcmd $\{bootcmd\}"

    expect {
        "TI8164_EVM#"
    }
    send "setenv bootcmd 'dhcp;setenv serverip 20.300.300.300;tftpboot;bootm'"

    expect {
        "TI8164_EVM#"
    }
    send "saveenv"

    expect {
        "TI8164_EVM#"
    }
    ! killall -s SIGHUP minicom

  • Hi Thanh,

               The saveenv command might not be working because NAND is switched off in the MainBoard at location SW2 near the power ON button.

               I'm also suspecting the fact that you are getting the prompt as "TI8164_EVM#" on TMDXEVM8148 EVM. Are you sure you have been using the SD/MMC Card provided in the kit.

     

    Regards,

    N.S.SriHarsha

     

  • Yes, I'm using the SD card which came with the board.  It is marked DM814x/C6A814x/AM387x.  The board packaging states it's a TMDXEVM8148.  Is it possible that there is a mix up between software and hardware versions?  I'll enable the NAND.  Thank you.

  • This problem has been solved.  The script was not waiting for the 2nd stage boot.  It jumped in at the 1st stage.  I also needed to modify the expected prompt.  The script needed to wait for a TI8148.