*****

Hi Philip,

Syscfg has the functionality to switch the target device for your configuration -- just click on "Show device view" in the top right and then switch:

From there, you have the option to target a new device and automatically port over the peripheral configurations. Obviously, this does not work 1:1 for all devices as peripheral offerings are different, but syscfg will tell you where those conflicts are.

Best,

Sam

Syscfg has no errors just compilation as described 

Hey Philip,

Ah, I think I understand your issue a bit more clearly. The G1519 does not have any opamps, so the code you have copied over from the G3507 which references this peripheral is not compatible. You will have to change any user code that uses opamps.

Best,

Sam

But I do not have any explicit code that I have written for the op-amp, for example.

It must all come from syscgf setup...and as the 519 does not have an opamp, why is there code ??

So it looks like dl_gpamp.h is being included in the build.

BUT the devices does not have one and I can't find a way of excluding this from the build...

I tried creating a fresh G1519 project in syscfg and also ported over a G3507 project in CCS and did not have the same compilation errors, could be something to do with your development environment. Could you share your version of sysconfig?

msp.h should look at DeviceFamily_ID and include the corresponding header (ti/devices/msp/m0p/mspm0g151x.h in this case) which defines which peripherals the device has. My guess is that your headers are defining __MSPM0_HAS_GPAMP__ and causing issues. Are you able to trace back to the included msp files and check?