• State TI Thinks Resolved
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 42 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSP432E401Y: ERROR CONNECTING TO THE TARGET - 613@0x0

kalyan
Expert 1735 points
Part Number: MSP432E401Y
Other Parts Discussed in Thread: MSP-EXP432E401Y

Tool/software:

Dear TI team members,

I'm using a msp432E401y customized board and I have been using the same board since last two months. However, suddenly I'm unable to flash the code in my board and getting the error 613 @0x0.

I verified the target connection :

  • The utility identified a 100/110/510 class product and loaded the jioxds110.dll adapter.
  • The controller does not use a programmable FPGA and successfully entered SWD mode after a reset attempt.
  • The SWD Mode Integrity test passed, confirming the proper functioning of the debug probe.
  • The IDCODE register value was read as 0x2ba01477 during the integrity test.

Kindly advise on the issue.

Thank you.

Regards 

Kalyan.

  • 0
    TI__Guru**** 191886 points

    HI,

      Which debug probe do you use?

      How many custom boards do you have? Can you repeat the same issue on all the boards or just one board? If you are having issue on all the boards then it could be the debug probe problem to look at. 

      Can you create a new target configuration file? This is to make sure if there is a possibility that you might have  accidently modified some JTAG setting compared to what was working before the last two months.  

      If you don't have an extra custom board, can you use the debug probe on the MSP-EXP432E401Y LaunchPad board? What is the result?

      Do you remember what code was loaded prior to getting connection error? Is that code in any way putting the device into some type of low power mode where the clock is turned off. If this is the case, there is no clock for the debug probe to synchronize with the target device. Or did you in any way disable JTAG or repurpose the JTAG pins for GPIO? These are all possibilities that can prevent the debugger from connecting to the device. 

  • 0 in reply to Charles Tsai
    Expert 1735 points

    Dear Charles,

    I tried with another board , JTAG worked well with the same code.

    Later again I tried with the earlier non working board with the same code. Fortunately, this time JTAG worked successfully.

    But I want to know what could be the reason for this behaviour.

    Regards

    Kalyan

  • 0 in reply to kalyan
    TI__Guru**** 191886 points
    kalyan said:

    I tried with another board , JTAG worked well with the same code.

    Later again I tried with the earlier non working board with the same code. Fortunately, this time JTAG worked successfully.

    Glad that it is working again. However, I don't know the reason why it suddenly failed. Since it is not a repeatable phenomenon, it is difficult to tell the reason.