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.

CCS5 Code Load Hang

Setup:

CCSv5.1.0.09000

Windows XP

XDS510Plus USB Emulator

DM6437 DSP

I have a project that successfully compiles and loads most of the time. Every now and then (most often after I disconnect and reconnect the emulator) the system will load the gel file, then load the code, and then do nothing. After a normal code load it should break at main, instead it does nothing. The emulator says its running, and if i hit pause i get "No Source available for "UTL_halt() at 0x8a8f5948". I have tried several boards, and all of them work fine with CCSV4 but have this problem with CCS5.

In order to get to work again I need to delete the project, load a different project, reload my project and try to load the code again several times. Keep in mind I am making no changes to the code itself.

I know that it is not related to my project as I can create a brand new project using the examples built into CCS and see the same issue.

Has anyone else seen this happening?

Thanks,

Mark

  • Just to add some more information. I have also tried the following.

    Compared a .map file from a working load, to one that is not working: There are no differences.

    Took a .out file that did not load, got the system in a working state and then tried to load the previously not working .out file: It successfully loaded.

    Because of the above I am fairly confident that the problem is not related to my project. I have also compared the emulator setup files (.ccxml?) and they do not change between working and non working.

    I have also duplicated this problem on a separate machine (this one being a windows 7 machine). Same emulator.

    Edit: I have also tried a new emulator (also a XDS510Plus) with the same results.

    Has anyone else seen this?

  • Mark,

    I haven't seen this happening so severely as you reported, therefore I can only comment on a few details that may help you.

    The UTL_Halt() is a BIOS function that is a landing point whenever the code reaches a conflict/crash condition that makes the system abort. Since you are getting this before reaching main(), I would carefully inspect if any hardware initialization or even a different GEL file may be the culprit. You can also try to diagnose this by de-selecting the option that runs automatically to main() and do a step-by-step initial execution. That may reveal something that can help you diagnose this.

    Also, since this seems to happen only when using CCSv5, I also wonder if a race condition in the application software may be causing this - when connected to an emulator, the code may run at different speeds depending on the CCS version, for example.

    Despite all that, the fact that CCS shows the issue repeatedly after happening just one looks suspicious. In this case I would try to delete the Debug Launch file as shown in the section Debugger of the troubleshooting page below: 

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS

    I will think about some additional aspects I may have missed and report back to this thread. 

    Hope this helps,

    Rafael