• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 101 subscribers
  • Views 1987 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Ubuntu host to Omap targetfs

Kevin Judge
Prodigy 120 points
Other Parts Discussed in Thread: DM3730

I have Ubuntu 10.04 LTS running as the host OS and I am working through the TMS320DM3730 Software Developers Guide.  I have compiled the helloWorld application and I copy it into the folder recommended here:

host $ mkdir ${HOME}/targetfs/home/root/dm3730
host $ cp helloworld ${HOME}/targetfs/home/root/dm3730

That works, but when I go to the target to run it I get a file not found error and indeed, the folder (target # /home/root) is empty.  The dm3730 folder is not present nor is the helloWorld file. 

The communication over the serial port to minicom is working well, but I can't seem to access the target file system.  What might be wrong?

Thank you,

Kevin

  • 0
    TI__Guru 65405 points
    Hi Kevin,
    Could you specify which OS and version you are using on the target TMS320DM3730 system, probably DVSDK?
    I suggest you to verify the destination (target system) path before copy the file. You can copy the helloworld program to each one folder on the target where you have full access rights.
    An other way to copy the helloworld is to use a card reader and ten insert the card to the board but this way needs of restarting the target system.

    BR
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    Prodigy 120 points
    on the target, uname -a responds:
    Linux dm37x-evm 2.6.32 #1 Thu Mar 24 20:15:56 CDT 2011 armv7l unknown
    Yes, you have the correct target, it is the Mistral EVM Rev G board (AM/DM37x). And yes, I have installed the DVSDK.
    How would you suggest that I verify the destination (target system) path? I am unclear on how the target system is set up for NFS access and how this is intended to work. The only way I seem to be able to do anything with the target system is via the minicom terminal where I can access the target system like a normal Linux terminal, but outside of that, I don't know how the target system is linked to my host Ubuntu 10.04LTS system
  • 0 in reply to Kevin Judge
    TI__Guru 65405 points
    Hi Kevin,
    After a perusal of the TMS320DM3730 Software Developer's Guide I found the you probably missing an important step. After copping of the helloworld to the described location "${HOME}/targetfs/home/root/dm3730" you must copy the whole content of the targetfs folder to the board flash because the described folder is on the host PC.

    BR
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    Prodigy 120 points
    How do I copy the contents of the targetfs to the boad flash? Do I need to copy it to the SD card? I thought the idea of the NFS was to avoid doing that? Is there a way to copy the targetfs folder to the board flash without writing to the SD card (which does work by they way, but is inconvenient)
  • 0 in reply to Kevin Judge
    TI__Guru 65405 points

    Kevin,

    The most popular and fast way is to copy the helloworld to the SD card.

    Also, you can use a serial console for file transfer. You need to have a serial console connected between the PC and the target board. Then type of the target board console:

    # cat </dev/ttyS0>helloworld

    then type on the PC:

    $ cp helloworld /dev/ttyUSB1

    This commands works on my environment where the serial console on the PC is connected on the USB port via USB to serial adapter and the target board console is connected to UART1. If your configuration is different you can change the /dev/ttyUSB1 and /dev/ttyS0 according your configuration.

    BR

    tsvetolin Shulev

  • 0 in reply to Cvetolin Shulev-XID
    Prodigy 120 points
    Thank you for your responses Tsvetolin,
    It turns out that the NFS wasn't working properly, once I got that sorted out and ran the minicom script that was built during the setup, then I was able to have access to the remote file system and the directions provided in the software developers guide worked as written. Yes, I always had the serial connection working, it was the network connection that was challenged. The issue is resolved. One thing that would be useful to add to the instructions in the user guide is to add to the instructions where is says to run "minicom -w" to "minicom -w -S setup_uimage-tftp_fs-nfs.minicom" To execute the script that is generated that configures NFS.
    Thank you,Kevin