• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Digital Signal Processors (DSP) » C6000 Multicore DSP » C64x Multicore DSP Forum » I can not build MIDAS_Ultrasound_v3.0_Demo. Please show me solution.
Share
C6000 Multicore DSP
  • Forums
  • Announcements
Options
  • Subscribe via RSS
Training Available
TI provides self-paced online training that introduces the primary components of the KeyStone II family of SoC devices.

  • KeyStone II SoC Overview >
  • KeyStone II Software Overview >
  • KeyStone II ARM Cortex-A15 Corepac Overview >
  • More Information >
  • Check out
    Multicore Mix blog
    • $core_v2_blog.Current.Name

      It’s our second anniversary, but you get the present!

      Posted 6 days ago
      by Lindsey Bare
      It’s hard to believe it’s already been two years...
    • $core_v2_blog.Current.Name

      Limited time offer: Save $100 on Keystone-based EVM!

      Posted 19 days ago
      by tscheck
      Have you been thinking about ordering a TI Keystone-based EVM...
    • $core_v2_blog.Current.Name

      Imagine the impact…TI’s KeyStone SoC + HP Moonshot

      Posted 30 days ago
      by Sanjay35057
      Last week, market leader Hewlett Packard announced a huge change...

    I can not build MIDAS_Ultrasound_v3.0_Demo. Please show me solution.

    I can not build MIDAS_Ultrasound_v3.0_Demo. Please show me solution.

    This question is answered
    masatoshi nakashima
    Posted by masatoshi nakashima
    on Nov 07 2011 00:32 AM
    Intellectual380 points

    I can not build MIDAS_Ultrasound_v3.0_Demo. I read "Software Setup , A Multicore DSP(Mid End)".

    First , "TI Software Components Setup c  Codec Engine 3.20.01.18"  is gone.

    So, I downloaded 3.21.00.19 instead. and changed  common_xdcpaths.mak file like below

     

    ********

    XDC_INSTALL_DIR := $(TI_INSTALL_DIR)/xdctools_3_20_06_81

    CE_INSTALL_DIR   := $(TI_INSTALL_DIR)/codec_engine_3_21_00_19

    FC_INSTALL_DIR      := $(TI_INSTALL_DIR)/framework_components_3_21_01_26

    BIOS_INSTALL_DIR    := $(TI_INSTALL_DIR)/bios_6_30_02_42

    # IQMATH_LIB_DIR      := $(TI_INSTALL_DIR)/IQmath_v213/lib

    IPC_INSTALL_DIR     := $(TI_INSTALL_DIR)/ipc_1_22_04_25

    OSAL_INSTALL_DIR    := $(FC_INSTALL_DIR)/fctools

    # IPC_INSTALL_DIR     := $(FC_INSTALL_DIR)/fctools

    # XDAIS_INSTALL_DIR   := $(FC_INSTALL_DIR)/fctools

    XDAIS_INSTALL_DIR   := $(TI_INSTALL_DIR)/xdais_7_21_01_07

    NDK_INSTALL_DIR := $(TI_INSTALL_DIR)/ndk_2_20_02_22    # new!!

    **************

    I can not understand OSAL, and can not understand original  common_xdcpaths.mak file.

     

     

     

    When I ran build6472.pl,  tool has complained  like below:

    ***********************************************

     configuring midendapp.p64P from package/cfg/midendapp_p64P.cfg ...

      js: "E:/midas_usound_demo3_rel/miDAS/ultrasound/demo3/midend/midendapp/midendapp

     .cfg", line 263: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: E:\Pro

     gram Files\Texas Instruments\framework_components_3_21_01_26\packages\ti\sdo\fc\

     ires\edma3chan\package.xdc found along the package path, but no schema file was

     found.  Ensure that the package 'ti.sdo.fc.ires.edma3chan' is completely built.

        "./package/cfg/midendapp_p64P.cfg", line 744

        "./package/cfg/midendapp_p64P.cfg", line 799

        "./package/cfg/midendapp_p64P.cfg", line 731

    gmake.exe: *** [package/cfg/midendapp_p64P.xdl] Error 1

     

    ****************************************************

     Please show me how to build demo3.

    Thank you.

     

     

     

     

    EVM6474 example code
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    All Replies
    • Uday
      Posted by Uday
      on Nov 07 2011 17:24 PM
      Expert3720 points

      Hello Masatoshi Nakashima

      CE 3.20.01.18 is available at http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ce/3_20_01_18/index_FDS.html

      Could you please try with this and tell us if it resolves the issue you are observing. 

      Thanks,
      Uday

       

      - Uday

      --- If you need more help, please reply. If this answers your question, please Verify Answer below this post ---

      midas demo 3.0 edma3 codec engine
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • masatoshi nakashima
      Posted by masatoshi nakashima
      on Nov 07 2011 17:59 PM
      Intellectual380 points

      I  am afraid that my question dose not understand.  

      Is correct  the content of original common_xdcpaths.mak  ?

      Please explain "OSAL_INSTALL_DIR    := $(FC_INSTALL_DIR)/fctools".

      what OSAL is?

      Please explain "IPC_INSTALL_DIR     := $(FC_INSTALL_DIR)/fctools".

      Why it doesn't point IPC's directory with version name, like ipc_1_22_04_25.

      Please explain why NDK_INSTALL_DIR line  doesn't exist.

       

      But , Thanks for codec engine URL.

      Please show me.

      Thank you.

      C6474
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • masatoshi nakashima
      Posted by masatoshi nakashima
      on Nov 07 2011 22:31 PM
      Intellectual380 points

      I have tried this version. But it did not resolve this issue.

      Please read my question,again.      Thank you

      C6472 EVM
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Uday
      Posted by Uday
      on Nov 08 2011 17:36 PM
      Expert3720 points

       

      I notice now that you have also used a different version of Framework Components and BIOS from the one that this v3.0 demo has been released with. Looks like you are using FC 3.21.01.26, whereas demo states to use FC 3.20.01.26. From your .mak it also looks like you are using BIOS 6.30.02.42, whereas demo states to use BIOS 6.30.03.46.

      Please verify and install exactly the same software components that the demo wiki page has listed. Also, please use the original common_xdcpaths.mak that was included in the release package with 1 change for IQMath. I do see that IQ Math 2.13 is no longer available, so you can use IQ Math 2.14. The wiki points to the new version, and I've pasted it here for your convenience:http://www.ti.com/tool/sprc542

      So common_xdcpaths.mak should look as follows:

      XDC_INSTALL_DIR := $(TI_INSTALL_DIR)/xdctools_3_20_06_81
      CE_INSTALL_DIR   := $(TI_INSTALL_DIR)/codec_engine_3_20_01_18
      FC_INSTALL_DIR      := $(TI_INSTALL_DIR)/framework_components_3_20_01_26
      BIOS_INSTALL_DIR    := $(TI_INSTALL_DIR)/bios_6_30_03_46
      IQMATH_LIB_DIR      := $(TI_INSTALL_DIR)/c64xplus-iqmath_2_01_04_00/lib
      OSAL_INSTALL_DIR    := $(FC_INSTALL_DIR)/fctools
      IPC_INSTALL_DIR     := $(FC_INSTALL_DIR)/fctools
      XDAIS_INSTALL_DIR   := $(FC_INSTALL_DIR)/fctools

      To answer your question on OSAL, it stands for Operating System Abstraction Layer. It is included within the FC install directory. 

      Please let us know what you see after incorporating the above suggestions. Thanks.

       

      - Uday

      --- If you need more help, please reply. If this answers your question, please Verify Answer below this post ---

      midas fc
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • masatoshi nakashima
      Posted by masatoshi nakashima
      on Nov 08 2011 20:40 PM
      Intellectual380 points

      I  changed BIOS version, and tried build Demo3,by your common_xdc_path.

      Errors are occured like below;

      generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...

      configuring midendapp.p64P from package/cfg/midendapp_p64P.cfg ...

      js: "E:/midas_usound_demo3_rel/miDAS/ultrasound/demo3/midend/midendapp/midendapp.cfg", line 263: 

           xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND:

           E:\Program Files\Texas    Instruments\framework_components_3_20_01_26\packages\ti\sdo\fc\ires\edma3chan\package.xdc

          found along the package path, but no schema file was found.  

          Ensure that the package 'ti.sdo.fc.ires.edma3chan' is completely built.

          "./package/cfg/midendapp_p64P.cfg", line 744

          "./package/cfg/midendapp_p64P.cfg", line 799

          "./package/cfg/midendapp_p64P.cfg", line 731

      gmake.exe: *** [package/cfg/midendapp_p64P.xdl] Error 1

      ***********

      In xs command    ( xdctools_3_20_06_81/xs --xdcpath) there is " /package".

      I guess that this may be NDK_INSTALL_DIR/package/

      By my poor knowledge, I can not understand common_xdcpaths.mak.

      Please teach me.

      1.  Why NDK_INSTALL_DIR is not defined.

      2. Why  IQMATH_LIB_DIR  is defined (     := $(TI_INSTALL_DIR)/c64xplus-iqmath_2_01_04_00/lib)

       http://processors.wiki.ti.com/index.php/MIDAS_Ultrasound_v3.0_Demo#A._Multicore_DSP.C2.A0.28Mid_End.29 say 

       "Enviroment variavle IQMATH_LIB_DIR and variable value is C:\ti\c64xplus-iqmath_2_01_04_00"(this case TI_INSTALL_DIR = C:\ti)

        This setting does not have "lib".    and  Why IQMATH_LIB_DIR is different from your recommendation.

      3  Why IPC_INSTALL_DIR  is $(FC_INSTALL_DIR)/fctools?

         In fctools, there is no file related with ipc.  

        And I can not understand IPC directory setting explanation in MIDAS Demo3 page.(    Install as C:\ti\ipc_1_22_04_25)

      4 Why XDAIS_INSTALL_DIR is   := $(FC_INSTALL_DIR)/fctools?

       I can not understand XDAIS directory setting explanation in MIDAS Demo3 page.(   Install as C:\ti\ xdctools_3_20_06_81)

       

      Please try build Demo3 according to  http://processors.wiki.ti.com/index.php/MIDAS_Ultrasound_v3.0_Demo#A._Multicore_DSP.C2.A0.28Mid_End.29.

      and answer my poor questions.

      Thank you.

      C6472 EVM MIDAS Demo3
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • masatoshi nakashima
      Posted by masatoshi nakashima
      on Nov 09 2011 03:33 AM
      Intellectual380 points

      Sorry,  I found  packages\ti\ipc   packages\ti\sdo  packages\ti\xdais  in  $(FC_INSTALL_DIR)/fctools .

      But I can not understand  relationship between packages\xdais_7_21_01_07 and ti/xdais , yet.

      Also, I can not understand there is not NDK_INSTALL_DIR setting in common_xdcpaths.mak.

      Error does not disappear.

      xdc.PACKAGE_NOT_FOUND:

      ti\sdo\fc\ires\edma3chan\package.xdc found along the package path,

      but no schema file was found.

       Ensure that the package 'ti.sdo.fc.ires.edma3chan' is completely built.

      Thank you.

       

       

       

       

      MIDAS Demo3
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Uday
      Posted by Uday
      on Nov 09 2011 19:12 PM
      Expert3720 points

      Hello Masatoshi,

      I took a new, clean Windows PC, and followed the wiki instructions exactly to see if I can try to recreate the issue you are seeing. I was able to successfully build all the projects using the script and I have attached the buildlog.txt for the same here 3618.buildlog.txt. I did have to do one additional step (after step 4 on wiki) to ensure that all the software components are recognized by CCS. I will add this step to the wiki, but here it is for convenience.

      After Step 4 on wiki: Once all software components and CCS are installed, please start CCS. When CCS is starting, it will ask you to choose a workspace. Select "C:\ti\midas_usound_demo3_rel\release\usound_demo3\ccsv4_workspace." If CCS is starting for the first time, it will also autodiscover the software components installed. Starting CCS before running the perl build script will ensure that all software components are discovered.

      However, before I go ahead with my suggestions, let me address your concerns about the common_xdcpaths.mak file. I remembered when I went through the build procedure on a new PC that the file common_xdcpaths.mak should not affect the CCS projects that you are building using the perl script, viz. serverlib, midendapp, server1, server2, server3, server4, server5. The software components like Codec Engine, Framework Components, etc. that are used to build each project, are specified within the CCS properties of the projects, which is what is stored in .cdtbuild, .ccsproject, .project and .cdtproject, within each project directory. Therefore wrt your questions on common_xdcpaths.mak, I would suggest that at this point you ignore the file, since it is not being used in this build. This file was being used for another purpose (in creating the provided algorithm packages, which is already prebuilt here). As you expressed, I understand that the presence of the common_xdcpaths.mak file can be a source of confusion here.

      Suggestions:

      I believe the error you are seeing might be because all the software components (or the right versions) are not being discovered. I'd appreciate if you could do the following:

      1. Download a fresh zip from https://gforge.ti.com/gf/download/frsrelease/566/4720/midas_usound_demo3_rel.zip

      2. Ensure that all the following software components are installed as indicated in the snapshot below. Please also make sure other versions of these tools are not installed, just in case it tries to pick those versions instead. 


      3. Start CCSv4. Select "C:\ti\midas_usound_demo3_rel\release\usound_demo3\ccsv4_workspace." If CCS is starting for the first time, it will also autodiscover the software components installed. To ensure that it has seen all the required components, please go to Window->Preferences->CCS->RTSC->Products. The snapshot should look similar to below with "C:/ti" listed under "Tool Discovery Path" and all components listed under "Discovered Tools."  

      4. Once you have confirmed the above, run the build script as "perl build6472.pl >> buildloguser.txt". After it finishes building, please send me the file "buildloguser.txt" 

      Once you are done with these, if you are still facing issues, please reply with the following attachments:

      a. Snapshot of C:/ti or whichever the TI_INSTALL_DIR folder is for you (as I have provided above for my system above)
      b. Snapshot of Window->Preferences->CCS->RTSC->Products in CCS (as I have provided for my system above)
      c. The log file buildloguser.txt that will created once you do step 4 above (here's what was generated after I ran it 3618.buildlog.txt)

      Thanks,
      Uday 

      - Uday

      --- If you need more help, please reply. If this answers your question, please Verify Answer below this post ---

      midas demo rtsc
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • masatoshi nakashima
      Posted by masatoshi nakashima
      on Nov 21 2011 04:44 AM
      Intellectual380 points

      7870.builduserlog.txtThank you kind suggestion. I changed my enviroment according to your suggestions.

      But my volume is E:.(not C:)

      Fail point is same. Js complains

      "xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND:

      E:\ti\framework_components_3_20_01_26\packages\ti\sdo\fc\ires\edma3chan\package.xdc found along the package path,

      but no schema file was found.  Ensure that the package 'ti.sdo.fc.ires.edma3chan' is completely built."

      I  attach 2 files. 

      Please look them,and please give me new suggestion.

      Thank you.

      MIDAS Ultrasound demo v3.0
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • masatoshi nakashima
      Posted by masatoshi nakashima
      on Nov 22 2011 00:17 AM
      Intellectual380 points

      Thaks for your suggestion,but in my enviroment  something wrong exists.

      I sent builtuserlog.  I have a question about difference between my log and your success log.

      Fail command line is like below :(not C:  but E:)

      **********

       

      "C:/ti/xdctools_3_20_06_81/xs"

      --xdcpath=

          "C:/ti/bios_6_30_03_46/packages;

           C:/ti/codec_engine_3_20_01_18/packages;

          C:/ti/codec_engine_3_20_01_18/examples;

          C:/ti/framework_components_3_20_01_26/packages;

         C:/ti/framework_components_3_20_01_26/examples;

          C:/ti/midas_usound_demo3_rel;

         C:/ti/midas_usound_demo3_rel/miDAS/ultrasound/demo3/midend/midendapp;

         /packages;

          C:/ti/pdk_c64x_1_00_00_06/packages;

         C:/ti/mcsdk_1_00_00_08/packages;

         C:/ti/ndk_2_20_02_22/packages;

          C:/ti/edma3_lld_02_10_03_04/packages;

          C:/ti/ipc_1_22_04_25/packages;

           C:/ti/framework_components_3_20_01_26/fctools/packages;"

       

       xdc.tools.configuro -o "configPkg" -t ti.targets.C64P -p midend_core0 -r whole_program

      -b "C:/ti/midas_usound_demo3_rel/miDAS/ultrasound/demo3/midend/midendapp/midend_core0/config.bld"

      -c "C:/ti/ccsv4/tools/compiler/c6000" "../midendapp.cfg"

      ************

      In my enviroment , this command line fails. And it print warning like below:
      "Warning: directory "E:/packages" on package path does not exist"
      But  your succesful log , there is no warning line.
      Your command line also include /package word for xdc path.
      Failure is 
      "E:\ti\framework_components_3_20_01_26\packages\ti\sdo\fc\ires\edma3chan\package.xdc found along the package path, but no schema file was found.
       Ensure that the package 'ti.sdo.fc.ires.edma3chan' is completely built."
      I do not know what the schema file is.  But I understand this simple error message. 
      Does your enviroment have the edma3chan package on your C:/  ?
      Please teach the errror message's meanning.  and comfirm TI's  framework_components_3_20_01_26, also.
      Thank you. 

       

      MIDAS Ultrasound Demo3
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Uday
      Posted by Uday
      on Nov 22 2011 03:46 AM
      Verified Answer
      Verified by masatoshi nakashima
      Expert3720 points

      Hello Masatoshi

      Thanks for sharing the screenshots and log. It does look like there is a difference between the contents of the framework_components_3_20_01_26\packages\ti\sdo\fc\ires\edma3chan\package directory between our installations even though it is the same version; I seem to have a few more files, as the screenshot below shows: 

      Since some of these files seem to be missing from your Framework Components installation, I would suggest that you uninstall and reinstall Framework Components 3.20.01.26 and then check this directory again to see if the files are there after the reinstall. Please let me know what you observe.

      -- Uday

       

       

      - Uday

      --- If you need more help, please reply. If this answers your question, please Verify Answer below this post ---

      midas fc
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • masatoshi nakashima
      Posted by masatoshi nakashima
      on Nov 23 2011 02:48 AM
      Intellectual380 points

      Very sorry!  I have succeeded the build accroding to your suggestion.

      Unarchiver that I used have some bug.  I replaced the  unarchiver to another,

      and I got directories that you appointed.

      The failure have disappered. 

      I apologize you.

       

      But I can not understand /package path  in the command line.

      In the Demo3 Wiki,  some links are disappered,like framework component's link.

      Please communicate with development people. " Please maintain  wiki. or revise them.".

      Thank you.

       

       

       

       

      MIDAS Ultrasound Demo3
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Uday
      Posted by Uday
      on Nov 23 2011 03:31 AM
      Verified Answer
      Verified by masatoshi nakashima
      Expert3720 points

      Glad the build is succeeding now, Masatoshi.

      To answer your question, the "/package" that you're seeing refers to a particular 'include path' location that the compiler cannot find. However, it doesn't affect your build, because it is an extraneous include path, which should not have been there in the include options for the project, a minor cleanup that was overlooked.

      Thanks for pointing out the missing weblinks. It looks like some of the TI software component installers were relocated to another web address. I've updated the wiki now to reflect the correct links.

      -- Uday

      - Uday

      --- If you need more help, please reply. If this answers your question, please Verify Answer below this post ---

      midas
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • hyungchul won
      Posted by hyungchul won
      on Apr 27 2012 04:14 AM
      Prodigy215 points

      I try MIDAS v2.0 following web site http://processors.wiki.ti.com/index.php/MIDAS_Ultrasound_v2.0_Demo

      I think that I succeeded compile in everything except touch screen.

      I try Touchscreen Setup follow web site blow.

      Touchscreen Setup

      MIDAS utilizes the tslib library for touchscreen support on the OMAP3530 EVM. This section will guide you through setting up tslib.

             1. Install required packages on host

                         host $ sudo apt-get install autogen autoconf libtool

              2. For cross-compiling, define environment variables in ~/.bashrc on host as:

                           export CC=/home/<username>/arm-2009q1/bin/arm-none-linux-gnueabi-gcc
                           export CXX=/home/<username/arm-2009q1/bin/arm-none-linux-gnueabi-g++
                           export CONFIG_SITE=omap3evm.autogen

              3. Download the source files for tslib from here and save it at ~

               4. Untar the source

                             host $ cd ~host $ tar xjf tslib-1.0.tar.bz2

                 5. Configure tslib

                              host $ cd ~/tslib-1.0
                              host $ ./autogen.sh
                              host $ ./configure --prefix=/home/<username>/workdir/filesys --host=arm-linux-gnu

                 6. Comment the line ‘AC_FUNC_MALLOC’ in ~/tslib-1.0/configure.ac

                 7. Comment ‘#define malloc rpl_malloc’ in ~/tslib-1.0/config.h if it exists

             

                 8. Build and install tslib

                                host $ make
                                host $ make install

       

                   9. Edit ~/workdir/filesys/etc/ts.conf to use linux layer event interface by uncommenting ‘module_raw input’

                   10. Modify the device’s startup script to export the required touchscreen related environment variables.

                        Add these lines to the file ~/development/workdir/filesys/etc/profile:

                                     export QWS_MOUSE_PROTO='Tslib:/dev/input/event1'
                                     export TSLIB_CALIBFILE='/etc/pointercal'
                                     export TSLIB_CONFFILE='/etc/ts.conf'
                                     export TSLIB_CONSOLEDEVICE='none'
                                     export TSLIB_FBDEVICE='/dev/fb0'
                                     export TSLIB_PLUGINDIR='/lib/ts'
                                     export TSLIB_TSDEVICE='/dev/input/event1'

                       11. Remember to run ‘ts_calibrate’ on the target the first time you start the board, to calibrate the touch screen.

      I inputed command ts_calibrate and I get some message blow.

      omap3evm login: root

      root@omap3evm:~# ts_calibrate
      No raw modules loaded.
      ts_config: Success
      root@omap3evm:~#

      root@omap3evm:~# <4>omap-dss: Could not find exact pixel clock. Requested 25188 kHz, got 25187 kHz
      omap-dss: Could not find exact pixel clock. Requested 25188 kHz, got 25187 kHz

      I'm looking for "Could not find exacpt pixel clock" at google and e2e.ti.com.

      I found a TI member as same error message. ( http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/t/94126.aspx )

      But I didn't get enough answer.

      So I try that as indicated.

      First, I input command ls -la /dev/input.

      root@omap3evm:~#

      root@omap3evm:~# ls -la /dev/input/

      drwxr-xr-x 2 root root 100 Jan 1 1970 .

      drwxr-xr-x 10 root root 3060 Sep 11 16:17 ..

      crw-r----- 1 root root 13, 64 Jan 1 1970 event0

      crw-r----- 1 root root 13, 65 Jan 1 1970 event1

      lrwxrwxrwx 1 root root 6 Jan 1 1970 touchscreen0 -> event1

      root@omap3evm:~#

      root@omap3evm:~#

      Second, I input command cat /proc/bus/input/devices

      root@omap3evm:~#

      root@omap3evm:~# cat /proc/bus/input/devices

      I: Bus=0019 Vendor=0001 Product=0001 Version=0003

      N: Name="omap_twl4030keypad"

      P: Phys=omap_twl4030keypad/input0

      S: Sysfs=/class/input/input0

      U: Uniq=

      H: Handlers=kbd event0

      B: EV=100003

      B: KEY=1680 0 70032 53840000

      I: Bus=0000 Vendor=0000 Product=0000 Version=0000

      N: Name="ADS784x Touchscreen"

      P: Phys=spi1.0/input0

      S: Sysfs=/class/input/input1

      U: Uniq=

      H: Handlers=event1

      B: EV=b

      B: KEY=400 0 0 0 0 0 0 0 0 0 0

      B: ABS=1000003

      root@omap3evm:~#

      3th, I input command cat /dev/input/event0 & 1 and touch screen.

      root@omap3evm:~# cat /dev/input/event0


      There is no response when I touched the screen.

      I input command cat /dev/input/event1 & touch screen.

      There is something reactions.

      root@omap3evm:~# cat /dev/input/event1

      }z▒JǗ~z▒J▒J~z▒J▒~z▒Jz▒J▒:z▒Jz▒J▒:

      z▒J▒:z▒J▒z▒Jz▒J▒d

      ▒J▒dz▒J▒dPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTz▒Jz▒J▒▒

      z▒J▒▒z▒J▒z▒J]

      z▒J]z▒Jz▒J>▒z▒J>▒▒ z▒J>▒z▒J>z▒J▒z▒J▒▒ z▒J▒z▒Jz▒J▒9z▒J:▒ z▒Jz▒J▒yz▒J▒yv z▒J▒yz▒J▒z▒J▒▒z▒JΚh z▒JΚz▒Jz▒J▒▒z▒J▒▒> z▒J▒z▒Jz▒J6m z▒J6z▒Jz▒Jgz▒Jz▒Jgz▒Jz▒J▒

      z▒J▒

      z▒J▒

      z▒J▒

      z▒J▒▒ z▒J▒▒ z▒J▒▒ z▒J▒▒ z▒J▒ z▒J▒ z▒J/▒

      4th, I input command ls -la /lib/ts

      root@omap3evm:~#

      root@omap3evm:~# ls -la /lib/ts/

      drwxr-xr-x 2 1000 1000 4096 Apr 27 2012 .

      drwxr-xr-x 6 1000 root 4096 Apr 27 2012 ..

      -rwxr-xr-x 1 1000 1000 944 Apr 27 2012 arctic2.la

      -rwxr-xr-x 1 1000 1000 5631 Apr 27 2012 arctic2.so

      -rwxr-xr-x 1 1000 1000 938 Apr 27 2012 collie.la

      -rwxr-xr-x 1 1000 1000 10498 Apr 27 2012 collie.so

      -rwxr-xr-x 1 1000 1000 932 Apr 27 2012 corgi.la

      -rwxr-xr-x 1 1000 1000 5597 Apr 27 2012 corgi.so

      -rwxr-xr-x 1 1000 1000 950 Apr 27 2012 dejitter.la

      -rwxr-xr-x 1 1000 1000 6658 Apr 27 2012 dejitter.so

      -rwxr-xr-x 1 1000 1000 932 Apr 27 2012 h3600.la

      -rwxr-xr-x 1 1000 1000 5625 Apr 27 2012 h3600.so

      -rwxr-xr-x 1 1000 1000 932 Apr 27 2012 input.la

      -rwxr-xr-x 1 1000 1000 7163 Apr 27 2012 input.so

      -rwxr-xr-x 1 1000 1000 938 Apr 27 2012 linear.la

      -rwxr-xr-x 1 1000 1000 8810 Apr 27 2012 linear.so

      -rwxr-xr-x 1 1000 1000 974 Apr 27 2012 linear_h2200.la

      -rwxr-xr-x 1 1000 1000 6368 Apr 27 2012 linear_h2200.so

      -rwxr-xr-x 1 1000 1000 932 Apr 27 2012 mk712.la

      -rwxr-xr-x 1 1000 1000 5629 Apr 27 2012 mk712.so

      -rwxr-xr-x 1 1000 1000 938 Apr 27 2012 pthres.la

      -rwxr-xr-x 1 1000 1000 6479 Apr 27 2012 pthres.so

      -rwxr-xr-x 1 1000 1000 944 Apr 27 2012 ucb1x00.la

      -rwxr-xr-x 1 1000 1000 5535 Apr 27 2012 ucb1x00.so

      -rwxr-xr-x 1 1000 1000 950 Apr 27 2012 variance.la

      -rwxr-xr-x 1 1000 1000 6545 Apr 27 2012 variance.so

      root@omap3evm:~#

      5th, I input command cat /etc/ts.conf


      root@omap3evm:~#

      root@omap3evm:~# cat /etc/ts.conf

      # Uncomment if you wish to use the linux input layer event interface

      # module_raw input

      # Uncomment if you're using a Sharp Zaurus SL-5500/SL-5000d

      # module_raw collie

      # Uncomment if you're using a Sharp Zaurus SL-C700/C750/C760/C860

      # module_raw corgi

      # Uncomment if you're using a device with a UCB1200/1300/1400 TS interface

      # module_raw ucb1x00

      # Uncomment if you're using an HP iPaq h3600 or similar

      # module_raw h3600

      # Uncomment if you're using a Hitachi Webpad

      # module_raw mk712

      # Uncomment if you're using an IBM Arctic II

      # module_raw arctic2

      module pthres pmin=1

      module variance delta=30

      module dejitter delta=100

      module linear

      root@omap3evm:~#


      What is the problem?

      Please tell me the solution.

      Additional noted items.

      root@omap3evm:~# dmesg
      Linux version 2.6.29-rc3-omap1 (won@ubuntu) (gcc version 4.2.3 (Sourcery G++ Lite 2008q1-126)) #6 Thu Apr 26 19:45:05 KST 2012

      CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f

      CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

      Machine: OMAP3 EVM

      Memory policy: ECC disabled, Data cache writeback

      On node 0 totalpages: 58112

      free_area_init_node: node 0, pgdat c0440c24, node_mem_map c0465000

      Normal zone: 512 pages used for memmap

      Normal zone: 0 pages reserved

      Normal zone: 57600 pages, LIFO batch:15

      OMAP3530 ES3.1 (full speed SGX, IVA2)

      SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000

      Built 1 zonelists in Zone order, mobility grouping on. Total pages: 57600

      Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.1.100:/home/won/workdir/filesys,nolock mem=99M@0x80000000 mem=128M@0x88000000 mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y

      Clocking rate (Crystal/DPLL/MPU core): 26.0/332/500 MHz

      IVA2 clocking rate: 360 MHz

      Reprogramming SDRC

      GPMC revision 5.0

      IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts

      Total of 96 interrupts on 1 active controller

      OMAP34xx GPIO hardware version 2.5

      PID hash table entries: 1024 (order: 10, 4096 bytes)

      OMAP clockevent source: GPTIMER1 at 32768 Hz

      Console: colour dummy device 80x30

      Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

      Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

      Memory: 99MB 128MB = 227MB total

      Memory: 225664KB available (3928K code, 370K data, 156K init)

      Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)

      Mount-cache hash table entries: 512

      CPU: Testing write buffer coherency: ok

      net_namespace: 520 bytes

      NET: Registered protocol family 16

      MUX: setup AF26_34XX_GPIO0 (0xd80021e0): 0x011c -> 0x0118

      MUX: setup L8_34XX_GPIO63 (0xd80020ce): 0x0118 -> 0x0004

      MUX: setup AF9_34XX_GPIO22 (0xd80025ec): 0x0100 -> 0x011c

      MUX: setup U3_34XX_GPIO61 (0xd80020c8): 0x0118 -> 0x011c

      MUX: setup AH14_34XX_GPIO21 (0xd80025ea): 0x0100 -> 0x011c

      MUX: setup AA10_3430_USB2HS_PHY_STP (0xd80025f2): 0x0100 -> 0x0003

      MUX: setup AA8_3430_USB2HS_PHY_CLK (0xd80025f0): 0x0100 -> 0x0003

      MUX: setup AA9_3430_USB2HS_PHY_DIR (0xd80025f4): 0x0100 -> 0x010b

      MUX: setup AB11_3430_USB2HS_PHY_NXT (0xd80025f6): 0x0100 -> 0x010b

      MUX: setup AB10_3430_USB2HS_PHY_D0 (0xd80025f8): 0x0100 -> 0x010b

      MUX: setup AB9_3430_USB2HS_PHY_D1 (0xd80025fa): 0x0100 -> 0x010b

      MUX: setup W3_3430_USB2HS_PHY_D2 (0xd80021d4): 0x0108 -> 0x010b

      MUX: setup T4_3430_USB2HS_PHY_D3 (0xd80021de): 0x0108 -> 0x010b

      MUX: setup T3_3430_USB2HS_PHY_D4 (0xd80021d8): 0x0100 -> 0x010b

      MUX: setup R3_3430_USB2HS_PHY_D5 (0xd80021da): 0x0100 -> 0x010b

      MUX: setup R4_3430_USB2HS_PHY_D6 (0xd80021dc): 0x0108 -> 0x010b

      MUX: setup T2_3430_USB2HS_PHY_D7 (0xd80021d6): 0x0100 -> 0x010b

      twl4030: client 1 is not initialized

      twl4030: client 1 is not initialized

      MUX: setup AA21_34XX_GPIO157 (0xd800218e): 0x0018 -> 0x011c

      MUX: setup C23_34XX_GPIO98 (0xd8002114): 0x0004 -> 0x011c

      omap3evmdc: Driver registration complete

      Switched to new clocking rate (Crystal/Core/MPU): 26.0/332/600 MHz

      IVA2 clocking rate: 430 MHz

      Calibrating delay loop... 597.64 BogoMIPS (lpj=2334720)

      OMAP DMA hardware revision 4.0

      USB: No board-specific platform config found

      OMAP DSS rev 2.0

      OMAP DISPC rev 3.0

      OMAP VENC rev 2

      OMAP DSI rev 1.0

      bio: create slab <bio-0> at 0

      i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz

      twl4030: PIH (irq 7) chaining IRQs 368..375

      twl4030: power (irq 373) chaining IRQs 376..383

      twl4030: gpio (irq 368) chaining IRQs 384..401

      i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz

      i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz

      SCSI subsystem initialized

      usbcore: registered new interface driver usbfs

      usbcore: registered new interface driver hub

      usbcore: registered new device driver usb

      musb_hdrc: version 6.0, musb-dma, host, debug=0

      HS USB OTG: revision 0x33, sysconfig 0x2011, sysstatus 0x1, intrfsel 0x1, simenable 0x0

      musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine (X), bulk split (X), HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)

      musb_hdrc: MHDRC RTL version 1.400

      musb_hdrc: setup fifo_mode 4

      musb_hdrc: 29/31 max ep, 16384/16384 memory

      musb_hdrc: hw_ep 0shared, max 64

      musb_hdrc: hw_ep 1tx, max 512

      musb_hdrc: hw_ep 1rx, max 512

      musb_hdrc: hw_ep 2tx, max 512

      musb_hdrc: hw_ep 2rx, max 512

      musb_hdrc: hw_ep 3tx, max 512

      musb_hdrc: hw_ep 3rx, max 512

      musb_hdrc: hw_ep 4tx, max 512

      musb_hdrc: hw_ep 4rx, max 512

      musb_hdrc: hw_ep 5tx, max 512

      musb_hdrc: hw_ep 5rx, max 512

      musb_hdrc: hw_ep 6tx, max 512

      musb_hdrc: hw_ep 6rx, max 512

      musb_hdrc: hw_ep 7tx, max 512

      musb_hdrc: hw_ep 7rx, max 512

      musb_hdrc: hw_ep 8tx, max 512

      musb_hdrc: hw_ep 8rx, max 64

      musb_hdrc: hw_ep 9tx, max 512

      musb_hdrc: hw_ep 9rx, max 64

      musb_hdrc: hw_ep 10tx, max 512

      musb_hdrc: hw_ep 10rx, max 64

      musb_hdrc: hw_ep 11tx, max 256

      musb_hdrc: hw_ep 11rx, max 256

      musb_hdrc: hw_ep 12tx, max 256

      musb_hdrc: hw_ep 12rx, max 256

      musb_hdrc: hw_ep 13tx, max 256

      musb_hdrc: hw_ep 13rx, max 4096

      musb_hdrc: hw_ep 14shared, max 1024

      musb_hdrc: hw_ep 15shared, max 1024

      musb_hdrc: USB Host mode controller at d80ab000 using DMA, IRQ 92

      musb_hdrc musb_hdrc: MUSB HDRC host driver

      musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1

      usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

      usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

      usb usb1: Product: MUSB HDRC host driver

      usb usb1: Manufacturer: Linux 2.6.29-rc3-omap1 musb-hcd

      usb usb1: SerialNumber: musb_hdrc

      usb usb1: configuration #1 chosen from 1 choice

      hub 1-0:1.0: USB hub found

      hub 1-0:1.0: 1 port detected

      Registered /proc/driver/musb_hdrc

      NET: Registered protocol family 2

      Switched to high resolution mode on CPU 0

      IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

      TCP established hash table entries: 8192 (order: 4, 65536 bytes)

      TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

      TCP: Hash tables configured (established 8192 bind 8192)

      TCP reno registered

      NET: Registered protocol family 1

      OMAP35x Linux PSP version 02.01.03.11 (OMAP3EVM)

      NetWinder Floating Point Emulator V0.97 (double precision)

      VFS: Disk quotas dquot_6.5.2

      Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

      JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.

      msgmni has been set to 441

      alg: No test for stdrng (krng)

      io scheduler noop registered

      io scheduler anticipatory registered (default)

      io scheduler deadline registered

      io scheduler cfq registered

      Generic Backlight Driver Initialized.

      Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

      serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654

      console [ttyS0] enabled

      serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654

      serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654

      brd: module loaded

      loop: module loaded

      smsc911x: Driver version 2008-10-21.

      smsc911x-mdio: probed

      eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)

      net eth0: MAC Address: 00:50:c2:7e:98:67

      Linux video capture interface: v2.00

      usbcore: registered new interface driver uvcvideo

      USB Video Class driver (v0.1.0)

      i2c /dev entries driver

      Driver 'sd' needs updating - please use bus_type methods

      omap2-nand driver initializing

      NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)

      Creating 5 MTD partitions on "omap2-nand.0":

      0x000000000000-0x000000080000 : "xloader-nand"

      0x000000080000-0x000000240000 : "uboot-nand"

      0x000000240000-0x000000280000 : "params-nand"

      0x000000280000-0x000000780000 : "linux-nand"

      0x000000780000-0x000010000000 : "jffs2-nand"

      OneNAND driver initializing

      ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

      ehci-omap ehci-omap.0: OMAP-EHCI Host Controller

      ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2

      ehci-omap ehci-omap.0: irq 77, io mem 0x48064800

      ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00

      usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

      usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

      usb usb2: Product: OMAP-EHCI Host Controller

      usb usb2: Manufacturer: Linux 2.6.29-rc3-omap1 ehci_hcd

      usb usb2: SerialNumber: ehci-omap.0

      usb usb2: configuration #1 chosen from 1 choice

      hub 2-0:1.0: USB hub found

      hub 2-0:1.0: 3 ports detected

      Initializing USB Mass Storage driver...

      usbcore: registered new interface driver usb-storage

      USB Mass Storage support registered.

      input: omap_twl4030keypad as /class/input/input0

      ads7846 spi1.0: touchscreen, irq 335

      input: ADS784x Touchscreen as /class/input/input1

      OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec

      cpuidle: using governor ladder

      cpuidle: using governor menu

      usbcore: registered new interface driver usbhid

      usbhid: v2.6:USB HID core driver

      Advanced Linux Sound Architecture Driver Version 1.0.19.

      usbcore: registered new interface driver snd-usb-audio

      No device for DAI twl4030

      No device for DAI twl4030 Voice

      No device for DAI omap-mcbsp-dai-0

      No device for DAI omap-mcbsp-dai-1

      No device for DAI omap-mcbsp-dai-2

      No device for DAI omap-mcbsp-dai-3

      No device for DAI omap-mcbsp-dai-4

      OMAP3 EVM SoC init

      TWL4030 Audio Codec init

      asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok

      ALSA device list:

      #0: omap3evm (twl4030)

      TCP cubic registered

      NET: Registered protocol family 17

      NET: Registered protocol family 15

      RPC: Registered udp transport module.

      RPC: Registered tcp transport module.

      Power Management for TI OMAP3.

      SmartReflex driver initialized

      Disabling unused clock "sr2_fck"

      Disabling unused clock "sr1_fck"

      Disabling unused clock "mcbsp_fck"

      Disabling unused clock "mcbsp_fck"

      Disabling unused clock "mcbsp_fck"

      Disabling unused clock "mcbsp_ick"

      Disabling unused clock "mcbsp_ick"

      Disabling unused clock "mcbsp_ick"

      Disabling unused clock "gpt2_ick"

      Disabling unused clock "gpt3_ick"

      Disabling unused clock "gpt4_ick"

      Disabling unused clock "gpt5_ick"

      Disabling unused clock "gpt6_ick"

      Disabling unused clock "gpt7_ick"

      Disabling unused clock "gpt8_ick"

      Disabling unused clock "gpt9_ick"

      Disabling unused clock "wdt3_ick"

      Disabling unused clock "wdt3_fck"

      Disabling unused clock "gpio2_dbck"

      Disabling unused clock "gpio3_dbck"

      Disabling unused clock "gpio4_dbck"

      Disabling unused clock "gpio5_dbck"

      Disabling unused clock "gpt9_fck"

      Disabling unused clock "gpt8_fck"

      Disabling unused clock "gpt7_fck"

      Disabling unused clock "gpt6_fck"

      Disabling unused clock "gpt5_fck"

      Disabling unused clock "gpt4_fck"

      Disabling unused clock "gpt3_fck"

      Disabling unused clock "gpt2_fck"

      Disabling unused clock "gpt12_ick"

      Disabling unused clock "wdt1_ick"

      Disabling unused clock "wdt2_ick"

      Disabling unused clock "wdt2_fck"

      Disabling unused clock "gpio1_dbck"

      Disabling unused clock "des1_ick"

      Disabling unused clock "sha11_ick"

      Disabling unused clock "rng_ick"

      Disabling unused clock "aes1_ick"

      Disabling unused clock "ssi_ick"

      Disabling unused clock "mailboxes_ick"

      Disabling unused clock "mcbsp_ick"

      Disabling unused clock "mcbsp_ick"

      Disabling unused clock "gpt10_ick"

      Disabling unused clock "gpt11_ick"

      Disabling unused clock "hdq_ick"

      Disabling unused clock "mspro_ick"

      Disabling unused clock "des2_ick"

      Disabling unused clock "sha12_ick"

      Disabling unused clock "aes2_ick"

      Disabling unused clock "icr_ick"

      Disabling unused clock "pka_ick"

      Disabling unused clock "ssi_ssr_fck"

      Disabling unused clock "hdq_fck"

      Disabling unused clock "mcbsp_fck"

      Disabling unused clock "mcbsp_fck"

      Disabling unused clock "mspro_fck"

      Disabling unused clock "gpt11_fck"

      Disabling unused clock "sad2d_ick"

      Disabling unused clock "dpll4_m6x2_ck"

      Disabling unused clock "dpll3_m3x2_ck"

      Disabling unused clock "sys_clkout1"

      VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1

      GPIO-153 autorequested

      omap-dss DISPC error: Requested pixel clock not possible with the current OMAP2_DSS_MIN_FCK_PER_PCK setting. Turning the constraint off.

      omap-dss: Could not find exact pixel clock. Requested 25190 kHz, got 25189 kHz

      Display already enabled

      Display already enabled

      Buffer Size = 3686400

      omap_vout: registered and initialized video device 0 [v4l2]

      Buffer Size = 3686400

      omap_vout: registered and initialized video device 1 [v4l2]

      display->updated

      net eth0: SMSC911x/921x identified at 0xd085c000, IRQ: 336

      Sending DHCP requests .., OK

      IP-Config: Got DHCP answer from 192.168.1.100, my address is 192.168.1.10

      IP-Config: Complete:

      device=eth0, addr=192.168.1.10, mask=255.255.255.0, gw=192.168.1.1,

      host=192.168.1.10, domain=, nis-domain=(none),

      bootserver=192.168.1.100, rootserver=192.168.1.100, rootpath=/home/won/workdir/filesys

      Looking up port of RPC 100003/2 on 192.168.1.100

      Looking up port of RPC 100005/1 on 192.168.1.100

      VFS: Mounted root (nfs filesystem) on device 0:12.

      Freeing init memory: 156K

      udev: starting version 141

      udev: deprecated sysfs layout; update the kernel or disable CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly

      omap-dss: Could not find exact pixel clock. Requested 25189 kHz, got 25188 kHz

      omap-dss: Could not find exact pixel clock. Requested 25188 kHz, got 25187 kHz

      root@omap3evm:~#

      midas ICould not find exact pixel clock not work omap3530 screen touch touchscreen v2.0
      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    TI E2E™ Community
    • Support Forums
    • Blogs
    • Videos
    • Groups
    • Site Support & Feedback
    • Settings
    TI E2E™ Community Groups
    • TI University Program
    • Make the Switch
    • Microcontroller Projects
    • Motor Drive & Control
    Other Communities
    • Deyisupport
    • Designsomething.org
    • beagleboard.org
    • TI on Element 14
    • TI on TechXchangeSM
    Other Technical & Support Resources
    • WEBENCH® Design Center
    • Product Information Centers
    • Technical Documents
    • TI Design Network
    • TI Technical Articles
    • TI Training

    All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

    Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

    Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
    TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

    TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
    embedded processors, along with software, tools and the industry’s largest sales/support staff.

    © Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
    Trademarks | Privacy Policy | Terms of Use