After upgrading to MCUX 11.0, I'm no longer able to see globals or expressions in the debug perspective. Here's a video showing what happens when I try. A copy is attached as well.
I disabled the DevStyle theme since that seems to cause similar display glitches sometimes, but it had no effect. I tried with an example project and got a null pointer exception.
Anyone else having this problem? Any idea how to fix it? It gets pretty tedious having to uninstall MCUX, delete my workspace, and recreate my workspace with all of my preferences and reimport all of my projects every time a glitch like this pops up.
1. C project
3. P&E Multilink Universal w/ latest drivers
4. MKl17Z256VLH4, SDK_2.x_MKL17Z256xxx4, 2.6.0 (228 2019-06-14), only SDK installed
5. Develop and Debug perspectives behave the same way.
7. The IDE is configured with all default settings.
Sometimes the array names are displayed in the Global Variables panel while the code is executing, but they disappear as soon as it is halted.
We are investigating - but it would be helpful to get some clarification from those reporting similar issues on the following in order to help us narrow down on where the problem might lie :
MCUXpresso IDE Support
3. Segger JLink Base (with the latest updates programmed)
5. I'm staying in "Develop" when debugging (as switching to "Debug" caused the error with the Global Vars view)
6. Win 10 always updated
7. default theme
Hope that helps
Is anyone at NXP working on this? In addition to the display issues in the Global Variables panel, hovering over an array name in the code when the debug session is halted just shows a blank window without any data values.
Please can you
It might also be useful if you could copy/paste the text from the gdb-traces entry in the Console View into a text file and attach that too.
MCUXpresso IDE Support
No errors in the log:
!ENTRY com.nxp.mcuxpresso.trace.core 1 0 2019-06-24 10:16:18.343
!MESSAGE PEMicro continuous memory service session connected on port 10224->52766 @ 127.0.0.1
!ENTRY com.nxp.mcuxpresso.trace.core 1 0 2019-06-24 10:16:21.955
!MESSAGE SWO session connected on port 10224->52774 @ 127.0.0.1
The problem seems to be just in the UI. If I stop the debug session, I can see all of the variable names that I've added. When it's running, it's like they're in white-on-white text - I can select an entry and see it, and I can see the arrows that let me expand and collapse structures, but I can't see the content.
This has happened at least occasionally as far back as CodeWarrior 10 at least. I've always just worked around it as best I could. I've always used P&E debug hardware - in this case a Cyclone ACP. I just tried it with an LPC-Link2 and I can view the variables, but it gives me a variety of errors when trying to step through code or resume and pause:
I'm not able to get any useful debugging out of it.
I am experiencing the exact same behavior as in the video with MCUX 11.0 on a Kinetis project. It seems to work fine with single variables, but not with arrays. Were you able to get it resolved?
No, in fact it got quite a bit worse after a P&E update a day or two ago. Now I can't view any structs and the FreeRTOS task list and queue list stopped working. Yesterday I wasn't even able to view any scalar variables - I could only see them by clicking on the 'add' button and looking for the address, and then plugging the address into the memory view.
Here's a video showing what it's doing today.
Thanks for the video, and that is exactly what I am experiencing using P&E Multilink hardware. This is my first use of MCUX after years of using CW and KDS, so I may be going back to KDS for this project. There are some issues with those as well, but they don't seem to be as extensive.