• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 78 subscribers
  • Views 660 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.

Original question:

MSP432E401Y: Error: The value is '-233' (0xffffff17). The title is 'SC_ERR_PATH_BROKEN'.

MSP432E401Y: Error -1170 @ 0x0

Stephen Poulsen
Prodigy 140 points
Part Number: MSP432E401Y

 When attempting to flash a new custom board implementing an MSP432e401y, using an XDS110 USB Debug probe on a separate launchpad, I get the following Error  

Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. 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 8.0.903.2)

When I test the connection with the JTAG tester it passes the IR and DR integrity tests. 

I have already reset, and power cycled the device, and tried using a lower clock (100kHz).  Where do I go from here?

  • 0
    TI__Guru 58006 points

    Have you ever had any success programming this device with a known good piece of software?

    Can you perform a JTAG unlock as described here?

    Chris

  • 0 in reply to Chris Sterzik
    Prodigy 140 points
    I had not, Having done so, this solves the problem initially.

    There now appears to be a hardware/firmware interaction issue, that does not make sense to me. I can flash the firmware to the MSP432E launchpad repeatedly wihtout any issues. However the custom board can only be flashed once. The second time I flash it, the 1170 Error reasserts itself.

    Any ideas on what would cause this? none of the issues listed in 6.2 Figure 4 seem to fit.
  • 0 in reply to Stephen Poulsen
    Prodigy 140 points
    For any who come after me. This issues was caused by the exclusion of an external osc crystam on the board. The launchpad includes one, so when my code configured the custom board to use the external crystal, there was no oscilation.

**Attention** This is a public forum