Jump to content
Mk_

Unrecoverable Emulation error

Recommended Posts

Hi everyone,

 

I have a C2k-Launchpad and was using it to run a program generated from simulink.

To do so, I was using CCS4, connecting to the target, downloading the code and running it.

 

Today, while the code was running, code composer showed a message abou the connection being lost, I was a little distracted and just closed the message and tried to connect again. Since then I'm receiving the following message:

post-290-14264717213118_thumb.png

 

And if I retry, it changes to:

post-290-14264717213986_thumb.png

 

Although it shows up in windows device manager:

post-290-14264717214849_thumb.png

 

I don't know what may have happend, and googling around I could not find a way to get it working again.

 

Actually I don't even know if this is a Target or Emulator(XDS) problem..

 

Does anyone had a similar problem?

Is there anything I can do or the board is useless forever?

 

Thank you!

Share this post


Link to post
Share on other sites

I was able to do a JTAG scan test.. here are the results:

 

 

[start]

 

Execute the command:

 

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

 

[Result]

 

 

-----[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 'Dec 19 2011'.

The library build time was '21:32:12'.

The library package version is '5.0.569.0'.

The library component version is '35.34.39.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.

This utility has successfully reset the controller.

 

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

 

The scan-path will be reset by toggling the JTAG TRST signal.

The controller is the FTDI FT2232 with USB interface.

The link from controller to target is direct (without cable).

The software is configured for FTDI FT2232 features.

The controller cannot monitor the value on the EMU[0] pin.

The controller cannot monitor the value on the EMU[1] pin.

The controller cannot control the timing on output pins.

The controller cannot control the timing on input pins.

The scan-path link-delay has been set to exactly '0' (0x0000).

 

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

 

There is no hardware for programming the JTAG TCLK frequency.

 

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

 

There is no hardware for measuring the JTAG TCLK frequency.

 

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

 

This path-length test uses blocks of 512 32-bit words.

 

The test for the JTAG IR instruction path-length succeeded.

The JTAG IR instruction path-length is 0 bits.

 

The test for the JTAG DR bypass path-length succeeded.

The JTAG DR bypass path-length is 0 bits.

 

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

 

This test will use blocks of 512 32-bit words.

This test will be applied just once.

 

Do a test using 0xFFFFFFFF.

Scan tests: 1, skipped: 0, failed: 0

Do a test using 0x00000000.

Scan tests: 2, skipped: 0, failed: 0

Do a test using 0xFE03E0E2.

Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

The details of the first 8 errors have been provided.

The utility will now report only the count of failed tests.

Scan tests: 3, skipped: 0, failed: 1

Do a test using 0x01FC1F1D.

Scan tests: 4, skipped: 0, failed: 2

Do a test using 0x5533CCAA.

Scan tests: 5, skipped: 0, failed: 3

Do a test using 0xAACC3355.

Scan tests: 6, skipped: 0, failed: 4

Some of the values were corrupted - 66.7 percent.

 

The JTAG IR Integrity scan-test has failed.

 

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

 

This test will use blocks of 512 32-bit words.

This test will be applied just once.

 

Do a test using 0xFFFFFFFF.

Scan tests: 1, skipped: 0, failed: 0

Do a test using 0x00000000.

Scan tests: 2, skipped: 0, failed: 0

Do a test using 0xFE03E0E2.

Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0.

The details of the first 8 errors have been provided.

The utility will now report only the count of failed tests.

Scan tests: 3, skipped: 0, failed: 1

Do a test using 0x01FC1F1D.

Scan tests: 4, skipped: 0, failed: 2

Do a test using 0x5533CCAA.

Scan tests: 5, skipped: 0, failed: 3

Do a test using 0xAACC3355.

Scan tests: 6, skipped: 0, failed: 4

Some of the values were corrupted - 66.7 percent.

 

The JTAG DR Integrity scan-test has failed.

 

[End]

Share this post


Link to post
Share on other sites

MK,

That's odd. There are a couple things to check.

  1. Make sure the right most boot switch is in the UP position (toward the emulator).
  2. Make sure the target is powered (using the jumpers JP1 and JP2 or externally through the headers).

One question, you have been able to successfully connect and program the board previously, correct?

Share this post


Link to post
Share on other sites

Hi Trey,

 

1. Make sure the right most boot switch is in the UP position (toward the emulator).

Yes, all of them were always in the UP position. (after the problem i tried all possible configurations, all of them giving the same result)

 

2. Make sure the target is powered (using the jumpers JP1 and JP2 or externally through the headers).

The target is being powered by usb, so the jumpers are connected.

 

One question, you have been able to successfully connect and program the board previously, correct?

Yes, i was able to connect and program it many times.

 

And yesterday (righ after posting here) I tried 2 more things:

1. Reinstall drivers on windows

2. Reprogram FT2232H EEPROM (I made a dump and then reprogrammed using files provided on TI's wiki)

 

None of them recovered it..

Share this post


Link to post
Share on other sites

I've also done another thing.. I took the schematics to find some "known voltage" points and measured them.

 

 

USBVcc = 4.68 V

FTDI_3v3 = 3.27 V

FTDI_1v8 = 1.75 V

+5V = 4.3 V

+3v3 = 3.2 V

Share this post


Link to post
Share on other sites

Mikhail,

I'm wondering if maybe something got zapped by ESD. Have you tried using this board on another computer? That may be a good test to determine whether something is wrong in hardware or on the host PC.

Share this post


Link to post
Share on other sites

Hi Trey,

 

I already tried connecting this board to another computer, and the problem still. (leds wont blink like they used to do before). Even changing the usb port. (I only had not a chance to run the JTAG test, since I don't have CCS installed with C2000 targets at work)

 

On the PC side everything seems Ok, I use usb to many other things (including msp-launchpad, stellaris-launchpad and many other boards I have).

 

Anyway, this board was really useful for me. I made a control's project, presented it (at class) and then the board got bad. (Lucky me!)

 

I wanted to get it working again, but now my hope is gone... but if you want to make further analysis and try to discover what may have happend, just PM me your address and I can ship you the board.

 

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...