Unable to connect to F28M36 using Uniflash and Code Composer

Isaac Abbott

Other Parts Discussed in Thread: UNIFLASH, F28M36P63C2

For the past year I have been developing on a Concerto F28M36 with no problems. I use Code Composer Studio v6 for debugging and Uniflash v3 to just do program updates.

Recently I starting on a second project using the Tiva TM4C129. When I started this project I had to add support to CCS and Uniflash. This involved re-installing both products and selecting Tiva support. This all went smoothly and I am able to connect to the Tiva part using ICDI.

Around this same time, however, I started getting this error when I try to connect to the Concerto Part:

[14:07:37] ERROR >> Cannot read System Setup data from XML file C:\ti\uniflashv3\Digital Accumeasure Configuration\F28M36P63C2_xds200.ccxml
Error parsing file:
Fatal Error at (0, 0): An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=C:\ti\uniflashv3\ccs_base\common\targetdb\Modules\C2000\28M36_Comp_Registers.xml while parsing file: C:\ti\uniflashv3\ccs_base\common\targetdb\Modules\C2000\28M36_Comp_Registers.xml
[14:07:37] com.ti.debug.engine.IApplication$InitializationException: Cannot read System Setup data from XML file C:\ti\uniflashv3\Digital Accumeasure Configuration\F28M36P63C2_xds200.ccxml
Error parsing file:
Fatal Error at (0, 0): An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=C:\ti\uniflashv3\ccs_base\common\targetdb\Modules\C2000\28M36_Comp_Registers.xml while parsing file: C:\ti\uniflashv3\ccs_base\common\targetdb\Modules\C2000\28M36_Comp_Registers.xml

It happens in both CCS and Uniflash. I completely re-installed Code Composer and that didn't help. It also happens in Uniflash when I attempt to create a new Target Configuraiton. It is almost as if the TI XML parsing tool is broken (the ccxml file is there), but it works correctly with the Tiva part.

The error is slightly different in CCS:

Cannot read System Setup data from XML file C:\Isaac\projects\Bootloader-M3\targetConfigs\F28M36P63C2.ccxml
Error parsing file:
Fatal Error at (0, 0): An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=C:\ti\ccsv6\ccs_base\common\targetdb\Modules\C2000\28M36_Comp_Registers.xml while parsing file: C:\ti\ccsv6\ccs_base\common\targetdb\Modules\C2000\28M36_Comp_Registers.xml

over 11 years ago

0 Isaac Abbott over 11 years ago

Intellectual 805 points

Update: I configured Uniflash to use the XDS200 Emulator with the Tiva part and it did not give me an error. Next I tried to use a different emulator to connect to the Concerto and they all produced the same error. The problem seems to follow the Concerto.

0 desouza over 11 years ago

TI__Guru**** 171819 points

Hi,

I was able to program my F28M36 board here, but I am using Uniflash 3.1.

The error message indicates you have somehow a corrupt/non-existing file in your Uniflash install:

The primary document entity could not be opened. Id=C:\ti\uniflashv3\ccs_base\common\targetdb\Modules\C2000\28M36_Comp_Registers.xml while parsing file: C:\ti\uniflashv3\ccs_base\common\targetdb\Modules\C2000\28M36_Comp_Registers.xml

In this case, can you see if the file above exists or if it is somehow corrupt? The one installed on my setup for comparison is shown below

Hope this helps,

Rafael

<?xml version="1.0" encoding="UTF-8" ?> 
<!-- 
  TI File $Revision: 
  Checkin $Date: 
  --> 

<!--  C28M35x COMP REGS Registers 
     =================================== 
     The offsets noted below are based on the base address that is specified in the device file that includes this file 
     --> 
<module id="COMP REGS" HW_revision="" XML_version="1" description="COMP REGS Registers">
    <register id="COMPCTL" acronym="COMPCTL" offset="0" page="1" width="16" description="Comparator Control" />
    <!--  1 empty  -->
    <register id="COMPSTS" acronym="COMPSTS" offset="2" page="1" width="16" description="Compare Output States" />
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <register id="DACVAL" acronym="DACVAL" offset="6" page="1" width="16" description="10-bit DAV Value" />
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  1 empty  -->
    <!--  2 empty  -->
</module>

0 Isaac Abbott over 11 years ago in reply to desouza

Intellectual 805 points

Hi Rafael, thank you for your response.

These files are identical.

I don't think the problem is Uniflash itself because I get the same error in Code Composer Studio, just with a different path:

This started happening after I installed Uniflash, so I suspect that Uniflash corrupted something, but it may be unrelated.

0 desouza over 11 years ago in reply to Isaac Abbott

TI__Guru**** 171819 points

Hi,

Hmm, I see. I agree with your suspicion if the issue started to happen after Uniflash was installed.

What is interesting is that I did not get this issue in my setup, and I have installed Uniflash after CCSv6.

This is a long shot, but can you perhaps try to uninstall or reinstall Uniflash and see if you get back the CCS functionality?

http://processors.wiki.ti.com/index.php/Category:CCS_UniFlash_Release_Notes_Archive

To uninstall a component, check section 6 of the page below:

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

Hope this helps,

