xds100v usb emulator error

Hello,

Can you be more detail so we can help you more?

1. What device (MCU) that you use?

2. What development kit that you use? Or is this your own board (custom board)?

3. Is this XDS100 on board or external board?

4. Is it XDS100 v1 or XDS100 v2 or XDS100 v3?

5. What CCS version that you use?

6. Did you try the Test Connection from CCS before debugging? What did it say?

Best regards,

Maria

Hello Maria,

                       Thanx for your prompt reply.

1. Delfino TMS320F28335 Development Kit

3.no this is an external usb cable connected between the pc and the kit

4.it is XDS100v2

5. CCS V 5.5

6. No I didn't.

regards

Sunil Behara

Yes i am using the same kit which you have mentioned.

The emulator is on board only. It is not an external one.

I have used a simple usb cable only for connection to the kit.

I will do the test connection and will you send the result shortly.

regards

Sunil

Sunil, also check the switches on the controlCard. All should be in the ON position.

Regards,

Gautam

Hello Sunil,

I am wondering, did you already set your SW1 (of experimenter kit) to ON position before debugging?

Best regards,

Maria

Dear Maria,

                      I have followed the same procedure but still not able to debug the code into the kit. I have done a test connection. Here is the snapshot of it.

[Start]

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:\DOCUME~1\20068040\LOCALS~1\APPLIC~1\.TI\
    693494126\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 'Aug 20 2013'.
The library build time was '22:56:19'.
The library package version is '5.1.232.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 succeeded.
The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 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.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[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.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End]

Dear Gautam,

                          Can you please elaborate which switches you are talking about on the kit?

regards

Sunil Behara

Sunil, I'm talking about these switches:

Regards,

Gautam

Yes they are in ON position

I have reinstalled the ccs 5.5 and it worked for me. The emulator is now getting connected and code is getting dumped. But i am facing some compiling and debugging errors.

Below are the two compiling errors :

1) Description    Resource    Path    Location    Type
subscript out of range    HVACI_Sensorless.c    /HVACI_Sensorless_2833x    line 211    C/C++ Problem


    PWMDAC_INIT_MACRO(7,pwmdac1)     // PWM 7A,7B

2) Description    Resource    Path    Location    Type
subscript out of range    HVACI_Sensorless.c    /HVACI_Sensorless_2833x    line 1365    C/C++ Problem


PWMDAC_MACRO(7,pwmdac1)                              // PWMDAC 7A, 7B 

Please provide some solution.

Check this link for the above issue:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/185345/674397.aspx

Regards,

Gautam

But the link is not much of help as the issue is slightly different of mine.  I think it has something to do with c2000 compiler options in the properties of the project. Did you come across a similar issue before ?

Yup the warnings have gone like charm. Thanks Maria !!

I didn't doubt the code as it was an example code, but anyway thanks again.

But now in the debug state the on board emulator is getting detected and the

code is getting dumped but what about the following warnings

After making these two lines as comment . It worked like a charm, those two warnings have gone after building the code again. Thanks Maria.

But i am still left out with the debugging issue. As i have started the thread as emulator error, but after reinstalling the ccs the error is gone and the on board emulator has been detected. But while debugging, the code got dumped but with some following warnings. i am not sure whether they are errors are only simple warnings.

1.main() at HVACI_Sensorless.c: 136 0x009000

2.Can't find a source file at "/tmp/TI_MKLIBr6S4KF/SRC/args_main.c"
Locate the file or edit the source lookup path to include its location.

3.Can't find a source file at "/tmp/TI_MKLIBr6S4KF/SRC/boot28.inc"
Locate the file or edit the source lookup path to include its location.

Regards

Sunil Behara

Hello Sunil,

Which folder that you refer for this project?

Do you use the one from here C:\ti\controlSUITE\development_kits\HVMotorCtrl+PfcKit_v2.1?

Best regards,

Maria

Hi Maria,

                 No, i am not refering to the path you have shown. But i have used the example code from the same folder and made it as a new project and placed it on my desktop. Since i have done some changes to the given code i have done like this. Should i refer it from control suite only?

Hello Sunil,

Of course you can make your own project, not using ControlSuite project.

However, please make sure all project's settings are correct (in this case you can compare with ControlSuite project).

If these warnings don't disturb your applications, I think you can ignore them.

About boot28, you can read this thread:

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

And about args_main, you may just ignore it.

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

Best regards,

Maria