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.

TMDEXVM3730: ${DVSDK}/setup.sh

Hello,

Just received my TMDEXVM3730 kit, and am having trouble with the setup.sh script. I am trying to follow the instructions in the TMS320DM3730 Software Developers Guide".

I am running Windows XP Pro on an HP laptop, and using VMPlayer to provide my Ubuntu 10.04 LTS environment.

I ran through the Quick Start Guide and everything works fine until Step 16 (last step). This step says to run setup.htm. I get all the way through to Step 8 without any warnings or errors or issues. This step says to follow the Software Developers Guide, which I began....

I have several questions/problem in the Software Developers Guide, starting at "Setting Up the DVSDK":

1. The guide says to run setup.sh. This script implies heavily that the host pc and therefore the ubuntu vm use static IP addressing. In my environment, dhcp is used. A custom script "setup_uimage-tftp_fs-nfs.minicom" gets generated, and the IP addresses get hard-coded in the script. Since my vm gets a different ip address every time, specifying a static IP in the script makes non sense. Suggestions? I accepted the current IP so I could keep going.

2. Must you run this setup.sh script every time, or just once?

3. The last step (Step 16) in the Quick Start Guide says to remove the Linux SDK SD card then plug it into the host PC and run setup.  Afterwards, are you suppose to plug the  SD card back into the evm board? Or do you need to leave it connected to the host PC? Or store it away? I left it attached to the host.

4. Do you run the setup.sh script for EACH USER? Does the user need to be root? I tried a normal user that has sudo privleges, but files and directories are created that are owned by root and not writable by the normal user.

5. I ran everything as a normal user, and setup.sh eventually asks me if I want to run the minicom script. Doing so does bring up minicom, but it just hangs there forever.

Hitting keys or "CTRL-A Z" has no affect. I have verified I have the correct serial port and that it works.

6. I noticed during the script that it sets up tftp and configures it. If I search for the running process 'tftp' using the command 'ps auxww|grep -i ftp' it shows nothing so named.

Is this a problem?

 

The end result is that I have minicom just sitting there, and no instructions on how to proceed or how to troubleshoot or validate that everything went correctly.

Any help would be very much appreciated. Thanks.

 

  • Hello,

    I'm giving you the summary of what you need to do instead of answering indivdual questions (as that can confuse a bit) and then some optional tips.

    1) After installing DVSDK on your Host PC, umount the SD card.

    2)  Make sure your EVM is powered OFF, plug the SD card back  into the EVM as explained in Quick Start Guide.

    3) Run the setup.sh script  (there is no harm running  it more than once). And technically you need to run this only once, but if your host IP address changes then you will need to re-program the new serverip address on u-boot (see optional steps for detail). When you see the below message ("Would you like to run the setup script now (y/n)). And if your RS-232 cable is connected between host and EVM then say "y"

    Would you like to run the setup script now (y/n)? This requires you to connect
    the RS-232 cable between your host and EVM as well as your ethernet cable as
    described in the Quick Start Guide. Once answering 'y' on the prompt below
    you will have 300 seconds to connect the board and power cycle it
    before the setup times out.

    After successfully executing this script, your EVM will be set up. You will be
    able to connect to it by executing 'minicom -w' or if you prefer a windows host
    you can set up Tera Term as explained in the Software Developer's Guide.
    If you connect minicom or Tera Term and power cycle the board Linux will boot.

    It will open minicom terminal. And at this point Power ON the EVM. You will see some activity on your minicom terminal (it will basically program all the right u-boot environment settings).

    4) After programming the env's the script will automatically kill the minicom.  And from here on,  just type minicom on your host PC and restart the EVM, everything should be ready now. 

    NOTE: SD card need to be left connected on EVM until you follow the optional steps from SDG to  copy boot loader in NAND. And once you copy the bootloader in NAND then you can remove the SD card from your EVM.

    Optional:

    While setting the kernel bootargs and u-boot bootcmd environment varaible script needs to know your host IP address and if your host IP address changed then you have to re-program those environment varaibles.  I would recommend to get a static IP address for your development host PC to save time and error during re-programming.  Otherwise you have two options:

       a)  Modify IP address hardcoded in setup_uimage-tftp_nfs.minicom (this is minicom configuration file) with your new IP address and then

              i) Power OFF the board

              ii)  run "minicom -S setup_uimage-tftp_nfs.minicom "

              iii) Power ON the board

            This will re-program the updated serverip address.

         or

        b) Run ./bin/setup-uboot-env.sh script. This will autodetect your IP address etc and re-generate updated "setup_uimage-tftp_nfs.minicom" and then follow the above steps to re-program new envs.

     

    Hope this helps.

    Thanks

    Brijesh

     

  • Brjesh,

    I would point out that apparently some critical items/steps are not mentioned in my version of the documentation... specifically:

    1. the SD card should be put back in the EVM after installing the SDK but before allowing the setup script to start minicom

    2. the scripts expect the host to have a static IP.

    3. apparently the EVM will boot up looking for a dhcp server for its own IP address

     

    Thanks for your help. I changed to a static IP, allowed the EVM to find my DHCP server by putting the EVM on a switch and a more-accessible network, and everything is working now based on your explanation.

    -JEG