After updating a KDS 3.2 project from KSDK v1.2 to v1.3, I am getting a long set of errors when Processor Expert loads.
PE v3.0.2.b151214.
They are related to fsl_usb_framework and DSPI components which have new features in 1.3. The project builds and runs but it takes a much longer time to load PE and the errors are disturbing. I can see the references to these v1.3 'types' in the PE XML file but they are all set to false and I have verified that they are unchecked in the KDS Component Inspector.
Even if I create a new project and use these components I still get these errors.
Anyone know why these are occurring and how to get them to go away?
Jun 16, 2016 9:03:58 PM Starting Processor Expert service
System directory = C:\Freescale\KDS_v3\eclipse\ProcessorExpert
Internal cache directory = C:\ProgramData\Processor Expert\PECache\763dfdd0
Processor Expert license file = not used (no license file)
Jun 16, 2016 9:03:59 PM Successfully started Processor Expert service
CDE: no license found, using Community Edition License
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_DEVICE_VBUS_DETECT
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_DEVICE_VBUS_DETECT
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_HOST_VBUS_ENABLE
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_HOST_VBUS_ENABLE
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_HOST_VBUS_OVERCURRENT
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_HOST_VBUS_OVERCURRENT
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_ID
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_ID
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_VBUS_ENABLE
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_VBUS_ENABLE
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_VBUS_VALID
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_VBUS_VALID
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_SESSION_VALID
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_SESSION_VALID
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_B_SESSION_END
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_B_SESSION_END
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_VBUS_CHARGE
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_VBUS_CHARGE
Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_VBUS_DISCHARGE
Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_VBUS_DISCHARGE
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_DEVICE_VBUS_DETECT from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_DEVICE_VBUS_DETECT from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_HOST_VBUS_ENABLE from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init. state"/PinInitState_USB_HOST_VBUS_ENABLE from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_HOST_VBUS_OVERCURRENT from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_HOST_VBUS_OVERCURRENT from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_ID from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_OTG_ID from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_VBUS_ENABLE from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init. state"/PinInitState_USB_OTG_VBUS_ENABLE from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_VBUS_VALID from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_OTG_VBUS_VALID from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_SESSION_VALID from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_OTG_SESSION_VALID from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_B_SESSION_END from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_OTG_B_SESSION_END from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_VBUS_CHARGE from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init. state"/PinInitState_USB_OTG_VBUS_CHARGE from component /fsl_usb_framework
Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_VBUS_DISCHARGE from component /fsl_usb_framework
Error: Unknown type info: typeSignalState in item "Init. state"/PinInitState_USB_OTG_VBUS_DISCHARGE from component /fsl_usb_framework
Cannot create new item, could not load item: symbol = SdkSpecificMethodsMasterInt item = Beans\fsl_dspi\Items\1.2.0\fsl_dspi_master_methods.item
Cannot create new item, could not load item: symbol = SdkSpecificMethodsSlaveInt item = Beans\fsl_dspi\Items\1.2.0\fsl_dspi_slave_methods.item
Cannot create new item, could not load item: symbol = SdkSpecificMethodsMasterDma item = Beans\fsl_dspi\Items\1.2.0\fsl_dspi_masterDma_methods.item
Cannot create new item, could not load item: symbol = SdkSpecificMethodsSlaveDma item = Beans\fsl_dspi\Items\1.2.0\fsl_dspi_slaveDma_methods.item
Hello,
I have been able to reproduce the issue in a new project. I will ask Processor Expert development team for a solution or a
workaround for this issue.
I will keep you informed.
Best Regards,
Marek Neuzil