MCUX v11.1.1 slow debug performance

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCUX v11.1.1 slow debug performance

1,101 Views
scottm
Senior Contributor II

I've been busy with other things thanks to COVID-19 and haven't been working on firmware much since MCUX  v11.1.1 came out, but I'm putting in some time now and I'm having a heck of a time getting the debugger to perform. Here's a quick video showing some issues: Dropbox - 2020-05-06 10-06-36.mp4 - Simplify your life 

I'm using a P&E Cyclone ACP connected via Ethernet. Firmware and plug-ins are up to date. As you can see in the video, the debugger initially works as it stops on a breakpoint, and from there it gets slower and slower. Hovering over a variable doesn't give its contents anymore, and the variables and global variables views stop refreshing and stop displaying even names.

Incidentally that's something it's done sometimes since at least CodeWarrior 10. It's common to have a tree with arrows to expand branches but it doesn't ever display names or contents.

After stepping through a few lines, the system just stops responding and there's nothing to be done except to stop the debug session.

How do I fix this? And what's the best place to look for relevant logs to see what's going on?

Thanks,

Scott

Labels (1)
0 Kudos
3 Replies

993 Views
lpcxpresso_supp
NXP Employee
NXP Employee

I suspect the "live variables" service responsible for the described behavior. You could try disabling it (see screenshot) and report back whether it fixes the problems. Please also attach GDB traces.

Greetings,
MCUXpresso IDE Support

pastedImage_1.png

0 Kudos

993 Views
Sabina_Bruce
NXP Employee
NXP Employee

Hello Scott,

Hope you are doing well.

Unfortunately, I was not able to open the link that you provided. If possible please try to attach it to the post directly. Can you confirm the OS that you are working with?

The .log is located in the metadata folder in your workspace.

Have you tried with a different device to see if the behavior only occurs when using the P&E Debug probe?

Once you have found the .log file please attach it here as well, so I can check it with detail.

Best Regards,

Sabina

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

----------------------------------------------------------------------------------------------------------------------- 

0 Kudos

993 Views
scottm
Senior Contributor II

Hi Sabina,

I'm using Windows 10 Enterprise. I tried my LPC-Link2 as well, with even worse results - though I don't remember the specific error right now.

I ended up deleting my debug launch configuration and recreating it, and that seems to have me going again. I'll let you know when it starts doing it again.

Regards,

Scott

0 Kudos