• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 53 subscribers
  • Views 6549 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

C28xx: Error initializing Emulator

Alejandro Liscano Olvera
Prodigy 70 points
Other Parts Discussed in Thread: TMS320F28035

Hello, I'm new in CCS and trying the "HVMotorCtrl+Pfc KIT", Im using Windows 8.1, CCS 6.0.1, the kit is called HVMotorCtrl+PfcKit, its card is piccolo F28035, emulator XDS100v1 USB. I have tried the executable to test my induction motor (sensorless) and it works well, I followed the "HVMotorCtrl+PFCKit_HowToRunGuide" and did everything as written and tried to debug and flash the program. However, when I try to flash the card with the file (HVACI Sensorless only) I get the following error:

C28xx: Error initializing emulator 

I've seen that this might happen and you should manually debug it with "Lauch Selected Configuration", but it also doesn't work, it gives me the next errror:

Error connecting to the target: (Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.507.0)

I have also tried to test the connection to the card and had the results shown next:

[Start: Texas Instruments XDS100v1 USB Emulator_0]

Execute the command:

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

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\Liscano\AppData\Local\TEXASI~1\
CCS\ti\0\0\BrdDat\testBoard.dat

-----[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 'May 21 2014'.
The library build time was '17:19:59'.
The library package version is '5.1.507.0'.
The library component version is '35.34.40.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 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 failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

-----[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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End: Texas Instruments XDS100v1 USB Emulator_0]

Did I miss something in the guide?

  • 0
    Guru 192875 points

    Hi Alex,

    Did you compare the voltage levels on the board and that of schematics? Do they seem fine?

    Also, has the target configuration been set properly?

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Prodigy 70 points

    The target configurations has been set according to the manual (XDS100v1 USB emulator and TMS320F28035 device), which to my understanding are correct.

    About the voltage levels, I haven't checked any of them, I assumed they were OK since I had been able to run the program pre-installed. But, what voltages do you refer to?

  • 0
    TI__Guru**** 467601 points

    Alejandro Liscano Olvera said:

    The test for the JTAG IR instruction path-length failed.
    The JTAG IR instruction scan-path is stuck-at-ones.

    The test for the JTAG DR bypass path-length failed.
    The JTAG DR bypass scan-path is stuck-at-ones.

    Unfortunately the "stuck-at-ones" error usually refers to an hardware issue with the actual JTAG connection since even basic circulation of bits on the JTAG scan chain failed. Do you have another dock to try the F28035 card in? Or does the card have a mini-usb connector on it (that is likely an on-board XDS100 on the card itself)?

  • 0 in reply to Ki
    Prodigy 70 points

    Haven't checked for a mini-usb, I'll check it.

    About the JTAG not working correctly, how come it worked fime with the executable? I mean, the card already had the program flashed into it and only needed me to set the reference speed for the motor to follow, but it still communicated to the PC by the JTAG.

  • 0 in reply to Alejandro Liscano Olvera
    Prodigy 70 points

    Good news, it seems the problem has been fixed. The problem seems to be 2 things:

    1) The DC voltage input was insufficient and not correctly wired (I didn't have the DC supply unit that came with the kit, so I used one that I bought but it was connected backwards plus-ground, ground-plus). This caused the "stuck at one" error, since after correcting that, the connection test was OK.

    2) In order to run the program I didn't just press debug, I had to go to target configurations and select "Launch Selected configuration", then "Connect to target", "Load Program" and it flashes the card (I verified it).

    I'm still having problems debugging the program, since it seems it doesn't run because of error "No source available for "0x3ff599", but one step at a time, I'm going to look for a solution for that in the forums before asking again.

  • 0 in reply to Alejandro Liscano Olvera
    TI__Guru**** 467601 points

    Alejandro Liscano Olvera said:
    1) The DC voltage input was insufficient and not correctly wired (I didn't have the DC supply unit that came with the kit, so I used one that I bought but it was connected backwards plus-ground, ground-plus). This caused the "stuck at one" error, since after correcting that, the connection test was OK.

    Nice. Glad you were able to successfully troubleshoot the problem.

    Alejandro Liscano Olvera said:
    2) In order to run the program I didn't just press debug, I had to go to target configurations and select "Launch Selected configuration", then "Connect to target", "Load Program" and it flashes the card (I verified it).

    Sure that is fine. You did something called a "project-less debug session"

    Alejandro Liscano Olvera said:
    I'm still having problems debugging the program, since it seems it doesn't run because of error "No source available for "0x3ff599", but one step at a time, I'm going to look for a solution for that in the forums before asking again.

    Here is a previous thread that had some answers for you:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/214217.aspx

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 70 points

    Ki-Soo Lee said:

    I'm still having problems debugging the program, since it seems it doesn't run because of error "No source available for "0x3ff599", but one step at a time, I'm going to look for a solution for that in the forums before asking again.

    Here is a previous thread that had some answers for you:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/214217.aspx

    [/quote]

    I don't see answers, I've read it a couple times to see if there was something that I wasn't seeing, but either there ins't or I don't get it. They talk initially of another problem (similar to my own), they work it out somehow and then they talk about the same error I'm having but their solution is "minimize the tab", except that in their case the code runs (in mine, it doesn't).

    But I guess that a picture is worth more than a thousand words.

  • 0 in reply to Alejandro Liscano Olvera
    Prodigy 70 points

    I forgot to comment, the picture uploaded corresponds to a procedure described in this post: 

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/200643.aspx

    More precisely this one:

    This message is simply saying that there is no source code equivalent to the reset vector but if you open the disassembly window, you should be able to see where you are halted. If you then do a Restart you will likely halt at "main". From there you can run your program.

    I will report the issues with the newer 2xPM_Sensorless_v1_1 example to the C2000 team. Thanks for your patience.

    I did as adviced and the previous picture is the result, still not being able to run the code.

  • 0 in reply to Alejandro Liscano Olvera
    TI__Guru**** 467601 points

    Alejandro Liscano Olvera said:
    I don't see answers, I've read it a couple times to see if there was something that I wasn't seeing, but either there ins't or I don't get it. They talk initially of another problem (similar to my own), they work it out somehow and then they talk about the same error I'm having but their solution is "minimize the tab", except that in their case the code runs (in mine, it doesn't).

    These are the key quotes from the thread:

    Brian: "I've been receiving the message "No source available for 0x3ff8a1" once I build/load my code. I understand that 0x3ff8a1 is the starting memory location when the processor is reset, which I confirm using the disassembly window"


    Aarti: "As you already mentioned, this message appears if you are halted at a location/portion of code where no source file is available. Unfortunately, there is no way to prevent the message from coming up"

     

  • 0 in reply to Alejandro Liscano Olvera
    TI__Guru**** 467601 points

    Alejandro Liscano Olvera said:
    This message is simply saying that there is no source code equivalent to the reset vector but if you open the disassembly window, you should be able to see where you are halted.

    Yes this is the same as the other thread.