Migrating to KSD1.3

[kyizawwin]

Hi all,

I used KSDK1.1 when I start to use Freedom KL25Z. When Freescale released KSDK1.2, I need to take some time as there is fundamental change in PE components. After I had familiar with 1.2, there is 1.3 is released. Since I am setting up my new PC, I thought I should switch to 1.3 and to my surprised, my projects based on 1.2 no longer work and some fundamental components has changed (like Wait). I'd like to know how you guys managed the migration. What should be the best practice I should adopt? Did you guys use PE?

It'll be good if Freescale standardized PE components name. Every new KSDK is new experience to me and I need to learn a few days to familiarized new KSDK components.

Thanks,

Bryan

Thanks in advance,

Bryan

[ivadorazinova]

Hi Kyi Zaw Win,

Thank you for your feedback and your suggestion.

I understand your situation, but this is a development. We still work on examples, fixing bugs, supporting new MCUs..

But every time you can ask for technical questions and we will help you.

About PE components, there are some known issues and limitations, I recommend you take a look at the Release Note (I´m attaching you the Release Note),

it is located at C:\Freescale\KSDK_1.3.0\tools\eclipse_update

here is described KSDK 1.3 supported processors, boards, peripheral initialization, driver, HAL components and also known issues.

I hope this helps you.

Best Regards,

Iva

[therealfreegeek · Accepted solution]

That is not a good reply, it would be better to understand the NXP strategy towards PE and KSDK development. Tell us what is deprecated and where we should focus for the future.

Are you aware you can leave customers high and dry from one version to the next?

[kyizawwin]

Oh....you point out another good point. What's NXP direction on KDS also? Are they supporting only CodeWarrior in future?

Thanks,

Bryan