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.

ICE v2.1 blank eeprom issue



Dear Sirs,

since I purchased a ICEv2.1 board I have experienced issues during connection with the embedded usb Jtag randomly; the xds100serial.exe tool reported:

VID/PID    Type            Serial #    Description
0403/6010  blank EEPROM    unknown     no description available

but after a random number of disconnection / reconnection of the ice, switch off/on the device and the pc I could reconnect again.

Today I wasn't able to reconnect at all.

I followed instructions in

http://processors.wiki.ti.com/index.php/Xds100#Q:_How_do_I_reprogram_the_VID.2FPID_EEPROM_if_it_has_not_been_programmed_correctly.3F

I erased the eeprom but I'm not able to program it anymore (error: no device found). Probably the file XDS100_wUART.ept isn't the correct one?

Please I need a procedure for reprogramming the ICE v2.1 eeprom. I found something in the forums but everything is related to Beaglebone, not ICE v2.1.

Thanks.

  • Hi Ettore,

    Is the ICE power supply switched on when you try to reprogram the EEPROM?

  • Hi Biser,

    yes it is.

    I forgot to say that I'm using a VMWare virtual machine with Windows 7 64bit. Maybe this can help.


    Best regards.

  • Hi,

    I tried using MProg with the file XDS100_wUART_FT2232H.ept, for FT2232H chip, and now, when using MProg to program the eeprom I've the error "error reading device"

    Somewhere I found that if MProg has problems I could use FT_prog. I tried but I found that FT_Prog uses a different format (xml instead of epl files). Does anybody have an xml file for ICE v2.1?

    Thanks and Best regards

  • Anthony,

    I tried reprogramming the eeprom, but I had an error. Please see the attached screenshot and the whole log.
    I didn't press continue button.

    // Start of LOG

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.IndexOutOfRangeException: Index was outside the bounds of the array.
       at FT_Prog.FT2232H.DataEEPROM()
       at FT_Prog.FT2232H.ProgramDevice(FTDI d2xx)
       at FT_Prog.ScanDevice.ProgramDevice(FTDevice ft)
       at FT_Prog.programForm.btProgram_Click(Object sender, EventArgs e)
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    ----------------------------------------
    FT_Prog
        Assembly Version: 2.8.2.0
        Win32 Version: 2.8.2.0
        CodeBase: file:///C:/Program%20Files%20(x86)/FTDI/FT_Prog/FT_Prog.exe
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    Microsoft.GeneratedCode
        Assembly Version: 1.0.0.0
        Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    // END of LOG

  • Ettore,

    Have you tried to contact FTDI for help?
    Were they able to give inputs on the error message?

    A.