MIMXRT1176 ADP – SEGGER J-Link debugging issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MIMXRT1176 ADP – SEGGER J-Link debugging issue

116 Views
HasanIqbalKhan
Contributor II

Hi everyone,

I am currently working with the MIMXRT1176 / i.MX RT1170 platform. I initially used the MIMXRT1170-EVKB for development, but have now shifted to the MIMXRT1176-ADP for interfacing a parallel RGB panel.

I am facing an issue with SEGGER J-Link debugging on the ADP board.

Environment:

  • Board: MIMXRT1176-ADP
  • Board revision: 700-51950 REV A1
  • Schematic revision: SCH-51950 REV B1
  • MCUXpresso IDE: v25.6.136
  • MCUXpresso SDK: v25.09.00
  • SEGGER J-Link: latest version

On the EVKB, both J-Link and LinkServer worked without any issues. However, on the ADP:

  • Firmware flashes successfully.
  • Debugger reaches the first line of main().
  • If I Step Over once, it stops at:

Break at address "0xdeadbeee" with no debug information available, or outside of program code.

  • Breakpoints at other locations work and are hit correctly.
  • However, Resume/Continue from a breakpoint again results in 0xDEADBEEE.

Could someone please confirm whether J-Link is fully supported with MCUXpresso IDE on the MIMXRT1176-ADP, and whether there is any specific J-Link script, reset/debug configuration, or ADP-specific initialization required?

Could this be related to the memory configuration, external flash/SDRAM, or startup code on the ADP?

Any guidance or working J-Link configuration for the ADP would be greatly appreciated.

Thanks!

0 Kudos
Reply
5 Replies

53 Views
Gavin_Jia
NXP TechSupport
NXP TechSupport

Hi @HasanIqbalKhan ,

Thanks for your questions!

As far as I know, when using JLink with the RT1170-ADP in MCUXpresso IDE, only "attach" is supported while direct debugging is not supported. This is likely a support issue with the JLink flashloader. In IAR, this issue has been resolved. We apologize for any inconvenience this may cause.

Best regards,
Gavin

0 Kudos
Reply

44 Views
HasanIqbalKhan
Contributor II
Is it possible to use debug via USB (J33) ?
0 Kudos
Reply

40 Views
HasanIqbalKhan
Contributor II
One more thing I tried, I connected an external MCU-Link and then tried debugging via the LinkServer in MCUXpresso IDE.

The Execution reached main, I am able to step through from there, but when I try to resume execution it gives "Break at address "0x0" with no debug information available, or outside of program code.", and sometimes when I try to restart execution, it gives "Break at address "0x2230c8" with no debug information available, or outside of program code."

For reference I am trying to run the "MIMXRT1176_dashboard_bt_ble_multiprofile" project, SW1 on the board is set to 01 and SW5 on the board is set to 000000000000.

I tried to test with MCU-Link because the EVKB board uses the same and works fine.

Also I do not think we can use Jlink, as it is clearly mentioned on their website that there is no support for octal flash, which the ADP board uses.

Thanks.
0 Kudos
Reply

25 Views
Gavin_Jia
NXP TechSupport
NXP TechSupport

Hi @HasanIqbalKhan ,

1. J33 is USB-OTG1 and cannot be used for debugging. 

2. It’s not that JLink doesn’t support Octal Flash; it’s just that by default, it only recognizes the flash found on the EVK/EVKB. As for IAR, this is because a corresponding download algorithm is provided. If you’re interested in this topic, you can refer to the RT-UFL project.

3. For information on current debugger/IDE support, please refer to: AN14387: https://docs.nxp.com/bundle/AN14378/page/topics/download_images_to_ADP_board.html

