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.

TMDSSOLARUINVKIT: Migration to other MCU

Part Number: TMDSSOLARUINVKIT
Other Parts Discussed in Thread: TMS320F28035, TMS320F280039C, TMS320F280025, SYSCONFIG, C2000WARE

Hi TI Team.

The TMDSSOLARUINVKIT microinverter solution is based on TMS320F28035 MCU. Its MIPS may not be enough to handle 4 PV panels. So I searching for its replacement but without need to rewrite entire code. I know that the TMS320F280039C is the best replacement for TMS320F28035  and specially recommended in micoinverters solutions but for that MCU I need to rewrite the code due to the driverlib aproach. But how about TMS320F280025? I need 12 PWM, 15 ADC, 4 comparators and more than 60 MHz.TMS320F280025 has it all and its a floating point unit and there is a TMS320F2802x/TMS320F2803x to TMS320F28002x
Migration document which my be helpfull.

I need your advice. What do you think?

  • Hello,

    In terms of functionality, both F280025C and F280039C would fulfill your design requirements. You may want to consider the lower cost of F280025C and the direct availability of the F2802x/F2803x to F28002x migration guide as you mentioned (there is no specific F2803x to F28003x migration guide available, though we do have an F28002x to F28003x migration guide to aid in migration to F28003x). That being said, F280025C does have a more limited FLASH/RAM size in comparison, so be sure to gauge which can best accommodate the application. 

    There are more application-specific ways to filter C2000 products on ti.com as well, such as this block diagram that shows other micro-inverter options. Here, you can see that  F28003x, F28002x, F280013x, and F280015x are all viable candidates. Note that F280013x and F280015x will yield similar software migration hurdles to F28003x.

    Other general migration resources:

    Please let me know if you have further inquiries.

    Regards,

    Allison

  • Hi . Thank you for information. Reducing project costs is important but can be considered in many ways. For me, one of those ways is the speed of code implementation and, at this point, the speed of code migration from TMS320F28035 MCU to something more powerfull BUT with the same peripheral bit-field structure approach. I will be very grateful when you help me to find more powerfull MCU than TMS320F28035 with Peripheral Bit-Field Structure Approach.

    Thank you very much in advance.

  • Hi WW,

    Bit-field structure is still supported on F28002x and F28003x, so you can still use bit-field approach with newer devices. There are still some bit-field examples in the C2000Ware SDK if you go to 'C2000Ware' > 'device support' > {device} > 'examples'. The limitation here is that there are no tools to directly help port bit-field code from one device to another. 

    The recommendation would be to try to utilize the SysConfig UI/DriverLib. Once translated into SysConfig/DriverLib format, it is very easy to migrate across newer devices (see the SysConfig video series I linked above). As further note, it is valid to use a hybrid of bit-field and DriverLib code together, you do not necessarily convert all of your program to one format or the other- more information on this can be found in this C28x programming documentation. Please let me know if you have further questions. 

    Regards,

    Allison

  • Hi . Thanks for info and yes, I have question. Can you give me advise to which MCU it will be easier to software code migration of the TMDSSOLARUINVKIT and what I should pay attention to during this process.
    Another question is it is possible to get help from you with code migration?

    Let me know. Thank you.

  • Hi WW,

    Software migration would be quite similar across those devices, and feel free to refer to the F2803x to F28002x migration guide for aid in understanding what to look for in terms of differences. I unfortunately cannot help directly with the code migration process .However, I did reach out to other TI experts to see if they are aware of other resources that may help you, and I will follow up with you if they provide further guidance or input there. 

    Regards,

    Allison

  • Hi . I think I can handle migrating TMDSSOLARUINVKIT software form F28035 to F280039C from the peripheral registers side. The difficulty will be reogranization to the different memory structure and handle TMDSSOLARUINVKIT libraries such as MPPT and rest.

  • Sounds good. I am still waiting for a response about other migration resources, but I will update here if there are further resources are highlighted. 

  • OK, I would appreciate any help.

  • Hi WW,

    I have heard back that there are no other specific resources to offer for this specific case other than the migration guide and programming document I listed above. However, I was also made aware that it might be helpful for you to leverage resources in the Digital Power SDK. One expert suggested you might find digital power reference code in newer devices helpful. For example, there is the SOLAR-DCDC design, which has MPPT algorithm, and there is HV-1PH_DCAC, which has inverter control algorithm. You can also find these TIDM in 'C2000Ware_DigitalPower_SDK' > 'solutions'. 

    Regards,

    Allison

  • Hi . Thank you for clarification.

  • No problem, WW.

    I will go ahead and resolve this thread for now, but feel free to post back here if you have further related questions.

    Regards,

    Allison

  • OK. I will. Thanks.