Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 03 Jun 2014 08:42 AM by  bradb
Error in connection to OMAP-L138
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages

John Papanikolaou



New Member


Posts:2
New Member


--
28 May 2014 06:32 AM

    Hello,

     

    We have been working with the OMAP L-138 Kit but suddenly we faced the following ERROR when trying to connect:

    -----------------------------------------------------------------

    "Error connecting to the target:
    (Error -2131 @ 0x0)
    Unable to access device register. 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.450.0)"

    -----------------------------------------------------------------

    We have tried the recommended actions but the problem remains. What should we do? 

     

     

     

     


    bradb



    Basic Member


    Posts:203
    Basic Member


    --
    03 Jun 2014 08:42 AM
    John,

    There is a similar post

    on the TI E2E.  The response from the Rafael at TI was the following:


    "The fact the emulator says it can't connect to the ICEPICK_D indicates the connection is not related to any GEL files (internally the ICEPICK_D is a JTAG component that is connected before any core). That said, it is possible the connection is physically ok but the emulator device driver is not able to properly communicate with the emulator because of the use of the virtual machine - at least we experienced several related issues and inconsistent behaviour with the boards and emulators here.

    If you are able to install CCS in the host Operating System (not VM) and connect successfully, I think the solution is either to try to use a different virtual machine vendor or use it in a different PC with native Linux."

     


    You are not authorized to post a reply.