• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 29 subscribers
  • Views 1644 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.

tms570lc4357: tms570lc4357 nPORRST,nRST Problem & CCS Error

BAKE KI
Prodigy 80 points
Part Number: TMS570LC4357

A new circuit was created using tms570lc4357.
An error occurs when connecting CTI20 [JTAG] using CCS7.


A peculiar point is nPORRST: 0.5 V / nRST: 0.01 V.
This figure is JTAG partial schematic. Do you see any problems?

It is a 16Mhz crystal waveform. Is there a problem?

Yellow: OSCIN / Pink: OSCOUT

  • 0
    Prodigy 80 points
    We have solved the problem by changing R237 to 2.2k.
    A new error occurred in CCS.

    Error connecting to the target:
    (Error -233 @ 0x0)
    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.
    (Emulation package 6.0.576.0)
  • 0 in reply to BAKE KI
    TI__Guru 59540 points
    Hello Bake,

    First, what is R237 affecting? This resistor is not included in the schematic excerpts you have included with your post.

    Have you been able to use this emulator previously with a Hercules development board such as an HDK or Launchpad? Could you try it with one of these boards to make sure everything within CCS is setup correctly?

    In your original post you indicated "A peculiar point is nPORRST: 0.5 V / nRST: 0.01 V." After your change to the resistor, is the problem with nPORRST and nRST still present? This indicates the device is being held in reset. Can you check your voltage levels to make sure there is no issues? Specifically, check the Vcc (1,8V) supply since I see OSCIN is the correct voltage level of 3.3V it is unlikely the Vccio supply is an issue.

    If the supplies are all within spec, can you check the current draw of the device to see if there is any unuaually high currents being consumed? This might indicate a board level issue such as a short between voltage domains.