topic SDK manual selection (2^part) in Kinetis Microcontrollers

SDK manual selection (2^part)

claudiobrunelli — Tue, 27 Nov 2018 00:22:08 GMT

Good morning.

I have just look about sdk manual selection with KDS ide.

As Kerry Zhou wrote me I saw at https://mcuxpresso.nxp.com/en/select to create a custom sdk.

For FRDMK25 everything was ok. And I saw (for my interest) how the flash, used as eeprom, works.

But I have to use the FRDMK27 and I'd like to start as I tried with FRDMK25 but the only project that I can extract from builded sdk is "middleware\multicore\erpc". And no other one.

But giving a look in the unzipped file downloaded from sdk builder site, I can see the files in my interest.

(pflash.c ecc. ecc.)

I tried to re-create the project inserting one by one the requiested file. But it doesn't work and is impossible to compile.

For my app it's very good for me to start with this example but, as I wrote, I can not extract totally from the builded sdk.

And so I cann't start with the flash example.

I hope I explained myself correctly...

Thanks in advance.

Claudio

Re: SDK manual selection (2^part)

kerryzhou — Tue, 27 Nov 2018 06:55:08 GMT

Hi Claudio Brunelli,

Thank you for your interest in NXP kinetis product, I would like to provide service for you.

I think you have mentioned FRDM-KL25 and FRDM-KL27, not FRDMK25 or FRDMK27.

When you open the SDK for FRDM-KL27, please use these folder code:

SDK_2.4.1_FRDM-KL27Z\boards\frdmkl27z\demo_apps

SDK_2.4.1_FRDM-KL27Z\boards\frdmkl27z\driver_examples

Don't use "middleware\multicore\erpc", that is just a middleware driver, not the project.

More details, just like FRDM-KL25, you can refer to the getting started page from the FRDM-KL27:

FRDM-KL27Z|Freedom Development Platform|Kinetis® MCU|NXP

Wish it helps you!

If you still have question about it, please kindly let me know.

Have a great day,
Kerry

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

Re: SDK manual selection (2^part)

claudiobrunelli — Tue, 27 Nov 2018 10:56:53 GMT

Hi Kerry.

You are right. I did a mistake when I was writing. I mean at FRDM-KL27.

But in this case I think I have a wooden head. I'm not very familiar with sdk. As I wrote for sdk about K25, when I want to import a new existing project in KDS ide, I could see different type of project and choose one of them.

pflash_frdmkl25z in my case. And start to write my app from there. And it's great for me this example project because I want to use the sdk only for the flash used as eeprom. For other peripherals I have already have my custom library.

So, I start with a new project base on FRDM-KL27 (with the target will be K17 processor) trying to import the necessary file but it doesn't compile at the end.As you wrote me I tried to use the suggest folder but I can't see any project to import.

I don't know at this popint. For My kds configuration see the attached file, just to try to help me.

Claudio

Re: SDK manual selection (2^part)

kerryzhou — Thu, 29 Nov 2018 08:14:35 GMT

Hi Claudio,

You said:I start with a new project base on FRDM-KL27 (with the target will be K17 processor)

Please tell me the full name of your KL17, I need to check whether you refer to KL27 is correct or not.

Have a great day,
Kerry

Re: SDK manual selection (2^part)

claudiobrunelli — Thu, 29 Nov 2018 13:24:42 GMT

Hi Kerry thanks for your assistance.

In the next future we will use MKL17Z256VFM4.

At this moment I'd like to use a portion of flash as eeprom, with freedom board just to understand how I can use the sdk functions for it, because further on in our application we will need it.

So it's enought for me to start with a simple project where I can call the flash functions.

But without PE.

A project as I found for K25, based on K27(just to use the freedom board) it's ok. So I can see well what happen about flash storing and use only what I really need and, also, to be able to better follow the flow of the code.

As I wrote it's a bit difficult to start with an empty project (like I posted) and insert step by step the right source and include file. Something is always missing and the compiler is crying for error.

See you soon, thanks.

Claudio

Re: SDK manual selection (2^part)

claudiobrunelli — Tue, 04 Dec 2018 00:07:34 GMT

Hi Kerry. Just to update you on my work I tell you that I resolved the question.Starting with an empty project step by step I could to use the sdk without use PE. It's not prompt and so easy but obviously possible. In my opinion in this project condition it's possible to limit the used size code but above all it's possible to follow the firmware flow more easly althought PE it's a good resource to use.

However I thank you for your assistance, See you at the next question.

Claudio

Re: SDK manual selection (2^part)

kerryzhou — Tue, 04 Dec 2018 05:46:53 GMT

Hi Claudio,

Thank you very much for you updated information, and that's very good to hear you can resolved it without the PE.

Actually, if you spent time in the SDK, you will find that code is easy to understanding.

Anyway, if you have the new question in the future, welcome to create the new question post to discuss it.

Have a great day,
Kerry