My question deals with Processor Expert Component names.
I am using KSKD 1.3 and KDS 3.00.
When I look at the component repository, say KSDK_Repository\Beans,
I see a USB component named Init_USB_OTG_VAR0. When I look at
the component in the component library of the IDE I see Init_USB_OTG.
The suffix _VAR0 is missing. (I am comparing the IDE repository with
the Windows directory.)
I attempt to build a USB CDC project, using the USB stack component,
Processor Expert is looking for Init_USB_OTG_VAR0, and does not find
it. There are a number of components which also have a name mismatch.
(Missing _VAR0, _VAR1)
The USB stack is in the My Repository repository, while the OTG
component is in the KSDK Repository.
Hello Richard,
The suffix _VAR0 ( _VAR1 and so on) is used for definition of components variants (e.g. every component can have several variants that are used for supporting of all Kinetis MCU). The suffix is used internally by Processor Expert (suffix is hidden) and the component variant is selected according to selected MCU. Therefore there is not any issue that you can see several components with same name but different suffix.
The issue, that you have reported, can be caused by incorrect project design. You are using a user defined component "USB stack" and one KSDK 1.3.0 Init_SUB_OTG_VAR0 component. Is this component inherited in the USB_stack? Have your created the project by using KSDK 1.3.0 and Processor Expert (i.e. are the correct repositories used for this project)?
I am not able to reproduce your problem. Could you provide more details about your project and the reported error(s), please? I will try to reproduce the issue and find the resolution.
Best Regards,
Marek Neuzil
Hi Richard,
I'm not sure, but I think this is a bug (or glitch?) with Processor Expert repositories introduced in KDS v3.0.0. The Init_USB_OTG_VAR0 component is present in the 'Kinetis' repository. It seems to me that for inherited (sub-)components Processor Expert is looking in the wrong place for the sub components. I have reported that problem already, but no resolution yet.
What worked for me (and you could try it) to disable the SDK components in the preferences (Window > Preferences menu):
That Init_USB_OTG_VAR0 component is present in KDS v2.0.0, and it works without issues as well in KDS v3.0.0. But as soon as I had KDSK 1.3.0. installed, issues started. My current solution is to disable the SDK 1.3.0 and to restart the IDE.
If you are using the McuOnEclipse components: I'm planning to release a new version over the weekend with a possible workaround (still testing it).
I hope this helps,
Erich
Thank you very much. I will try disabling the SDK.
Dick Fox
Firmware Engineer
NATIONAL CONTROLS CORPORATION BUSINESS UNIT
INSTRUMENTATION AND SPECIALTY CONTROLS DIVISION
1725 Western Dr | West Chicago, IL 60185 | http://www.ametekncc.com
Phone: (630)621-3118 | email: Dick Fox@ametek.com
Hi Richard,
in case you are using the FSL_USB_Stack: I had to release a new drop because of that.
See McuOnEclipse Components: 17-Oct-2015 Release for a description including the workaround.
It seems that the issue is caused by loading the wrong template file, so you could use the workaround of renaming the template file:
If you create a new USB_Init_OTG component without the template: make sure you set the Init settings as outlined in above article.
I hope this helps,
Erich
Hello Erich,
I am working on a project that will be using the MK22FN256VLH12 chip along
with
a CDC USB device. While waiting for the HW, I am using the FRDM-K22F board
as an early development board.
Your post on Dec 27,2014, "USB with the Freescale FRDM-K22F board" is
similar
to the HW/SW I will be using. The problem that I am having, is getting the
project to
build and execute on the FRDM-K22F.
I downloaded and install the new components per your e-mail message.
The error that I am receiving now is the Init_USB_OTG component generating
an
error message "The component is not supported for selected processor".
Again I am using KDS 3.0.0 and KSDK 1.3. I have installed all of the
available
upgrades.
I tried disabling the KSDK repository but that affects the FSL_USB_CDC
component. It is in the KSDK 1.3 repository.
Dick Fox
Firmware Engineer
NATIONAL CONTROLS CORPORATION BUSINESS UNIT
INSTRUMENTATION AND SPECIALTY CONTROLS DIVISION
1725 Western Dr | West Chicago, IL 60185 | http://www.ametekncc.com
Phone: (630)621-3118 | email: Dick Fox@ametek.com
Hi Dick,
the problem is that you have choosen the Kinetis SDK for your project: the SDK only supports dedicated components made for the SDK, no others.
So if you have the SDK enabled for your project during project creation, you cannot use these components like the FSL_USB_Stack one :-(
Erich
Hi Erich,
I want to thank you for your assistance. My problem was
inclusion of the SDK. Must have had a brain freeze because
I was sure that I did not include the SDK.
Also thanks for the new PE components.
Sorry I misspelled your name.
Dick
Dick Fox
Firmware Engineer
NATIONAL CONTROLS CORPORATION BUSINESS UNIT
INSTRUMENTATION AND SPECIALTY CONTROLS DIVISION
1725 Western Dr | West Chicago, IL 60185 | http://www.ametekncc.com
Phone: (630)621-3118 | email: Dick Fox@ametek.com
Hi Erick,
I remember not selecting the KSDK during project creation. But
I will delete the project and start over.
Thanks,
Dick
Dick Fox
Firmware Engineer
NATIONAL CONTROLS CORPORATION BUSINESS UNIT
INSTRUMENTATION AND SPECIALTY CONTROLS DIVISION
1725 Western Dr | West Chicago, IL 60185 | http://www.ametekncc.com
Phone: (630)621-3118 | email: Dick Fox@ametek.com