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.

Registers View issue with C5505

Dear Team,

My customer has an issue after update CCS to version 4.1.3.00038:

The "Registers"-View don´t show the right values of the register contents according to their register address.

For example, the register PCGCR1 (Periperal Clock Gating Configuration Register 1) shows the value that is stored at the location 0x001C02@PROGRAM but it should be 0x001C02@I/O. If I don´t be mistaken this problem occurs aproximately after the last software update of CSS. How can I resolve this problem?

Have you observed this behavior before?

Thanks and Regards,

Sergio Ortega

  • Sergio,

    We had another report of this the other day.  It was for a different register group but the problem is the same.  Basically there is an issue with some of the peripheral register definition files in 4.1.3 and 4.2.0 where they don't define that the register is on the I/O page.  I will find an updated file and attach it to this post.

    Regards,

    John

  • Sergio,

    The attached zip file contains a version of the peripheral register files with the proper page information.  Inside the zip there is a \C5505 folder replace the contents of your \ccsv4\common\targetdb\Modules\C5505 folder with the contents of the folder in the zip. 

    3146.C5505.zip

     

    Regards,

    John

  • The suggested fix to replace those XML files causes my CCS v4 installation to become corrupted (v4.2.3.00004 on Windows 7).

    If I do a clean install of CCS v4, I can connect to the target and debug my project.  But if I overwrite those XML files, CCS crashes (repeatedly) when I try to 'Debug Active Project'

    Here is the error message:

    Restoring the original XML files does not fix the problem.  Note that I can still debug a C6000 target, but not the C5505.

    One of my co-workers also tried this on his computer with the same results.

    The only work-around we found was to:

    1. Uninstall CCS v4 (and manually delete all remaining files in the "Texas Instruments" directory, except the license file)
    2. Install CCS v4
    3. Replace the XML files BEFORE running CCS v4 for the first time after install
    4. Run CCS v4

    Eclipse is such a ghetto IDE

  • Justin,

    The crashing issue is likely not Eclipse but an issue with xml file caching.  For performance reasons the debugger creates a cache file that represents an expansion of all the xmls referenced by your target configuration.  It could be that when dropping in the fixed xmls that cache file is not being regenerated.  If the files dropped in are newer it should detect this and regenerate it but we have seen cases where that does not happen.   There is info on how to delete the cache files here: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#Debugger

    I am pretty sure this is the problem you are seeing since if you drop in the files before running CCS the cache files would not have been created.

    Regards,

    John

     

  • Thanks, John.  Deleting the target cache files worked.

    Are there plans to fix these XML files in a release of CCS?

  • Jeremy,

    They are supposed to be fixed up in 4.2.4.

    Regards,

    John