• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 635 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/TMDSHVMTRPFCKIT: Trouble Reading DAC Signal(Error -154/-1138/-1142)

Dan99537
Prodigy 70 points

Part Number: TMDSHVMTRPFCKIT

Tool/software: Code Composer Studio

Hi guys,

my environment is

OS(Win7) + IDE(CCSV5) + HW(TMDSHVMTRPFCKIT) + MCU(TMS320f28035) + emulator(XDS100v1) + controlSUITE(HVBLDC_Sensored)

Everything worked well until today, and here's what happened:

1.After debugging,I pressed the "Enable silicon real-time mode” button , “Enable polite real-time mode” button and “Continuous Fresh” button.

2.set "EnableFlag" into 1 and pressed the "Run" botton.

Then the BLDC motor started to work, but I found out that there wasn't any signal showed on the scope when I tried to read the DAC pins.

Besides the CCS showed the following error (Error -154 @ 0x0) and became not responding

At the same time the LD3 on the controlcard was blinking in red(the motor was still worling, too).

After closing the CCS and then debugging again, I found out that once I pressed the "Reset CPU" botton, there would be another error showed up.

It seems that there was somthing wrong with the emulator, but I'm not quite familiar with it.

Please help me out.

Thank you for your time.

Here's the result of test connection of the emulator.

[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 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]

  • 0
    TI__Guru** 114050 points
    1. You might power off both HV-Kit and controlCard, restart the CCS to re-load the code to F28035, to look at what happened.
    2. Did you enable the CSM for F28035 in your project? Did you halt the emulator during the device is programming?
    You might load an example project that only running in RAM to check if the flash is damaged, the example project could be found in the "device support" folder of controlSUITE.
  • 0 in reply to Yanming Luo
    Prodigy 70 points
    Thanks a lot for your response.
    Here's what I found out today:
    1.After pressing "Run", the CCS can work properly but there is still no any signal coming out from ADC pins(and LD3 was blinking in red).
    Besides the two error(1138&1142) showed up when I pressed the "Reset CPU" botton.
    2.The CSM didn't enable, and I didn't halt the emulator during the device is programming.
    I checked the example projects in "device_support\f2803x\v127\DSP2803x_examples_ccsv5" but wasn't sure which one only running in RAM. I have tried "Example_2803xCpuTimer" and "Example_2803xECanBack2Back" which both worked.
    Please give me some advice.
    Thank you for your time.
  • 0 in reply to Dan99537
    TI__Guru** 114050 points
    Good, that means the h/w boards worked well, you may add a magnetic ring on USB cable to suppress the harmonic noise that maybe cause the disconnection of the emulator.

    Please follow the project guide to debug the motor step by step, you should get correct ADC value on the related Pins since the motor spins well.

    You need to connect the related inputs to PWMDAC module in the project if you want to use the simulation DAC. You could find PWMDAC guide in controlSUITE also.