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

POWERSUITE: Changing Device in PowerSuite Example

Nishka Rao
Intellectual 1466 points
Part Number: POWERSUITE
Other Parts Discussed in Thread: SYSCONFIG, TIDA-01606, TMS320F28388D, TIDA-010236, SFRA,

Hi Team,

I'm looking to modify several reference designs, such as TIDA-01606 and TIDA-010236, to use a different C2000s, TMS320F28388D. The peripheral set of the F28388D would be compatible with the usage of the reference designs but when I change the device through SysConfig, I get build errors and greyed out sections of the reference design. Is there a process that would be recommended to migrating the code from one C2000 to another?

Thanks!

  • +1
    TI__Intellectual 2266 points

    Hi Nishka, 

    As far as migration goes there isn't a formal process, most of migration works fine after switching to a different device. In your particular case however, F2838x comes with default fpu64 support, which is different than F2837x's fpu32 support. And that is the reason why you're seeing the errors about data mismatch here.

    One possible solution is within your project Properties-> Build -> C2000 Compiler -> Specify floating point support (--float_support), you could change that to fpu32 to maintain the data matchiness. 

    Or if you wanted to leverage the performance of fpu64, we also do offer sfra_f64_eabi.lib/sfra_f64_tmu_eabi.lib that is in fpu64, you could try to use this library instead. Simply go to Properties-> Build -> C2000 Linker -> File Search Path and modify the corresponding sfra lib name should suffice.

    Best,

    Sen Wang

  • 0 in reply to Sen Wang
    TI__Intellectual 1466 points

    Thank you so much! The one other change I assume would have to be made is the pin mux configuration as they are different devices. It seems like in at least TIDA-01606 the pin mux is defined in tinv_user_settings.h and set up in tinv_hal.c.

    Are those 2 files modified by the SYSconfig Gui?

    Would I have to manually change the pinmux to use the new device?

    Thanks!

  • 0 in reply to Nishka Rao
    TI__Intellectual 2266 points

    Hi Nishka,

    On the top, righthand corner of the main.syscfg GUI interface it would show you all the generated files produced by sysconfig. In the case of TIDA-01606, the generated file (tinv_settings.h) only holds controller and powerstage parameters but not the pinmux that you mentioned.

    Therefore you would have to edit tinv_user_settings.h and tinv_hal.c manually to change pinmux and peripheral settings.

    Additionally, DPSDK's PowerSUITE only contains a subset of the full sysconfig feature, switching the device under PowerSUITE doesn't actually switches the respective driverlib and target configuration. Therefore you also would need to switch to F2838x's driverlib and targetConfig (.ccxml) manually.

    I don't recall if f2837x and f2838x shares the same driverlib API, but If they do (meaning no function not found errors in tinv_hal.c once you've switched driverlib and targetConfig and build the project), then you don't necessarily have to edit tinv_hal.c.

    Best,

    Sen Wang