Best regards,
Gavin

 

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2414987%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EMIMXRT1176%20ADP%20%E2%80%93%20SEGGER%20J-Link%20debugging%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2414987%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%20class%3D%22%22%3E%3CSPAN%3EHi%20everyone%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22%22%3E%3CSPAN%3EI%20am%20currently%20working%20with%20the%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EMIMXRT1176%20%2F%20i.MX%20RT1170%20platform%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E.%20I%20initially%20used%20the%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EMIMXRT1170-EVKB%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E%20for%20development%2C%20but%20have%20now%20shifted%20to%20the%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EMIMXRT1176-ADP%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E%20for%20interfacing%20a%20parallel%20RGB%20panel.%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22%22%3E%3CSPAN%3EI%20am%20facing%20an%20issue%20with%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3ESEGGER%20J-Link%20debugging%20on%20the%20ADP%20board%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22%22%3E%3CSTRONG%3E%3CSPAN%3EEnvironment%3A%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EBoard%3A%20MIMXRT1176-ADP%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EBoard%20revision%3A%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3E700-51950%20REV%20A1%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3ESchematic%20revision%3A%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3ESCH-51950%20REV%20B1%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EMCUXpresso%20IDE%3A%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3Ev25.6.136%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EMCUXpresso%20SDK%3A%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3Ev25.09.00%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3ESEGGER%20J-Link%3A%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3Elatest%20version%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%20class%3D%22%22%3E%3CSPAN%3EOn%20the%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EEVKB%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E%2C%20both%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EJ-Link%20and%20LinkServer%20worked%20without%20any%20issues%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E.%20However%2C%20on%20the%20ADP%3A%3C%2FSPAN%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EFirmware%20flashes%20successfully.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EDebugger%20reaches%20the%20first%20line%20of%20%3C%2FSPAN%3E%3CSPAN%3Emain()%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EIf%20I%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EStep%20Over%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E%20once%2C%20it%20stops%20at%3A%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CBLOCKQUOTE%3E%3CP%20class%3D%22%22%3E%3CSPAN%3EBreak%20at%20address%20%220xdeadbeee%22%20with%20no%20debug%20information%20available%2C%20or%20outside%20of%20program%20code.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CUL%3E%3CLI%3E%3CSPAN%3EBreakpoints%20at%20other%20locations%20work%20and%20are%20hit%20correctly.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EHowever%2C%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EResume%2FContinue%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E%20from%20a%20breakpoint%20again%20results%20in%20%3C%2FSPAN%3E%3CSPAN%3E0xDEADBEEE%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%20class%3D%22%22%3E%3CSPAN%3ECould%20someone%20please%20confirm%20whether%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EJ-Link%20is%20fully%20supported%20with%20MCUXpresso%20IDE%20on%20the%20MIMXRT1176-ADP%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E%2C%20and%20whether%20there%20is%20any%20specific%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3EJ-Link%20script%2C%20reset%2Fdebug%20configuration%2C%20or%20ADP-specific%20initialization%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E%20required%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22%22%3E%3CSPAN%3ECould%20this%20be%20related%20to%20the%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3Ememory%20configuration%2C%20external%20flash%2FSDRAM%2C%20or%20startup%20code%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E%20on%20the%20ADP%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22%22%3E%3CSPAN%3EAny%20guidance%20or%20working%20J-Link%20configuration%20for%20the%20ADP%20would%20be%20greatly%20appreciated.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2415185%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20MIMXRT1176%20ADP%20%E2%80%93%20SEGGER%20J-Link%20debugging%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2415185%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F263926%22%20target%3D%22_blank%22%3E%40HasanIqbalKhan%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20questions!%3C%2FP%3E%0A%3CP%3EAs%20far%20as%20I%20know%2C%20when%20using%20JLink%20with%20the%20RT1170-ADP%20in%20MCUXpresso%20IDE%2C%20only%20%22attach%22%20is%20supported%20while%20direct%20debugging%20is%20not%20supported.%20This%20is%20likely%20a%20support%20issue%20with%20the%20JLink%20flashloader.%20In%20IAR%2C%20this%20issue%20has%20been%20resolved.%20We%20apologize%20for%20any%20inconvenience%20this%20may%20cause.%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3CBR%20%2F%3EGavin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2415375%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20MIMXRT1176%20ADP%20%E2%80%93%20SEGGER%20J-Link%20debugging%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2415375%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EOne%20more%20thing%20I%20tried%2C%20I%20connected%20an%20external%20MCU-Link%20and%20then%20tried%20debugging%20via%20the%20LinkServer%20in%20MCUXpresso%20IDE.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20Execution%20reached%20main%2C%20I%20am%20able%20to%20step%20through%20from%20there%2C%20but%20when%20I%20try%20to%20resume%20execution%20it%20gives%20%22Break%20at%20address%20%220x0%22%20with%20no%20debug%20information%20available%2C%20or%20outside%20of%20program%20code.%22%2C%20and%20sometimes%20when%20I%20try%20to%20restart%20execution%2C%20it%20gives%20%22Break%20at%20address%20%220x2230c8%22%20with%20no%20debug%20information%20available%2C%20or%20outside%20of%20program%20code.%22%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20reference%20I%20am%20trying%20to%20run%20the%20%22MIMXRT1176_dashboard_bt_ble_multiprofile%22%20project%2C%20SW1%20on%20the%20board%20is%20set%20to%2001%20and%20SW5%20on%20the%20board%20is%20set%20to%20000000000000.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20tried%20to%20test%20with%20MCU-Link%20because%20the%20EVKB%20board%20uses%20the%20same%20and%20works%20fine.%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%20I%20do%20not%20think%20we%20can%20use%20Jlink%2C%20as%20it%20is%20clearly%20mentioned%20on%20their%20website%20that%20there%20is%20no%20support%20for%20octal%20flash%2C%20which%20the%20ADP%20board%20uses.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2415281%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20MIMXRT1176%20ADP%20%E2%80%93%20SEGGER%20J-Link%20debugging%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2415281%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EIs%20it%20possible%20to%20use%20debug%20via%20USB%20(J33)%20%3F%3C%2FLINGO-BODY%3E