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.

CortexR4: Can't Run Target CPU: (Error -1141 @ 0x1FE)

Other Parts Discussed in Thread: RM48L952, HALCOGEN

Hi,

I want debugging my code. When I push the "debug as ---> 1 .code composer debug session", I got a error showed below.

CortexR4: Can't Run Target CPU: (Error -1141 @ 0x1FE) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)

I have tested the Jtag by push " test connect" button many times, The Jtag interface never failed.

The CCS can erase flash and program, but it just enter the debug status when the code is simple and some times it was dead at load sign after erase flash  and some times CCS was stop by system.

I use the CCS  5.4.0.00091 , usb100v2-arm and HALCoGen 03.05.02 for my RM48L952 MCU PCB.

 

Thanks,

chuan

  • Chaun,

    How many different projects are in your workspace, and do they have different target configuration files.

    Sometimes I get this and the problem is as simple as I've got the XDS560v2 type emulator target configuration set as [ACTIVE/DEFAULT] but I'm trying to do the load on a project where the board is supposed to be using XDS100v2.

    In other words, one simple explanation is that the emulator you think you are using might not actually be selected.   Make sure it's got [active/default] both set after it...

    Of course this is not the only explanation but we have to start checking with the simple ones ...

  • Hi Anthony,

    Thanks for your reply.

    There is only one project in my workspace. There are two target configuration files, but one of them is not ACTIVE.

    This is my  target configuration files with "active" attribute:

    <?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 XDS100v2 USB Emulator_0">

            <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Emulator_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Emulator_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>

            <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Emulator_0">

                <instance XML_version="1.2" href="drivers/tixds100v2icepick_c.xml" id="drivers" xml="tixds100v2icepick_c.xml" xmlpath="drivers"/>

                <instance XML_version="1.2" href="drivers/tixds100v2cs_dap.xml" id="drivers" xml="tixds100v2cs_dap.xml" xmlpath="drivers"/>

                <instance XML_version="1.2" href="drivers/tixds100v2cortexR.xml" id="drivers" xml="tixds100v2cortexR.xml" xmlpath="drivers"/>

                <platform XML_version="1.2" id="platform_0">

                    <instance XML_version="1.2" desc="RM48L952_0" href="devices/rm48l952.xml" id="RM48L952_0" xml="rm48l952.xml" xmlpath="devices"/>

                </platform>

            </connection>

        </configuration>

    </configurations>

     

     

    This is my target configuration files advanced window.

    This is CCS' picture with a error  after I want enter a debug status.

    It is seem enter the debug status and running the code, but the  target  PCB did not anything. When I exit the debug status and reset the   target  PCB , it works correct. So I think the code have been programmed and debugging did not work.

    Would you help me to find something wrong in my  target configuration files.

    Thanks,

     

    Chuan

     

  • Hi Chuan,

    If you can connect then I think your target configuration file is fine.

    It may be something in the code that you flashed;  if this code changes the PLL or some other settings inappropriately you might have difficulty connecting until the reset is performed.

    Would you please try just erasing the flash after connecting and then see if you can connect to this erased part reliably?

     

  • Hi Anthony.

    Thanks for your reply.

    Everything is fine right now. CCS can debug my code. the problem was caused from my code.

    Thanks.

     

    Chusn

  • Hi Anthony,

    Sorry. The " RM48x 16/32-Bit RISC Flash Microcontroller Technical Reference Manual " is  the " SPNU503B".

    I just notice it.

     

    Thanks,

     

    B.Rs,

     

    Chuan