[csolution] Extend CMSIS Solution input format to configure Custom Datapath Extension CoProcessor (CDECP)

[jkrech]

Description

Devices can specify whether they implement Custom Data Path Extension Coprocessors using the processor elements attribute Dcdecp

When building an application that makes use of a CDECP the compiler needs to know which coprocessors are enabled and can be used by the application.
This changes the command line e.g. for AC6 an Arm Cortex-M55 with Coprocessor 0 enabled looks like this:

-mcpu=cortex-m55+cdecp0

Since the selected processor and the enabled coprocessors define the -mcpu option this can not be easily added via a MISC option and should have an abstraction.

There is Coprocessor from index 0 to 7. We could use a hexadecimal or binary representation added to the processor: in the YAML Input Format.

processor:
  cde_copro: 0x11

This would enable coprocessor 0 and 4

Is this request a Security Requirement?

• Yes

Priority

Low

Related Issues (Optional)

No response

Additional Notes (Optional)

Current workaround is to override -mcpu= adding +cdecpN to the -mcpu string generated for the application.