• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 32 subscribers
  • Views 193 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0G3519: Error in building gpio_toggle_output code

Dibyarekha Maharana
Prodigy 100 points

Part Number: MSPM0G3519
Other Parts Discussed in Thread: SYSCONFIG

Hi,

 

Till Today I was using the gpio_toggle_output code provided by TI , it was workign fine. All of sudden the code is not building. Please help me on this. Other projects are building fine.

 

I am getting the following errorimage.png

  • 0
    TI__Expert 7025 points

    Hi, can you let me know if you changed any of the project options? I have definitely seen this before when something is changed in the project, but this could be due to several issues. Can you try importing a new copy of the project and see if the issue persists? This is usually due to some changes in the linker/start-up file or device selection, can you confirm the target device matches what is in sysconfig, ensure there are no duplicate startup/linker files?

    -Brian

  • 0 in reply to Brian Dempsey
    Prodigy 100 points

    Hi,

    I tried with a new copy, even I kept backup of my working code, both are not working. Even I imported an empty project with syscfg , that project also not building. Where is the problem I am not able to find out. where as other codes like secondary bsl and bsl software invoke, those codes are working fine.

    Please help me out

  • +1
    Guru 102595 points

    I encounter this sporadically. I don't know what sets it off, but it has to do with Debug/subdir_rules.mk "forgetting" the rule for startup_mspm0XXXX_ticlang.o.

    I work around it by using File->Add Files/Folders and providing (for your case)

    C:\ti\mspm0_sdk_2_10_00_04\source\ti\devices\msp\m0p\startup_system_files\ticlang\startup_mspm0g351x_ticlang.c

    to the Project.

  • 0 in reply to Bruce McKenney
    Prodigy 100 points

    Thanks,

    But why it happened like this, any reasons?

  • 0 in reply to Dibyarekha Maharana
    Guru 102595 points

    subdir_rules.mk is generated by (I suppose) Sysconfig. I don't know what triggers a (re-)generation, nor why it would be (re-)generated incorrectly.

  • 0 in reply to Bruce McKenney
    Prodigy 100 points

    Hi,

    Now in every project , I am getting the same error, after adding the file in this project, now in the given path the file is not present.

    Will it effect in firmware upgrade. I mean whatever .bin file I am generating if I am flashing the code from CCS its working but if I am doing fimrware upgrade its not running. Is there any such effect? 

    I have some earlier .bin file have size 2432 bytes, that is running fine with firmware upgrade but now i have generated a file of 3044bytes and when I am doing firmware upgrade, its not running. what could be the reason? related to this I raised a question in another thread, yet its unanswerable. Could you please guid me?

    I will be waiting for your response.

    Thanks

  • 0 in reply to Dibyarekha Maharana
    Guru 102595 points

    1) One hazard of this workaround is that it effectively locks you into a particular MSPM0 variant. You've only mentioned using one variant (G3519) so I expect this isn't what you're seeing.

    2) A program built to be used in firmware upgrade typically uses a non-standard linker (.cmd) file. It seems possible that whatever is causing this (presumed) Sysconfig malfunction has also caused your project to "forget" about your alternate linker file. I suppose I haven't encountered that since I almost always use a standard one.

    I suspect the actual fix will have to be in Sysconfig, something I'm not in a position to help with.

  • 0 in reply to Bruce McKenney
    Prodigy 100 points

    Hi,

    I completely uninstalled and installed the IDE and SDK , now its working fine. But can You suggest something on firmware upgrade, why this 3020 bytes file is not working.

  • 0 in reply to Dibyarekha Maharana
    TI__Expert 7025 points

    Regarding the firmware upgrade failure with the 3020-byte file, this specific size is often a symptom of a protocol mismatch or flash alignment issue rather than the content of the file itself. A couple of reasons you may be seeing this:

    • The MSPM0 Bootloader (BSL) has a strict timer. If your file is small but being sent at a very low baud rate, or if there are long delays between packets, the BSL may timeout before the transfer completes.
    • Header and CRC Mismatch
    • Flash Sector Alignment
    • Non-Main Memory Lock
    • Bank Swap Requirements

    Could you check your update logs or the console output of your update tool? Knowing if it fails at the "Start," "Data Transfer," or "Verification/Swap" stage would pinpoint the exact cause I believe.

    -Brian