Is KSDK v2.0 the way forward?

[adyr]

Hi,

I have been looking at the new KSDK v2.0. I am puzzled as it seems to be a huge leap backwards. Have MQX, MFS, HTTP server, FTP server, ..., etc. been dropped for ever? Will there be any PEx integration at some point?

Will KSDK v1.3 be updated to fix bugs?

I have invested huge amounts of time over the last year developing our new product with the KSDK + MQX and building a web server to control it, etc. believing it was going to be supported and get better but now it has all gone!

Can anyone at Freescale (if NXP hasn't already made you all redundant) shed any light on the future?

Best regards,

Adrian.

[alexeyusoltsev]

Hi,

same here! Moreover I even cant download it:   "Pending download approval" the message i got.

PEx+KSDK were the things made me migrate to Kinetis.

To get the Old KSDK 1.3 FULL I need to download around 300mb and need no any approval. Now for only 1 part i need to dowanload 100mb and wait for some approval. What for?

Are there any public roadmap of the future? Why do we need discret ksdk download for each part? I got like 10 different Kinetis parts on my working place right now. Maybe there any plans to make a paid license to different ksdk? Will MQX die?

I need answers to decide whether or not to migrate other vendor.

[ivadorazinova]

Hi Alexey and adyr!

now you should download KSDK without problems - please check it and let me know.

Here is whole procedure, please check the steps if you are not wrong:

How to: install KSDK 2.0

Using Kinetis Design Studio V3.x with Kinetis SDK V2.0

The decision for downloading each package separately is because of the size.

You don´t need to download whole KSDK package for all boards.

MQX will not be supported by KSDK and PEx will be replaced by another tool.

Please, see the roadmap for coming KSDK versions here Introducing Kinetis SDK v2

I hope this helps you.

Best Regards,

Iva

[PO220]

Hi

You say "MQX will not be supported by KSDK and PEx will be replaced by another tool."

Processor Expres I do not like from the start but I'm using MQX lite with PE.

I still use CodeWarrior an I have to migrate to KDS and KSDK precisely for using MQX (the not lite one)...

How long do you think this will be clarified ?

Thanks in advance

[alexeyusoltsev]

Hi Iva!

Thanks for response. I am from Russia and i got that

from the last week. So the question is: If pending and other stuf is the 1st step will be stop sell MCU's into our country the 2d step ? So i am interesting in a rouadmap. Freescale beeng american company never done such a thing beside TI for example. So i am very exited do I need to change vendor for my projects immideately. I am RnD and making half a year-year of guaranty for my projects. And if, for example, my clients will not be able to buy MCU's next 3 mounths i would made to solve their problems that week i.e. remake the whole project-new pcb's,new firmware, new test stend. Or pay a lot of my money,

Adrian you can look for MQX service here and it's further development here:

MQX RTOS – Embedded Access

[ivadorazinova]

Hi Alexey,

yes, we know about the issue and work on it.

Thank you for your patience, I will keep you informed.

Best Regards,

Iva

[adyr]

Hi Alexey,

Thanks for the link. I'm not sure from the web site what they offer to who but I will contact them to see.

Best regards,

Adrian.

[adyr · Accepted solution]

Thanks Iva. Not the answer I wanted but I appreciate the update. I guess this is the price of free software so can't complain but it is sad as the KSDK 1.3 was starting to come along well.

Do you know if the HTTP, etc. network stacks will make a comeback and work with the FreeRTOS as that is the main reason I think 2.0 is such a big step backwards?

Is MQX and it's suit of protocols being maintained separately like it used to be?

As the KSDK 1.3 with MQX works quite well and I have fixed a lot of the bugs already I guess I will continue with that for my current project.

Best regards,

Adrian.

[mnorman]

The MQX kernel, stacks and middleware have been removed from the Kinetis SDK.  However, MQX Software is still a supported software suite from NXP that is available in the MQX RTOS and MQX for KSDK v1.3 products. New ports of MQX following the “Classic” architecture (i.e. similar style to MQX v4.x) will soon be available for newer Kinetis devices.  From here forward, the Kinetis SDK will focus on open-source RTOS solutions.

We are working on a more comprehensive, unified communication stack to replace RTCS in the KSDK.  For now, we offer lwIP as a TCP/IP solution.

Regards,

Michael

[adyr]

Thanks Michael. I have looked at the code for KSDK 2.0 and it does look very clean and efficient so congratulations to the team for that. Obviously for me it is frustrating that MQX support has been dropped from the KSDK as I have already moved a long way down that path with KSDK 1.3 + MQX.

Changing from MQX to FreeRTOS is not a major problem except for loosing the RTCS. The RTCS has a few bugs, some I have fixed and reported and some solutions have been provided by other forum members but some are still causing me problems so I was hoping they would be fixed in future updates. Otherwise I would be happy just sticking with the current solution.

Do you have any approximate time scale for the new RTCS?

Will it have Web Server support?

Do you know if it will support the CGI and SSI call-backs?

Once again, thank you for your input.

Best regards,

Adrian.

[mnorman]

Hi, Adrian,

We are planning an updated web server based on lwip to add CGI and SSI so that we can have the same level of demo available that we had in RTCS.  It will be July at the earliest.  I'll let you know when we have more definitive info. 

-Michael

[martinmadron]

Same questions here, is it a good idea to continue my work with KSDK 1.3?

[PitOn]

Hi Alexey!

Chech email.