You can refer to the latest version of the Dual-CPU App Note:
It explains the steps in detail to enable the CM0+.
By default, the CM0+ does not have access to the BSP_DESIGN_MODUS files, since we expect the customer will only use the CM4.
If you want to enable the design.modus for the CM0+, please add in COMPONENTS= of the CM0+ Makefile the following:
For the ipc-pipes code example, try to open the design.modus for the desired target, save it, and compile it again.
Thanks - that's good information. I tried adding BSP_DEISGN_MODUS to the COMPONENTS variable, and that eliminated the complaint about cycfg_peripherals.h, but replaced it with one about cyhal_hw_types.h. Still, it's progress. I'll read the updated documentation and see if I can figure out where to go next.
That's because the CM0P app is trying to build the HAL library. The HAL library was designed to only work with CM4.
You have to add the CY_IGNORE in the Makefile to ignore the HAL.
You can refer to the Makefile of the ipc-sema how that is done.
That's one of the first things I found in the document you linked. I must say I find the notion of a hardware-specific abstraction layer a bit amusing.
I've modified my code to eliminate the use of the HAL library. Unfortunately, that also has eliminated interrupts from my ADC. Obviously I'm doing something wrong, but I haven't been able to find an example of configuring an input pin with Device Configurator and hooking its interrupt using the PDL's GPIO functions.
We have updated all our code examples to use HAL. You can refer to the cyhal_adc code itself to see how it is done. It is based on the ADC PDL.
Yes, of course that's what I've done. Unfortunately, and rather inexplicably, the HAL examples choose not to use the tool provided for the purpose of configuring the hardware, the Device Configurator, but instead use hard-coded pin assignments. If this is the only way to configure interrupts, I'll be forced to follow suit, but it feels as though this is something of a step backward.