• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 41 subscribers
  • Views 1535 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.

TIDA-00120: Problems connecting to the GUI

James Lake
Prodigy 60 points
Part Number: TIDA-00120

I built out the PMP7605 (TIDA-00120) Solar Charge Controller reference design. I programmed the microcontroller using a Launch Pad and CCS, and the hardware seems to be working. However, I cannot connect with the GUI. I have attempted to use the Launch Pad, as described in the documentation, wired as indicated to P2.4 and P2.5 of the uC(L2 and L3 on the hardware). However, my PC gives me an error when I try to connect and I see no activity on TXD or RXD. While attempting to connect with the GUI, the hardware is being powered by my lab power supply at 19v on the panel input. I have connected a jumper from J4 pins 1 and 2 and connected TXD and RXD to L2 and L3 as stated in the docs:

  MSP430 launch pad is used to establish the connection with the hardware. The same launch pad can be used to program the controller as well. For programming the controller, take out Vcc, test, reset and ground  pins out of the launch pad and connect to the respective pins of the board. To connect the hardware to GUI connect Rx,Tx of launch pad to L3,L2 indicator pins respectively and short the grounds.

The docs also suggest the following:

If the connection could not be established please check for the following.
• The EVM is power is present.
• The 3V3 (JP1) jumper is in place.
• The connection cable between the PC and Hardware is connected.

These raise some questions.

(1) What is the EVM power? The "EVM" is mentioned no where else in the docs. Do they mean the hardware (PMP7605)?

(2) There is no JP1 on the schematic. Do they mean J4 pins 1 and 2?

(3) Can you give me any additional assistance (suggestions) for connecting to the GUI?

Kind Regards,

Jim Lake

  • 0
    TI__Expert 3860 points
    Hi Jim,

    The EVM in this context refers to the PMP7605 board. The power during programming is provided through J6. So the jumper has to be between J4 pins 2 & 3. During stand-alone application, this jumper will be moved to between pins 1 & 2 on J4, so that the controller is powered from on-board power supply.

    Regards,

    Salil
  • 0 in reply to Salil
    Prodigy 60 points

    Salil,

    I am still unable to connect the GUI to the PMP7605. I have tried this on several different PC's and always get the same result, a fail to connect. My PC device manager tells me it is connected to an MSP  Application UART on COM 5 and a MSP debug interface. So it appears that the PC sees the Launch Pad, but the launch pad does not seem to send data to the PMP7605. I put a scope on the TX and RX lines running to the PMP7605 and I see no activity on the UART.

    Perhaps the problem is that I have something connected incorrectly. I am attaching a photo of the setup, perhaps you could look at it and see if you see something obvious. As I said above, the PMP7605 seems to be working fine. I am powering it with 18v from my lab supply to the PV panel input, and I have a jumper on J4 pins 2 and 3.

  • 0 in reply to James Lake
    TI__Expert 3860 points

    Hi James,

    I will get help from firmware designers to see what is the problem here, as I am not able to identify it.

    Regards,

    Salil

  • 0 in reply to Salil
    Prodigy 60 points
    Thank you. Also ask someone to clarify this statement from the GUI documentation:

    RUNNING THE HARDWARE IN STAND-ALONE MODE
    The firmware loaded by default in the MCU on board is a User Experience code. Using this firmware will
    need the GUI to work properly.
    However, once the parameters are tuned, the output of the GUI can be used to operate the hardware in
    a stand-alone mode (without GUI). These parameters are given by the GUI in form of the ‘config.c’ file
    which is further used to change the code inside the MCU on hardware.

    To use the system without GUI, user can follow these steps:
    1. Add the generated Config.c file to the CCS project.
    2. Remove/comment the statement ‘#define GUI’ at the beginning in main.c, GUI.c and config.c files.
    To use the system without GUI, add the statement ‘#define GUI’ at the beginning in main.c, GUI.c and config.c files.

    It seems to me that the last statement should read "To use the system with the GUI..." Is that correct?

    Also, be aware that the firmware, as distributed, had the #define GUI statement commented out in main(), GUI.c and config.c.

    Does that suggest that the system has been defaulted to run standalone?