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.

TMDS2MTRPFCKIT GpioG1CtrlRegs symbol problems

Other Parts Discussed in Thread: CONTROLSUITE, INSTASPIN-BLDC, DRV8312, TMDSCNCD28035ISO, MOTORWARE

I am trying to compile the TMDS2MTRPFCKIT and have encountered the following error.

undefined       first referenced 

symbol in file

---------       ---------------- 

_GpioG1CtrlRegs ./F28M35x_Gpio.obj

_GpioG2CtrlRegs ./F28M35x_Gpio.obj

When I search for GpioG1CtrlRegs or  G2, I find then in F28M35Gpio.h not DSP2803xGpio.h.  Yet when I include F28M35Gpio.h I understandably get incompatibility errors since DSP2803x..... is the correct file.  Is this normal?  Do you folks mix and match F28M35 files with DSP2803x files??  You don't do you?  Assuming I am correct, what should I do to fix my problem?  Add the two GPIOG1CtrlRegs symbols to the DSP2803xGpio.h file??

Thanks in advance for your help......

I believed I fixed the problem.  I simply replaced the file F28M35Gpio.c with DSP2803xGpio.c and it attendant h file and the problem has been resolved.  How the F28M35Gpio.c file got in there initially, I have no idea.  I certainly did not add it on my own.  Now whether the logic works as intended is another question. 

 

  • Hi Erich,

    I have moved your thread to the C2000 forums. They will better be able to help you.

    -Nick

  • Erich,

    F28M35x should not be in the TMDS2MTRPFCKIT project. In fact, when I search the controlSUITE\development_kits folder I only find these files with one kit:

    C:\ti\controlSUITE\development_kits\HV_SOLAR_DC_AC_v1.1

    The 2MTR kit is supported through

    C:\ti\controlSUITE\development_kits\LVMultiAxis+PfcKit_v1.4

    which is built with the F28035 devices.

    I hope everything is working for you now.

  • No unfortunately it's not working yet.  Unfortunately TI created a one time combination of the two motor low voltage example within which they added the HV Solar logic.  I have been working with both the C2000 only version and trying to get the Concerto version working.  I have probably inadvertently 'mixed my metaphors' as it were.

  • please post exactly which project you are working off of, and exactly which controlCARD you are using.

  • TMDS2MTRPFCKIT-2xPM_Sensorless project and F2803x control card.

  • Eric,

    I opened CCSv5.4.0

    Imported

    The defautl build configuration that is active (right click on project --> Build configurations --> Set Active) is the F2803x_RAM

    Built successfully, with the following two warnings:

    1. build attribute vendor section TI missing in DSP2803x_Headers_nonBIOS.cmd 
    1. this is a known issue with using IQMath library that hasn't been updated to make this warning go away. No issue.
    • This project was created using a version of compiler that is not currently installed: 5.2.3 [C2000]. Another version of the compiler will be used during build: 6.1.3. Please install the compiler of the required version, or migrate the project to one of the available compiler versions by adjusting project properties.
      1. New compiler in CCSv5.4, can update the project settings to remove this warning, but the build is correct

    The _FLASH version also built with the same warnings.

    There is nothing in any of the files regarding 28M3x

    I would look to start fresh on this project, or all of controlSUITE.

     

  • Chris - Thanks.  I'll replace the ControlSuite in that I just imported the project.  Based on that, a follow up question.  When one makes changes to the files, I had thought those changes were constrained to the Workspace, now it appears the changes actually make it back to the source files in the respective folders such as include, examples, asm, etc.  Is this the case?  It certainly would explain why my freshly imported projects appear to be corrupt, in that my prior changes would already be in there.....

    Chris - I just unzipped the control suite over the top of the existing ControlSuite.  I imported the project once again and it's as corrupt as ever.  In fact the file DSP2803x_Headers_nonBIOS.cmd  is excluded from the project (something I tried a while back when I was have problems.)  To  give you a bit of background: I have simply been using the same Workspace and just deleting and reimporting the project expecting I will be importing a virgin copy.  Is this not the case?  It almost seems as if whatever I import mirrors the offending project I deleted.

     Chris - I just created a new Workspace and imported the project.  It's still corrupt.  I am now downloading the latest ControlSuite from TI.  I had been unzipping a version I downloaded in March.  BTW - when importing Existing CCS\Eclipse Projects I go to: ControlSuite\DevelopmentKits\LV_MultiAxis+PfcKit_v1.4\2xPM_Sensorless_v1_1.  Not that there are a lot of options but this is where you find the project as well no?

    I do see when importing there is a Copy Project to Workspace option.  I also remember TI advises against this in most cases.  So I guess the long and the short of it is, when I've been changing the code I've been changing the original source.  I also suspect my extract to the ControlSuite location is not working so I have now deleted the original ControlSuite and will extract once more.

    One mystery solved.  I did not realize that when extracting the downloaded file I was simply extracting a ControlSuite install exe. (suspected something was different when it stated extracting one item) I am now running the install. 

    Erich

     

  • Erich,

    Yes, I am using

    C:\ti\controlSUITE\development_kits\LVMultiAxis+PfcKit_v1.4\2xPM_Sensorless_v1_1

    if you want to keep a golden source and edit your own project I recommend copying 2xPM_Sensorless_v1_1 to your own folder and importing that

    ex:

    C:\ti\controlSUITE\development_kits\LVMultiAxis+PfcKit_v1.4\2xPM_Sensorless_working

    I just tested this and it worked find

    BTW - are you particularly looking at a two motor design?  If not I would recommend using the DRV8312-C2-KIT or DRV8301-HC-C2-KIT based projects for InstaSPIN-BLDC, hall BLDC, and sensorless SMO FOC and the DRV8312-69M-KIT / DRV8301-69M-KIT for IntaSPIN-FOC and InstaSPIN-MOTION solutions.  The 2MTR kit is quite old and doesn't have the latest features or updates.

     

     

  • Good to know.  I am not married to the two motor idea.  I am trying actually to use a sensor (not senseless) example so the Hall aspect is intriguing.  Where I want to go with this eventually is to replace the F2803x card with my Concerto F28M35 card and port the logic over to the Concerto.  One of your contemporarites, Ramesh Ramamorthy sent me a TI (alpha?) version of code that should work on the 2 MTR board and was wrtiien for the Concerto.  So far I have been unsuccessful in getting it to run  Thus I have been bouncing back and forth try to see what the differences between the two are.  Get's kind of confusing after awhile.

     

    I appreciate your time and attention to this.  Oh and yes, I heeded your suggestion and made a golden copy of the project.

    OK - I brought in a virgin copy and tried to build.  First off, when imported, the configuration is set to RAM but the Flash CMD file is included and the RAM file is excluded.  Maybe all this takes is going to each files properties and changing the include/exclude status?  I'll try to see if it's a simple as that.  Also when building it as is, I get two warnings as you did, one applying to the Compiler level but my other warning is ( no I was mistaken noticed this is the same error you mentioned) different:  build attribute vendor section TI missing in ....

    this applies to the DSP2803x_Headers_nonBIOS.cmd file.

  • Ah, yes. There was a Concerto project created for the 2MTR board for a tradeshow some time back. We actually haven't ported much else over to Concerto ourselves, but I know that VisSim has several diagrams working with Concerto and the DRV8312 and DRV830x boards, both hall sensored and sensorless FOC. 

     

  • Thanks Chris - I'll pick up one of these and possibly with a bit of guidance I'll get an Concerto based example running for my customer.  Of the two, 8312 and 830x given my stated direction any preferences?  I got the DRV8312.  Surprisingly the company I bought it from has it marked - end of life??

  • Erich,

    Tell me about the motors you plan to use. Voltage, current, use case (speeds, position, etc.) and I'll give you a recommendation.

     

  • Chris - I just purchased the DRV8312 with the NEMA 17 motor supplied with it.  I'm not by any means an expert on Motors so I just picked the kit with the motor supplied relying on the supplier to make the correct combination.... Thanks...

  • The DRV8312-C2-KIT and DRV8312-69M-KIT use the same NEMA17 motor as the 2MTRPFCKIT.  So from that perspective you are fine.

     

  • This is what I got: 595-DK-LM3S-DRV8312 DK-LM3S-DRV8312 Sandstrom Control.  Once I entered  DRV8312-C2-KIT , the TI site had links to several 3rd party suppliers, one being Mouser Electronics.  Hopefully it's one of the two parts you call out.  I doubled checked my purchase.  Yes indeed it maps to TI's DRV8312-C2-KIT

  • Erich,

    Yes, the DRV8312 baseboard is the same in all of the DRV8312 kits, they just come with different controlCARDs.  This DRV8312 Rev D board supports 50V and 3.5A continous.

    You can use this board with TMDSCNCD28035ISO or TMDXCNCD28069ISO with controlSUITE

    Sensored BLDC, Sensorless Bemf ZC BLDC, Sensorless InstaSPIN-BLDC, Sensorless (SMO) FOC

    C:\ti\controlSUITE\development_kits\DRV8312-C2-KIT_v128

    or TMDSCNCD28069MISO with MotorWare

    Sensorless (FAST) InstaSPIN-FOC, Sensorless (FAST) InstaSPIN-MOTION (SpinTAC Motion Suite), Sensored (Encoder) InstaSPIN-MOTION (SpinTAC Motion Suite)

     

  • Super Chris.  Thanks for all the great information.  I posted a new but related question since I think you answered everything directly related to this thread.  Again thanks!