Debugger issue(open SDA)

[pandi]

Hi

We are using kv31 evaluation board when i program flash retry to connect or abort notification showing.

bellow attached the screenshot if any additional power enabled or any other configuration  missing you have to guide me 

 Screenshot 2024-04-30 114551.pngScreenshot 2024-04-30 114828.png

BR

PANDI

[Pavel_Hernandez]

Hello, may name is Pavel and I will be supporting your case, could you share an image of your environment, about your connections.

The issue is presenting when the debugger does not find the power on the board, could you review you SWD or what kind of debugger are you using the debugger on the board or an external? 

Best regards,
Pavel

[pandi]

Hi

@Pavel_Hernandez Thank you for your reply

WhatsApp Image 2024-05-06 at 12.51.50 PM.jpeg

We are using MKV31F512VLL12 evaluation board in onboard debugger when i try to flash the code without any other connections  it is showing connect or abort notification as displayed  in the figure.

Screenshot 2024-05-04 112201.png

                                                  Thankyou 

BR

PANDI

[Pavel_Hernandez]

Hello, let me show you something, when you have a project without a debug launcher seems like this.

Pavel_Hernandez_0-1715019158310.png

When a debug session is started, a popup window appears with all sondes available.

Pavel_Hernandez_1-1715019220522.png

In this case the board has a J-Link firmware.

Pavel_Hernandez_2-1715019283101.png

If I change for an external debugger or debugger firmware, I need to remove de launcher in order to the IDE stared again the Probe Discovery.

Pavel_Hernandez_3-1715019442201.png

Pavel_Hernandez_4-1715019578791.png

Pavel_Hernandez_5-1715019597421.png

I change the OpenSDA from J-Link to LinkServer, but I need to delete the launcher to change the interface between the IDE and debugger.

Let me know if you have more questions.

Best regards,
Pavel

[pandi]

Hi

@Pavel_Hernandez Thank you for your reply.

We tried download the code as steps give by you, we also deleted the launch file but error not get resolved.

 Due to issue of onboard debugger Now we are using Segger mini EDU for downloading the code we are facing the different issue as mentioned below Screenshot 2024-05-07 123456.pngScreenshot 2024-05-07 123804.png

lWhatsApp Image 2024-05-07 at 12.50.28 PM.jpegScreenshot 2024-05-07 123512.png

with segger also we are  unable to download the code,we are facing the error as mentioned in the image.

                                             Thank you

BR 

PANDI

[Pavel_Hernandez]

Hello, in order to use the external debugger in the board need to use it directly to the target.

The J24 is exclusive to communicate with the MK20 (the debugger).

Pavel_Hernandez_0-1715135667091.png

To communicate directly to the MCU use this J19.

Pavel_Hernandez_1-1715135825570.png

Pavel_Hernandez_0-1715135960485.png

If the error still there, could you please do a mass erase?

Best regards,
Pavel 

[pandi]

Hi

@Pavel_Hernandez 

We are getting still facing below error and when I  erase the program , please tell me the procedure for mass erase.

Screenshot 2024-05-08 124430.png

This is correct or not if not means give correct method of erase the program.

Screenshot 2024-05-08 130009.png

BR

PANDI

[Pavel_Hernandez]

Hello, yes that is a good way to do the mass erase, I saw something on your board.

Could you put the J25 in the default position?

Pavel_Hernandez_0-1715217826209.png

Pavel_Hernandez_1-1715217844816.png

Best regards,
Pavel

[pandi]

Hi

@Pavel_Hernandez  hope you are doing good. Thank you for consistent replies.

The Kv31 evaluation board has issues with the on-board debugger that we are using. When I flash the firmware inti target(); error displaying,
when using external debugger Segger J-link EDU mini is also not functioning. You mentioned that you were still having problems with the initial mass erase program, but when I tried for mass erase in the debug module, the terminal output indicated that it was not powering up.

Screenshot 2024-05-09 165104.png

Both Onboard debugger and with external debugger  Segger J-link  it detects IC  name MKV31F512VLL12  and also detects the debugger name .

Screenshot 2024-05-09 180613.png

Screenshot 2024-05-09 180637.png

From this we are unable to find where the error but still we can`t flash the code.

                                 Thank you

BR 

PANDI

[Pavel_Hernandez]

Hello, I tested it on my side, and this works as expected with the recommendation that I mentioned. Are you sure that the board was working in the past? 

I erased the MCU with the J-Link mini-EDU because this has the LED blinky demo.

Pavel_Hernandez_1-1715279974899.png

Pavel_Hernandez_0-1715279933710.png

Then I start a debug session with the J-Link external debugger.

Pavel_Hernandez_2-1715279978323.png

Work as expected.

Pavel_Hernandez_3-1715279992265.png

Then I tried with the debugger on the board has P&E firmware.

Pavel_Hernandez_4-1715280101477.png

Pavel_Hernandez_5-1715280216825.png

Best regards,
Pavel

[pandi]

Hi

@Pavel_Hernandez  Thank you for your reply.

Our evaluation board was initially working well, but now debugging is not working as mentioned in previous posts. We are unable to find the issue either in the hardware or software.

please tell me possible cases this may occur.

                                        Thank you

BR

PANDI

[Pavel_Hernandez]

Hello, what was the result with the J-Link EDU on the right spot SWD? Did you change your flat cable to the J9?

Could you try changing the debugger firmware to discard if the MK20 works well?
OpenSDA Serial and Debug Adapter | NXP Semiconductors

If the new firmware does not work well, I recommend unsoldering the MK20, to discard any malfunction from this.

Best regards,
Pavel

[pandi]

@ewilliams

@Pavel_Hernandez 

if any one knows pls let me know debugger issue?

Same problem

BR

PANDI