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.

[ExDsp c5535] How to deal with emulator error -154 () ?

Hi, folks.

I was using my eZdsp C5535 normally until the usb cable was accidentally unplugged during a debug session.

Now I can't connect to the emulator anymore. I get the following message via dbgjtag.exe

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Jun 14 2011'.
The library build time was '22:23:33'.
The library package version is '5.0.429.0'.
The library component version is '35.34.29.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will now attempt to reset the controller.

A error occurred while attempting to reset the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver.

The value is '-154' (0xffffff66).
The title is 'SC_ERR_POD_TBC_WRITE'.

The explanation is:
This utility failed to use the adapter for a custom
emulator to perform a write to a controller register.
The adapter returned an error.


And if tried with CCS, the following message shows on the console output:

C55xx: Error connecting to the target: (Error -1041 @ 0xFFFFFF66) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Release 5.0.429.0) 


Anyone has a clue on how to proceed? Did I brick my emulator or can I reset it?


Thanks in advance

  • Well, a simple CCS restart solved the issued. Weird enough.

  • Hi,

    Have not heard of this happening.

    Verify you are using the larger USB connector (J2) to connect XDS100 to the PC.

    You can try the troubleshooting section on the XDS100 wiki: http://processors.wiki.ti.com/index.php/XDS100#Troubleshooting

    Spectrum Digital also provides the Emulator EEPROM contents (EPT file) for use with the FTDI FT_PROG tool (chip for XDS100): http://www.ftdichip.com/Support/Utilities.htm#FT_Prog

    I've also attached the "template" file that the FT Prog tool accepts.

    <?xml version="1.0" encoding="utf-16"?>
    <FT_EEPROM>
      <Chip_Details>
        <Type>FT2232H</Type>
      </Chip_Details>
      <USB_Device_Descriptor>
        <VID_PID>1</VID_PID>
        <idVendor>0403</idVendor>
        <idProduct>A6D0</idProduct>
        <bcdUSB>USB 2.0</bcdUSB>
      </USB_Device_Descriptor>
      <USB_Config_Descriptor>
        <bmAttributes>
          <RemoteWakeupEnabled>false</RemoteWakeupEnabled>
          <SelfPowered>false</SelfPowered>
          <BusPowered>true</BusPowered>
        </bmAttributes>
        <IOpullDown>true</IOpullDown>
        <MaxPower>400</MaxPower>
      </USB_Config_Descriptor>
      <USB_String_Descriptors>
        <Manufacturer>SD</Manufacturer>
        <Product_Description>Texas Instruments Inc.XDS100 Ver 2.0</Product_Description>
        <SerialNumber_Enabled>true</SerialNumber_Enabled>
        <SerialNumber />
        <SerialNumberPrefix>SD</SerialNumberPrefix>
        <SerialNumber_AutoGenerate>true</SerialNumber_AutoGenerate>
      </USB_String_Descriptors>
      <Hardware_Specific>
        <Suspend_DBUS7>false</Suspend_DBUS7>
        <TPRDRV>0</TPRDRV>
        <Port_A>
          <Hardware>
            <UART>true</UART>
            <_245FIFO>false</_245FIFO>
            <CPUFIFO>false</CPUFIFO>
            <OPTO>false</OPTO>
          </Hardware>
          <Driver>
            <VCP>false</VCP>
            <D2XX>true</D2XX>
          </Driver>
        </Port_A>
        <Port_B>
          <Hardware>
            <UART>true</UART>
            <_245FIFO>false</_245FIFO>
            <CPUFIFO>false</CPUFIFO>
            <OPTO>false</OPTO>
          </Hardware>
          <Driver>
            <VCP>true</VCP>
            <D2XX>false</D2XX>
          </Driver>
        </Port_B>
        <IO_Pins>
          <Group_AL>
            <SlowSlew>true</SlowSlew>
            <Schmitt>true</Schmitt>
            <Drive>4mA</Drive>
          </Group_AL>
          <Group_AH>
            <SlowSlew>true</SlowSlew>
            <Schmitt>true</Schmitt>
            <Drive>4mA</Drive>
          </Group_AH>
          <Group_BL>
            <SlowSlew>true</SlowSlew>
            <Schmitt>true</Schmitt>
            <Drive>4mA</Drive>
          </Group_BL>
          <Group_BH>
            <SlowSlew>false</SlowSlew>
            <Schmitt>false</Schmitt>
            <Drive>4mA</Drive>
          </Group_BH>
        </IO_Pins>
      </Hardware_Specific>
    </FT_EEPROM>

    Hope this helps,
    Mark

  • Hi, Mark.

    I've decided to test this behavior and it happens every time a unplug the usb cable during debug session ( I know this is not ok but I got curious =P ). Restarting the IDE solves it.

    eZdspC5535

    Code Composer Studio

    Version: 4.2.4.00033

  • I'm glad you could resolve the issue. Here's what I think is happening...

    If the emulator is physically disconnected from the USB port then you will not be able to connect to the target until you Terminate the target configuration and relaunch it. You shouldn't have to restart CCS...

    If the emulator is not physically disconnected but the target is disconnected or powered down (i.e. if using external emulator and removing it from the header of the board or using embedded emulator on the C5515 EVM and removing external power) then you can reconnect by just doing a target disconnect --> target connect.

    Hope this helps,
    Mark