Rafael

0 Isaac Abbott over 11 years ago in reply to desouza

Intellectual 805 points

I uninstalled Uniflash, old versions of Code Composer and a few other TI applications that were hanging around that I no longer used. The problem persists.

I could try uninstalling and re-installing Code Composer, though I did this last week.
Are there other drivers that a re-install of Code Composer won't touch that could've been corrupted?

Thanks,
Isaac

0 desouza over 11 years ago in reply to Isaac Abbott

TI__Guru**** 171819 points

Isaac,

I know now what is happening: I have multiple versions of CCS and one of them uses the C2000 Device Support release 4.1.1.0 which does not display this issue. However, another release has a TI C2000 Device Support release 4.1.3.0 and shows this issue - along with additional F28M36 devices (the release 4.1.1.0 has only F28M36P63C2).

Therefore, I updated the working copy to 4.1.3.0 and it started showing this issue as well.

Unfortunately I couldn't find previous releases of this component at the CCS update site (probably removed by the C2000 folks), therefore you would have two options: either reinstall CCS or copy the original C2000 component from the CCS full install directory and install it in your existing directory

To do that second option, uninstall the TI C2000 Device support component (check section 6 of this page) and you must have the original full CCS installer (the 800MB .zip file). Inside this package, locate the file below, copy it to a temp directory and rename it to .zip

/featurerepo/binary/com.ti.c2000.support.win32_root_4.1.1.0

Unzip this file and then you will find another .zip file inside: ti_c2000support_setup_4.1.1.0.zip. Unzip this file under the <CCS_INSTALL_DIR>/ccsv6

That should restore the previous functionality.

Regards,

Rafael

0 desouza over 11 years ago in reply to desouza

TI__Guru**** 171819 points

Isaac,

I just located the issue: the error message mentions the file 28M36_Comp_Registers.xml is missing, and in fact it is. The filename on the disk is, in fact, 28M36x_Comp_Registers.xml.

That really escaped my eyes.

Therefore a third option is available: simply edit the file(s) f28m36*.xml under <CCS_INSTALL_DIR>/ccsv6/ccs_base/common/targetdb/devices and add the "x" to the entry in the XML file.

For example, the f28m36p63c2.xml has these entries at lines 118~123. Simply replace them with the following:

<instance href="../Modules/C2000/28M36x_Comp_Registers.xml" id="COMP1" xml="28M36x_Comp_Registers.xml" xmlpath="../Modules/C2000/" HW_version="" description="Comparator 1 Register" requestor="" baseaddr="0x006400" endaddr="0x00641F" size="0x0020" accessnumbytes="4" permissions="p" /> 
<instance href="../Modules/C2000/28M36x_Comp_Registers.xml" id="COMP2" xml="28M36x_Comp_Registers.xml" xmlpath="../Modules/C2000/" HW_version="" description="Comparator 2 Register" requestor="" baseaddr="0x006420" endaddr="0x00643F" size="0x0020" accessnumbytes="4" permissions="p" />
<instance href="../Modules/C2000/28M36x_Comp_Registers.xml" id="COMP3" xml="28M36x_Comp_Registers.xml" xmlpath="../Modules/C2000/" HW_version="" description="Comparator 3 Register" requestor="" baseaddr="0x006440" endaddr="0x00645F" size="0x0020" accessnumbytes="4" permissions="p" />
<instance href="../Modules/C2000/28M36x_Comp_Registers.xml" id="COMP4" xml="28M36x_Comp_Registers.xml" xmlpath="../Modules/C2000/" HW_version="" description="Comparator 4 Register" requestor="" baseaddr="0x006460" endaddr="0x00647F" size="0x0020" accessnumbytes="4" permissions="p" />
<instance href="../Modules/C2000/28M36x_Comp_Registers.xml" id="COMP5" xml="28M36x_Comp_Registers.xml" xmlpath="../Modules/C2000/" HW_version="" description="Comparator 5 Register" requestor="" baseaddr="0x006480" endaddr="0x00649F" size="0x0020" accessnumbytes="4" permissions="p" />
<instance href="../Modules/C2000/28M36x_Comp_Registers.xml" id="COMP6" xml="28M36x_Comp_Registers.xml" xmlpath="../Modules/C2000/" HW_version="" description="Comparator 6 Register" requestor="" baseaddr="0x0064A0" endaddr="0x0064BF" size="0x0020" accessnumbytes="4" permissions="p" />

Hope this helps,

Rafael

0 WJ over 11 years ago in reply to desouza

Intellectual 340 points

Hi Rafael,

I had the same issue.

Your advice works for now.

Best regards,

0 Isaac Abbott over 11 years ago in reply to desouza

Intellectual 805 points

Rafael,

Thank you for your response, and sorry for my delayed response. For some reason, I didn't get any emails on Dec. 8 when you replied, so I didn't see the fix until just now when WJ posted.

I have made the changes to the f28m36p63c2.xml file with success, and I am back in business. This is great timing, too, since I am in the midst of a significant re-work of Concerto software!

Thanks again,
Isaac

Code Composer Studio™︎

Code Composer Studio forum

Unable to connect to F28M36 using Uniflash and Code Composer