• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 623 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.

F28M35xx Control Card - M3 (Error-1063)

Justin Tran
Prodigy 40 points

I've been developing on the F28M35xx Control Card using the example code for epmw_deadband.c and setup_m3 included in Control Suite. I've been successfully debugging, connecting, loading code, and running the PWM code over the last week, but now I can't connect to the M3 module.

Set Up:

USB Drivers: TI XDS100 Channel A: USB\VID_0403&PID_A6D0&REV_0700&MI_00, Channel B: USB\VID_0403&PID_A6D0&REV_0700&MI_01

Target Configuration - Connection: Texas Instruments XDS100v2 USB Emulator, Device - F28M35H52C1

Code Implementation:

I started playing with the M3 clock in the setup_m3.c file as seen in: http://e2e.ti.com/support/microcontrollers/c2000/f/171/p/194073/697896.aspx#697896

Now the C28 sometimes connects(Error -1138) and M3 returns an (Error - 1063)

Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 5.0.872.0)

Error connecting to the target: (Error -1138 @ 0x0) Device refused to allow debug mode. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.872.0) 

Anyone have experience with these errors?

  • 0
    Prodigy 40 points

    Additional information:

    I'm able to run the test configuration for my target configuration and the results are:

    [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:\Users\justint\AppData\Local\.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 'Apr 16 2013'. The library build time was '22:33:22'. The library package version is '5.1.92.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 6 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]

    It looks like the JTAG is working fine, but I still can't connect to the M3.

  • 0 in reply to Justin Tran
    Prodigy 40 points

    After many hours of debugging, I ended up purchasing a new chip and it solved all my problems.

    Here are the steps that I took.

    1) Power Cycle

    2) Switching the workspace

    3) Re checking my target configuration

    4) Re checking FTDI drivers

    5) Cleaning CCS in cmd prompt

    6) Complete uninstall and reinstallation of CCS v5.3

    7) Possible hardware issue, purchase new chip to check