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.

What warning #10247-D means?

Other Parts Discussed in Thread: SYSCONFIG, MSPM0G1507, MSPM0G3507, LP-MSPM0G3507

Hi, ALL

My name is Tanaka.

I build project and found some error showed below.

(CCS 12.4.0, MSPM0 SDK  1.10.0.05:MSPM0G1507, SysConfig 1.17.0.

4478.error06.pptx

What warnung #10247-D means? And how can I solve this issue?

Please advice me.

Kind regards

  • You are not using a linker command file, and you need to add one.  To understand why, please see this forum post.  Please ignore all the other posts in that forum thread, as they do not apply to your project.

    My reply raises the question: What linker command file should you use, and where should you get it?  For that, I'll give responsibility for this thread to experts on the Cortex-M0+ family of products.

    Thanks and regards,

    -George

  • Hi Tanaka,

    All the linker files can be found in the SDK. Default path; C:\ti\mspm0_sdk_1_10_00_05\source\ti\devices\msp\m0p\linker_files\ticlang 

    I recommend starting with one of our example projects (gpio_toggle_output is my recommended) to verify your software environment is properly setup. These examples will include all the proper files and you can switch to the MSPM0G1507 in sysconfig.

    To switch to the MSPM0G1507, open the .syscfg file, click the top right device, and the switch button. Choose your device variant.

    Regards,

    Luke

  • Hi Luke-san

    Thank you for your advice.

    I just copy mspm0g1507.cmd from sdk, and build my project. This was the MSPM0G3507 project running correctly and I want to change CPU from 3507 to 1507.

    I changed syscfg file and I could build it, but finally I found the error showed below.

    error08.pptx

    It shows unresolved symbol interruptVectors, and I imagine that will be the issue in mspm0g1507cmd command fike description.

    I'm not well about the linker command file. Is this error concerned about command file, or any other problem?

    Can you advice how can I change command file?

    Please help me.

    Kind regards

  • Hi Tanaka,

    I want to first verify that the software environment is properly setup with the gpio_toggle_output test.

    • Can you import the gpio_toggle_output example (default path: C:\ti\mspm0_sdk_1_10_00_05\examples\nortos\LP_MSPM0G3507\driverlib\gpio_toggle_output) and build the project.
    • If no errors appear, go to the Sysconfig file and switch the device to the MSPM0G1507, then add the mspm0g1507.cmd file and exclude the mspm0g3507.cmd file (right click on the file and select exclude).
    • Rebuild the project.

    If the project builds after switching to the MSPM0G1507 device, then we will look at your project specifically. The linker file (.cmd file), is what assists in partitioning your memory into sections and varies per device/memory size. For this device, it shares the same amount of memory as the MSPM0G3507 so you could use the same linker file.

    Regards,

    Luke

  • Hi, Luke-san

    I did some setting test in accordance with your advice.

    1) I Import example gpio_toggle from SDK 1.10.0.05, change config from 3507 to 1507. Also chage cmd file from  mspm0g3507.cmd to mspm0g1507.cmd.

    Original product setting was Sysconfig: 1.16.2, SDK: 1.0.1.03, so I changed CCS setting General>Products to  sysconfgi: 1.17.0, SDK: 1.10.0.5.

    I could build project with no error showed below. (^ ^)v

    I can re-start project using this template.

    2) As for my original error project, I cannot find what is the difference to uppper no-error project.

    I tried to make new project from the first time.  Perhaps same CCS setting and main.c (no work), temporary config file mspm0g1507.syscfg, copy same cmd file.

    I found the same error that happend in my original project showed below.

    At this point, I haven't be able to find the difference of CCS setting between 1)-project and 2)-project.

    How can I close this error?

    Please advice me.

    Kind regards

  • Hello Tanaka,

    Can you explain where you are starting from with the new project? If you want to use a sysconfig enabled project, I recommend importing one of the empty examples in the SDK. I have tested all the empty examples in the SDK and switched the device to the MSPM0G1507 in both Sysconfig and with the linker file. I was not able to replicate this issue.

    If you decide you need to use the new project then I would pay attention to the differences in the include paths. I believe the issue is coming from the include options. I took a new project and below are the include options I used to include all the proper paths for the project (these are also the same includes in our example projects).

    Regards,

    Luke

  • Hi, Luke-san

    Thank you everytime for your advice.

    TI firmware development was the first time for me, so I started using LP-MSPM0G3507 eve kit. I finished to develop firmware on ths eva-board, so I started to change CPU from MSPMG3507 to 1507. But I found that I coudn't select target CPU on the syscfg menu, or I cannot re-new old .syscfg file (cannot save it, find error).

    Old project using sysconfg 1.15.0, SDK 0.56.0.01_eng, and I tried to chage CCS setting combination of sysconfig and SDK, and I imagined that sysconfig 1.15.0 cannot treat 1507 device.

    So I started to make new project, using SDK 1.10.0.5, sysconfig 1.17.0. 

    As you mentionedI, I wonder what the difference of these 1),2) project.  I again check setting, and set it with same showed below.

    CSS_setting_comp.xlsx 

    I tried to buikd again, but in the project 2), I found same error and 2 warning.

    As you said, it's safe to start project using SDK sample, and it's no problem for my bussiness.

    I just want to know "why" this issue occures, because I wonder there may be some issue on development tools.

    Kind regards

  • Hi Tanaka,

    Your original project, using SDK 0.56, was for pre-production silicon. For the build errors, moving from a pre-production device to the official device there are some backend changes in CCS to support the production version of the device, as well as some differences in the SDK with regards to API and #define names.

    More information on changes on the SDK and Sysconfig between pre-production to production can be found in the SDK (default path: C:/ti/mspm0_sdk_1_10_00_05/docs/english/early_samples_migration_guide/MSPM0_Early_Samples_Migration_Guide.html).

    Moving forward, working with the production silicon and the released SDK (1.00+), you should see no issues moving from G3507 to G1507. For directions on moving between device derivatives we have a document in the SDK (C:\ti\mspm0_sdk_1_10_00_05\docs\english\tools\ccs_ide_guide) section 2.5.

    Regards,

    Luke

  • Hi, Luke-san

    Thank you everytime for your detail explanation.

    I'm convinced about the background of the development tools, and my issues.

    When I start new project, I'll use the SDK 1.10  examples.

    Kind regards