                Troubleshooting Tips for HTI USB


1.  Insure that the HTI processor revision supports USB.

    In order to use the HTI with USB, the mask revision for the processor
    MUST BE 0K44M; this number is stamped onto the BGA package on the HTI
    main board.  Generally, if the silkscreen on the HTI case says
    "CodeWarrior HTI" then it is very likely that the silicon inside is 0K44M.
    If the silkscreen says "Panther" or something else entirely, there is
    a good chance that the silicon is an older rev (e.g. 0K24A) which will
    not work reliably with USB.

2.  Insure that the Windows-side Jungo drivers are loaded and active.

    Run msinfo32 (Start/Run.../msinfo32) and check under Software Environment/
    System Drivers.  There should be an entry for windriver6.  The driver
    should be started and running, with status OK.

3.  Insure that the Windows-side Jungo drivers are the correct version.

    In the CCS console window, enter the command "show wdv".  The output should
    be something like:

        WinDriver v7.00 Jungo (c) 1997 - 2005

    The version number must be 7.00.

4.  Insure that the HTI executable image file is downloaded properly.

    Reboot the HTI.  In the CCS console window, enter the following set of
    commands:

        delete all
        config cc usb
        show cc

    After a few seconds, CCS should display the following in the console window:

        Sending code to HTI - please wait

    If an error appears instead, then either the HTI executable image file is
    missing or the HTI loader code in flash is corrupt.

5.  Insure that the HTI executable image file is valid.

    After the download completes, CCS should display something like the following
    in the console window:

        0: USB CC software ver. {1.7}

    If instead CCS displays a "USB open failure" message, then either:
        a. The executable image file is bad and must be replaced.  The image file 
           is named nhti.mot, and within the distribution hierarchy it resides in ccs/bin.
        b. The firmware image on the HTI is bad and must be replaced.  You can update
           the firmware using the "updatenhti" command.  However, this may fail if the
           firmware is already bad.  You can try connecting to the HTI from another host
           machine and updating the firmware from there.  If this does not work, you may
           need to return the HTI for factory re-programming.

6. To reinstall the driver, search your CodeWarrior installation for the file HTIWD6.inf.
   In the same folder, there should be a file named setup.bat.  Run setup.bat from that
   folder.  The HTI should be connected to the USB port when you re-install the driver.
   If you have any USB TAPs, please disconnect them while installing this driver.
