• State Resolved
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 26 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSPM33C321A: Ease of Porting Code Between the MSPM0 and MSPM33

Michael V
Intellectual 496 points

Part Number: MSPM33C321A
Other Parts Discussed in Thread: MSPM0G5117, SYSCONFIG,

Hello,

I received a question on software compatibility between the MSPM0G and MSPM33 from one of my clients, and would appreciate some insights into the similarities/differences, and ease of porting code between the two SDKs. 

My client plans to use a dual-MCU architecture (MSPM33C321 as main + MSPM0G5117 as sub MCU) and would like to reuse as much code as possible between the two.

I have currently explained that much of the DriverLib appears to be shared/similar between the two, and that application code using the same peripherals may be reusable with minor adjustments.

However, I am only able to speak vaguely on the topic, so I would appreciate assistance with the following:

  1. What are the main similarities and differences between the MSPM33 and MSPM0 SDKs?
  2. How easy is it to port software between the two? What can be reused, what can't be reused?
    1. Please also provide application notes or helpful documents if any exist.
  3.  Are there any current or planned features in SysConfig to support easier migration or cross-device configuration reuse between MSPM0 and MSPM33?
    1. (similar to how switching between different MSPM0 devices is currently supported)

Code reusability/porting is a key factor for them in their part selection so I would appreciate any helpful information.

Best regards,

Michael

  • +1
    TI__Intellectual 2550 points

    Hi Michael,

    The for specifically the MSPM33 and MSPM0 SDK's we tried to keep the driver libs extremely similar. There's two only two key differences between the two.The MSPM33C321A has an HSADC that has a different architecture than the MSPM0G5117 device. The other difference is the Trustzone integration so peripherals like the GSC and EAM are new to this device. If you don't need trustzone it's not a big deal and you can refrain from using the GSC and EAM peripherals.

    All other peripherals are extremely similar and have similar API's. 

    For the last point we are looking into some porting tools to migrate between the MSPM33 and MSPM0 SDK's but we don't have a confirmed timeline.