Part Number: MSPM0G1507
Other Parts Discussed in Thread: MSPM0G3507,
I am in the process of migrating an existing CCS project from an MSPM0G3507 target to MSPM0G1507. While reviewing the project settings, I noticed that the FreeRTOS include path still references a folder named:
\freertos\config\g3507
even though the project’s device variant is now MSPM0G1507 and the code builds and runs correctly on the 1507 device. I don't see a corresponding g1507 folder.
I'm curious whether the FreeRTOS config is truly device-specific, or whether the g3507 folder name is just a convention / superset that’s reused for G1507 projects?
My questions are:
1. Does the MSPM0 SDK provide a FreeRTOS configuration that is specifically tailored to MSPM0G1507, or is the g3507 FreeRTOS configuration intended to be shared across multiple MSPM0G variants (including G1507)?
2. Is it expected behavior that a CCS project targeting MSPM0G1507 will continue to reference a \freertos\config\g3507 path?
3. Are there any functional or memory-related differences that would require a separate FreeRTOS config for MSPM0G1507, or is the existing configuration device-agnostic within the MSPM0G family?
I want to confirm that leaving this path unchanged is correct and supported, rather than an artifact of the original project template.
