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.

CCSTUDIO: Program loading procedure using CCS

Part Number: CCSTUDIO
Other Parts Discussed in Thread: TM4C129ENCZAD

Hello fellow TI engineers.
Write the program to TM4C129ENCZAD (IC on custom board) using LAUNCHXL-1350.


I want the TM4C129 to have the functionality of StandAlone's XDS110.

After that, I have two questions.

1. Check if there is a procedure to read from CCS
First I set the Target Configuration.

I connected with the following settings.

And I chose Core. (CORTEX_M4_0)

After this, I did a Test Connection and got the following response.


The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe_0]


Next, I connected the target and the Debugger.

Are there any problems with the steps up to this point?

2. Program load
It's the .axf file I mentioned before.
Then the console file showed the following results:

What could be the cause?

  • Are there any problems with the steps up to this point?

    No, it looks good so far.

    2. Program load
    It's the .axf file I mentioned before.
    Then the console file showed the following results:

    What could be the cause?

    The default behavior of CCS debugger is to auto-run to the 'main' function on program load. But if the program that is loaded does not have a 'main' function, then you will get the message you see and the program will continue to run. The axf file you loaded does not appear to have a 'main' function. This is not an error of any sort.

    You can disable auto-run in the debugger properties:

    https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#auto-run-and-launch-options

    Thanks

    ki

  • Hello, thank you for your kind reply.

    I understand that step 1 is correct.
    By the way, the target-debugger connection means that the internal core of TM4C129ENCZAD and the debugger are firmly connected.

    There is no error in the program loading procedure in 2.
    By the way, does that mean that the boot_loader.axf file was successfully loaded if there were no errors?
    Please let me know what console message you get if successful.

    -------------------------------------------------- -----------------------
    Add question.

    ・By the way, the program file I loaded the other day is the boot_loader.axf file, is there any problem?
    C:\ti\ccs1220\ccs\ccs_base\common\uscif\xds110

    ・As I mentioned earlier, if there is no error, do you want to proceed to the procedure to load firmware.bin as it is?

    ・I found the countermeasure item you suggested.


    However, even if Run to symbol was left blank in this item, a warning was issued that it would become a running state if some kind of box was enabled.
    (referenced text)
    software-dl.ti.com/.../ccs_debug-main.html

    7.2.3. Debug Properties
    'Project Properties → Debug (if target configuration file is part of the project), or
    Right-click on the target configuration file in Target Configurations view and select Properties.
    Note that if you are using the first option above, you need to have already specified a Connection in your Project Properties in order for the Debug Properties to be populated. file and show the Properties based on that file which may be incorrect/not match up with your device, so make sure you have the correct Connection selected for your project.'

    What specific fields should be left blank?

  • By the way, a file called uscif.out was also in ccs_base.

    What exactly is this file for?
    What is the purpose of the .out files in the C:\ti\ccs1220\ccs\ccs_base\common\uscif hierarchy?

    I would appreciate it if you could tell me each.
    (I can't find it even if I look for the documentation.)

  • By the way, does that mean that the boot_loader.axf file was successfully loaded if there were no errors?

    Yes. But it does not guarantee that it will run correctly.

    Please let me know what console message you get if successful.

    You will know if a program was not successfully loaded with some kind of error message. 

    However, even if Run to symbol was left blank in this item, a warning was issued that it would become a running state if some kind of box was enabled.

    Disable "On a program load or restart" check box. This prevent the target from running after program load.

  • Hello, Thank you for your kindness.

    Future communication will be done in the following thread or private message.

    e2e.ti.com/.../4489401

  • After all, I think that the following command is not executing the program?

  • After all, I think that the following command is not executing the program?

    The "AutoRun" message indicates that the target is running. 

    Assuming that you loaded the program (*.axf) successfully, the program should be running unless you manually halted the target 

  • OK, Thank you!

    Is it correct to understand that boot_loader.bin is boot_loader for XDS110 and is different from Boot_loader.bit for Tiva Device?

  • Is it correct to understand that boot_loader.bin is boot_loader for XDS110 and is different from Boot_loader.bit for Tiva Device?

    There is only one boot_loader.bin that i am aware of. What is Boot_loader.bit?

  • thank you for your reply.
    It means boot_loader.bin.

  • There is only one boot_loader.bin (which is the binary from boot_loader.axf). This one boot_loader.bin is designed to work with a few supported Tiva devices that is recommended for XDS110 development.