• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 85 subscribers
  • Views 570 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28P650DK: How to resolve load program error?

Rishitha
Prodigy 115 points
Part Number: TMS320F28P650DK
Other Parts Discussed in Thread: C2000WARE

  • +1
    TI__Mastermind 27486 points

    Hi Rishitha,

    Have you tried loading a basic C2000WARE Example first like the led or gpio project?

    Looks like you may be loading an incorrect file for a different device. Are you using the C2000WARE's SDK version for the target configuration files then loading your .out file?

    Could you try and restart the device, terminate the debugging session and try to reconnect to the device?

    Best,

    Ryan Ma

  • 0 in reply to Ryan Ma
    TI__Mastermind 32400 points

    Hi Ryan,

    yes, I rebuild the project and good following error when downloading:

    C28xx_CPU1: GEL Output:
    Memory Map Initialization Complete
    C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
    C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. User code execution from SR could commence after the selected CPU1/CPU2 flash banks executable are programmed.
    C28xx_CPU1: Only CPU1 on-chip Flash Plugin can configure clock for CPU1, and CPU2 Flash operations. Plugin automatically configures PLL when CPU1 Flash operations are invoked. However, if users want to do only CPU2 Flash operations without doing a prior CPU1 operation in the current session, they should click on 'Configure Clock' button in CPU1's on-chip Flash Plugin before invoking CPU2 Flash operations. When this button is used, Flash Plugin will configure the clock for CPU1/CPU2 at 200MHz using INTOSC as the clock source. Plugin will leave PLL config like this and user application should configure the PLL as required by application.
    C28xx_CPU1: Before doing any flash operations using the flash plugin, (a) Please select which flash banks should be mapped to which CPU (CPU1 vs CPU2) - This selection should be done in CPU1 flash plugin GUI. (b) Please select the flash banks that the user would like the flash plugin to erase (in the CPU1 flash plugin GUI and the CPU2 flash plugin GUI)
    C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x10058: (Error -1066 @ 0x10058) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 12.6.0.00029)
    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
    C28xx_CPU1: GSxMSEL register configured correctly
    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x10058: (Error -1066 @ 0x10058) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 12.6.0.00029)
    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x100e6: (Error -1066 @ 0x100E6) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 12.6.0.00029)
    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
    C28xx_CPU1: Error writing the init algorithm. Flash algorithm returned error code. Operation cancelled.
    C28xx_CPU1: File Loader: Memory write failed: Unknown error
    C28xx_CPU1: GEL: File: C:\Users\a0406234\workspace_v12_6\gpio_ex2_toggle\CPU1_FLASH\gpio_ex2_toggle.out: Load failed.
    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x10058: (Error -1066 @ 0x10058) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 12.6.0.00029)
    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    Regards, Holger

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/171/f28p65.ccxml

  • 0 in reply to HS FAE Germany
    TI__Mastermind 27486 points

    Hi Holger,

    Thank you for providing the .ccxml, i will try and see if i can replicate this issue with this specific example and report back.

    Best,

    Ryan Ma

  • 0 in reply to Ryan Ma
    TI__Mastermind 27486 points

    Hi Holger,

    In your .ccxml, are you using XDS100v2? 

    If you're using either of our control card or launchpad there is an XDS110 on the EVM. Could you please try this .ccxml and double check to make sure you're loading the .out to CPU1's core.

    <?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/tixds510cla2.xml" id="drivers" xml="tixds510cla2.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510ajsm.xml" id="drivers" xml="tixds510ajsm.xml" xmlpath="drivers"/>
            <property Type="choicelist" Value="3" id="SWD Mode Settings"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F28P650DK9_0" href="devices/f28p650dk9.xml" id="TMS320F28P650DK9_0" xml="tms320f28p650dk9.xml" xmlpath="devices"/>
                <device HW_revision="1" XML_version="1.2" description="" id="TMS320F28P650DK9_0" partnum="TMS320F28P650DK9" 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>
                        <subpath id="Subpath_0">  
                            <cpu HW_revision="1.0" XML_version="1.2" desc="CPU1_CLA1" description="CLA Accelerator" deviceSim="false" id="CPU1_CLA1" isa="TMS192C2008"/>                     
                        </subpath>                 
                    </router>
                </device>
            </platform>
        </connection> 
    </configuration>
</configurations>

  • 0 in reply to Ryan Ma
    TI__Mastermind 32400 points

    with XDS100v2 JTAG test is successful with XDS110 it fails:

    [Start: Texas Instruments XDS110 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\a0406234\AppData\Local\TEXASI~1\
        CCS\ccs1260\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100/110/510 class product.
    This utility will load the adapter 'jioxds110.dll'.
    The library build date was 'Dec  6 2023'.
    The library build time was '17:33:10'.
    The library package version is '12.6.0.00029'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.

    An error occurred while hard opening the controller.

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-260' (0xfffffefc).
    The title is 'SC_ERR_XDS110_OPEN'.

    The explanation is:
    An attempt to connect to the XDS110 failed.
    The cause may be one or more of: no XDS110 is connected, invalid
    firmware update, invalid XDS110 serial number, or faulty USB
    cable. The firmware and serial number may be updated using the
    xdsdfu utility found in the .../ccs_base/common/uscif/xds110
    directory of your installation. View the XDS110SupportReadMe.pdf
    file there for instructions.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

  • 0 in reply to HS FAE Germany
    TI__Mastermind 36526 points

    Hi,

    Could you show me what you see in your PC's device manager? 

    Also, are you using a controlcard? Are you using the onboard debug probe, or are you using an external debug probe with the docking station? 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    TI__Mastermind 32400 points

    Hi,

    I used the wrong controlcard. Now it worked.

    Regards, Holger