• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 83 subscribers
  • Views 668 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.

TMS320F28069M: Using GUI Composer v2 w/ InstaSPIN-FOC 28069M

Ken Bass
Prodigy 90 points
Part Number: TMS320F28069M
Other Parts Discussed in Thread: MOTORWARE, TMS320F28069, TMS320F280049C, C2000WARE, INSTASPINUNIVERSALGUI

Code Composer Studio is up to version 10.0 now. The INSTASPIN Universal GUI requires an old 6.0 version. I have encountered numerous links prodding me to use the 'Cloud' based GUI Composer v2 and I would rather not install the older CCS 6.x version if I don't have to.

I thought I would try it out. In the gallery I did find an Insta-SPIN project designed for another board / CPU. I figure that existing effort would save me time building the UI. However, after importing that project into GUI Composer v2, going to Project Properties, there is no TMS320F28069M device listed (only the non-M version). Does that matter for the GUI? Is this GUI Composer v2 suppose to work with the older motorware stuff?

I even tried selecting the TMS320F28069 (non-M) so see if the console would connect and it says 'Failed to connect to device TMS320F280049C.' - that isn't even the device I selected.

  • 0
    TI__Guru 52065 points

    You may be able to run the original Universal GUI without CCS 6 if you open up the standalone executable, but yes, you will need an older CCS with the original GC if you ever need to edit it.

    I was able seemingly to get the GC2 version it to switch devices if I updated the device/connection in the project properties, opened up the .gui file, made some small change to get it to let me save, saved, and tried connecting again. I don't have an F28069M with me to test with, but it is displaying "Failed to connect to device TMS320F28069" now.

    The new GUI is not compatible with the F28069M labs as it is now though. Many of the variable names were changed between the MotorWare versions and the F28004x version released within the C2000Ware MotorControl SDK. It could still serve as a decent starting point if you have the patience to map the variable bindings from new names to equivalent names from the MotorWare version.

    Whitney

  • 0 in reply to Whitney Dewey
    Prodigy 90 points

    Hi Whitney, I too was able to get it to save my choice of TMS320F28069 like you did. When I click the Project Properties 'Connect' I get the messages below...

    It does appear that it downloads the lab app to the board (mismatched names aside) because I see the LED blinking. I know under CCS debugger you have to click the 'enable silicon debug', does this GUI Composer v2 handle that? What causes the failure at the verifying connection step?

  • 0 in reply to Ken Bass
    TI__Guru 52065 points

    I'm guessing you've also updated the .out to a MotorWare lab one instead of the default one that the GUI started with? Not sure why it would fail to reconnect after the load. I'll forward your post to someone on the GC team to see if they have any insights.

    Whitney

  • 0 in reply to Whitney Dewey
    Prodigy 90 points

    Thanks and that assumption is correct, I updated/'uploaded' the .out file to a MotorWare lab3b which works. I also ran the same lab3b (renamed to appProgram.out) using the INSTASPINUNIVERSALGUI.EXE (which is v1 based) and verified it works.

    In case it matters, I am initially trying to get this working a DRV8301-HC-EVM Rev D board kit.

  • 0 in reply to Ken Bass
    TI__Guru**** 433951 points

    Hi Ken,

    Can you share the *.out file that you are using?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 90 points

    Attached is zip file containing the appProgram.out

    4760.appProgram.zip

  • 0 in reply to Ken Bass
    TI__Guru**** 433951 points

    Thanks. It seemed to connect for me:

    Can you try creating a new project from scratch?

  • 0 in reply to Ki
    Prodigy 90 points

    Ki said:
    Can you try creating a new project from scratch?

    I created a new project from scratch and it worked.

  • 0 in reply to Ken Bass
    TI__Guru**** 433951 points

    Ken, I suggest starting from scratch instead of trying to work with a modified version of an existing solution. There is likely some configuration in there that is causing some conflict.

    ki 

  • 0 in reply to Ki
    Prodigy 90 points

    I guess I will have to. I was trying to save time by reusing the existing GUI layout for the instaspin.

  • 0 in reply to Ken Bass
    TI__Guru**** 433951 points

    Yes, I would recommend that despite the initial headache of starting from scratch.

    ki