I have some issues with MCUXpresso when using a J-Link probe and when debugging an NXP i.MX RT1020 board. I can upload and run the code. The code executes successfully and I can ping the board's IP address so I know it works. However, some time after I run the code in the debugger, I get the error as shown in the following screenshot. The board still runs, but I am at that point unable to use the debugger. I have no breakpoints set in the debugger.
screenshot: https://ibb.co/X8XHfyh
I see dead bees
Hi @surfskidude
Thanks a lot for letting me know and for sharing again the link to download your project, I could download it already. Just give me some more time to check it, and I would appreciate so much your patience, our backlog is higher than usual these days.
Please let me know if you have some updates, and also I will keep you informed by our findings as soon as we can test it.
Thanks a lot for your comprehension.
Best Regards.
Pablo Avalos.
Hello Pablo,
Thank you for the email. I do see my response on the support page (support.nxp.com). I'll just duplicate it here since it is public information and maybe easier for you to find.
The complete ready to run project: https://realtimelogic.com/downloads/examples/LspAppMgr-RT1020.zip
Project documentation: https://realtimelogic.com/downloads/bas/rt1020/
Hi Pablo, did you get a chance to test the download I provided? Now after more testing, I believe there are some issues with the lwIP driver.
I inherited the project, but I believe all drivers are original and from a recent SDK. The weird thing is that I do not have issues with the built in JTAG.
Hi @surfskidude
Thanks a lot for reaching our technical support.
Regarding your issue, when the MCU is trapped in the 0xdeadbeef address, it is usually due to some incorrect configuration of the peripheral used and actually if you pause the debugger, you might see a HardFault sometimes or simply the debugger is lost due an incorrect flow of the program. So my question is, did you modified something on the SDK example? and also, do you have the Ethernet port connected for that example?
Hope we can hit the nail on the head soon, please let me know if you have more questions or comments.
Best Regards.
Pablo Avalos.
The debugger goes haywire after it executes ENET_SetSMI in fsl_enet.c, after the following line:
base->MSCR = mscr;
mscr is 304.
I get the error as shown above if I try to step after this line.
The NXP provided driver is in the SDK at 1020\devices\MIMXRT1021\drivers\fsl_enet.c