• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 285 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.

ICE board - Error connecting to the target

Moonsun Park
Intellectual 595 points
Other Parts Discussed in Thread: AM3359

HI I'm AM3359 ICE board user..

and i'm trying to connect dpram by GMPC

my dpram is Cypress Cy7c024AV as described in ICE board 's schemetic

i found example code in this forum.. and soldering dpram into my board...

but i got this error message and can't boot Example also bootloader ... just power led was ON..

ccsv error message is below

IcePick_D_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 5.0.952.0) 

what should i do?? and what makes this error??

thanks in advance..

Moonsun

  • 0
    TI__Guru**** 393215 points
    Hi Moonseon,
     
    You should check very carefully the board. Possibly you have shorted something during rework.
  • 0 in reply to Biser Gatchev-XID
    Intellectual 595 points

    Thanks your reply

    Of course  i checked miss soldering.. 

    But i couldn't find ..

    is there any procedure that can figure out what is wrong??

    Now i can only see power led 

  • 0 in reply to Moonsun Park
    TI__Mastermind 44306 points

    Moonseon,

    the DPRAM is mainly connected to GPMC and some GPIOs. So I don't see where it would destroy your JTAG access. Only if you shorted power signals...

    Check the power supply voltages.
    Run a known good program from SD card (LED blink) so you see if the processor still comes out of reset.
    Use a scope to measure JTAG signals.
    Measure other critical processor signals (reset, clock,..)

    Did you do any other modifications to the board?

    Since we removed the DPRAM from the boards we are not testing our software anymore with this configuration. So I can't say if ROM bootloader or SPI boot loader can cause any pin-mux conflicts with the additional device. Still you should be able to run the debugger...

    Regards.