<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PE 'Error: Unknown type info:' KSDK 1.3 in Processor Expert Software</title>
    <link>https://community.nxp.com/t5/Processor-Expert-Software/PE-Error-Unknown-type-info-KSDK-1-3/m-p/541357#M3920</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have been able to reproduce the issue in a new project. I will ask Processor Expert development team for a solution or a&lt;/P&gt;&lt;P&gt;workaround for this issue.&lt;/P&gt;&lt;P&gt;I will keep you informed.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Marek Neuzil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Jun 2016 20:31:40 GMT</pubDate>
    <dc:creator>marek_neuzil</dc:creator>
    <dc:date>2016-06-23T20:31:40Z</dc:date>
    <item>
      <title>PE 'Error: Unknown type info:' KSDK 1.3</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/PE-Error-Unknown-type-info-KSDK-1-3/m-p/541356#M3919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After updating a KDS 3.2 project from KSDK&amp;nbsp; v1.2 to v1.3, I am getting a long set of errors when Processor Expert loads. &lt;/P&gt;&lt;P&gt;PE v3.0.2.b151214.&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;Even if I create a new project and use these components I still get these errors. &lt;/P&gt;&lt;P&gt;Anyone know why these are occurring and how to get them to go away?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jun 16, 2016 9:03:58 PM Starting Processor Expert service&lt;/P&gt;&lt;P&gt;System directory = C:\Freescale\KDS_v3\eclipse\ProcessorExpert&lt;/P&gt;&lt;P&gt;Internal cache directory = C:\ProgramData\Processor Expert\PECache\763dfdd0&lt;/P&gt;&lt;P&gt;Processor Expert license file = not used (no license file)&lt;/P&gt;&lt;P&gt;Jun 16, 2016 9:03:59 PM Successfully started Processor Expert service&lt;/P&gt;&lt;P&gt;CDE: no license found, using Community Edition License&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_DEVICE_VBUS_DETECT&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_DEVICE_VBUS_DETECT&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_HOST_VBUS_ENABLE&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_HOST_VBUS_ENABLE&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_HOST_VBUS_OVERCURRENT&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_HOST_VBUS_OVERCURRENT&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_ID&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_ID&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_VBUS_ENABLE&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_VBUS_ENABLE&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_VBUS_VALID&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_VBUS_VALID&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_SESSION_VALID&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_SESSION_VALID&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_B_SESSION_END&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_B_SESSION_END&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_VBUS_CHARGE&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_VBUS_CHARGE&lt;/P&gt;&lt;P&gt;Type specification is not defined "typePinPolarity", symbol: PinPolarity_USB_OTG_VBUS_DISCHARGE&lt;/P&gt;&lt;P&gt;Type specification is not defined "typeSignalState", symbol: PinInitState_USB_OTG_VBUS_DISCHARGE&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_DEVICE_VBUS_DETECT from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_DEVICE_VBUS_DETECT from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_HOST_VBUS_ENABLE from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init. state"/PinInitState_USB_HOST_VBUS_ENABLE from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_HOST_VBUS_OVERCURRENT from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_HOST_VBUS_OVERCURRENT from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_ID from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_OTG_ID from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_VBUS_ENABLE from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init. state"/PinInitState_USB_OTG_VBUS_ENABLE from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_VBUS_VALID from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_OTG_VBUS_VALID from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_SESSION_VALID from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_OTG_SESSION_VALID from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_B_SESSION_END from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init state"/PinInitState_USB_OTG_B_SESSION_END from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_VBUS_CHARGE from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init. state"/PinInitState_USB_OTG_VBUS_CHARGE from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typePinPolarity in item "Polarity"/PinPolarity_USB_OTG_VBUS_DISCHARGE from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Error: Unknown type info: typeSignalState in item "Init. state"/PinInitState_USB_OTG_VBUS_DISCHARGE from component /fsl_usb_framework&lt;/P&gt;&lt;P&gt;Cannot create new item, could not load item: symbol = SdkSpecificMethodsMasterInt item = Beans\fsl_dspi\Items\1.2.0\fsl_dspi_master_methods.item&lt;/P&gt;&lt;P&gt;Cannot create new item, could not load item: symbol = SdkSpecificMethodsSlaveInt item = Beans\fsl_dspi\Items\1.2.0\fsl_dspi_slave_methods.item&lt;/P&gt;&lt;P&gt;Cannot create new item, could not load item: symbol = SdkSpecificMethodsMasterDma item = Beans\fsl_dspi\Items\1.2.0\fsl_dspi_masterDma_methods.item&lt;/P&gt;&lt;P&gt;Cannot create new item, could not load item: symbol = SdkSpecificMethodsSlaveDma item = Beans\fsl_dspi\Items\1.2.0\fsl_dspi_slaveDma_methods.item&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2016 04:43:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/PE-Error-Unknown-type-info-KSDK-1-3/m-p/541356#M3919</guid>
      <dc:creator>ericnetherland</dc:creator>
      <dc:date>2016-06-17T04:43:10Z</dc:date>
    </item>
    <item>
      <title>Re: PE 'Error: Unknown type info:' KSDK 1.3</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/PE-Error-Unknown-type-info-KSDK-1-3/m-p/541357#M3920</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have been able to reproduce the issue in a new project. I will ask Processor Expert development team for a solution or a&lt;/P&gt;&lt;P&gt;workaround for this issue.&lt;/P&gt;&lt;P&gt;I will keep you informed.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Marek Neuzil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jun 2016 20:31:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/PE-Error-Unknown-type-info-KSDK-1-3/m-p/541357#M3920</guid>
      <dc:creator>marek_neuzil</dc:creator>
      <dc:date>2016-06-23T20:31:40Z</dc:date>
    </item>
  </channel>
</rss>

