• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 762 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.

F28020 InstaSPIN project

Nancy Jean Burkholder
Prodigy 50 points

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

I am porting a sensorless BLDC motor controller from a LF2407 CPU to a F28020 CPU. I can't find an example InstaSPIN project that supports the F28020 but I do see a project for a F28030. Comparing the two processors I don't see any show-stopping incompatibilities. Working in CCS 5.5 I am trying to adapt the F28030 project but am running into various build issues.

I would like to know if there is an existing F28020 motor control project I can use, or if not, are there any issues that would prevent me from using the modified F28030 project?

I would prefer not to port the existing LF2407 code due to the incompatibilities with in-line asm and CPU architecture, as well as sorting through implementation/design issues.

Regards,

Nancy Burkholder

  • 0
    TI__Guru** 119680 points

    InstaSPIN-BLDC example projects in controlSUITE are supported on 2803x and 2806x series, but there is nothing that should stop you from using a 2802x version. You need to switch out the linker .cmd file and double check the pin mapping.  The same can be said for all of the other types of software, like the SMO based sensorless FOC, etc. Many customers for example use the examples in tmdshvmtrpfckit with 02x.

    For the F2802x the working motor control example software we support is the more extensive InstaSPIN-FOC solution which only runs on F28026F and 27F through MotorWare.

  • 0 in reply to ChrisClearman
    Prodigy 50 points

    Hi Chris,

    Thank you for confirming my approach. If folks had chosen the 2803x I would be half done already. 

    I decided to create a new project rather than modifying an existing project that links to artifacts stored in the controlSUITE hierarchy. As I copy files into the project I can edit their name/contents to reflect the 28020 port. I have a successful build and will start the IO default and pin mapping. The hardware implements active low PWM. I tried using a RAM linker .cmd file but the code doesn't fit and I will move to the ROM version.

    controlSUITE has 7 choices in device_support. My inclination without reviewing each folder's contents is to use the latest; v220. Do you have any recommendations for a particular version?

    Regards,

    Nancy

  • 0 in reply to Nancy Jean Burkholder
    TI__Guru** 119680 points

    Use the most recent version. controlSUITE doesn't do a good job of versioning. Projects are typically self contained for most source code but often reference whichever were latest drivers, modules, and libraries at the time of production. It is not a good method...and has led to controlSUITE having so many versions of each SW carried forward.