• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 942 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Reading sysboot register of AM3359

Niyati Shah
Prodigy 130 points
Other Parts Discussed in Thread: AM3359

Hi,

I have a custom board with SOM containing AM3359. Board was working fine earlier but now it is not booting.I have connected XDS 100 Jtag debugger(v3) with my custom board. I wish to read sysboot register to debug this booting issue. I am using CCS v5.4. I see a register window that has a list of registers but am unable to find sysboot registers(control_status register). Control module itself is not appearing.

Regards,

Niyati

  • 0
    TI__Guru**** 393215 points

    Moving this to the CCS forum.

  • 0 in reply to Biser Gatchev-XID
    Prodigy 130 points

    Thanks Biser.

    To describe more, it throws following error on running test connection:

    An error occurred while hard opening the controller.

     

    -----[An error has occurred and this utility has aborted]--------------------

     

    This error is generated by TI's USCIF driver or utilities.

     

    The value is '-233' (0xffffff17).

    The title is 'SC_ERR_PATH_BROKEN'.

     

    The explanation is:

    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.

  • 0 in reply to Niyati Shah
    TI__Guru**** 433871 points

    Hi Niyati,

    Niyati Shah said:

    -----[An error has occurred and this utility has aborted]--------------------

     

    This error is generated by TI's USCIF driver or utilities.

     

    The value is '-233' (0xffffff17).

    The title is 'SC_ERR_PATH_BROKEN'.

     

    The explanation is:

    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.

    This error is a low level error where even the basic JTAG scan test failed. This is a serious error, usually some kind of HW failure. Please check all your connections (cable, connector, etc).

    ki

  • 0 in reply to Ki
    Prodigy 130 points

    Thank you Ki. It was indeed a hardware issue and is solved now.

    -Niyati