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

Supposed Communication Problem Between a TMS320F28035-DSP on a Solar Explorer Kit Board and CCSv6.

Gustaf Falk Olson
Prodigy 30 points


Dear to whom it might concern,
We are a group of five students working with the TI Solar Explorer Kit for educational purpose. However, we have not yet managed to establish a proper communication between our TMS320F28035-DSP on the board and CCSv6, despite our joint and continuous efforts. During the last week we have sorted out several issues by referring to posts in the forum, but now it seems we have run into a dead end.
We have followed the instructions under the section 3.2 Software Setup in the TI-document Implementing Photovoltaic Inverter System using C2000 Microcontrollers on Solar Explorer Kit to set up the Code Composer Studios. However, when trying to connect through the main USB (JTAG-emulator) on M7, we obtain the following error message:
-------------------------------------------------------------------------------------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Sep  4 2015'.
The library build time was '21:59:23'.
The library package version is '6.0.14.5'.
The library component version is '35.35.0.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).

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-150' (0xffffff6a).
The title is 'SC_ERR_FTDI_FAIL'.

The explanation is:
One of the FTDI driver functions used during
configuration returned a invalid status or an error.

[End: Texas Instruments XDS100v1 USB Debug Probe_0]
------------------------------------------------------------------------------------------------------------------------
A test with the db jtag troublehooting software confirms there is no connection, although all the drivers are confirmed to be installed. Moreover the device manager recognizes the usb-connection and shows the correct ID. We have performed the actions suggested on the XDS100-wiki-page without success.
 
Hence, we tried to connect via the mini-USB port that connects to M5 and the PV-emulator. We discovered that this actually resolves the previously described issues and following the same procedure as above, the db jtag indicates that there is an established connection. In particular, the error message e-150 disappears and the lamp on the main-dsp blinks. Subsequently, the build process in CCS progresses for a couple of minutes before the following error message appears:
   
Finally, we tried to connect the board to the host via the jtag itself (the pins on M7) through a Spectrum Digital Inc. XDS100v.2 JTAG-emulator. Although the connections seems to be fine (just as in the case when the mini-usb was connected), CCS prompts that power is missing to the emulation package.
Having reached this point, we feel that we have run out of options and are at a loss. Any assistance and advice on how to proceed would be much appreciated.
Thank you for taking your time,
Gustaf
  • 0
    Guru 192875 points
    Hi Gustaf,

    Can you quickly do a hardware check? Check the voltages around the controller and regulator.

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    TI__Guru 57255 points

    Hi Gustaf,

    Most of what you are saying makes sense, however not quite everything.  I will give my thoughts on your issue and perhaps it will help clarify some things.

    First off, there are two separate C2000 devices on the Solar Explorer board.  Assuming that you have bought the TMDSSOLARPEXPKIT:

    1) A F28035 - located on the controlCARD that is included in the kit and should be plugged into H1

    • can be connected to CCS using either the USB connector ([M7]-JP1) or JTAG header ([M7]-J2) within the [M7] section of the board.

    2) A F28027 -

    • can be connected to CCS using the USB-mini connector ([M5]-JP1) within the [M5] section of the board.


    It seems you are having issues with both.  Let's treat them separately.

    Note that it is possible for CCS to get confused as to which emulator is being used if both USBs are connected.  For simplicity, I would recommend that you either connect a USB cable to [M7]-JP1 (the inverter's USB) or connect a USB cable to [M5]-JP1 (the panel emulator's USB).

    ====

    F28027 -

    When you say that you are able to connect CCS via the mini-USB connector, you are connecting to the F28027.  When using this, make sure that you are loading the PV emulator software to it and make sure that your target configuration is xds100v1+F28027.  If done, this device should run and should not give you issues - ie should not lose emulation after running for a few minutes.  If you are not doing this, can you try this?

    ===

    F28035 -

    Based on your description, you have not been able to connect up to the F28035 at all yet.  When you are trying to connect to the controlCARD, make sure that the controlCARD is powered - make sure that LD1 on the controlCARD is lit.  You should also make sure that [Main]-J4 is populated - see picture below.  Please check this.



    ===


    Hopefully this helps.


    Thank you,
    Brett