MCUXpresso debugging impossible

[simpledeveloper]

Anybody has vbig problem with debugging with MCUXpresso? 
Basically different projects, all born clean from blank projects from nxp sdks and then evolved, are just impossible to debug with the same problems, tipical cases:

• setting up a breakpoint on a c file, the debugger correctly stops on the line, then removing the breakpoint, the debugger cannot exit the line with none of the debug commands (resume, next line, step into, step over, return) and in this case the only solution is to completely exit the debug session and star all over but the problem is non-recovery since it continue repeating over and over every launched session
• breakpoint setup at a certain code line, then going into functions with "Step into" command, at a certain point going down the call stack the debugger just exit the session without any code error, the last "step into" is just into some defined and clear function and not into some closed library file so there's no apparent reason why the debugger should completely exit without any error.

I already checked on this forum and online, but no reasonable answer neither some solution have been posted rather than "just use the last sdk version" or "go back to where the debug works good and then reapply all the other changes" that clearly are not feasible in many case and not explaining at all the root cause of the problem.

Any suggestion/help?
Thank you

[kackle123]

You mention having multiple projects, so I assume you have much experience with this IDE--if so, my past observations (of this and CodeWarrior) might not help you:

--You can only have so many breakpoints enabled in a project at once.  (4 for the Kinetis K64, for example.)  If you happen to enable more than 4 for the K64, the debugger can malfunction.  The fix is to remove all breakpoints and re-set each. 

--You cannot edit a source file above any breakpoints.  If you do, the debugger can malfunction.  The fix is to remove all breakpoints in that file at least and re-set each.  

--If a breakpoint is set on a line without executable C code (such as a preprocessor statement), the debugger can malfunction.  The fix is to remove all breakpoints and re-set each. 

--Using the 'X All Debugging Sessions' buttons sometimes causes the debugger to act funny.

--Restarting the IDE has fixed debugging issues for me.

--Restarting the computer has fixed debugging issues for me.

--Re-powering the programming pod has fixed debugging issues for me.

--Re-powering the MCU has fixed debugging issues for me.

--Deleting/re-importing the project has fixed debugging issues for me.

--Deleting/restoring the Debug Launch Configuration has fixed debugging issues for me.

--Un/Checking the 'set breakpoint at "main"' setting in the Debug Launch Configuration has fixed debugging issues for me.

[simpledeveloper]

Hi @kackle123 and thank for the kind reply!
Unfortunately for me all the fix you are proposing (thank you again) have already been tried by me, and also others that I have already cited in comments in this community post, I will list them also here to complete your list for future navigants:

- Importing the project in different workspaces of the same MCUXpresso version

- Importing the project into workspaces of different version of MCUXpresso

- Updating CMSIS-DAP debugger firmware version

- Upgrade CMSIS-DAP debugger to Jlink (bought the MCU-Link PRO appositely to try this, cannot be done on basic MCU-link debugger) and debug with this second one

[kackle123]

By the way, I upgraded my MCUX 11.6 to a newer version (11.8, I believe, running on Windows 7) and the debugger was very flaky, so I downgraded back to 11.6 so I could get back to working.

[simpledeveloper]

Given that in the settings I have:
• Zero optimization or optimize for debugging
• Updated debugger drivers that are compatible with mcuxpresso 11.7.1

I tried following some advices found online, these are the tests:
• To go back in project commits until I could, remaining within the same workspace, no improvement
• To import the project in a workspace always of MCUXpresso 11.7.1, it seems that in some cases it is the single workspace settings to be corrupted, no improvement
• To install a new version of MCUXpresso 11.8.1, import the previous project, no improvement

I still can’t get back the control of the debugging session after blocking into a breakpoint.

What else can I try?

[ZhangJennie]

Hi simpledeveloper 

As we can't reproduce your issue, we need to identify where is the problem.

Please create a new project under a new workspace. Import a SDK demo code. Can you reproduce the problem?

Thanks,

Jun Zhang

[simpledeveloper]

Hi @ZhangJennie,

unfortunately I cannot reproduce the problem into a newly imported project from the sdk, and neither in other project than the broken one.
For this reason I stated that the broken part is embedded somewhere in the specific project.

The project hase already some stuffs integrated inside, so it will be time consuming to start all over and re-integrated all the logic that has already been ported inside the broken project.

If we can open a case on the nxp support section for this thing, I will send my project to you so that you can reproduce the behaviour on your own PCs and try to debug some solution.

Let me know!
Have a great day!

[ZhangJennie]

Hi simpledeveloper 

Yes, if the problem can be only reproduced on your specific project, I suggest you creating a private case to NXP imxrt support team. I suggest you providing below information to imxrt support team as well:

1 problem screenshot

2. demo project

3. IDE and SDK version.

4. if necessary, provide the steps of how to reproduce the issue.

We will have an imxrt engineer to help you.

Have a niec day,

Jun Zhang

[simpledeveloper]

I've just created a ticket about this topic, but as far as I know i have to invite partecipants to the case, is it right? There's a way it can be assigned to some nxp application engineers or MCUXpresso team so that I can share also the project with them under NDA to proceed to debug the MCUXpresso bug?
I already contacted application engineers from our direct vendors to debug the issue but nothing is solved at the moment.

Thank you @ZhangJennie 

[ZhangJennie]

HI simpledeveloper 

Your private ticket was assigned and answered.

You could just contact the case owner for sending the code.

Thanks,

Jun Zhang

[simpledeveloper]

Hi @ZhangJennie , the case was close by mistake by the assigned nxp employee, it needs to be re-opened ASAP since it is not solved at all and critical.
Could you eventually re-open it or internally contact the employee to do so? thanks

[ZhangJennie]

I saw your private ticket is reopened. The engineer will continue working on it.

[simpledeveloper]

MCUXpresso IDE v11.7.1 [Build 9221] [2023-03-28]

SDK_2.x_MIMXRT1060-EVKB, version 2.13.1

versions are alligned as stated in:
https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-i... 

SDK v2.13 requires IDE V11.7.x or later

[ZhangJennie]

Hi simpledeveloper 

What is your IDE version and what is your SDK version? It's happened if IDE and SDK versions don't match.

As this problem is not replicatable on my MCUXPresso IDE. I need to know the full enviroment of how to reproduce the issue?

Thanks,

Jun Zhang

[simpledeveloper]

The versions are ok, check my other comment