• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 99 subscribers
  • Views 1056 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.

FTDI USB Serial driver for C6747

Bogdan15639
Intellectual 350 points
Other Parts Discussed in Thread: OMAP-L137, OMAP-L138

Dear community,

is there a driver available  for the USB to serial chip from FTDI (FTDI2232d), which makes the USB appear as a serial port?

Many thanks in advance. Bogdan

  • 0
    TI__Expert 7435 points

    You can use the standad FTDI drivers that are available in the Linux Kernel that ships with C67xx platform.  On the other hand if you are refering to BIOSUSB then we do not package such drivers.  You would have to get the driver from the vendor and compile it for C67xx platform and interface them to the BIOSUSB stack.  Pl. note that such products are not supported in the BIOSUSB stack as of today.

    regards

    swami

  • 0 in reply to swami
    Intellectual 350 points

    Dear swami,

    It seems that the best solution is to install the MontaVista Linux that comes with C6747 EVM.

    Many thanks for your response!

  • 0 in reply to Bogdan15639
    TI__Expert 7435 points

    Bogdan,

    Pl. refer to the Aarago GIT releases that accompany OMAPL13xx platform.  These release should support both L137 and L138.  These releases are on top of the latest community davinci tree and are pretty well tested by TI.

    regards

    swami

  • 0 in reply to swami
    Prodigy 30 points

    Dear swami,

    I would like to install the Aarago GIT as you recommended but I cannot find any documentation on how to do this. I have found this:

    http://arago-project.org/files/releases/2009.11-rc1/images/da830-omapl137-evm/

    Should I follow the getting started guide using for the DaVinci GIT based SDK?

    http://wiki.davincidsp.com/index.php/Getting_Started_Guide_for_OMAP-L137

    I would appreciate it very much if you could give me step-by-step info to install the Arago GIT.

  • 0 in reply to Prodan
    TI__Expert 7435 points

    Hi,

    You would have to do the following to enable the FTDI support in the kernel.  Using menuconfig pl. follow the below path (enabling the selection if not already selected)

    Device Drivers --> USB support --> USB Serial Converter Support --> USB Serial Console device support

                                                                                                                           ---> USB FTDI Single Port Serial Driver

    Ensure that you have selected the above options as part of the kernel and compile the kernel.  Once you have done this you should be able to talk to the FTDI device over USB.

    regards

    swami

  • 0 in reply to Prodan
    TI__Expert 6385 points

    Hello,

    OMAP-L137 USB support is available from the GIT tree here: http://arago-project.org/git/people/?p=sekhar/linux-omapl1.git;a=summary

    You need to have 'git' installed on your host to fetch and track this tree.

    However, if you just want to checkout the sources once, you can use the snapshot feature of gitweb URL above. Click on the 'tree' link on the top of the page, then click 'snapshot' on the page that appears. Here is the direct link for your convenience: http://arago-project.org/git/people/?p=sekhar/linux-omapl1.git;a=snapshot;h=HEAD;sf=tgz

    Information on using this kernel is available here: http://wiki.davincidsp.com/index.php/Community_Linux_PSP_for_OMAP-L1. Specifically, information on re-building this kernel is available here: http://wiki.davincidsp.com/index.php/GSG:_Building_Software_Components_for_OMAP-L1xx#Rebuilding_the_Linux_kernel

    The page is still being constructed for OMAP-L137; do point out any issues you see. This is an open wiki so do feel free to contribute as well!

    Thanks,

    Sekhar

  • 0 in reply to swami
    Prodigy 30 points

    Hi,

    I installed  the Montavista 5 (kernel version 2.6.18) and it is running good. I tried to insert the FTDI Single Port Serial Driver as above but the option "USB Serial Console Device support" does not appear under "USB Serial Converter Support" inside menuconfig.

    I have the source files of the FTDI for linux...is there any way to include it in the Montavista kernel?

    But I guess you said to do this using the Arago GIT, no?

  • 0 in reply to Prodan
    TI__Expert 7435 points

    Yes I mentioned in the context of Aarago Git kernel.

    regards

    swami

  • 0 in reply to Sekhar Nori
    Intellectual 350 points

    Dear Sekhar and dear swami,

    Many thanks for your replies!  I followed your links and info and I have build the kernel. I have two questions though:

    1. in the /arch/arm/boot there is no uImage file as written in the link below ; just zImage, Image and a makefile. How can I obtain the uImage?

    http://wiki.davincidsp.com/index.php/GSG:_Building_Software_Components_for_OMAP-L1xx#Rebuilding_the_Linux_kernel

    2. I could not find any documentation on how to export the Arago NFS. In the link below a file called "/fs/nfs.tar.gz" is mentioned but in the /linux-omapl1/fs there are just source files. Could you please give some guidance also here?

    http://wiki.davincidsp.com/index.php/GSG:_Setting_up_OMAP-L138_Target_File_System

    I am using the OMAPL137-EVM but the links always point to OMAP-L138, which is (at least in the beginnig) very confusing.

     

     

     

     

  • 0 in reply to Bogdan15639
    TI__Expert 6385 points

    Hello Bogdan,

    Bogdan said:

    1. in the /arch/arm/boot there is no uImage file as written in the link below ; just zImage, Image and a makefile. How can I obtain the uImage?

    uImage should be obtained after 'make uImage' completes. Look for an error of the sort 'mkimage not found' in the build logs toward the end of the build process. If you see that, please make sure you have followed step #2 of the build process correctly. Quoting it here:

    "

    If U-Boot is not built yet, build U-Boot first, as building Linux Kernel requires mkimage utility, which gets built along with U-Boot. Refer to Rebuilding U-Boot for steps to build U-Boot. mkimage will be present under the tools folder of U-Boot source (/home/<user>/OMAP_L138_arm_x_xx_xx_xx/DaVinci-PSP-SDK-xx.xx.xx.xx/src/u-boot/uboot-xx.xx.xx.xx/tools). Ensure that this path is added to the $PATH variable by adding the following PATH=home/<user>/OMAP_L138_arm_x_xx_xx_xx/DaVinci-PSP-SDK-xx.xx.xx.xx/src/u-boot/uboot-xx.xx.xx.xx/tools:$PATH to the ~/.bashrc file. You can then source the ~/.bashrc file with the following command

    "

    Bogdan said:

    2. I could not find any documentation on how to export the Arago NFS. In the link below a file called "/fs/nfs.tar.gz" is mentioned but in the /linux-omapl1/fs there are just source files. Could you please give some guidance also here?

    http://wiki.davincidsp.com/index.php/GSG:_Setting_up_OMAP-L138_Target_File_System

    The nfs.tar.gz is present in DaVinci-PSP-SDK-03.#.#.#/images/fs/nfs.tar.gz inside the PSP package. The gitweb link I gave in the previous post was to the Linux kernel only - not the entire PSP package. The PSP package (which also includes a snapshot of the kernel) is available at: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/psp/DaVinci-PSP-SDK/03_20/index_FDS.html. You can use the latest available 03.20.00.06 version. Note that the kernel snapshot in this package is older than the one you downloaded yesterday from Arago website. Periodically, TI completes testing on a kernel snapshot available on arago website and uploads it as a complete package (along with filesystem, boot utils etc) and uploads it to the public download site above.

    Bogdan said:

    I am using the OMAPL137-EVM but the links always point to OMAP-L138, which is (at least in the beginnig) very confusing.

    Yes, we are in the process of fixing up the documentation to include OMAP-L137 references (or use generic OMAP-L1 naming). The way things turned out, community Linux PSP on OMAP-L138 got commissioned before OMAP-L137.

    Thanks,

    Sekhar

  • 0 in reply to Sekhar Nori
    Prodigy 30 points

    Dear Sekhar,

    I followed your hints and now the Arago Linux kernel boots with the drivers that I need. Many thanks again to you and swami for the help! Below is some feedback:

    1) Although I built the kernel with make da830_omapl137_defconfig, when the kernel boots I got the prompt  "root@da850-omapl138-evm", which should be "root@da830-omapl137-evm".

    2) There were two error messages while booting:

    --------------------------------------------------------------------------------

    Remounting root file system...                                                                                                                              

    modprobe: FATAL: Could not open 'kernel/fs/minix/minix.ko': No such file or directory

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

    root: mount: mounting usbfs on /proc/bus/usb failed: No such file or directory

    ....

    Starting syslogd/klogd: modprobe: FATAL: Could not open 'kernel/net/ipv6/ipv6.ko': No such file or directory

    done                                                                                                                                                       
    Starting thttpd.

    ---Arago Project Logo---

    ---------------------------------------------------------------------------------

    I searched for the two files mentioned in the errors and they are installed in:

    /home/<useraccnt>/workdir/filesys_arago/lib/modules/2.6.32-rc6/kernel/fs/minix

    /home/<useraccnt>/workdir/filesys_arago/lib/modules/2.6.32-rc6/kernel/net/ipv6

    The files I tried rebuilding the kernel and reinstalling the modules but this did not help. Then, I removed the two modules from the kernel and now I do not get the two modprobe errors.