• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 199 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSPM0G1107: #10010 error.

Muhammed Hakbilen
Prodigy 90 points
Part Number: MSPM0G1107
Other Parts Discussed in Thread: TIDA-010243, MSPM0G3507, SYSCONFIG

Tool/software:

Hi,

Description  Resource      Path   Location       Type

#10010 errors encountered during linking; "TIDA-010243-MSPM0G3507.out" not built   TIDA-010243-MSPM0G3507                          C/C++ Problem

 

https://www.ti.com/tool/TIDA-010243

I use TIDA-010243 firmware. I built for MSPM0G1107 but ı get error.

I use CCS platform.

Best regards

  • 0
    Expert 1310 points

    The #10010 error in Code Composer Studio (CCS) during linking typically indicates a problem with the linking process, such as missing or incompatible files, incorrect project configuration, or resource issues.

  • 0 in reply to Zain Nasir
    Prodigy 90 points

    This code was compiled for MSPM0G3507. I tried to translate it to MSPM0G1107, apparently I couldn't. How can I code this code, that is, the firmware, according to MSPM0G1107?

  • 0 in reply to Muhammed Hakbilen
    TI__Mastermind 28070 points

    Hi Muhammed,

    Welcome to the E2E Forums.

    How did you try to port this to MSPM0G1107?

    Starting from the default project, the easiest way is probably to go to the device view in sysconfig and hit "Switch"

    Then select your device and package in the dialog box that opens:

    After that I would recommend you exclude the MSPM0G1107 linker file from the build, as the linker in the project is custom and includes some different memory regions.

    Since these devices have the same memory sizes you should be fine to use the MSPM0G3507.cmd linker. 

    Give that a try after importing the default project, and let me know if you still see an error.

    Best Regards,
    Brandon Fisher

  • 0 in reply to Brandon Fisher94
    Prodigy 90 points

    I set it up like this.

    I get the same error again.

  • 0 in reply to Muhammed Hakbilen
    Prodigy 90 points

    by the way, it gave this error at first and after deleting the functions it gave the above error.

  • 0 in reply to Muhammed Hakbilen
    TI__Mastermind 28070 points

    This example code includes the linker and startup files in the project, but it looks like you have linker/startup file generation on in SysConfig. Can you disable this? 

    The automatically generated linker doesn't include the custom regions used in this code. Syconfig will generate a warning when you do this, but you can ignore or suppress that warning. 

    Best Regards,
    Brandon Fisher