Frdm KE15z "0 available SWD Devices detected. Connect a device and try again"

cancel
Showing results for 
Search instead for 
Did you mean: 

Frdm KE15z "0 available SWD Devices detected. Connect a device and try again"

Jump to solution
977 Views
daonguyen3154
Contributor II

Hi, 

I am having a problem. When trying to initiate Debug, the probe is detected:

pastedImage_1.png

But when I pressed OK button, it cannot access to SWD link:

pastedImage_2.png

I tried with reset button, restart my computer, but none of them work. How can I fix this?

Best regard,

0 Kudos
1 Solution
664 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hi Nguyen,

 

Do you have an external debugger so you could check if you can program the MCU someway?

 

Best Regards,

Alexis Andalon

View solution in original post

0 Kudos
16 Replies
664 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hi Nguyen,

Could try using the erase feature from MCUXpresso to see if the firmware did lock the MCU?

pastedImage_1.png

Best Regards,

Alexis Andalon

0 Kudos
664 Views
daonguyen3154
Contributor II

Hi Alexis, 

pastedImage_4.png

I tried with the GUI Flash tool, but when I chose Mass erase, it still cannot find SWD link

pastedImage_6.png

Best regard,

0 Kudos
664 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hi Nguyen,

Do you have both this headers placed? This are the SWD lines connected from the debugger to the MCU.

pastedImage_1.png

Also you could try updating the firmware debugger, press the reset button while powering up the board. A mass storage device will be enumerated, download the firmware from the following link and drag and drop to this device.

Let me know if this helps you.

Best Regards,

Alexis Andalon

0 Kudos
664 Views
daonguyen3154
Contributor II

Hi, 

Thanks for the replies. My board still had all the headers. I also tried firmware update by following step by step but it didn't work for me either.


Best regard.

0 Kudos
664 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hi Nguyen,

Can you let me know which MCUXpresso version are you using and could you try updating the firmware to the one from segger and do the following test?

-Open the J-Link Commander and check that the power is around 3.3 V

pastedImage_2.png

-Type the following commands:

   -connect

   -? (Found your MCU)

   -s (SWD)

   -Enter (Default)

And check if it can be connected, if this doesn't happen try the command: "unlock kinetis"

Let me know if this helps you.

Best Regards,

Alexis Andalon

0 Kudos
664 Views
daonguyen3154
Contributor II

Hi,

My MCUXpresso IDE version is 11.0.1_2563


pastedImage_5.png
When I tried to connect, It cannot recognize my chip and show up a table like this.

Best regard.

0 Kudos
664 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hi Nguyen,

Could you try using the latest MCUXpresso version (11.1.0)?

Also, this is a new brand freedom? or did this happen after you flash a program for the first time.

Best Regards,

Alexis Andalon

0 Kudos
664 Views
daonguyen3154
Contributor II

Hi,

I have tried with the lastest MCUXpresso version but it still did not work. 
In addition, this freedom board is not the new one. Before that, It worked well. I just have met this issue for a couple days.

Best regard.

0 Kudos
664 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hi Nguyen,

Could you try again to change the debugger firmware to the DAPLink one?

pastedImage_1.png

After this opening the J-Link Commander the following log should appear, if this no happens something is wrong with the K20 debugging chip.

pastedImage_3.png

Best Regards,

Alexis Andalon

0 Kudos
664 Views
daonguyen3154
Contributor II

Hi, 

I tried to change the debugger firmware to the one you mentioned but It still did not work for me. 

Best regards.

0 Kudos
665 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hi Nguyen,

 

Do you have an external debugger so you could check if you can program the MCU someway?

 

Best Regards,

Alexis Andalon

View solution in original post

0 Kudos
664 Views
daonguyen3154
Contributor II

Hi,

I have a J-link debugger, which headers should I remove to test the MCU work or not? 

Best regards.

0 Kudos
664 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hi Nguyen,

This are the headers you need to remove:

pastedImage_1.pngBest Regards,

Alexis Andalon

0 Kudos
664 Views
daonguyen3154
Contributor II

Hi,

The MCU still worked normally, I can program it by using my J-link debugger.

Best regards.  

0 Kudos
664 Views
Alexis_A
NXP TechSupport
NXP TechSupport

Hello Nguyen,

Could you try to follow the following post to recover the OpenSDA?

How to Recover the OpenSDA V2.x Bootloader | MCU on Eclipse 

Best Regards,

Alexis Andalon

0 Kudos
664 Views
daonguyen3154
Contributor II

Hi,

After a few times I used the J-link debugger to program my board, I tried again with the OpenSDA interface and it worked normally. I don't understand the reason behind this but my board now works well. 

Best regards,
Thanks.

0 Kudos