• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 595 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.

LAUNCHXL-F28P55X: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register.

Kamakshi Tatkare
Prodigy 40 points
Part Number: LAUNCHXL-F28P55X


Tool/software:

Hi

I am trying to debug the led_ex1_blinky example on F28P55X. But I get the following error -

Texas Instruments XDS110 USB Debug Probe_0/IcePick_C_0 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 20.2.0.3536)

IcePick_C_0: 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 20.2.0.3536)



I tried resetting and power-cycling. I don't see the target configuration option in debug anymore. How do I fix it?


  • 0
    TI__Mastermind 36526 points

    Hi,

    Could you please look at this app note? https://www.ti.com/lit/pdf/spracf0

    Thanks,

    Ben Collier

  • 0
    Prodigy 40 points

    Thanks Benjamin for the manual!

    I am following this table on page 7 in the JTAG manual -

    Error connecting to the target: (Error -2131 @ 0x0) Unable to access the device register. Reset the device, and retry the operation. If error persists, confirm configuration, pwer-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). 1. Verify that Test Connection in the target configuration passes. If the connection fails, follow the steps for that error code. 2. Set device to wait-boot mode. 3. Follow the Manual Launch instructions and connect to the device. 4. Verify that you are able to read PARTID in the memory browser. 5. Try again to program the device. 6. If applying these steps still fails to clear the error, check the following: Are there password locations on the device? On-chip flash tool settings? Is it possible to program RAM only?

    I did step 1. The test connection succeeds when I select cJTAG(1149.7) 2-PIN advanced mode in connection properties.

    How do I set device to wait-boot mode to perform step 2?

  • 0 in reply to Kamakshi Tatkare
    Prodigy 40 points

    So I set the following positions on switch S3 to put it into wait-boot mode and plugged and unplugged the usb to power cycle:

    GPIO24 (LEFT switch): OFF (logic 0), GPIO32 (RIGHT switch): ON (logic 1)

    And started following the manual launch steps in https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#manual-launch.

    I right-clicked on the desired target configuration file in the Target Configuration View and selected Start Project-less Debug in the context menu.

    Then I connected to the target (Connection to a core can be established by right-clicking on the desired core in the Threads view and selecting Connect Target in the context menu) following step 1 in additional manual launch.

    Then I loaded the program following step 2 in additional manual launch. 

    Now I do not understand what to do in the last step - [Set debug source search paths: For the debugger to provide source code debug visibility, it must know where to find the source files. This can be specified by going to menu Run → Edit Source Search Paths... and using the Add button in the Source Search Path dialog to specify the paths of the source files.]

    Also, do I need to switch the GPIO24 back to '1' again or leave it as it is?

    The code in led_ex1_blinky has GPIO 31, shouldn't that be GPIO 20 or GPIO 21 to match the user LEDs on the LAUNCH-F28P55X?




  • 0 in reply to Kamakshi Tatkare
    TI__Mastermind 36526 points

    Hi,

    Kamakshi Tatkare said:
    Now I do not understand what to do in the last step - [Set debug source search paths: For the debugger to provide source code debug visibility, it must know where to find the source files. This can be specified by going to menu Run → Edit Source Search Paths... and using the Add button in the Source Search Path dialog to specify the paths of the source files.]

    You will not usually need this step. Does CCS show your program being halted at the beginning of main function? 

    Kamakshi Tatkare said:
    Also, do I need to switch the GPIO24 back to '1' again or leave it as it is?

    You can leave it as is, unless you want to boot from flash after a power cycle. 

    Kamakshi Tatkare said:
    The code in led_ex1_blinky has GPIO 31, shouldn't that be GPIO 20 or GPIO 21 to match the user LEDs on the LAUNCH-F28P55X?

    Yes, this is a mistake.

    Best Regards,

    Ben Collier

  • 0 in reply to Kamakshi Tatkare
    TI__Prodigy 10 points

    hey kamakshi,
    do you have any more questions regarding this?

    Dhruv Parekh
    Systems Engineering Intern - TI

  • 0 in reply to Dhruv Parekh
    Prodigy 40 points

    Hey Dhruv,

    Thanks for the reply!

    I could resolve the issues with target config and JTAG. 

    When I hit debug for the led_ex1_blinky, the C28xx_CPU1 thread gets halted. So I hit continue and the debug runs without any errors. 

    But I still don't see the user led (gpio 21). 

    Any suggestions on what I could try next?

  • 0 in reply to Kamakshi Tatkare
    TI__Mastermind 36526 points

    Closed to support offline.