Hi @wj_kwak
For S32K358, S32DS creates two independent projects by default, one for M7_0 and one for M7_2. These projects correspond to the two processing cores. They do not represent a bootloader area and an application area.
The S32DS project creation wizard does not normally create a single project containing the application for both cores. If such a project structure is required, it has to be created/configured manually. However, in most cases there is no need to do this and the typical approach is to use two independent projects, one for each core.
The "Inherit boot core toolchain" option can be used to inherit the toolchain configuration from the boot-core project when creating the project for the other core. If it is enabled, you can select the toolchain only for Cortex-M7_0_0. The toolchain selection for Cortex-M7_0_2 will be greyed-out because the configuration from the Cortex-M7_0_0 will apply.
You can also refer to the multicore examples and documentation provided here:
community.nxp.com/t5/S32K/S32K324-Multi-Core-Example-Project-based-on-Whiteboard/m-p/1547771
The package demonstrates both approaches: independent projects for each core and a single project for both cores compiled into a single ELF file.
So, M7_0 and M7_2 should not be understood as bootloader and application projects. They are simply the projects associated with the respective cores.
Best regards,
Lukas
