• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 81 subscribers
  • Views 129 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.

TMS320F280049C: MOTORCONTROL-SDK roadmap vs Motorware

Giannis Roussos
Expert 2290 points
Part Number: TMS320F280049C
Other Parts Discussed in Thread: MOTORWARE, C2000WARE, CONTROLSUITE

Hi,

we have been using Motorware to develop a product family of motor control products based on F28027 and F28069 and are now considering migrating to F280049 for better features and availability.

I have seen the division in SW support between Motorware-supported devices and MOTORCONTROL-SDK - supported devices, TBH I dont't understand why TI intentionally breaks compatibility, creates a division between similar products and prevents what would otherwise could be an easy upgrade path for existing product families. I understand the motivation to start fresh with the new devices - Motorware was far from perfect- but I think supporting the old devices in the new C2000Ware+MOTORCONTROL-SDK framework could be added with not a lot of effort, at least for devices with an FPU like F2806x. In any case, it is what it is, so I have been looking into porting our existing Motorware-base codebase to MOTORCONTROL-SDK and I have some questions about it:

  • Is there any migration guide / tutorial about MOTORCONTROL-SDK and its differences / commonalities wrt Motorware?
  • In the F280049 examples it seems that the main .c file contains a lot more code than the similar Motorware examples, where the main .c is leaner and more functionality is outsourced to the code modules. eg. the ctrl module. Is this a design choice for MOTORCONTROL-SDK that will remain or is it because MOTORCONTROL-SDK is less mature and will be better modularised in later releases?
  • Is there any intention from TI to offer a unified SW support framework for all small C2000 models (F280*) or a subset of them, eg. those with an FPU?
  • Is there a roadmap for MOTORCONTROL-SDK so that we can better plan our migration plan and steer our efforts to better align with new releases?

Thank you in advance,

Giannis

  • 0
    TI__Guru 50595 points

    The InstaSPIN-FOC interface remains pretty much the same with the main difference being the fixed point to floating point change, so the InstaSPIN User's Guide still applies. Many of the other supporting modules from MotorWare have been ported over to the MC SDK as well. The main difference is the underlying HAL layer is implemented using DriverLib from C2000Ware, so adding support for additional peripherals is more straightforward than the process of trying to blend MotorWare and controlSUITE was.

    With regard to road map, there's no plan to bring support for our previous generation of devices (F2802x, F2803x, F2806x, etc...) into the SDKs. The current generation (basically the set of devices shown in the flash & performance graph on this page www.ti.com/.../overview.html) is what we're supporting in the SDK--so for the sort of entry-mid class devices you're using, that means F28002x, F28004x, F28003x, and those to come. Another thing we've done in the most recent couple SDK releases is to start providing the InstaSPIN FAST observer as a .lib, so there's no special ROM requirement to use it--just a device with FPU enabled.

    Whitney