Dual Core Debugging RT1186

[Mastrmat]

Hi, I'm trying to debug the M7 core of an RT1186 using a SEGGER J-Link. However, I'm having a lot of trouble attaching correctly after starting the M33 core. Could you help me with the json.launch configuration? I've attached what I currently have.

{

      "type": "mcuxpresso-debug",

      "name": "Dbg (M7) with JLink",

      "request": "launch",

      "cwd": "${workspaceFolder}",

      "executable": {

        "elf": ""

      },

      "probeSerialNumber": "59101260",

      "isAttach": true,

      "skipBuildBeforeDebug": false,

      "gdbInitCommands": [

        "set remotetimeout 600",

        "set debug-file-directory",

        "set non-stop off"

      ],

      "gdbServerConfigs": {

        "linkserver": {},

        "segger": {

          "device": "MIMXRT1186XXX8_M7",

          "interface": "SWD",

          "gdbServerPath": "c:\\Program Files\\SEGGER\\JLink_V930\\JLinkGDBServerCL.exe",

          "gdbServerArgs": [

            "-select",

            "usb=59101260",

            "-device",

            "MIMXRT1186XXX8_M7",

            "-if",

            "swd",

            "-speed",

            "4000",

            "-port",

            "2393",

            "-swoport",

            "2394",

            "-scriptfile",

            "c:\\NXP\\mcuxsdk\\mcuxsdk\\examples\\_boards\\frdmimxrt1186\\jlinkscript\\frdmimxrt1186_cm7.jlinkscript",

            "-single run"

          ],

          "scriptfile": "c:\\NXP\\mcuxsdk\\mcuxsdk\\examples\\_boards\\frdmimxrt1186\\jlinkscript\\frdmimxrt1186_cm7.jlinkscript",

          "speed": "4000",

          "gdbServerLaunchTimeout": 5000,

          "gdbServerExtraArgs": [],

          "gdbPort": 2393,

          "swoPort": 2394,

          "resetAfterLoad": true

        },

        "pemicro": {}

      },

      "showDevDebugOutput": "raw",

      "probeType": "SEGGER",

      "toolchainPath": "C:\\Users\\mastrmat\\.mcuxpressotools\\arm-gnu-toolchain-14.2.rel1-mingw-w64-x86_64-arm-none-eabi",

      "svdPath": "c:\\NXP\\MIMXRT1186_cm7.xml",

      "preLaunchCommands": [],

      "postLaunchCommands": [],

      "executableLoadTypePriority": "auto",

      "domain": "multicore_manager_secondary_core",

      "stopAtSymbol": "main",

      "extraLoadFiles": [

        "c:\\repo\\sidel_tmp\\flexspi_nor_debug\\multicore_manager_secondary_core\\multicore_manager_secondary_core_cm7.elf"

      ],

      "extraSymbolFiles": []

    }

[mayliu1]

Hi @Mastrmat ，

Thank you so much for your interest in our products and for using our community.

Regarding your question, I think that for the M7 attach session, the main change is to place the CM7 ELF in executable.elf instead of extraLoadFiles. executable.elf provides the program and debug information for the session, whereas extraLoadFiles is intended for additional files to be loaded and does not load their debug symbols.

Please try the simplified configuration below and let me know the result.

Due to NXP policy, I cannot share the source code. Instead, I have attached a key figure for reference.

Please start the M33 debug session first and allow it to start the M7 core. Then attach to the M7 using this configuration. For this setup, the secondary-core debug session should use attach mode. I have removed the duplicate server arguments and other optional settings for the initial test.

If the issue persists, please send the first error reported in the J-Link GDB Server log.

Wish it helps you

Best Regards

May Liu