KSDK_1.3.0_K82F_1.0.0 install breaks PE...

[DavidS]

Hello,

I downloaded and installed (unzipped really) Kinetis SDK 1.3.0 Standalone for the FRDM-K82F - Windows.zip, did the Install New Software... and point to the eclipse K82 and it installs fine.

RE-start KDS and it installs stuff OK.

But when I try to create a new project for the frdm-k64f for KSDK and PE I get the following error:

Any help appreciated.

Regards,

David

[Jorge_Gonzalez]

Hello David:

I have not tried, so it's just a guess but I see you have "KSDK 1.3.0_K82F_1.0.0" selected in the Kinetis SDK option:

Can't you select the KSDK v1.3 (not standalone) from that list?

Regards!

Jorge Gonzalez

[DavidS]

Hi Jorge,

Good suggestion.

The option is for KSDK_1.3 and doesn’t mention K82…but the error does.

Going alternate route….uninstalling KDS and re-installing.

I can try to reproduce again by adding in the K82 Zip contents next week and see if I still get that error.

Thank you for reply. Have a great weekend.

Regards,

David

[ivadorazinova]

Hi David,

Do you want to work with K64F for KSDK 1.3 or K82 ?

If you want to work with K82, you must choose K82 processor, not FRDM-K64F.

(For this case you must to have installed Eclipse Update) and path for the package.

In case, that you want to work with KSDK 1.3 and FRDM-K64 just select

I hope this helps.

Best Regards,

Iva

[DavidS · Accepted solution]

Hi Iva,

Thank you for the suggestions.

I had uninstalled KDS and re-installed and associated with KSDK_1.3 only.  Then I made the rookie mistake of applying the FRDM-K82F ZIP file to KSD_1.3 folder.  I had assumed since the ZIP didn't contain a root folder it was to be copied into KSDK_1.3.  A big mistake...

What ultimately worked for me was uninstalling KDS_3.0 and KSDK_1.3, re-installing KDS and KSDK and then making a separate KSDK_1.3_FRDM-K82F only folder.  With KDS_#.0 installed again, I associated it with the KSDK_1.2, KSDK_1.3, and KSDK_1.3_FRDM-K82F and now when I want to create a new project all is good.

I wish the K82F standalone had been an installer.  Would have save me a bunch of time.  But lesson learned.  Hope others can use this to prevent an issue.

Regards,

David