RT1170 EVK MCUXpresso "SWD Configuration" 0 available SWD devices detected?

[EdOfTheMountain]

Everything was debugging well, then I started getting this issue.

It started after trying to get M4 to control PRINTF debug and call BOARD_InitDebugConsole instead of M7

I tried re-programming with RT1170 EVK using LPCScrypt and program_CMSIS.cmd

Thanks in advance for any tips or suggestions?

-Ed

[expertsleepers]

This seems to be a common problem. While it's great to be able to use the Boot Utility to recover, do we actually know what causes this in the first place, so we can avoid it happening again?

[kerryzhou]

Hi @expertsleepers ,

  Any issues, please create your own question post, then we will help you in your own question post, thanks.

Best Regards,

kerry

[kerryzhou]

Hi @EdOfTheMountain ,

   Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you.

   When you meet the debugger can't connect issues, normally, you need to do the external flash mass erase at first.

1. Please delete the .launch in your MCUXPresso IDE project, then debug, whether you can find the CMSIS DAP interface, if yes, it means RT1170-EVK on board debugger still OK.

2. Please download the MCUbootUtility tool, then do the flash mass erase in the serial download mode.

  1)  power off, SW1: 1-OFF,2-OFF,3-OFF,4-ON , power on, enter serial download mode.

  2) Download MCUbootUtility tool:

https://github.com/JayHeng/NXP-MCUBootUtility/archive/refs/tags/v3.4.0.zip

the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility

  You can use UART or USB HID connect it, when you use USB HID, you need to find another USB cable to connect J20.

Then you can do the erase.

3. Power off ,SW1: 1-OFF,2-OFF,3-ON,4-OFF , power on,  enter internal boot mode

  Then use your debugger to download the simple SDK project, eg, led_blinky, it should works.

Please try it on your side.

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

Best Regards,

Kerry

[EdOfTheMountain]

Hi @kerryzhou ,

I deleted the ‘*.launch’ files in my MCUXpresso workspace.  When I attempt to debug a blinky or other project project using MCUXpresso, it detects a CMSIS-DAP probe, it also sows up under Windows Device Manager and Human Interface Devices as CMSIS-DAP, and under Ports as LPC-Link II UCom Port. 

However, it finds zero available SWD devices detected. 

I assume this means my on-board debugger is still OK.

I tried making MCU Boot Utility settings match your screenshot. I did not understand what yellow numbers 1 through 6 indicated in your screenshot.  However, I did make Start/Offset and Byte Length numbers match your screenshot numbers, 0x30000000 and 0x10000

When I press "Mass" Erase button I see following message:

"Please configure boot device via Flashloader first!"

Here is what I did:

1) Power-off EVK, disconnect all EVK cables

2) Set SW1 to serial mode: SW1: 1-OFF, 2-OFF, 3-OFF, 4-ON

3) Connect power cable J43, switch on power SW5

4) Connect USB cable to PC host, J11

5) Launch NXP MCU Boot Utility, bin\NXP-MCUBootUtility.exe

6) Select MCU Device: i.MXRT117x, USB-HID says "N/A - Not Found" as seen in your screenshot.

Please note I did NOT connect a second USB cable to J20.  Only J11 USB is connected.  Is J20 USB connection required to " Mass Erase" ?

7) Select tab Boot Device Memory

Change Start/Offset: 0x30000000

9) Change Byte length 0x10000

10) Press button Mass Erase

11) Popup displays saying "Please configure boot device via flashloader first"

I am concerned I may "brick" my RT 1170 if I incorrectly use the MCU Boot Utility. 

There is a lot to understand and learn about MCU Boot Utility.  This tool might also be handy for automated build and testing purposes.

Any advice is much appreciated. 

Thank you for your help,

-Ed

[kerryzhou]

Hi @EdOfTheMountain ,

    Thanks for your information!

   Due to COVID-19, I am working at home and no MIMXRT1170-EVK board on my hand, so I give your the picture which is didn't connect the board, the 1,2,3 means click steps.

  Please note, you must connect J20, this is the USB HID, after you connect it, and repower the board, you will find the USB HID VID number, after that appear, then you click connect button.

  So, you need to use 2 USB cable now.

After you find the USB HID VID number in the following area:

Then connect to ROM, after the connection is finished, then you can do erase.

Please try it on your side.

If you still have issues, give me your connection picture, this MCUbootUtility tool is very easy to use.

Best Regards,

kerry

[EdOfTheMountain · Accepted solution]

@kerryzhou Thank you. 

This is what worked for me.  I used a single cable USB connected to J20 plus external power J43.  J11 was not connected.

1) Power-off EVK, disconnect all USB cables

2) Set SW1 to serial mode: SW1: 1-OFF, 2-OFF, 3-OFF, 4-ON

3) Connect single USB cable from PC host to J20 USB1 (SDB)

4) With power cable J43 connected, switch on power SW5.

4) Launch NXP MCU Boot Utility, bin\NXP-MCUBootUtility.exe

5) Press button “Connect to ROM” on left

6) After “Connect to ROM”, verify USB-HID displays Vendor ID: 0x15A2, Product ID: 0x0073

7) Under Target Setup, select MCU Series and Device: i.MXRT1117x

Select tab Boot Device Memory

9) Change Start/Offset: 0x30000000 ( 8-digits) , Change Byte length 0x1000 (4-digits).

While not required, setting helps you erase flash memory, especially the FCB, IVT,BD area, which influence the boot, and debugger connection.

10) Press button Mass Erase

11) Restore SW1 to internal boot mode: SW1: 1-OFF, 2-OFF, 3-ON, 4-OFF, and reboot EVK board

I can debug again normally using MCUXpresso,

Thank you for your patience and assistance!

-Ed

[Vancongq]

How is 2nd step done on FRDM-KL82Z ?

"Set SW1 to serial mode: SW1: 1-OFF, 2-OFF, 3-OFF, 4-ON"

[kerryzhou]

Hi @EdOfTheMountain ,

    So good to hear your issue is solved now, perfect!

  About your question:Is Step 9 necessary for Mass Erase? 

   No, it just helps you erase some flash memory, especially the FCB, IVT,BD area, which will influence the boot, then influence your debugger connection.

Wish it helps you!

If you have any new issues, welcome to create the new case.

To this case, please help to mark the correct answer, just to close this case, thanks.

Best Regards,

Kerry