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: PMP7605 GUI PC S/W cannot set serial port to be connected ?

Part Number: TIDA-00120
Other Parts Discussed in Thread: MSP430F5132

Dear PMP7605 related engineers,  

I made PMP7605 PCB and used the same S/W with reference PCB.    But PMP7605 GUI PC S/W never be connected with

the PCB with original PMP7605 S/W with '#Define GUI'  in every S/W module. 

  Actually,  I have many experience of using UART communcation betwen board to Board and board to PC.

It looks that problem is caused by PMP7605 GUI PC S/W do not have serial port setting.  PC normally assign the serial port#

depend on attached H/W.   I don't know whether PMP7605 GUI PC S/W automatically search right serial port and connect.  

As it's never been connected,  I have tested the UART signal with oscilloscope.   But  there was no UART R/TX signal change when

I start PMP7605 GUI PC S/W or by clicking retry button.   

Since there was  only two com ports except MSP debug com port in PC device manager,  I checked both PC's COM1 port and

MSP-EXP430F5529's serial ports.       But none of R/TX signal change by pressing PMP7605GUI PC S/W retry button.  


 Looks PMP7605 GUI PC S/W do not send UART signal to assigned serial port.  

But when I used terminal S/W like CoolTerm,  I verified PC was sending proper UART signal to Com1 or MSP-EXP4305529LP serial port.


There is no way for user to select the assigned serial port ? 

Even I seached all the related E2E Q&A and  google,   I couldn't find clear answer.  


FYI, I'm using Window10 for PC OS and tested with both MSP-EXP4305529 & MSP-EXP430G2.  

Another problem is PMP7605 reference S/W do not make proper dead time for high / low side driving transition time.    


 Low to high dead time looks too enough but High to Low don't have dead time.   according to PMP7605 user's guide, 

the ref S/W is making proper daed time if I see the attached pictures.

The timing confliction is related with high resolution Timer D setting,  it's just up mode, not up&down mode.

When TDR reached to TDCCR0, CCR1& CCR2 out signal looks to be toggled.     But TDCCR1  & TDCCR2 have timing

difference 20,  it can make dead time.     It's just my understanding.   Anything I misunderstood  ?  

I attached the picture captured by osilloscope. 

  

YS Kim               

  • Yongsung,

    It looks like you were able to successfully compile and download the source code to the board since you are generating PWMs.

    By default, the GUI is not enabled in the source code. Have you recompiled it and flashed the MCU after uncommenting the "//#define GUI" at the beginning of each source file?

    You can find some additional clarification here: https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/346502/1484353#1484353 

    The PMP7605 GUI was also not tested for Windows 10 compatibility. You might try running it in compatibility mode, or as administrator. I will continue to look into your issue and reply if I find anything else.

    Regards,

    Bart

  • Hi Bart,

    Thanks for your advice!

    Since I was quite sleepy in the midnight, my question was somewhat unclear.

    Of course, I ereaed remark symbol "//" in fromt of "#define GUI" in main .c , GUI.c and Config.c. Compiling and target downloading was no roblem. The PWM signal was made by using Config.c parameter by adding comment symbol "// #define GUI" at any c files.

    By setting a breakpoint at Interrupt_enable(RX) in GUI.c, I found that S/W is jumping to GUI.c well. But when I set breakpoint on interupt vector subroutine, it was hanging all the time. Of course no signal on LED2/3 and R/TX port when I run GUI PC S/W and clicking connection retry button. It was monitored by scope.
    MPPT target board MSP430F5132 itself have no problem for UART comm.

    So, as I said GUI PC S/W do not send any initialization signal to any UART port. I tried to find any external config file that can change com port assignment . But there was no. And PMP7605 GUI PC SW do not send any UART signal to anywhere outside. And no menu to set com port.

    My PC is showing that MSP Application UART1 is assigned to (COM7).
    Is there no way that I can config 'PMP7605 PC SW' to contact with COM7 port ? Any hyper termial S/W can set any COM port. And verified that MSP-EXP430 UART was responding on the Hyper terminal S/W. I think PMP7605 PC app designer can fix this issue.
    Expecting any method !

    YS Kim
  • YS,

    Thank you for the detailed response and explanation, it helps tremendously. 

    Regrettably, I don't have a solution based on what you said. It does indeed look like the GUI software isn't sending anything out of the COM port.

    I'm working on getting the original source code for the GUI application so I can look deeper into how it operates and get you a solution. I'll update you on the progress soon.

    Regards,

    Bart

  • YS,
    I believe I have tracked down the issue for you.

    The software was intended to be used with the G2 Launchpad as the interface board, but you are using the F5529 Launchpad. The G2 only enumerated a single COM port, as opposed to the two that the 5529 enumerates in hardware. The GUI (via the listcomports.exe application) is detecting the debug interface COM port first and attempting to use it, rather than the application COM port. This listing is based on the USB VID/PID rather than the port number, so the debug port will always be selected.

    I do need your help to test this if possible. Can you uninstall the debug com port in your device manager, leaving the application port enabled, and attempt to connect again? listcomports.exe should only see the single entry from the Launchpad and connect approperiatly. If this works, please let me know and I will attempt to get you a new version of the GUI that will be a bit more robust to this issue.

    Regards,
    Bart
  • Hi Bart,

     Since I do have serveral pcs of  G2 and F5529 launchpads.   I tested both.    In case of G2,   it was never been connected.  

    In case of F5529 Launchpads,   As you guided, I removed the  debug com port driver in PC device manager.    But the GUI S/W  was not connected F5529 launchpad serial port.    But when I tried to start the PC GUI SW more than 10 times,   it was connected with target board suddenly.  (It's the case when I didn't  remove the debug com port driver in PC device manager).          

    For overall,  GUI S/W can be connected with 5529 Lauchpad.   But connection can be done  once per 10-20 times of  GUI S/W restart trial.     If possible,   need to make some modification of GUI S/W to set com port to be connected ratehr than USB VID/PID.    

    Like any other Hyper terminal S/W (Coolterm & etc).     I attached the UART waveform picture when it wsa connected.  

    yellow= EVM RX,  red= EVM TX pin.     Every 1sec,  PC GUI S/W send UART link stay & update  signal.

    In my thinking ,   adding new menu to set com port will be difficulut.   How about the GUI S/W to be linked with  external

    com??.ini file to set the com port among  the com port that PC  dvice manager assigned for the dedicated H/W ?      

    Thank you !

    YS Kim

  • YS,

    Thanks for the follow-up, this information is very helpful.

    I'll work on the changes to the software you propose and get it updated as quick as possible.

    Regards,

    Bart

  • YS,
    I'd like to let you know that we have made an update to the software and it's now published on the TIDesign page: www.ti.com/.../TIDA-00120

    Please try it out and let me know how it works for you.

    Regards,
    Bart
  • Hi Bart,  

     I downloaded & tested the updated GUI S/W.   

    It looks perfect.     As soon as I set the EVM assigned port,    It was connected with 1 trial.  

    Thank you very much for your effort !  

    YS Kim