MCUXpresso IDEのトピックRe: Debugger issue(open SDA)

Debugger issue(open SDA)

pandi — Tue, 30 Apr 2024 07:13:57 GMT

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

PANDI

Re: Debugger issue(open SDA)

pandi — Fri, 03 May 2024 14:07:41 GMT

@ewilliams

@Pavel_Hernandez

if any one knows pls let me know debugger issue?

Same problem

PANDI

Re: Debugger issue(open SDA)

Pavel_Hernandez — Sat, 04 May 2024 02:12:46 GMT

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

Re: Debugger issue(open SDA)

pandi — Mon, 06 May 2024 07:40:18 GMT

@Pavel_Hernandez Thank you for your reply

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.

Thankyou

PANDI

Re: Debugger issue(open SDA)

Pavel_Hernandez — Mon, 06 May 2024 18:23:21 GMT

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

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

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

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.

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

Re: Debugger issue(open SDA)

pandi — Tue, 07 May 2024 07:44:16 GMT

@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

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

Thank you

PANDI

Re: Debugger issue(open SDA)

Pavel_Hernandez — Wed, 08 May 2024 02:39:29 GMT

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).

To communicate directly to the MCU use this J19.

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

Best regards,
Pavel

Re: Debugger issue(open SDA)

pandi — Wed, 08 May 2024 08:39:06 GMT

@Pavel_Hernandez

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

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

PANDI

Re: Debugger issue(open SDA)

Pavel_Hernandez — Thu, 09 May 2024 01:24:29 GMT

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?

Best regards,
Pavel

Re: Debugger issue(open SDA)

pandi — Thu, 09 May 2024 12:39:49 GMT

@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.

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

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

Thank you

PANDI

Re: Debugger issue(open SDA)

Pavel_Hernandez — Thu, 09 May 2024 18:43:49 GMT

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.

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

Work as expected.

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

Best regards,
Pavel

Re: Debugger issue(open SDA)

pandi — Fri, 10 May 2024 12:21:05 GMT

@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

PANDI

Re: Debugger issue(open SDA)

Pavel_Hernandez — Mon, 13 May 2024 23:33:05 GMT

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