IMXRT1064 board is showing Unable to connect wire for probe index 1.

[kalyan1]

I followed the procedure according to the previous questions asked in the forum https://community.nxp.com/t5/MCUXpresso-IDE/Link-Server-Unable-to-connect-wire-for-probe-index-1/m-p.... but still we are facing  an issue after pasting the axf file. 

[kerryzhou]

Hi @Jeffries ,

  You are welcome!

   If you have any questions, you also can create the new question post, we will help you in your own question post.

Best Regards,

Kerry

[kerryzhou]

Hi kalyan1,

   The linker you shared is an invalid link, I can't open it.

   So, could you please descript your detailed question again?

   Do you use the MIMXRT1064-EVK board? Which IDE you are using?

   Can you make the onboard debugger works directly? With the CMSIS DAP?

    Please tell me the detail way to reproduce your issues.

Best Regards

Kerry

[kalyan1]

The text file can be opened once if it was downloaded then it can be seen. And the information in the file is ----> error: The interface firmware FAILED to reset/halt the target MCU
type: target

And the issue is when i am trying to flash the program in the mimxrt1064 controller then it was showing an error that it is unable to connect the  link server  probe index 1.And the IDE i am using is MCUxpreeso.

Detailing:-

Actually a program is flashed into the board when it was in debug mode suddenly it stopped and once again after flashing the program it is showing the error like unable to flash.

so we are not using CMSIS DAP to flash the program,we are unable to find out the issue .so let us know any method is there to solve the issue. 

[kerryzhou]

Hi kalyan1,

   Seems the DFAE ask a similar question as you, please try my following method:

Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you.
This issue should be caused by the invalid code is downloaded to the internal flash, which is in fact also the external Winbond QSPI flash, just put in the RT1064 internal chip. Then the debugger will be influenced, it is know issue.
Normally, when meet this issue, customer can enter the serial download mode, and erase all the flash to recover it.
Now, follow me to do it, you can use the MCUBootUtility to finish it.
https://github.com/JayHeng/NXP-MCUBootUtility/archive/v2.4.0.zip
the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility
Then enter the serial downoad mode:SW7:1-OFF,2-OFF,3-OFF,4-ON, power off and power on the board again.
Use the MCUBootUtility to connect your board through the COM, you also can use the USB but you need to connect another USB cable to J9.
After you connect the to the ROM, then you can select the Boot Device Memory, fill the Start address as the MIMXRT1064 flash memory address 0x70000000, length, you can fill 0x10000.
Then click the erase.

After you erase the memory, change the boot mode to internal boot again:SW7:1-OFF,2-OFF,3-ON,4-OFF, power off and power on the board again.
Now, you should can use the MCUXpresso Debug your board again.
You can try it on your side.

If you still have questions about it, please kindly let me know.

Best Regards,

Kerry

[kalyan1]

Thanks for the reply, we got an issue

while following the procedure,pls help me with this issue.

[kerryzhou]

Hi kalyan1，

   Do you already modify the boot mode?

  Power off the board, then :

SW7:1-OFF,2-OFF,3-OFF,4-ON

 Power on the board again.

  Please also note, the COM port is the MIMXRT10640EVKB COM port.

Please check it and try it again.

Any updated information, just kindly let me know.

Best Regards,

Kerry

[kalyan1]

we have checked whether the communication port is connected or not .it is connected. And the switch also configured correctly but still we are facing the issue.please let me know any other modifications is to be done.

Thanks & Regards,

kalyan

[kalyan1]

It is showing  like this...

[kerryzhou]

MCU device should be RT1064 SIP, you are using the rt106x, it's wrong, try it again.

[kalyan1]

still we are facing the same issue.

[kerryzhou]

Give me your whole connection board photo, I will check your hardware connections and the configurations.

[kalyan1]

 

[kerryzhou]

Didn't find any connection issues, that's strange.

Do you have external Segger JLINK on your side?

If you have it, you can use the Segger JLINK to connect the JTAG interface, and remove the on board debugger by disconnect the related jumper, then use the JLINK commander to check whether you can find the ARM core or not. It seems your hardware have issues now.

[kalyan1]

 we have connected through jlink and tried to flash the program but still we are facing the issue, if hardware issue please let us  know how to resolve it..

Thanks & Regards 

kalyan

[kerryzhou]

Hi kalyan1,

  Remove on board J47,J48,J49, J50 jumper.

  Power off and power on the board again, then use the JLINK commander window.

  You can find the JLINK commander window in the JLINK driver install path.

  Then, use the SWD interface to connect your board, this is the RT1050 JLINK commander example, for your reference:

Can you find the ARM core or not?

Any updated information, please kindly let me know.

Best Regards,

Kerry

[kerryzhou]

Hi kalyan1,

  Thanks for your feedback.

  Do you have another USB cable?

   If yes, please plug it to the on board J9, then press the reset button.

   In the MCUBootUtility, Select the USB-HID, can you find the PID VID?

Best Regards,

Kerry