CW10 Processor Expert problems with Kinetis K10

[MarkP_]

Hi,
I managed to generate PWM signals with bsp_twrk60n512_pe on FTM0_CH0.
Then with modifications on PWM.C got five outputs FTM0_CH0..CH4 working.

Then added ADC and I2C -components to bsp_twrk60n512_pe.
Unfortunatelly this removed my PWM changes (luckily I copied they to svn).
How to configure PE to support five PWM channels?
Also does the PE ADC component support multiple (5) ADC channels?

Processor Expert Component Wizard doesn't start, error:
"Licence for BeanWizard not found. Exiting"

Added into file "cwide-env" (as recommended in this forum):
FLEXLM_BATCH= -add 1
Didn't help.
Then tested by changing CPU to another type to see if Component wizard works, it didn't.
Changed CPU back to MK60N512VMD100.

The Generate Processor Expert Code got broken:
Error: "The Processor Expert project "bsp_twrk60n512_pe" was NOT generated because
of some errors." Problems:
Description    Resource    Path    Location    Type
ERROR: Error in the component setting. More details provided by Component Inspector for this component   

bsp_twrk60n512_pe        GPIO1    Processor Expert Errors
ERROR: Error in the component setting. More details provided by Component Inspector for this component   

bsp_twrk60n512_pe        PWM    Processor Expert Errors
ERROR: Error in the component setting. More details provided by Component Inspector for this component   

bsp_twrk60n512_pe        TRG    Processor Expert Errors
ERROR: Timing setting failed. It is not possible to generate code.    bsp_twrk60n512_pe       

Code Generator    Processor Expert Errors

Reverting file ProcessorExpert.pe, got compile working.
Added I2C to project. This caused an error:
Description    Resource    Path    Location    Type
ERROR: Error in the component setting. More details provided by Component Inspector for this component   

bsp_twrk60n512_pe        I2C2    Processor Expert Errors

How to remove I2C component, now the Component Inspector shows nothing and ProcessorExpert.pe
lost its tree view where components could be removed.

Actually my CPU is MK10X256VMD100, does PE support this?
Modified manually and software ran OK in K10.

Changed in user_config.h:
//#define MQX_CPU     PSP_CPU_MK60N512
#define MQX_CPU     PSP_CPU_MK10X256

Some modifications also needed to PWM.C etc. to get compile:

#include "mqx.h" /* Moved here from below to get compile */
#include "Events.h"
#include "PWM.h"
//#include "mqx.h"

Also added support to K10 into IO_map.h:
/* Prevention from multiple including the same memory map */
/* Check if memory map has not been already included */
#if !defined(MCU_MK60N512VMD100) && !defined(MCU_MK10X256VMD100)
#if TARGET_FINALHW==0
 #define MCU_MK60N512VMD100
#else
 #define MCU_MK10X256VMD100
#endif

How to repair the Component Inspector?
Reinstall whole stuff?

When bsp_twrk60n512_pe is used should bsp_twrk60n512 not be used?
Now I2C is used like this:
i2cDevHandle = _io_fopen (I2C_FILE_NAME, NULL);
(and with quite many _io_write, _io_read and ioctrl-calls).
Does PE-code offer easier API?

BR,
Mark

[MarkP_ · Accepted solution]

Update "Processor Expert Feature 1.0.6b1131-0312" corrected the PE.

Now Components can be added

I'll keep the CPU definition as PSP_CPU_MK60N512.

(idea for correct K10 CPU definition is that possible usb, enet etc. references will be noticed during compile)

At startup the error message:

'Initialize RSE' has encountered a problem.

failed to load initializer
com.freescale.startup.RseInitializer.

~Mark