• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 206 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.

TMS320F280049C: Motor controller not working

Ruud B
Intellectual 260 points

Part Number: TMS320F280049C
Other Parts Discussed in Thread: LAUNCHXL-F280049C

Hi,

I've been working for months on our motorcontroller. And it seems that the code refuses to go to mainISR().

Steps:

Tried our own hardware and the software provided by TI. Code can be build, programmed and itn runs. It never reaches mainISR().

Read all documentation, tried different setups, labs etc etc.

Now, put all above aside and bought launchxl + boostxl 8320rs

Read all documentation. Installed everything new, motocontroller software 4.00.00.0.

labs01 will build, program and it runs. According to the manual: "At this point, one of the LEDs on the controlCARD or LaunchPad board will blink"

Well, it does not blink. Again the firmware does not go to mainISR() where the led is turned on/off.

One LED is on, below the boostxl card (turned on on line 201 :    HAL_turnLEDOff(halHandle, HAL_GPIO_LED1);//turn ON

 

Please guide me, this is frustrating.

Is the documentatio up-to-date? Is the firmware up-to-date?

All software from ti is re-installed.

Best regards,

Ruud

  • 0
    TI__Guru** 117040 points

    No. It works if you didn't change anything in the lab. You may try to set "motorVars.flagEnableSys" and monitor the "counterLED" to see if the value of this variable is changed in mainISR().

    BTW, the lab01 can work on LAUNCHXL-F280049C without connecting the boostxl 8320rs.

  • +1
    Intellectual 260 points

    It seems that the motor SDK will not use the default installation directory I and/or TI use for the installation of SDK's and compilers (default is c:\ti\c2000\), therefor when installing the SDK via the resource manager its installation directory is c:ti\.

    Removing al the SDK's from the ti\c2000\ folder but leaving the installation in ti\ results in using (old) modified code which does not run well on the BoostXL board (hal.c file was changed). Hence, there is some discrepancy when installing an SDK directly or via the resource manager AND then importing via the project explorer or the Resource Manager.

    To fix it, I had to go to Window->Preferences->Code Composer Studio->Products and Add... the c2000 folder TI use for other products to install. After adding this location, the Motor SDK is discovered in the window below (click refresh). 

    Now, the LED blinks.