When following the example documentation for the ADSP SC589 EZLITE BSP, the instructions include creating a debug session of the core 1 project.
When following the instructions (which appear out of date with the current Crosscore version) which suggest that the projects for each core should be built in a particular sequence, Crosscore fails to build the Core1 project. Core 0 and Core 2 build correctly. Crosscore by default builds the selected project first, and then core 0 and the subsequent unbuilt core project automatically on any build call from the CCES UI. As such, it is not possible to follow the prescribed order of Core0, Core2, Core1 from the 'build project' buttons..
The error return is as follows:
cc2388: catastrophic error: cannot open source file "sys/ADSP-SC58x.h"
cc3089: fatal error: Compilation failed (code:4)
make: *** [system/Services_Init.doj] Error 1
It would appear that the path '/ADI_SC589_EZKit/Lib/VendorInclude' contains the offending file, as opposed to '/ADI_SC589_EZKit/Lib/VendorInclude/sys'
Modifying the include statements that look for the 'sys' folder results in moving forward to a failure to link.
Adding the VendorInclude folder to the link does not fix the problem.
The linker error reported is as follows:
cc3089: fatal error: Link failed (code:1)
make: *** [C:/DSPConcepts/ADI_SC589_EZKit/Build/SC589_Ezkit_BSP_Core1/../../Bin/SC589_Ezkit_BSP_Core1.dxe] Error 1
Could someone please confirm their version of the BSP is building correctly, and could you please also suggest a direction to look in for a fix?
As an aside; AWE 6.18.2 by default installs with a default file path the includes space characters. If you store BSPs for ADSP core in the DSP Concepts folder, CCES will fail to build because the make system cannot handle space characters in file paths. While this is not a bug, it is a pain.