MCUXpresso - debugger jumps to unknown address outside of code

cancel
Showing results for 
Search instead for 
Did you mean: 

MCUXpresso - debugger jumps to unknown address outside of code

149 Views
Contributor II

Hello,

I experience a problem while using MCUXpresso (v11.2.0_4120) and I try to debug any code (Demo software or not) using J-Link debugger on JN5189 chip (SDK_2.6.0_JN5189): 

Debugger gets stuck at a weird address which seems to be outside of program code and it doesn't even reach main function.

Please check picture below.

pastedImage_1.png

Anyone had a similar issue or knows a fix for this ?

Thank you in advance,

Andrei Pobega

Labels (1)
3 Replies

55 Views
NXP TechSupport
NXP TechSupport

Hi Andrei, I hope you're doing well!

 

Could you please provide some more information about the behavior you're experiencing?

 

If you're having issues with an Application Note, then there some modifications are needed to debug successfully:

  • First, the Application Note's Makefile needs to be changed for the corresponding chip:
# Set specific chip     (choose one)
#JENNIC_CHIP           ?= K32W061
#JENNIC_CHIP           ?= K32W041
JENNIC_CHIP           ?= JN5189
#JENNIC_CHIP           ?= JN5188

 

  • And the toolchain path needs to be changed to your corresponding MCUXpresso Version:
# Toolchain paths
TOOLCHAIN_DIR_PATH  = ../../../../../MCUXpressoIDE_11.2.0_4120/ide/tools
TOOLCHAIN_PATH      = $(TOOLCHAIN_DIR_PATH)/bin

 

  • The MCU Settings must be configured to use the JN5189 driver:

 pastedImage_2.png

  • In the project's settings, please add the following build command to the options:

DEBUG=HW

Like so:

 pastedImage_3.png

  • And finally, the compiled .axf file needs to be selected in the debug configuration:

pastedImage_5.png

Note: Be sure that the JP4 and JP7 are shorted as 3-4 on the board.

If your issue is with the SDK examples, could you please provide some more information about the example being used?

Please let me know if you continue to have issues.

 

Best regards,

Sebastian

55 Views
Contributor II

Hello Sebastian,

Thanks for the detailed response.

I figured out what was the problem: I did not install the tool chain correctly and the code did not build correctly, even if it showed 0 errors.

It's ok now, thanks a lot !

Have a good day!

Andrei Pobega

55 Views
NXP TechSupport
NXP TechSupport

Hi Andrei,

 

It's great to hear that you got it working!

 

Please let me know if you need any more information or if you have any further issues.

 

Best regards,

Sebastian