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.

MSPM0G3507: Setting up project environment that will compile and flash to hw on both Windows and Mac.

Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG,

Tool/software:

This forum post is on behalf of professor Jonathan Rogers at Georgia Tech (jonathan.rogers@ae.gatech.edu) who has 50 students in a graduate mechatronics class.  FIRST semester using the M0.  If they can't get help with the issues below, they aren't sure they can use TI products for the course. 

"We used MSP432 devices in the past and are now revising the class around the MSPM0 architecture. As we are going through the process of updating the class material, I have encountered some difficulties just in the process of setting up projects and developing lab assignments that will work for our students. The MSPM0 and MSP32 architectures are quite different so it has become apparent that we will need more than just cosmetic updates to the labs and lectures.

The first issue is setting up a project environment that will compile and flash to the hardware successfully on both Windows and Mac.  I have gotten this to work using the Sysconfig tool, but we are hoping to not use Sysconfig as I am trying to teach students the basics (register access, macros, bit-level manipulation in registers, etc) and Sysconfig hides much of this".

"Can you assist me in creating a project setup workflow that will compile and flash successfully, and also avoid using Sysconfig?  I can provide the error messages we are seeing to give you more detail.  Just let me know if this is something you are willing to help with and we can go from there".

  • Hi John,

    • For an IDE, I would recommend using CCS on both the Windows and Mac. The SDK is also available for both platforms (and linux).
    • For register level programming, there is a default example in the driverlib folder called "empty_non_sysconfig" which will remove the SysConfig from your projects. Here's the default file path C:\ti\mspm0_sdk_2_02_00_05\examples\nortos\LP_MSPM0G3507\driverlib\empty_non_sysconfig
    • We use SysConfig for ease of configuring, if you click into the functions that are called by SysConfig and DriverLib you will get the register writes that are happening to the physical device. This can help you abstract from the C level to the metal layer. I often will do direct register access to help speed up critical functions.

    Regards,
    Luke