TMS320F28379D: CLI uniflash package 8.8.1 does not recognize FlashEraseSelection setting

Hi Piotr,

Thank you for the logs and file. I will be taking a look at this tomorrow.

Thanks

ki

I have tried reproducing this on a variety of machines including WIndows 10, Ubuntu 22.04, and Ubuntu 24.04 (which is not officially supported by UniFlash). All my generated standalone packages with FlashEraseSelection being used did not cause any issue. They have all been successful.

Would it be possible to share your standalone package?

Hi Ki,

I isolated the problem. 

I have configuration file generated in CCS (I needed power supply for JTAG isolation adapter). When I use my f28379d.ccxml file the error appears. 
f28379d.ccxml from the uniflash generated package works fine.

I executed following command line (f28379d.ccxml - is one of two versions listed below):

sudo ccs_base/DebugServer/bin/DSLite flash -c f28379d.ccxml -l user_files/settings/generated.ufsettings -s VerifyAfterProgramLoad=No verification -e -f -v user_files/images/Bootloader_cpu02-part2.hex -n 2

My f28379d.ccxml from CCS:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
                    



    
    <configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
                
        <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
                
        <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
                        
            <instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
                        
            <instance XML_version="1.2" href="drivers/tixds510c28x.xml" id="drivers" xml="tixds510c28x.xml" xmlpath="drivers"/>
                        
            <instance XML_version="1.2" href="drivers/tixds510cla1.xml" id="drivers" xml="tixds510cla1.xml" xmlpath="drivers"/>
                        
            <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
                        
            <property Type="choicelist" Value="1" id="Power Selection">
                <choice Name="Probe supplied power" value="1">
                    <property Type="stringfield" Value="3.3V" id="Voltage Level"/>
                    <property Type="choicelist" Value="1" id="Power Isolation"/>
                </choice>
            </property>
            <property Type="choicelist" Value="1" id="The JTAG TCLK Frequency (MHz)">
                <choice Name="Fixed with user specified value" value="SPECIFIC">
                    <property Type="stringfield" Value="3.0MHz" id="-- Enter a value from 100.0kHz to 2.5MHz"/>
                </choice>
            </property>
            <platform XML_version="1.2" id="platform_0">
                                
                <instance XML_version="1.2" desc="TMS320F28379D_0" href="devices/f28379d.xml" id="TMS320F28379D_0" xml="f28379d.xml" xmlpath="devices"/>
                                
                <device HW_revision="1" XML_version="1.2" description="" id="TMS320F28379D_0" partnum="TMS320F28379D" simulation="no">
                                        
                    <router HW_revision="1.0" XML_version="1.2" description="ICEPick_C router" id="IcePick_C_0" isa="ICEPICK_C">
                                                
                        <subpath id="Subpath_1">
                                                        
                            <property Type="numericfield" Value="0x11" desc="Port Number_0" id="Port Number"/>
                                                    
                        </subpath>
                                            
                    </router>
                                    
                </device>
                            
            </platform>
                    
        </connection>
            
    </configuration>
    
</configurations>

f28379d.ccxml from uniflash:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="configuration_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe">
        	
        		   <instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
        	
        		   <instance XML_version="1.2" href="drivers/tixds510c28x.xml" id="drivers" xml="tixds510c28x.xml" xmlpath="drivers"/>
        	
        		   <instance XML_version="1.2" href="drivers/tixds510cla1.xml" id="drivers" xml="tixds510cla1.xml" xmlpath="drivers"/>
        	
        		   <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
        	
            
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F28379D" href="devices/f28379d.xml" id="TMS320F28379D" xml="f28379d.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

The error message was misleading.

What is wrong with my ccxml file?

Regards,

Piotr Romaniuk

PS
I used following  generated.ufsettings:

{"Texas Instruments XDS110 USB Debug Probe/C28xx_CPU1":{"FlashEraseSelection":"Necessary Sectors Only (for Program Load)"},"Texas Instruments XDS110 USB Debug Probe/C28xx_CPU2":{"FlashEraseSelection":"Necessary Sectors Only (for Program Load)"}}

I am currently using the F28379D LaunchPad with onboard XDS100. I will have to try an F2837xD setup using an XDS110. I will give this a try tomorrow.

Hi Ki,

Ki said:

I suspect that you generated the command-line package using the default ccxml file generated by UniFlash and then swapped in your custom one afterwards?

Yes. The file generated.ufsettings was from uniflash generated package, and .ccxml was taken from CCS. I was not aware that it is needed for proper (consistent) settings creation. 

Ki said:

Assuming that is the case, you should instead specify your custom ccxml file to open the UniFlash session and then generate the standalone package. This would make sure the debug probe names match across all the files

Thank you for the suggestion.
I had limited control over GUI flash it was very slow in previous version. I see that new version (8.8.1) works fine - it is usable and responsive.
I will remember that ccxml should be entered into uniflash at the begining of the session.

Thank you for the solution.

Regards,

Piotr Romaniuk

Piotr Romaniuk said:

I see that new version (8.8.1) works fine - it is usable and responsive.

That is good to hear! Thanks for this feedback.