• State Answer Suggested
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 780 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.

Error connecting to the Target Board.

Vipin A N
Prodigy 50 points
Other Parts Discussed in Thread: TMS320VC5509A

Hi,

I'm getting the following error message in CCS 3.1 while trying to connect the board,using TMS320VC5509A DSP.

Error connecting to the target:
Error 0x80000242/-1143
Fatal Error during: Memory, Initialization, OCS,
The memory at 0x000000BE continually indicated it was 'not ready'
All memory operations currently in progress were aborted in order
to regain control of the processor.
This is considered a catastrophic event, but the debugger should
still be able to access memory and CPU registers.
System state has been altered.  It is strongly advised
that the processor should be reset before resuming execution

Regards

Vipin

  • 0
    Genius 4530 points

    Hi Vipin,

    Are you using your own custom board?

    Which emulator are you using to connect to the target?

    What happens after the error, does it continue to occur again and again? Or occurs only the first time and then you can work normally?

    This error generally occurs due to some runtime error in emulator connection which results in a discrepancy in reading the correct state of the target. So some details about the questions I asked above might help.

    Regards,

    Sid

  • 0 in reply to Sid
    Prodigy 50 points

    Dear Sid,

                We are using the BlackHawk USB 510L Emulator.If I 'Retry' to connect the board after pressing the reset button,it shows the same error again.

    Regards,

    Vipin

  • 0 in reply to Vipin A N
    Genius 4530 points

    Hi Vipin,

    USB emulator has the feature of variable clock frequencies. try with a slower clock for JTAG (TCK). You didnt mention whether you are using a custom board or any EVM? Alos, is this the problem right from the start or the board has suddenly started giving these problems?

    regards,

    Sid

  • 0 in reply to Sid
    Prodigy 50 points

    Hi Sid,

        We are using the custom board and it was working properly before. now only it started giving these problems.

    Regards,

    Vipin

  • 0 in reply to Vipin A N
    Genius 4530 points

    Ok,

    this means that either the emulator or the board has gone awry.

    Have you checked JTAG Chain integrity? Specturm digital XDS510 uses SDConfig feature for continuous scan which helps it to test chain integrity, Not sure ,what Blackhawk has. Also try dbgjtag from command line , it gives details about error.

    Regards,

    Sid

  • 0 in reply to Sid
    Prodigy 50 points

    These are custom boards. They were working and have started showing "JTAG disconnected" messages. We have NOR Flash. Some of these boards are working ( we made 20) some marginality exists. The JTAG signals on the scope look fine. Can we send the schematics. Using CCS3.1. 5509A is at 12Mhz clock

     

    Regards

     

    Vipin

     

     

  • 0 in reply to Vipin A N
    Genius 4530 points

    Hi Vipin,

    you can attach the schematics here. But, I didnt understand what you meant by this - Some of these boards are working ( we made 20) some marginality exists.

    What kind of margianility? Also, have you tested other working boards using present emulator to ensure that the emulator is still OK. If you can isolate as t owhether the emulator or the board is faulty, then you can concentrate more on the faulty case.

    Regards,

    Sid

  • 0 in reply to Vipin A N
    TI__Expert 6995 points

    The error seems to indicate that the debugger cannot read the memory mapped registers.

     

    There is an article to help debug JTAG problems, I might prove useful to you:

    http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

     

    On Chapter 3 of the XDS560 document, you will find some design considerations for target boards. In particular, make sure that if the distance form the emulator header and the device is greater than 6 inches, the appropriate buffers are placed.

    http://focus.ti.com/lit/ug/spru589a/spru589a.pdf

  • 0
    Intellectual 270 points

    Hi Vipin, we also have seen this error - it happened when we increased the crystal frequency from 10MHz to 20MHz we see the error on our XDS510 Emulator (CCS3.3.) and on the XDS100 Emulator (CCS4) - the signals for the 10MHz and 20MHz to and from the emulator appear to be OK - any suggestions?

    Regards

  • 0
    Intellectual 270 points

    We found two things - 1) Signal integrity between the emulator and the hardware platform whilst appeared to be OK was not - we added a ground plane with some EMC copper tap and this fixed the problem - we were able to try the solution out on 6 boards all of which then worked at the higher frequency. 2) We ensured the flashed memory was erased so that the lower frequency configuration did not load through the boot process.