• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 30 subscribers
  • Views 3493 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Error connecting to the target: (Error -241 @ 0x0)

HaoChe Chen
Prodigy 30 points
Other Parts Discussed in Thread: RM48L952

Hello

I'm programing RM48L952 PGE, using  CCS 5.5.0.00077  by XDS100V2, 

I already did  test connection,

here is the information


This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

but when i try to debug i get 

Dap: Error connecting to the target: (Error -241 @ 0x0) A router subpath could not be accessed. A security error has probably occurred. (Emulation package 0.0.0.0)
Dap: Error connecting to the target: (Error -1265 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 0.0.0.0)

[

  • 0
    TI__Mastermind 22715 points

    HaoChe,

    It seems that you have built the cxml file and the connection test works without error. Then you need to launch a debug session with the cxml file and then connect to target (CPU). Did those steps work?

    Thanks and regards,

    Zhaohong

  • 0 in reply to Zhaohong Zhang
    TI__Mastermind 22375 points

    HaoChe,

    Which hardware board are you using? is it one of our HDK or a custom board?
    Also were you able to connect in the past and it is not working anymore? 

    Can you provide the source of your Target Configuration? Double click on your target configuration, select Advanced Setup and than click on Source. Copy past and send it to us.

     

  • 0 in reply to Jean-Marc Mifsud
    Prodigy 30 points

    Jean-Marc Mifsud,

       this hardware is a custom board,

        i just notice the error light is light on, when it turn on,

     

    Here is the source    

    <?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 XDS100v2 USB Emulator" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Emulator" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Emulator">
    <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" href="devices/rm48l952.xml" id="RM48L952" xml="rm48l952.xml" xmlpath="devices"/>
    </platform>
    </connection>
    </configuration>
    </configurations>

      

  • 0 in reply to HaoChe Chen
    TI__Mastermind 22375 points

    HaoChe,

    Please can you answer the following questions?

    1] Were you able to connect to the device previously?

    2] Does the problem started after downloading your application in flash?

    3] Does your application using the AJSM module (JTAG security module)?

  • 0 in reply to Jean-Marc Mifsud
    Prodigy 30 points

    Jean-Marc Mifsud, 

     I try to resoldering RM48L952， and now I can download application in flash, and working well,

     thanks for your help,

    about the Q3, what is the AJSM module(JTAG security)?

    Hao che

     

       

        

  • 0 in reply to HaoChe Chen
    TI__Mastermind 22375 points

    Hao Che,

    AJSM is a module that allows the blocking of any jtag access to the device.

    My default, the device is in unlock state. So it is possible to access the part via jtag to program the internal flash and debug your application. Once your application is fully debugged and stable, it is possible to block jtag access.
    This is possible by changing (programming) the AJSM key (located in custom OTP).
    At that point, access to the device is only possible after scanning the new key in the AJSM (using a command line utility) The device will remain unlock until the next power on reset.

    NOTE: It is not possible to unlock the device forever once the default key has been reprogrammed.

    I will suggest to refer to the AJSM section in the TRM for your device.