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.

DM368 "Hello World"

Other Parts Discussed in Thread: TMS320DM368

Hi

I followed TMS320DM368 software developers guide step by step. Now I am trying to execute the "Hello World!" application. An executable called helloworld has been generated. I create a directory ${HOME}/targetfs/home/root/dm368, and copied the executable helloworld to this directory. We also add this directory into the exports file, and we then restated the nfs. however, when we logged into the target, and execute /home/root/dm368/helloworld, it corresponded that "-sh:/ /home/root/dm368/helloworld: not found".

FYI, I am using the DM368EVM.

Any help would be appreciated.

Thanks in advance!

  • it seems like the target can't be accessible from /home/root/dm368/helloworld. what should I do? Any suggestion?

  • Are you sure your NFS is working properly? Once you have added some file to your NFS share, you should be able to see it immediately on your target, without the need of restarting.

  • Thanks for your answer. I just know I can boot from NFS. I don't know how to check whether the NFS is working properly. Could you please give  detailed explanation?

    Thanks for your prompt response!

  • boot from nfs means your rootfs is the NFS share on your host machine. If you are familiar with Samba, it's pretty similar concept.

    After your target booted from NFS, on your target, when you list the files, it's actually listing the files of your NFS share. Say your share is /home/user/targetfs, if you run

    echo 'test'>/home/user/targetfs/tmp/test

    on your host, then you should be able to see the content of this file on your target by typing "cat test".

    If it doesn't work, post your /etc/exports

  • The etc/exports is as blew:

    # /etc/exports: the access control list for filesystems which may be exported
    # to NFS clients. See exports(5).
    #
    # Example for NFSv2 and NFSv3:
    # /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
    #
    # Example for NFSv4:
    # /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
    # /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
    #
    /home/zf/dm368/dvsdk/filesystem/dm368rootfs *(rw,nohide,insecure,no_subtree_check,async,no_root_squash)
    /home/zf/dm368/targetfs/home/root/dm368 *(rw,nohide,insecure,no_subtree_check,async,no_root_squash)
    
    

    /home/zf/dm368/dvsdk/filesystem/dm368rootfs This is the u-boot directory

    /home/zf/dm368/targetfs/home/root/dm368  This is the directory of helloworld

  • that's the problem

    "/home/zf/dm368/dvsdk/filesystem/dm368rootfs This is the u-boot directory"

    This is your rootfs for your target. so  you should put your helloworld code under /home/zf/dm368/dvsdk/filesystem/dm368rootfs/root directory

    You don't need the 2nd NFS share entry

  • I see. But what if I create a directory for my own application, can't I add it into the NFS share entry?

  • Thanks very much for your help.

  • Of course you could use multiple shares. But usually your application is part of your files system anyway, so it makes more sense to only use one.

  • Got it. I'm a new beginner! Thanks for your patient.

  • hi,

        My EVM is TMS320DM368 which is bought from TI.I have changed boot :

    setenv nfshost 200.162.162.254

    setenv rootpath /root/targetfs                       

    setenv bootargs mem=60M console=ttyS0,115200n8 noinitrd rw ip=200.162.162.253:255.255.255.0:200.162.162.100 root=/dev/nfs nfsroot=$(nfshost):$(rootpath)video=davincifb:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=4

    After power the EVM,I cannot see the file folder in Linux. Can you help me???

    Thanks in advance....

    fanfan

  • hi,

        I come with the same problem with you.I want the EVM boot from NFS,and I have changed the boot in below:

    setenv nfshost 200.162.162.254

    setenv rootpath /root/targetfs     :this file folder does not put in DVSDK installing directory.Does it OK?

    setenv bootargs mem=60M console=ttyS0,115200n8 noinitrd rw ip=200.162.162.253:255.255.255.0:200.162.162.100 root=/dev/nfs nfsroot=$(nfshost):$(rootpath)video=davincifb:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=4

    saveenv

                   In the end,I cannot see the files from Linux by Source CRT in XP windows.

                   question: Should I change the boot mode to NAND Flash boot ???