Solved! Go to Solution.
Hi @FNilsson,
I made a mistake on my earlier comment. In previous versions of the SDK, two linked projects were imported, one for the primary core and another one for the secondary core. However, from SDK 25.xx, this is no longer the case. Only one project is imported, which has two directories, one for each core. Therefore this is not the issue.
I recommend you try again, but this time importing the project as a freestanding project, and on a folder closer to C:\ drive. Sometimes issues can arise with the compiler when having a path that's too long.
Hi @FNilsson,
We don't have much more documentation about multicore examples, other than the following two from the MCUXpresso for VS Code User Guide:
Debug Common Operations · nxp-mcuxpresso/vscode-for-mcux Wiki · GitHub
Multicore Examples on LPC55S6x and MCUXPresso SDK · nxp-mcuxpresso/vscode-for-mcux Wiki · GitHub (This is fore LPC55s6x but the multicore characteristics still apply for the i.MX RT devices)
With respect to the error message, do you see both the primary and secondary core imported on your "projects" window? Does this error also happen in standalone MCUXpresso IDE?
Hi, I have not tried the IDE. I've tried VS Code, and I have tried to build and flash using the Linux command line by following the steps from the following sources:
https://mcuxpresso.nxp.com/mcuxsdk/latest/html/gsd/run_project.html
https://mcuxpresso.nxp.com/mcuxsdk/latest/html/develop/build_system/Sysbuild.html
https://mcuxpresso.nxp.com/mcuxsdk/latest/html/examples/multicore_examples/hello_world/readme.html
Neither has worked so far. VS Code generates the error above. It imports the "primary core" project, but there is no second one as far as I can see. I'm also not sure which one to import as the "primary core" example is the only one that appears in the list.
The command-line route appears to work, as it builds and flashes without error. But after I reboot the board, nothing happens. No output over serial.
I've also tried the Multicore manager demo with the same result. Builds, flashes, but no output and no LEDs blinking.
I've added the following to the CMaketext.txt:
> # Convert binary to bin format
> mcux_convert_binary(BINARY
> ${APPLICATION_BINARY_DIR}/${MCUX_SDK_PROJECT_NAME}.bin)
And I built and flashed with the following commands:
> west build examples/multicore_examples/hello_world/primary --pristine --toolchain armgcc --config flexspi_nor_debug -b evkmimxrt1180 -Dcore_id=cm33
> west flash -r linkserver
Hi @FNilsson,
I also noticed that currently, VS Code seems to only import one of the two projects. This might be the root of the issue. I will investigate internally with the VS Code team to see if there is a fix for this issue.
BR,
Edwin.
Hi @FNilsson,
One last thing to consider: What SDK repository are you using? I it the latest (v25.06)?
Hi,
Yes, I'm using version 25.6.0.
Hi @FNilsson,
I haven't been able to replicate this issue. Does the issue occur when running with the normal "Debug" button instead of running the application via command prompt?
So there are two different issues.
Which one is it that you could not reproduce?
When I use the "Debug" button in VS Code, I get the error in the screenshot and when I use the command line, it goes through the entire process without error, but the application does not seem to start on the board after flashing.
In an earlier comment, you said that VS Code did not import both projects. Has that changed?
Hi @FNilsson,
I made a mistake on my earlier comment. In previous versions of the SDK, two linked projects were imported, one for the primary core and another one for the secondary core. However, from SDK 25.xx, this is no longer the case. Only one project is imported, which has two directories, one for each core. Therefore this is not the issue.
I recommend you try again, but this time importing the project as a freestanding project, and on a folder closer to C:\ drive. Sometimes issues can arise with the compiler when having a path that's too long.