Why I could not debug simple MCXXN546 code in MCUXpresso IDE, getting stuck inside the startup file?

[Elakiya]

Hello, I have tried to flash and debug simple uart test project code to my customized MCXn546VKL PCB board through segger J-Link, once I start my debugging it stuck inside the file startup_mcxn546_cm33_core0.c as shown in screen shot, and heap, stack shows 0% used and stack sometime overflow.

And in console tab I am getting 

[MCUXpresso Semihosting Telnet console for 'MCXN546_Project JLink Debug' started on port 60310 @ 127.0.0.1]SEGGER J-Link GDB Server V8.44 - Terminal output channel

If I try to pause and resume, it is entering to break page and showing "Break at address "0x20018040" with no debug information available, or outside of program code."
@Habib_MS 
I have added above my debug config screenshot and PCB circuit design of the customized MCXN546v power pinout .png file is attached with post. Please analyse both hardware circuit and software tools to find the solution for my debug issue. Kindly check the PCB circuit and debug config to solve my issue. Thanks in advance

[Elakiya]

Hi, kindly check my MCXN546VKL pinout design and debug configuration to solve my issue

[Celeste_Liu]

Hello @Elakiya ,

Sorry for the late reply. Before reviewing your schematic, could you please confirm whether you are using LDO mode or DCDC mode?

For the HLQFP 100 package, I recommend referring to the “3.2 HLQFP100 package” section in our latest UG10092 document.

MCX N Series Hardware Design Guide

You may also refer to UG10343, although it was written for the N23x series, it is still applicable to the N54x series.

MCX N23 HLQFP100 Hardware Design Guide 

I suggest paying particular attention to the power supply part and the debug part.

Please let me know if you have made any progress or if you have any further questions.

BR

Celeste

[Elakiya]

Hello @Celeste_Liu, We are using DC-DC mode and faced the above problem which hangs during debugging and shown Stack, Heap memory 0.0% usage or overflow and we have changed the stack location with code few lines in project_debug.ld file, and in the Properties -> C/C++ Build -> setting -> MCU Linker -> Manage Linker Script is unchecked to make this changes in .ld file included the screenshot with this post.

_vStackTop = 0x20037FF0; 

_vStackBase = _vStackTop - _StackSize;

.stack _vStackBase (NOLOAD) : ALIGN(4)

{

. = _StackSize; 

} > SRAM

After making this changes, it is debugging and running, but why this changes is need in all the generated project file to make it work. Why do I face this problem stack memory? Please give clear explanation. Thanks in advance.

[Celeste_Liu]

Hello @Elakiya ,

I reviewed the linker script in the SDK and I don’t think there is anything wrong with it. As for why your modifications are required in order to debug successfully, I suspect the issue may be related to your application code rather than the linker script itself.

Have you ever enabled TrustZone or any secure features on this MCU?

If you create a new empty project—with no custom code added—and do not modify the .ld file, please test whether the issue “Stack, Heap memory 0.0% usage or overflow” still occurs. Steps see attached. This will help determine whether the problem is caused by the linker script or by the application code.

BR

Celeste