Migrating from CW 10.6 to KDS 3.2

[davidrr]

Hi,

I am using CodeWarrior for a while it is great! working perfrectly. My project uses MKL16ZZ128 with Proccessor Expert tool. I have a problem that my code size is above 64K (codewarrior can't program above 64KB? ) and I read that it is time to move to KDS.

I downloaded KDS and installed it and tried the porting guide and I am sorry but it doesn't work ( after reading in the this forum it worked only few people).

I opened a new project and copied my source files & PE components and I was amazed but it compiled (with little help), but the debbuger interface with P&E multilink is bad, much worst than with CW 10.6.

I get a lot debugger problem for example:

1. source not found.

2. don't close connection to P&E when I stopped my running and more.

IS there any complete guide to transfer CodeWarrior to KDS?

Thanks,

David

[Alice_Yang]

Hello David Raisfeld  ,

Just add,

Since there is no error after you build ,  maybe there is some debug configuration issue.

I recommend you create a simple project, build , debug ,to check whehter it can work well.

About debug configuration , you can refer to "KDS_Users_Guide" -> 2.5 Debugging Projects

Hope it helps

Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[BlackNight]

Hi David,

the easiest way (to me) porting all my CodeWarrior 10.x projects to KDS was following this:

- create a new project for that device in KDS

- copy over the application specific source files

which worked very well for me.

For the Processor Expert components/settings, I can copy the components from one project/IDE to another (see Copy of Processor Expert Components | MCU on Eclipse ).

Other than that, I think Comparing CodeWarrior with Kinetis Design Studio | MCU on Eclipse  might give you an overview about the differences.

I hope this helps,

Erich

[mjbcswitzerland]

Hi

I would have thought that NXP would prefer to have people moving from CW to MCUXpresso, rather than KDS since KDS is also "end-of-life" (?)

Regards

Mark

[BlackNight]

Mark,

yes, indeed, but the question was explicitly to move to KDS. And MCUXpresso does not have Processor Expert, so KDS in that case remains a viable alternative, otherwise the whole application needs to be rewritten.

Erich

[mjbcswitzerland]

Eric

As I understand it, processor expert has been dropped by NXP so this means that although NXP probably would like all to use their MCUXpresso it also means that not all can. This is similar to the fact that K70 (for example) users are still stuck with CW since their devices are not supported (and in some cases officially will never be supported) by newer tools.
Is there a strategy behind this or it is just dictated by marketing/upper management mood changes?

Regards

Mark