search

nxp-mcuxpresso / mcux-sdk-examples

MCUXpresso SDK Examples
Other
48 stars 24 forks source link

Multicore armgcc examples "cannot" be built. #5

Closed Hadatko closed 2 years ago

Hadatko commented 2 years ago

Hello, i took complete sdk for rt1176 from mcuxpresso.nxp.com see: image

Multicore examples cm7 side cannot be built as cm7 example has targets flexspi_nor_debug|release and cm4 has debug|release targets. CM7 is expecting M4 binary at ..//flexspi_nor_debug|release but binary is placed at debug|release folder. erpc_matrix_multiply_mu_rtos.zip -> tak look into armgcc build_.sh and CmakeList.txt for both cores.

I noticed that when i was trying to use standalone app bellow erpc_matrix_multiply_mu_rtos_cm4_erpc_matrix_multiply_mu_rtos_cm7.zip

Issue is at least in rpmsg and mu examples. Not sure if in others too.

MichalPrincNXP commented 2 years ago

Hello @Hadatko , thank you for reporting this behavior. This issue relates to standalone multicore examples, all is ok when building from the sdk package (please use this way until the fix for standalone rt1170 multicore apps is applied). Thank you. Regards Michal

Hadatko commented 2 years ago

Thank you for investigation of this issue.

mcuxsusan commented 2 years ago

Hi @Hadatko, do you have same issue for GitHub SDK delivery? If this issue only exists on standalone multicore example package built from mcuxpresso.nxp.com, I would like to close the issue here.

Hadatko commented 2 years ago

Hi @mcuxsusan SDK delivery from GITHUB i didn't try, but generated SDK package is ok. But the folder structure we are using is taken from example package.

Maybe the name of issue can be renamed to be more specific. But if you want to close it before fixing it it is up to you.

mcuxsusan commented 2 years ago

@Hadatko, thanks for your update. @MichalPrincNXP, could you please provide some detail about how the issue will be fixed and when it will be fixed? I would like to close the issue after you have updated the information about the fix.

MichalPrincNXP commented 2 years ago

@mcuxsusan , this problem has been reported to and being solved by the imx conf tools team. Based on internal records it should be fixed in v11 EAR1. The rootcause are different target names on the cm7 and cm4 sides (specific for imxrt1170/1160).